BSOD problem with AMD mobility radeon

jakuza

Member
Joined
Sep 21, 2014
Posts
5
Pleas help.
I see that the problem is with unsigned driver atikmpag.sys, but can not find signed one. When I start Windows with options Disable digital signature enforcement there is always BSOD cousing by atikmpag.sys.
Tried with different version of driver, but no luck. Earlier I had BSOD cousing by atkmdag.sys, but I somehow fixed that installing driver from .inf file.
 

Attachments

Code:
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80057ff010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: [COLOR="#008000"]fffff88004245c48[/COLOR], 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.

Code:
fffff880`051fa9c8 fffff880`042e2000 : 00000000`00000116 fffffa80`057ff010 fffff880`04245c48 00000000`00000000 : [COLOR="#0000FF"]nt!KeBugCheckEx[/COLOR]
fffff880`051fa9d0 fffff880`042e1d0a : fffff880`04245c48 fffffa80`057ff010 fffffa80`054b6c00 fffffa80`05459410 : [COLOR="#0000FF"]dxgkrnl!TdrBugcheckOnTimeout+0xec[/COLOR]
fffff880`051faa10 fffff880`04fc0f07 : fffffa80`057ff010 00000000`00000000 fffffa80`054b6c00 fffffa80`05459410 : [COLOR="#FF0000"]dxgkrnl!TdrIsRecoveryRequired+0x1a2[/COLOR]
fffff880`051faa40 fffff880`04feab75 : 00000000`ffffffff 00000000`00000578 00000000`00000000 00000000`00000002 : [COLOR="#FF0000"]dxgmms1!VidSchiReportHwHang+0x40b[/COLOR]
fffff880`051fab20 fffff880`04fe92bb : 00000000`00000102 00000000`00000000 00000000`00000578 00000000`00000000 : [COLOR="#FF8C00"]dxgmms1!VidSchiCheckHwProgress+0x71[/COLOR]
fffff880`051fab50 fffff880`04fbc2c6 : ffffffff`ff676980 fffffa80`05459410 00000000`00000000 00000000`00000000 : [COLOR="#800080"]dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb[/COLOR]
fffff880`051fabf0 fffff880`04fe8e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`04e31c68 : [COLOR="#800080"]dxgmms1!VidSchiScheduleCommandToRun+0x1da[/COLOR]
fffff880`051fad00 fffff800`02b17fee : 00000000`031cd67a fffffa80`054b8a10 fffffa80`03b6e040 fffffa80`054b8a10 : [COLOR="#800080"]dxgmms1!VidSchiWorkerThread+0xba[/COLOR]
fffff880`051fad40 fffff800`0286e5e6 : fffff800`029f2e80 fffffa80`054b8a10 fffff800`02a00cc0 4836336d`6f6d6235 : nt!PspSystemThreadStartup+0x5a
fffff880`051fad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

We can see the Directx routines executing and performing scheduled events, when it checks the progress it finds that it has simply hanged, it's not responding so it tries to perform a TDR (Timeout Detection and Recovery), the TDR fails to accomplish anything so we bugcheck.

I would say that your graphics card is failing, do you have another one you can use?
You could try integrated graphics and see how things go.

Check your temperatures; is your GPU overheating?
 
Code:
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80057ff010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: [COLOR=#008000]fffff88004245c48[/COLOR], 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.

Code:
fffff880`051fa9c8 fffff880`042e2000 : 00000000`00000116 fffffa80`057ff010 fffff880`04245c48 00000000`00000000 : [COLOR=#0000FF]nt!KeBugCheckEx[/COLOR]
fffff880`051fa9d0 fffff880`042e1d0a : fffff880`04245c48 fffffa80`057ff010 fffffa80`054b6c00 fffffa80`05459410 : [COLOR=#0000FF]dxgkrnl!TdrBugcheckOnTimeout+0xec[/COLOR]
fffff880`051faa10 fffff880`04fc0f07 : fffffa80`057ff010 00000000`00000000 fffffa80`054b6c00 fffffa80`05459410 : [COLOR=#FF0000]dxgkrnl!TdrIsRecoveryRequired+0x1a2[/COLOR]
fffff880`051faa40 fffff880`04feab75 : 00000000`ffffffff 00000000`00000578 00000000`00000000 00000000`00000002 : [COLOR=#FF0000]dxgmms1!VidSchiReportHwHang+0x40b[/COLOR]
fffff880`051fab20 fffff880`04fe92bb : 00000000`00000102 00000000`00000000 00000000`00000578 00000000`00000000 : [COLOR=#FF8C00]dxgmms1!VidSchiCheckHwProgress+0x71[/COLOR]
fffff880`051fab50 fffff880`04fbc2c6 : ffffffff`ff676980 fffffa80`05459410 00000000`00000000 00000000`00000000 : [COLOR=#800080]dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb[/COLOR]
fffff880`051fabf0 fffff880`04fe8e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`04e31c68 : [COLOR=#800080]dxgmms1!VidSchiScheduleCommandToRun+0x1da[/COLOR]
fffff880`051fad00 fffff800`02b17fee : 00000000`031cd67a fffffa80`054b8a10 fffffa80`03b6e040 fffffa80`054b8a10 : [COLOR=#800080]dxgmms1!VidSchiWorkerThread+0xba[/COLOR]
fffff880`051fad40 fffff800`0286e5e6 : fffff800`029f2e80 fffffa80`054b8a10 fffff800`02a00cc0 4836336d`6f6d6235 : nt!PspSystemThreadStartup+0x5a
fffff880`051fad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

We can see the Directx routines executing and performing scheduled events, when it checks the progress it finds that it has simply hanged, it's not responding so it tries to perform a TDR (Timeout Detection and Recovery), the TDR fails to accomplish anything so we bugcheck.

I would say that your graphics card is failing, do you have another one you can use?
You could try integrated graphics and see how things go.

Check your temperatures; is your GPU overheating?


Jared,
thanks for quick reply.

It is my laptop dell N5010. No other graphic card available. Temperature are about 65-70C, it was more, but I replaced thermal pad and paste also, it was overheathing obvious.
Could it be that my GPU is dead?
 
Is this at idle temp or under stress?
If it's idle then we have a serious overheating issue so I wouldn't be surprised if it's causing the problem.

You might want to try and clean out any dust.
Unfortunately because laptops are so compact components overheat more, it makes it much more difficult to bring down temperatures.
 
That's quite warm as idle but under stress there is no problem. I can't see overheating being the cause.
 
The temperatures were way to high before I cleaned the dust-maybe 85C and more. How to know if my GPU is dead? I have picture on my display now, does it means that the GPU is OK and that I have driver problem only? Max resolution on screen display with VGA driver is 1280x768.
 
It can be difficult to tell, what do you normally do when it crashes?
Have you tried lots of different drivers?
If you have tried different drivers do they increase or decrease the frequency of the crashes, if so then we're looking more towards a driver issue as opposed to a dead GPU although there can be exceptions sometimes to these guidelines.
 
Windows won't start, BSOD appears when using ATI drivers. No problem with safe mode, and when usind VGA driver, but when I installed ATI mobility radeon HD 5xxx driver, BSOD always appear. Tried 4 different driver, all from ATI, mostly some previous version, and latest one v.14.4.
Now it is working with installed ATI mobility radeon HD 5000 driver, but as atikmpag.sys is not digitally signed windows do not using it and boot correctly but there is yellow flag in device manager in display driver. And also max resolution for screeen display remain 1280x768.
When I boot windows with option Disable digital signature enforcement BSOD appears.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top