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.

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, Thanks for the info! Have tried this today and so far, the machine is rendering a C4D-scene (with 7* GTX 1080ti) without crash for over 2 hours. Have not been able to do that yet, so looking good. Fingers crossed, I will post back with results.

Unfortunately, it crashes again. It rendered fine for about 5,5 hours last night, but today it will crash after 10-30 minutes. Same watchdog violation. Please release a fix, NVIDIA!

Hmm. I've been more stable on my end but haven't been rendering as much as you. Couple of things to check... running Windows 10 1709 using latest Nvidia driver when you ran the Nvidia supplied app you made sure to check / activate msi for every gpu you restarted your system after the app ran

Thanks for the reminder, it seems I forgot the reboot after applying the MSI-Utility. Silly :) The machine has now been rendering for 15+ hours on 7 cards and still going strong, which absolutely is a first! Thank you very, very much for posting the workaround.

Glad to hear it's working for you. Let's hope it stays that way! One thing I have noticed on my end is that occasionally the display graphics will freeze up for several seconds and then contine on normally. This hasn't been a huge problem but it is noticeable from time to time. I'm relieved that the system crashing has seemed to stop altogether. Hope we see a solution in place of a workaround in an upcoming driver.

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-08-07T18:03:52+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,

Thanks for the info!

Have tried this today and so far, the machine is rendering a C4D-scene (with 7* GTX 1080ti) without crash for over 2 hours. Have not been able to do that yet, so looking good. Fingers crossed, I will post back with results.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2018-08-08T16:30:12+00:00

Unfortunately, it crashes again. It rendered fine for about 5,5 hours last night, but today it will crash after 10-30 minutes. Same watchdog violation.

Please release a fix, NVIDIA!
Was this answer helpful?

0 comments No comments
Anonymous

2018-08-08T16:35:42+00:00
Hmm. I've been more stable on my end but haven't been rendering as much as you. Couple of things to check...
- running Windows 10 1709
- using latest Nvidia driver
- when you ran the Nvidia supplied app you made sure to check / activate msi for every gpu
- you restarted your system after the app ran
Was this answer helpful?

0 comments No comments
Anonymous

2018-08-10T06:44:14+00:00

Thanks for the reminder, it seems I forgot the reboot after applying the MSI-Utility. Silly :)

The machine has now been rendering for 15+ hours on 7 cards and still going strong, which absolutely is a first!

Thank you very, very much for posting the workaround.
Was this answer helpful?

0 comments No comments
Anonymous

2018-08-10T11:48:06+00:00

Glad to hear it's working for you. Let's hope it stays that way!

One thing I have noticed on my end is that occasionally the display graphics will freeze up for several seconds and then contine on normally. This hasn't been a huge problem but it is noticeable from time to time. I'm relieved that the system crashing has seemed to stop altogether.

Hope we see a solution in place of a workaround in an upcoming driver.
Was this answer helpful?

0 comments No comments