BSOD Error 0x00000116 (atikmdag.sys) only with graphic-driver

[virus01]

Hello alltogether,

I am using Windows 7 on my ACER Aspire 6530 (Graphics: ATI Radeon HD 3000 Series). On Monday, I did a lot of video-editing the whole day. I went into the hibernate mode over the night. Yesterday, my laptop rebootet after booting up windows.

Problem:
1. When I turn on my laptop (when I type my BIOS passwort in order to boot), i get some vertical grey lines on my screen. After getting in the BOOT-Menu (I have more OS) the grey lines disappear.
2. I am using a Monitor on VGA and my laptop display (2 displays), because my laptop-display does not work normaly anymore...Sometimes I only get a black screen --> graphic-card hardware problem?? VGA works well.
3. After selecting a OS and booting up, I get a Bluescreen 0x00000116 error. I followed the BSOD - Posting Instructions and posted the zip-File here. I attached a screenshot of my last Dump-File that I opened with "BlueScreenView" too.

What I did:
I can get into the SafeMode without problems. In Hardware-Manager, I deleted the DisplayDriver.
Without display-Driver, I can boot normaly and work in Windows. After Windows boots up, it installs the standard display driver automatically. After rebooting, I get the same BlueScreen again.

So I can only work without display driver.

I hope somebody can help me.
Thank you,

Regards,
virus01

 

[virus01]

Oh I forgot to upload my attachments:
- Dump Files
- Screenshot of last Dump

 

[Arc]

The display driver is failing, may be because of its old age?
Acer's website hosts a similar old age display driver. IMHO you may try Catalyst 13.9 from Here: Legacy

Moreover, you dont update windows, that increases the chances of issues.

