Haunted by ntoskrnl.exe BSODs.

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
T

tkurgpold

Commendable
Jul 22, 2018
35
0
1,530
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
==================================================

 
Sort by date Sort by votes


100% sure that was the error that came up, and this was the most recent mini dump there, so.. Not sure what happened.
 
Upvote 0 Downvote
Alright, well...

Tried letting it bluescreen a few more times just now, it refuses to generate a minidump. Started to think that it's because my pagefil is on a different hard drive. Okay, I'll do the system restore, move it back, and then try Driver Verifier again. Except system restore wont work. Tried it three times, all I get is an "unspecified error", 0x80070003. Damnit.
 
Upvote 0 Downvote
"What’s Driver Verifier? Sure sounds like something that messes up all your drivers and screws up windows. Your best to do a clean reinstall I don’t ever use driver verifier or any driver utility that automatically install the drivers that’s the quickest way to failure"

You're kidding, right?
 
Upvote 0 Downvote

Driver Verifier is a part of Windows itself. What it does is basically stresses all of your drivers out therefore making one crash. In the process, hopefully it makes the bad driver show it's face (usually in the dump file). It works sometimes, doesn't other times. There's no special download or install for it (it's kinda like Notepad, it's from Microsoft and built into Windows itself).

It can cause your PC to go into a boot loop, so read Colifs instructions and the instructions on the Microsoft website first. Important: Create a restore point first. Be prepared to get out of the boot loop if you go into the boot loop. If you don't understand it, then either ask more questions or don't try it.
 
Upvote 0 Downvote


I've already done all this, I'm well aware of what Driver Verifier is and how it works.
 
Upvote 0 Downvote
@ Peter Martin - https://answers.microsoft.com/en-us/windows/forum/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

@ Thurgold. 0x80070003 is a windows update error.
see if this helps -
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
 
Upvote 0 Downvote


Sorry - this is happening when I try to do the system restore, both from the flash drive and in the recovery options when trying to boot, and both from the point I created and a system-generated one from a minute earlier.
 
Upvote 0 Downvote
did you try the SFC command and other one? They will find any corrupt system files and the combination should fix them. SFC (System File Checker) uses the image files used by windows when it first installed, to scan for any bad files. The 2nd command cleans the Image files themselves, so if SFC finds files it cannot fix, run it again after the 2nd command and restart PC.

just to confirm its not your hard drive causing the slow down you get every 6 months - run Data Lifeguard for windows and check drive out - https://support.wdc.com/downloads.aspx?p=3 (its made by western Digital)

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.
 
Upvote 0 Downvote


I've been unable to run the commands, as Windows does not boot. The error happens when I try to run System Restore.
 
Upvote 0 Downvote
slaps self for suggesting same thing twice in 1 thread :) (SFC twice.. oops)

the western digital link i showed creates a bootable USB so can test hdd without windows. You can run the chkdsk scan in safe mode if you left PC on in there?

Hope the driver verifer wasn't reason it stopped booting?

Wonder what "Gear Software Advanced SCSI Programming Interface Windows Driver" is part of?
seems it can be CD/DVD drivers from Itunes? Old drivers are usual reason for BSOD, not always but its a start. 2013 is too old for it to be a win 10 driver.

GEARAspiWDM.sys is a driver that is part of both iTunes and Norton's Save & Restore software suites. With this process, disks can be partially opened both physically and physically so that the above mentioned applications have access. It helps to directly copy music to the iPod connected via the USB drive and where the iTunes library is considered virtual
Click to expand...

this is all that was loaded
May 16 2013 GEARAspiWDM.sys Gear Software Advanced SCSI Programming Interface Windows Driver Model http://www.gearsoftware.com/
Nov 26 2015 usbfilter.sys AMD USB Filter driver
Apr 11 2016 asmtxhci.sys ASMedia USB 3.0 driver http://www.asmedia.com.tw/
Apr 21 2016 tap0901.sys TAP-Win32 Virtual Private Network Driver 0901 (OpenVPN by OpenVPN Technologies) https://openvpn.net/
Jun 15 2018 rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver http://www.realtek.com.tw/
Jun 24 2018 nvlddmkm.sys Nvidia Graphics Card driver http://www.nvidia.com/
Click to expand...
 
Upvote 0 Downvote

Ah, yeah, does seem like the iTunes driver might be it then, everything else(apart from the OpenVPN thing) looks to be drivers provided by hardware manufacturers for the parts I have. I'll see if I can uninstall the driver in the morning.

Odd, though, considering I'm using the Windows Store version of iTunes...

And yeah, driver verifier was what stopped it from booting. Blue screen came up before the login screen could even come up, then looped. Turned out I was dumb and I could just go into safe mode and turn it off that way.
 
Upvote 0 Downvote
Driver Verifer - Often the safe mode route actually doesn't work, its why i offer system restore. You were 1st person I have given that advice to where it didn't work and the default way to stop it did. I wish there was a reliable way to turn it off. If they going to force PC to crash, they could at least provide an escape route.

wait and see if taking Itunes driver off fixes it or not, we thought we fixed it in July after all
 
Upvote 1 Downvote
Looked into how to uninstall it, the documentation I found said that iTunes would no longer allow me to use CDs.. Which kind of sucks. Tried updating the driver to the latest version, blue screens stopped for a while. Then, tried playing a bit of Forza just now, UNEXPECTED_STORE_EXCEPTION. Mini dump is 0kb.
 
Upvote 0 Downvote
I hate that error, its name used to make me think it was storage so would recommend checking ram/hdd. Now I suspect its more likely to be USB devices or PCI cards. I haven't nailed its cause down yet.

Was/is CD drive internally mounted or external?
What USB devices have you got?

is minidump on C drive? Is page file on C?
 
Upvote 0 Downvote


CD drive is internally mounted. USB devices are, apart from keyboard and mouse, 2 external hard drives, Presonus Audiobox, webcam/ps3 controller depending on which im using, and some generic cheap xbox controller off Amazon. Minidumps are on C, there's a pagefile on C at the moment because I wasn't getting minidumps from the driver verifier bsod.
 
Upvote 0 Downvote
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom