Haunted by ntoskrnl.exe BSODs.

[tkurgpold]

Specs:
FX-6300 (No overclock or AMD Turbo Core, chipset drivers installed)
8GB DDR3
M5a97 LE R2.0
EVGA GTX 660 SIG2 SC (No overclock, drivers up to date)
500GB WD Green of unknown origin as a boot drive

I've reinstalled Windows 10 on multiple hard drives, once or twice a year, since 2016. Every time it's the same thing, Windows gets sluggish(like, to the point that I have to leave the room for a solid 3 minutes before I can use it normally. CCleaner, defrag, uninstalling programs, nothing works. My startup list is always kept to the essentials.), I start to get BSODs, and most of the time they're caused by ntoskrnl.exe. Which is a bit unnerving. I was originally under the impression that it was a drive issue, but after having it occur multiple times on 2-3 different drives, I'm not so sure. If that is the case, I have $100 that I can spend on getting a new boot drive(most likely solid state), if need be.

Minidumps below.

==================================================
Dump File : 072218-47453-01.dmp
Crash Time : 7/22/2018 11:14:16 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000006
Parameter 2 : fffff802`106f93d2
Parameter 3 : ffff858f`a5ad0440
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+198430
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+198430
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\072218-47453-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 17134
Dump File Size : 694,556
Dump File Time : 7/22/2018 11:22:14 AM
==================================================

==================================================
Dump File : 072218-46515-01.dmp
Crash Time : 7/22/2018 12:11:53 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000006
Parameter 2 : fffff801`5dcfb3d2
Parameter 3 : ffffb287`e7de8c10
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+198430
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+198430
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\072218-46515-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 17134
Dump File Size : 695,644
Dump File Time : 7/22/2018 9:17:40 AM
==================================================

 

[Colif]

If only we could delete ntoskrnl but well, Windows won't work without it. It stands for New Technology Operating System Kernel. It looks after memory management, power management & Driver interactions.

can you go to C:\Windows\Minidump
copy contents of folder to another folder
upload the minidumps from new folder to a file sharing web site amd show a link here. I will have someone convert dumps into a format I can read.

Do you have last BIOS for motherboard? Current version is 2701. New bios can help system stability
https://www.asus.com/us/Motherboards/M5A97_LE_R20/HelpDesk_Download/

Look in Device Manager to see if any devices are marked with the exclamation point

Try running memtest86 on your ram stick (If more than 1 stick, run it on 1 stick at a time), Up to 8 passes. Any error count above 0 is too many, remove/replace any memory sticks that have errors.

It might not be ram, I am just checking. It shouldn't be cause of slowing down at startup... that is more likely drivers or hard drive but you have used 3 drives.

 

[tkurgpold]

If only we could delete ntoskrnl but well, Windows won't work without it. It stands for New Technology Operating System Kernel. It looks after memory management, power management & Driver interactions.

can you go to C:\Windows\Minidump
copy contents of folder to another folder
upload the minidumps from new folder to a file sharing web site amd show a link here. I will have someone convert dumps into a format I can read.

Do you have last BIOS for motherboard? Current version is 2701. New bios can help system stability
https://www.asus.com/us/Motherboards/M5A97_LE_R20/HelpDesk_Download/

Look in Device Manager to see if any devices are marked with the exclamation point

Try running memtest86 on your ram stick (If more than 1 stick, run it on 1 stick at a time), Up to 8 passes. Any error count above 0 is too many, remove/replace any memory sticks that have errors.

It might not be ram, I am just checking. It shouldn't be cause of slowing down at startup... that is more likely drivers or hard drive but you have used 3 drives.

Here's the contents of the minidump folder: http://www.mediafire.com/file/58w8hxbgbeosope/Desktop.rar

Should probably also mention that this is approximately a 3 week old install of Windows.

As far as the BIOS is concerned, I bought the board in August of 2014, never updated the BIOS, and who knows how long it was on the shelf or in inventory. I debated updating the BIOS recently, but decided against it as I had read that it's something I should avoid unless the update explicitly states that it fixes a problem I'm having. So not sure on that one.

Nothing in Device Manager shows an exclamation point.

Conveniently enough, I ran Memtest for a full day recently as well(the longest I can feasibly run it), and at the end of the day still had no errors.

 

[Karadjgne]

Windows 10 has had issues with legacy drivers since the release of Creators Edition, that includes bios instructions.

What chipset drivers are loaded? If it's the ones that came with the board, those will most definitely need to be updated to latest released, and that includes all available from audio, USB family, Lan, Sata etc. Windows has generic drivers for most of that stuff, but generic isn't component specific and will affect performance and compatability.

 

[tkurgpold]

Windows 10 has had issues with legacy drivers since the release of Creators Edition, that includes bios instructions.

