Recently I have built a 3D rendering station for a client of mine. The machine runs, but crashes about once or twice a day with a BSOD (watchdog violation 1x133. Blue Screen View mentions either nvlddmkm.sys or ntoskrnl.exe as culprit. Things I have tried so far: Clean install Windows 10 Clean install Windows 7 DDU removal of graphics drivers latest nVidia drivers older nVidia drivers extensive RAM testing Specs: Asus X99-WS 10G E Intel 6850K 7x Zotac 1080ti Blower Edition (transformed to water cooling) 64GB RAM Samsung 960 Pro 512GB (system drive) 3x WD Red in RAID 0 (data drive) 2x Cooler Master V1200 PSU Custom EK watercooling loop Obsidian 900D Speccy Snapshot: http://speccy.piriform.com/results/qchWoHD0m7mueWTEVccxFlD Any help or insight on this issue would be greatly appreciated, as this issue now causes great delays in my client's workflow.

Only NVIDIA can determine what's going on within its driver. That's because, besides new features, NVIDIA has to also accommodate changes made in the Windows Kernel by Microsoft. I've read that Windows 7 doesn't suffer from the same issues. Its kernel is stable and the NVIDIA driver is well tested on that OS. Windows 8, 8.1 and, now Windows 10 are a mess. There are major changes in how hardware resources are managed and application developers can't fix kernel related issues; they can only report them to Microsoft and wait for fixes to be applied in the next patch, which often breaks something else. That's the problem of continuous updates in Windows 10. We were served a half baked, buggy OS and now suffer from the consequences of poorly coordinated, continuous changes. Currently, in Windows 10, 3D rendering professionals suffer from GPU-related system crashes, and audio professionals suffer from audio dropouts and pops caused by high DPC Latency.

Thank you for this insight, very helpful to know that this is happening somewhere else as well. Regarding driver 382.53, unfortunately, it failed as well. System crashes with the difference of recovering two times before BSOD. No recovering like TDR recovery. Just hang, cursor & sound freeze, then cursor & sound back, then freeze again, then finally dies. Reverted to 378.92. Stable with Win 10 v1703. Quick question, which version of Win 10 are you running with 382.53?

Thank you for this insight, very helpful to know that this is happening somewhere else as well. Regarding driver 382.53, unfortunately, it failed as well. System crashes with the difference of recovering two times before BSOD. No recovering like TDR recovery. Just hang, cursor & sound freeze, then cursor & sound back, then freeze again, then finally dies. Reverted to 378.92. Stable with Win 10 v1703. Quick question, which version of Win 10 are you running with 382.53? 382.53 is stable on Win 10 Pro 64bit 1709 (OS Build 16299.251). It has only frozen once, while running heavy GPU workloads on all 4x GPUs, when I attempted to run GPU-z, at the time the utility was scanning the system (on the splash screen). Hasn't happened again and I've tested this scenario several times.

Hello! I'm also on 382.53 with win 10 ASUS X99 E WS 4X 1080TI Win 10 Pro 64bit 1709 (OS Build 16299.251) the ONLY stable driver atm is 382.53. I've tested pretty much everything. And like another member I need to update my drivers to run the latest Octane Render's version. Hope that the problem will be solved soon. If we need to do multiple messages for Microsoft or Nvidia I'm here :) the more we will be the more the updates will come fast. Cheers Max

Hello! I'm also on 382.53 with win 10 ASUS X99 E WS 4X 1080TI Win 10 Pro 64bit 1709 (OS Build 16299.251) the ONLY stable driver atm is 382.53. I've tested pretty much everything. And like another member I need to update my drivers to run the latest Octane Render's version. Hope that the problem will be solved soon. If we need to do multiple messages for Microsoft or Nvidia I'm here :) the more we will be the more the updates will come fast. Cheers Max In response to Ticket Ref. 180226-000525 NVIDIA Support has confirmed that the bug has been filed, but they cannot commit to how soon it will be resolved. Looks like both MS and NVIDIA update their software too often and release it without sufficient, timely testing. ASUS Support does not exist (in the UK, at least). They don't pick up the phone or answer to tickets submitted via their web site. I used FB Messenger to inform ASUS Rog UK about the problem and they promised to forward it to HQ. It always helps when more people open tickets with clear explanation of the problem. If you haven't openned a ticket with ASUS, NVIDIA and Microsoft, please consider doing so.

PC crashing - BSOD Watchdog violation 1x133 (possibly nVidia issue)

Anonymous

