Random BSOD Bugcheck code: 0xA0 (0x1, 0x6, 0xFFFFFA800835ACF0, 0x0)

Hi everybody, this is my first post here and I don't know a whole lot this kind of stuff just as an FYI. Anyways, 2 months ago I had a customized rig put together by a computer shop and it was fine up until about a week ago. At first it started stuttering at random times, everything would get really choppy, sometimes the audio would completely cut out and the only thing I could do was using the mouse (nothing I clicked on would respond). A quick restart would fix it but lately the computer has been crashing about once a day. The last 2 crashes have happened when it was not even in use (I usually leave the computer on 24/7, so I would come back and my computer would either be completely shut off or at the log in screen for windows). I have run different diagnostic tools but I don't know how to interpret any of it. Ive attached the SF debug tool in hopes someone here could help me.

Computer specs:
Intel i5-4670K 3.4GHz
8GB ram
Windows 7 64 bit

If you need any other info from me please let me know. Thanks.

Hi unally.

The issue is: The system has failed to allocate a necessary power IRP.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 0000000000000001, Error Handling power IRP.
Arg2: 0000000000000006, The system has failed to allocate a necessary power irp.
Arg3: fffffa800844bcf0, target device object
Arg4: 0000000000000000, system power irp

Some results I am obtaining from the dump that I am not aware of. Like .....

Code:

IoStatus.Status = 00002044: The preset referral limit was exceeded.

Still, if it is a desktop computer (it seems to be, from the original post), disable hibernate.

If still the situation is the same, change the mouse.

Code:

 [ 78,cc]  73  b fffff880044d4338 fffff880044d428c fffff880044d4200-fffff880044d417c    pending
          fffff880044d4338: is not a device object
    mouclass!MouseClassSetWmiDataBlock

If it is still the same, get the PSU replaced.

Let us know the results.
__________________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A0, {1, 6, fffffa800835acf0, 0}

Probably caused by : ntkrnlmp.exe ( nt!PopAllocateIrp+d0 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 0000000000000001, Error Handling power IRP.
Arg2: 0000000000000006, The system has failed to allocate a necessary power irp.
Arg3: fffffa800835acf0, target device object
Arg4: 0000000000000000, system power irp

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


BUGCHECK_STR:  0xA0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80002d83550 to fffff80002c7cbc0

STACK_TEXT:  
fffff880`031e04a8 fffff800`02d83550 : 00000000`000000a0 00000000`00000001 00000000`00000006 fffffa80`0835acf0 : nt!KeBugCheckEx
fffff880`031e04b0 fffff800`02ec95e8 : 00000000`00000005 00000000`00000003 00000000`00000028 fffffa80`00000000 : nt!PopAllocateIrp+0xd0
fffff880`031e0530 fffff800`02ec9928 : fffffa80`00000002 fffffa80`083568b8 fffffa80`0a5aea20 fffffa80`0a5ae810 : nt!PopNotifyDevice+0x88
fffff880`031e0580 fffff800`02ecb88f : 00000000`00000006 00000000`00000000 fffff880`031e0700 fffffa80`0a5ae810 : nt!PopSleepDeviceList+0x148
fffff880`031e0650 fffff800`02ecbb7c : 00000000`00000004 00000000`00000006 00000000`00000000 00000000`00000001 : nt!PoBroadcastSystemState+0x27f
fffff880`031e06e0 fffff800`02ecd7f7 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000004 : nt!PopSetDevicesSystemState+0x7c
fffff880`031e0730 fffff800`02c7be53 : fffffa80`06702b50 00000000`00000000 00000000`00000000 fffff800`02c83900 : nt!NtSetSystemPowerState+0x467
fffff880`031e0870 fffff800`02c78410 : fffff800`030ee3b0 00000000`00000000 fffff800`02e22200 fffff800`02e22200 : nt!KiSystemServiceCopyEnd+0x13
fffff880`031e0a08 fffff800`030ee3b0 : 00000000`00000000 fffff800`02e22200 fffff800`02e22200 00000000`00000000 : nt!KiServiceLinkage
fffff880`031e0a10 fffff800`030ee58c : 00000000`00000007 fffff800`02e22200 00000000`00000002 00000000`00000004 : nt!PopIssueActionRequest+0x280
fffff880`031e0aa0 fffff800`02c35315 : 00000000`00000001 fffffa80`06702b00 fffffa80`193746e0 00000000`00000000 : nt!PopPolicyWorkerAction+0x4c
fffff880`031e0b00 fffff800`02c86261 : fffff800`00000002 fffff800`00000004 fffff800`02c35218 00000000`00000000 : nt!PopPolicyWorkerThread+0xfd
fffff880`031e0b70 fffff800`02f192ea : 00000000`00000000 fffffa80`06702b50 00000000`00000080 fffffa80`066f0990 : nt!ExpWorkerThread+0x111
fffff880`031e0c00 fffff800`02c6d8e6 : fffff880`02f65180 fffffa80`06702b50 fffff880`02f6ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031e0c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PopAllocateIrp+d0
fffff800`02d83550 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PopAllocateIrp+d0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

IMAGE_VERSION:  6.1.7601.18247

FAILURE_BUCKET_ID:  X64_0xA0_nt!PopAllocateIrp+d0

BUCKET_ID:  X64_0xA0_nt!PopAllocateIrp+d0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa0_nt!popallocateirp+d0

FAILURE_ID_HASH:  {2429636e-015f-b688-d6ad-e59ada7a8e26}

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

There are ways, but those are risky.

• PSU - Test DC Output Voltage
• PSU - Jump Start

   Warning

This could damage your PSU if done incorrectly, and poses an electrical shock risk. Always take the appropriate cautions when working with electrical parts. The PSU EVEN WHEN TURNED OFF has enough power to SEVERELY INJURE OR KILL YOU.

The mouse does not contribute in power supply, but like all other PnP devices it also contributes a great role in the states of power transition like hibernation or sleep to wake up.