Pc rebooting

J

jaydenrw98

Bronze Level Poster
Turned my pc on got past the login screen and 5 minutes later it just started rebooting over and over again, tried to do a system restore which ended up failing for some reason. Since it's reboot after the failed restore it now seems to be running fine (for now).

Can anyone give me troubleshooting advice please.
 
J

jaydenrw98

Bronze Level Poster
Case FRACTAL FOCUS G BLACK GAMING CASE (Window)
Processor (CPU)AMD Ryzen 7 3800X Eight Core CPU (3.9GHz-4.5GHz/36MB CACHE/AM4)
MotherboardASUS® ROG STRIX B450-F GAMING (DDR4, USB 3.1, 6Gb/s) - RGB Ready!
Memory (RAM)16GB Corsair VENGEANCE DDR4 3600MHz (2 x 8GB)
Graphics Card8GB NVIDIA GEFORCE RTX 2060 SUPER - HDMI, DP - VR Ready!
1st Storage Drive2TB PCS 2.5" SSD, SATA 6 Gb (520MB/R, 470MB/W)
DVD/BLU-RAY DriveNOT REQUIRED
Power SupplyCORSAIR 550W TXm SERIES™ SEMI-MODULAR 80 PLUS® GOLD, ULTRA QUIET
Power Cable1 x 1 Metre UK Power Cable (Kettle Lead)
Processor CoolingCorsair H80i V2 Hydro Series High Performance CPU Cooler
Thermal PasteSTANDARD THERMAL PASTE FOR SUFFICIENT COOLING
Extra Case Fans2x 120mm Black Case Fan (configured to extract from rear/roof)
down_right_arrow.gif
Change to: 1 x 120mm Black Case Fan
Sound CardONBOARD 6 CHANNEL (5.1) HIGH DEF AUDIO (AS STANDARD)
Wireless Network CardWIRELESS INTEL® Wi-Fi 6 AX200 2,400Mbps/5GHz, 300Mbps/2.4GHz PCI-E CARD + BT 5.0
USB/Thunderbolt OptionsMIN. 2 x USB 3.0 & 2 x USB 2.0 PORTS @ BACK PANEL + MIN. 2 FRONT PORTS
Operating SystemWindows 10 Home 64 Bit - inc. Single Licence [KUK-00001]
Operating System LanguageUnited Kingdom - English Language
Windows Recovery MediaNO RECOVERY MEDIA REQUIRED
 
Last edited by a moderator:
B4zookaw

B4zookaw

VALUED CONTRIBUTOR
When it got into the boot loop, did it boot into windows and then restart? Or just restarted after a failed POST?
 
B4zookaw

B4zookaw

VALUED CONTRIBUTOR
Ok. Look in window’s event viewer and see if there are any Error entries in the system log. They might contain info as to why it restarted each time.
 
B4zookaw

B4zookaw

VALUED CONTRIBUTOR
Anything that refers to unexpected shutdown or restart. Hard to say what exactly might be listed, could be anything causing the reboots at this point.

Maybe post screenshots of what you can see?
 
J

jaydenrw98

Bronze Level Poster
IRLRobinS said:
Anything that refers to unexpected shutdown or restart. Hard to say what exactly might be listed, could be anything causing the reboots at this point.

Maybe post screenshots of what you can see?
Click to expand...
this appears to be the error i'm getting whenever my pc crashes, before my PC just crashed i noticed my pc to start getting laggy, so i went into task manager and noticed "news and interests" was causing a huge memory spike so maybe that was the issue, idk?
 

Attachments

  • Screenshot_122.png
    Screenshot_122.png
    12.7 KB · Views: 82
Last edited:
J

jaydenrw98

Bronze Level Poster
IRLRobinS said:
Could be a range of causes for the 161 error from my quick research/Google. Might be worth looking at the dump files to see if they have more info: https://www.windowscentral.com/how-open-and-analyze-dump-error-files-windows-10
Click to expand...
0: kd> !analyze -v

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 12165

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x116

Key : Bugcheck.Code.Register
Value: 0x116

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


