How can I tell if a power supply is causing shutdowns?

earwicker7

In Runtime
Messages
345
My computer has been getting a lot of random shutdowns recently. Often, it won't even BSOD, but will just flat out shut down like a lamp would when the power goes off. There are also some spontaneous reboots... unfortunately, I forgot to turn off "Automatically Restart" in the Startup and Recovery field when I reinstalled the OS, so I don't have any recent BSODs to use for troubleshooting.

Other than buying another power supply, is there any way to use voltmeters, or some kind of software, to try to nail down the problem? I just don't want to spend a couple of hundred dollars for a new supply and find out that isn't the issue.

The only thing which is currently overclocked is my memory... 2133 is the stock speed for it, but I have to overclock the board to get there.
 
Do you have anything stored under C:\Windows\Minidump

If so, zip them up and upload them and I can analyze them.
 
You could take out the 7970 and run the intel igp and see if it still dies.

You can use a digital multi meter and measure your voltage using a 4 pin, it'll give your 3V quality.
 
Do you have anything stored under C:\Windows\Minidump

If so, zip them up and upload them and I can analyze them.

I got a BSOD today with a Driver_Power_State_Failure, for which I've attached the dump file. I'm not sure if this is related to the PC completely shutting down or not... there are no dump files for when that happened.
 

Attachments

  • 052815-11093-01.zip
    67.6 KB · Views: 2
Do you have the proper and most recent drivers for all components? You have disabled all power saving features on the motherboard correct? Two things come up when I look at that minidump, MSPQM.sys errors out, and ntoskrnl.exe errors out, also, remove your overclock, it's pointless to have the ram overclocked like that really.
 
Do you have the proper and most recent drivers for all components? You have disabled all power saving features on the motherboard correct? Two things come up when I look at that minidump, MSPQM.sys errors out, and ntoskrnl.exe errors out, also, remove your overclock, it's pointless to have the ram overclocked like that really.

I will check the power saving features once I'm finished on this print run. While that finishes, are there any particular things I should do about those two errors?

To the best of my knowledge, all of the drivers are up to date, but I'll double check.
 
Here's the analysis of the dump:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa801f7a3c10, fffff8800141b7f0, fffffa80230ff010}

*** WARNING: Unable to verify timestamp for asmthub3.sys
*** ERROR: Module load completed but symbols could not be loaded for asmthub3.sys
Probably caused by : asmthub3.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa801f7a3c10, Physical Device Object of the stack
Arg3: fffff8800141b7f0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa80230ff010, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: fffffa801e0445e0

IMAGE_NAME:  asmthub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  520e7d76

MODULE_NAME: asmthub3

FAULTING_MODULE: fffff88008d90000 asmthub3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre

DPC_STACK_BASE:  FFFFF88001422FB0

STACK_TEXT:  
fffff880`0141b7b8 fffff801`cba1af22 : 00000000`0000009f 00000000`00000003 fffffa80`1f7a3c10 fffff880`0141b7f0 : nt!KeBugCheckEx
fffff880`0141b7c0 fffff801`cba1af55 : fffffa80`231cc480 fffffa80`1f3d1000 fffff880`0141b939 fffff801`cb9a8150 : nt!PopIrpWatchdogBugcheck+0xe2
fffff880`0141b820 fffff801`cb9077ba : fffffa80`1f3d1000 fffff880`0141b939 00000000`00000001 00000000`00000000 : nt!PopIrpWatchdog+0x32
fffff880`0141b870 fffff801`cb905c25 : 00000000`00000000 fffff801`cb9072cf 00000000`00140001 fffff801`cbb80100 : nt!KiProcessExpiredTimerList+0x22a
fffff880`0141b9a0 fffff801`cb907c38 : fffff880`009f0180 fffff801`cbb7ef80 00000000`00000002 00000000`0027aa64 : nt!KiExpireTimerTable+0xa9
fffff880`0141ba40 fffff801`cb906fd6 : fffffa80`00000000 00001f80`009f0080 00000000`00000000 00000000`00000002 : nt!KiTimerExpiration+0xc8
fffff880`0141baf0 fffff801`cb907f8a : fffff880`009f0180 fffff880`009f0180 00000000`00000000 fffff880`009fc040 : nt!KiRetireDpcList+0x1f6
fffff880`0141bc60 00000000`00000000 : fffff880`0141c000 fffff880`01416000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_IMAGE_asmthub3.sys

BUCKET_ID:  0x9F_3_POWER_DOWN_IMAGE_asmthub3.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_image_asmthub3.sys

FAILURE_ID_HASH:  {12eb0d90-8fd7-cc3c-7648-32ce90a0e457}

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

asmthub3.sys is the faulting driver

Checking out the driver...
Code:
1: kd> lmvm asmthub3
start             end                 module name
fffff880`08d90000 fffff880`08db5000   asmthub3 T (no symbols)           
    Loaded symbol image file: asmthub3.sys
    Image path: \SystemRoot\System32\drivers\asmthub3.sys
    Image name: asmthub3.sys
    Timestamp:        Fri Aug 16 14:28:54 2013 (520E7D76)
    CheckSum:         00028CD4
    ImageSize:        00025000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It's from 2013 (note the timestamp value). Update that driver - sounds like it's a chipset/USB 3.0 driver. So go to your motherboard manufacturer's website, download the latest chipset and/or USB3.0 driver. See here for more info: http://answers.microsoft.com/en-us/...top-0x9f/3734a91f-a075-42b4-9fc7-2e4177abd57a

Edit:
Diving further into the memory locations, there's also references to Razer drivers. Do you have any Razer devices?

