Sign in to follow this  
Angelo Cosma

P3D 3.2 BSOD Win 10 64 report included

Recommended Posts

I had a BSOD in the middle of descent on a 45 minute flight, I wasn't tabbing in and out of the sim or anything at all. Just watching the aircraft descend and BAM. BSOD. 

 

Specs in Sig, PMDG Ngx, ASN, UT2, REX (textures only), FSDT and Flightbeam, EzDok. 

 

Note this is not a regular crash, I have seen the IRQL before but its random and only about 2 times or so a month, maybe 3 if I am on the sim a lot.

 

Here is the report:

 

Version=1
EventType=BlueScreen
EventTime=131040422342433393
ReportType=4
Consent=1
ReportIdentifier=1daba90d-f885-11e5-9d08-001ee5efae6e
IntegratorReportIdentifier=e64700b6-8884-4b04-9a24-7c178d1a1a30
NsAppName=BlueScreen
Response.type=4
Sig[0].Name=Code
Sig[0].Value=a
Sig[1].Name=Parameter 1
Sig[1].Value=289
Sig[2].Name=Parameter 2
Sig[2].Value=ff
Sig[3].Name=Parameter 3
Sig[3].Value=41
Sig[4].Name=Parameter 4
Sig[4].Value=fffff802d74f5459
Sig[5].Name=OS version
Sig[5].Value=10_0_10586
Sig[6].Name=Service Pack
Sig[6].Value=0_0
Sig[7].Name=Product
Sig[7].Value=768_1
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.10586.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
File[0].CabName=040116-6843-01.dmp
File[0].Path=040116-6843-01.dmp
File[0].Flags=589826
File[0].Type=2
File[0].Original.Path=C:\Windows\Minidump\040116-6843-01.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-8359-0.sysdata.xml
File[1].Flags=589826
File[1].Type=5
File[1].Original.Path=C:\Windows\Temp\WER-8359-0.sysdata.xml
File[2].CabName=Report.cab
File[2].Path=Report.cab
File[2].Flags=196608
File[2].Type=11
File[2].Original.Path=Report.cab
Ns[0].Name=stopcode
Ns[0].Value=0000000A
Ns[1].Name=p1
Ns[1].Value=289
Ns[2].Name=p2
Ns[2].Value=FF
Ns[3].Name=p3
Ns[3].Value=41
Ns[4].Name=p4
Ns[4].Value=D74F5459
FriendlyEventName=Shut down unexpectedly
ConsentKey=BlueScreen
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=00000000000000000000000000000000
 
 
 
This is what was in the "Critical" area:
 
Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          4/1/2016 8:43:47 PM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (70368744177664),(2)
User:          SYSTEM
Computer:      Angelo
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
  <System>
    <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
    <EventID>41</EventID>
    <Version>3</Version>
    <Level>1</Level>
    <Task>63</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000400000000002</Keywords>
    <TimeCreated SystemTime="2016-04-02T03:43:47.400252800Z" />
    <EventRecordID>16228</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>Angelo</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="BugcheckCode">10</Data>
    <Data Name="BugcheckParameter1">0x289</Data>
    <Data Name="BugcheckParameter2">0xff</Data>
    <Data Name="BugcheckParameter3">0x41</Data>
    <Data Name="BugcheckParameter4">0xfffff802d74f5459</Data>
    <Data Name="SleepInProgress">0</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
    <Data Name="BootAppStatus">0</Data>
  </EventData>
</Event>
 
 
Ma8xu38.jpg

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Ran the driver update program, found 11 things that needed updating took care of that. Was flying KSFO KLAX 777 and just got a BSOD, here is the Event viewer:

 

Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
 
Problem signature:
P1: 139
P2: 3
P3: fffff801d200ab30
P4: fffff801d200aa88
P5: 0
P6: 10_0_10586
P7: 0_0
P8: 768_1
P9: 
P10: 
 
Attached files:
C:\Windows\Minidump\040216-6671-01.dmp
C:\Windows\Temp\WER-8203-0.sysdata.xml
 
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_2a4de59f92aa5ba902c37cc845532e4b25a6f_00000000_cab_0ec08414
 
Analysis symbol: 
Rechecking for solution: 0
Report Id: 2da06bce-a0f4-4bf5-a321-9e1f7026023e
Report Status: 2048
Hashed bucket: 
 
It said something about IRQL Security or something, I missed it before I could commit it to memory.
 
oeh3mWC.jpg

Share this post


Link to post
Share on other sites

Did you scan your system for corrupted drivers as this is a driver issue?

 

Use the System File Checker to look for corrupt/missing files (AKA - SFC \scannow) - If you are unfamiliar with the procedures to scan your system, please go to the following link for procedures depending on your Windows version - https://support.microsoft.com/en-us/kb/929833.  Basically, you will use the Windows Search and search for ‘Run’, look up in the menu and open up your ‘Run’ command in elevated mode (right click and open with Administrator Rights).  You then enter sfc \scannow and the press the enter key.  This program will then scan your system for corrupted or missing files and replace them if any are found.

 

Since you ran a driver updater and you updated your drivers (11 of them), it must be a corrupted system file.

 

Bugcheck code 0139 indicates kernel security check failure.  Several individuals at Nvidia indicated they were getting this error suddenly and they resolved it by going back to an earlier driver.  Also make sure your video card is properly seated and all connections are snug.

 

Best regards,

Share this post


Link to post
Share on other sites

Sfc Scan did not find any integrity violations, my Nvidia drivers are from 3/7/2016 version 10.18.13.6451 I have not got the latest ones yet. Are you advising I roll back to an older driver? Do both BSOD's indicate the same fault?

Share this post


Link to post
Share on other sites

I'm just saying that this error was fixed when several individuals went back to a previous version of their display drivers.  Your drivers are older than the latest.  The latest WHQL drivers are 364.72.

 

EDIT:  Wanted to add that a BSOD is pretty serious.  It means a hardware issue (failing, not properly seated, bad drivers causing it to fail).  You want to fix this as soon as possible as you could do serious damage to your computer.

 

Best regards,

Share this post


Link to post
Share on other sites

Right, I understand the severity, but my graphics card is properly seated, PSU is more than enough for the job, power connections secure, BIOS updated the latest. I am not sure what else I could check or do. Maybe try the latest nvidia drivers then? Its all I can really think of. 

Share this post


Link to post
Share on other sites

I guess I will have to try different drivers and see. I checked all my connections and they are fine. Are both BSODs related to the same issue or area? It doesn't have anything to do with my overclock does it? I can add a little more volts if need be, but CPU stress tests are fine and nothing fails. 

Share this post


Link to post
Share on other sites

An overclock or too high/low cpu voltage would have been most likely a bugcheck code of 0124.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this