Question Too low of a voltage in GPU 8pin connector? Kernel dump file with error DPC_WATCHDOG_VIOLATION (133)

[potac]

Hello,

During the last week I havent been able to play games (pubg or apex legends), the monitor turns off at random while the pc is still on. I get no signal back from displayport and I need to manually shutdown the machine. Twixe I think there was a BSOD (although I cant see it cause displayport signal is off). The generated kernel dump files showed the following:

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8065f8fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 3858

Key  : Analysis.Elapsed.mSec
Value: 4003

Key  : Analysis.IO.Other.Mb
Value: 0

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 0

Key  : Analysis.Init.CPU.mSec
Value: 593

Key  : Analysis.Init.Elapsed.mSec
Value: 8994

Key  : Analysis.Memory.CommitPeak.Mb
Value: 93

Key  : Bugcheck.Code.KiBugCheckData
Value: 0x133

Key  : Bugcheck.Code.LegacyAPI
Value: 0x133

Key  : Failure.Bucket
Value: 0x133_ISR_nvlddmkm!unknown_function

Key  : Failure.Hash
Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}

Key  : Hypervisor.Enlightenments.Value
Value: 0

Key  : Hypervisor.Enlightenments.ValueHex
Value: 0

Key  : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key  : Hypervisor.Flags.ApicEnlightened
Value: 0

Key  : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key  : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key  : Hypervisor.Flags.CpuManager
Value: 0

Key  : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key  : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key  : Hypervisor.Flags.Epf
Value: 0

Key  : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

Key  : Hypervisor.Flags.HardwareMbecAvailable
Value: 0

Key  : Hypervisor.Flags.MaxBankNumber
Value: 0

Key  : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key  : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key  : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0

Key  : Hypervisor.Flags.Phase0InitDone
Value: 0

Key  : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key  : Hypervisor.Flags.RootScheduler
Value: 0

Key  : Hypervisor.Flags.SynicAvailable
Value: 0

Key  : Hypervisor.Flags.UseQpcBias
Value: 0

Key  : Hypervisor.Flags.Value
Value: 0

Key  : Hypervisor.Flags.ValueHex
Value: 0

Key  : Hypervisor.Flags.VpAssistPage
Value: 0

Key  : Hypervisor.Flags.VsmAvailable
Value: 0

Key  : Hypervisor.RootFlags.AccessStats
Value: 0

Key  : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key  : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key  : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key  : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key  : Hypervisor.RootFlags.IsHyperV
Value: 0

Key  : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key  : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key  : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key  : Hypervisor.RootFlags.Nested
Value: 0

Key  : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key  : Hypervisor.RootFlags.Value
Value: 0

Key  : Hypervisor.RootFlags.ValueHex
Value: 0

Key  : SecureKernel.HalpHvciEnabled
Value: 0

Key  : WER.OS.Branch
Value: vb_release

Key  : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8065f8fb320

BUGCHECK_P4: 0

FILE_IN_CAB:  MEMORY_pubg.DMP

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff806637fb670 -- (.trap 0xfffff806637fb670)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffffa48ba28ffd02
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8065ee430c0 rsp=fffff806637fb808 rbp=fffff806637fb970
r8=0000000000000000  r9=0000000000000000 r10=fffff80689fdd1c0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe cy
nt!KzLowerIrql:
fffff806`5ee430c0 4053            push    rbx
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  TslGame.exe

STACK_TEXT:  
fffff806`63802c88 fffff806`5f037616     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`5f8fb320 : nt!KeBugCheckEx
fffff806`63802c90 fffff806`5ee5945d     : 0000063b`c48d284d fffff806`5b38a180 00000000`00000246 00000000`0001d7aa : nt!KeAccumulateTicks+0x1e13d6
fffff806`63802cf0 fffff806`5ee519b1     : 00000000`0001d7a9 00000000`00011922 fffff806`5b38a180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff806`63802d40 fffff806`5ee53873     : fffff806`5b38a180 00000000`00000000 fffff806`5f831950 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff806`63802e80 fffff806`5ee50a82     : fffff806`637fb670 fffff806`637fb6f0 fffff806`637fb600 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
fffff806`63802f30 fffff806`5ef00825     : 00000004`649f96d9 fffff806`5f8f3a60 fffff806`5f8f3b10 ffffce09`5563cb87 : nt!HalpTimerClockInterrupt+0xe2
fffff806`63802f60 fffff806`5efff65a     : fffff806`637fb6f0 fffff806`5f8f3a60 fffff806`637fb970 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff806`63802fb0 fffff806`5efffe27     : 000003a8`00000000 00001f80`008f0c40 00000000`00000000 00001f80`00fd02c0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff806`637fb670 fffff806`5ee430c0     : fffff806`893cd77f fffff806`637fb970 00000000`00000000 fffff806`637fb970 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff806`637fb808 fffff806`893cd77f     : fffff806`637fb970 00000000`00000000 fffff806`637fb970 fffff806`5ee51ca1 : nt!KzLowerIrql
fffff806`637fb810 fffff806`893cf097     : ffffa48b`a802d000 ffffa48b`a812e000 fffff2dd`21662da4 ffffa48b`a812e000 : nvlddmkm+0xad77f
fffff806`637fb840 fffff806`893bbe34     : ffffa48b`a802d000 ffffa48b`a812e000 ffffa48b`a802d000 ffffa48b`a812e000 : nvlddmkm+0xaf097
fffff806`637fb870 fffff806`5eec166e     : fffff806`5b38d240 ffffa48b`a040f000 fffff806`637fbed0 fffff806`5b38a180 : nvlddmkm+0x9be34
fffff806`637fbbb0 fffff806`5eec0954     : fffff806`5b38a180 00000000`00000000 00000000`00000008 00000000`00010757 : nt!KiExecuteAllDpcs+0x30e
fffff806`637fbd20 fffff806`5f005bb5     : 00000000`00000000 fffff806`5b38a180 ffffc801`62df7b40 00000218`0852d490 : nt!KiRetireDpcList+0x1f4
fffff806`637fbfb0 fffff806`5f0059a0     : fffff806`5eff9770 fffff806`5ef251fa 00007ff7`c9974f60 00000000`00000000 : nt!KxRetireDpcList+0x5
ffffd88b`88bfeac0 fffff806`5f005125     : 00000218`0852d490 fffff806`5efff721 0000001a`56dec490 ffffa48b`00000001 : nt!KiDispatchInterruptContinue
ffffd88b`88bfeaf0 fffff806`5efff721     : 0000001a`56dec490 ffffa48b`00000001 00000000`0000019a ffffd88b`88bfeb80 : nt!KiDpcInterruptBypass+0x25
ffffd88b`88bfeb00 00007ffa`413712de     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0xb1
0000001a`56dec368 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`413712de


