BoD (DPC_WATCHDOG_VIOLATION / VIDEO_TDR_FAILURE) due to graphics driver or faulty hardware?

Hi Miguel,

sorry that it took me so long (a lot to do at work).

I did run FurMark expecting it to instantly crash but it did not. I tested with different setting and let it run for 20 minutes. No crash, no errors, and no issues. Everything stable and temperature caps out at around 84° C.

I did take a look at the even manager around the times it crashed in the past. There is nothing significant predating the system crashes.

I did run the Driver Verifier as you instructed and it did already crash on the restart with a DRIVER_VERIFIER_DETECTED_VIOLATION (c4).

See the memory dump file here: https://1drv.ms/u/s!Ap66x80gdX2BlckQjiZYe1Fz8ZFUWQ?e=TdhMb7

See the full output here:

2: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

A device driver attempting to corrupt the system has been caught.  This is

because the driver was specified in the registry as being suspect (by the

administrator) and the kernel has enabled substantial checking of this driver.

If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will

be among the most commonly seen crashes.

Arguments:

Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)

Arg2: fffff808acfc38c4, The address in the driver's code where the error was detected.

Arg3: 0000000000000000, Pool Type.

Arg4: 0000000053694558, Pool Tag (if provided).

Debugging Details:

---

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec

    Value: 5015

    Key  : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on SPEN-PC

    Key  : Analysis.DebugData

    Value: CreateObject

    Key  : Analysis.DebugModel

    Value: CreateObject

    Key  : Analysis.Elapsed.mSec

    Value: 5350

    Key  : Analysis.Memory.CommitPeak.Mb

    Value: 78

    Key  : Analysis.System

    Value: CreateObject

    Key  : WER.OS.Branch

    Value: vb_release

    Key  : WER.OS.Timestamp

    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version

    Value: 10.0.19041.1

ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  c4

BUGCHECK_P1: 2000

BUGCHECK_P2: fffff808acfc38c4

BUGCHECK_P3: 0

BUGCHECK_P4: 53694558

BLACKBOXNTFS: 1 (!blackboxntfs)

PROCESS_NAME:  System

LOCK_ADDRESS:  fffff8034f64fc80 -- (!locks fffff8034f64fc80)

Resource @ nt!PiEngineLock (0xfffff8034f64fc80)    Exclusively owned

     Threads: ffffaf8708ec8040-01<*> 

1 total locks

PNP_TRIAGE_DATA: 

Lock address  : 0xfffff8034f64fc80

Thread Count  : 1

Thread address: 0xffffaf8708ec8040

Thread wait   : 0x427

STACK_TEXT:  

ffffdd8e7eb2c3e8 fffff8034f3d8e34     : 00000000000000c4 0000000000002000 fffff808acfc38c4 0000000000000000 : nt!KeBugCheckEx

ffffdd8e7eb2c3f0 fffff8034efa67b5     : fffff8034f61dc2c 0000000000002000 fffff808acfc38c4 0000000000000000 : nt!VerifierBugCheckIfAppropriate+0xe0

ffffdd8e7eb2c430 fffff8034f3cfdf4     : 0000000053694558 fffff8034f61dc2c fffff808acfc38c4 0000000000000000 : nt!VfReportIssueWithOptions+0x101

ffffdd8e7eb2c480 fffff8034f3dcff2     : 0000000000000000 ffffaf8708ee3060 0000000000000026 00000000000000c0 : nt!VfCheckPoolType+0x90

ffffdd8e7eb2c4c0 fffff808acfc38c4     : 0000000000000220 0000000000000000 00000000000000a0 fffff8034f3bc094 : nt!VerifierExAllocatePoolWithTag+0x62

ffffdd8e7eb2c510 fffff8034ffec2ca     : ffffaf8708619f70 ffffaf8708ee3060 ffffaf870c4aa910 ffffaf870c4aaa60 : SiUSBXp+0x38c4

ffffdd8e7eb2c670 fffff8034ed75b67     : fffff8034ffec190 0000000000000004 ffffaf8708ee3060 0000000000000000 : VerifierExt!xdv_AddDevice_wrapper+0x13a

ffffdd8e7eb2c6d0 fffff8034f12703c     : ffffaf870c8e9e10 ffffaf8708bf8690 0000000000000003 ffffaf870873ab00 : nt!PpvUtilCallAddDevice+0x3b

ffffdd8e7eb2c710 fffff8034f12a82f     : 0000000000000003 0000000000000000 000000006e657050 fffff80300000000 : nt!PnpCallAddDevice+0x94

ffffdd8e7eb2c7d0 fffff8034f129bb7     : ffffaf870c495aa0 ffffdd8e7eb2ca11 ffffaf870c495aa0 0000000000000000 : nt!PipCallDriverAddDevice+0x827

