Windows 7: BSOD random shutdowns

olsonfamily · 12 Mar 2012

PC just shuts off with no apparent pattern. Please help - files attached

zigzag3143 · 12 Mar 2012

Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST

http://us.norton.com/support/kb/web_...080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows

* Did you run a FULL SYSTEM scan with Malwarebytes?

olsonfamily · 24 Mar 2012

any other suggestion beside unistalling Norton - I did disable temporarily but still got the issue... and still get a BSOD 1-3 times a day - very frustrating!

writhziden · 24 Mar 2012

Re-enable Norton so you are fully protected and please upload your latest crash reports.

Also, what version of Norton are you using; is it up to date and a 2012 version?

olsonfamily · 10 Apr 2012

Sorry for the tardy reply - I have been out of town.

BSOD seems to happen when away from computer only - not sure if in sleep mode yet or not.

THANKS much for looking into this

writhziden · 10 Apr 2012

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\olsonfamily\Windows_NT6_BSOD_jcgriff2\041012-15506-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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 Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02a15000 PsLoadedModuleList = 0xfffff800`02c59650
Debug session time: Mon Apr  9 20:42:31.674 2012 (UTC - 6:00)
System Uptime: 0 days 2:38:38.517
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800c9aa930, fffff80000b9c3d8, fffffa800db2f2f0}

Probably caused by : hidusb.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: fffffa800c9aa930, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa800db2f2f0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa800db2f2f0

DEVICE_OBJECT: fffffa800c9feb30

DRIVER_OBJECT: fffffa800c9e0aa0

IMAGE_NAME:  hidusb.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665

MODULE_NAME: hidusb

FAULTING_MODULE: fffff880079cd000 hidusb

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00b9c388 fffff800`02aff192 : 00000000`0000009f 00000000`00000003 fffffa80`0c9aa930 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`02a9ca6c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34040
fffff800`00b9c430 fffff800`02a9c906 : fffffa80`0d218af8 fffffa80`0d218af8 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`02a9c7ee : 00000016`297a8b69 fffff800`00b9cb18 00000000`00094f6d fffff800`02c0a028 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`02a9c5d7 : 00000007`578662c4 00000007`00094f6d 00000007`5786621c 00000000`0000006d : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02a89a6a : fffff800`02c06e80 fffff800`02c14cc0 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_3_IMAGE_hidusb.sys

BUCKET_ID:  X64_0x9F_3_IMAGE_hidusb.sys

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

The problem appears to be caused by a USB device or the USB ports themselves. It could also be Bluetooth causing these types of crashes.

Start with USB Driver - General Fix for Problems to resolve the USB issues. Also, USB ports can sometimes enter a safe power state to protect the system from power surges due to USB devices. To reset the USB ports to a nominal power state:
1. Shut down and turn off the computer.
2. Unplug the computer from the wall or surge protector (then remove the battery if it is a laptop).
3. "Remove the computer from any port replicator or docking station, disconnect
  cables to printers or devices such as external monitors, USB memory sticks or SD cards,
  headset or external speakers, mouse or auxiliary keyboard, turn off WIFI and Bluetooth
  wireless devices." (Use Hard Reset to Resolve Hardware and Software Issues HP Pavilion dv5000 Notebook PC series - HP Customer Care (United States - English))
4. Hold down the power button for 30 seconds. This closes the circuit and ensures all
  power from components is drained to clear the software connections between the BIOS
  and hardware and clear any corruption in the temporary memory.
5. (If it is a laptop, plug the battery back into the laptop and then) Plug the computer back into the wall. Do not reconnect any unnecessary peripherals; monitor, keyboard,
  and mouse should suffice and be the only peripherals reconnected.
6. Turn it on to reinitialize the software connections between the BIOS and hardware

Windows 7: BSOD random shutdowns

BSOD random shutdowns problems?