Code:
1: kd> !irp fffffa80230ff010
Irp is active with 11 stacks 7 is current (= 0xfffffa80230ff290)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context

<snipped>

			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa801f7a3c10 00000000 00000000-00000000    pending
	       \Driver\asmthub3
			Args: 00041100 00000001 00000001 00000002
 [ 16, 2]   0 e1 fffffa80206bdd20 00000000 fffff8800881cf40-00000000 Success Error Cancel pending
	      Unable to load image \SystemRoot\System32\drivers\rzdaendpt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rzdaendpt.sys
*** ERROR: Module load completed but symbols could not be loaded for rzdaendpt.sys
 \Driver\rzdaendpt	hidusb!HumPowerCompletion
			Args: 00041100 00000001 00000001 00000002

I would definitely update those drivers as well (or reinstall them and then update). You could also try a different USB port to see if it's an issue with the port/Razer device.
 
Last edited:
Here's the analysis of the dump:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa801f7a3c10, fffff8800141b7f0, fffffa80230ff010}

*** WARNING: Unable to verify timestamp for asmthub3.sys
*** ERROR: Module load completed but symbols could not be loaded for asmthub3.sys
Probably caused by : asmthub3.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa801f7a3c10, Physical Device Object of the stack
Arg3: fffff8800141b7f0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa80230ff010, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: fffffa801e0445e0

IMAGE_NAME:  asmthub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  520e7d76

MODULE_NAME: asmthub3

FAULTING_MODULE: fffff88008d90000 asmthub3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre

DPC_STACK_BASE:  FFFFF88001422FB0

STACK_TEXT:  
fffff880`0141b7b8 fffff801`cba1af22 : 00000000`0000009f 00000000`00000003 fffffa80`1f7a3c10 fffff880`0141b7f0 : nt!KeBugCheckEx
fffff880`0141b7c0 fffff801`cba1af55 : fffffa80`231cc480 fffffa80`1f3d1000 fffff880`0141b939 fffff801`cb9a8150 : nt!PopIrpWatchdogBugcheck+0xe2
fffff880`0141b820 fffff801`cb9077ba : fffffa80`1f3d1000 fffff880`0141b939 00000000`00000001 00000000`00000000 : nt!PopIrpWatchdog+0x32
fffff880`0141b870 fffff801`cb905c25 : 00000000`00000000 fffff801`cb9072cf 00000000`00140001 fffff801`cbb80100 : nt!KiProcessExpiredTimerList+0x22a
fffff880`0141b9a0 fffff801`cb907c38 : fffff880`009f0180 fffff801`cbb7ef80 00000000`00000002 00000000`0027aa64 : nt!KiExpireTimerTable+0xa9
fffff880`0141ba40 fffff801`cb906fd6 : fffffa80`00000000 00001f80`009f0080 00000000`00000000 00000000`00000002 : nt!KiTimerExpiration+0xc8
fffff880`0141baf0 fffff801`cb907f8a : fffff880`009f0180 fffff880`009f0180 00000000`00000000 fffff880`009fc040 : nt!KiRetireDpcList+0x1f6
fffff880`0141bc60 00000000`00000000 : fffff880`0141c000 fffff880`01416000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_IMAGE_asmthub3.sys

BUCKET_ID:  0x9F_3_POWER_DOWN_IMAGE_asmthub3.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_image_asmthub3.sys

FAILURE_ID_HASH:  {12eb0d90-8fd7-cc3c-7648-32ce90a0e457}

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

asmthub3.sys is the faulting driver

Checking out the driver...
Code:
1: kd> lmvm asmthub3
start             end                 module name
fffff880`08d90000 fffff880`08db5000   asmthub3 T (no symbols)           
    Loaded symbol image file: asmthub3.sys
    Image path: \SystemRoot\System32\drivers\asmthub3.sys
    Image name: asmthub3.sys
    Timestamp:        Fri Aug 16 14:28:54 2013 (520E7D76)
    CheckSum:         00028CD4
    ImageSize:        00025000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It's from 2013 (note the timestamp value). Update that driver - sounds like it's a chipset/USB 3.0 driver. So go to your motherboard manufacturer's website, download the latest chipset and/or USB3.0 driver. See here for more info: Blue Screen: Stop 0x9f - Microsoft Community

Edit:
Diving further into the memory locations, there's also references to Razer drivers. Do you have any Razer devices?

Code:
1: kd> !irp fffffa80230ff010
Irp is active with 11 stacks 7 is current (= 0xfffffa80230ff290)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context

<snipped>

			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa801f7a3c10 00000000 00000000-00000000    pending
	       \Driver\asmthub3
			Args: 00041100 00000001 00000001 00000002
 [ 16, 2]   0 e1 fffffa80206bdd20 00000000 fffff8800881cf40-00000000 Success Error Cancel pending
	      Unable to load image \SystemRoot\System32\drivers\rzdaendpt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rzdaendpt.sys
*** ERROR: Module load completed but symbols could not be loaded for rzdaendpt.sys
 \Driver\rzdaendpt	hidusb!HumPowerCompletion
			Args: 00041100 00000001 00000001 00000002

I would definitely update those drivers as well (or reinstall them and then update). You could also try a different USB port to see if it's an issue with the port/Razer device.

Under the chipset downloads on the motherboard's website, it has Intel(R) Chipset Software Installation Utility V9.3.2.1015 and Intel Management Engine Interface V9.5.15.1730. Should I install both?

I do have a Razer mouse, and it has been giving me some funky issues... when I put my computer into sleep mode, it often doesn't work when I wake the computer up. All I have to do is unplug it and plug it back in. I'll reinstall those drivers.
 
Back
Top Bottom