Solved BlueScreen IRQL_NOT_LESS_OR_EQUAL with Prepar3DV3

[h0155apd]

Dear All,

I fly with Prepar3D and a lot of hardware via an Wireless network in my home cockpit on 3 different computer and get all 2 days a blue screen (espacily if I fly to very busy airports) on the main computer.

My last dump was: IRQL_NOT_LESS_OR_EQUAL
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800032C156C)
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)

I will attach the dm log collector files here and hope that some one can help me with identifying the driver, who do that problem.

Many thanks in advance.


Best regards from Germany

Oliver

 

[axe0]

Please follow this tutorial and upload a zip with a .nfo file

 

[h0155apd]

hello, please find enclosed the needed file many thanks for looking in it best regards oliver

 

[axe0]

Unfortunately I still cannot open the .nfo due to corruption.

Diagnostics Test

 System File Check

Please try following:

• Open an admin command prompt
• Copy/paste "sfc /scannow" (without quotes) and press enter
• When it is finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Make a photo of the result and post it.

 

[h0155apd]

Hi,

both scan are performed without any failure:

"Der Windows-Ressourcenschutz hat keine Integritätsverletzungen gefunden."

Interessting information for your. I have switched from overclocking the processor to no overclocking, since them (2 days before) no BSOD.

But this cannot be the solution for the future.

Best regards

Oliver

 

[axe0]

OC is a common cause for BSODs, if you want to over clock again you need to adjust settings

 

[h0155apd]

many thanks, no problems after switch to not overclocked, best regards Oliver