ffffdd8e7eb2c990 fffff8034f14c1d4     : ffffaf870c8c5100 fffff8034ece6101 ffffdd8e7eb2cab0 fffff80300000002 : nt!PipProcessDevNodeTree+0x333

ffffdd8e7eb2ca60 fffff8034ed7b7f6     : 0000000100000003 ffffaf870873abe0 ffffaf870c8c5150 ffffaf870c8c5150 : nt!PiProcessReenumeration+0x88

ffffdd8e7eb2cab0 fffff8034ed0e4b5     : ffffaf8708ec8040 ffffaf8703890a00 fffff8034f64e4e0 ffffaf8700000000 : nt!PnpDeviceActionWorker+0x206

ffffdd8e7eb2cb70 fffff8034ecad9a5     : ffffaf8708ec8040 0000000000000080 ffffaf87038c5040 00078405b19bbdff : nt!ExpWorkerThread+0x105

ffffdd8e7eb2cc10 fffff8034ee07868     : ffff8a8001bda180 ffffaf8708ec8040 fffff8034ecad950 3b3b3b3b3b3b3b3b : nt!PspSystemThreadStartup+0x55

ffffdd8e7eb2cc60 0000000000000000     : ffffdd8e7eb2d000 ffffdd8e7eb27000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME:  SiUSBXp+38c4

MODULE_NAME: SiUSBXp

IMAGE_NAME:  SiUSBXp.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  38c4

FAILURE_BUCKET_ID:  0xc4_2000_VRF_SiUSBXp!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {628948ff-6ca9-cb58-bf7a-4538f8f264d3}

Followup:     MachineOwner

---

2: kd> !verifier

Verify Flags Level 0x03bbedbb

  STANDARD FLAGS:

    [X] (0x00000000) Automatic Checks

    [X] (0x00000001) Special pool

    [X] (0x00000002) Force IRQL checking

    [X] (0x00000008) Pool tracking

    [X] (0x00000010) I/O verification

    [X] (0x00000020) Deadlock detection

    [X] (0x00000080) DMA checking

    [X] (0x00000100) Security checks

    [X] (0x00000800) Miscellaneous checks

    [X] (0x00020000) DDI compliance checking

  ADDITIONAL FLAGS:

    [ ] (0x00000004) Randomized low resources simulation

    [ ] (0x00000200) Force pending I/O requests

    [X] (0x00000400) IRP logging

    [X] (0x00002000) Invariant MDL checking for stack

    [X] (0x00004000) Invariant MDL checking for driver

    [X] (0x00008000) Power framework delay fuzzing

    [X] (0x00010000) Port/miniport interface checking

    [ ] (0x00040000) Systematic low resources simulation

    [X] (0x00080000) DDI compliance checking (additional)

    [X] (0x00200000) NDIS/WIFI verification

    [X] (0x00800000) Kernel synchronization delay fuzzing

    [X] (0x01000000) VM switch verification

    [X] (0x02000000) Code integrity checks

  RESERVED FLAGS (use of these flags is unsupported):

    [X] (0x00100000) Unused or reserved flag

    [X] Indicates flag is enabled

Summary of All Verifier Statistics

  RaiseIrqls           0x18

  AcquireSpinLocks     0xee09

  Synch Executions     0x0

  Trims                0x15e

  Pool Allocations Attempted             0x23ab

  Pool Allocations Succeeded             0x23ab

  Pool Allocations Succeeded SpecialPool 0x23ab

  Pool Allocations With NO TAG           0x0

  Pool Allocations Failed                0x0

  Current paged pool allocations         0x13 for 000026BA bytes

  Peak paged pool allocations            0x13 for 000026BA bytes

  Current nonpaged pool allocations      0x8f for 0021E332 bytes

  Peak nonpaged pool allocations         0x90 for 0021E71A bytes

  Execute pool type count                0x0

  Execute page protection count          0x0

  Execute page mapping count             0x0

  Execute-Write section count            0x0

  Section alignment failures             0x0

  IAT Executable Section failures:       0x0

It seems to have some problem with this SiUSBXp thing which seems to be part of the Nvidia driver if I'm not mistaken. A quick google search did not bring anything up on how to update this part (or anything else). I have no clue what it is and what it does.

See the memory dump file here: https://1drv.ms/u/s!Ap66x80gdX2BlckQjiZYe1Fz8ZFUWQ?e=TdhMb7

I'm not sure what to make of that. So does that mean the GPU is fine but there is some problem with the Nvidia driver?

Hi Miguel,

sorry that I questioned you.

I will take a look at the even manager tomorrow and will come back to you when I find something.

I will also check with the Driver Verifier.

The issue does happen very frequently (multiple times a session) but it is not clearly reproduceable.

