[SOLVED] How can I fix SYSTEM_SERVICE_EXCEPTION BSODs caused by ntoskrnl.exe?

[DDingus]

Hello everyone,

I have recently been getting SYSTEM_SERVICE_EXCEPTION BSODs very frequently. When I checked BlueScreenView, it said it was caused by ntoskrnl.exe. Here is the full report:

https://imgur.com/a/qdNAv0r

View: https://imgur.com/a/qdNAv0r

Here are my system's specs:
Ryzen 2600 CPU
RX 580 GPU
16GB 2666MHz RAM
Crucial MX500 250GB SATA SSD
1 TB HDD


Things I have done so far:

• Updated all drivers
• Ran chkdsk /r
• Checked cables
• Virus scan
• Ran sfc /scannow
• Updated Windows
• Ran Dism /Online /Cleanup-Image /RestoreHealth
• Ran Repair-WindowsImage -Online -RestoreHealth

I would really appreciate any suggestions regarding how to fix this

 

[Colif]

can you go to c:/windows/minidump
copy contents from here to a new folder
upload the copies from new folder to a file sharing website and show link here.

dumps will show more than what BSV does.

ntsokrnl - Windows kernel. It might be what crashed but its not the problem. If ntoskrnl was broken, windows wouldn't work.

imgur must be doing maintenance, its really slow to even show your pictures

 

[DDingus]

Here is a link to a Google Drive folder containing the minidump files:
https://drive.google.com/drive/folders/1n8z_MyU0VkTOCpitul4gztIsV1nlQ2xR?usp=sharing

Also, Imgur seems to be fine on my end.

 

[Colif]

i will send link to this thread to a friend, he will convert dumps and we see what might be to blame. He in USA so won't reply for a few hours

 

[DDingus]

Alright, thanks for helping me out.

 

[DDingus]

I'm not sure if this will help, but I have just crashed and received a different error. I got the CRITICAL_PROCESS_DIED error. The recording process was stuck at 0%, so I stopped it and now I don't have the dump file for it.

 

[Colif]

what Build of win 10 are you on?
right click start
choose run,...
type winver and press enter
Current build is 18362.207

If you on that, I am starting to think its windows causing that BSOD. I have seen it too often this month, its normally not an error I see as often as I have. So starting to suspect a windows update is the cause.

critical process died covers a wide range of windows system files that if they crash, so does windows.

I was about to suggest SFC/scannow but you done it already so try this instead
right click start button
choose powershell (admin)
copy/paste this command into window:
Repair-WindowsImage -Online -RestoreHealth and press enter

this command fixes the image file, try running sfc /scannow after it and restart PC if it found anything to fix.

 

[DDingus]

The version of Windows I am using is 17134.860

I followed the steps you provided and got this after the sfc /scannow:
Windows Resource Protection did not find any integrity violations.

The results from the Repair-WindowsImage -Online -RestoreHealth command is:
Path :
Online : False
ImageHealthState : Healthy
RestartNeeded : False

 

[gardenman]

Hi, I'm not sure if you've solved the problem or not? It says the thread is answered but it doesn't look like it is. I ran the dump file through the debugger and got the following information: https://pste.eu/p/PQUU.html

File information:	070919-7187-01.dmp (Jul 9 2019 - 05:44:36)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process: Registry)
Uptime:	0 Day(s), 9 Hour(s), 07 Min(s), and 42 Sec(s)

Possible Motherboard page: https://www.asrock.com/mb/AMD/B450M Pro4/
There are BIOS updates available for your system. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

Someone marked thread as solved, I have changed it back to unfixed since its clearly not

corrupt registry?

try these fixes
go to settings/update & security/recovery
under advanced startup, click restart now
choose troubleshoot
choose advanced
choose start up repair - this will scan PC and maybe fix this - will ask for logon info

another is run chkdsk
search for command prompt
right click control panel result and choose run as admin
type chkdsk c: /f and press enter
2 paragraphs will pop up, agree to run it at startup
restart PC and let chkdsk run.

 

[DDingus]

Just tried start-up repair and chkdsk c: /f. Here are the results:
Start-up Repair
I got a blue screen saying "Start-up Repair couldn't repair your PC". It also showed a directory to a log file. (I can post it here if you want.)

chkdsk c: /f
Process was completed normally in about 30 seconds.

 

[DDingus]

I recently crashed again and obtained another minidump file. Interestingly, BlueScreenView tells me that it was caused by both ntoskrnl.exe and AtihdWT6.sys. I posted in on my Google Drive folder:
https://drive.google.com/drive/folders/1n8z_MyU0VkTOCpitul4gztIsV1nlQ2xR?usp=sharing

 

[Colif]

Apr 30 2019

AtihdWT6.sys

AMD High Definition Audio Function driver

Seems its part of the GPU drivers.

driver date wouldn't have made me suspect it though, normally bsod caused by older drivers, not relatively new ones.

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://pste.eu/p/QSlP.html

File information:	070919-6968-01.dmp (Jul 9 2019 - 09:13:06)
Bugcheck:	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Driver warnings:	*** WARNING: Unable to verify timestamp for AtihdWT6.sys
Probably caused by:	AtihdWT6.sys (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 49 Min(s), and 21 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[DDingus]

I ran the dump file through the debugger and got the following information: https://pste.eu/p/QSlP.html

File information:	070919-6968-01.dmp (Jul 9 2019 - 09:13:06)
Bugcheck:	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Driver warnings:	*** WARNING: Unable to verify timestamp for AtihdWT6.sys
Probably caused by:	AtihdWT6.sys (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 49 Min(s), and 21 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

Does anyone know what I can do about this?

 

[Colif]

Did you try updating GPU drivers as that is what is causing the BSOD

https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

 

[DDingus]

I believe the problem is gone since the crashing has stopped. Thanks for the help!