What chipset drivers are loaded? If it's the ones that came with the board, those will most definitely need to be updated to latest released, and that includes all available from audio, USB family, Lan, Sata etc. Windows has generic drivers for most of that stuff, but generic isn't component specific and will affect performance and compatability.

The chipset drivers are from AMD. Audio(normally I use an external interface), USB, LAN drivers were all installed from the ASUS product page upon installing windows.

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/JmMs.html

File: 072218-47656-01.dmp (Jul 22 2018 - 16:46:07)
BugCheck: [UNEXPECTED_STORE_EXCEPTION (154)]
Probably caused by: hardware_disk (Process: MemCompression)
Uptime: 0 Day(s), 2 Hour(s), 28 Min(s), and 54 Sec(s)

File: 072218-47453-01.dmp (Jul 22 2018 - 14:14:16)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: memory_corruption (Process: Registry)
Uptime: 0 Day(s), 2 Hour(s), 03 Min(s), and 03 Sec(s)

File: 072218-46515-01.dmp (Jul 22 2018 - 03:11:53)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: memory_corruption (Process: Registry)
Uptime: 0 Day(s), 14 Hour(s), 38 Min(s), and 00 Sec(s)

BIOS information was not included in the dump file. This can sometimes mean you are using an older version of BIOS. Consider looking for an update. Note: Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

I can't help you with this. Wait for additional replies. Good luck.

 

[Colif]

See bios update instructions on page 3-32 of your manual - http://dlcdnet.asus.com/pub/ASUS/mb/SocketAM3+/M5A97_LE_R2.0/E8047_M5A97_LE_R20_V2_WEB.pdf

Dl current BIOS from top link on this page - https://www.asus.com/us/Motherboards/M5A97_LE_R20/HelpDesk_Download/

If you have never done an upgrade, it may fix this error as drivers may be sending commands it doesn't know.

Scarlet Crush PS4 controller software can also cause errors in Win 10
Download latest LAN drivers from here - http://www.realtek.com.tw/Downloads/downloadsView.aspx?Conn=4&DownTypeID=3&Langid=1&Level=5&PFid=5&PNid=13

 

[tkurgpold]

See bios update instructions on page 3-32 of your manual - http://dlcdnet.asus.com/pub/ASUS/mb/SocketAM3+/M5A97_LE_R2.0/E8047_M5A97_LE_R20_V2_WEB.pdf

Dl current BIOS from top link on this page - https://www.asus.com/us/Motherboards/M5A97_LE_R20/HelpDesk_Download/

If you have never done an upgrade, it may fix this error as drivers may be sending commands it doesn't know.

Scarlet Crush PS4 controller software can also cause errors in Win 10
Download latest LAN drivers from here - http://www.realtek.com.tw/Downloads/downloadsView.aspx?Conn=4&DownTypeID=3&Langid=1&Level=5&PFid=5&PNid=13

Just finished updating the BIOS. Was running version 2301, dated January 2014. Ended up being much more painless than I had originally assumed. Also downloaded the LAN drivers, reinstalled it for good measure. Unsure how to go about removing the PS4 controller driver, as I don't actually have any PS4 controllers plugged into my computer. Hell, I don't even have a PS4.

 

[Colif]

it could be a PS3 controller driver, I am not sure which Scarlet Crush is for.

this should help - https://github.com/nefarius/ScpToolkit/wiki/Manual-driver-removal

 

[tkurgpold]

it could be a PS3 controller driver, I am not sure which Scarlet Crush is for.

this should help - https://github.com/nefarius/ScpToolkit/wiki/Manual-driver-removal

Ah. Yeah, I need the PS3 driver.

 

[Colif]

Are you still getting errors? If you are, upload the minidump files so we can keep trying to fix it

 

[tkurgpold]

Are you still getting errors? If you are, upload the minidump files so we can keep trying to fix it

Nothing yet. I'll probably try leaving GTA IV running for a while later, as that was one of the instances I got the blue screen.

 

[Colif]

BSOD don't wave a white flag and surrender, they just stop. I don't want to jinx us though so wait and see

 

[tkurgpold]

BSOD don't wave a white flag and surrender, they just stop. I don't want to jinx us though so wait and see

Not quite sure what you mean by that, since nobody was really implying that it would do anything besides either stop or continue. :/

Regardless, it's been a week and no blue screens to speak of. Going to go ahead and say that the BIOS update fixed it.

 

[Colif]

it was just a joke. not a very good one but oh well.

 

[tkurgpold]

Well, damn. After weeks of stability, I had another blue screen last night. Then another one earlier, WdFilter.sys and Ntoskrnl.exe. Then another one an hour ago. Ntoskrnl.exe. For some reason I don't seem to have the mini dump from last night, but it was REGISTRY_FILTER_DRIVER_EXCEPTION for WdFilter.sys.

After the last sod earlier, I tried to turn it back on, a disk check started, lasted for a few seconds, and then spontaneously rebooted. I also can't run Firefox for some reason.

