Hi. This topic might be better put in the CTD section but as it also has to do with hardware i thought i'd post it here. If moderators want to move it, by all means :)I bought some new Ram from g.skill (8GB 2133 /9-11-10-28) after having low-on-memory issues with my earlier 4GB mushkin 1600CL6 and feeling a bit "ripped off" by the Corsair 2000Mhz CL9 only running 1866 and not 2133 which i had hoped.Right after the switch I had problems starting another game but that was easily fixed by reinstalling the client for it. After starting FSX I got a APPCRASH fatal error when opening the free flight section. The 3D screen of the default plane immediately freezes when opening that screen."Problem signature: Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61355.0 Application Timestamp: 4643ee0a Fault Module Name: d3d9.dll Fault Module Version: 0.0.0.0 Fault Module Timestamp: 4b926eb5 Exception Code: c0000005 Exception Offset: 000013cb OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1053Additional information about the problem: LCID: 1053 FSX was working fine before, unless my memory blacked out and I did some switch inbetween my last working flight and the RAM switch; which i seriously doubt.I have since done 3 stresstests:Intel burntest on maximum ram - completed 5 (default number) passes successfullyOvernight (7h or so) Memtest 4.0a completed without errorsPrime95 blendtest completed 3h without errors or warnings.Can it really be the memory that is faulty or has my fsx install been corrupted somehow? I have windows 7 update on manual download and install.Is it possible to fix this error without having to reinstall FSX/reformat the computer? (i heard the d3d9.dll error is tricky to cure without a full reformat)Any advice is appreciated!

Could've asked me, I could tell you about Corsair not able to run 2133. And SB only supports 1866 OR 2133. No 2000. That's a known fact.I think that everything points to the faulty memory. Test with separate sticks, if you now have 2 or more.

Weird thing is, I just did a clean reinstall of FSX and so far (SP2 installed but nothing else) I'm able to start the sim, run a flight etc without any errors. If the memory was faulty you'd think the stresstests I did would've picked it up. I'll run an overnight blendtest tonight, my corsairs failed that with even a slight OC so if these are faulty hopefully it shows. If nothing shows up and FSX gets unstable I'll do a memtest on each stick.That should be enough, right?

Was d3d9.dll always the fault module? (considering the sim failed at the 3d screen, I assume so) If that was the case, faulty RAM was not the culprit. Typically that points to a DX9/FSX installation issue. That you re-installed FSX, I doubt you'll get your CTD again.

Edited February 9, 201214 yr by ZachLW

Run the Memtest+ on both sticks overnight. That should confirm that the sticks are ok.

Hmm, I just had a BSOD 0x000007A error while watching a video in VLC. I've tried searching for info about the BSOD code but I'm not finding much usuable info. An hour before I updated windows (quite a big update as I hadn't done it in about 3 months).Anyone know what causes that kind of BSOD?

Upload the crash dump. Should be in C:/Windows/Minidump

The folder is empty, dunno why.

The folder is empty, dunno why.

There's a config in Win 7.System Properties -> Advanced System Settings -> Startup & recovery -> Settings -> Write debugging information -> Small memory dump (256KB)

Ok, I did that. But this will only make me read the next crash dump, right?EDIT: What I don't get though is, if one of the sticks are faulty shouldn't the memtest I did last night have come up with errors? Or does the healthy stick somehow "cover" for the bad one?

Edited February 9, 201214 yr by MrGreen

Try downclocking to 1600 CL9 and run it like that for a while. What Vdram are you at and what are the sticks rated to?

Edited February 10, 201214 yr by dazz

The ram sticks are rated at 2133/9-11-10-28, the speed im running them at. If they can't handle that I will have to send them back.I just checked on my computer after an overnight prime95 blendtest and it had rebooted, minidump folder had one .dmp file; how do I read it?As the sticks don't fail memtest but prime95 could it be mobo-related? Maybe I need to increase a voltage somewhere?EDIT: I found a way to read the .DMP file and it said stop code 0x124. Isn't that low vcore?

Edited February 10, 201214 yr by MrGreen

0x0124 is hardware/overclock, not necessarily Vcore. I think it's pretty obvious that if you had a stable overclock with your old RAM, then problem must be the new RAM or more likely the way you're running your new RAMAre these your new sticks?http://www.gskill.com/products.php?index=403Did you manually set Command Rate to 1T? It should be 2T/2NAnd again, what Vdimm voltage did you set for your new RAM sticks? should be 1.65VYou can confirm if it's a memory issue downclocking to 1600 temporarily

Yeah Dario, those are the RAMs I use, and they are set to 1T. I'll switch to 2T but wont that decrease the performance a lot?

No, not at all