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

87 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-01-17T06:45:50+00:00

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-17T16:38:00+00:00

    You're welcome for the help.

    The memory.dmp seems to indicate the issue is solely with the NVIDIA graphics driver.

     From here:

    "faulty driver code that under certain conditions, does not complete its work within the allotted time frame"

    The "certain conditions" may be the Operating System (Fall Creators Update), motherboard, etc.

    Can you provide the following information which may help determine any issue(s):

    Windows Key + R > type eventvwr in the "Open" box > OK > expand "Custom Views" and then right-click "Administrative Events" > select "Save all events in Custom View As" and save as an .evtx file

    Then make the resulting .evtx file available via Google Drive.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-26T09:18:28+00:00

    Hi Vinsend, did you end up fixing that issue? I've got a similar set up, with 4 gtx 780, and same issue.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-26T09:26:01+00:00

    Hi,

    Not really. I ended up circumventing the problem by disabling one of the 1080ti's in Device Manager. Machine now runs without problems.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-03-02T11:57:25+00:00

    Hi,

    Not really. I ended up circumventing the problem by disabling one of the 1080ti's in Device Manager. Machine now runs without problems. 

    I've also experienced the same problem. I tested with 2 different, brand new ASUS X99-E WS motherboards. No difference.

    Then, I moved to ASRock X99 WS motherboard and the problem was "magically" solved.

    Later, I upgraded to ASUS WS X299 SAGE, for the faster CPU and more PCI-lanes, I got back to the same problematic situation!

    What is common in the problematic configurations are: 1) ASUS, 2) motherboards with PLX chips.

    Are there people who use 4x1080Ti GPUs on the particular ASUS Workstation motherboards and do not suffer from the DPC_WATCHDOGP_VIOLATION issue?

    If this is a common issue, I'm surprised Microsoft, NVIDIA and ASUS have not yet figured out what's going wrong.

    Was this answer helpful?

    0 comments