Question Windows 10 reboots in middle of the night while I'm sleeping

Sep 11, 2021
5
0
10
0
Hi,
So my setup is
Board: GIGABYTE B450M GAMING
PSU: Gigabyte P850 GM
Processor: AMD Ryzen 5 2600 Six core
RAM: 1 Kingston KHX3200C16D4/16GX , Corsair CMK8GX4M1D3000C16 (24GB in total)
GPU1 connected to a riser: NVIDIA Asus 1660ti
GPU2: connected to the main PCIE slot (the 16pin) : NVIDIA RTX 3060ti LHR

So here's the problem, I have my GPUs overclocked as I'm currently mining, My mining settings are in the screenshots here View: https://imgur.com/a/hyxRe8P

This is how my GPUs is connected as well if it's needed.. View: https://imgur.com/a/U0LTzRb

I know it's better to connect the GPUs from different power cable each, But the cables are too short to connect the riser and a GPU at the same time, Hope that's not the problem anyways.

Almost everyday, If I spend 12 hours on my PC nothing goes wrong, I'm mining, gaming, or both together and nothing wrong happens, But whenever I go to sleep, I wake up the following day and the PC has restarted, I checked my PC sleep/display options and nothing seems to be wrong. it shouldn't restart on its own.

I check the event log and this was there,
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


-System

-Provider
[ Name]Microsoft-Windows-Kernel-Power
[ Guid]{331c3b3a-2005-44c2-ac5e-77220c37d6b4}

EventID41

Version8

Level1

Task63

Opcode0

Keywords0x8000400000000002

-TimeCreated
[ SystemTime]2021-10-25T09:31:53.6669364Z

EventRecordID13358

Correlation

-Execution
[ ProcessID]4
[ ThreadID]8

ChannelSystem

ComputerDESKTOP-07RN8AL

-Security
[ UserID]S-1-5-18

-EventData

BugcheckCode278

BugcheckParameter10xffff9e8bcac35460

BugcheckParameter20xfffff8028febac44

BugcheckParameter30xffffffffc000009a

BugcheckParameter40x4

SleepInProgress0

PowerButtonTimestamp0

BootAppStatus0

Checkpoint0

ConnectedStandbyInProgressfalse

SystemSleepTransitionsToOn0

CsEntryScenarioInstanceId0

BugcheckInfoFromEFIfalse

CheckpointStatus0

CsEntryScenarioInstanceIdV20

LongPowerButtonPressDetectedfalse



Can anyone help me resolve this issue? I don't want my PC restarting out of nowhere or crashing idk, I'm not a pro in resolving issues so please explain as if you're explaining to a monkey on what am I supposed to check/do :'D , Thanks in advance
 
Last edited:

Drew125

Distinguished
Nov 3, 2014
188
9
18,695
3
If it "crashed" a minidump should have been created. Please check in c:\windows\minidump. Upload a copy of the latest one. I can analyze it and tell you more of what the cause was.
 

Drew125

Distinguished
Nov 3, 2014
188
9
18,695
3
Here's the latest minidump file with the date 25/10/2021 , There's also 4 more if needed from the dates 21/10 to 23/10.. Hope you can help

https://easyupload.io/ioa2g5

Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\arobbins\Downloads\102521-15140-01\102521-15140-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff8027ea00000 PsLoadedModuleList = 0xfffff8027f62a270
Debug session time: Mon Oct 25 05:31:15.624 2021 (UTC - 4:00)
System Uptime: 0 days 9:26:56.282
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
11: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff9e8bcac35460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8028febac44, 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 nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 1

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on EIC3180

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 2

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

Key : Analysis.System
Value: CreateObject


DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 116

BUGCHECK_P1: ffff9e8bcac35460

BUGCHECK_P2: fffff8028febac44

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff9102b0b09a18 fffff8028b0c665e : 0000000000000116 ffff9e8bcac35460 fffff8028febac44 ffffffffc000009a : nt!KeBugCheckEx
ffff9102b0b09a20 fffff8028b076e44 : fffff8028febac44 ffff9e8bc3f8c010 0000000000002000 ffff9e8bc3f8c0d0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff9102b0b09a60 fffff8028b06f97c : ffff9e8bc3f6a000 0000000001000000 0000000000000004 0000000000000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffff9102b0b09a90 fffff8028b0c5d85 : 0000000000000100 ffff9e8bc3f6aa70 00000000b3e69580 0000000000000300 : dxgkrnl!DXGADAPTER::Reset+0x4dc
ffff9102b0b09b10 fffff8028b0c5ef7 : fffff8027f725440 0000000000000000 0000000000000000 0000000000000300 : dxgkrnl!TdrResetFromTimeout+0x15
ffff9102b0b09b40 fffff8027ecb8515 : ffff9e8bc928c040 fffff8028b0c5ed0 ffff9e8bb3e69580 ffff9e8b00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff9102b0b09b70 fffff8027ed55855 : ffff9e8bc928c040 0000000000000080 ffff9e8bb3ea1080 0000000000000001 : nt!ExpWorkerThread+0x105
ffff9102b0b09c10 fffff8027edfe808 : ffffe601a2bde180 ffff9e8bc928c040 fffff8027ed55800 000000000009afa0 : nt!PspSystemThreadStartup+0x55
ffff9102b0b09c60 0000000000000000 : ffff9102b0b0a000 ffff9102b0b04000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+dcac44

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner
---------
Cause: nvlddmkm.sys, This is a video driver for NVidia.

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

