BSOD awakening the display

[LookingForHelp1]

Evening,

Yesterday, after returning home, I attempted to awaken my computer. For some reason, the computer didn't respond to my mouse clicks, so I restarted it by holding the On/Off button for few seconds to turn it off, and then turned it on.
Today, after leaving the computer for a couple of hours and coming back, the display was off and didn't respond again. This time I just left the computer to be, and after 5 or so minutes I got a BSOD.
I'm really clueless in everything technical, so I don't really know how to approach this problem, but I hope you guys will be able to help. Note that after the first incident, I disabled sleeping of the computer as I heard this may be the cause to the issue, but considering the problem happened twice I guess the issue is somewhere else.
I've uploaded the .zip file as requested in the posting instructions. If you any other questions, fill free to ask and I'll try to answer.

 

[LookingForHelp1]

Considering a day passed and no answer, bumping the thread.

 

[essenbe]

Hello, LookingForHelp1 welcome to the forums. Sorry you had to wait, but it gets kind of busy in here. I will try to help you, but I need you to do something for me.

Please fill out your System Specs​

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html Please include Manufacturer and Model for the components and be sure to include the PSU and CPU Cooler.​

You only had one dump file dated 05/21 This is what it listed

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: fffffa80095795a0, Physical Device Object of the stack
Arg3: fffff80000b9a3d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa8007d942e0, The blocked IRP

BugCheck 9F, {3, fffffa80095795a0, fffff80000b9a3d8, fffffa8007d942e0}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys

That is your graphics driver, as I am sure you know. Once I know your system specs, I can give you a few suggestions. Meanwhile, please make sure your computer is configured for Small Memory Dumps
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Also, please
open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Could you tell me what you have plugged into your USB ports, other than a Keyboard and mouse. I noticed a lot of USB errors along the way to the dump file. If you are using a wireless USB Dongle, that could be a big part of it.

 

[LookingForHelp1]

Thank you essenbe for your reply. I'll detail in this post what I've done:

I added system specs using the automatic tool the site provide. The computer was built in a local company, so I'm not entirely sure what kind of PSU or CPU cooler it has. I could pay a visit to the store, but in such case I'll probably take the computer with me and hope they will be able to fix it.

I changed the configuration to Small Memory Dumps, so if the BSOD will happen again I'll update with the new dump files.

