Constant BSOD GTX1070

[hrmstealth]

Evening all

I've been having some seriously frustrating BSOD issues for a while now, with no solution found yet.

PC ran fine for months after being built, then all of a sudden it started to produce the same "Video_Scheduler_Internal_Error" BSOD over and over again, even getting to the point where the PC refused to boot at all. Thankfully the onboard graphics does work, so I can still use it for now but without being able to do much in the meantime.

I've been all over the internet looking for possible solutions but at this point I'm willing to try anything to get this fixed.

I have run sfc/ scannow and chkdsk, no issues reported
Updated BIOS to latest version
Updated to latest graphic drivers from the NVIDIA site and mobo chipsets
Reinstalled Windows


PC Specs:
Intel i5 6600K
Gigabyte GA-Z170X-UD3 Motherboard
Gigabyte GeForce GTX 1070 Windforce 8GB
Corsair Vengeance 16GB DDR4 RAM
Antec VPF650W PSU
Samsung PM951 512GB SSD
Toshiba 3TB SATA HDD


I have also attached the 2 latest minidump files in case they are of any help.

https://drive.google.com/file/d/0Bw5JkNPFtA3rVmRXT1BuRG1uQlk/view

Cheers

 

[PC Tailor]

Can you run on the GPU in Safe Mode?
When you installed to the latest drivers, did you cleanse your computer completely of all old ones?

If you cannot run in Safe Mode, it is likely not a driver issue.
If you did not clean before updating drivers, clean up using Display Driver Uninstaller http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Then reinstall latest drivers.

 

[hrmstealth]

Can you run on the GPU in Safe Mode?
When you installed to the latest drivers, did you cleanse your computer completely of all old ones?

If you cannot run in Safe Mode, it is likely not a driver issue.
If you did not clean before updating drivers, clean up using Display Driver Uninstaller http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Then reinstall latest drivers.

When I'm able to boot the PC after BSOD (sometimes it wont boot at all but sometimes it will) I can enter safe mode using it. I've also followed many threads about completely wiping the drivers and have used DDU numerous times, to the point where I have used it every time I update the drivers. Unfortunately it is the same issue every time.

Attached is an image of the minidump through BlueScreenViewer.

http://i.imgur.com/sEy05nz.png

 

[PC Tailor]

Can you run on the GPU in Safe Mode?
When you installed to the latest drivers, did you cleanse your computer completely of all old ones?

If you cannot run in Safe Mode, it is likely not a driver issue.
If you did not clean before updating drivers, clean up using Display Driver Uninstaller http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Then reinstall latest drivers.

When I'm able to boot the PC after BSOD (sometimes it wont boot at all but sometimes it will) I can enter safe mode using it. I've also followed many threads about completely wiping the drivers and have used DDU numerous times, to the point where I have used it every time I update the drivers. Unfortunately it is the same issue every time.

Attached is an image of the minidump through BlueScreenViewer.

http://i.imgur.com/sEy05nz.png

Well based on what you are experiencing, it's definitely a driver issue, if you can boot into Safe Mode, what OS are you on?

See this for reference also: https://forums.geforce.com/default/topic/413110/the-nvlddmkm-error-what-is-it-an-fyi-for-those-seeing-this-issue/

Have you tried installing the last stable drivers, as opposed to just the latest ones for your OS? So maybe just rollback to a previous driver, see if the error still continues.

Just to confirm, you cleaned using Display Driver uninstaller in Safe Mode, and then when you reinstalled the latest drivers, you ensured 'clean install' was ticked and only reinstalled the PhysX driver?

 

[hrmstealth]

Can you run on the GPU in Safe Mode?
When you installed to the latest drivers, did you cleanse your computer completely of all old ones?

If you cannot run in Safe Mode, it is likely not a driver issue.
If you did not clean before updating drivers, clean up using Display Driver Uninstaller http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Then reinstall latest drivers.

When I'm able to boot the PC after BSOD (sometimes it wont boot at all but sometimes it will) I can enter safe mode using it. I've also followed many threads about completely wiping the drivers and have used DDU numerous times, to the point where I have used it every time I update the drivers. Unfortunately it is the same issue every time.

Attached is an image of the minidump through BlueScreenViewer.

http://i.imgur.com/sEy05nz.png

Well based on what you are experiencing, it's definitely a driver issue, if you can boot into Safe Mode, what OS are you on?

