BSOD Watchdog Violation 1x133 (possible nVidia)


  1. Posts : 4
    Windows 10
       #1

    BSOD Watchdog Violation 1x133 (possible nVidia)


    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/q...7mueWTEVccxFlD





    Any help or insight on this issue would be greatly appreciated, as this issue now causes great delays in my client's workflow.
    Last edited by vinsend; 16 Jan 2018 at 08:27.
      My Computer


  2. Posts : 14,897
    Windows 10 Pro
       #2

    EDIT: it appears driver verifier caused each of the crashes, what was the reason for using driver verifier?
      My Computers


  3. Posts : 4
    Windows 10
    Thread Starter
       #3

    axe0 said:
    EDIT: it appears driver verifier caused each of the crashes, what was the reason for using driver verifier?
    Driver Verifier was installed to try and troubleshoot the issue, because it seems to be caused by a driver. The BSOD's also occurred prior to installing Driver Verifier.

    I have disabled Driver Verifier and will test again, thanks.


    EDIT: Got a crash again. New report is enclosed.
    Last edited by vinsend; 16 Jan 2018 at 13:37.
      My Computer


  4. Posts : 14,897
    Windows 10 Pro
       #4

    The nvidia driver is being blamed, there have been a few updates released which you could try.
      My Computers


  5. Posts : 4
    Windows 10
    Thread Starter
       #5

    axe0 said:
    The nvidia driver is being blamed, there have been a few updates released which you could try.
    Thanks. I have completely removed the drivers using DDU and did a clean install of 390.65. Unfortunately, shortly there after I got a crash again.

    The new DM log is attached: Attachment 172943

    And here is the full MEMORY.DMP in .7z format:
    0117MEMORY.7z - Google Drive
      My Computer


  6. Posts : 14,897
    Windows 10 Pro
       #6

    Memory dump is no use, can't debug the dump completely due to lack of specific information, that I always see with this specific kind of dumps, which I assume is private.

    The next step is to find out which GPU it is about.
      My Computers


  7. Posts : 4
    Windows 10
    Thread Starter
       #7

    axe0 said:
    Memory dump is no use, can't debug the dump completely due to lack of specific information, that I always see with this specific kind of dumps, which I assume is private.

    The next step is to find out which GPU it is about.
    Ok, thanks.

    Do you have a suggestion how to find out which GPU it is? Problem is they are all connected on one water cooling block, so it is hard to take them out one by one.

    Does it suffice to disable them in Device Manager?
      My Computer


  8. Posts : 14,897
    Windows 10 Pro
       #8

    It should suffice to disable them.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 08:23.
Find Us




Windows 10 Forums