BSOD while in standby

wasknick · Jun 18, 2011

Hi everyone. I am new to this forum and am here to try and get some help with a recent BSOD issue I have been having. The blue screen only happens when my computer is in standby mode, I have never seen it while actually actively using it. It is a Dell XPS 15 that is only a few months old. Its running Windows 7 Pro x64. Here is the debugging file I get, I need a little help analyzing it.

Code:

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


Loading Dump File [C:\Users\wasknick\Desktop\061611-35739-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e1c000 PsLoadedModuleList = 0xfffff800`03061650
Debug session time: Thu Jun 16 00:36:26.796 2011 (UTC - 4:00)
System Uptime: 0 days 0:14:06.811
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8007ae6380, fffff80000b9c518, fffffa8007802760}

Probably caused by : ACPI.sys

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8007ae6380, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8007802760, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79294

MODULE_NAME: ACPI

FAULTING_MODULE: fffff88000ed8000 ACPI

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02f089c2 : 00000000`0000009f 00000000`00000003 fffffa80`07ae6380 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02ea7652 : fffff800`00b9c648 fffff800`00b9c648 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`02ea74f6 : fffffa80`0700cc68 fffffa80`0700cc68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02ea73de : 00000001`f8bd25cf fffff800`00b9cc58 00000000`0000d40a fffff800`030113c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02ea71c7 : 00000000`554501c5 00000000`0000d40a 00000000`55450145 00000000`0000000a : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02e93a2a : fffff800`0300ee80 fffff800`0301ccc0 00000000`00000002 fffff800`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_SynTP_IMAGE_ACPI.sys

BUCKET_ID:  X64_0x9F_3_SynTP_IMAGE_ACPI.sys

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

zigzag3143 · Jun 18, 2011

wasknick said:

Hi everyone. I am new to this forum and am here to try and get some help with a recent BSOD issue I have been having. The blue screen only happens when my computer is in standby mode, I have never seen it while actually actively using it. It is a Dell XPS 15 that is only a few months old. Its running Windows 7 Pro x64. Here is the debugging file I get, I need a little help analyzing it.

Code:

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


Loading Dump File [C:\Users\wasknick\Desktop\061611-35739-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e1c000 PsLoadedModuleList = 0xfffff800`03061650
Debug session time: Thu Jun 16 00:36:26.796 2011 (UTC - 4:00)
System Uptime: 0 days 0:14:06.811
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8007ae6380, fffff80000b9c518, fffffa8007802760}

Probably caused by : ACPI.sys

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8007ae6380, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8007802760, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79294

MODULE_NAME: ACPI

FAULTING_MODULE: fffff88000ed8000 ACPI

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02f089c2 : 00000000`0000009f 00000000`00000003 fffffa80`07ae6380 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02ea7652 : fffff800`00b9c648 fffff800`00b9c648 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`02ea74f6 : fffffa80`0700cc68 fffffa80`0700cc68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02ea73de : 00000001`f8bd25cf fffff800`00b9cc58 00000000`0000d40a fffff800`030113c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02ea71c7 : 00000000`554501c5 00000000`0000d40a 00000000`55450145 00000000`0000000a : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02e93a2a : fffff800`0300ee80 fffff800`0301ccc0 00000000`00000002 fffff800`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_SynTP_IMAGE_ACPI.sys

BUCKET_ID:  X64_0x9F_3_SynTP_IMAGE_ACPI.sys

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

Thanks for the debugging but we need the actual DMP file to do more extensive analysis.

Please upload.

ALSO since it is a driver power state issue we want to find which driver by running driver verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

wasknick · Jun 18, 2011

wasknick said:

Hi everyone. I am new to this forum and am here to try and get some help with a recent BSOD issue I have been having. The blue screen only happens when my computer is in standby mode, I have never seen it while actually actively using it. It is a Dell XPS 15 that is only a few months old. Its running Windows 7 Pro x64. Here is the debugging file I get, I need a little help analyzing it.

Code:

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


Loading Dump File [C:\Users\wasknick\Desktop\061611-35739-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e1c000 PsLoadedModuleList = 0xfffff800`03061650
Debug session time: Thu Jun 16 00:36:26.796 2011 (UTC - 4:00)
System Uptime: 0 days 0:14:06.811
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8007ae6380, fffff80000b9c518, fffffa8007802760}

Probably caused by : ACPI.sys

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8007ae6380, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8007802760, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79294

MODULE_NAME: ACPI

FAULTING_MODULE: fffff88000ed8000 ACPI

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02f089c2 : 00000000`0000009f 00000000`00000003 fffffa80`07ae6380 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02ea7652 : fffff800`00b9c648 fffff800`00b9c648 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`02ea74f6 : fffffa80`0700cc68 fffffa80`0700cc68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02ea73de : 00000001`f8bd25cf fffff800`00b9cc58 00000000`0000d40a fffff800`030113c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02ea71c7 : 00000000`554501c5 00000000`0000d40a 00000000`55450145 00000000`0000000a : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02e93a2a : fffff800`0300ee80 fffff800`0301ccc0 00000000`00000002 fffff800`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_SynTP_IMAGE_ACPI.sys

BUCKET_ID:  X64_0x9F_3_SynTP_IMAGE_ACPI.sys

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

Here is the DMP file as well.

Once again, thanks for all the help with this.

wasknick · Jun 18, 2011

wasknick said:

Hi everyone. I am new to this forum and am here to try and get some help with a recent BSOD issue I have been having. The blue screen only happens when my computer is in standby mode, I have never seen it while actually actively using it. It is a Dell XPS 15 that is only a few months old. Its running Windows 7 Pro x64. Here is the debugging file I get, I need a little help analyzing it.

Code:

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


Loading Dump File [C:\Users\wasknick\Desktop\061611-35739-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e1c000 PsLoadedModuleList = 0xfffff800`03061650
Debug session time: Thu Jun 16 00:36:26.796 2011 (UTC - 4:00)
System Uptime: 0 days 0:14:06.811
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8007ae6380, fffff80000b9c518, fffffa8007802760}

Probably caused by : ACPI.sys

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8007ae6380, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8007802760, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79294

MODULE_NAME: ACPI

FAULTING_MODULE: fffff88000ed8000 ACPI

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02f089c2 : 00000000`0000009f 00000000`00000003 fffffa80`07ae6380 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02ea7652 : fffff800`00b9c648 fffff800`00b9c648 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`02ea74f6 : fffffa80`0700cc68 fffffa80`0700cc68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02ea73de : 00000001`f8bd25cf fffff800`00b9cc58 00000000`0000d40a fffff800`030113c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02ea71c7 : 00000000`554501c5 00000000`0000d40a 00000000`55450145 00000000`0000000a : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02e93a2a : fffff800`0300ee80 fffff800`0301ccc0 00000000`00000002 fffff800`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_SynTP_IMAGE_ACPI.sys

BUCKET_ID:  X64_0x9F_3_SynTP_IMAGE_ACPI.sys

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

Here is the DMP file. Once again, thanks for all the help with this.

zigzag3143 · Jun 18, 2011

My pleasure

This one was Related to Synaptics Touchpad Driver.. I would re-install with latest driver available.

wasknick · Jun 24, 2011

Well I updated the driver for the Synaptics touchpad and I thought it might have been resolved, but when I woke up this morning I found that I have had another blue screen in standby during the night. Any ideas why it might still be happening? I added the most recent dump file in case anything has changed.

BSOD while in standby

wasknick

New member

My Computer

zigzag3143

New member

My Computer

wasknick

New member

My Computer

wasknick

New member

My Computer

zigzag3143

New member

My Computer

wasknick

New member

My Computer