Random BSOD crashes - grapics problems?

daverobertsfilm · 09 Mar 2015

Hi, just had a new work PC but I keep getting random blue screens. It mentions an ati .sys file and I tried in installing and re installing the driver but it didn't seem to help.
Anyway, I have attached a zip with the BSOD info, would greatly appreciate some help.
Cheers Dave.

Arc · 10 Mar 2015

Yes, graphics problem.

Uninstall the installed display driver using DDU. Then install the CCC 14.4 WHQL only.

When done, 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. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.

eXtreme Power Supply Calculator - The only power supply calculator trusted by PSU manufacturers and computer enthusiasts

Also let us know the wattage of teh PSU that is installed in your Optiplex 990. Is it 240 watts?

EDIT: Well, it seems that RADEON X600 PRO graphics chip is nicely old and it may not support the latest drivers. I am not a radeon user, I am not very sure about it.

If 14.4 WHQL does not work for you, try AMD Driver Autodetect and see which driver it takes. Let us know it, also let us know the resulting situation after installing it.
____________________________________________

Code:

BugCheck 116, {fffffa8006da7010, fffff880048a5d9c, 0, 2}

*** 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
---------

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006da7010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880048a5d9c, 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: 
atikmdag+12d9c
fffff880`048a5d9c 48895c2408      mov     qword ptr [rsp+8],rbx

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:  
fffff880`020fc888 fffff880`03d52134 : 00000000`00000116 fffffa80`06da7010 fffff880`048a5d9c 00000000`00000000 : nt!KeBugCheckEx
fffff880`020fc890 fffff880`03d51e3e : fffff880`048a5d9c fffffa80`06da7010 fffffa80`06a38940 fffffa80`079a5010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`020fc8d0 fffff880`04dc4f13 : fffffa80`06da7010 00000000`00000000 fffffa80`06a38940 fffffa80`079a5010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`020fc900 fffff880`04deecf1 : 00000000`ffffffff 00000000`00005481 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`020fc9e0 fffff880`04ded437 : 00000000`00000102 00000000`00000000 00000000`00005481 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`020fca10 fffff880`04dc02d2 : ffffffff`ff676980 fffffa80`079a5010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`020fcab0 fffff880`04decff6 : 00000000`00000000 fffffa80`06a15d50 00000000`00000080 fffffa80`079a5010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`020fcbc0 fffff800`02f13b8a : 00000000`fffffc32 fffffa80`079a4b50 fffffa80`069b6040 fffffa80`079a4b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`020fcc00 fffff800`02c668e6 : fffff800`02df1e80 fffffa80`079a4b50 fffff800`02dffcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`020fcc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

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

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

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmdag.sys

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

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

2: kd> lmvm atikmdag
start             end                 module name
fffff880`04893000 fffff880`04db5000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Fri Apr 24 16:21:57 2009 (49F199CD)
    CheckSum:         004CC863
    ImageSize:        00522000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4