I scanned the system files 4 times (As I didn't fully read your instructions, between the first and the second I didn't reboot). In all of them I got the message: "Windows Resource Protection found corrupt files but was unable to fix some them". I have the .log files of the scans, so I could try and upload them if it will help (But they require administrator access, so I'm not entirely sure what exactly to upload).

Finally, I have 3 things connected to my USB port: cam, a wireless thing for keyboard and mouse, and a USB flash drive which is mentioned in my specs.

 

[essenbe]

It's no problem that you didn't reboot between runs of sfc, did you reboot between the runs after you realized you were supposed to? It matters because sometimes the scan can only fix so many and the fixes it does do not actually occur until you reboot. Sometimes it is because some fixes have to happen before the rest can be fixed. So, if you didn't reboot, you can do it again and reboot. Nothing was harmed.

I see you have a Gigabyte Motherboard. If you have any Gigabyte utilities, please uninstall every one of them. They are know to cause BSODs.

This is your current Graphics driver

atikmpag
start             end                 module name
fffff880`044b4000 fffff880`0454a000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Thu [COLOR=red]Nov 20 20:08:54 2014[/COLOR] (546E9EB6)
    CheckSum:         00093077
    ImageSize:        00096000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I would like you to reinstall your graphics driver to either a newer WHQL driver or and older WHQL driver. I will also give you some suggestions to get a clean install and not install the things you do not need or use. Sometimes those things can cause driver conflicts. The only thing you really need is the Graphics Driver. Just go to Control Panel and Uninstall a program and uninstall CCC.

I am going to give you some links that will help you get a good clean install and not have any drivers you don't need that will conflict with other drivers. Download a WHQL driver from http://www.sevenforums.com/graphic-cards/329659-latest-amd-catalyst-video-driver-windows-7-a.html . Once you have them downloaded, uninstall your current driver from control panel. next clean up any left over drivers from following this tutorial http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html and select only ATI Display Drivers. After you have done that and rebooted, install the new driver, only select custom install and install only what you have to. Very few people need most of what they include. You do not need the audio/HDMI drivers as you already have that in your Motherboard drivers. Unless there is some reason you need them, the only thing you really need is the Display Driver.

Try that and let me know how it goes. If you run sfc again and it cannot repair the files, copy the CBS files to your desktop, then right click them and select send to then compressed ZIP folder. You should be able to upload them here on your next post. If you can't let me know and I will tell you what you need to do. They are protected and you will either warn you but allow you to continue or you will have to enter the administrator password. It's OK, you are not doing anything other than copying them.

 

[LookingForHelp1]

Before I get into the horrible process of reinstalling drivers, I'll answer some of your questions and ask some of my own.

I did reboot after each of the last 3 scans (Out of the 4), same message always.

I removed a couple of Gigabyte utilities: EasySaver and OnOffCharge. Hopefully this will help.

The link you gave me directs me to a forum post, which in turn links to the AMD site. Strangely, the WHQL link there directs me to the 15.4 version of the driver, which seems to be in Beta, and not the 14.12 version which is the latest version according to AMD's site and the forum post itself. Which should I download?

Last, I've downloaded a new game recently through Steam, and for a couple of times the computer froze and was unresponsive like I mentioned in my first post. Yet, this time, trying to wait for a BSOD was useless. Waiting both an hour the first time and 4 hours the second did nothing, the computer still had a frozen screen and was unresponsive.

This issue could be an issue with the game and not with the driver. I'll try to work regularly on my computer, without playing the game before uninstalling the driver, checking if removing the Gigabyte utilities helped. If the computer does become unresponsive again, I'll reinstall it according to your instructions.

Thank you very much for your help.

 

[essenbe]

The link is just here but is a direct link to AMD, so that is no problem. Yes, I just looked and found you were correct, that should not be the case. I would suggest you download the 14.2 WHQL driver.

There are many games which are poorly coded and give a lot of issues. That's why there are so many patches with a lot of them. It could very well be the game. I have had that a few times and usually end up uninstalling the game. Through Steam you can verify the files to see if it is installed correctly and if there are any corrupted files.

Before doing a clean install, try uploading the CBS files and I'll ask someone to look at them to see if they can be repaired. See option 3 which is here http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html#option3. Once you get the files on your Desktop, right click them, select send to > compressed zip folder and upload the zip folder here. this is how to upload them
http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If they are too large to upload here, upload them to a public folder at Onedrive or Dropbox and I will ask for help.

 

[LookingForHelp1]

I re-scanned just in case, same message, here are the logs.
Again, thank you for your help, it is highly appreciated.

 

[essenbe]

Ok, it may take a while to get some help, but I'm asking now.

 

[LookingForHelp1]

It seems like I already have the 14.12 version, considering it came out a while ago (December). I could try to reinstall it, but I guess it is not an "old version" issue.

I found out about the existence of the event log. There are no events from when the computer becomes unresponsive, but after shutting it down by holding the button and turning it on again, the computer logs an "Unexpected shutdown" event. The strange thing is that the time of the shutdown is the same time when the computer got stuck, and not when I actually shut it down. (worth mentioning there are error events related to that flash drive occurring every time I turn the computer on, so these may be the USB errors you saw in the dump file).

Moreover, after using the computer for a couple of hours while browsing online and playing a Flash game, the computer became unresponsive again. I left it stuck all night, for 8 hours, but no BSOD.

Considering all of this evidence, I suspect the BSOD was an exception (Or perhaps could've been caused by the Gigabyte utilities), and the real error may be an hardware issue. I'll try to bring it to the store.

 

[NoelDP]

Here's the errors from the SFC log...

2015-05-24 00:59:13, Info                  CSI    0000033a [SR] Repairing 1 components
2015-05-24 00:59:13, Info                  CSI    0000033b [SR] Beginning Verify and Repair transaction
2015-05-24 00:59:13, Info                  CSI    0000033d [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-24 00:59:13, Info                  CSI    0000033f [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

This is from the KB3022345 patch - which you may want to uninstall

If not, then here's the fix...

SFCFix Script

Warning: this fix is specific to the above corruptions only, do not run these fixes if you do not have these corrupt files.

• Download SFCFix.exe (by niemiro) and save this to your Desktop.
• Download SFCFix.zip from the below link, and save this to your Desktop. Ensure that this file is named SFCFix.zip – do not rename it.
• download this version: SFCFix(x64version)
• Save any open documents and close all open windows.
• On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.

• Drag the file SFCFix.zip onto the file SFCFix.exe and release it.

• SFCFix will now process the script.
• Upon completion, a file should be created on your Desktop: SFCFix.txt.

• Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please – put tags around the log to break up the text.

SFC /SCANNOW

• Right click on the Start button
• Click on Command prompt (Admin) => Press Yes on the prompt
• Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW

 

[LookingForHelp1]

I do prefer to try and fix problems instead of uninstalling patches, considering a patch could be the fix to a different issue.

I did what you said, and it worked! "Windows Resource Protection did not find any integrity violations".
I also didn't experience any problems for 4 hours now, which makes me suspect that there's some hardware issue that is triggered only when the computer is using a certain amount of resources. Of course, this is just a speculation, hopefully inspecting all of the logs will help to understand what's going on in there.

Thank you for your help!

Here is the SFCFix text:

SFCFix version 2.4.3.0 by niemiro.
Start time: 2015-05-24 14:15:03.381
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Or\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\diagtrack.dll
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.asm-windowsdefault.json
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utcresources.dll

The file \\?\C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\diagtrack.dll is in use and must be replaced over a reboot.
Successfully copied file C:\Users\Or\AppData\Local\niemiro\Archive\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.asm-windowsdefault.json to C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.asm-windowsdefault.json.
Successfully copied file C:\Users\Or\AppData\Local\niemiro\Archive\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json to C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json.
Successfully copied file C:\Users\Or\AppData\Local\niemiro\Archive\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utcresources.dll to C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utcresources.dll.

Successfully pended file for replace over reboot: \\?\C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\diagtrack.dll

Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.asm-windowsdefault.json
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.asm-windowsdefault.json
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utcresources.dll
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utcresources.dll
PowerCopy:: directive completed successfully.




Reboot:: directive completed successfully.




PostRebootCorruptionDetection::
No hash verification failures detected.
PostRebootCorruptionDetection:: directive completed successfully.




PostRebootRestorePermissions::
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\diagtrack.dll
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\diagtrack.dll
PostRebootRestorePermissions:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.3.0 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2015-05-24 14:21:59.168
----------------------EOF-----------------------

 

[NoelDP]

Great!
Good luck with the BSOD's

 

[essenbe]

See if it works any better for you now. If you are still having problems, let us know.