BSOD on startup - atikmdag.sys - Vista x64

Hi GordyBoy87.

We need some more info. Only crash dumps are not enough.

Click on button below ....

It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
Screenshots and Files - Upload and Post in Seven Forums

Also do some more things ....

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

Update the display driver to the latest ..... Download Drivers . It is too old.

Code:

    Image name: atikmpag.sys
    Timestamp:        Thu Nov 10 07:42:44 2011 (4EBB331C)

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: Speccy - Publish Snapshot of your System Specs .

Let us know the results.
________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8005fa04e0, fffffa60024f58c8, 0, 2}

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
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : atikmpag.sys ( atikmpag+78c8 )

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

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

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


FAULTING_IP: 
atikmpag+78c8
fffffa60`024f58c8 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

STACK_TEXT:  
fffffa60`045c9a08 fffffa60`030c2e28 : 00000000`00000116 fffffa80`05fa04e0 fffffa60`024f58c8 00000000`00000000 : nt!KeBugCheckEx
fffffa60`045c9a10 fffffa60`030c2c5b : fffffa60`024f58c8 fffffa80`05fa04e0 fffffa80`0664e540 fffffa80`05fa04e0 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffffa60`045c9a50 fffffa60`0307c1c6 : 00000000`00000000 00000000`00000000 fffffa80`0664e540 00000000`00001b5f : dxgkrnl!TdrIsRecoveryRequired+0x16f
fffffa60`045c9a90 fffffa60`0313f9e3 : 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000002 : dxgkrnl!VidSchiReportHwHang+0x312
fffffa60`045c9b40 fffffa60`0313e5e5 : fffffa80`0664e540 fffffa80`00000000 00000000`00001b5f 00000000`00000000 : dxgkrnl!VidSchiCheckHwProgress+0x7b
fffffa60`045c9b70 fffffa60`03080534 : ffffffff`ff676980 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!VidSchiWaitForSchedulerEvents+0x199
fffffa60`045c9bf0 fffffa60`0313e405 : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0664e540 : dxgkrnl!VidSchiScheduleCommandToRun+0x398
fffffa60`045c9d10 fffff800`030b4227 : fffffa80`05bf7bb0 00000000`00000000 00000000`00000000 00000000`00000001 : dxgkrnl!VidSchiWorkerThread+0x95
fffffa60`045c9d50 fffff800`02ee5456 : fffff800`02fc4680 fffffa80`05bf7bb0 fffff800`02fc9b80 fffffa80`066fd138 : nt!PspSystemThreadStartup+0x57
fffffa60`045c9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+78c8
fffffa60`024f58c8 ??              ???

SYMBOL_NAME:  atikmpag+78c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ebb331c

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmpag.sys

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

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

1: kd> lmvm atikmpag
start             end                 module name
fffffa60`024ee000 fffffa60`02543000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Thu Nov 10 07:42:44 2011 (4EBB331C)
    CheckSum:         000502CB
    ImageSize:        00055000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

There is a fair chance that the graphics is not being able to perform. Specially when it refused to run furmark.

If you can, you may apply any other graphics card there, just to see if it is the same there or not. Let us know.