graphics card crashing, drivers installed and reinstalled windows same

Chatta66 · 29 Mar 2012

Ok here's a couple more.

writhziden · 29 Mar 2012

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\Chatta66\032912-20170-01\032912-20170-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e05000 PsLoadedModuleList = 0xfffff800`03049650
Debug session time: Thu Mar 29 18:39:19.743 2012 (UTC - 6:00)
System Uptime: 0 days 0:01:12.304
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 3e0, fffffa8009721230, fffff880053a9640}

Unable to load image LMouKE.Sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for LMouKE.Sys
*** ERROR: Module load completed but symbols could not be loaded for LMouKE.Sys
Probably caused by : LMouKE.Sys ( LMouKE+e640 )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000003e0, Handle value being referenced.
Arg3: fffffa8009721230, Address of the current process.
Arg4: fffff880053a9640, Address inside the driver that is performing the incorrect reference.

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  KHALMNPR.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000330a3dc to fffff80002e81d40

STACK_TEXT:  
fffff880`09868f98 fffff800`0330a3dc : 00000000`000000c4 00000000`000000f6 00000000`000003e0 fffffa80`09721230 : nt!KeBugCheckEx
fffff880`09868fa0 fffff800`0331fae4 : 00000000`000003e0 fffffa80`09721230 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`09868fe0 fffff800`031bea85 : 00000000`00000000 00000000`000003e0 fffff880`09869170 ffffffff`fffffd90 : nt!VfCheckUserHandle+0x1b4
fffff880`098690c0 fffff800`02e80fd3 : fffffa80`0b0b4060 fffff800`02eacb4b 00000000`00000001 fffff800`02e40f0e : nt! ?? ::NNGAKEGL::`string'+0x23045
fffff880`098690f0 fffff800`02e7d570 : fffff880`053a9640 fffff880`098695a9 fffff880`098695a0 ffffffff`fffffd90 : nt!KiSystemServiceCopyEnd+0x13
fffff880`09869288 fffff880`053a9640 : fffff880`098695a9 fffff880`098695a0 ffffffff`fffffd90 00000000`00000009 : nt!KiServiceLinkage
fffff880`09869290 fffff880`098695a9 : fffff880`098695a0 ffffffff`fffffd90 00000000`00000009 00000000`00000000 : LMouKE+0xe640
fffff880`09869298 fffff880`098695a0 : ffffffff`fffffd90 00000000`00000009 00000000`00000000 fffff880`00000000 : 0xfffff880`098695a9
fffff880`098692a0 ffffffff`fffffd90 : 00000000`00000009 00000000`00000000 fffff880`00000000 fffff880`098692e0 : 0xfffff880`098695a0
fffff880`098692a8 00000000`00000009 : 00000000`00000000 fffff880`00000000 fffff880`098692e0 0053002b`00000000 : 0xffffffff`fffffd90
fffff880`098692b0 00000000`00000000 : fffff880`00000000 fffff880`098692e0 0053002b`00000000 00000000`00140012 : 0x9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
LMouKE+e640
fffff880`053a9640 488d4c2440      lea     rcx,[rsp+40h]

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  LMouKE+e640

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: LMouKE

IMAGE_NAME:  LMouKE.Sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e60769c

FAILURE_BUCKET_ID:  X64_0xc4_f6_LMouKE+e640

BUCKET_ID:  X64_0xc4_f6_LMouKE+e640

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

1: kd> lmvm LMouKE
start             end                 module name
fffff880`0539b000 fffff880`053bc000   LMouKE   T (no symbols)           
    Loaded symbol image file: LMouKE.Sys
    Image path: LMouKE.Sys
    Image name: LMouKE.Sys
    Timestamp:        Fri Sep 02 00:24:28 2011 (4E60769C)
    CheckSum:         0002B0B5
    ImageSize:        00021000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The mouse is now up to date, but still causing problems. However, the problems may be due to the Logitech advanced configuration software. Go into Start Menu -> Control Panel -> Uninstall a Program

Remove any Logitech software listed. Restart your computer and let Windows install the device driver for your mouse when Windows starts up (assuming uninstalling the Logitech software also ends up uninstalling your mouse drivers).

Chatta66 · 03 Apr 2012

here's one from a recent crash I have had. I haven't had very much time this last week, overtime at work and what not.