FILE_IN_CAB: 091322-16140-01.dmp

BUGCHECK_CODE: 116

BUGCHECK_P1: ffffde81518d4010

BUGCHECK_P2: fffff8028ffee0c0

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffde81518d4010
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:
ffffb68e`0faaca18 fffff802`72b2638e : 00000000`00000116 ffffde81`518d4010 fffff802`8ffee0c0 ffffffff`c000009a : nt!KeBugCheckEx
ffffb68e`0faaca20 fffff802`72ad6b04 : fffff802`8ffee0c0 ffffde81`4a0436e0 00000000`00002000 ffffde81`4a0437a0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffb68e`0faaca60 fffff802`72acf63c : ffffde81`4a040000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffffb68e`0faaca90 fffff802`72b25ab5 : 00000000`00000100 ffffde81`4a040a70 00000000`00000000 00000000`00000300 : dxgkrnl!DXGADAPTER::Reset+0x4dc
ffffb68e`0faacb10 fffff802`72b25c27 : fffff802`64b25440 ffffde81`3d2f5ab0 00000000`00000000 00000000`00000300 : dxgkrnl!TdrResetFromTimeout+0x15
ffffb68e`0faacb40 fffff802`64086265 : ffffde81`4601f0c0 fffff802`72b25c00 ffffde81`3d2ada20 00000000`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffb68e`0faacb70 fffff802`64158235 : ffffde81`4601f0c0 00000000`00000080 ffffde81`3d28e040 000f8067`b4bbbdff : nt!ExpWorkerThread+0x105
ffffb68e`0faacc10 fffff802`641fff48 : ffff9000`bb840180 ffffde81`4601f0c0 fffff802`641581e0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffb68e`0faacc60 00000000`00000000 : ffffb68e`0faad000 ffffb68e`0faa7000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+e2e0c0

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; 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
---------
 
B4zookaw

B4zookaw

VALUED CONTRIBUTOR
If it was me in this situation Id now be looking at doing a fresh, clean install of Windows from scratch. If it still occurs after that, it's likely to be a hardware issue.
 
J

jaydenrw98

Bronze Level Poster
Done a full restore, 30 minutes later my computer has just restarted randomly, only error i see in the event logger
 

Attachments

  • Screenshot_9.png
    Screenshot_9.png
    6.2 KB · Views: 60
SpyderTracks

SpyderTracks

We love you Ukraine
jaydenrw98 said:
How would do I do this?
Click to expand...
Option One from here:

www.howtogeek.com

How to do a Clean Install of Windows 10 the Easy Way

The Windows 10 upgrade process drags old files, settings, and programs from your previous Windows system to your new one.
www.howtogeek.com www.howtogeek.com

When you come to saying which partition to install to, you need to delete any partitions on the OS drive and install to the spare space, assuming of course you've backed up any data you need to firstly.
 
ubuysa

ubuysa

The BSOD Doctor
jaydenrw98 said:
Done a full restore, 30 minutes later my computer has just restarted randomly, only error i see in the event logger
Click to expand...
That BSOD (0x116) is a VIDEO_TDR_FAILURE. TDR is the 'timeout detection and recovery' feature of Windows attempting to recover from a graphics driver timeout, but failing - hence the BSOD.

If you've not yet done the clean install please follow the directions here to upload any minidumps and logs.

That said, your issue is either going to be a flaky driver or the graphics card. If the PC has been moved at all lately I would try reseating the graphics card. If you've updated the graphics driver lately I would try rolling back to an earlier version.

If this happens again after the clean install please follow the directions at https://www.pcspecialist.co.uk/forums/threads/when-youre-seeking-help-with-a-bsod.71885/#post-568901 to upload any dumps and logs.

FYI everyone: When users report a system rebooting by itself, please point them to this post: https://www.pcspecialist.co.uk/forums/threads/when-youre-seeking-help-with-a-bsod.71885/#post-568901. Windows auto-restarts after a 'system failure' and whilst these aren't always BSODs, those that are will be more easily solved. Thanks! :)
 
You must log in or register to reply here.
Top