Windows 8 BSOD DRIVER_POWER_STATE_FAILURE

*******************************************************************************
* *
* 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: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8008ba1620, Physical Device Object of the stack
Arg3: fffff8026f5967f0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800daf3010, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: usbccgp.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5010aafa

MODULE_NAME: usbccgp

FAULTING_MODULE: fffff88004e37000 usbccgp

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

TAG_NOT_DEFINED_c000000f: FFFFF8026F59CFB0

STACK_TEXT:
fffff802`6f5967b8 fffff802`7039c202 : 00000000`0000009f 00000000`00000003 fffffa80`08ba1620 fffff802`6f5967f0 : nt!KeBugCheckEx
fffff802`6f5967c0 fffff802`7039c241 : fffffa80`0eec7a10 fffffa80`0eb781f0 fffff802`6f596939 fffff802`7032a050 : nt!PopIrpWatchdogBugcheck+0xe2
fffff802`6f596820 fffff802`7028900a : fffffa80`0eb781f0 fffff802`6f596939 00000000`00000001 fffff880`02ad1180 : nt!PopIrpWatchdog+0x32
fffff802`6f596870 fffff802`70287475 : 00000000`00000000 fffff802`70288b1f 00000000`00140001 fffff802`70502a20 : nt!KiProcessExpiredTimerList+0x22a
fffff802`6f5969a0 fffff802`70289488 : fffff802`704fe180 fffff802`70500f80 00000000`0000000d 00000000`00149fad : nt!KiExpireTimerTable+0xa9
fffff802`6f596a40 fffff802`70288826 : fffffa80`00000000 00001fa0`004f0080 00000000`00000000 00000000`00000002 : nt!KiTimerExpiration+0xc8
fffff802`6f596af0 fffff802`702897da : fffff802`704fe180 fffff802`704fe180 00000000`001a3db0 fffff802`70558880 : nt!KiRetireDpcList+0x1f6
fffff802`6f596c60 00000000`00000000 : fffff802`6f597000 fffff802`6f591000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x9F_3_mausbmp_IMAGE_usbccgp.sys

BUCKET_ID: 0x9F_3_mausbmp_IMAGE_usbccgp.sys




!DevObj !DrvObj !DevExt ObjectName
fffffa8008b65910 \Driver\ksthunk fffffa8008b65a60 InfoMask field not found for _OBJECT_HEADER at fffffa8008b658e0

> fffffa8008a5b040 Unable to load image \SystemRoot\system32\DRIVERS\mausbmp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mausbmp.sys
*** ERROR: Module load completed but symbols could not be loaded for mausbmp.sys
\Driver\MAUSBMP fffffa8008a5b1b0 InfoMask field not found for _OBJECT_HEADER at fffffa8008a5b010

fffffa8008ba1620 \Driver\usbccgp fffffa8008ba1770 Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode fffffa8008bb2d30 :
DeviceInst is "USB\VID_0763&PID_200F&MI_00\6&5dc2b50&0&0000"
ServiceName is "MAUSBMP"





Loaded symbol image file: mausbmp.sys
Image path: \SystemRoot\system32\DRIVERS\mausbmp.sys
Image name: mausbmp.sys
Timestamp: Mon Feb 09 18:37:49 2009


------------------------------------------------------------------------------------------------------------------------------------------------

"A programmer is just a tool which converts caffeine into code"

What USB devices are pluged in? are you using the latest drivers?

mausbmp.sys is the associated file of mausbmp.sys error which has been categorized as a serious system error. The undesirable system error has the power to lead to further complicated system problems, including unexpected Blue Screen of Death errors, network connection problems, deterioration of network performance, Black Screen of Death pops- up, inexplicable loss of computer performance and system security problem. Due to the fact that the file plays a crucial role in Windows operating system, the undesirable associated error can not be easily repaired through system utilities.

Install the latest drivers

This issue is almost always due to a driver issue with one of the devices installed in your computer. If you've recently installed a new hardware device, such as a printer, modem, video card, etc., make sure you've got the latest drivers from the manufacturer's web site.
A listing of driver manufacturer web pages can be found on our driver section.
Disconnect external devices

Disconnect all external devices. External hardware such as USB peripherals can cause this error to happen. If no errors occur while these devices are disconnected, visit the manufacturers web site for the latest drivers or contact the hardware manufacturer for suggestions.
Verify all drivers have proper digital signatures

Out of date drivers for hardware devices, or system utilities that run in the background, such as backup software, antivirus scanners, etc., can also cause this issue to occur. To verify if your system has any of these files follow the below steps.
Click Start
In the Run line type sigverif and press enter.
This should open the Windows File Signature Verification utility that can scan for files without a digital signature.
If you need help identifying what a file is or what it's associated with enter the full file name into the Computer Hope log tool.
Disable BIOS APM

Make sure that the Advanced Power Management (APM) is disabled within CMOS setup.
Motherboard BIOS update

If none of the above suggestions have helped resolve your issue visit the motherboard manufacturers or computer manufacturers web site and see if your motherboard has any available BIOS updates.
Additional information and help with BIOS updates.
Bad hardware

Finally, if you've tried all of the above suggestions and are sure this issue is not a driver related issue, bad hardware can cause a wide variety of issues including this one. We suggest first that you test the memory in the computer to verify it's not bad. If not bad, start trying to isolate the bad hardware by doing the process of elimination.

Use Malware Bytes and stay Safe
Good programme and i personally usi it

Better to scan because they also cause some problems in mine

a BSoD doesn’t mean that your computer is broken beyond repair — it just means it encountered something that it didn’t know how to interpret. Sometimes you never encounter the problem again, but other times it persists, possibly even to the point where you can’t use your computer. Since you took the care to document your error, we’re likely dealing with the latter, so here we go.


What is DRIVER_POWER_STATE_FAILURE?

This particular Blue Screen, DRIVER_POWER_STATE_FAILURE (also known as 0x0000009F), is (usually) encountered due to driver errors encountered when, say, you put your computer to sleep or take it out of sleep. Drivers are instructions given by your device to tell your computer how to interact with them — your keyboard’s driver is what registers the keys you tap as letters to appear on your screen. Drivers are for peripherals and nearly every part of your computer. The motherboard, however, has a BIOS, which is just as important to keep updated as your device drivers.
How do I fix DRIVER_POWER_STATE_FAILURE?

If on a laptop, find the name of your laptop and the appropriate BIOS update for it. If on a desktop, find your model or look at the packaging of your motherboard to determine where you can find the manufacturer’s website and upgrade your BIOS. If your BIOS is fully upgraded or updating it didn’t fix your problem, continue reading.
For driver updates, you have three choices: use the Device Manager, found in the Control Panel in all versions of Windows, and individually update your drivers from there. You can also search online manually for your driver updates or use our Driver Reviver software to save yourself the trouble.
If upgrading the BIOS and drivers still hasn’t resolved your problem, then there may very well be a problem with your operating system installation (especially if you’re using Windows 8) or the hardware itself.
To fix these problems, consult Microsoft’s tech support