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.

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!

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.

391.05 not 391.01 http://www.guru3d.com/files-get/geforce-391-05-hotfix-driver-download,1.html

Indeed, that's what I meant to test. Thanks for the link! Update : 391.05 has the same effect on my setup, crashes with DPC_WATCHDOG_VIOLATION, as in 391.01. Reverting back to 382.53. Looks like I can't use CUDA 9.0 apps until NVIDIA fixes the drivers.

Hi heavyhouse, Is there a way for you to screenshot your bios set up, few pages? I'm curious to see if there is anything regarding the options by default being different with my mother board, with 4G decoding, or other things that may trigger the problem on my end. My motherboard (ASUS X99-E WS) is the previous model compared to yours, so who knows... Thanks for your input :)

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-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-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-13T03:37:49+00:00

391.05 not 391.01

http://www.guru3d.com/files-get/geforce-391-05-hotfix-driver-download,1.html
Was this answer helpful?

0 comments No comments
Anonymous

2018-03-13T03:46:28+00:00

Indeed, that's what I meant to test. Thanks for the link!

Update : 391.05 has the same effect on my setup, crashes with DPC_WATCHDOG_VIOLATION, as in 391.01. Reverting back to 382.53.

Looks like I can't use CUDA 9.0 apps until NVIDIA fixes the drivers.
Was this answer helpful?

0 comments No comments
Anonymous

2018-03-17T01:36:06+00:00

Hi heavyhouse,

Is there a way for you to screenshot your bios set up, few pages? I'm curious to see if there is anything regarding the options by default being different with my mother board, with 4G decoding, or other things that may trigger the problem on my end. My motherboard (ASUS X99-E WS) is the previous model compared to yours, so who knows...

Thanks for your input :)
Was this answer helpful?

0 comments No comments