Question PC freezing and restarting on its own

[shreyas31]

PC Specs -
Ryzen 5 3600
16GB DDR4
GTX 1650
GIGABYTE B450M - H
Corsair 550W

Below is the MEMORY.DMP file
Running current GPU drivers
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: fffff8055e0fb320, 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: 4093

Key : Analysis.Elapsed.mSec
Value: 4167

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

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

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

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

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

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

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: 1

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: 1

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: 16908288

Key : Hypervisor.Flags.ValueHex
Value: 1020000

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: fffff8055e0fb320

BUGCHECK_P4: 0

FILE_IN_CAB: MEMORY.DMP

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: fffff80560e9e650 -- (.trap 0xfffff80560e9e650)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffe7056eafee02
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8055d61e76b rsp=fffff80560e9e7e0 rbp=fffff80560e9e970
r8=0000000000000000 r9=0000000000000000 r10=fffff8057cc0d1c0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KzLowerIrql+0x1b:
fffff805`5d61e76b 4883c420 add rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: RainbowSix.exe

STACK_TEXT:
fffff805`60ea5c88 fffff805`5d843814 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`5e0fb320 : nt!KeBugCheckEx
fffff805`60ea5c90 fffff805`5d686e3d : 000005ea`74295d01 fffff805`59077180 00000000`00000246 00000000`0003f288 : nt!KeAccumulateTicks+0x1bfbf4
fffff805`60ea5cf0 fffff805`5d67dec1 : 00000000`0003f287 00000000`00025a52 fffff805`59077180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff805`60ea5d40 fffff805`5d681253 : fffff805`59077180 00000000`00000000 fffff805`5e031558 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff805`60ea5e80 fffff805`5d688ae2 : fffff805`60e9e650 fffff805`60e9e6d0 fffff805`60e9e600 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff805`60ea5f30 fffff805`5d73e965 : 00000009`6af14453 fffff805`5e0f3a60 fffff805`5e0f3b10 ffff5ea6`df2abf31 : nt!HalpTimerClockInterrupt+0xe2
fffff805`60ea5f60 fffff805`5d7fdc3a : fffff805`60e9e6d0 fffff805`5e0f3a60 fffff805`60e9e970 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff805`60ea5fb0 fffff805`5d7fe407 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff805`60e9e650 fffff805`5d61e76b : ffffe705`770b8000 00000000`00000000 ffffe705`771ba000 ffffe705`770b8000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff805`60e9e7e0 fffff805`7bffd77f : fffff805`60e9e970 00000000`00000000 fffff805`60e9e970 fffff805`5d67f681 : nt!KzLowerIrql+0x1b
fffff805`60e9e810 fffff805`7bfff097 : ffffe705`770b8000 ffffe705`771ba000 ffff82e1`84d258cb ffffe705`771ba000 : nvlddmkm+0xad77f
fffff805`60e9e840 fffff805`7bfebe34 : ffffe705`770b8000 ffffe705`771ba000 ffffe705`770b8000 ffffe705`771ba000 : nvlddmkm+0xaf097
fffff805`60e9e870 fffff805`5d68b57e : fffff805`5907a240 ffffe705`6d053000 fffff805`60e9eef0 fffff805`59077180 : nvlddmkm+0x9be34
fffff805`60e9ebb0 fffff805`5d68a864 : fffff805`59077180 00000000`00000000 00000000`00000008 00000000`00024887 : nt!KiExecuteAllDpcs+0x30e
fffff805`60e9ed20 fffff805`5d804195 : 00000000`00000000 fffff805`59077180 ffffb781`a6afe140 ffffe705`7877c2c0 : nt!KiRetireDpcList+0x1f4
fffff805`60e9efb0 fffff805`5d803f80 : fffff805`5d7f7d70 fffff805`5d6f5f5a 00000000`00000218 ffffe705`6c010340 : nt!KxRetireDpcList+0x5
ffffd484`aeb9f400 fffff805`5d803705 : ffffe705`7877c2c0 fffff805`5d7fdd01 00000000`000616d2 ffffe705`6c012640 : nt!KiDispatchInterruptContinue
ffffd484`aeb9f430 fffff805`5d7fdd01 : 00000000`000616d2 ffffe705`6c012640 ffffe705`6c012880 01000000`000000f0 : nt!KiDpcInterruptBypass+0x25
ffffd484`aeb9f440 fffff805`5d60a6f8 : ffffd484`aeb9f6d0 00000000`00000218 ffffe705`7797ede0 00000000`00000000 : nt!KiInterruptDispatch+0xb1
ffffd484`aeb9f5d0 fffff805`6df9c0f7 : ffffe705`7c179005 ffffd484`aeb9f6d0 ffffe705`50646641 00000000`00000000 : nt!ExAllocatePoolWithQuotaTag+0x1c8
ffffd484`aeb9f650 fffff805`6df9b892 : 00000000`0000020c ffffd484`aeb9f6d0 00000000`00000080 00000000`00000000 : afd!AfdPollGetInfo+0x27
ffffd484`aeb9f690 fffff805`6df9b79b : 00000001`ffffff00 ffffe705`7797ef88 00000000`00000000 fffff805`5da11b31 : afd!AfdPoll64+0xde
ffffd484`aeb9f7a0 fffff805`6df9b22c : ffffe705`7797ef88 00000000`00000000 00000000`0000020c 00000000`00000000 : afd!AfdPoll+0x2b
ffffd484`aeb9f7d0 fffff805`5d611385 : 00000000`00000002 00000000`00000000 ffffd484`20206f49 00000000`00000030 : afd!AfdDispatchDeviceControl+0x7c
ffffd484`aeb9f800 fffff805`5da10b1c : 00000000`00000002 00000000`00000000 ffffe705`7e469c80 ffffe705`7877c2c0 : nt!IofCallDriver+0x55
ffffd484`aeb9f840 fffff805`5da10771 : ffffe705`7797ef88 ffffd484`aeb9fb80 00000000`00000005 ffffe705`7797ef88 : nt!IopSynchronousServiceTail+0x34c
ffffd484`aeb9f8e0 fffff805`5da0fae6 : 0003d486`00000000 00000000`00001994 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xc71
ffffd484`aeb9fa20 fffff805`5d80f4f8 : 0000020c`8cfa80c8 0000020c`d7a802b0 ffffe705`6bec69a0 ffffb781`a5ccf180 : nt!NtDeviceIoControlFile+0x56
ffffd484`aeb9fa90 00007fff`b784d144 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000012`3b9bed58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`b784d144


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

 