[COLOR=Red]Windows 7 Kernel Version 7600 MP[/COLOR] (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

• Learn how to install Windows 7 Service Pack 1 (SP1)
• Service Pack and Update Center - Microsoft Windows

Taking the age of the laptop into consideration .... Is the computer hot? 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: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Do these. See how it goes. Let us know for any further BSOD.
__________________________________________________________________________________

BugCheck 116, {fffffa800636d010, fffff88003c54d9c, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+12d9c )

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: fffffa800636d010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003c54d9c, 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:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  7600.16695.amd64fre.win7_gdr.101026-1503

SYSTEM_MANUFACTURER:  Acer, inc.

SYSTEM_PRODUCT_NAME:  Aspire 6530G     

SYSTEM_VERSION:  Not Applicable

BIOS_VENDOR:  Acer   

BIOS_VERSION:  v0.3222

BIOS_DATE:  12/30/2008

BASEBOARD_MANUFACTURER:  Acer, Inc.

BASEBOARD_PRODUCT:  Mantasta         

BASEBOARD_VERSION:  Not Applicable

DUMP_TYPE:  2

BUGCHECK_P1: fffffa800636d010

BUGCHECK_P2: fffff88003c54d9c

BUGCHECK_P3: 0

BUGCHECK_P4: 2

FAULTING_IP: 
atikmdag+12d9c
fffff880`03c54d9c 48895c2408      mov     qword ptr [rsp+8],rbx

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CPU_COUNT: 2

CPU_MHZ: 76c

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 11

CPU_MODEL: 3

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-6AMUR58

ANALYSIS_SESSION_TIME:  05-19-2016 23:57:28.0258

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

STACK_TEXT:  
fffff880`04c409c8 fffff880`0428bef8 : 00000000`00000116 fffffa80`0636d010 fffff880`03c54d9c 00000000`00000000 : nt!KeBugCheckEx
fffff880`04c409d0 fffff880`0428bc02 : fffff880`03c54d9c fffffa80`0636d010 fffffa80`06011d50 fffffa80`03aad410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`04c40a10 fffff880`04332f07 : fffffa80`0636d010 00000000`00000000 fffffa80`06011d50 fffffa80`03aad410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`04c40a40 fffff880`0435cb75 : 00000000`ffffffff 00000000`000007af 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`04c40b20 fffff880`0435b2bb : 00000000`00000102 00000000`00000000 00000000`000007af 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`04c40b50 fffff880`0432e2c6 : ffffffff`ff676980 fffffa80`03aad410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`04c40bf0 fffff880`0435ae7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`05143168 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`04c40d00 fffff800`035147c6 : 00000000`0268dd5f fffffa80`05f238c0 fffffa80`03a4f450 fffffa80`05f238c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`04c40d40 fffff800`0324fc26 : fffff880`009e9180 fffffa80`05f238c0 fffff880`009f3f40 fffff880`01257534 : nt!PspSystemThreadStartup+0x5a
fffff880`04c40d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  a03fc032c072a6c1d9d97fb4ece393866dfe03bb

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  d0e69d3c4b4eef86ef51c68f1f9f1491861faa49

THREAD_SHA1_HASH_MOD:  8a8b82c1b789d2b57d111dee06f2d5d20bb3d242

FOLLOWUP_IP: 
atikmdag+12d9c
fffff880`03c54d9c 48895c2408      mov     qword ptr [rsp+8],rbx

FAULT_INSTR_CODE:  245c8948

SYMBOL_NAME:  atikmdag+12d9c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49f199cd

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys

PRIMARY_PROBLEM_CLASS:  X64_0x116_IMAGE_atikmdag.sys

TARGET_TIME:  2016-05-18T19:02:49.000Z

OSBUILD:  7600

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2010-10-27 08:13:09

BUILDDATESTAMP_STR:  101026-1503

BUILDLAB_STR:  win7_gdr

BUILDOSVER_STR:  6.1.7600.16695.amd64fre.win7_gdr.101026-1503

ANALYSIS_SESSION_ELAPSED_TIME: aaf

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmdag.sys

FAILURE_ID_HASH:  {7527b2fa-489f-c504-9452-1a10bd154401}

Followup:     MachineOwner
---------

0: kd> lmvm atikmdag
Browse full module list
start             end                 module name
fffff880`03c42000 fffff880`04164000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Apr 24 16:21:57 2009 (49F199CD)
    CheckSum:         004CC863
    ImageSize:        00522000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[virus01]

Something changed now - new BSOD 0x0000003b

Thank you Archie,

Yesterday I did the following steps:

- I installed the Windows 7 SP1 (without graphic-driver installed)

- Temperature-check with speedFan and Speccy (Screenshot is attached and I have a SpeccyScreenshot-Link too: http://speccy.piriform.com/results/oPyR2lRdypdEUxfoys17f6x
Temp seems to be OK: CPU= 54 °C Motherboard= 61 °C

- I installed the Catalyst 13.9 from the link you provided (i checked only graphic driver, no catalyst constrol center and so on)

After reboot everything was fine up to login. I logged in and before my Desktop showed up, the screen was black, then I saw my mouse and Taskbar, then againg black..after a while BSOD, but a new one: 0x0000003b. I have attached the dumpfiles and a screenshot of my last dumpfile with the new BSOD.
I rebooted and started in safe mode in order to remove the graphic-driver. Now I am working without a graphic-driver again.
Today I will install all other Windows Updates and try the same again. What does the new BSOD mean?
I saw there is a Windows-Hotfix for 0x0000003B. I will install this later too: http://support.microsoft.com/en-us/kb/2584454

Thank you

 

[Arc]

The temps are not very normal, they are approaching the critical level. Its the time to gift a cooling pad to your laptop.

But unfortunately I am failing to locate the new dumps in your post.

 

[virus01]

I am not wondering, the laptop is about 8,9 years old. I will open the back-cover for now. attached my dump-file after editing. Here I have it again

Thank you

 

[Arc]

BugCheck 3B, {c0000005, fffff800034e2687, fffff880034960d0, 0}


[COLOR=Red]Probably caused by : hardware [/COLOR]( nt+2cf687 )

Followup:     MachineOwner
---------

A 0x3B caused by hardware .... and it does not BSOD without a display driver. That gives a hint that it is the display hardware that is causing the issue. The state of dxdiag from your first post supports this observation too.

---------------
Display Devices
---------------
          Card name: 
       Manufacturer: 
          Chip type: 
           DAC type: 
         Device Key: Enum\
     Display Memory: n/a
   Dedicated Memory: n/a
      Shared Memory: n/a
       Current Mode: 1280 x 1024 (32 bit) (1Hz)
        Driver Name: 
Driver File Version:  ()
     Driver Version: 
        DDI Version: unknown
       Driver Model: unknown
  Driver Attributes: Final Retail
   Driver Date/Size: , 0 bytes
        WHQL Logo'd: n/a
    WHQL Date Stamp: n/a
  Device Identifier: {D7B70EE0-4340-11CF-B123-B03DAEC2CB35}
          Vendor ID: 0x0000
          Device ID: 0x0000
          SubSys ID: 0x00000000
        Revision ID: 0x0000
 Driver Strong Name: Unknown
     Rank Of Driver: Unknown
        Video Accel: 
      Deinterlace Caps: n/a
       D3D9 Overlay: n/a
            DXVA-HD: n/a
       DDraw Status: Not Available
         D3D Status: Not Available
         AGP Status: Not Available

When display causes the similar issue irrespective of the driver version installed, there is a fair chance that the display hardware is the source of the issue. Still, give it another go in order to be sure.

• Uninstall the installed display driver: http://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.html
• Download CCC 12.6 from here: Detail
• Install it following this guide: http://www.sevenforums.com/tutorial...install-without-catalyst-install-manager.html

Does it cause the same situation? Let us know. If so, it is a display hardware issue for sure.

 

[virus01]

Hello Archie,

Yesterday I did the following as you said:

1. Uninstalled the display driver using Display Driver Uninstaller
2. Installed CCC Version 12.6 only Display-Driver (without catalyst)

After Reboot, 0x00000116 BSOD again. I attached the DumpFiles. Hmm, seems it indeed is the hardware. Without a display driver, even the vertical grey lines in BIOS disappear.

Maybe it is only one resistor on my graphic card that has to be changed!?

Thanks for helping Archie

 

[Arc]

So we have seen the situation with at least three different driver versions. All resulted the same BSOD. So we can say it at this stage that the display hardware is failing.

Now, it may be the system heats that may make the graphics fail; or the graphics card is failing on itself. Whatever, it needs a servicing.

Divide the servicing task in two parts.
First, do a clean-up, dusting, re-applying the thermal paste to the CPU. when the system heat is under control, see how the computer works.
Second, if it causes the same BSOD irrespective of doing the above, better you replace the graphics card.

 

[virus01]

Ok Archie,
I will try the step you mentioned. I allready cleaned up the interior. Now I have to renew the thermal paste. If it does not work I will use the laptop without graphic driver until i buy a new one in 3 months.

Thank you very for your help, you are great
Regards,
virus