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.

Nice guys! Thanks for letting us know :) I got BSOD twice, today, with same error: DPC_WATCHDOG_VIOLATION. It looks like I judged too early I suppose... UPDATE (29/09/2018): I confirmed with NVIDIA Support that the issue has not been resolved. The Release Notes in the latest driver update (27/09/2018) have been updated accordingly.

Well, it looks like indeed, they changed it from resolve to still known issue... To be continued.

I received feedback and a temporary workaround from Nvidia tech support (see below). I have followed these instructions and so far haven't experienced another crash. It would be great if others could report back with their findings / experience. Note that this will allow users to update to the latest drivers. This is a known issue that our development team is actively investigating. Our development team have root-caused the issue and will be implementing a solution in future driver update. At this point I don't know which driver release will have this fix. Until we can get this resolved in a driver update there is a workaround to this problem with our current drivers. Development indicated that enabling Message-Signaled Interrupts (MSI) does resolve the problem. Consider the steps below to enable MSI after installing the latest graphics drivers and that should help with the issue. You'll need to enable MSI for each GPU. 1. Download the MSI Utility v2.0 zip file here: https://github.com/CHEF-KOCH/MSI-utility/releases 2. Open the zip file and then extract "MSI_util_v2.exe" to your local system. 3. Right-click the "MSI_util_v2.exe" and Run as administrator. 4. Enable MSI for each GPU listed. 5. Restart the system. Until we can get the fix into a driver update you'll need to apply this workaround with each new driver update. We are working to get this fix into our drivers as soon as we can. Hope this helps. Let me know if you have any further questions. Best regards, Just built a 2nd machine with spare parts and grabbed this ASUS X99-E WS Mobo for the job. Using Octane for C4D was causing freezes and BSOD!! (tested Octane 3.08.3, 3.08.4, 4.00RC5) -Had installed Nvidia's 416.16, then 399.24, then 398.82 (current driver) all clean installs using DDU but none worked without BSOD until running MSI Utility v2.0. Specs: Machine 1 Xeon E5-2642 v3 64 GB DDR4 3x Geforce GTX 980 Ti (Driver 398.82) Asus X99-E WS mobo Windows 10 Pro v1803 -OS Build 17134.320 Machine 2 Xeon E5-2642 v3 64 GB DDR4 Asus Z10PE-D8 1x Geforce RTX 2080 (Driver 416.16) Windows 10 Pro v1803 -OS Build 17134.285 Currently running Octane for C4D 4.00RC5 on both machines with different card architecture and drivers and network rendering is solid after this fix! *just in case it wasn't clear, the problems that occurred were on machine 1 @Nvidia and @TorontoJones this seems to have fixed the issue for now-- thank you for sharing!

On Asus X299 Sage Workstation motherboard, with 4x 1080Ti GPUs, the MSI solution doesn't work, i.e. it still causes BSOD. Only the older drivers, version 388.13, work well on my machine.

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-09-24T19:27:33+00:00

Nice guys! Thanks for letting us know :)

I got BSOD twice, today, with same error: DPC_WATCHDOG_VIOLATION. It looks like I judged too early I suppose...

UPDATE (29/09/2018): I confirmed with NVIDIA Support that the issue has not been resolved. The Release Notes in the latest driver update (27/09/2018) have been updated accordingly.
Was this answer helpful?

0 comments No comments
Anonymous

2018-09-25T17:56:31+00:00

Well, it looks like indeed, they changed it from resolve to still known issue...

To be continued.
Was this answer helpful?

0 comments No comments
Anonymous

2018-10-07T19:10:40+00:00

I received feedback and a temporary workaround from Nvidia tech support (see below). I have followed these instructions and so far haven't experienced another crash. It would be great if others could report back with their findings / experience. Note that this will allow users to update to the latest drivers.

This is a known issue that our development team is actively investigating. Our development team have root-caused the issue and will be implementing a solution in future driver update. At this point I don't know which driver release will have this fix. Until we can get this resolved in a driver update there is a workaround to this problem with our current drivers. Development indicated that enabling Message-Signaled Interrupts (MSI) does resolve the problem. Consider the steps below to enable MSI after installing the latest graphics drivers and that should help with the issue. You'll need to enable MSI for each GPU.

1. Download the MSI Utility v2.0 zip file here:https://github.com/CHEF-KOCH/MSI-utility/releases

2. Open the zip file and then extract "MSI_util_v2.exe" to your local system.

3. Right-click the "MSI_util_v2.exe" and Run as administrator.

4. Enable MSI for each GPU listed.

5. Restart the system.

Until we can get the fix into a driver update you'll need to apply this workaround with each new driver update. We are working to get this fix into our drivers as soon as we can. Hope this helps. Let me know if you have any further questions.

Best regards,

Just built a 2nd machine with spare parts and grabbed this ASUS X99-E WS Mobo for the job.

Using Octane for C4D was causing freezes and BSOD!!

(tested Octane 3.08.3, 3.08.4, 4.00RC5)

-Had installed Nvidia's 416.16, then 399.24, then 398.82 (current driver) all clean installs using DDU but none worked without BSOD until running MSI Utility v2.0.

Specs:

Machine 1

Xeon E5-2642 v3

64 GB DDR4

3x Geforce GTX 980 Ti (Driver 398.82)

Asus X99-E WS mobo

Windows 10 Pro v1803

-OS Build 17134.320

Machine 2

Xeon E5-2642 v3

64 GB DDR4

Asus Z10PE-D8

1x Geforce RTX 2080 (Driver 416.16)

Windows 10 Pro v1803

-OS Build 17134.285

Currently running Octane for C4D 4.00RC5 on both machines with different card architecture and drivers and network rendering is solid after this fix!

*just in case it wasn't clear, the problems that occurred were on machine 1

@Nvidia and @TorontoJones this seems to have fixed the issue for now-- thank you for sharing!
Was this answer helpful?

0 comments No comments
Anonymous

2018-10-07T19:21:49+00:00

On Asus X299 Sage Workstation motherboard, with 4x 1080Ti GPUs, the MSI solution doesn't work, i.e. it still causes BSOD.

Only the older drivers, version 388.13, work well on my machine.
Was this answer helpful?

0 comments No comments
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more