[Anziaty]

I had a similar problem, cleaning helped

 

[shreyas31]

I had a similar problem, cleaning helped

way back in time i reseated my gpu and cleaned the slots and fans which made the problem disappear for a few months but its back now . im feeling its a power supply issue

 

[shreyas31]

Then, I'd use HWinfo, to log as I used the hardware, check for voltage problems, etc...

id run the logging in the bg right?

 

[shreyas31]

There is a program called "why so slow" and "who crashed"... I'd give those a go. They're both free if I remember right.

i'd give these a try thanks

 

[The Anti-Chadite]

id run the logging in the bg right?

Yeah, mainly you wanna just watch the 12v rails, if they drop below 12 or something, that's usually a fairly decent indicator it's your PSU's problem. ...but it's one of many ways to determine a problem.

 

[shreyas31]

Yeah, mainly you wanna just watch the 12v rails, if they drop below 12 or something, that's usually a fairly decent indicator it's your PSU's problem. ...but it's one of many ways to determine a problem.

ok ill report back once it happens again

 

[shreyas31]

There is a program called "why so slow" and "who crashed"... I'd give those a go. They're both free if I remember right.

WhoCrashed returned this after analyzing my last dump file -

Crash dump file:	C:\Windows\MEMORY.DMP (Kernel memory dump)
Bugcheck code:	0x133(0x1, 0x1E00, 0xFFFFF8055E0FB320, 0x0)
Bugcheck name:	DPC_WATCHDOG_VIOLATION
Driver or module in which error occurred:	amdppm.sys (amdppm+0x2fa7)
File path:	C:\Windows\System32\drivers\amdppm.sys
Description:	Processor Device Driver
Product:	Microsoft® Windows® Operating System
Company:	Microsoft Corporation
Bug check description:	The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
Analysis:	This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.

 