SYMBOL_NAME:  nvlddmkm+ad77f

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  ad77f

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

Followup:     MachineOwner

I have tried everything indicated in forums with no avail: reinstall windows, roll back GPU drivers, memcheck, update bios, change PCLIe slot, sfc /scannow etc. It looks like the culprit is nvidia drivers (nvlddmkm.sys).

Therefore I started monitoring some sensor values using OCCT and HWInfo64. In the 8pin PCIe connector of my GPU I am getting too low voltage values I think. I am a noob on this so I would like some guidance. I don't have a physical device to measure voltage, I can only rely on software atm. The big image is reading from OCCT that belongs to my GPU whereas the one-line reading is the +12V from motherboard. These are the values a couple of seconds before the display turned off and had to restart.

https://imgur.com/a/LYsllx1

View: https://imgur.com/a/LYsllx1


Also I have uploaded the HWInfo64 logs here.

What do you get out of this. Does this mean I need a new PSU or maybe PCIe cables? I would like a second opinion. Thanks!

Hardware (All purchased in 2016 except GPU and nvme):
- Asus Z97A motherboard
- Intel core i7 4790
- 16gb ram DDR3
- GeForce RTX 2080 Ti
- 1TB nvme, 1TB SATA, 256GB SSD
- AeroCool Extreme Silence 700W 80 Plus Bronze

 

[Lutfij]

Welcome to the forums, newcomer!

AeroCool Extreme Silence 700W 80 Plus Bronze
Source(borrow, not buy) a donor PSU with a reliably built unit that can deliver 650W of power to the entire system.

 

[potac]

Welcome to the forums, newcomer!

AeroCool Extreme Silence 700W 80 Plus Bronze
Source(borrow, not buy) a donor PSU with a reliably built unit that can deliver 650W of power to the entire system.

Sorry, not sure if I understand. It says 700W but it really only delivers 650?

 

[--SID--]

Does this mean I need a new PSU or maybe PCIe cables?

You definitely need a new PSU because

AeroCool Extreme Silence 700W 80 Plus Bronze

is hot garbage. You don't want to power any GPU with this piece of trash. Very low quality, group regulated, missing essential protections like OCP and OTP.

 

[faalin]

I can tell you right now that the 2080 Ti has very bad power spikes, I was running a EVGA 750w G2 PSU and was having the same issue. I was lucky enough to have a 1600W G2 laying around that i put in and havent had issues since then.

I would recommend a very good 850w, or if your planning on upgrading your system anytime soon a 1000w ATX 3.0

 

[potac]

You definitely need a new PSU because

is hot garbage. You don't want to power any GPU with this piece of trash. Very low quality, group regulated, missing essential protections like OCP and OTP.

I see. Any good recommendations? Should I stay in 700 or go up to 850?

 

[potac]

I can tell you right now that the 2080 Ti has very bad power spikes, I was running a EVGA 750w G2 PSU and was having the same issue. I was lucky enough to have a 1600W G2 laying around that i put in and havent had issues since then.

I would recommend a very good 850w, or if your planning on upgrading your system anytime soon a 1000w ATX 3.0

I didn't know about the power spikes. Which PSU is a decent PSU? Some advice on what to look for or maybe you know some models?

 

[--SID--]

I see. Any good recommendations? Should I stay in 700 or go up to 850?

Depends on the availability in your country. Even a decent 650w is fine but 850w doesn't hurt and it's only about $/€30 more expensive. Take a look here for the best ATX3.0 units https://hwbusters.com/best_picks/best-atx-v3-0-pcie-5-0-ready-psus-picks-2023-hardware-busters/