Thanks Ryan, I will see if there are any updates. Now that I think about it I haven't updated in a while. I don't know if this helps, but the BSOD cited nv4.dll(?) one of the times. If I'm not mistaken, tha would be the driver for my GPU no? I couldn't read the BSOD the second time, but it was different than the first.I OC'd my chipset, but nothing else. Heat is fine.

You still may have a stability issue, try setting it back a bit and see if things stabilize.

I went through hours of stability tests when I OC'd six months ago. Are you suggesting doing it again? If so I will, just checking to be sure.

I went through hours of stability tests when I OC'd six months ago. Are you suggesting doing it again? If so I will, just checking to be sure.

Not suggesting you go through the entire regiment, just slow things down a bit and see if the problem continues.George

nv4disp.dll was likely the file you saw Ethan - yeah that's the Nvidia driver. I think George may actually have a point with the OCing - I'd go back down to stock clocks and voltage on everything and just verify that the problem is still there... Stability problems can pop up in unexpected ways.

nv4disp.dll was likely the file you saw Ethan - yeah that's the Nvidia driver. I think George may actually have a point with the OCing - I'd go back down to stock clocks and voltage on everything and just verify that the problem is still there... Stability problems can pop up in unexpected ways.

Yeah, thats absolutely true! Even now I can set my CPU voltages the way, that it will run 24/h burn test flawlessly and crash FSX after 15minutes. OCing is not only getting separate components to their maximum, but also to do it keeping balance between them. When OCing I always: test/stress CPU, test/stress RAM, test/stress GPU and in the end test/stress them all together with benchmarks and some games even if I was OCing only single component. During last few years of OCing I found that TDU is very sensitive and therefor great as final test app :)

My personal thoughts,,, if you ran this with no problems before it has nothing to do with your clock. The problem is that at one point you had a crash and the #1 issue I have had with any .dll is the PMDG sound dll. I have done more testing on it alone than anything else and would recommend doing a CTRL+SHIFT start up of FSX. That means you hold those two down, right click the FSX.exe and run by admin if installed in the default directory (regardless if you have UAC shut off) and let it reset alllll of your settings. That means everything including controller settings, FSX settings and trusted dll's. This is the final step you would do before reinstalling but one that works.It's always 50/50 whether or not I see PMDG sound options in the FSX menu as I'm sure is the same with most people. It fails to load the way it should and always has. Years of using all of PMDG's products and even with the work-arounds here (some just are stalls) won't fix it, it just doesn't work right, period (never has).Worst case scenario: Uninstall everything PMDG related. Do a registry cleaner (not really needed, but since you took the time, hey) then reboot and reinstall. You should back up your aircraft folders but they are not registry related so you can paste them back in place later with no problems.If it's hardware related (Overclock falls under that category to me) then it's either a problem with creep of your sound card, you have imbedded sound, or creep with a single stick of ram after your first dim. Shut your PC off, do a power flush (unplug the pc and hold the power button in for 15 seconds) then take out your ram and sound card and reseat them. I have done custom builds for years and now silicon most things in place to keep from "Creep". This is most often seen after moving or bumping a pc but can happen over time with just the low vibrations from the current going from them.

Hey Dan nice to hear from ya. OT: I tried to sign up on your forums when you announced, but received no verification email. You can PM or email me. Guys, I don't know what is going on. All of my hardware has gone kaput. I am now getting BSODs on everything. My mem doesn't pass testing, my CPU doesn't pass any stability tests even underclocked without a BSOD, my GPU is shot, my LCD monitor has purple streaks that vibrate through it no matter what computer it is connected to. Everything is raining down on me. I am in disbelief. Everything was fine.....and then KABOOM! Sooo, nothing you guys can do. I will try to save some money and build a new PC next month. I don't know where I'm gonna get the money, but somehow I'll scrape together something. My HDDs were untouched so I can hook them up to another computer and extract any info I need. *Sigh* Got fired again do to budget cuts.....Not a good Jan 1st .... Not a good one at all.

Ethan,Certainly very strange. Are you certain your power supply is giving everything enough juice?

Just my 2 cents here. I had instability issues with my machine and it was due to me not cleaning my machine out regularly enough. A good clean out of all hardware and re heatsinking my CPU solved if.

Sounds to me like a RAM chip has gone bad. Do you have a code when it BSOD, like 0X000000d. That would let you know for sure.If it was me, I would default BIOS (making a note of all OC settings first)Reboot with one Ram module and see if anything changes, try each RAM module individually and test. I had something similar about a year ago. I RMA'd the ram and it was replaced by the manufacturer.

Ethan,Certainly very strange. Are you certain your power supply is giving everything enough juice?

I bet on PSU too, I had very similar symptoms two weeks ago. Failing PSU makes PC act like everything would be broken, simply try other PSU, borrow from friend or anything.

It could be the PSU, but from my experience a faulty PSU will shut down, not BSOD, without warning. It would also create unreliable cold boot ups.To test, Shut down, wait for it to completely power down[30sec], take out the power cord and leave for ten minutes before putting it all back together again and starting up. Can you get into your O/S?

Thanks everybody for you replies!I do get a code with the BSOD, but it is letters and numbers not 0s. I never thought about a fails PSU, that is a good idea. I have 100watts and 4 +12 Volt rails, so it is more than enough to power it, but if there is a failure or malfunction, that could certainly do it. Hmm, let me get back to you on that one. I will check some stuff and see if, as suggested, I can borrow a PSU to test. Thank you for bringing this to my attention. As for cleaning my PC, I take great pride in the way my PC looks, and I have a windowed case, so my PC is beautifully clean all heatsinks etc are cleaned weekly with an air duster. Thanks though. I'll get back to you on the PSU. I might just buy a new one and call it a day since I am planning on overhauling my three year old home built anyway. I was going for an i7 950 but with the sandy bridge coming out on Wednesday, I'll see what the 'what' is with that and my get that instead. It is hard to plan on cost though since I don't see any 1155 MOBOs on the market yet, so I don't know what to expect for that. I'd really like a MOBO with 6GB/s SATA available. I am expecting around $330 USD for the CPU. We'll see soon enough.

It could be the PSU, but from my experience a faulty PSU will shut down, not BSOD, without warning. It would also create unreliable cold boot ups.To test, Shut down, wait for it to completely power down[30sec], take out the power cord and leave for ten minutes before putting it all back together again and starting up. Can you get into your O/S?

I unplugged and then pushed the power button to drain the capacitors, but it is the same.

You've probably done this already, googling the codes will give you a big clue as to which component is causing the issue.

You've probably done this already, googling the codes will give you a big clue as to which component is causing the issue.

I wish. When it comes up, I can see it for a half second and then the computer turns off. It is so fast that I can get a picture of the screen. The only think that I can tell is that it has an f and an e.