Question Long beep followed by shutdown

May 13, 2021
4
0
10
0
My computer is shutting down at night. I will have been on it all day play World of Warcraft and watching videos. I typically just turn off my monitors at night and let my computer go to sleep. I'll have turned off monitors, gone upstairs brushed my teeth etc and I'll hear a long beep coming from downstairs. I come down in morning and find that I need to start my computer up. I poked around my case and found that my top big case fan wasn't spinning. Ok fine. I've had the case for a really long time and was about time to replace it anyway. I bought a Fractal case and put in an additional 4 Noctua 140mm fans along with the 2 120mm fans that came with it.

Well the problem is still happening. I've read that it could be either a PSU or memory issue. Power would make sense since the beep happens right around the time the computer typically goes to sleep. Problem is I've also manually put the computer to sleep before bed and the beep still happens a bit later. I just bought my Corsair RM 750x PSU 2.5 years ago so I'm hoping it's not that. I'm also thinking if it was a memory problem wouldn't the beep and shutdown happen while my computer was under load? I've also found while using CCleaner that the memory dump is around 1.5G. Does that mean it's definitely the memory? Parts aren't exactly cheap right now so I'm hoping to nail down the issue before buying parts.


Windows 10 Home 64-bit
Intel Core i7 @ 3.70GHz Coffee Lake 14nm Technology
2x 8GB G.Skill TridentZ DDR4 3200 (16-18-18-38) Bought about 5 years ago
Micro-Star International Co. Ltd. MAG Z390 TOMAHAWK (MS-7B18) (U3E1)
4095MB NVIDIA GeForce GTX 1070 Ti
500GB Samsung SSD 850 EVO M.2
500GB Samsung SSD 860 EVO M.2

Thanks
 

iPeekYou

Honorable
Jul 7, 2014
322
57
10,790
8
My computer is shutting down at night. I will have been on it all day play World of Warcraft and watching videos. I typically just turn off my monitors at night and let my computer go to sleep. I'll have turned off monitors, gone upstairs brushed my teeth etc and I'll hear a long beep coming from downstairs. I come down in morning and find that I need to start my computer up. I poked around my case and found that my top big case fan wasn't spinning. Ok fine. I've had the case for a really long time and was about time to replace it anyway. I bought a Fractal case and put in an additional 4 Noctua 140mm fans along with the 2 120mm fans that came with it.

Well the problem is still happening. I've read that it could be either a PSU or memory issue. Power would make sense since the beep happens right around the time the computer typically goes to sleep. Problem is I've also manually put the computer to sleep before bed and the beep still happens a bit later. I just bought my Corsair RM 750x PSU 2.5 years ago so I'm hoping it's not that. I'm also thinking if it was a memory problem wouldn't the beep and shutdown happen while my computer was under load? I've also found while using CCleaner that the memory dump is around 1.5G. Does that mean it's definitely the memory? Parts aren't exactly cheap right now so I'm hoping to nail down the issue before buying parts.

Thanks
Probably not the PSU, sounds like bad power from your outlet or more likely, an issue with Windows power plan. Is the plan set to never shut down? You can also try changing power plans and/or reset power plan defaults. Some changes in power plan is not available through the menu, and I figure it might bork up eventually.
 
May 13, 2021
4
0
10
0
I figured out I should be analyzing those 1.5G memory dump files with Windbg Preview. It just happened again and I tried to interpret the results but it's going over my head. Maybe a GPU issue now?

***
  • *
  • Bugcheck Analysis *
  • *
***

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffffba8889e33060, Physical Device Object of the stack
Arg3: fffff80423c71750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffba890656b010, The blocked IRP

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

Implicit thread is now ffffba8887f24080
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a494df49ba2f9f36\nvlddmkm.sys, Win32 error 0n2

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3233

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 8683

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

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

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: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffba8889e33060

BUGCHECK_P3: fffff80423c71750

BUGCHECK_P4: ffffba890656b010

DRVPOWERSTATE_SUBCODE: 3

FAULTING_THREAD: ffffba8887f24080

ADDITIONAL_DEBUG_TEXT: DXG Power IRP timeout.