See this for reference also: https://forums.geforce.com/default/topic/413110/the-nvlddmkm-error-what-is-it-an-fyi-for-those-seeing-this-issue/

Have you tried installing the last stable drivers, as opposed to just the latest ones for your OS? So maybe just rollback to a previous driver, see if the error still continues.

Just to confirm, you cleaned using Display Driver uninstaller in Safe Mode, and then when you reinstalled the latest drivers, you ensured 'clean install' was ticked and only reinstalled the PhysX driver?

I'm running Win10 x64.

I can rollback using previous drivers but any drivers I've installed the past few months havent been that stable in terms of the PC crashing. I can give it another go though.

I always make sure that clean install is ticked every time I install new drivers, and have done tests selecting and deselecting each individual component i.e PhysX driver but same issue.

I'll give it another shot now and see what happens.

 

[hrmstealth]

Rolled back to previous driver and ran DDU to uninstall everything etc, same result if not worse.

Latest minidump image below.

http://i.imgur.com/KnbO5Sz.png

 

[PC Tailor]

Rolled back to previous driver and ran DDU to uninstall everything etc, same result if not worse.

Latest minidump image below.

http://i.imgur.com/KnbO5Sz.png

Very strange, there could potentially be another driver conflicting with the GPU. But I would expect driver rollback usually to resolve that.

Out of curiosity, are you overclocking in any way, bad OC can also cause this kind of problem.
Additionally does the BSOD occur when you open certain types of applications or completely random?
Have you tried using Whocrashed to interpret the minidump in detail? http://www.resplendence.com/whocrashed

- Firstly I would go into the device manager, scan for hardware changes, and see if there are any drivers that are showing an error / exlamation mark.
- Do you also have MSI Afterburner or RivaTuner Statistics? If so I would remove them both and see if this helps in any way
- Ensure that every other driver in your PC is up to date - this may be of use https://www.intel.com/content/www/us/en/support/detect.html
- I would also perform a memtest just to rule out the possibility.

 

[hrmstealth]

Rolled back to previous driver and ran DDU to uninstall everything etc, same result if not worse.

Latest minidump image below.

http://i.imgur.com/KnbO5Sz.png

Very strange, there could potentially be another driver conflicting with the GPU. But I would expect driver rollback usually to resolve that.

Out of curiosity, are you overclocking in any way, bad OC can also cause this kind of problem.
Additionally does the BSOD occur when you open certain types of applications or completely random?
Have you tried using Whocrashed to interpret the minidump in detail? http://www.resplendence.com/whocrashed

- Firstly I would go into the device manager, scan for hardware changes, and see if there are any drivers that are showing an error / exlamation mark.
- Do you also have MSI Afterburner or RivaTuner Statistics? If so I would remove them both and see if this helps in any way
- Ensure that every other driver in your PC is up to date - this may be of use https://www.intel.com/content/www/us/en/support/detect.html
- I would also perform a memtest just to rule out the possibility.

When the PC was first built it had a slight OC on the CPU, but I believe last time we upgraded the bios to its current version it was wiped, unless there is something else we are missing..

BSOD can occur either while in a game or in the case of last night, watching a youtube video. When it reboots it either doesnt work at all or when it boots into windows everything freezes every few seconds which is strange.

I have Whocrashed, the main memory.dmp file stated nvlddmkm.sys as the issue, however the minidump said it was a steelseries driver causing the crash which is a new one. I updated the drivers for that also so it will be interesting to see what the cause will be next time aside form the usual nvlddmkm.sys and watchdog files.

I have scanned for hardware changes throughout device manager, and there is nothing there showing any errors.

I havent had Afterburner or RivaTuner installed for quite some time so I'm not sure if that could be the cause, again will have to wait and see for the next crash.

Just installed the Intel Driver update utility and it couldnt find any drivers to update.

I have run the standard windows memtest before and it showed no errors, I can run memtest86 later on if that is any help?

Since the last crash I have changed a few settings and looked at the audio drivers, so far so good but I havent tested anything with it yet. I will report back if anything changes.

 

[hrmstealth]

Please disregard my last post.
As I posted the answer it gave me another bluescreen, same BSOD, then a further 3 times as it was trying to boot.
As of now I have removed the card and it is running fine.

This is the result from WhoCrashed

