Hi,
This evening the blue screen came up every time i turned on my laptop after just a few minutes, four times in a row. I had been having the blue screen on a few occasions in the past months, but this week it has been happening repeatedly.
I have attached the zipped dump files.
I would really appreciate help on this. Thanks in advance.
Hi Miranda.
Update the display driver. Let us know the result.
____________________________________
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa8009560390, fffff88004e2db78, 0, 2} Unable to load image \SystemRoot\system32\DRIVERS\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 Probably caused by : atikmpag.sys ( atikmpag+7b78 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa8009560390, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff88004e2db78, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000002, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: atikmpag+7b78 fffff880`04e2db78 4883ec28 sub rsp,28h DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre STACK_TEXT: fffff880`0af44888 fffff880`04d35144 : 00000000`00000116 fffffa80`09560390 fffff880`04e2db78 00000000`00000000 : nt!KeBugCheckEx fffff880`0af44890 fffff880`04d34e4e : fffff880`04e2db78 fffffa80`09560390 fffffa80`0d301960 fffffa80`0d2aa010 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`0af448d0 fffff880`04c0ffbf : fffffa80`09560390 00000000`00000000 fffffa80`0d301960 fffffa80`0d2aa010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`0af44900 fffff880`04c39d09 : 00000000`ffffffff 00000000`00004d62 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`0af449e0 fffff880`04c3844f : 00000000`00000102 00000000`00000008 00000000`00004d62 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`0af44a10 fffff880`04c0b2e6 : ffffffff`ff676980 fffffa80`0d2aa010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`0af44ab0 fffff880`04c3800e : 00000000`00000000 fffffa80`0d37fd50 00000000`00000080 fffffa80`0d2aa010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`0af44bc0 fffff800`0331b73a : 00000000`fffffc32 fffffa80`0d304060 fffffa80`05b03b30 fffffa80`0d304060 : dxgmms1!VidSchiWorkerThread+0xba fffff880`0af44c00 fffff800`030708e6 : fffff800`031fae80 fffffa80`0d304060 fffff800`03208cc0 fffffa80`0d270010 : nt!PspSystemThreadStartup+0x5a fffff880`0af44c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: atikmpag+7b78 fffff880`04e2db78 4883ec28 sub rsp,28h SYMBOL_NAME: atikmpag+7b78 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmpag IMAGE_NAME: atikmpag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4e4c6c36 FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0x116_image_atikmpag.sys FAILURE_ID_HASH: {83e844bc-fe68-2042-4230-7f5d3e90b48a} Followup: MachineOwner --------- 0: kd> lmvm atikmpag start end module name fffff880`04e26000 fffff880`04e77000 atikmpag T (no symbols) Loaded symbol image file: atikmpag.sys Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys Image name: atikmpag.sys Timestamp: Thu Aug 18 07:04:46 2011 (4E4C6C36) CheckSum: 0005396D ImageSize: 00051000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Hi Arc,
Thanks for your reply. I followed the link you provided and downloaded the AMD Mobility Radeon driver.
I then tested it, just playing a movie file. The screen went black, some sound from the movie was still playing but not understandable and looping, I had to force shutdown the laptop.
btw what is AMD gaming evolved, this seems to have been downloaded in the process, not sure I want this...
The fan is also on and off loud, especially just before it crashes. I'll test it some more and keep you posted.
Thank you so much for your help.
AMD gaming evolved is some bloatware bundled with the driver pack. You may not install it, by opting for the advanced installation mode.
What you are saying .....
andI then tested it, just playing a movie file. The screen went black, some sound from the movie was still playing but not understandable and looping, I had to force shutdown the laptop.
.... it it happens despite of the latest driver, then the focus goes to the hardware. It needs a stress test to determine its health.Code:The fan is also on and off loud, especially just before it crashes.
As you have switchable graphics, it is somehow hard to stress test the dedicated AMD GPU, as the Onboard Intel HD graphics is the primary one. Stress test will run on it only. So you need to set the AMD GPU as the primary one. The options are available in the BIOS, and in the CCC too. You may have an idea about it in the video .....
When the AMD GPU is set to be the primary graphics, Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Also report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .
Thanks a lot Arc.
I uninstalled the AMD gaming evolved (as I had already installed the driver package) - it seems it comes under the name "Raptr", not "AMD Gaming Evolved" in the Windows control panel program list. I noticed it also installed Microsoft visual C++ 2012 Redistributable as part of the package, should I keep this, or can I also uninstall it?
At least I haven't had the BSOD since installing the new display driver, so that is great and thanks. I will have to test it some more, as night has come and gone here and I haven't been on the computer in the past 10 hours. One thing I did after my previous message, was look up about the black screen when I used VLC to play a movie. I thought it might be something to do with the new driver, and maybe a conflict of some kind, since this was a different issue to the BSOD issue I had originally posted about. I followed one of the suggestions I found and unticked the "Accelerated video output (Overlay) under Tools->Preferences->Video. I tested it again for a few minutes and it seemed to work fine.
With respect to the fan, I also googled about it last night and then changed the power settings to power saver, and it's much quieter now.
Do you still think I should still run the stress test? I am off to work now, so will anyway be using the laptop throughout the day and see how it performs. I'll report back how it goes.
Thanks again for your help.
You may keep Visual C ++.
If there is no further BSOD after installing the new display driver, the stress test is not rightly required now. Give it a bit more time. If the issue recurs, then the stress test will be a must.
Let us know about the situation. :)
Thank you Arc.
I had another instance of black screen today (but no BSOD). To be fair, I was running lots of program's when the screen went black (MS word, VLC movie, Kaspersky full scan, and Chrome 4 or 5 tabs), but this is a new issue that has popped up since installing the AMD driver. I was wondering if maybe I should disable the Intel CPU - is this how to make the AMD one primary? Can you think of any other reason why the screen is going black (the computer still seems to be running in the background, but I then have to force shutdown and restart)?
Thanks again for your help.
There may be many a reasons behind the screen going black.
If it recovers at its own, you may need to attempt another version of the display driver.
But if it is beyond repair, most probably it is some issue from the hardware's part.
As you have noticed it after installing the new driver, as the first attempt let us try another one. Uninstall the driver using Display Driver Uninstaller and then download the display driver from HP this time: HP Drivers and Downloads for Printers, Scanners and More | HP ® Support
Let us know how it works.
Thank you Arc.
I'll update the Intel GPU via the link you sent and test the laptop today.
I'll let you know how it goes.
I tried installing the Intel driver on the HP website, but received an error message saying "this computer does not meet the minimum requirements for installing the software".
I haven't uninstalled the AMD one because it was already on the notebook, but the link you provided was an upgrade for it.
Should I disable the intel one, and see how things go just using the AMD? You can probably tell I don't know much about computers!
Quote
Mobile