Frequent Annoying Blue Screen of Death

[technomann]

Data from Windows:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1000009f
BCP1: 0000000000000004
BCP2: 0000000000000258
BCP3: FFFFFA8006749B50
BCP4: FFFFF800050323D0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\122312-30529-01.dmp
C:\Users\Tom\AppData\Local\Temp\WER-63929-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


Data from WhoCrashed:

[FONT=Segoe UI, Arial]On Sun 12/23/2012 12:25:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122212-25272-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x81E7A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA800676CB50, 0xFFFFF80000B9C3D0)
Error: [FONT=Segoe UI, Arial]CUSTOM_ERROR[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]
If anyone has any insight into this problem I would welcome a solution.

Thank you!

 

[bagavan]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa8006749b50, fffff800050323d0}

*** WARNING: Unable to verify timestamp for FLxHCIh.sys
*** ERROR: Module load completed but symbols could not be loaded for FLxHCIh.sys
Implicit thread is now fffffa80`06749b50
Probably caused by : FLxHCIh.sys ( FLxHCIh+14b5e )

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8006749b50, The thread currently holding on to the Pnp lock.
Arg4: fffff800050323d0, nt!TRIAGE_9F_PNP on Win7

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

Implicit thread is now fffffa80`06749b50

DRVPOWERSTATE_SUBCODE:  4

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003491a32 to fffff8000349ee7a

STACK_TEXT:  
fffff880`03d5af80 fffff800`03491a32 : fffffa80`06749b50 fffffa80`06749b50 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`03d5b0c0 fffff800`034a2d8f : 00000000`00000308 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff880`03d5b150 fffff800`0378dfde : fffff880`03b17100 fffff800`00000006 00000000`00000000 fffffa80`06749b00 : nt!KeWaitForSingleObject+0x19f
fffff880`03d5b1f0 fffff800`0349b253 : fffffa80`06749b50 fffff880`08d6a2a8 00000000`00000000 fffffa80`0b962b50 : nt!NtWaitForSingleObject+0xde
fffff880`03d5b260 fffff800`03497810 : fffff880`08d6eb5e fffffa80`00000000 fffffa80`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`03d5b3f8 fffff880`08d6eb5e : fffffa80`00000000 fffffa80`00000000 00000000`00000000 fffffa80`0b962c58 : nt!KiServiceLinkage
fffff880`03d5b400 fffffa80`00000000 : fffffa80`00000000 00000000`00000000 fffffa80`0b962c58 00000000`0000012a : FLxHCIh+0x14b5e
fffff880`03d5b408 fffffa80`00000000 : 00000000`00000000 fffffa80`0b962c58 00000000`0000012a fffff880`08d6e666 : 0xfffffa80`00000000
fffff880`03d5b410 00000000`00000000 : fffffa80`0b962c58 00000000`0000012a fffff880`08d6e666 fffffa80`0c1892b0 : 0xfffffa80`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
FLxHCIh+14b5e
fffff880`08d6eb5e ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  FLxHCIh+14b5e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: FLxHCIh

IMAGE_NAME:  FLxHCIh.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc2a879

FAILURE_BUCKET_ID:  X64_0x9F_4_FLxHCIh+14b5e

BUCKET_ID:  X64_0x9F_4_FLxHCIh+14b5e

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

update this

Fresco Logic xHCI USB 3.0 Hub Device Driver - OEM ONLY; none at - FRESCO LOGIC INC.===Leap into SuperSpeed===


Computer Manufacturers' Contact Information

 

[technomann]

---------

[/CODE]update this

Fresco Logic xHCI USB 3.0 Hub Device Driver - OEM ONLY; none at - FRESCO LOGIC INC.===Leap into SuperSpeed===


Computer Manufacturers' Contact Information

I ran Driver Detective and Fresco Logic xHCI USB 3.0 Hub Device Driver was one of many outdated drivers. I updated it and the others and haven't had any more crashes.

Thanks!!!

 

[bagavan]

Good news.