L
lucmru
Hi,
Recently I'm having issues with my computer. I'm using a Dell Precision 5530. After a Windows reinstall, I noticed that from time to time my laptop would not respond after going in standby mode (not sleep mode) (screen off but PC on).
Normally when the computer goes in standby mode (not sleep mode) I just have to touch the trackpad or the keyboard for it (the Pc) to come back to life. But when my laptop is not connected to the power brick sometimes (not frequently) it would not respond when trying to wake it up from standby.
When this happens, the computer would reboot in recovery mode after a while for some reason.
By just restarting the computer manually again (from recovery mode), Windows boot up as normal!
I tried updating drivers, bios and Windows itself with no success
I ran dell system check from the bios and everything works as expected.
I'm now wondering if the problem is hardware related or software related?
If it’s software related, what should I do to fix this please?
I downloaded WinDbg from the windows store an opened the Memory dump (C: \Windows\MEMORY.DMP), here is what it says:
-----------------------------------------------------------------------------------------------------
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff807`0e200000 PsLoadedModuleList = 0xfffff807`0e6461b0
Debug session time: Mon Jan 25 18:31:28.041 2021 (UTC + 1:00)
System Uptime: 5 days 1:27:19.657
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`0e3c3b20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff30d`51a3f780=000000000000009f
2: kd> !analyze -v
*******************************************************************************
* *
* 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: ffff808bdde1c060, Physical Device Object of the stack
Arg3: fffff30d51a3f7b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff808bddd339a0, The blocked IRP
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4546
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-DOS0V98
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 4612
Key : Analysis.Memory.CommitPeak.Mb
Value: 81
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffff808bdde1c060
BUGCHECK_P3: fffff30d51a3f7b0
BUGCHECK_P4: ffff808bddd339a0
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
MODULE_NAME: pci
FAULTING_MODULE: fffff807111c0000 pci
PROCESS_NAME: System
STACK_TEXT:
fffff30d`51a3f778 fffff807`0e4edc57 : 00000000`0000009f 00000000`00000003 ffff808b`dde1c060 fffff30d`51a3f7b0 : nt!KeBugCheckEx
fffff30d`51a3f780 fffff807`0e4edb61 : ffff808b`ddd68890 fffff30d`51a3f800 ffffcd01`cbc80100 ffffcd01`cbc80180 : nt!PopIrpWatchdogBugcheck+0xef
fffff30d`51a3f7f0 fffff807`0e2c3559 : ffff808b`ddd688c8 00000000`00000000 000186a0`00000001 fffff30d`ffffffff : nt!PopIrpWatchdog+0x31
fffff30d`51a3f840 fffff807`0e2c22b9 : 00000000`00000004 00000000`00989680 00000000`00fe81c9 00000000`000000e1 : nt!KiProcessExpiredTimerList+0x169
fffff30d`51a3f930 fffff807`0e3c764e : ffffffff`00000000 ffffcd01`cbc80180 ffffcd01`cbc91340 ffff808b`da716040 : nt!KiRetireDpcList+0x4e9
fffff30d`51a3fb60 00000000`00000000 : fffff30d`51a40000 fffff30d`51a39000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7e
IMAGE_VERSION: 10.0.18362.1171
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x9F_3_AML!_SB.PCI0.PEG0.PG00._ON_ACPI_IMAGE_pci.sys
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {fe45222d-6294-f08d-fc4c-a4480753a8dc}
Followup: MachineOwner
-----------------------------------------------------------------------------------------------------------------------------
If needed I can upload the memory dump.
I hope someone can help me, and thanks in advance!
Continue reading...
Recently I'm having issues with my computer. I'm using a Dell Precision 5530. After a Windows reinstall, I noticed that from time to time my laptop would not respond after going in standby mode (not sleep mode) (screen off but PC on).
Normally when the computer goes in standby mode (not sleep mode) I just have to touch the trackpad or the keyboard for it (the Pc) to come back to life. But when my laptop is not connected to the power brick sometimes (not frequently) it would not respond when trying to wake it up from standby.
When this happens, the computer would reboot in recovery mode after a while for some reason.
By just restarting the computer manually again (from recovery mode), Windows boot up as normal!
I tried updating drivers, bios and Windows itself with no success
I ran dell system check from the bios and everything works as expected.
I'm now wondering if the problem is hardware related or software related?
If it’s software related, what should I do to fix this please?
I downloaded WinDbg from the windows store an opened the Memory dump (C: \Windows\MEMORY.DMP), here is what it says:
-----------------------------------------------------------------------------------------------------
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff807`0e200000 PsLoadedModuleList = 0xfffff807`0e6461b0
Debug session time: Mon Jan 25 18:31:28.041 2021 (UTC + 1:00)
System Uptime: 5 days 1:27:19.657
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`0e3c3b20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff30d`51a3f780=000000000000009f
2: kd> !analyze -v
*******************************************************************************
* *
* 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: ffff808bdde1c060, Physical Device Object of the stack
Arg3: fffff30d51a3f7b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff808bddd339a0, The blocked IRP
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4546
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-DOS0V98
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 4612
Key : Analysis.Memory.CommitPeak.Mb
Value: 81
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffff808bdde1c060
BUGCHECK_P3: fffff30d51a3f7b0
BUGCHECK_P4: ffff808bddd339a0
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
MODULE_NAME: pci
FAULTING_MODULE: fffff807111c0000 pci
PROCESS_NAME: System
STACK_TEXT:
fffff30d`51a3f778 fffff807`0e4edc57 : 00000000`0000009f 00000000`00000003 ffff808b`dde1c060 fffff30d`51a3f7b0 : nt!KeBugCheckEx
fffff30d`51a3f780 fffff807`0e4edb61 : ffff808b`ddd68890 fffff30d`51a3f800 ffffcd01`cbc80100 ffffcd01`cbc80180 : nt!PopIrpWatchdogBugcheck+0xef
fffff30d`51a3f7f0 fffff807`0e2c3559 : ffff808b`ddd688c8 00000000`00000000 000186a0`00000001 fffff30d`ffffffff : nt!PopIrpWatchdog+0x31
fffff30d`51a3f840 fffff807`0e2c22b9 : 00000000`00000004 00000000`00989680 00000000`00fe81c9 00000000`000000e1 : nt!KiProcessExpiredTimerList+0x169
fffff30d`51a3f930 fffff807`0e3c764e : ffffffff`00000000 ffffcd01`cbc80180 ffffcd01`cbc91340 ffff808b`da716040 : nt!KiRetireDpcList+0x4e9
fffff30d`51a3fb60 00000000`00000000 : fffff30d`51a40000 fffff30d`51a39000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7e
IMAGE_VERSION: 10.0.18362.1171
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x9F_3_AML!_SB.PCI0.PEG0.PG00._ON_ACPI_IMAGE_pci.sys
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {fe45222d-6294-f08d-fc4c-a4480753a8dc}
Followup: MachineOwner
-----------------------------------------------------------------------------------------------------------------------------
If needed I can upload the memory dump.
I hope someone can help me, and thanks in advance!
Continue reading...