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

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,

This workaround...

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,

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.

It may help to look at the minidump files from the blue screen crashes.

Can you zip up the minidump files in the C:\Windows\Minidump folder and make available (provide link) via a public folder on OneDrive or similar site.

Here's a link on using OneDrive:

http://windows.microsoft.com/en-ca/onedrive/share-file-folder

If you have problems zipping the minidump files copy the minidump files to another location such as a folder on the Desktop

Also, you do not necessarily have to zip up the minidump files, you can upload them one at a time

Hello,

A stop error (also called a "blue screen" error) can occur if a problem causes your PC to shut down or restart unexpectedly. These errors can be caused by both hardware and software issues. Th error indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above. The value of Parameter 1 indicates whether a single DPC exceeded a timeout, or whether the system cumulatively spent an extended period of time at IRQL DISPATCH_LEVEL or above. DPCs should not run longer than 100 microseconds and ISRs should not run longer than 25 microseconds, however the actual timeout values on the system are set much higher.

Let's try performing the steps below as this method fixed the vast majority of DPC_WATCHDOG_VIOLATION errors on Windows 10.

1. Press Windows key + R, then type in devmgmt.msc and press Enter.
2. Open the IDE ATA/ATAPI controllers section.
3. Select the controller that says ‘SATA AHCI’, right click and select Properties.
4. Select the Driver tab and Driver Details. Make sure the driver is ‘iastor.sys’. If it is, kindly proceed. If it isn’t, try another or move on to the next step.
5. Select Update Driver Software, Browse and Let me Pick from a list of devices.
6. Select ‘Standard SATA AHCI Controller’ from the list and install.

Also, you can check this **article**to troubleshoot blue screen errors on Windows 10.

We look forward to your response.

Regards.