I have WinDBG and symbols installed, if you have the crash dumps I can run it on them

I had the same exact crash report on my x58 motherboard after a bit of research it was just cleaning my computer of dust check cables and even switch them out changed my main power chord from outlet to power supply da da problem gone so give that a shot, I also thought it was my overclock but it was not.

I have WinDBG and symbols installed, if you have the crash dumps I can run it on them

Sounds great! Might see if I can do that tonight. I'll short you a pm later, thanks.

When I started with flightsiming everything ran well. But after several month I started to get lot's of bluescreens. Sometimes 3 or 4 a day, even without FSX running. However, as I replaced my Saitek CyborgX with their ProFlight Yoke the bluescreens stopped. It definataly was a problem with that stick or it's drivers. Maybe you have also a problem with your Saitek stick?

I might get some people rolling their eyes when they read this, as this is regarding the old FS9, but please help! I have been out of flightsimming for almost 2 years, but my gf is letting me use her new computer for it until I can buy my own. I keep getting a blue screen and i've done many searches, tried tons of advice, but I'm still getting it on occasion. At first I thought it was some saitek drivers for my x52, but I got rid of them, and it still happened. I have C++ (installed with PMDG aircraft). I already ran a RAM Diagnostic with no errors found. Can't figure it out guys.Windows 7 64-bitFS9.1 with 64 bit patch to the executable as suggested in the W7 avsim forums.GT520 (yes I know not the latest) with Nvidia Inspector settings at 8xS as suggested by Ryan in his pinned topic (285.62 driver)PMDG 744, 744F, MD-11, Level D 767 all up to date, fresh installs, all for FS98GB RAM DDR3here is the error info:Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033Additional information about the problem: BCCode: 7f BCP1: 0000000000000008 BCP2: 0000000080050031 BCP3: 00000000000406F8 BCP4: FFFFF8800F2C4500 OS Version: 6_1_7601 Service Pack: 1_0 Product: 768_1Files that help describe the problem: C:WindowsMinidump012212-11216-01.dmp C:UsersOnnarashiiAppDataLocalTempWER-23259-0.sysdata.xmlWould setting properties for FS9 to run in WinXP SP3 make this go away? But then wouldn't that cancel out the 64-bit patch to the .exe? Also, would that inhibit the amount of RAM allowed to be used? If anyone could help, or just point me where to go for better help, that would be awesome. As I've said, I have done searches and tried to find a solution already.Thanks!

What did you use for the RAM diagostic? Memtest 86 sometimes lies (I think modern Bios systems attempt to compensate for bad RAM) I've just had a spate of problems with a new PC build. I initially thought it was a RAM problem. Tested it with Memtest 86 and no errors shown. Iwas g to RMA the Mobo and then decided to boot one stick at a time (I have 16gb RAM 4gbx4 modiules) . Booted fine with three modules qand then I got to the last one advice is that if you have more thanm one module try it one stick at a time to see. Other potentioal; causes of blue scvreens of death could be a CPU overheatging (FSX is VERY CPU intensive) if the TEmps are too high under load the CPU will shut down. This sometimes happens if the PC is dirty dusty inside (blocks airflow) or the thermal; past on the CPU has failed. A graphics card overheating could cause the same problem or the mobo could be failing (cheap VRMs are often the culprits). Personally I reckon its a RAM problem.

Personally I reckon its a RAM problem.

It's relatively rarely a RAM issue. The culprit behind BSODs in non-overclocked rigs are usually corrupt files, drivers, peripherals, or junk software.

Opening a crash-dump on another machine might not get the correct results.expecially if one machine is 32-bit and the other is a 64-bit or different OS.If you can manage to read through the windbg help and set the symbol path to the Microsoft server,then it might show something.The key thing is to try to remember the Blue screen header information ...ie SYSTEM_POINTER_PENDING or IRQL_NOT_LESS_THAN_EQUAL orsomething like that.99% of the time it's hardware or drivers.

Yeah, I'm thinking its the saitek x52 drivers for some reason. I remember uninstalling those drivers at one point, bsod went away, but I thought it was something else. Then when I thought I had it figured out, I reinstalled the saitek drivers and programming software. Almost a week later, while using the x52 profiles, I was getting occasional bsod's. Crazy, but that might be it. I'll FINALLY have time tonight to test that after working three days in a row of double shifts.

Opening a crash-dump on another machine might not get the correct results.expecially if one machine is 32-bit and the other is a 64-bit or different OS.If you can manage to read through the windbg help and set the symbol path to the Microsoft server,then it might show something.The key thing is to try to remember the Blue screen header information ...ie SYSTEM_POINTER_PENDING or IRQL_NOT_LESS_THAN_EQUAL orsomething like that.99% of the time it's hardware or drivers.

I will definitely check that if it happens again

hi.I think the most common causes of bsod are RAM, Drivers or Registry. As you have run a RAM diag without any issues, then make sure all your drivers are upto date.. I had a bsod before, and although my drivers were upto date, some of them must of corrupted during install, so after i reinstalled them it sorted it, so try that too. Also, run a registry scan using CCleaner and fix any issues it finds. It's free and can be dloaded here.http://www.piriform.com/ccleanerhope this helps.

hi.I think the most common causes of bsod are RAM, Drivers or Registry. As you have run a RAM diag without any issues, then make sure all your drivers are upto date.. I had a bsod before, and although my drivers were upto date, some of them must of corrupted during install, so after i reinstalled them it sorted it, so try that too. Also, run a registry scan using CCleaner and fix any issues it finds. It's free and can be dloaded here.http://www.piriform.com/ccleanerhope this helps.

I will definitely look into that. Hope reinstalling drivers helps. Just got back from a BSOD now

UPDATE:I reinstalled the latest official drivers from nvidia, still got a BSOD. I also installed win debugging tool. After running the .dmp file, it says that nvlddmkm.sys (located in systems32drivers) is probably to blame. I see that this is an nvidia file, but curious as to why it would cause a problem when I reistalled the latest driver (GT520 1GB RAM). First thoughts are to look up and see if i can delete that file, then reinstall the driver, or do the CCleaner as recommended to fix registry issues. If you need more info on the crash report I can type it up here, but it won't let me copy/paste.Any ideas?

When installing this driver, did you use the clean install option?

When installing this driver, did you use the clean install option?

you know, I am not sure lol. What does that do?

It's supposed to remove all traces of the previous driver install. I usually do this manually, but 'clean install' is supposed to take care of it for you. I'd recommend uninstalling the driver, running the installer again as admin and select 'clean install'Edit: don't let windows install anything by itself unless its a generic VGA driver! Windows updates/auto installs mess up nvidia drivers more than anything else in my opinion and that's why I have windows update set to manual, so I can skip anything to do with my displays.

Edited February 2, 201214 yr by MrKen

Hi..Did the clean install work? ... if not, try booting up your PC in 'Safe Mode' then go into 'Device Manager' .. select your display adapter, uninstall the drivers, then run ccleaner to remove any Nvidia entries in the registry, then restart the system in normal mode, & reinstall the lastest Nvidia drivers... Also make sure that ALL other drivers are upto date, Mobo, sound etc.