Recently I have built a 3D rendering station for a client of mine. The machine runs, but crashes about once or twice a day with a BSOD (watchdog violation 1x133. Blue Screen View mentions either nvlddmkm.sys or ntoskrnl.exe as culprit.

Things I have tried so far:

Clean install Windows 10
Clean install Windows 7
DDU removal of graphics drivers
latest nVidia drivers
older nVidia drivers
extensive RAM testing

Specs:

Asus X99-WS 10G E
Intel 6850K
7x Zotac 1080ti Blower Edition (transformed to water cooling)
64GB RAM
Samsung 960 Pro 512GB (system drive)
3x WD Red in RAID 0 (data drive)
2x Cooler Master V1200 PSU
Custom EK watercooling loop
Obsidian 900D

Speccy Snapshot: http://speccy.piriform.com/results/qchWoHD0m7mueWTEVccxFlD

Any help or insight on this issue would be greatly appreciated, as this issue now causes great delays in my client's workflow.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

87 answers

Anonymous

2018-03-08T07:40:43+00:00

Only NVIDIA can determine what's going on within its driver. That's because, besides new features, NVIDIA has to also accommodate changes made in the Windows Kernel by Microsoft.

I've read that Windows 7 doesn't suffer from the same issues. Its kernel is stable and the NVIDIA driver is well tested on that OS.

Windows 8, 8.1 and, now Windows 10 are a mess. There are major changes in how hardware resources are managed and application developers can't fix kernel related issues; they can only report them to Microsoft and wait for fixes to be applied in the next patch, which often breaks something else.

That's the problem of continuous updates in Windows 10. We were served a half baked, buggy OS and now suffer from the consequences of poorly coordinated, continuous changes.

Currently, in Windows 10, 3D rendering professionals suffer from GPU-related system crashes, and audio professionals suffer from audio dropouts and pops caused by high DPC Latency.
Was this answer helpful?

0 comments No comments
Anonymous

2018-03-08T19:28:13+00:00

Thank you for this insight, very helpful to know that this is happening somewhere else as well.

Regarding driver 382.53, unfortunately, it failed as well. System crashes with the difference of recovering two times before BSOD. No recovering like TDR recovery. Just hang, cursor & sound freeze, then cursor & sound back, then freeze again, then finally dies.

Reverted to 378.92. Stable with Win 10 v1703.

Quick question, which version of Win 10 are you running with 382.53?
Was this answer helpful?

0 comments No comments
Anonymous

2018-03-09T16:40:09+00:00

Thank you for this insight, very helpful to know that this is happening somewhere else as well.

Regarding driver 382.53, unfortunately, it failed as well. System crashes with the difference of recovering two times before BSOD. No recovering like TDR recovery. Just hang, cursor & sound freeze, then cursor & sound back, then freeze again, then finally dies.

Reverted to 378.92. Stable with Win 10 v1703.

Quick question, which version of Win 10 are you running with 382.53?

382.53 is stable on Win 10 Pro 64bit 1709 (OS Build 16299.251).

It has only frozen once, while running heavy GPU workloads on all 4x GPUs, when I attempted to run GPU-z, at the time the utility was scanning the system (on the splash screen). Hasn't happened again and I've tested this scenario several times.
Was this answer helpful?

0 comments No comments
Anonymous

2018-03-10T10:43:27+00:00

Hello!

I'm also on 382.53 with win 10 ASUS X99 E WS

4X 1080TI Win 10 Pro 64bit 1709 (OS Build 16299.251)

the ONLY stable driver atm is 382.53. I've tested pretty much everything. And like another member I need to update my drivers to run the latest Octane Render's version.

Hope that the problem will be solved soon. If we need to do multiple messages for Microsoft or Nvidia I'm here :)

the more we will be the more the updates will come fast.

Cheers

Max
Was this answer helpful?

0 comments No comments
Anonymous

2018-03-10T12:52:10+00:00

Hello!

I'm also on 382.53 with win 10 ASUS X99 E WS

4X 1080TI Win 10 Pro 64bit 1709 (OS Build 16299.251)

the ONLY stable driver atm is 382.53. I've tested pretty much everything. And like another member I need to update my drivers to run the latest Octane Render's version.

Hope that the problem will be solved soon. If we need to do multiple messages for Microsoft or Nvidia I'm here :)

the more we will be the more the updates will come fast.

Cheers

Max

In response to Ticket Ref. 180226-000525 NVIDIA Support has confirmed that the bug has been filed, but they cannot commit to how soon it will be resolved.

Looks like both MS and NVIDIA update their software too often and release it without sufficient, timely testing.

ASUS Support does not exist (in the UK, at least). They don't pick up the phone or answer to tickets submitted via their web site. I used FB Messenger to inform ASUS Rog UK about the problem and they promised to forward it to HQ.

It always helps when more people open tickets with clear explanation of the problem. If you haven't openned a ticket with ASUS, NVIDIA and Microsoft, please consider doing so.
Was this answer helpful?

0 comments No comments