Flic1

Random BSOD crashes continue

11 posts in this topic

Hi guys - I posted about this issue a month back or so.  I continue to have random BSOD's  I have had them happen in P3Dv4, XP11 and also randomly while computer is idle.  Good news is that it is not sim specific!  I have not been able to pinpoint the cause.  I had added 2 new memory sticks before this all started so I removed them thinking that may be the cause but BSOD's still continue.  I also checked all of my drivers with Driver Booster and I did have some that needed updating but again...still getting BSOD's.  They are very random and I can go a week or 2 without one.  I flew about 10 hours in P3Dv4 without problems but I just had another this morning while in P3D.  I checked 'Blue Screen View' and it says caused by driver 'win32kfullsys+49b4b' and the Bug Check String said 'system_service_exception'  Other times it says it is caused by driver 'dxgkrnl.sys+197d28'.  Others have been reported as well, it is never consistent.  I also ran a memory test and no issues were reported. I think this also started after Windows Creator update but cannot be 100% sure. Thanks again for help or ideas!! I pasted my AppCrashView below. 

Version=1
EventType=BlueScreen
EventTime=131470196411993402
ReportType=4
Consent=1
UploadTime=131470196712494853
ReportStatus=268435456
ReportIdentifier=6227ccdb-bf87-4e0f-a2c5-ae346eb27079
IntegratorReportIdentifier=df9171a6-ee67-4ac8-91a2-13564a957508
Wow64Host=34404
NsAppName=BlueScreen
AppSessionGuid=00000000-0000-0000-0000-000000000000
BootId=60
Response.BucketId=0x3B_win32kfull!TimersProc
Response.type=4
Response.CabId=697dac11-0ec5-4bf3-b0f4-af7d6ed81d49
Sig[0].Name=Code
Sig[0].Value=3b
Sig[1].Name=Parameter 1
Sig[1].Value=c0000005
Sig[2].Name=Parameter 2
Sig[2].Value=ffffe1cd27849b4b
Sig[3].Name=Parameter 3
Sig[3].Value=ffff918193b98ca0
Sig[4].Name=Parameter 4
Sig[4].Value=0
Sig[5].Name=OS version
Sig[5].Value=10_0_15063
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.15063.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
State[0].Key=Transport.DoneStage1
State[0].Value=1
File[0].CabName=081217-7046-01.dmp
File[0].Path=081217-7046-01.dmp
File[0].Flags=589826
File[0].Type=2
File[0].Original.Path=\\?\C:\WINDOWS\Minidump\081217-7046-01.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-9187-0.sysdata.xml
File[1].Flags=589826
File[1].Type=5
File[1].Original.Path=\\?\C:\Windows\Temp\WER-9187-0.sysdata.xml
File[2].CabName=WERInternalMetadata.xml
File[2].Path=WER2A9A.tmp.WERInternalMetadata.xml
File[2].Flags=851970
File[2].Type=5
File[2].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A9A.tmp.WERInternalMetadata.xml
File[3].CabName=memory.csv
File[3].Path=WER9FCA.tmp.csv
File[3].Flags=589826
File[3].Type=5
File[3].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9FCA.tmp.csv
File[4].CabName=sysinfo.txt
File[4].Path=WER9FDA.tmp.txt
File[4].Flags=589826
File[4].Type=5
File[4].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9FDA.tmp.txt
File[5].CabName=Report.zip
File[5].Path=Report.zip
File[5].Flags=196608
File[5].Type=11
File[5].Original.Path=\\?\C:\WINDOWS\system32\Report.zip
Ns[0].Name=stopcode
Ns[0].Value=0000003B
Ns[1].Name=p1
Ns[1].Value=00000000C0000005
Ns[2].Name=p2
Ns[2].Value=FFFFE1CD27849B4B
Ns[3].Name=p3
Ns[3].Value=FFFF918193B98CA0
Ns[4].Name=p4
Ns[4].Value=0000000000000000
FriendlyEventName=Shut down unexpectedly
ConsentKey=BlueScreen
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=00000000000000000000000000000000
MetadataHash=930498627

 

0

Share this post


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

This BSOD means that an exception happened while executing a routine that transitions from non-privileged code to privileged code. BSOD error code 0x0000003B may also show "SYSTEM_SERVICE_EXCEPTION" on the same blue screen.  See https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x3b--system-service-exception

On page 8 of the AVSIM CTD Guide (BSOD's), if you downloaded the BSOD Report program as suggested, it will provide more information.  For each BSOD, you will see the drivers or more information about the hardware that caused the crash.  Very important information for individuals trying to debug.

Best regards,

Jim

0

Share this post


Link to post
Share on other sites
33 minutes ago, Jim Young said:

On page 8 of the AVSIM CTD Guide (BSOD's), if you downloaded the BSOD Report program as suggested, it will provide more information.  For each BSOD, you will see the drivers or more information about the hardware that caused the crash.  Very important information for individuals trying to debug.

Hi Jim - Thanks for the response.  This has been a frustrating problem!  I have run Blue Screen Viewer and here are the 2 entries that are in pink at the top...not sure this helps??

 

ntoskrnl.exe    ntoskrnl.exe+1778a9    fffff801`8a693000    fffff801`8af1c000    0x00889000    0x597fd80d    7/31/2017    9:23:25 PM      
win32kfull.sys    win32kfull.sys+49b4b    ffffe1cd`27800000    ffffe1cd`27b93000    0x00393000    0x02354c46     Microsoft® Windows® Operating System    Full/Desktop Win32k Kernel Driver    10.0.15063.540 (WinBuild.160101.0800)    Microsoft Corporation    C:\WINDOWS\system32\win32kfull.sys 

0

Share this post


Link to post
Share on other sites

Did you update your drivers using a program such as Driver Booster (the one I use) (see page 15, AVSIM CTD Guide)?  USB ports need to be updated, SATA controllers, sys bus, etc., as they fix bugs found that affect Windows 10 users.  Windows Update does not do this for all hardware and you have to go out and find the fixes yourself.  This error indicates it is a driver that is not working properly and corrupted the memory space throwing the BSOD.

Best regards,

Jim

0

Share this post


Link to post
Share on other sites
11 minutes ago, Jim Young said:

Did you update your drivers using a program such as Driver Booster (the one I use) (see page 15, AVSIM CTD Guide)?  USB ports need to be updated, SATA controllers, sys bus, etc., as they fix bugs found that affect Windows 10 users.  Windows Update does not do this for all hardware and you have to go out and find the fixes yourself.  This error indicates it is a driver that is not working properly and corrupted the memory space throwing the BSOD.

Best regards,

Jim

Hi Jim - Yes, I did use your recommendation of Driver Booster several weeks ago and I had about a dozen drivers that were out of date.  Those were all updated with no luck...:huh:

0

Share this post


Link to post
Share on other sites

Run System File Checker (page 14, AVSIM CTD Guide).  Although you have updated all of your drivers, the crash indicates a corrupted driver.  System File Checker will look for corrupted or missing files and fix them.

If that checks out okay, then I would run the Windows Repair utility (freeware) as described on page 24 of the CTD Guide (has a link to the repair tool).

The 'dxgkrnl.sys' is usually related to video card drivers.  I know you have updated the drivers but you might want to reinstall.  Go to C:\Nvidia\Display Drivers and right click the .exe program for the latest drivers and select install as admin.

Best regards,

Jim

0

Share this post


Link to post
Share on other sites
10 hours ago, Jim Young said:

Run System File Checker (page 14, AVSIM CTD Guide).  Although you have updated all of your drivers, the crash indicates a corrupted driver.  System File Checker will look for corrupted or missing files and fix them.

If that checks out okay, then I would run the Windows Repair utility (freeware) as described on page 24 of the CTD Guide (has a link to the repair tool).

The 'dxgkrnl.sys' is usually related to video card drivers.  I know you have updated the drivers but you might want to reinstall.  Go to C:\Nvidia\Display Drivers and right click the .exe program for the latest drivers and select install as admin.

Best regards,

Jim

Hi Jim - I ran the Driver Booster again and there were 2 drivers that I guess did not update last time. A USB driver and an Intel driver and I was able to update both of them. The System File Checker was clean.  I ran the Windows Repair Utility...I believe successfully?  It didn't really say what it fixed but seemed to run ok and restarted the system. I also did an uninstall and reinstall of my Nvidia driver.

That being done, I completed one 2.5 hour flight without issue. I did another flight immediately after which was another 2.5 hours and on very short final got the BSOD:angry:  This one showed it was caused by the 'ntoskrnl.exe' driver and caused by address ntoskrnl.exe+16c560 in BlueScreenView.  I have seen this one before...like I mentioned, the error tends to be different each time but some of the same ones keep popping up. 

 

0

Share this post


Link to post
Share on other sites

Was it the same bugcheck code - 0x3b?

Can you move whatever is plugged into your USB port to another USB port?

The fact it is crashing after 2.5 hours is significant.  What is the power for your power supply unit? 

The fact it is crashing near the end of the flight and not at the beginning of the flight is significant too.  The airport you are trying to land at.  Is it fully compatible with P3Dv4?  The airport is being called at the end of the flight and may be causing corruption in the memory.  The next time you try the flight, if it is an add-on, disable it.  Of course, all of your add-on airports have add-on.xml's created.  Right?  You don't have them just in your scenery.cfg.  Right?  Because the scenery.cfg is specially coded in V4 and, if you opened it up using SceneryConfigEditor, it will get corrupted and P3D will simply not load corrupted things.  This type of crash is remote as you got a BSOD and BSOD indicates you have a problem with your hardware (a driver, a port, HDD, SSD, Mouse, Throttle, etc.).  Still the ntoskrnl is responsible for various system services such as hardware virtualization, process and memory management, thus making it a fundamental part of the system. It contains the cache manager, the executive, the kernel, the security reference monitor, the memory manager, and the scheduler.  When it comes to memory management, if something is corrupted in the memory (like a corrupted file) it could cause the BSOD.

If you are overclocked, reset your overclock to the optimal defaults.

Best regards,

Jim

0

Share this post


Link to post
Share on other sites
25 minutes ago, Jim Young said:

Was it the same bugcheck code - 0x3b?

Can you move whatever is plugged into your USB port to another USB port?

The fact it is crashing after 2.5 hours is significant.  What is the power for your power supply unit? 

The fact it is crashing near the end of the flight and not at the beginning of the flight is significant too.  The airport you are trying to land at.  Is it fully compatible with P3Dv4?  The airport is being called at the end of the flight and may be causing corruption in the memory.  The next time you try the flight, if it is an add-on, disable it.  Of course, all of your add-on airports have add-on.xml's created.  Right?  You don't have them just in your scenery.cfg.  Right?  Because the scenery.cfg is specially coded in V4 and, if you opened it up using SceneryConfigEditor, it will get corrupted and P3D will simply not load corrupted things.  This type of crash is remote as you got a BSOD and BSOD indicates you have a problem with your hardware (a driver, a port, HDD, SSD, Mouse, Throttle, etc.).  Still the ntoskrnl is responsible for various system services such as hardware virtualization, process and memory management, thus making it a fundamental part of the system. It contains the cache manager, the executive, the kernel, the security reference monitor, the memory manager, and the scheduler.  When it comes to memory management, if something is corrupted in the memory (like a corrupted file) it could cause the BSOD.

If you are overclocked, reset your overclock to the optimal defaults.

Best regards,

Jim

Good morning Jim - The bug check code on this one was 0x00000139.  I have nearly all of the USB ports full...I have 5 in the back and 4 in the front.  I am using 7 of 9 ports and a 750w power supply.  All of my addons are V4 compliant and in fact this latest BSOD was on approach to a default airport. Like I had mentioned, I have had this happen in XP11 as well (I have not flown XP11 very much since P3Dv4 though) so I agree it seems more hardware or driver related than sim. These do seem hard to diagnose, too bad there isn't a more clear-cut way of identifying these crashes in Windows. I am overclocked....I may have to contact Jetline and see if they can help with any of this as I have never messed with overclocking myself. I did just swap out my 2 original sticks of 16gb RAM with 2 newer identical sticks just for kicks as I have seen some reports of bad RAM causing this. Will try a few more flights:huh:  Appreciate all your help and insight!! 

 

Eric

0

Share this post


Link to post
Share on other sites

A BSOD means there is something serious with your hardware and your computer shuts down to protect your computer system until the problem is fixed.  If a piece of hardware is not properly seated in the MB or a SATA drive not connected properly to a SATA controller, it could throw the BSOD.  It is not P3D or XP11 that is causing your BSOD other than there is a small possibility of memory corruption. 

An overclock, even if done by a computer expert, can cause a BSOD.  When the computer starts up you will see a logo and you should hit the Del key several times until the BIOS opens up.  After it opens, look for resetting the BIOS to optimal defaults or the default, save, and restart the computer.  The optimal default for your CPU should be 4.2GHz.  That should work until you can get ahold of Jetline.

I do not recall seeing whether you ran the Windows Memory Diagnostics.  Just click on the search bar in the lower left corner and type in memtest and then look up in the menu and click on Windows Memory Diagnostic.

Best regards,

Jim

 

0

Share this post


Link to post
Share on other sites
10 hours ago, Jim Young said:

I do not recall seeing whether you ran the Windows Memory Diagnostics.  Just click on the search bar in the lower left corner and type in memtest and then look up in the menu and click on Windows Memory Diagnostic.

Yup, I did run this with no problems being found.  I will continue troubleshooting and will certainly give an update here if and when I find the solution!!  Thanks!

0

Share this post


Link to post
Share on other sites