I initially thought it had something to do with the network driver since it often happens when I'm loading webpages.

It happens most frequently when a YouTube video is running in a tab while I'm performing other stuff. If often crashed while opening a new tab in Edge.

I guess that stress testing the GPU e.g. with FurMark will also trigger a crash. I can test that. Might be good to have a consistent reproduction.

I wonder how I could differentiate between hardware failure and driver issues?

If it is a hardware failure then it is what it is but I wouldn't like to declare my GPU as dead while it is just some software problem with the hardware being fine.

Hey there Spen!

Trust me, I did read your post and I gave you instructions to a proper driver reinstallation and I gave you the steps that NVIDIA itself gave for this issue. We are not NVIDIA experts, and I think you've taken all the right steps that should be taken. Drivers uninstall, reinstall and update, BIOS update, Windows update, OS reinstallation... If these all don't work, it must be a hardware issue or incompatibility.

The Event Manager can give information on what exactly happened to cause the issue.

To see if it's a driver issue, can you run Driver Verifier? Follow these steps:

1. Make sure you have a Restore Point created before running these steps.
2. Type 'verifier' in the Windows search menu.
3. Select "Create custom settings (for code developers)" and click "Next"
4. Select "Select individual settings from a full list" and click "Next"
5. Select everything except for "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next".
6. Select "Select driver names from a list" and click "Next"
7. Then select all drivers NOT provided by Microsoft and click "Next"
8. Select "Finish" on the next page.
9. Reboot your system and use it as you normally do.

This will show if the issue actually resides on the NVIDIA driver, any other, or if it's a hardware issue.

Let's see if this gives any other clue. You've done a proper troubleshooting process, so if this doesn't give any other clue we may be in trouble.

Being a Windows Insider, I don't think it should do any problem if the problem didn't start after an Insider update. Try to rollback NVIDIA's driver to other versions, not just one, and see if there's an appropiate one among all of them.

Have you noticed this problem to happen after any procedure, or just randomly?

I'll be here waiting for you.

Miguel Ángel :)

Hi Miguel,

I don't feel you did actually read my post. I still want to give some additional information based on your reply:

• The GPU is close to reference design and is water cooled.
• The GPU is not and never was overclocked.
• The GPU is running in its default configuration.
• The GPU core temperature is 40-60° C and should be fine.
• The power supply is a very good one which supports min. 3 times the power output then needed. It should be very stable. There is also no power loss behavior (like instantly turning off).
• As written in my original post, I already installed the NVIDIA drivers clean and correctly.
• I have no special programs running in the background.
• I have no additional task management or optimization tools running.
• I have no system monitoring tools running
• I have no overclocking tools running
• No hardware overclocking is active
• I have no additional virus scanner besides the Microsoft one
• The installed drivers as described in my original post are official drivers from NVIDIAs site.
• I already used the custom install option to only install the drivers
• My Windows is up-to-date and as I mentioned I'm also ahead (insider program) - the version I have is also in my original post.

I don't know what running FurMark should tell me. It will crash with a BoD and then? It is already crashing even without FurMark so running FurMark will not add any information.

I will look into the even manager. Not sure what the event manager should tell me in addition to what the momory dumps already tell me?

The links are just the Nvidia support pages and so on. So are you saying I should contact them instead of asking for help here?

Hi there Spen!

Updated drivers shouldn't give any problem at all. If they do, there must be a problem. I've checked over NVIDIA's forums and they have given these solutions:

1. Reboot and install the driver from Intel first, reboot and install the NVIDIA driver.
2. Shut down any un-necessary programs in the background.
3. If your GPU is overlocked set it back to the factory clocks.
4. Shut down any and all system monitoring programs and any overlooking tools you might have.
5. Shut down your virus scanner.
6. nstall the driver only from the .exe downloaded from https://www.nvidia.com/Download/index.aspx?lang..., don't use GeForce experience.
7. Use the custom installation and only install the components you need (don't deselect components you need, the installation program will deinstall them if you do)
8. Always perform a clean installation. (if you have profiles for games, back them up using "NVIDIA inspector")

These are taken directly from NVIDIA forums. Please, it's important that you deinstall any program related to NVIDIA to do a clean install.

Run Windows Update as well, remember it's what may solve our problem as well!

Check as well the Event Viewer. See if there's any critical error in the time of the BSOD. It may help us as well.

If these don't work, we'll run FurMark to stress the GPU. It seems it could be as well a hardware issue.

You may as well check over the NVIDIA forums and even NVIDIA support in these links:

https://www.nvidia.com/en-us/support/

https://www.nvidia.com/en-us/about-nvidia/commu...

Drivers: https://www.nvidia.com/en-us/geforce/drivers/

Let me know how it goes!

Miguel Ángel :)

---

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.