Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD at random times after driver crash/recovery ati graphics related

08 Apr 2015   #1

Windows 7 Home Premium 64 bit
BSOD at random times after driver crash/recovery ati graphics related

The title pretty much says it all... i do also get the catalyst control center crashing everytime i boot the machine but as it never seemed to have any effect in the past i've mostly ignored it. logs are attached in .zip format.
My System SpecsSystem Spec
08 Apr 2015   #2

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

From the title it seems so ... still asking ... have you faced any such notification popup?

The display chip is a ATI Mobility Radeon HD 4670. And all the random dumps (from the latest to the earliest) I have checked, it shows a very old display driver, and the same one allover.
    Image name: atikmpag.sys
    Timestamp:        Fri Jan 22 18:37:54 2010 
Such an old driver may fail by itself only.

Have you ever updated the display driver? If not, install the CCC 14.4 WHQL.

Let us know for any further BSOD after doing it. The reporting will be important, because there may be some more things causing display failure influencing the BSODs.
BugCheck 116, {fffffa80076a84e0, fffff88003e10c98, 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 : atikmpag.sys ( atikmpag+5c98 )

Followup: MachineOwner

2: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Attempt to reset the display driver and recover from timeout failed.
Arg1: fffffa80076a84e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003e10c98, 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:

fffff880`03e10c98 4883ec28        sub     rsp,28h






ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

fffff880`037ed308 fffff880`03e94134 : 00000000`00000116 fffffa80`076a84e0 fffff880`03e10c98 00000000`00000000 : nt!KeBugCheckEx
fffff880`037ed310 fffff880`03e93e3e : fffff880`03e10c98 fffffa80`076a84e0 fffffa80`0d72d280 fffffa80`08208410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`037ed350 fffff880`04f1df13 : fffffa80`076a84e0 00000000`00000000 fffffa80`0d72d280 fffffa80`08208410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`037ed380 fffff880`04f4bed6 : fffffa80`ffffffff 00000000`0003a427 fffff880`037ed4d0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`037ed460 fffff880`04f31ce9 : fffffa80`09b1e000 ffffffff`feced300 00000000`00000002 fffff880`037ed7d8 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`037ed4a0 fffff880`04f34be7 : 00000000`000001f9 00000000`00000000 fffffa80`06d6ba80 fffff8a0`0e35a720 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`037ed5a0 fffff880`04f332d8 : fffff8a0`0e35a720 00000000`00000000 fffffa80`09b1e000 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0xd7
fffff880`037ed5e0 fffff880`04f3322e : 00000000`00000000 00000000`00000001 fffffa80`09b1e000 fffff880`04f31b56 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+0x34
fffff880`037ed770 fffff880`04f3c77e : fffffa80`09808a60 00000000`00000001 00000000`00000001 fffff800`030e20f2 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegment+0x13e
fffff880`037ed7e0 fffff880`04f3c527 : fffff8a0`0e35a720 00000000`00001000 fffffa80`09808a60 fffff8a0`0e35a720 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapApertureRange+0x7a
fffff880`037ed830 fffff880`04f3becb : fffff8a0`0e35a720 fffffa80`09b1ec80 00000000`00000000 fffffa80`09b1ec80 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapTemporaryResource+0x9b
fffff880`037ed890 fffff880`04f2f8a4 : fffffa80`09b1e000 fffffa80`09b1e000 fffffa80`09b1ec80 fffffa80`09b1e000 : dxgmms1!VIDMM_APERTURE_SEGMENT::ReleaseTemporaryResource+0xcf
fffff880`037ed8d0 fffff880`04f2c257 : 00000000`c0000001 00000000`00000000 00000000`00000006 fffffa80`09b1e000 : dxgmms1!VIDMM_GLOBAL::EvictTemporaryAllocations+0xbc
fffff880`037ed910 fffff880`04f467d9 : 00000000`00000000 fffff8a0`0ec519d0 fffffa80`00000002 fffffa80`07929d40 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x69f
fffff880`037edae0 fffff880`04f46514 : fffff800`04415080 fffff880`04f45f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`037edcd0 fffff880`04f46012 : 00000000`00000000 fffffa80`06d4f7f0 00000000`00000080 fffffa80`08208410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`037edd00 fffff800`0337bb8a : 00000000`fffffc32 fffffa80`09809b50 fffffa80`06d17890 fffffa80`09809b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`037edd40 fffff800`030ce8e6 : fffff800`03259e80 fffffa80`09809b50 fffff800`03267cc0 fffffa80`07c4fe70 : nt!PspSystemThreadStartup+0x5a
fffff880`037edd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb

fffff880`03e10c98 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+5c98

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys


FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys


FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmpag.sys

FAILURE_ID_HASH:  {83e844bc-fe68-2042-4230-7f5d3e90b48a}

Followup: MachineOwner

2: kd> lmvm atikmpag
start             end                 module name
fffff880`03e0b000 fffff880`03e37000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Jan 22 18:37:54 2010 (4B59A32A)
    CheckSum:         000279B5
    ImageSize:        0002C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
09 Apr 2015   #3

Windows 7 Home Premium 64 bit

Every time I start I get the below error for Catalyst control main, and the install of the new version failed... i uninstalled the old version but still no luck installing new.. as for updating the driver I have only done what windows update does so likely not.

Problem signature:
Problem Event Name: APPCRASH
Application Name: BrCtrlCntr.exe
Application Version:
Application Timestamp: 503c3313
Fault Module Name: dlbktwds.ds
Fault Module Version:
Fault Module Timestamp: 45df4d5a
Exception Code: c0000005
Exception Offset: 00004da2
OS Version: 6.1.7601.
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
My System SpecsSystem Spec

09 Apr 2015   #4

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

That event log is an appcrash, the crashed app is Brother Control Center, a software bundled with Brother printer. Update to the printer software might be needed there, also you should not let it allow to auto-start Brother Control Center alongwith windows. Remove it from startup.

Asking again .... have you got any such message as a popup balloon?

And, if you go to Download Drivers, what is the suggested driver for you?
My System SpecsSystem Spec

Thread Tools

Similar help and support threads
Thread Forum
Random BSOD - Presumably graphics card related
Hi all! I've been annoyed by BSOD quite a while now. Don't know exactly what caused it, but I suspect it has something to do with the graphics card (ATI). To help in diagnosis I'll describe more about what happened. My computer shuts down (power failure, not normal shutdown) or BSOD randomly...
BSOD Help and Support
BSOD at random times, maybe new graphics driver is at fault?
I attached like 7 different crash files, I hope someone can help me out.. Thanks a lot in advance!
BSOD Help and Support
BSOD @ Random Times. Running SQL Server, could be related?
BSOD occurs randomly, sometimes 2-3 times a day, sometimes 2-3 times a week total. But generally always happens at least once per week. Been ongoing for over a year. I upgraded all my RAM. I have run the MemTest86 and it reported good. The BSOD was occurring before and after that RAM upgrade. ...
BSOD Help and Support
BSoD at random times and pink graphics at times,
Hello, New member here and thanks in advance for looking. I have a home built w7 Home Premium box we use almost exclusively for Windows Media Center. I started getting bsod's about a month ago and before that got distorted *pinkish* video on restart or bootup at times. Tried using...
BSOD Help and Support
Random BSOD's, possibly related to graphics card
Windows 7 Ultimate x64 CPU: AMD FX-8150 8-Core CPU 3.6 GHz Mobo: ASUS Sabertooth 990FX Ram: 4x 4GB (Corsaire, can't remember model name of it) Graphics: Nvidia GeForce GTX 560 Ti 1200w PSU (modular) So basically over the past several weeks, I've been getting BSOD's about 1-4 times per...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 12:19.
Twitter Facebook