Solved BSOD Win7 x64 BugCheck 9F

emfurry

New member
Local time
10:40 AM
Messages
3
Location
Philadelphia
Hi, first time post. I hope to get help with a reoccurring crash. Here are my basic PC stats:

* Windows 7 Professional x64
* Original OS was Windows 7 Home Premium x64, has been upgraded with Windows Anytime Upgrade
* The original OS was OEM
* Hardware is about 1 year old
* OS is about 1 year old
* System is a Dell Studio XPS 8100

The crash symptoms are as such:
* it only occurs when I do a sleep (and perhaps also a hibernate, not sure)
* it is intermittent, but more often than once per month
* the computer enters sleep correctly, but once in sleep it occasionally will reboot itself due to a bugcheck 9F, typically after several hours
* the computer can exit sleep properly if it has not already crashed
* the computer is stable with no other types of crashes; that is, if I avoid the sleep and hibernate features I do not have any crashes or problems.
* the computer has been patched fully on Windows Update
* despite the informational message in the perfmon report to the contrary, I have Microsoft Security Essentials running and up to date
* I have no other symptoms of viruses or malware

I tried loading the dump in WinDbg which implicated usbccgp.sys, but do not know how to proceed from there or whether that driver is in fact the root cause.

I would greatly appreciate any help since I would love to use the sleep feature of my computer!

Eric
 

My Computer My Computer

OS
Windows 7 Professional x64
Your Logitech webcam driver is the cause, please update it
Support + Downloads

The driver it uses it obsolete
Code:
lvpopf64.sys        fffff880`044b1000    fffff880`045fbd00    0x0014ad00    0x464502a5    12/05/2007 03:56:21                
lvuvc64.sys        fffff880`06020000    fffff880`06390500    0x00370500    0x46450350    12/05/2007 03:59:12                
LVUSBS64.sys        fffff880`02ff5000    fffff880`02fff900    0x0000a900    0x464503d0    12/05/2007 04:01:20

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800b854a00, fffff80000b9c518, fffffa8007f88a60}

*** WARNING: Unable to verify timestamp for lvuvc64.sys
*** ERROR: Module load completed but symbols could not be loaded for lvuvc64.sys
Probably caused by : lvuvc64.sys


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: fffffa800b854a00, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8007f88a60, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8007f88a60

DEVICE_OBJECT: fffffa800b893350

DRIVER_OBJECT: fffffa800a7d7e70

IMAGE_NAME:  lvuvc64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  46450350

MODULE_NAME: lvuvc64

FAULTING_MODULE: fffff88006020000 lvuvc64

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000313bcd2 to fffff800030cdc40

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`0313bcd2 : 00000000`0000009f 00000000`00000003 fffffa80`0b854a00 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`030d95fc : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`030d9496 : fffffa80`0bb18710 fffffa80`0bb18710 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`030d937e : 0000006c`71edc95e fffff800`00b9cc58 00000000`002d8ec8 fffff800`03247b88 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`030d9167 : 0000001d`944426c2 0000001d`002d8ec8 0000001d`9444265d 00000000`000000c8 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`030c596a : fffff800`03243e80 fffff800`03251cc0 00000000`00000002 fffff880`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_IMAGE_lvuvc64.sys

BUCKET_ID:  X64_0x9F_IMAGE_lvuvc64.sys

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

My Computer My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom Build
OS
Windows 10 Pro x64, Arch Linux
CPU
Intel Core 2 Quad Q8200 OC'd 3.08GHz
Motherboard
Asus Rampage formula LGA775
Memory
8GB DDR2 900Mhz
Graphics Card(s)
MSI GT730 2GB GDDR5 (Kepler)
Sound Card
Supreme FX2
Monitor(s) Displays
Samsung LS22F350 LED
Screen Resolution
1080P
Hard Drives
Kingston SSDNow UV400 120GB, 500GB Hitachi, 2TB Samsung, 500GB Seagate FreeAgent, 640GB Samsung, 160GB Toshiba (Arch)
PSU
AeroCool 500W Bronze
Cooling
Cooler Master V6 + 3X fans
Keyboard
Prolink keyboard
Mouse
Logitech M705
Internet Speed
1MiB/s
Browser
Chrome Beta
Thanks! I will try that and post back here if I do not experience any problems after a week or two.

Also, I would like to learn how to make these determinations. I know you don't have time to tell me all there is about reading memory dumps, but do you have any quick tips about how you were able to find the culprit so quickly? If you used WinDbg, what command and result pointed you toward the Logitech driver? Thanks!
 

My Computer My Computer

OS
Windows 7 Professional x64
Thanks! I will try that and post back here if I do not experience any problems after a week or two.

Also, I would like to learn how to make these determinations. I know you don't have time to tell me all there is about reading memory dumps, but do you have any quick tips about how you were able to find the culprit so quickly? If you used WinDbg, what command and result pointed you toward the Logitech driver? Thanks!
In WinDBG using the !analyze -v command the faulting driver, lvuvc64.sys belonging to the logitech webcam driver was identified as the cause of BSODs
 

My Computer My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom Build
OS
Windows 10 Pro x64, Arch Linux
CPU
Intel Core 2 Quad Q8200 OC'd 3.08GHz
Motherboard
Asus Rampage formula LGA775
Memory
8GB DDR2 900Mhz
Graphics Card(s)
MSI GT730 2GB GDDR5 (Kepler)
Sound Card
Supreme FX2
Monitor(s) Displays
Samsung LS22F350 LED
Screen Resolution
1080P
Hard Drives
Kingston SSDNow UV400 120GB, 500GB Hitachi, 2TB Samsung, 500GB Seagate FreeAgent, 640GB Samsung, 160GB Toshiba (Arch)
PSU
AeroCool 500W Bronze
Cooling
Cooler Master V6 + 3X fans
Keyboard
Prolink keyboard
Mouse
Logitech M705
Internet Speed
1MiB/s
Browser
Chrome Beta
Just posting back that this was the problem, I uninstalled drivers and haven't had the problem since. Solved! Thanks!!
 

My Computer My Computer

OS
Windows 7 Professional x64
Back
Top