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]

Did you ever do this? I know I suggested but you were stuck in a boot loop at the time

Try running chkdsk C: /f /r in command prompt (admin) - it will check system files and move files around if there are bad sectors
2 paragraphs will pop up after you type that, one asks if you want to run at start up, click Y and press enter. Restart PC and let it run scan.

your PC doing strange things and I would love to know why

Did you run Data Lifeguard for windows and check drive out - https://support.wdc.com/downloads.aspx?p=3 (its made by western Digital)?

 

[tkurgpold]

Did you ever do this? I know I suggested but you were stuck in a boot loop at the time

Try running chkdsk C: /f /r in command prompt (admin) - it will check system files and move files around if there are bad sectors
2 paragraphs will pop up after you type that, one asks if you want to run at start up, click Y and press enter. Restart PC and let it run scan.

your PC doing strange things and I would love to know why

Did you run Data Lifeguard for windows and check drive out - https://support.wdc.com/downloads.aspx?p=3 (its made by western Digital)?

Tried running both the quick and full scans on the WD utility, both passed.
Tried running chkdsk C: /f /r in an elevated command prompt, got stuck at 17%, rebooted while I was out of the room, came back on startup at 100%, then booted normally.
Tried running driver verifier several more times over the course of two days:

The driver for my M-Audio Delta 1010 threw a blue screen.
Then NIWinCDEmu.sys(something relating to Native Instruments' service center type software, which may make it awkward when I purchase some software from them in the coming weeks).
Then a driver from Voice Meeter.
Then the driver for SCP, which is what I use to connect my PS3 controller.

After that, all was well, driver verifier seemed to come up clean, I was able to run Car Mechanic Sim 2018, which has become my yardstick for testing things, as it always seemed to trigger the blue screen pretty quick. Later, played it again, 20 minutes or so in and it blue screened. Tried again this morning, no problem. Tried again later on, 20 minutes or so in it blue screened. Tried it again an hour or so ago, not even 20 minutes.

It's still giving me ntoskrnl.exe in BlueScreenView, but half the time ntfs.sys will be in there as well. I do have my pagefile set to 8193mb, and on my C drive in order to get minidumps to generate.

Currently have driver verifier running, and have for a while now, everything seems to be fine. Very confused at this point.

All four dumps I've gotten since then, for reference: http://www.mediafire.com/file/ls589f9a49g44gw/dump.zip/file

 

[gardenman]

All four dumps I've gotten since then, for reference: http://www.mediafire.com/file/ls589f9a49g44gw/dump.zip/file

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

Spoiler

File: 092118-38796-01.dmp (Sep 21 2018 - 21:50:40)
BugCheck: [UNEXPECTED_STORE_EXCEPTION (154)]
Probably caused by: hardware_disk (Process: MemCompression)
Uptime: 0 Day(s), 4 Hour(s), 23 Min(s), and 18 Sec(s)

File: 092118-34546-01.dmp (Sep 21 2018 - 17:25:50)
BugCheck: [UNEXPECTED_STORE_EXCEPTION (154)]
Probably caused by: hardware_disk (Process: MemCompression)
Uptime: 0 Day(s), 4 Hour(s), 09 Min(s), and 17 Sec(s)

File: 092018-62312-01.dmp (Sep 20 2018 - 14:42:50)
BugCheck: [CRITICAL_PROCESS_DIED (EF)]
Probably caused by: ntkrnlmp.exe (Process: services.exe)
Uptime: 0 Day(s), 0 Hour(s), 02 Min(s), and 58 Sec(s)

File: 092018-42140-01.dmp (Sep 20 2018 - 23:32:50)
BugCheck: [UNEXPECTED_STORE_EXCEPTION (154)]
Probably caused by: hardware_disk (Process: MemCompression)
Uptime: 0 Day(s), 7 Hour(s), 53 Min(s), and 11 Sec(s)

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

 

[Colif]

Did you ever get an answer on Tenforums? I have removed the best answer as clearly I haven't worked this out yet.

what USB devices are attached? tried playing without Presonus attached?

its not memory, its not hdd, Scarlet Crush isn't even showing as running.

unusual suggestion: Try turning off Fast startup - link - it is mentioned as one possible cause of BSOD.

I wish there were more people here who could answer these things, I will send a PM to someone who might get to bottom of this for you, though he hasn't posted here for 2 weeks so I can't guarantee he will answer

in case he answers, can you do this

Please do the following to provide additional information
- Go to https://www.sysnative.com/blogs/download/sysnativebsodcollectionapp-exe/ and download the SysnativeBSODCollectionApp.exe
- Run the tool and give it approx. 10-20 minutes to finish, on some machines it may take some time
- When the tool is finished, it will have created a zip file on your desktop and open the desktop folder and a file called BSODPostingInstructions.txt. Upload the zip file ton onedrive, google drive or dropbox and post a share link.

 

[axe0axe0]

Hi tkurgpold,

Please follow the instructions Colif provided in his last post to provide logs needed for troubleshooting.

Please note, since the end of august I am back in school and so my replies may be delayed by a few days. I do understand that BSOD crashes can be a very annoying and frustrating problem, I've been through the same many, many times, but I have priorities.

 

[tkurgpold]

Did you ever get an answer on Tenforums? I have removed the best answer as clearly I haven't worked this out yet.

what USB devices are attached? tried playing without Presonus attached?

its not memory, its not hdd, Scarlet Crush isn't even showing as running.

unusual suggestion: Try turning off Fast startup - link - it is mentioned as one possible cause of BSOD.

I wish there were more people here who could answer these things, I will send a PM to someone who might get to bottom of this for you, though he hasn't posted here for 2 weeks so I can't guarantee he will answer

in case he answers, can you do this

Please do the following to provide additional information
- Go to https://www.sysnative.com/blogs/download/sysnativebsodcollectionapp-exe/ and download the SysnativeBSODCollectionApp.exe
- Run the tool and give it approx. 10-20 minutes to finish, on some machines it may take some time
- When the tool is finished, it will have created a zip file on your desktop and open the desktop folder and a file called BSODPostingInstructions.txt. Upload the zip file ton onedrive, google drive or dropbox and post a share link.

Unfortunately not, been about 4 days since posting.

USB devices attached would be keyboard and mouse, external hard drive, MIDI keyboard, and dj controller.

Relieved that it's not memory or hdd. Fast startup I already turned off sometime last month. I'll try running without the presonus and edit with the results.

Ran the collection tool:
http://www.mediafire.com/file/7ozj6lwt96ihu42/SysnativeFileCollectionApp.zip/file

 

[axe0axe0]

Hi tkurgpold,

I've had a quick look through the eventlogs and the dumps. It is pretty worrying.
Many of the dumps, if not all, specify that an attempt was made to perform an I/O operation on a device which didn't exist.
The eventlogs show similar things, retried I/O operations, bad blocks, paging errors, controller errors, corrupted file system structure, crash dump initialization failure, dump creating failure, etc.

I understand you've replaced the Windows drive a few times, but what about the other drives that are connected? The eventlog doesn't show the Windows drive only as a problem, but pretty much any drive that could possibly have been connected the past few months.
I would recommend to disconnect any device that you don't need, they quite often make I/O operations and as that will probably go wrong it might give confusion and get us off of the main picture.

My current suspicion is that your motherboard, or the cables, are causing your problems. If I exclude the second drive and consider everything that has been done up to this point, I'd say I'm almost certain the motherboard is the cause.


Due to the circumstances, it is better if any driver issues that were/are being addressed are temporary ignored as they are very likely affected by the drive related errors. I mean, you can address them, but they'll very likely keep returning.

 

[tkurgpold]

Hi tkurgpold,

I've had a quick look through the eventlogs and the dumps. It is pretty worrying.
Many of the dumps, if not all, specify that an attempt was made to perform an I/O operation on a device which didn't exist.
The eventlogs show similar things, retried I/O operations, bad blocks, paging errors, controller errors, corrupted file system structure, crash dump initialization failure, dump creating failure, etc.

I understand you've replaced the Windows drive a few times, but what about the other drives that are connected? The eventlog doesn't show the Windows drive only as a problem, but pretty much any drive that could possibly have been connected the past few months.
I would recommend to disconnect any device that you don't need, they quite often make I/O operations and as that will probably go wrong it might give confusion and get us off of the main picture.

My current suspicion is that your motherboard, or the cables, are causing your problems. If I exclude the second drive and consider everything that has been done up to this point, I'd say I'm almost certain the motherboard is the cause.


Due to the circumstances, it is better if any driver issues that were/are being addressed are temporary ignored as they are very likely affected by the drive related errors. I mean, you can address them, but they'll very likely keep returning.

I end up swapping drives around from time to time. Right now I've only got my Windows drive, and a 1TB one with some games on it for testing. (Which I've also run the same scan on as my Windows drive, which came up clear)


