Question New PC restarts randomly during gaming.

May 29, 2021
6
0
10
0
Got a new PC but have been getting seemingly random restarts (only) during gaming. The crashes happen at completely different intervals, can be after 40 minutes, usually is after 4-5 hours, the last crash happened after 3 days without problems. This makes it very hard(time consuming) to test things (like swapping ram sticks). Monitors go out, then after about 7 seconds the PC just restarts. Event viewer details below.

Notes:
  1. Seems to crash less often with only 1 Memory Stick (might be random luck)
  2. Monitor wanted to go into Power savings in the beginning, fixed it by disabling the mode entirely, but maybe this is a clue that something is wrong with the GPU?
  3. I tried different RAM slots, tried both RAM sticks alone. Memtest86 in BIOS found 0 errors after 10 hours (ruled out RAM in my mind unless BIOS settings/voltage is responsible)
  4. Ran Furmark, 3d Benchmark, Userbenchmark, Passmark - No crashes, no high temperature, no bad performance (except ram underperforming, which makes sense because I underclock it)
  5. Tried the /sfc function to repair the disk image, it apparently did find some corrupted files and repaired them, but didn't change the crashes.
  6. Sound continues for about 7 seconds after the monitors go out before the PC restarts (I can still communicate on skype for example)
  7. Updated all Drivers, even uninstalled and completel installed the drivers again via GeForce Experience.
System:

Windows 10 professional

be quiet! Silent Base 600 - black, window

Intel Core i7-11700, 8x 2.50GHz

be quiet! Pure Rock 2

MSI MPG Z490 Gaming Plus, S. 1200

NVIDIA GeForce RTX 3060 Ti 8GB

2x16GB DDR4-3600 Corsair Vengeance LPX (I clock it to 3200 in XMP profile but tried automatic XMP and disabled XMP)

500GB | Samsung 980

850 Watt 80 PLUS GOLD | Corsair RMx Series

HD-Audio Onboard



Event Viewer Error: Bugcheck 0x00000116

Minidump Debug:
***

  • *
  • Bugcheck Analysis *
  • *
***

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff9d0515e32010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8069c7951bc, 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_a494df49ba2f9f36\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: 2796

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 23657

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

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

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

BUGCHECK_P2: fffff8069c7951bc

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffff9d0515e32010
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:
fffff98f65b612d8 fffff80697bf2cce : 0000000000000116 ffff9d0515e32010 fffff8069c7951bc ffffffffc000009a : nt!KeBugCheckEx
fffff98f65b612e0 fffff80697ba34f4 : fffff8069c7951bc ffff9d05090216e0 0000000000002000 ffff9d05090217a0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
fffff98f65b61320 fffff80697b9c02f : ffff9d0509010000 0000000001000000 0000000000000002 0000000000000002 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
fffff98f65b61350 fffff80697bf23f5 : 0000000000000100 ffff9d0509010a58 0000000000000000 0000000000000000 : dxgkrnl!DXGADAPTER::Reset+0x4df
fffff98f65b613d0 fffff80697bf2567 : fffff80680124440 ffff9d050816bac0 0000000000000000 0000000000000100 : dxgkrnl!TdrResetFromTimeout+0x15
fffff98f65b61400 fffff8067f741225 : ffff9d050e4eb040 fffff80697bf2540 ffff9d0500292c70 0000000000000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
fffff98f65b61430 fffff8067f6f53b5 : ffff9d050e4eb040 0000000000000080 ffff9d05002af040 0000000000000080 : nt!ExpWorkerThread+0x105
fffff98f65b614d0 fffff8067f7fe348 : ffffd58102567180 ffff9d050e4eb040 fffff8067f6f5360 ff938882ff897f76 : nt!PspSystemThreadStartup+0x55
fffff98f65b61520 0000000000000000 : fffff98f65b62000 fffff98f65b5b000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+d851bc

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


I was looking through many forums and threads of other people with similar issues thinking GPU is the cause, but it doesn't crash in Furmark (only ran it for an hour though) or when watching movies for example only during games (but both high demand (FPS shooters or Path of Exile) and low demand games like windowed Hearhtstone, so I think it's not due to high demand/settings.