[lojikal]

Are you using a stock or aftermarket CPU Cooler?

 

[shreyas31]

Are you using a stock or aftermarket CPU Cooler?

stock. is it really a thermal issue? fans are cleaned and no overclocking done . system is 3 years old

 

[The Anti-Chadite]

There's a program called SDI or "Snappy Driver Installer" I'd go grab it, download the indexes and then your machines driver specifically. Run it, reboot then lemme know. ...wouldn't hurt to stop by Majorgeeks and grab the C++ runtimes AIO and the DX Installer, just because they're free and why not.

 

[lojikal]

stock. is it really a thermal issue? fans are cleaned and no overclocking done . system is 3 years old

In addition to the possibility of a faulty PSU. An overheating CPU will cause your PC to freeze and reset. Just something you could additionally check to rule out.

 

[shreyas31]

There's a program called SDI or "Snappy Driver Installer" I'd go grab it, download the indexes and then your machines driver specifically. Run it, reboot then lemme know. ...wouldn't hurt to stop by Majorgeeks and grab the C++ runtimes AIO and the DX Installer, just because they're free and why not.

i recently did a full fresh windows install in order to rule out any software/driver . It has only happened once after that . i'll try to run these

 

[shreyas31]

In addition to the possibility of a faulty PSU. An overheating CPU will cause your PC to freeze and reset. Just something you could additionally check to rule out.

ill monitor the cpu temps actively with HWInfo while running anything demanding

 

[shreyas31]

There's a program called SDI or "Snappy Driver Installer" I'd go grab it, download the indexes and then your machines driver specifically. Run it, reboot then lemme know. ...wouldn't hurt to stop by Majorgeeks and grab the C++ runtimes AIO and the DX Installer, just because they're free and why not.

ran SDI, installed drivers and rebooted .

 

[shreyas31]

Yeah, mainly you wanna just watch the 12v rails, if they drop below 12 or something, that's usually a fairly decent indicator it's your PSU's problem. ...but it's one of many ways to determine a problem.

after a small intensive session i saw the 12v rail value goes all the way down at 11.448v

 

[thestryker]

One of your logs shows nvidia driver failure and the other amd which leads me to believe it's unlikely software related (GPU crash and CPU crash respectively). The first two things that come to mind are PSU and motherboard and I'd lean towards the former.

 

[The Anti-Chadite]

after a small intensive session i saw the 12v rail value goes all the way down at 11.448v

So, how goes it? You still having issues?

 

[shreyas31]

So, how goes it? You still having issues?

no crashes since the last one

 

[shreyas31]

One of your logs shows nvidia driver failure and the other amd which leads me to believe it's unlikely software related (GPU crash and CPU crash respectively). The first two things that come to mind are PSU and motherboard and I'd lean towards the former.

yea im suspecting the psu too , ill keep monitoring voltages thanks

 

[shreyas31]

Pretty cool eh? If only more people listened to me...

lets see ill give it a week and report back if it happens again

 

[The Anti-Chadite]

lets see ill give it a week and report back if it happens again

I'm by no means an expert with anything relating to electricity or PSU's but unless someone wants to say I'm wrong, I'd say that the rails dropping below 12v is a good indication you should get a new one.

 

[shreyas31]

I'm by no means an expert with anything relating to electricity or PSU's but unless someone wants to say I'm wrong, I'd say that the rails dropping below 12v is a good indication you should get a new one.

yea for sure but im using software monitoring and arent they usually inaccurate? for testing psu voltages a multimeter would be more accurate

 

[The Anti-Chadite]

yea for sure but im using software monitoring and arent they usually inaccurate? for testing psu voltages a multimeter would be more accurate

Hwinfo is a fairly solid program, I can't remember a time I thought I needed something else because it wouldn't work.

 

[shreyas31]

crashed again. however in the hwinfo log there wasnt significant voltage drop across any rails. also can outdated audio drivers cause this? because im using a 3 year old one because only that version seems to work with realtek audio console