Anyway, mini dumps: http://www.mediafire.com/file/58w8hxbgbeosope/Desktop.rar/file

 

[gardenman]

That's the same 3 dump files that I reviewed earlier.

072218-46515-01.dmp
072218-47453-01.dmp
072218-47656-01.dmp

 

[tkurgpold]

That's the same 3 dump files that I reviewed earlier.

072218-46515-01.dmp
072218-47453-01.dmp
072218-47656-01.dmp

For the love of- I edited the right link in 2 minutes after I posted that, what the hell..

http://www.mediafire.com/file/dt951s5z574ked4/Desktop%282%29.rar

 

[gardenman]

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

File: 081218-595937-01.dmp (Aug 12 2018 - 00:12:56)
BugCheck: [REGISTRY_FILTER_DRIVER_EXCEPTION (135)]
Probably caused by: memory_corruption (Process: Registry)
Uptime: 2 Day(s), 12 Hour(s), 12 Min(s), and 14 Sec(s)

File: 081218-760265-01.dmp (Aug 12 2018 - 14:03:28)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: memory_corruption (Process: Registry)
Uptime: 0 Day(s), 0 Hour(s), 30 Min(s), and 56 Sec(s)

2 new drivers that I haven't seen before:
paeusbaudio.sys
paeusbaudioks.sys

I can't help you with this. Wait for additional replies. Good luck.

 

[tkurgpold]

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

File: 081218-595937-01.dmp (Aug 12 2018 - 00:12:56)
BugCheck: [REGISTRY_FILTER_DRIVER_EXCEPTION (135)]
Probably caused by: memory_corruption (Process: Registry)
Uptime: 2 Day(s), 12 Hour(s), 12 Min(s), and 14 Sec(s)

File: 081218-760265-01.dmp (Aug 12 2018 - 14:03:28)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: memory_corruption (Process: Registry)
Uptime: 0 Day(s), 0 Hour(s), 30 Min(s), and 56 Sec(s)

2 new drivers that I haven't seen before:
paeusbaudio.sys
paeusbaudioks.sys

I can't help you with this. Wait for additional replies. Good luck.

paeusbaudio, after a bit of googling that appears to be related to my PreSonus audio interface. Doubt it's the problem, and if it is, well... crap.

 

[Colif]

try this
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

 

[tkurgpold]

try this
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

PS C:\Windows\system32> SFC /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

PS C:\Windows\system32> Repair-WindowsImage -Online -RestoreHealth


Path :
Online : False
ImageHealthState : Healthy
RestartNeeded : False

EDIT: Third one of the day now. KERNEL_INPAGE_ERORR.

 

[Colif]

well, windows 10 seems okay. that is what those results show.

One way to flush out a bad driver - I just don't like it was it can also cause boot loops. To counter that, search cortana for System restore and use the button in the pop up to create a system restore point (Its bottom button called Create)

Also, download the Windows 10 media creation tool and use it to make a win 10 installer on USB - this is a handy boot drive and we can use it to break the boot loop and run system restore. Hopefully its not needed but its a precaution

try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, upload the minidump file and we see what it shows us.

The instructions to stop it looping are listed below
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose system restore
pick the restore point you created before starting driver verifer and PC should reload those settings and boot normally.

 

[tkurgpold]

well, windows 10 seems okay. that is what those results show.

One way to flush out a bad driver - I just don't like it was it can also cause boot loops. To counter that, search cortana for System restore and use the button in the pop up to create a system restore point (Its bottom button called Create)

Also, download the Windows 10 media creation tool and use it to make a win 10 installer on USB - this is a handy boot drive and we can use it to break the boot loop and run system restore. Hopefully its not needed but its a precaution

try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, upload the minidump file and we see what it shows us.

The instructions to stop it looping are listed below
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose system restore
pick the restore point you created before starting driver verifer and PC should reload those settings and boot normally.

Came up with a blue screen with Driver Verifier Found Problem type of thing, before login screen.

http://www.mediafire.com/file/mdgi92d2caha6eq/082418-867640-01.dmp/file

 

[gardenman]

Came up with a blue screen with Driver Verifier Found Problem type of thing, before login screen.

http://www.mediafire.com/file/mdgi92d2caha6eq/082418-867640-01.dmp/file

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

File: 082418-867640-01.dmp (Aug 24 2018 - 14:07:10)
BugCheck: [CRITICAL_PROCESS_DIED (EF)]
Probably caused by: ntkrnlmp.exe (Process: csrss.exe)
Uptime: 0 Day(s), 0 Hour(s), 08 Min(s), and 19 Sec(s)

Usually errors that are caused by Driver Verifier have the word "VERIFIER" in them. For example: DRIVER_VERIFIER_DETECTED_VIOLATION ... This one doesn't. Are you sure it's the right time/date? It looks like this one happened around 2:07pm.

I can't help you with this. Wait for additional replies. Good luck.