It looks to me like either the video driver needs to be re-installed or your graphics card is so overwhelmed by the mining operation that it cant recover fast enough before the watchdog timer kills it. Id try reloading the drivers and see if that helps.

If that does not fix the issue you might have to get a small graphics adapter for the monitor that way the monitor is not powered off the mining graphics card. Something close to this.

https://www.amazon.com/VisionTek-Radeon-5450-DVI-I-Graphics/dp/B01CN1F1ZM/ref=sr_1_6?dchild=1&keywords=video+card&qid=1635258728&sr=8-6
 
Last edited:
Sep 11, 2021
5
0
10
0
Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\arobbins\Downloads\102521-15140-01\102521-15140-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff8027ea00000 PsLoadedModuleList = 0xfffff8027f62a270
Debug session time: Mon Oct 25 05:31:15.624 2021 (UTC - 4:00)
System Uptime: 0 days 9:26:56.282
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
11: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff9e8bcac35460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8028febac44, 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 nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 1

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on EIC3180

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 2

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

Key : Analysis.System
Value: CreateObject


DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 116

BUGCHECK_P1: ffff9e8bcac35460

BUGCHECK_P2: fffff8028febac44

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff9102b0b09a18 fffff8028b0c665e : 0000000000000116 ffff9e8bcac35460 fffff8028febac44 ffffffffc000009a : nt!KeBugCheckEx
ffff9102b0b09a20 fffff8028b076e44 : fffff8028febac44 ffff9e8bc3f8c010 0000000000002000 ffff9e8bc3f8c0d0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff9102b0b09a60 fffff8028b06f97c : ffff9e8bc3f6a000 0000000001000000 0000000000000004 0000000000000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffff9102b0b09a90 fffff8028b0c5d85 : 0000000000000100 ffff9e8bc3f6aa70 00000000b3e69580 0000000000000300 : dxgkrnl!DXGADAPTER::Reset+0x4dc
ffff9102b0b09b10 fffff8028b0c5ef7 : fffff8027f725440 0000000000000000 0000000000000000 0000000000000300 : dxgkrnl!TdrResetFromTimeout+0x15
ffff9102b0b09b40 fffff8027ecb8515 : ffff9e8bc928c040 fffff8028b0c5ed0 ffff9e8bb3e69580 ffff9e8b00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff9102b0b09b70 fffff8027ed55855 : ffff9e8bc928c040 0000000000000080 ffff9e8bb3ea1080 0000000000000001 : nt!ExpWorkerThread+0x105
ffff9102b0b09c10 fffff8027edfe808 : ffffe601a2bde180 ffff9e8bc928c040 fffff8027ed55800 000000000009afa0 : nt!PspSystemThreadStartup+0x55
ffff9102b0b09c60 0000000000000000 : ffff9102b0b0a000 ffff9102b0b04000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+dcac44

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner
---------
Cause: nvlddmkm.sys, This is a video driver for NVidia.

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

It looks to me like either the video driver needs to be re-installed or your graphics card is so overwhelmed by the mining operation that it cant recover fast enough before the watchdog timer kills it. Id try reloading the drivers and see if that helps.

If that does not fix the issue you might have to get a small graphics adapter for the monitor that way the monitor is not powered off the mining graphics card. Something close to this.

https://www.amazon.com/VisionTek-Radeon-5450-DVI-I-Graphics/dp/B01CN1F1ZM/ref=sr_1_6?dchild=1&keywords=video+card&qid=1635258728&sr=8-6
Which graphics card keeps crashing? I need to figure which one to lower the overclock as well in case it's over overlocked which might be the reason of the crash, Any ideas how to figure which one crashed?
 

Drew125

