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

Anonymous
2018-01-16T13:57:39+00:00

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.

Windows for home | Windows 10 | Performance and system failures

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 No comments

87 answers

Sort by: Most helpful
  1. Anonymous
    2018-06-03T11:07:38+00:00

    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 narrowed down the issue to the NVIDIA drivers for Windows 10. It affects specifically the high-end Workstation Motherboards that feature PLX PEX 8747 PCI-E switches from Broadcom, with three or more GTX Pascal GPU cards.

    Whether this is by accident or intentional by NVIDIA I don't know, but I'm very frustrated they've known it and haven't acted for several months. The drivers are broken since last July/August, for 9 months already.

    An old but stable driver is version 382.53 (supports up to CUDA 8.0), from June / July 2017. You can download it directly from NVIDIA. The issue was first introduced in the newer drivers that followed.

    Following lots of pressure, NVIDIA's Tech Support have confirmed they're looking into this and they recently added the issue in the Known Issues section, in the Release Notes of the recently released drivers (May).

    So, I hope this information is helpful to everyone with the aforementioned computer configuration. Use driver 382.53 as a workaround and report your problem to NVIDIA's Tech Support, mentioning the model of your WS motherboard and why you need NVIDIA to address this issue in its latest drivers.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-06-02T22:32:05+00:00

    Looks like flashing my BIOS didn't do the trick, nor did updating the motherboard firmware.  Still BSOD after 1 min when using both GPUs.  Here is my mini dump if anyone can take a look.

    https://drive.google.com/file/d/1u3i1nG71cqZ7lm\_3IocfvKP7oKM72YBP/view?usp=sharing

    For now I'm going to try disabling one card and see if it remains stable.  Only other thing I can think to do now is update Windows to 1803.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-06-02T18:56:28+00:00

    awesome thank you.... dang auto correct.

    so far I disabled one of my cards and I've been rendering for the last hour without a BSOD, which has been a long time since it's stayed stable for that long.  I'll probably try the BIOS update on of my render nodes first and see if that does the trick first before changing anything on this system.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-06-02T18:46:14+00:00

    plus, didn't have to disable instead of did.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-06-02T18:45:05+00:00

    Grrrrr autocorrect, > no bsod

    Was this answer helpful?

    0 comments No comments