On Tue 01/08/2017 6:21:41 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\080117-18078-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x355E)
Bugcheck code: 0x119 (0x5, 0xFFFF9A8E40EC5000, 0xFFFF9A8E40F5E010, 0x315)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 01/08/2017 6:21:41 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x10D3BB)
Bugcheck code: 0x119 (0x5, 0xFFFF9A8E40EC5000, 0xFFFF9A8E40F5E010, 0x315)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
Bug check description: This indicates that the video scheduler has detected a fatal violation.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys .
Google query: nvlddmkm.sys VIDEO_SCHEDULER_INTERNAL_ERROR



On Tue 01/08/2017 6:20:28 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\080117-15828-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x355E)
Bugcheck code: 0x119 (0x5, 0xFFFFD78BEF597000, 0xFFFFD78BEBEFAAD0, 0xF0)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

[PC Tailor]

Please disregard my last post.
As I posted the answer it gave me another bluescreen, same BSOD, then a further 3 times as it was trying to boot.
As of now I have removed the card and it is running fine.

This is the result from WhoCrashed

On Tue 01/08/2017 6:21:41 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\080117-18078-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x355E)
Bugcheck code: 0x119 (0x5, 0xFFFF9A8E40EC5000, 0xFFFF9A8E40F5E010, 0x315)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 01/08/2017 6:21:41 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x10D3BB)
Bugcheck code: 0x119 (0x5, 0xFFFF9A8E40EC5000, 0xFFFF9A8E40F5E010, 0x315)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
Bug check description: This indicates that the video scheduler has detected a fatal violation.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys .
Google query: nvlddmkm.sys VIDEO_SCHEDULER_INTERNAL_ERROR



On Tue 01/08/2017 6:20:28 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\080117-15828-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x355E)
Bugcheck code: 0x119 (0x5, 0xFFFFD78BEF597000, 0xFFFFD78BEBEFAAD0, 0xF0)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

I would just double check your BIOS settings and make sure everything is as standard. Sometimes a minor voltage or frequency change (even if almost negligible) can sometimes cause this.

Equally I would remove all USB devices (such as Webcams, Microphones etc) just in case there is a driver conflict there.

Failing that, you have 2 different BSOD bugchecks there, have you had more than just these 2?
Multiple different types of BSOD may indicate hardware. Especially considering you have already reinstalled windows.

 

[hrmstealth]

I'll double check the bios, but not too sure what the original values for any of the voltages would/should be but I'll have a look around.

I'll remove what I can USB wise and see what happens, I only usually have one or 2 plugged in at a time as it is so I'll see what happens.

In regards to the different BSODs, its constantly watchdog and nvlddmkm, everything else is just random. I actually had the graphics card sent away for testing but results came back negative so must be something else going on.
If all else fails I'll try and get the entire PC looked at a local shop if it persists.

 

[PC Tailor]

After that. If you can't see any frequency or voltage abnormality, potentially try these and see if you encounter any changes:
- Move RAM into different slots and retest. Ram can cause all sorts of errors for almost no obvious reason. Equally try with one RAM stick at a time and see of you hit any errors. Also are all your RAM slots populated?

- Check for GPU bios updates and update accordingly

- I haven't looked at your motherboard yet, but if you have another PCIE slot, try moving the GPU over and retesting.

Edit: accidentally pressed select solution! So apologies if you get a notification saying you solved your own thread :')

 

[hrmstealth]

No problem, the saga continues haha.

I actually swapped the ram slots from 2 and 4 to 1 and 3 the other day (2 sticks, 4 slots) and ran the windows memtest again and still showed no issues, so I'll just had to do it induvidually I suppose.

Not sure about GPU bios updates so I'll see what can be done there.

when the problem first arose I actually plugged the card into both other slots but still had the same issue, so I'm not too sure what else to do in that regard.

I'll keep testing and see what happens

 

[PC Tailor]

No problem, the saga continues haha.

I actually swapped the ram slots from 2 and 4 to 1 and 3 the other day (2 sticks, 4 slots) and ran the windows memtest again and still showed no issues, so I'll just had to do it induvidually I suppose.

Not sure about GPU bios updates so I'll see what can be done there.

when the problem first arose I actually plugged the card into both other slots but still had the same issue, so I'm not too sure what else to do in that regard.

I'll keep testing and see what happens

Yeah GPU bios is the next step.

Also I wouldn't say run a memtest each time you change ram, just change ram around, run one stick at a time and then just run the PC normally and wait to encounter a problem.

Being as you're saying you can run in safe mode fine, it would seem likely that there's some devious conflicts occurring somewhere and memtest wouldn't really pull them out.

I hope you can get it sorted! Obviously keep me updated.