writhziden · 03 Apr 2012

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\Chatta66\033012-18439-01\033012-18439-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e06000 PsLoadedModuleList = 0xfffff800`0304a650
Debug session time: Fri Mar 30 21:37:05.631 2012 (UTC - 6:00)
System Uptime: 0 days 3:02:29.802
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800c4f2010, fffff88004525ae4, 0, 2}

Unable to load image 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
Probably caused by : atikmpag.sys ( atikmpag+7ae4 )

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: fffffa800c4f2010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004525ae4, 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+7ae4
fffff880`04525ae4 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`07baf9c8 fffff880`05705000 : 00000000`00000116 fffffa80`0c4f2010 fffff880`04525ae4 00000000`00000000 : nt!KeBugCheckEx
fffff880`07baf9d0 fffff880`05704d0a : fffff880`04525ae4 fffffa80`0c4f2010 fffffa80`0ac4cbf0 fffffa80`09d1f010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`07bafa10 fffff880`057abf07 : fffffa80`0c4f2010 00000000`00000000 fffffa80`0ac4cbf0 fffffa80`09d1f010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`07bafa40 fffff880`057d5b75 : 00000000`ffffffff 00000000`000ab52d 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`07bafb20 fffff880`057d42bb : 00000000`00000102 00000000`00000000 00000000`000ab52d 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`07bafb50 fffff880`057a72c6 : ffffffff`ff676980 fffffa80`09d1f010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`07bafbf0 fffff880`057d3e7a : 00000000`00000000 fffffa80`0ac4cbf0 00000000`00000080 fffffa80`09d1f010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`07bafd00 fffff800`0311cf7a : 00000000`fffffc32 fffffa80`09b1fb60 fffffa80`06d0e040 fffffa80`09b1fb60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`07bafd40 fffff800`02e739c6 : fffff880`02fd5180 fffffa80`09b1fb60 fffff880`02fdffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`07bafd80 00000000`00000000 : fffff880`07bb0000 fffff880`07baa000 fffff880`0c113b70 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+7ae4
fffff880`04525ae4 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+7ae4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f597fca

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

Same graphics card error as usual. I do have some different steps for resolving it if you are willing to give them a go. Also, did you install an NVIDIA graphics card at any time since your last clean install? You may want to go through both graphics card removal steps if you did. Your AMD drivers look like they may be corrupted, so a re-install is in order:

Download the latest drivers for your display card(s)
Click Start Menu
Click Control Panel
Click Uninstall a program
For NVIDIA:
- Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
- Restart your computer
- Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
- If any remain of the above, uninstall one at a time
- If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
For AMD:
- Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
- If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers:
  1. Download the latest drivers for your display card(s)
  2. Click Start Menu
  3. Right Click My Computer/Computer
  4. Click Manage
  5. Click Device Manager from the list on the left
  6. Expand Display adapters
  7. Do the following for each adapter (in case you have multiple display cards)
    - Right click the adapter
    - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  8. Restart your computer after uninstalling drivers for all display cards
  9. Install the latest driver for the display cards once Windows starts
  Alternatively:
  1. Login as an adminstrative user
  2. Download the latest drivers for your display card(s)
  3. Click Start Menu
  4. Click Control Panel
  5. Click Hardware and Sound
  6. Click Device Manager (the last link under Devices and Printers)
  7. Expand Display adapters
  8. Do the following for each adapter (in case you have multiple display cards)
    - Right click the adapter
    - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer after uninstalling drivers for all display cards
Install the latest driver for the display cards once Windows starts

Chatta66 · 17 Apr 2012

Ok that's done now... We will see if it helps in time.

Chatta66 · 17 Apr 2012

Didn't fix the issue

writhziden · 17 Apr 2012

It is likely hardware, then. It could also be RAM incompatibility or settings. Let's check for these.

Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

Chatta66 · 18 Apr 2012

Ok here's the images.

writhziden · 18 Apr 2012

Did you do a clean install of Windows when you got the new motherboard?

If not, I would recommend it. Also, are you using any optimization software?

After clean installing Windows, do not use any optimization programs, and follow the steps in Hardware Troubleshooting Via System Stripdown

Chatta66 · 19 Apr 2012

I don't know what you mean by optimization software. I haven't done a clean install since I got the motherboard back yet being that it's not a new board it's the same board I sent away but I will do that before I run the tests. Which boot disk should I download. Keep in mind I have no floppy drive.