atikmpag.sys BSOD - Windows 7 x64

H

hauw

New member
Joined
Feb 15, 2015
Posts
4
Is a laptop
OS : Windows 7 64 bit.
No original OS installed (DOS)
Age of system is 3 years
Age of OS is around 1.5 years
CPU : intel i5-2430M
Video Card : ATI Radeon HD7650M
System Manufacturer : Dell
Model Number : N4110 Inspiron

Installed the OS the 3rd time. Updated the driver and everything is used to be fine.
BSOD occasionally happened before but not like this.
Always BSOD on 2 games only : Elder Scrolls IV : Oblivion and Dragon Age : Origins Awakening.
Elder Scrolls V : Skyrim worked fine. And so does Warcraft 3, Diablo 3, and The Sims 4.
And also i'm unable to find any compatible video card driver so far.
The detect driver application told me to check on my vendor and they are already out of business.

Thanks before!

View attachment 10860
 
I can't find any way to edit my post so here's the perfmod attachment which i've forgot in my first post.

Edited :
strange that i can edit this message. The error logs in the first post appears to contain all the BSODs so far. Just ignore everything else except the latest one which occurs when i'm trying to run Elder Scrolls IV - thanks!
 

Attachments

There is a time limit imposed on how long a post can be edited. It's about 15 minutes I think.
 
Code: 
[COLOR=#ff0000]BugCheck 116[/COLOR], {[COLOR=#0000cd]fffffa80041fe010[/COLOR], [COLOR=#008000]fffff880042133f8[/COLOR], 0, 2}

*** 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=#ff0000]atikmpag.sys[/COLOR] ( atikmpag+73f8 )

The first parameter is a pointer into the TDR_RECOVERY_CONTEXT structure, which can be dumped if you have private symbols for the dxgkrnl module.

The second parameter points to the driver which is responsible for causing the crash.

Code: 
2: kd> [COLOR=#008000]u fffff880042133f8[/COLOR]
[COLOR=#ff0000]atikmpag+0x73f8[/COLOR]:
fffff880`042133f8 4883ec28        sub     rsp,28h
fffff880`042133fc 4c8bd1          mov     r10,rcx
fffff880`042133ff 41b8010000c0    mov     r8d,0C0000001h
fffff880`04213405 4885c9          test    rcx,rcx
fffff880`04213408 7451            je      atikmpag+0x745b (fffff880`0421345b)
fffff880`0421340a 4885d2          test    rdx,rdx
fffff880`0421340d 744c            je      atikmpag+0x745b (fffff880`0421345b)
fffff880`0421340f 488b05cafe0300  mov     rax,qword ptr [atikmpag+0x472e0 (fffff880`042532e0)]

We can then dump the driver module information, and obtain the timestamp of the driver:

Code: 
2: kd> [COLOR=#008000]lmvm atikmpag[/COLOR]
start             end                 module name
fffff880`0420c000 fffff880`0425b000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        [COLOR=#ff0000]Mon Oct 17 07:03:15 2011[/COLOR] (4E9BC523)
    CheckSum:         000544D9
    ImageSize:        0004F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The driver seems to be dated as 2011, I would suggest finding an update from the AMD website or your laptop model's support page.
 
It does work at first but then i'm still having BSODs on Elder Scrolls 4.
On Dragon Age i get error message : video card not supported.
It tuns out that my ATI Catalyst.exe causes BSODs.

Uploaded new file.
View attachment 11015
So... Can a guru here help me please? Pretty please with a tablespoon of sugar here :3
 
So... Can a guru here help me please?
Click to expand...

BlueRobot is about as smart as they come for kernel-debugging, so you were in good hands.

Anyway, still 0x116.

Code: 
0: kd> k
Child-SP          RetAddr           Call Site
fffff880`067ad288 fffff880`0413fcbc nt!KeBugCheckEx
fffff880`067ad290 fffff880`0413fa43 dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`067ad2d0 fffff880`0400ff07 dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`067ad300 fffff880`0403dd7e dxgmms1!VidSchiReportHwHang+0x40b
fffff880`067ad3e0 fffff880`04023bb1 dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`067ad420 fffff880`04026aaf dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`067ad520 fffff880`0402278f dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0xd7
fffff880`067ad560 fffff880`04022726 dxgmms1!VIDMM_GLOBAL::MemoryTransferInternal+0x37
fffff880`067ad6f0 fffff880`0402f171 dxgmms1!VIDMM_GLOBAL::MemoryTransfer+0x216
fffff880`067ad790 fffff880`04021af3 dxgmms1!VIDMM_MEMORY_SEGMENT::CommitResource+0x1fd
fffff880`067ad870 fffff880`0401e763 dxgmms1!VIDMM_GLOBAL::PageInAllocations+0xbb
fffff880`067ad8d0 fffff880`0403865d dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xccf
fffff880`067adaa0 fffff880`04038398 dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`067adc90 fffff880`04037e96 dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`067adcc0 fffff800`0331e166 dxgmms1!VidSchiWorkerThread+0xd6
fffff880`067add00 fffff800`03059486 nt!PspSystemThreadStartup+0x5a
fffff880`067add40 00000000`00000000 nt!KiStartSystemThread+0x16

DurectX MMS as opposed to kernel this time, and we're starting up a worker thread. We're preparing direct memory access buffers, transferring memory, etc. We go off the rails waiting for engines, and then TDR reports a display driver hang > failure to recover > inevitable bug check.

IMO given the calls throughout the stack, your video card is the issue and not the display driver from AMD itself. Check temperatures first with Speccy during load especially since it's a laptop, possible overheating during gaming. If not, like I said, probably a bad card.
 
I know he did. Otherwise i wouldn't have followed his advice in the first place.
A second opinion won't hurt however.

I guess that's the problem, being the laptop over 3 yrs old and all... Lol...
 

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

Back
Top