IRP_ADDRESS: ffffba890656b010

DEVICE_OBJECT: ffffba888e0ca030

DRIVER_OBJECT: ffffba888ddede30

IMAGE_NAME: nvlddmkm.sys

MODULE_NAME: nvlddmkm

FAULTING_MODULE: fffff80429010000 nvlddmkm

PROCESS_NAME: System

STACK_TEXT:
fffff28a
54617260 fffff8041e40c970 : 000000000000000a fffff28affffffff fffff80400000000 ffffba88e89d4398 : nt!KiSwapContext+0x76
fffff28a
546173a0 fffff8041e40be9f : ffffffffffffffff fffff28a54617500 fffff28a54617560 0000000000000016 : nt!KiSwapThread+0x500
fffff28a
54617450 fffff8041e40b743 : fffff57a00000000 fffff80400000000 00000a0000000000 ffffba8887f241c0 : nt!KiCommitThreadWait+0x14f
fffff28a
546174f0 fffff80425c451ae : fffff28a54617640 fffff28a00000000 ffffba888e0ca100 ffffba888e0cc600 : nt!KeWaitForSingleObject+0x233
fffff28a
546175e0 fffff80425c44296 : 0000000000000003 0000000000000010 ffffba888e0cb050 ffffba888e0cb050 : dxgkrnl!DpiRequestIoPowerState+0xbe
fffff28a
54617680 fffff80425c44e34 : 0000000000000000 ffffba890656b010 0000000000000004 0000000000000004 : dxgkrnl!DpiFdoSetAdapterPowerState+0x336
fffff28a
54617740 fffff80425c44441 : fffff8041e20ca01 ffffba888dee5210 ffffba8889d6a6e0 ffffba890656b170 : dxgkrnl!DpiFdoHandleDevicePower+0x134
fffff28a
546177e0 fffff80425c45991 : ffffba890656b010 ffffba888e0ca180 ffffba888e0ca030 fffff8041e400000 : dxgkrnl!DpiFdoDispatchPower+0x21
fffff28a
54617810 fffff80429d91e65 : ffffba888e0ca030 fffff28a546179d9 0000000000000000 ffffba890656b170 : dxgkrnl!DpiDispatchPower+0xe1
fffff28a
54617930 fffff80429d91328 : ffffba888e0ca030 ffffba8800000000 ffffba8887f24080 ffffba888e0ca030 : nvlddmkm+0xd81e65
fffff28a
54617a40 fffff8041e59ce99 : ffffba8887f24080 fffff28a54617af0 ffffba890656b010 ffffba8892995000 : nvlddmkm+0xd81328
fffff28a
54617a70 fffff8041e4f53b5 : 0000000000000000 fffff8041e59ccc0 0000000000000000 00000000000000fa : nt!PopIrpWorker+0x1d9
fffff28a
54617b10 fffff8041e5fe348 : ffffa6007d9c4180 ffffba8887f24080 fffff8041e4f5360 781f3159185d4fb3 : nt!PspSystemThreadStartup+0x55
fffff28a
54617b60 0000000000000000 : fffff28a54618000 fffff28a54611000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


STACK_COMMAND: .thread 0xffffba8887f24080 ; kb

SYMBOL_NAME: nvlddmkm+0

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_DXG_POWER_IRP_TIMEOUT_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {429899a1-e4f8-75f1-8d13-ef3a0081fac6}

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

0: kd> lmvm nvlddmkm
Browse full module list
start end module name
fffff804
29010000 fffff804`2b59c000 nvlddmkm (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a494df49ba2f9f36\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Fri Apr 23 14:12:01 2021 (60833821)
CheckSum: 024FD385
ImageSize: 0258C000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
 
May 13, 2021
4
0
10
0
Probably not the PSU, sounds like bad power from your outlet or more likely, an issue with Windows power plan. Is the plan set to never shut down? You can also try changing power plans and/or reset power plan defaults. Some changes in power plan is not available through the menu, and I figure it might bork up eventually.
Yeah the plan is to never shut down. I've been running the same power plan for years so I'm hesitant to think that that's the issue.
 

ASK THE COMMUNITY

TRENDING THREADS