Some mention PSU as the issue, but I believe I have a very good one (unless it's somehow broken) and I have been told PSU would shut down the PC not restart it.

I didn't completely reinstall windows yet because I highly doubt it's a software issue and I have a lot of important data and it would take a lot of time to save it. Anyone got idea or can find something valueable in the minidump? Starting to go crazy..

Thanks!
 
Last edited:

boju

Titan
Ambassador
Doubt it's psu related and or ram trying them singly.

Windows reinstall would be recommended if the drive came from another system with Windows already on it congested with other drivers and registry entries. If this is so, I'd at least get another hdd to test a clean install on.

Regarding graphics card, it's possible i guess there could be something up with the driver it's on. Maybe try an older version, there's few to choose from.
 
Reactions: dotas1
May 29, 2021
6
0
10
0
Doubt it's psu related and or ram trying them singly.

Windows reinstall would be recommended if the drive came from another system with Windows already on it congested with other drivers and registry entries. If this is so, I'd at least get another hdd to test a clean install on.

Regarding graphics card, it's possible i guess there could be something up with the driver it's on. Maybe try an older version, there's few to choose from.
The Windows was a clean install from the official windows media creation tool. Software is also all downloaded and installed from scratch, just a lot of documents/data is copied from an external HD. And like browser profiles or game save-files.

There has been a new Driver already in the meantime, so I tried the current and the previous one. Currently: 466.47 from 05/18/2021 but I have my computer a little bit longer than that, it crashed with the previous one as well.
 

boju

Titan
Ambassador
If it was maybe gpu power fluctuations causing reboots, have you tried setting power management to max in NvidiaCP?

Have you tried running stress tests as you've mentioned overnight? Not that immediate work load would restart the system but seems it's randomness could be caused by power spikes from gpu since games aren't always solid work load.

Trying another psu could be on the cards.
 
May 29, 2021
6
0
10
0
If it was maybe gpu power fluctuations causing reboots, have you tried setting power management to max in NvidiaCP?

Have you tried running stress tests as you've mentioned overnight? Not that immediate work load would restart the system but seems it's randomness could be caused by power spikes from gpu since games aren't always solid work load.

Trying another psu could be on the cards.
Today the PC crashed while I was on the desktop working/browsing with no game running at all. I noticed the mouse froze, couldn't use the keayboard, but the monitor did not go out, after 10 seconds the computer restarted.

Event viewer shows the same error though, unexpected shutdown and:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xffffd7013f1ef460, 0xfffff8075f6d71e4, 0xffffffffc000009a, 0x0000000000000004).

Considering that not much was going on, I doubt it's power fluctuations? I changed the power management to maximum performance now and will see if it makes a difference. Unfortunately I don't have a PSU or other GPU to test these.

[Edit]: One thing to add, according to my BIOS I have:
BIOS Version/Date American Megatrends Inc. A.60, 30.01.2021

But the BIOS update to be compatible with 11th Gen Intel Processors
supposedly came 04.02.2021 (https://www.msi.com/Motherboard/support/MPG-Z490-GAMING-PLUS) or was this just another version of the previous? Because I assume A.60 and vA6 refer to the same BIOS version?
 
Last edited:
May 29, 2021
6
0
10
0
If it was maybe gpu power fluctuations causing reboots, have you tried setting power management to max in NvidiaCP?

Have you tried running stress tests as you've mentioned overnight? Not that immediate work load would restart the system but seems it's randomness could be caused by power spikes from gpu since games aren't always solid work load.

Trying another psu could be on the cards.
Still crashed with max power management just now. Haven't tried stress test over night, I was told it's not good because you need to watch temperatures with programs such as Furmark.

In CPU-Z I get high CPU temperatures during stress test 88-92 roughly after 15 minutes, as I was told the 11700 has problems with temperatures, but it wouldn't explain why I crash in games like Hearthstone which have very low demand and only get my temp up to around 60.

Would a simple Windows "Repair" be good enough, to avoid a clean install to rule out software issue? Or can it be ruled out already?
 
Jun 1, 2021
13
3
15
0
My old apartment had problems with brownouts. 10ms power dips you could just barely see if you had the lights on and were paying attention. When I had my 750W (bare min for my setup) power supply it would crash and reboot. Stepped up to a 1200W and it had enough inertia/capacitance to survive the brown out.
 

boju

Titan
Ambassador
Spare hdd to trial a fresh Win install or creating another user with minimal running apps might shed some light. Look at startup items in task manager and maybe disable them to troubleshoot.
 
May 29, 2021
6
0
10
0
Any updates? Having the same problem with the same motherboard and cpu but with a 3070?
No. Will be sending it to inspection/repair this/next week. Wanted to do it last week, but I went without crashes for 6 days and was hopeful, just crashed again today without any gaming. Must be cursed, I give up.
 
May 29, 2021
6
0
10
0
Alright please let me know what they say.
So I got my Computer back and it hasn't crashed in 5 days (Doesn't mean it's 100% fixed but it looks promising). What most likely was causing the issue was the BIOS version not having the intel 11th generation support.

When Troubleshooting I was already looking into this as the potential issue because the BIOS update was somewhere in january and I saw in April they released 11th gen support update (I got mine at the end of May), however the version of this BIOS was also the version that was displayed in my BIOS despite the date being older. So I wasn't sure and didn't want to mess with updating BIOS myself since I have never done it, and wasn't sure if I break something and the PC doesn't work if I would still have warranty. Also my friend told me they would be assholes to ship something with an outdated BIOS, but I guess this is what happened. If it should crash again I will post once more, otherwise I consider this to be fixed for now. Thanks for the help, everyone, I hope this may help others with the same issue.

TLDR: Updating the BIOS with the intel 11th generation update most likely fixed the issue for me.
 

ASK THE COMMUNITY

TRENDING THREADS