Ntoskrnl blue screen of death random crashes

William Cricket

Honorable
Dec 9, 2013
21
0
10,520
Hello,

Recently i have been having multiple blue screens of death and the cause always ends up being the file "ntoskrnl.exe" acording to Bluescreenview.
It is completly random and has been happening for a few weeks now. It's usually while gaming or sometimes on the desktop, while the pc is iddling, and i'm browsing the web.
I dont know what to do, cant find the exact cause of the problem

My pc specs are the following:
intel core i7 6700k
asus z170-a
g.skill ripjaws v 16gb 2400mhz (2x8)
gigabyte gtx 1070 g1 gaming
samsung 850 evo 250gb ssd
seagate barracuda 2tb 7200rpm hdd
evga gq 650w
nzxt s340
cryorig h7
tp-link wdn4800
windows 10 home 64bit

Can anyone help me out on this?

Much appreciated
 
Solution
Reporting back.
After a lot of crap i went through i finally found out what was causing these bsods. It weren't any drivers or corrupted system files, it turns out my processor just needed more voltage.

To explain the voltage situation: On my first boot after assembling my machine i noticed the auto mode vcore was at 1.328 volts, which i though were too much for running at stock clocks, so i set it at 1.200 volts manually.

Fastforward to today: To simply put it, my cpu is a glutton and needs at least 1.250 volts to run at stock. It wasn't getting the power it needed and because of that it was bsoding in heavy workloads.

Seanie280672

Estimable
Mar 19, 2017
1,958
1
2,960
Most of the time it's caused by drivers, and lately it seems to be graphics drivers causing the problems.

Fully uninstall your current graphics drivers, reboot your computer, and then download and install the latest from the nvidia website.

Also make sure you motherboard drivers etc are up to date.
 

William Cricket

Honorable
Dec 9, 2013
21
0
10,520


Well i reinstalled my gpu drivers. Motherboard drivers are all up to date, that includes usb, chipset, sound, and sata.
Let's see how this turns out

 
Please uninstall your GPU drivers using DDU, http://www.guru3d.com/files-details/display-driver-uninstaller-download.html, and install the drivers using a fresh download http://www.geforce.com/drivers.
When installing, check the clean install box and only install the graphics driver and the physx driver.
 
I'm new to this forum, not sure how this vote system works but can't you undo the downvote if it was a misclick?

The nvidia display drivers have been flagged in both dumps, chances are they are the cause but they are at least involved. With crash dump analysis we can't say anything for certain until it has been proven.
 

Seanie280672

Estimable
Mar 19, 2017
1,958
1
2,960


Just upvote to undo it I believe.

Theres something wrong with the nVidia drivers at the moment, they seem to be causing a lot of problems, as I stated in my 1st response, it might be worth trying the previous version of drivers or a beta release if one is available.

But when you uninstall the drivers, what you really need to do is some kind of driver cleaner to make sure all traces of it are gone, reg cleaner maybe, or manually clean all traces like common files, user files, physics drivers etc.
 

William Cricket

Honorable
Dec 9, 2013
21
0
10,520


Reporting back on my issue: i booted up to safe mode, opened up DDU and uninstalled the nvidia gpu drivers. After that i rebooted into normal mode and clean installed the nvidia drivers. I only installed the driver itself and the physx engine.
I'm going to test the machine and see if any bsods persist.

 

William Cricket

Honorable
Dec 9, 2013
21
0
10,520


Last time i tried to use driver verifier i got stuck into a freaking boot loop, in which as soon as i booted into windows i would get a blue screen of death right away called "driver verifier detected violation". I had to reset my machine just to turn it off.
 

William Cricket

Honorable
Dec 9, 2013
21
0
10,520


Well well well, i followed the instructions on the link https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/29-driver-verifier-bsod-related-windows-10-8-1-8-7-vista.html and enabled driver verifier. About 25/30 seconds after booting into windows i got a "driver verifier detected violation" bsod. Booted into safe mode, disable driver verifier, and proceeded to normal boot without issues. I consulted the dump file with with the "Whocrashed" software and it was "avgsnx.sys", a component of avg antivirus software. Since windows 10 wont let me upload the dump file onto google drive because i "do not have permission", i'll post a screenshot of the dump.

https://drive.google.com/file/d/0B1eOzCzxxfNRZEtqZGtZbE1Lcm8/view?usp=sharing
https://drive.google.com/file/d/0B1eOzCzxxfNRdlRpeWhESzQtWFE/view?usp=sharing
 

William Cricket

Honorable
Dec 9, 2013
21
0
10,520


I cant upload it to anything, windows 10 keeps telling me i dont have permission to open this file and i should contact an administrator.
I am so sick of this crap

 

William Cricket

Honorable
Dec 9, 2013
21
0
10,520
Reporting back.
After a lot of crap i went through i finally found out what was causing these bsods. It weren't any drivers or corrupted system files, it turns out my processor just needed more voltage.

To explain the voltage situation: On my first boot after assembling my machine i noticed the auto mode vcore was at 1.328 volts, which i though were too much for running at stock clocks, so i set it at 1.200 volts manually.

Fastforward to today: To simply put it, my cpu is a glutton and needs at least 1.250 volts to run at stock. It wasn't getting the power it needed and because of that it was bsoding in heavy workloads.
 
Solution