Bugcheck, Flightsim and BSOD's

[Domo]

Hi all,

I have been playing FS for the last 4 years and I have started to have totally random BSODS when I play it. It is sooooo annoying and i lose flights constantly.

I think this is what you want?

The computer has rebooted from a bugcheck. The bugcheck was: 0x100000c5 (0x012c0089, 0x00000002, 0x00000001, 0x805505a1)

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xf6002a1a, 0xb279d93c, 0x00000000)

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x00000103, 0x0000001c, 0x00000001, 0x804e1bf8)

Error code 1000000a, parameter1 00000103, parameter2 0000001c, parameter3 00000001, parameter4 804e1bf8.

Error code 1000008e, parameter1 c0000005, parameter2 f6002a1a, parameter3 b279d93c, parameter4 00000000.

Error code 1000000a, parameter1 00000103, parameter2 0000001c, parameter3 00000001, parameter4 804e1bf8.

I hope you can help this is driving me crazy,

Cheers Dom

 

[howard_hopkinso]

Hello and welcome to Techspot.

Go HERE and follow the instructions.

If that doesn`t help. Zip 5 or 6 of your latest minidumps together and attach them here.

Regards Howard :wave: :wave:

 

[Domo]

oK ILL TRY, ARE YOU ABLE TO GAIN ANY INFO FORM THOSE BUGCHECKS? soz caps thanks for quick reply

 

[howard_hopkinso]

0x000000C5: DRIVER_CORRUPTED_EXPOOL

An attempt occurred to touch invalid memory at a process IRQL that is too high. This is almost always caused by drivers that have corrupted the system pool. If you’ve recently installed any new software, check to see if it’s properly installed; and check for updated drivers on the manufacturer’s web site.

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Typically due to a bad driver, or faulty or incompatible hardware or software. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)

As you can see. Those bugchecks can be caused by a variety of things.

I may be able to tell you more, once I`ve seen your minidumps. these are a lot more detailed.

Regards Howard