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.

Thank you, Heavyhouse. I've tested Windows 10 Pro 1709 + 391.01 and it doesn't work; BSOD within minutes of running GPU workloads. I can only assume it's the combination of Windows version 1709 with the hotfix that likely makes the difference for you. I'll try it tomorrow. I've also got a ticket with Nvidia Support open. They recently confirmed the bug has been logged and promised to come back when a solution is available.

mrpinoux, I saw your comment in the OTOY forums and was having the same issue for the past two days. Today I got everything working seperately on two identical systems and also using them with NetRender. I posted this in the forums but I'm not sure if you have seen it there yet. Also I forgot to mention both in the post that both the PC's are running 4x1080tis This fixed my DPC_WATCHDOG_VIOLATION crashes that I was having when updating to the newest nvidia drivers for this release. This was my system: X99 E-10G-WS Bios: 05XX (Can't remember) Windows 10 1703 Nvidia Drivers 391.01 (Not Stable) 382.53 (was stable with previous Octane builds) Cinema 4D R19.053 On support with Nvida all day, then sent me a hotfix build 391.05 which did not fix it. I updated my BIOS to 0802 and that did not fix it. Said screw it and updated Windows to 1709. Voila, fixed. The fix might have just been to update Windows (which I hate doing) or it might have been a combination of the BIOS the OS and the Nvidia Driver update. I am updating my second identical workstation now and will try with NetRender to see if everything stays stable. Will let you know if it fails. Working build as of right now: X99 E-10G-WS Bios: 0802 Windows 10 1709 Nvidia Drivers 391.05 (Hotfix) Cinema 4D R19.053 Hope this can help someone!

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.

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

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.

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-13T03:32:59+00:00

Thank you, Heavyhouse.

I've tested Windows 10 Pro 1709 + 391.01 and it doesn't work; BSOD within minutes of running GPU workloads.

I can only assume it's the combination of Windows version 1709 with the hotfix that likely makes the difference for you. I'll try it tomorrow.

I've also got a ticket with Nvidia Support open. They recently confirmed the bug has been logged and promised to come back when a solution is available.
Was this answer helpful?

0 comments No comments
Anonymous

2018-03-13T02:56:32+00:00

mrpinoux,

I saw your comment in the OTOY forums and was having the same issue for the past two days. Today I got everything working seperately on two identical systems and also using them with NetRender. I posted this in the forums but I'm not sure if you have seen it there yet. Also I forgot to mention both in the post that both the PC's are running 4x1080tis

This fixed my DPC_WATCHDOG_VIOLATION crashes that I was having when updating to the newest nvidia drivers for this release.

This was my system:

X99 E-10G-WS Bios: 05XX (Can't remember)

Windows 10 1703

Nvidia Drivers 391.01 (Not Stable) 382.53 (was stable with previous Octane builds)

Cinema 4D R19.053

On support with Nvida all day, then sent me a hotfix build 391.05 which did not fix it.

I updated my BIOS to 0802 and that did not fix it.

Said screw it and updated Windows to 1709. Voila, fixed.

The fix might have just been to update Windows (which I hate doing) or it might have been a combination of the BIOS the OS and the Nvidia Driver update.

I am updating my second identical workstation now and will try with NetRender to see if everything stays stable. Will let you know if it fails.

Working build as of right now:

X99 E-10G-WS Bios: 0802

Windows 10 1709

Nvidia Drivers 391.05 (Hotfix)

Cinema 4D R19.053

Hope this can help someone!
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
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-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