Windows 7 2 months of freezes leads to my first BSOD

designcoup

New Member
Joined
Feb 7, 2012
Messages
2
Hi all,

This is a relatively new Win 7 64 bit that has given random freezes every single day since a new PC two months ago.

Today, I received my first BSOD. Nothing intense running at the time (Outlook, Browser, Word).

I have attached the minidump file for help in finding possible clues to the issues.

Thanks,
Bruce
 


Attachments

Solution
Hello and welcome to the forum.
A single dump file is not a whole lot to go on.
SUMMARY:
Code:
BugCheck 9F, {3, fffffa800d663a00, fffff800049dd518, fffffa80108d5710}
Probably caused by : usbccgp.sys
[COLOR=#ff0000][U][B]DRIVER_POWER_STATE_FAILURE (9f)[/B][/U][/COLOR]
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: fffffa800d663a00, Physical Device Object of the stack
Arg3: fffff800049dd518, Functional Device Object of the stack
Arg4: fffffa80108d5710, The blocked IRP
The driver being blamed usbccgp.sys (USB Common Class Generic Parent Driver) is a Microsoft System File and unlikely the true culprit. However; it may be something that you have attached...
Hello and welcome to the forum.
A single dump file is not a whole lot to go on.
SUMMARY:
Code:
BugCheck 9F, {3, fffffa800d663a00, fffff800049dd518, fffffa80108d5710}
Probably caused by : usbccgp.sys
[COLOR=#ff0000][U][B]DRIVER_POWER_STATE_FAILURE (9f)[/B][/U][/COLOR]
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: fffffa800d663a00, Physical Device Object of the stack
Arg3: fffff800049dd518, Functional Device Object of the stack
Arg4: fffffa80108d5710, The blocked IRP
The driver being blamed usbccgp.sys (USB Common Class Generic Parent Driver) is a Microsoft System File and unlikely the true culprit. However; it may be something that you have attached??
So....
First make sure your machine is configured properly to facilitate the collection of .dmp files.
Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be found later
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
Then:
Please read the first post in this sticky thread here Link Removed
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 Link Removed .
Good luck
Randy
 


Solution
Back
Top