Question Computer Crashes Every Single Time After Start Up

[ehodg]

Thank you in advance for any advice... I have been trying to diagnose this issue for close to 2 years. This is a tough one...

The ONLY issue I have with my computer is it will hard crash not long after I start it up. Once it crashes, it won't crash again as long as I keep the computer running. If I turn it off for the night and start it back up the next day it will crash once again. If I play any game after startup it seems to crash sooner. If I left my computer on 24/7 I wouldn't have an issue, but I would like to avoid that.

I completely reinstalled windows thinking that would help, oddly enough it changed the crash from a hard freeze lock-up where I would have to manually restart to now hard freezing and restarting on it's own. I tried with Windows Support but had to give up - after hours of troubleshooting and talking to multiple people, none of them could figure it out.

I have stress tested my CPU, GPU, RAM, etc and found no issues/errors. I always update my drivers and OS.

Custom Built PC
CPU: Intel Core i7-6800K CPU @ 3.40GHz
GPU: NVIDIA GeForce GTX 1070
RAM: 16GB
MOBO: X99A RAIDER (MS-7885)
BIOS: Up to date (issue persisted before and after update)
Windows is installed on 250gb SSD, also using 1TB HDD

Here is the minidump analyzed:

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4734

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 31876

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

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

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

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


BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff803236fb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: fffff803270b8770 -- (.trap 0xfffff803270b8770)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffa1843f4e36d0 rbx=0000000000000000 rcx=fffff803270b89e0
rdx=0000000000000018 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8033d959f3a rsp=fffff803270b8900 rbp=fffff803270b8a10
r8=0000000000000014 r9=0000000000000000 r10=0000000000000000
r11=fffff8033e23a7f8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nvlddmkm+0xc9f3a:
fffff8033d959f3a 4883ec20 sub rsp,20h Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: Discord.exe DPC_STACK_BASE: FFFFF803270B8FB0 STACK_TEXT: fffff803270bfc88 fffff80322e3ac52 : 0000000000000133 0000000000000001 0000000000001e00 fffff803236fb320 : nt!KeBugCheckEx fffff803270bfc90 fffff80322c7541d : 00028c220649b66e fffff8031e95e180 0000000000000246 0000000001ebe5bf : nt!KeAccumulateTicks+0x1c8a52 fffff803270bfcf0 fffff80322c759c1 : 0000000001ebe5be 0000000001253197 fffff8031e95e180 0000000000000001 : nt!KiUpdateRunTime+0x5d fffff803270bfd40 fffff80322c6f833 : fffff8031e95e180 0000000000000000 fffff80323631b48 0000000000000000 : nt!KiUpdateTime+0x4a1 fffff803270bfe80 fffff80322c781f2 : fffff803270b8770 fffff803270b87f0 fffff803270b8700 0000000000000002 : nt!KeClockInterruptNotify+0x2e3 fffff803270bff30 fffff80322d27f55 : 00000494cfb586f5 fffff803236f3ba0 fffff803236f3c50 ffffa052e307d9ee : nt!HalpTimerClockInterrupt+0xe2 fffff803270bff60 fffff80322df76fa : fffff803270b87f0 fffff803236f3ba0 fffff803270b89e0 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5 fffff803270bffb0 fffff80322df7c67 : fffff80322c36d20 0000000000000000 0000000000000018 0000000000000014 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff803270b8770 fffff8033d959f3a : ffffa18441470000 fffff8033d94b362 ffffa18441470000 ffffa184414b63f0 : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff803270b8900 ffffa18441470000 : fffff8033d94b362 ffffa18441470000 ffffa184414b63f0 0000000000000000 : nvlddmkm+0xc9f3a fffff803270b8908 fffff8033d94b362 : ffffa18441470000 ffffa184414b63f0 0000000000000000 0000000000000000 : 0xffffa18441470000
fffff803270b8910 ffffa18441470000 : ffffa184414b63f0 0000000000000000 0000000000000000 0000000000000004 : nvlddmkm+0xbb362
fffff803270b8918 ffffa184414b63f0 : 0000000000000000 0000000000000000 0000000000000004 0000000000000000 : 0xffffa18441470000 fffff803270b8920 0000000000000000 : 0000000000000000 0000000000000004 0000000000000000 000000ff00000300 : 0xffffa184414b63f0


SYMBOL_NAME: nvlddmkm+c9f3a

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: c9f3a

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


If I forgot anything please feel free to ask anything... Thanks again.

 

[mdd1963]

I'd experiment with running the system with only 1 RAM stick for a day or two, and, if no change, the other stick, although you will take a hit in performance running only a single RAM stick and half as much at that....

I'd also completely disconnect the spinning drive, and, install one of your games in question to the SSD alone, and retest.

Naturally, a PSU could cause weird issues as you have seen....

 

[ehodg]

I'd experiment with running the system with only 1 RAM stick for a day or two, and, if no change, the other stick, although you will take a hit in performance running only a single RAM stick and half as much at that....

I'd also completely disconnect the spinning drive, and, install one of your games in question to the SSD alone, and retest.

Naturally, a PSU could cause weird issues as you have seen....

Thank you so much for the advice. Testing the ram sticks is a great idea. I'll give it a go and let you know. The problem with this issue is I have to wait until the next day to troubleshoot.

 

[ehodg]

I had no luck with troubleshooting; however, I randomly got an error code during one of its usual restarts... "VIDEO TDR FAILURE" What failed: nvlddmkm.sys

Time to research this now... If anybody has any advice, I'm all ears!