BSOD ntoskrnl.exe

[Ryanmlt1 16]

I recently upgraded to P3D V4.5 after not being in the sim for sometime.  Now after about 15-20 min of flight time I get this BSOD.  I have ran driver booster and updated all my drivers. I also ran all the windows svc scans and chkdsk scans. I really am at the point of just doing a full Windows and P3D install.  Im running ORBX Scenery, TrackIR, EZdok. It happens with all different types of Aircraft always about 15 -20 min flight. Below is the Blue Screen View Report.  

 

Below are the last two crashes. Its ntsokrnl.exe causing this crash.  

==================================================
Dump File         : 112719-6609-01.dmp
Crash Time        : 11/27/2019 7:58:18 PM
Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code    : 0x00000050
Parameter 1       : ffffb00b`d985f46d
Parameter 2       : 00000000`00000002
Parameter 3       : fffff804`7c1f0ff5
Parameter 4       : 00000000`00000002
Caused By Driver  : hal.dll
Caused By Address : hal.dll+32cb
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+1c14e0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\WINDOWS\Minidump\112719-6609-01.dmp
Processors Count  : 12
Major Version     : 15
Minor Version     : 18362
Dump File Size    : 1,292,500
Dump File Time    : 11/27/2019 7:59:03 PM
==================================================

==================================================
Dump File         : 112319-10593-01.dmp
Crash Time        : 11/23/2019 4:27:28 PM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : 00000000`8824fe69
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000000
Parameter 4       : fffff801`6e87531e
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c14e0
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+1c14e0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\WINDOWS\Minidump\112319-10593-01.dmp
Processors Count  : 12
Major Version     : 15
Minor Version     : 18362
Dump File Size    : 749,364
Dump File Time    : 11/23/2019 4:28:14 PM
==================================================
AppCrashView

==================================================
Process File      : WerFault.exe
Event Name        : Shut down unexpectedly
Event Time        : 11/27/2019 7:59:05 PM
User Name         : All Users
Exception Code    : 
Exception Code Description: 
Exception Offset  : 
Fault Module Name : 
Fault Module Version: 
Process Path      : C:\Windows\System32\WerFault.exe
Report File Size  : 8,678
Report File Path  : C:\Users\All Users\Microsoft\Windows\WER\ReportArchive\Kernel_50_d96d979adaa1c698cefa4a86f955cf95b5d494_00000000_cab_aa09e6ab-009b-4ab2-8c74-08acf5827f54\Report.wer
==================================================

Edited November 28, 2019 by Ryanmlt1

[Jim Young 2,356]

6 minutes ago, Ryanmlt1 said:

Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : 00000000`8824fe69
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000000
Parameter 4       : fffff801`6e87531e
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c14e0

BSOD's are serious hardware issues and you must shutdown or fix the problem as soon as you can.  In this case the driver caused this BSOD.  If you do not fix the problem, shutdown your computer as you could do damage to hardware components.

I would first run the System File Checker - https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system

Update your drivers.  I use Driver Booster (freeware) - https://www.iobit.com/en/driver-booster.php

Scan your Windows Memory using Windows Diagnostic Tool.  Type Memory Diagnostic in the search bar on your desktop.  Look up in the Menu and click on Windows Memory Diagnostic.

If you overclocked your computer, go into the BIOS and save your configuration as Optimal Defaults.  Save and restart your computer.

What did you do recently?  Put in new memory?  Replace an SSD?  If you did anything with your computer hardware, suspect this as the issue.

 

[Ryanmlt1 16]

I did most of this already.  I did turn pre set overclock from extreme to fast and did a 40min flight with the Vertx DA62.  It didnt crash, but Im not holding my breath.   

Ryan

[Daytona125 225]

Having the same issue. BSOD often at very beginning of descent, any plane. I am starting ORBX might have something to do with it. Just did a clean install and still happening. FRUSTRATING to say the least. 

[Jim Young 2,356]

FSX/P3D cannot cause a BSOD as BSOD's are an indication you have a bad hardware driver or a piece of hardware is going bad.  BSOD's need to be fixed immediately as you could do further damage to your computer.  In the AVSIM CTD Guide, page 10, AVSIM provides information on the link to download a program called BlueScreenView.  The Guide provides valuable information to look for and provide to us so we can assist.