Windows 10: BSOD while computer is idle(crashes seem infrequent)

Im am experiencing some sort of crash while my computer is in idle. I do not see the bsod myself but I know they are happening. As I return to my computer I am back in the login screen. I checked the mini dump to find that I have had 2 incidents of my computer crashing with a week apart from them but with the similar problems. I know it is probably my cpu or gpu.

Before experiencing these problems I attempted an oc on my cpu but realized my motherboard was not the model that can be overclocked( I am running on an m5a97 non revision version). I reseted it to default settings for my cpu. It is then i experience these rare crashes.

If not the cpu it may be graphics as i have been downloading the updated version of my gpu's drivers.

:)

 

Frozen computer and BSOD Windows 10

Oh and BTW, many times my computer will crash after it was been idle for a while even a few hours. But will also crash while being used by a program, it doesn't seem to matter which program either.

Thanks.

 

System restarts after sometime without user interaction.

I started the computer in safe mode , and computer ran with a BSOD .

now how am i going to find what's responsible for the BSOD while computer is idle?

 

Hello Hankumin and welcome to TenForums *Smile

I've looked at the crash report and the last one relates to a driver power state failure. I've looked at the blocked IRP to see which driver is causing it and it would seem to be the graphics driver (atikmpag.sys). Please remove all traces of the display drivers including the Catalyst Control Center using DDU and then reinstall but only install the Display Driver using the custom/advanced options.

Code: 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: ffff8d0916179060, Physical Device Object of the stack Arg3: fffff8039c61f960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffff8d0916ce6b40, The blocked IRP 0: kd> !irp ffff8d0916ce6b40 Irp is active with 5 stacks 4 is current (= 0xffff8d0916ce6ce8) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned cmd flg cl Device File Completion-Context [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)] 0 0 ffff8d0916179060 00000000 fffff8060b23ed40-ffffdb004073e9f0 \Driver\pci dxgkrnl!DpiFdoPowerCompletionRoutine Args: 00000000 00000000 00000000 00000000 >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffff8d0916726030 00000000 fffff8039a937a00-ffff8d0916637538 Success Error Cancel pending Unable to load image \SystemRoot\System32\DriverStore\FileRepository\c0309792.inf_amd64_16fba8c07200efae\atikmpag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys \Driver\amdkmdap nt!PopRequestCompletion Args: 00000000 00000001 00000001 00000000 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-ffff8d0916637538 Args: 00000000 00000000 00000000 00000000[/quote]

 

Thank you for the response *Smile. I am following those instructions right now. Ill mark this thread as complete since the crash seems pretty sporadic and it will take a while for me to see if the bsod still occcurs.

 

Unfortunately this did not fix the problem *Sad. I used ddu to clean my drivers and reinstalled the latest display driver but i got another bsod. Again the problem occurred while it was idle. It appears to be the same error. I will try to clean my display drivers again but here is the new dump file.

 

Yes it is the same error and the blocked IRP still refers to the same video driver. It may be that you need to revert to an older driver or wait for a newer one to be provided for your graphics card.

 

Just did that, I have a couple of old driver installers in my comp so i reverted to a an older one hopefully that will fix the problem. Like last time ill put the thread as solved for while. Thank you for the response *Smile.