Code:
BugCheck [COLOR="red"]116[/COLOR], {858a2510, [COLOR="Green"]93b6d7f2[/COLOR], [COLOR="Orange"]c0000001[/COLOR], 3}
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 : [COLOR="Red"]atikmpag.sys[/COLOR] ( atikmpag+77f2 )
0x116 bugchecks indicate an attempt to reset the display within the allocated time interval failed which resulted in a bugcheck.
Lets take a look at the error I highlight in
orange.
Code:
0: kd> [COLOR="Green"]!error c0000001[/COLOR]
Error code: (NTSTATUS) 0xc0000001 (3221225473) - {Operation Failed} The requested operation was unsuccessful.
As it says the previous operation failed but it doesn't say why which isn't helpful.
Code:
0: kd> [COLOR="Green"]u 93b6d7f2[/COLOR]
atikmpag+0x77f2:
93b6d7f2 8bff [COLOR="Blue"]mov[/COLOR] [COLOR="Red"]edi[/COLOR],[COLOR="red"]edi[/COLOR]
93b6d7f4 55 push ebp
93b6d7f5 8bec mov ebp,esp
93b6d7f7 56 push esi
93b6d7f8 57 push edi
93b6d7f9 8b7d08 mov edi,dword ptr [ebp+8]
93b6d7fc be010000c0 mov esi,0C0000001h
93b6d801 85ff test edi,edi
I'm seeing a lot of push instructions which is used to add data onto the stack.
The faulting instruction pointer tried to move data onto the zeroed stack which isn't allowed, now it might be zeroed because it's a minidump as it doesn't save all registers.
At this point I'm thinking more of a driver problem rather than a graphics card failure.
Code:
0: kd> [COLOR="Green"]lmvm atikmdag[/COLOR]
start end module name
9480b000 951f6000 atikmdag (deferred)
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Timestamp: [COLOR="Red"]Tue Apr 30 03:02:54 2013[/COLOR] (517F264E)
CheckSum: 009A2A46
ImageSize: 009EB000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Lets try an update, I suggest one around December as the latest drivers have caused quite a few issues.
Download Drivers
One last suggestion would be to remove avast using the
removal tool then replace it with
MSE and
Malwarebytes.
Tip
Make sure you don't enable the free trial of malwarebytes pro, deselect the option when prompted.
Looking at your msinfo file I see this installed...
Code:
[COLOR="Red"]DAEMON Tools Pro Agent[/COLOR] "c:\program files\daemon tools pro\dtagent.exe" -autorun geo-PC\geo HKU\S-1-5-21-2682449194-873571423-3709750171-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Daemon Tools/Alcohol is known cause of BSODs.
Registry and SPTD problems | DAEMON Pro Help
How to remove sptd.sys from system
1. Uninstall Daemon Tools.
2. Download the
SPTD standalone installer and follow these steps:
3. Double click the executable to open it
4. Click the button shown below
If the button it is grayed out, as shown in the image, there is no more SPTD installation on your system, and you can just close the window.
