Windows 7 BSOD driver power state failure on standby

[mpollard]

View attachment Seven Forums.zip

After closing lid on Dell XPS 15, every once and a while when come back to computer, seems to have crashed while on standby, or perhaps when it woke from standby to go into hibernation?

minidump files attached. All stock hardware, per below.

many thanks for any help you can offer!


Item Value
OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name MATT-XPS
System Manufacturer Dell Inc.
System Model Dell System XPS L502X
System Type x64-based PC
Processor Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz, 2301 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date Dell Inc. A10, 20/02/2012
SMBIOS Version 2.6
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume2
Locale United Kingdom
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name Matt-XPS\Matt
Time Zone GMT Daylight Time
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 3.90 GB
Available Physical Memory 1.78 GB
Total Virtual Memory 7.79 GB
Available Virtual Memory 5.61 GB
Page File Space 3.90 GB
Page File C:\pagefile.sys

[Hardware Resources]



[Conflicts/Sharing]

Resource Device
I/O Port 0x00000000-0x0000001F Direct memory access controller
I/O Port 0x00000000-0x0000001F PCI bus

Memory Address 0xF0000000-0xF10FFFFF 2nd generation Intel® Core™ processor family PCI Express Controller - 0101
Memory Address 0xF0000000-0xF10FFFFF NVIDIA GeForce GT 525M

I/O Port 0x00000070-0x00000077 System CMOS/real time clock
I/O Port 0x00000070-0x00000077 Motherboard resources

I/O Port 0x00002000-0x00002FFF Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 6 - 1C1A
I/O Port 0x00002000-0x00002FFF Realtek PCIe GBE Family Controller

Memory Address 0xF1B00000-0xF1BFFFFF Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 2 - 1C12
Memory Address 0xF1B00000-0xF1BFFFFF Intel(R) WiFi Link 1000 BGN

IRQ 16 Intel(R) Management Engine Interface
IRQ 16 Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 5 - 1C18
IRQ 16 2nd generation Intel® Core™ processor family PCI Express Controller - 0101
IRQ 16 NVIDIA GeForce GT 525M
IRQ 16 Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 1 - 1C10
IRQ 16 Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C2D

IRQ 17 Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 2 - 1C12
IRQ 17 Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 6 - 1C1A

Memory Address 0xA0000-0xBFFFF PCI bus
Memory Address 0xA0000-0xBFFFF Intel(R) HD Graphics Family

Memory Address 0xF1800000-0xF18FFFFF Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 6 - 1C1A
Memory Address 0xF1800000-0xF18FFFFF Realtek PCIe GBE Family Controller

Memory Address 0xC0000000-0xD1FFFFFF 2nd generation Intel® Core™ processor family PCI Express Controller - 0101
Memory Address 0xC0000000-0xD1FFFFFF NVIDIA GeForce GT 525M

IRQ 19 Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 4 - 1C16
IRQ 19 Intel(R) Mobile Express Chipset SATA AHCI Controller

Memory Address 0xF1A00000-0xF1A01FFF Renesas Electronics USB 3.0 Host Controller
Memory Address 0xF1A00000-0xF1A01FFF Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 4 - 1C16

 

[Trouble]

Hello and welcome to the forum.
All of your most recent dump files are identical.
It seems that your Touch Pad driver is having issues with a power configuration present on your laptop.

BugCheck 9F, {3, fffffa8003c7c5c0, fffff80000b9c3d8, fffffa80048f38d0}
*** WARNING: Unable to verify timestamp for   [COLOR=#ff0000][B]SynTP.sys[/B][/COLOR]  
  *** ERROR: Module load completed but symbols could not be loaded for [COLOR=#ff0000][U][B]SynTP.sys[/B][/U][/COLOR]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[COLOR=#ff0000][U][B]Probably caused by : SynTP.sys[/B][/U][/COLOR]
DRIVER_POWER_STATE_FAILURE (9f)
[COLOR=#ff0000][U][B]A driver is causing an inconsistent power state.[/B][/U][/COLOR]
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8003c7c5c0, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa80048f38d0, The blocked IRP
DRVPOWERSTATE_SUBCODE:  3
IRP_ADDRESS:  fffffa80048f38d0
DEVICE_OBJECT: fffffa800711c040
DRIVER_OBJECT: fffffa8007075a30
IMAGE_NAME:       [COLOR=#ff0000][B]SynTP.sys[/B][/COLOR]     
DEBUG_FLR_IMAGE_TIMESTAMP:  4d0b9501
     MODULE_NAME: [COLOR=#ff0000][U][B]SynTP[/B][/U][/COLOR]
FAULTING_MODULE: fffff88004691000 [COLOR=#ff0000][U][B]SynTP[/B][/U][/COLOR]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff800036ef702 to fffff800036851c0
STACK_TEXT:  
fffff800`00b9c388 fffff800`036ef702 : 00000000`0000009f 00000000`00000003 fffffa80`03c7c5c0 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`0368fe4c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x34050
fffff800`00b9c430 fffff800`0368fce6 : fffffa80`08805c10 fffffa80`08805c10 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`0368fbce : 00000380`f2dba631 fffff800`00b9cb18 00000000`0178ceda fffff800`037fbdc8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`0368f9b7 : 000000c8`f3960ac4 000000c8`0178ceda 000000c8`f3960a84 00000000`000000da : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`0367ceca : fffff800`037f7e80 fffff800`03805cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_[COLOR=#ff0000][U][B]SynTP.sys[/B][/U][/COLOR]
[COLOR=#ff0000][/COLOR]BUCKET_ID:  X64_0x9F_IMAGE_[COLOR=#ff0000][U][B]SynTP.sys[/B][/U][/COLOR]

SynTP.sys 12/17/2010 there is what I believe to be a slightly more recent driver here from the manufacturer Drivers | Synaptics SynTP.sys 03/11/2011

These types of energy saving issues resulting in BSODs are never easy to solve. They can be anything from the Laptop Mfg's own power utility conflicting with Windows 7''s native power configuration, to something called C-states or C-modes in the BIOS utility, on Intel boards, which I usually suggest disabling or turning off. They can also be related in certain instances to systems temps which may or may not be related to overclocking of CPU, Memory or Graphics.
I suggest you familiarize yourself with the native windows power options as well as the Powercfg utility and see if it reveals any helpful information. The links below may prove useful.
How Do I: Use PowerCfg in Windows 7?
Learning Windows 7: Manage Power Settings - How-To Geek
How Do I: Use PowerCfg in Windows 7?
Use PowerCfg in Windows 7 to Evaluate Power Efficiency - How-To Geek

If Blue Screens persist;
Please read the first post in this sticky thread here How to ask for help with a BSOD problem
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Additionally, if you haven’t already, please take some time and fill out your system specs in your forum profile area http://windows7forums.com/windows-7...you-filling-your-system-specs.html#post235529 .
Good luck
Randy