GPU or PSU problem?

[jayzackzz]

Thankss guyss i'll keep trying all the options and see if anything ever works Really grateful for all your help. I'll update if I ever got a fix

[jayzackzz]

I got this from the dump file.

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffb00e49d47010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80240a96bd8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_abe8c5cbd39cd342\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3124

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 14391

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

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

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

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

BUGCHECK_P1: ffffb00e49d47010

BUGCHECK_P2: fffff80240a96bd8

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffb00e49d47010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffac05`418972d8 fffff802`3c191cce     : 00000000`00000116 ffffb00e`49d47010 fffff802`40a96bd8 ffffffff`c000009a : nt!KeBugCheckEx
ffffac05`418972e0 fffff802`3c1424f4     : fffff802`40a96bd8 ffffb00e`4291a050 00000000`00002000 ffffb00e`4291a110 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffac05`41897320 fffff802`3c13b02f     : ffffb00e`428f3000 00000000`01000000 00000000`00000002 00000000`00000002 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffffac05`41897350 fffff802`3c1913f5     : 00000000`00000100 ffffb00e`428f3a58 00000000`393f9350 fffff802`238cf40c : dxgkrnl!DXGADAPTER::Reset+0x4df
ffffac05`418973d0 fffff802`3c191567     : fffff802`24324440 ffffb00e`49d78a20 00000000`00000000 00000000`00000300 : dxgkrnl!TdrResetFromTimeout+0x15
ffffac05`41897400 fffff802`238b8515     : ffffb00e`39275100 fffff802`3c191540 ffffb00e`340a5cb0 ffffb00e`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffac05`41897430 fffff802`23955875     : ffffb00e`39275100 00000000`00000080 ffffb00e`340a9040 001fa4ef`b59bbfff : nt!ExpWorkerThread+0x105
ffffac05`418974d0 fffff802`239fe578     : ffffc501`ac1c0180 ffffb00e`39275100 fffff802`23955820 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffac05`41897520 00000000`00000000     : ffffac05`41898000 ffffac05`41891000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nvlddmkm+dc6bd8

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Followup:     MachineOwner
---------


Does this point to a GPU problem?

[Guest]

1 hour ago, MadGoatHaz said:

His PSU had 2 rails of 12v. OCP will work separately on each rail. 

exceeding OCP causes the PSU to shut down.  OP's PSU is not shutting down.

 

[jayzackzz]

Just did a furmark 1080 and 1440p and everything is normal. 3dmark still causing reboots.

[MadGoatHaz]

1 hour ago, jonnyGURU said:

exceeding OCP causes the PSU to shut down.  OP's PSU is not shutting down.

 

Yup, will trigger differently on separate rails. OCP is essentially what "makes" separate rails. OPP is on the primary. 

 

1 hour ago, jayzackzz said:

Just did a furmark 1080 and 1440p and everything is normal. 3dmark still causing reboots.

Driver power limits known power virus software like furmark. It has since back in the day people were burning up their cards with it. It is good for temp and load testing but won't trigger high power loads. 

[Guest]

7 minutes ago, MadGoatHaz said:

Yup, will trigger differently on separate rails. OCP is essentially what "makes" separate rails. OPP is on the primary. 

I suggest you study a little more into how a PSU and it's protections work.

 

OCP is on the secondary.  OPP is on the primary.  Tripping either makes the PSU shut down. OP's PSU is not shutting down.

 

 

[jayzackzz]

I tried removing all driver with DDU again, installed 466.47 (which still cause crashes), then updated to the latest drivers. For a moment, everything worked. Ran time spy for 3 times without crashing, port royal twice and port royal dlss another once. The only problem is there is no audio in 3d mark. (audio normal in browsers) Tried rebooting the pc, ran 3d mark and everything started crashing again. Another difference i noticed is during the run without audio, the results from 3d mark show that the display connected is "\\.\DISPLAY6 Generic PnP Monitor", after reboot it goes back to DISPLAY1 Generic PnP Monitor and started crashing (similar to that when it was crashing every time previously).WTH.....can anyone explain this 

 

[jayzackzz]

Changed my PSU to a Cosair SF600, problem persists. Still worth it since the small form factor made the whole case so much tidier and improved airflow. Time to get the GPU replaced. Thanks for the help guys.

[jayzackzz]

just an update, tried my gpu on another system with a 6th gen i5. Passed 3 3d Mark timespy tests without any problem. Tried another 3070 on my own system, ran perfectly (damn the 3070 is really fast). Am I just unlucky that my different components are not getting along with each other...

[jayzackzz]

Problem solved, the problem is in my motherboard pcie settings. Forced pcie gen 3.0 in the BIOS instead of putting it on auto. Not sure why there is a pcie gen 4 option since my H470 motherboard shouldnt be supported, must be causing some conflict or whatever I'm not sure. No crashes after few hours of 3dmark stress test.