I just wanted to let you guys n gals know that this issue seems to have been solved, so I am sharing it with the greater 3D community as widely as possible. This happens to mobo's using more than a single GPU on a board with PLX chips (X99)
Our current workstations are using:
X99-E WS usb 3.1 (Bios 3803, but not likely required for the fix)
4 liquid cooled GTX 1080 TI's and misc I/O slots fully populated
Fixing this:
1. We grabbed the Message-Signaled Interrupts Utility v2.0 from github (pre compiled executable is also available) which enables MSI messaging over the BSOD-inducing line-based interrupts using Nvidia's latest driver branches beyond 382.33.
2. Extract MSI_util_v2.exe
3. Right-click MSI_util_v2.exe and Run as administrator (Or the pci-e devices and GPU's will not display)
4. Enable MSI for each GPU listed (Multiple similar GPU's should be stacked together) by clicking each GPU checkbox in the MSI column.
5. Click apply in the upper right corner, and Restart your workstation
6. Re-run the tool to to make sure MSI is still enabled
We have been hammering our workstations' GPU's for 13 hours straight using the latest 399.07 drivers and not a single crash occurred. This used to happen after minutes into a simple login.
Thanks for all you do!
DPC_WATCHDOG_VIOLATION BSOD [SOLVED]
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
- Tenth_Old_Man
- Posts: 17
- Joined: Thu Sep 15, 2011 7:04 am
Last edited by Tenth_Old_Man on Thu Sep 13, 2018 6:50 pm, edited 3 times in total.
- eyelovemotion
- Posts: 63
- Joined: Mon Sep 16, 2013 3:13 pm
That would cure my headaches since almost 2 Years now.
I have read so much about this issue regarding the PLX X99 Problems and it was very intersting to experience, that
NVIDIA is also working on that special problem.
i have just run MSI Tool and set all of my Cards to MSI checked on.
You Forgot to mention, to klick the Apply button on the top right before closing.
I just started my Win10 fresh.
All my Cards have MSI still checked on.
Now- ich will start rendering and see if that really helped.
I want to belief in that....
Thank you so much for sharing. I will also share.
Will report if / when that cured the PLX Disease.
Bye from Hamburg, Germany
I have read so much about this issue regarding the PLX X99 Problems and it was very intersting to experience, that
NVIDIA is also working on that special problem.
i have just run MSI Tool and set all of my Cards to MSI checked on.
You Forgot to mention, to klick the Apply button on the top right before closing.
I just started my Win10 fresh.
All my Cards have MSI still checked on.
Now- ich will start rendering and see if that really helped.
I want to belief in that....

Thank you so much for sharing. I will also share.
Will report if / when that cured the PLX Disease.
Bye from Hamburg, Germany
- eyelovemotion
- Posts: 63
- Joined: Mon Sep 16, 2013 3:13 pm
Yes.
I can confirm:
THE MSI SOLUTION WORKS A 100%!!!!
NO MORE CRASHES ON X99 WITH LPX CHIP!
HELLO TO NVIDIA!
HAVE A LOOK AT THAT MSI TOOL AND IMPLEMENT THAT CURE IN YOUR DRIVERS!
THANK YOU FOR YOUR POST!
SAVED MY NERVES!
I can confirm:
THE MSI SOLUTION WORKS A 100%!!!!
NO MORE CRASHES ON X99 WITH LPX CHIP!
HELLO TO NVIDIA!
HAVE A LOOK AT THAT MSI TOOL AND IMPLEMENT THAT CURE IN YOUR DRIVERS!
THANK YOU FOR YOUR POST!
SAVED MY NERVES!
- Tenth_Old_Man
- Posts: 17
- Joined: Thu Sep 15, 2011 7:04 am
eyelovemotion wrote:That would cure my headaches since almost 2 Years now.
...
You Forgot to mention, to klick the Apply button on the top right before closing.
...
Thank you for the apply button comment, I totally forgot to mention that. I have edited my original post.
Rick
Hello,
I was hoping this would solve this issue for me as well. After 12 hours of rendering with no crashes or errors, I finally did get a crash with the same error. I do seem to be able to render more frames however so I guess that is a plus.
Anyone else have a crash after using this utility to manage the irq's on the gpus?
Rick
I was hoping this would solve this issue for me as well. After 12 hours of rendering with no crashes or errors, I finally did get a crash with the same error. I do seem to be able to render more frames however so I guess that is a plus.
Anyone else have a crash after using this utility to manage the irq's on the gpus?
Rick
try this link please: http://www.mediafire.com/file/2kkkvko7e ... til_v2.zip
(don't forget to run as admin)
(don't forget to run as admin)
- linvanchene
- Posts: 783
- Joined: Mon Mar 25, 2013 10:58 pm
- Location: Switzerland
When I did render with the Message Signaled Interrupts Utility on I did not encounter any DPC_Watchdog errors.
At one time possibly a Windows update removed the checkmarks for the GPUs and then I did encounter DPC errors.
-> My subjective impression is that this utility helps a lot.
- - -
Thank you for reposting. That the original file on GitHub is not available anymore worried me.
Questions:
1) The original utility seemed to be created a few years ago. Is there a risk that windows updates will break it?
2) Is there any chance that Otoy staff can provide their own "official" version of this utility?
- - -
At one time possibly a Windows update removed the checkmarks for the GPUs and then I did encounter DPC errors.
-> My subjective impression is that this utility helps a lot.
- - -
Thank you for reposting. That the original file on GitHub is not available anymore worried me.
Questions:
1) The original utility seemed to be created a few years ago. Is there a risk that windows updates will break it?
2) Is there any chance that Otoy staff can provide their own "official" version of this utility?
- - -
Win 10 Pro 64bit | Rendering: 2 x ASUS GeForce RTX 2080 Ti TURBO | Asus RTX NVLink Bridge 4-Slot | Intel Core i7 5820K | ASUS X99-E WS| 64 GB RAM
FAQ: OctaneRender for DAZ Studio - FAQ link collection
FAQ: OctaneRender for DAZ Studio - FAQ link collection
Utility does work, but does not solve problem 100%. PLX/Driver issue is know by NVIDIA and they seem to be working on this - how much of a priority is that for them that's another question. X99 boards will eventually be phased out and new ones are going to come. Some users reported that x299, even those that do have PLX chips have less bsods of similar fashion compared to x99 equipped with PLX.linvanchene wrote: 1) The original utility seemed to be created a few years ago. Is there a risk that windows updates will break it?
2) Is there any chance that Otoy staff can provide their own "official" version of this utility?
I'm not sure it's OTOY's issue to make sure that Your hardware works in combination with drivers, however I guess company can help white listing certain systems that do tend to have less issues (for now) based on feedback from community and internal testing. However OTOY can not guarantee for other hardware/software vendors providing parts and drivers that their solution will be perfect.