Question New build randomly freezes and then crashes ?

Feb 3, 2024
4
0
10
Specs:
Mobo: Asus TUF Gaming Z790-Plus
CPU: Intel 14700K
GPU: GeForce RTX™ 4070 Ti SUPER 16G VENTUS 3X OC
RAM: 2x 16 GB Corsair ddr5 6400mhz
PSU: BeQuiet 1000W Platinum
OS: Windows 11 Pro


I built this PC about a week ago and everything seemed to be running fine until it wasn't. I've been getting very random screen freezing and then windows crashing right after. Doesn't matter what I'm doing, whether I be in a game or just simply in the browser, it will crash randomly. A dmp file is generated if I wait long enough.


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: fffff8001831d340, 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: 281

Key : Analysis.Elapsed.mSec
Value: 1569

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x133

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: 0x133_ISR_nvlddmkm!unknown_function

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


BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8001831d340

BUGCHECK_P4: 0

FILE_IN_CAB: 020324-10593-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8001`a7307c88 fffff800`17812bb9 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`1831d340 : nt!KeBugCheckEx
ffff8001`a7307c90 fffff800`17812421 : 00004c10`1a9d6023 00000000`0017e332 00000000`0017e331 00000000`00000000 : nt!KeAccumulateTicks+0x239
ffff8001`a7307cf0 fffff800`178104b1 : 00000000`00000000 ffff8001`ac5bfe00 ffff8001`a72ed180 00000000`00000000 : nt!KiUpdateRunTime+0xd1
ffff8001`a7307ea0 fffff800`1780feda : fffff800`1825ff98 ffff8001`ac5bfe70 ffff8001`ac5bfe70 00000000`00000002 : nt!KeClockInterruptNotify+0xc1
ffff8001`a7307f40 fffff800`17924b2c : 00000038`f3dcd493 ffffdc87`89769fe0 ffffdc87`8976a090 ffffdc87`97c69c18 : nt!HalpTimerClockInterrupt+0x10a
ffff8001`a7307f70 fffff800`17a18cba : fffffb04`d12d6b60 ffffdc87`89769fe0 ffffdc87`97c69bf8 ffffdc87`97c69bf8 : nt!KiCallInterruptServiceRoutine+0x9c
ffff8001`a7307fb0 fffff800`17a19567 : 00000000`00000000 00000000`00000001 ffffdc87`97c69000 fffff800`495c7042 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffb04`d12d6ae0 fffff800`48dde0c4 : ffffdc87`00000000 00000000`00000000 00000000`000001d0 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffb04`d12d6c70 ffffdc87`00000000 : 00000000`00000000 00000000`000001d0 00000000`00000000 00000000`000001d0 : nvlddmkm+0xbe0c4
fffffb04`d12d6c78 00000000`00000000 : 00000000`000001d0 00000000`00000000 00000000`000001d0 fffff800`48e0d779 : 0xffffdc87`00000000


SYMBOL_NAME: nvlddmkm+be0c4

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: be0c4

FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner

I've tried reinstalling windows, going through all my drivers, remounting, and I'm not really sure what else to try. Given the dump, it seems to be nvidia drivers, but I have nothing else to rollback to because it's a 4070 ti super. Updated bios for MOBO and GPU. Stress tests don't cause it to freeze or crash, it's very random and sporadic. Could be fine for 5 hours and then freeze, or freeze after 5 minutes.

Looking for some sort of idea as to what to try next?
Is it possibly some sort of defective hardware, I'm completely lost now.
 
i believe it has happened with XMP disabled
Possibly could reduce your ram speed to 6000 see if it makes it more stable ?
I attempted to reduce ram speed to 5400 and it once again froze.

Do you have any other suggestions? I’d ram the likely culprit? Anyway to narrow it down?
 
Since you have an Intel 14700K, that has onboard graphics, you could, as a test, remove the GeForce RTX 4070 Ti SUPER and run the pc for a few hours and if its still unstable, then its not the GPU.
So, it could be the PSU with an unstable power delivery. Can you borrow a PSU and re-test ?
 
  • Like
Reactions: 35below0
Since you have an Intel 14700K, that has onboard graphics, you could, as a test, remove the GeForce RTX 4070 Ti SUPER and run the pc for a few hours and if its still unstable, then its not the GPU.
So, it could be the PSU with an unstable power delivery. Can you borrow a PSU and re-test ?
I'll give this a go and see what happens.
What's the exact partnumber of the RAM?
Corsair CMH32GX5M2B6400C32
Is the BIOS fully up to date?
Yes, version 1611
Which model exactly? be quiet! has several 1000w Platinum units.

be quiet! BN516 Straight Power 12-1000w 80 Plus Platinum, ATX 3.0

 
Since you have an Intel 14700K, that has onboard graphics, you could, as a test, remove the GeForce RTX 4070 Ti SUPER and run the pc for a few hours and if its still unstable, then its not the GPU.
So, it could be the PSU with an unstable power delivery. Can you borrow a PSU and re-test ?
Currently going on over 11 hours of no freezing or crashing on the CPU graphics. Assuming this means it's either PSU, GPU power cable, or the GPU itself?

Should I return GPU and wait for another one? Will attempt to scavenge up another GPU power cable and test that as well.
 
As the GPU is currently out of the PC you could consider using the DDU "display driver uninstaller" utility (as recommended by Toms) to thoroughly clean out the nVidia drivers, then once done, reinstall the GPU and drivers and see if it helps.
Read their artical here, but I have never used it so cannot directly recommend it. Do some research....
https://www.tomshardware.com/how-to/uninstall-nvidia-amd-intel-gpu-drivers