I've been getting constant BSOD's, and after many days of trying to fix the problem, I came accross the Windows debugging tool, so I could view the minidump file. Basically what it tells me is that the problem is caused by the : ntoskrnl.exe : My guess is that this is an operating system kernel file. So my question is.....is there an easy way to fix this? Is there a way I can replace this file? I dread doing a reinstall of my operating system. Even then I'm not sure that a reinstall would fix the problem. Any suggestions?Thanks,Chris

I've been getting constant BSOD's, and after many days of trying to fix the problem, I came accross the Windows debugging tool, so I could view the minidump file. Basically what it tells me is that the problem is caused by the : ntoskrnl.exe : My guess is that this is an operating system kernel file. So my question is.....is there an easy way to fix this? Is there a way I can replace this file? I dread doing a reinstall of my operating system. Even then I'm not sure that a reinstall would fix the problem. Any suggestions?Thanks,Chris

ntoskrnl.exe BSOD's indicate a memory issue (you can Google the file for more info). You should run Windows Memory Diagnostics and it should find a problem and indicate you have a hardware problem. I had this BSOD many times when I first set up my new system and I fixed it by changing the memory frequency in the BIOS from 'DDR3-1600MHz' to 'Auto'. That immediately stopped the crashes but a couple of weeks later, I would get a sudden crash while running FSX or running a stress test like Prime95. I then went back into the BIOS and changed my memory timings to one of the supported frequencies for my memory. I had 3 supported frequencies - 444.4 MHz, 592.6 MHz, and 666.7 MHz. Of course I set the memory timings for the 666.7 MHz. I ran stress tests and several benchmarks and have yet to get a BSOD or crash. Maybe this info will be of some value to you too. Bottom line though - you have an issue with your system memory and that's causing your constant BSOD's.Best regards,Jim

Thanks for your response Jim.I was running 12 gigs of ram (corsair). The same ram that is giving me BSOD's! I swapped that set out, and put in a set of 6 gigs (G-Skill) Ram. I Loaded up a flight and completed a 2 hr.40 min flight without a problem. I thought to myself good, my other set of ram was bad. I then loaded up a flight this morning, and what do you know. BSOD with the new set of ram! I'm at a loss. BSOD's with 2 seperate sets of ram. The thing is I have no problems running any other games or applications! Just FSX! I also passed OCCT stress test for 2 hours without a problem. Also I'm not sure how to go about running the windows memory diagnostic tool? Is it a program in Windows itself, or do I need to download it from somewhere? Thanks for your help,Chris

Thanks for your response Jim.I was running 12 gigs of ram (corsair). The same ram that is giving me BSOD's! I swapped that set out, and put in a set of 6 gigs (G-Skill) Ram. I Loaded up a flight and completed a 2 hr.40 min flight without a problem. I thought to myself good, my other set of ram was bad. I then loaded up a flight this morning, and what do you know. BSOD with the new set of ram! I'm at a loss. BSOD's with 2 seperate sets of ram. The thing is I have no problems running any other games or applications! Just FSX! I also passed OCCT stress test for 2 hours without a problem. Also I'm not sure how to go about running the windows memory diagnostic tool? Is it a program in Windows itself, or do I need to download it from somewhere? Thanks for your help,Chris

For opening the memory diagnostic tool, the easiest way is to hit the Start button and where it says search programs, type in memory diagnostic tool and look above in the menu and you'll see it. Click on it and run it. It will run the next time you start up your system. It runs through about 5 tests and it isn't very long. Again, I think BSOD's are the result of bad memory timings in the BIOS. You want to make sure you have the latest BIOS too as an update might fix a memory issue.Best regards,Jim

Hi, Well I tried everything you suggested. I ran the windows memory diagnostic tool without any errors. I loosend up the timing on my ram. I went from 7-8-7-20 to 9-9-9-24 . I updated my bios. And I ran RegServ which is a registry cleaner. I'm still getting BSOD's! Only now Windows Debugger is saying that- win32k.sys -is the problem? Any other suggestions?Thanks for your help,Chris

Hi, Well I tried everything you suggested. I ran the windows memory diagnostic tool without any errors. I loosend up the timing on my ram. I went from 7-8-7-20 to 9-9-9-24 . I updated my bios. And I ran RegServ which is a registry cleaner. I'm still getting BSOD's! Only now Windows Debugger is saying that- win32k.sys -is the problem? Any other suggestions?Thanks for your help,Chris

Here's a possible fix for the win32k.sys BSOD - http://www.pcreview.co.uk/forums/bsod-win32k-sys-crashes-t94921.html . Also, you changed the memory timing and you're no longer getting the ntoskrnl.exe driver as the cause of the crash? That's progress.Best regards,Jim

Well it appears that the problem after all was not enough cpu core voltage! Funny thing is I had passed a 2 hour stress test using O.C.C.T. But apparently that still was'nt enough voltage for FSX. So I bumped up the core voltage a couple of extra notches. No more BSOD's! So be weary that even though you may pass stress tests, FSX may require even more voltage than you passed the stress test with!

Well it appears that the problem after all was not enough cpu core voltage! Funny thing is I had passed a 2 hour stress test using O.C.C.T. But apparently that still was'nt enough voltage for FSX. So I bumped up the core voltage a couple of extra notches. No more BSOD's! So be weary that even though you may pass stress tests, FSX may require even more voltage than you passed the stress test with!

Yes, I had that exact thing happen to me when FSX crashed and I had a BSOD out of the clear blue sky even though I had run Prime 95 and several other stress tests. It was the memory settings. For me it was the timing. Let's hope this fix is permanent.Best regards,Jim