In the past few months I've had my 3TB data drive, which was part of a storage space until the second 3TB drive I purchased to use with it died after a few days. I've been keeping the data drive safely tucked away in an anti static bag until I can replace the second drive with something a bit more robust. Apart from that, I also have a 2TB external drive connected, and previously had a borrowed 1TB external drive connected which I used to back up important data off my previous boot drive using a Linux dualboot.

I've currently got everything disconnected apart from mouse/keyboard, audio, the two drives and my DVD drive.

 

[axe0axe0]

Could you try connecting the hard drive cables to a different SATA port.

 

[tkurgpold]

Could you try connecting the hard drive cables to a different SATA port.

Swapped SATA ports twice, and used different cables for both the drives. Second round tried connecting them in the same order as the boot order set in my BIOS(so optical drive>C drive>1tb drive). Blue screen both times, first try CRITICAL_PROCESS_DIED, then another store exception.

 

[axe0axe0]

At this point I suggest to replace the motherboard.

 

[tkurgpold]

Damnit..

 

[Colif]

I am going to have to look at that info in that zip at some stage. I need to figure out all the causes of that error, everytime I think i know what it is, it turns out I am wrong. I appreciate Axe looking at this post as it had dragged on too long.

Motherboards are hardest thing to identify as cause of problems, its generally why we test everything else until there is no alternative. Only way to be certain in most cases is to swap in a known working version, and only people with spare motherboards lying around are repair stores.

 

[tkurgpold]

I am going to have to look at that info in that zip at some stage. I need to figure out all the causes of that error, everytime I think i know what it is, it turns out I am wrong. I appreciate Axe looking at this post as it had dragged on too long.

Motherboards are hardest thing to identify as cause of problems, its generally why we test everything else until there is no alternative. Only way to be certain in most cases is to swap in a known working version, and only people with spare motherboards lying around are repair stores.

Really appreciate the help through all this. Not sure if I mentioned that.

 

[axe0axe0]

I am going to have to look at that info in that zip at some stage. I need to figure out all the causes of that error, everytime I think i know what it is, it turns out I am wrong. I appreciate Axe looking at this post as it had dragged on too long.

Motherboards are hardest thing to identify as cause of problems, its generally why we test everything else until there is no alternative. Only way to be certain in most cases is to swap in a known working version, and only people with spare motherboards lying around are repair stores.

You might not be necessarily wrong, this kind of issues just has a wide range of causes depending on the error. Through analysis it's a trial-error process of narrowing it down.

IMO, with this kind of issues, CPUs are the hardest to identify. Due to the complexicity of the hardware things are sometimes quite tricky.