Distinguished
Nov 3, 2014
188
9
18,695
3
Which graphics card keeps crashing? I need to figure which one to lower the overclock as well in case it's over overlocked which might be the reason of the crash, Any ideas how to figure which one crashed?
Which graphics card keeps crashing? I need to figure which one to lower the overclock as well in case it's over overlocked which might be the reason of the crash, Any ideas how to figure which one crashed?
Without pulling one and testing, no. The Crash info just gives the driver.
 
Reactions: moataz987

Drew125

Distinguished
Nov 3, 2014
188
9
18,695
3
This is the complete Debug text.

Microsoft (R) Windows Debugger Version 10.0.15063.400 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Andrew\Downloads\102521-15140-01\102521-15140-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


* Symbol Path validation summary **
Response Time (ms) Location
Deferred SRVc:\symbols Symbol search path is: SRVc:\symbols Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff8027ea00000 PsLoadedModuleList = 0xfffff8027f62a270
Debug session time: Mon Oct 25 05:31:15.624 2021 (UTC - 4:00)
System Uptime: 0 days 9:26:56.282
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.........
***
  • *
  • Bugcheck Analysis *
  • *
***

Use !analyze -v to get detailed debugging information.

BugCheck 116, {ffff9e8bcac35460, fffff8028febac44, ffffffffc000009a, 4}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+dcac44 )

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

11: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.19041.1288 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: B450M GAMING

SYSTEM_SKU: Default string

SYSTEM_VERSION: Default string

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F30

BIOS_DATE: 03/21/2019

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: B450M GAMING

BASEBOARD_VERSION: x.x

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_P1: ffff9e8bcac35460

BUGCHECK_P2: fffff8028febac44

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FAULTING_IP:
nvlddmkm+dcac44
fffff8028febac44 48ff255506b7ff jmp qword ptr [nvlddmkm+0x93b2a0 (fffff8028fa2b2a0)]

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CPU_COUNT: c

CPU_MHZ: d42

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: ANDREW2-PC

ANALYSIS_SESSION_TIME: 10-30-2021 21:47:13.0221

ANALYSIS_VERSION: 10.0.15063.400 amd64fre

STACK_TEXT:
ffff9102b0b09a18 fffff8028b0c665e : 0000000000000116 ffff9e8bcac35460 fffff8028febac44 ffffffffc000009a : nt!KeBugCheckEx
ffff9102b0b09a20 fffff8028b076e44 : fffff8028febac44 ffff9e8bc3f8c010 0000000000002000 ffff9e8bc3f8c0d0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff9102b0b09a60 fffff8028b06f97c : ffff9e8bc3f6a000 0000000001000000 0000000000000004 0000000000000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffff9102b0b09a90 fffff8028b0c5d85 : 0000000000000100 ffff9e8bc3f6aa70 00000000b3e69580 0000000000000300 : dxgkrnl!DXGADAPTER::Reset+0x4dc
ffff9102b0b09b10 fffff8028b0c5ef7 : fffff8027f725440 0000000000000000 0000000000000000 0000000000000300 : dxgkrnl!TdrResetFromTimeout+0x15
ffff9102b0b09b40 fffff8027ecb8515 : ffff9e8bc928c040 fffff8028b0c5ed0 ffff9e8bb3e69580 ffff9e8b00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff9102b0b09b70 fffff8027ed55855 : ffff9e8bc928c040 0000000000000080 ffff9e8bb3ea1080 0000000000000001 : nt!ExpWorkerThread+0x105
ffff9102b0b09c10 fffff8027edfe808 : ffffe601a2bde180 ffff9e8bc928c040 fffff8027ed55800 000000000009afa0 : nt!PspSystemThreadStartup+0x55
ffff9102b0b09c60 0000000000000000 : ffff9102b0b0a000 ffff9102b0b04000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 56a150c818aff348d17e35fc9e822916b6c0190b

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 566318dfd710cc1e0e9f44288bdfb7068acf4ad7

THREAD_SHA1_HASH_MOD: 3225689ea8bf23dca00cdfd517975e0703e07271

FOLLOWUP_IP:
nvlddmkm+dcac44
fffff8028febac44 48ff255506b7ff jmp qword ptr [nvlddmkm+0x93b2a0 (fffff8028fa2b2a0)]

FAULT_INSTR_CODE: 5525ff48

SYMBOL_NAME: nvlddmkm+dcac44

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 613fe436

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

PRIMARY_PROBLEM_CLASS: 0x116_IMAGE_nvlddmkm.sys

TARGET_TIME: 2021-10-25T09:31:15.000Z

OSBUILD: 19041

OSSERVICEPACK: 1288

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 1995-01-03 23:27:11

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.19041.1288

ANALYSIS_SESSION_ELAPSED_TIME: 593

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x116_image_nvlddmkm.sys

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

Followup: MachineOwner
---------
 
Reactions: moataz987

ASK THE COMMUNITY