Hey guys, this is an odd one, as up until yesterday I have never experienced a BSOD. After a relatively short flight in Orbx's UK, I got a BSOD shortly after landing Aerosoft's Katana. The strange thing is, for a few minuites prior to the landing, the airspeed seemed not to move, I lost the GPS and radio displays. On approach to landing the plane would not slow up either... all very odd. Then, as I say, I got the BSOD. I ran the little prog BluescreenView and unless I am mistaken, it seemed to point to ntoskrnl.exe as the culprit. Has anyone any idea what the cause could be and how to correct it for the future? Cheers fellas...

 

Need more vCore, Howard.

Hi.

 

I'm sure you may need more vcore since you got the BSOD code 101 and your system is overclocked.

You should run Prime95 and test the stability of you OC. But watch out for the temperatures.

 

http://www.sevenforums.com/crash-lockup-debug-how/63501-stop-0x101-clock_watchdog_timeout-troubleshtg.html

 

Ntoskrnl.exe could also be corrupt.

Hey guys, I'm confused... my rig has worked perfectly under the most extreme of scenery and addon conditions, ever since I got it a year and a half ago. Why should the OC all of a sudden be an issue? Especially when it occurred with lightweight weather, with only a small grass strip and an addon that is fairly light on resources. I normally fly the NGX, with real weather, all the big addon airports, GEX/UTX, REX Ess, etc etc... with no problem at all.

 

EDIT: I was just starting a flight from YMLT to YMML using Orbx's AUS, half way through programming the FMC FSX simply shut down and disappeared... with the usual little error box appearing to tell me that Microsoft is looking for a solution, not that it ever does! Prior to the CTD, the textures were starting to load very slowly after changing the view... something else that I have never had a problem with before, except very little anyway...

Run some stress test using Prime95 or OCCT. Watch your temps. When was the last time you cleaned out the dust inside your case, fans and GPU? Something has changed. Maybe you just need a little maintenance and you don't have a component going bad.

Hey Joe, you beat me to it! I've just taken a look at the CPU cooler rad and it was covered in dust. I've just given it a vacuum so will do some tests and report back. Cheers fellas, fingers crossed.

Hey Joe, you beat me to it! I've just taken a look at the CPU cooler rad and it was covered in dust. I've just given it a vacuum so will do some tests and report back. Cheers fellas, fingers crossed.

 

This kind of maintenance is well worth doing on a regular basis, as well as your CPU cooler you will probably find your GPU cooler is just as clogged and any case cooling fans will possibly have a layer of dust on the fins. I'd advise caution when using a vacuum cleaner, and would suggest ensuring any fans / cards are disconnected from the motherboard before applying sufficient airflow to start the fans spinning. I have not experienced it myself but beleive it to be true that causing a fan to spin generates an electrical charge via the motor which if the fan is spinning in reverse can cause sufficient negative charge to take out motherboard components.

This kind of maintenance is well worth doing on a regular basis, as well as your CPU cooler you will probably find your GPU cooler is just as clogged and any case cooling fans will possibly have a layer of dust on the fins. I'd advise caution when using a vacuum cleaner, and would suggest ensuring any fans / cards are disconnected from the motherboard before applying sufficient airflow to start the fans spinning. I have not experienced it myself but beleive it to be true that causing a fan to spin generates an electrical charge via the motor which if the fan is spinning in reverse can cause sufficient negative charge to take out motherboard components.

 

Ooops, sounds like good advice. Anyway, everything seems to be back to normal. It never ceases to amaze me how easy it is to forget the obvious in FSX. Thanks for all the advice fellas...