Otoy, please pressure Nvidia. X99 mobo BSOD PLX chip bug. Tweet

[joneil]

Hey Guys is there any movement on this?

Getting all the same issues. My computer is in the shop and they have done all these tests and its none of it so it must be this
x99 motherboard problem. Is it worth getting a non PLX chip board? for four cards? will that solve it? also can anyone recommend on that can hold four cards for me?

Thanks

[joneil]

https://forums.geforce.com/default/topi ... ues-help-/

[joneil]

UNBELIEVABLE

they still haven't fixed in the driver that was released yesterday:

http://us.download.nvidia.com/Windows/3 ... -notes.pdf

[Tenth_Old_Man]

HOLY CRAP THIS MAY BE [SOLVED]!

I just got done rendering for hours (instead of minutes then BSOD) with Win10 1803/Nvidia 399.07 and octane 4 without a single crash!
X99-E WS usb 3.1 (Bios 3803, likely not required)
Xeon E51650-V3
256 GB ECC RAM
4 GTX 1080 TI's and misc other I/O cards.

1. Download the Message-Signaled Interrupts Utility v2.0 from github:
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 ones should be stacked together) by clicking each GPU checkbox in the MSI column.
5. Restart your workstation
6. Re-run the tool to to make sure MSI is still enabled

Please report back your results!

TL;DR
As a side note, I re-enabled my Group Policy that disallows ANY new driver or piece of sw from installing or getting recognized on boot up or plug in that is not explicitly allowed. This prevents Windows update from updating drivers without you knowing and killing the MSI attribute and BSOD-ing you again until this is actually implementedtwi.

Thanks to page 6 of this threadfor the discovery!

SPREAD THE NEWS AND HELP THE COMMUNITY. Nvidia will implement this fix in another driver release soon and we won't need to do this, but for now, HECK YAH!

[FAZ]

HOLY CRAP THIS MAY BE [SOLVED]!

I just got done rendering for hours (instead of minutes then BSOD) with Win10 1803/Nvidia 399.07 and octane 4 without a single crash!
X99-E WS usb 3.1 (Bios 3803, likely not required)
Xeon E51650-V3
256 GB ECC RAM
4 GTX 1080 TI's and misc other I/O cards.

1. Download the Message-Signaled Interrupts Utility v2.0 from github:
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 ones should be stacked together) by clicking each GPU checkbox in the MSI column.
5. Restart your workstation
6. Re-run the tool to to make sure MSI is still enabled

Please report back your results!

TL;DR
As a side note, I re-enabled my Group Policy that disallows ANY new driver or piece of sw from installing or getting recognized on boot up or plug in that is not explicitly allowed. This prevents Windows update from updating drivers without you knowing and killing the MSI attribute and BSOD-ing you again until this is actually implementedtwi.

Thanks to page 6 of this threadfor the discovery!

SPREAD THE NEWS AND HELP THE COMMUNITY. Nvidia will implement this fix in another driver release soon and we won't need to do this, but for now, HECK YAH!

Tried this a while back and it worked great for a whole day, then bsod. After that bsod it then resorts to the usual constant bsod. I use the usb 3.1 version of the Asus X99 E ws motherboard. Still working for you?

[Tenth_Old_Man]

I am also using the X99-E WS usb 3.1 mobo under nvidia 398.82 with MSI mode enabled and its rock solid.

One thing to do is to update to that nvidia version, then click on the msi mode, apply button in the upper right, and reboot. Make sure it is still enabled by admin running the tool again for all GPU's after reboot.

You could even try to turn on MSI mode for all devices the tool found as it really is a better interrupt methodology overall, but mileage may vary with certain devices.

Sidenote: I am running without MSI mode now under this driver just to see if it works without the manual mode change, and so far so good with no crashes. 399.XX BSOD's sadly.

[jblessing]

Any updates on this? We recently tried updating an Asus WS x99 usb 3.1 win 8.1 machine to win 10 (because of Adobe!) and have had all of these issues with any nvidia driver we tried. Also updated the mobo BIOS with no luck. Also tried various versions of win 10 with no real success. Prior to win 10, the machine was 100% stable on nvidia 388.71 drivers in win 8.1. Now it's unusable if more than 1 GPU is enabled in Octane. The MSI utility just makes the crash take down Octane instead of BSOD the whole machine.

[paride4331]

Any updates on this? We recently tried updating an Asus WS x99 usb 3.1 win 8.1 machine to win 10 (because of Adobe!) and have had all of these issues with any nvidia driver we tried. Also updated the mobo BIOS with no luck. Also tried various versions of win 10 with no real success. Prior to win 10, the machine was 100% stable on nvidia 388.71 drivers in win 8.1. Now it's unusable if more than 1 GPU is enabled in Octane. The MSI utility just makes the crash take down Octane instead of BSOD the whole machine.

Hi jblessing,
Did you try this? many user I know solved that issue with this:
https://render.otoy.com/forum/viewtopic.php?f=9&t=67801&p=348427#p344997
Regards
Paride

[jblessing]

Yes, that is what stopped the BSOD, but Octane still crashes.

[paride4331]

Yes, that is what stopped the BSOD, but Octane still crashes.

Hi jblessing,
try with Nvidia 391.35 using [DDU unistaller](https://www.guru3d.com/files-details/di ... nload.html)
Regards
Paride