Solved Had a BSOD, ntoskrnl.exe problem or something.

[Vextor]

I had a BSOD today, I just want to check if it's a permanent problem or a one-time BSOD. I'm going to post all the information I know from checking on a program called BlueScreenView.

Dump File : 020512-21278-01.dmp
Crash Time : 05/02/2012 12:35:00
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`08984a00
Parameter 3 : fffff800`00b9c4d8
Parameter 4 : fffffa80`0b2eebd0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\020512-21278-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601

 

[Nathan Wootton]

Well, i think its your RAM that may have gone bad if you google the error code its mostly about ram and PSU. so Right, can you do these test for me....

1. chkdsk c: /r to eliminate bad sectors / failing HDD
2. Memtest+ 86 and leave it running
3. Swapping out PSU ?

 

[acuariano]

remove the battery for like 10 minutes and then reinstall it...
this may clear it

 

[Vextor]

remove the battery for like 10 minutes and then reinstall it...
this may clear it

I'm on a desktop.

 

[Valentin N]

have you analysed the dump file?

 

[pcjunklist]

I would out all ram but 1 stick and try again
You could try a driver verifier http://www.techsupportforum.com/forums/showpost.php?p=2670109
And you could check you system files http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Its usually a memory or driver issue




Go Pats!

 

[Prorootect]

Can be a bad contact somewhere .. Cleans the dust and moves a little all connectors.

 

[Vextor]

have you analysed the dump file?

Well, the information above is all I know of the problem.

 

[Valentin N]

have you analysed the dump file?

Well, the information above is all I know of the problem.

Analyzing the dump file will point which exe file is causing problem. I will ask a person to show me how to analyze it.

 

[Vextor]

have you analysed the dump file?

Well, the information above is all I know of the problem.

Analyzing the dump file will point which exe file is causing problem. I will ask a person to show me how to analyze it.

I did something with WinDBG and I got this log:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\020612-16598-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`049eb4c0?
Symbol search path is: srv*C:\SymbolCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0341d000 PsLoadedModuleList = 0xfffff800`03662670
Debug session time: Mon Feb 6 21:16:09.263 2012 (UTC + 0:00)
System Uptime: 0 days 15:30:38.964
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8008c82a00, fffff800049eb4d8, fffffa800adf07c0}

Probably caused by : usbccgp.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: fffffa8008c82a00, Physical Device Object of the stack
Arg3: fffff800049eb4d8, Functional Device Object of the stack
Arg4: fffffa800adf07c0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: usbccgp.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c0a

MODULE_NAME: usbccgp

FAULTING_MODULE: fffff88009aeb000 usbccgp

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff800`049eb488 fffff800`03507cd2 : 00000000`0000009f 00000000`00000003 fffffa80`08c82a00 fffff800`049eb4d8 : nt!KeBugCheckEx
fffff800`049eb490 fffff800`034a55fc : fffff800`049eb5d8 fffff800`049eb5d8 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`049eb530 fffff800`034a5496 : fffff880`0c8cda90 fffff880`0c8cda90 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`049eb5a0 fffff800`034a537e : 00000082`029dc88d fffff800`049ebc18 00000000`00369e05 fffff800`03612328 : nt!KiProcessExpiredTimerList+0xc6
fffff800`049ebbf0 fffff800`034a5167 : 00000025`fe75cbc4 00000025`00369e05 00000025`fe75cb1f 00000000`00000005 : nt!KiTimerExpiration+0x1be
fffff800`049ebc90 fffff800`0349196a : fffff800`0360fe80 fffff800`0361dcc0 00000000`00000000 fffff880`02edc588 : nt!KiRetireDpcList+0x277
fffff800`049ebd40 00000000`00000000 : fffff800`049ec000 fffff800`049e6000 fffff800`049ebd00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_RTL2832UUSB_IMAGE_usbccgp.sys

BUCKET_ID: X64_0x9F_3_RTL2832UUSB_IMAGE_usbccgp.sys

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

 

[Valentin N]

looks like you found the source: usbccgp.sys

 

[Vextor]

looks like you found the source: usbccgp.sys

Ok, do you have any idea what I should do about it? It has happened again and I want a fix.

 

[pcjunklist]

what hardware have you recently added to your computer via usb? Like a printer or a new keyboard? Reinstall that driver. Open the run command type in devmgmt.msc look for any yellow explanation points

 

[Vextor]

what hardware have you recently added to your computer via usb? Like a printer or a new keyboard? Reinstall that driver. Open the run command type in devmgmt.msc look for any yellow explanation points

I haven't added any hardware via USB, apart from an iPod cable, which has been in for 3 weeks now. Device Manager shows no ! marks, meaning I have no device problem.
So that I don't know.

 

[Valentin N]

From what I see this is attached to usb.

When do you get this bsod? here is info

 

[Gnosis]

What I am going to say is just a shot in the dark, but what if it is exlusively to do with the USB port itself? Is that possible?

 

[pcjunklist]

If you have an Intel CPU,

Install the latest java which is 6 (java.com)

Run the Intel driver utility to see if it has any updates for your system
http://www.intel.com/p/en_US/support/detect

 

[malbky]

I had this problem due to a faulty motherboard. After that later i again got a bsod on my new motherboard. This time it was due to Avast and Online armor firewall. Use BlueScreen viewer by nirsoft, which will show all affected drivers.

 

[Vextor]

If you have an Intel CPU,

Install the latest java which is 6 (java.com)

Run the Intel driver utility to see if it has any updates for your system
http://www.intel.com/p/en_US/support/detect

I have Java 7.

 

[Vextor]

I had this problem due to a faulty motherboard. After that later i again got a bsod on my new motherboard. This time it was due to Avast and Online armor firewall. Use BlueScreen viewer by nirsoft, which will show all affected drivers.

If you check the first page, I did use the viewer and I posted all the Data there.
Also go-ahead and check the bottom of the page, where I posted a Debug from WinDBG.