graphics card crashing, drivers installed and reinstalled windows same

[writhziden]

See my previous post for how long to run Furmark. I updated it with more information (and you already followed that information more than adequately)... Let us know how the video memtest goes.

 

[Chatta66]

15 passes no errors, I ran it over night.

 

[writhziden]

Looks good. How is the system behaving?

 

[Chatta66]

It's ok but still getting crashing. It seems to be that the drivers crash when i am currently access or have previously accessed the internet during the running period.

 

[Chatta66]

That being said, every time I try to run thr prime 95 test according to the specs on the AMD site I reach max temps on my CPU in under a minute. But I am using the program speed fan due to the one u recommended not working with my CPU. So I'm not sure if it's accurate or not.

 

[Chatta66]

When I reinstalled the CPU I applied new heat sink gel as well so I don't understand why it would get so hot so fast.

 

[writhziden]

Please upload the latest crash reports and we'll take a look to see if we can narrow down any culprits.

 

[Chatta66]

Ok so i downloaded a program called "Who Crashed" and apparently the cause of the last crash was a files called atikmpag.sys

 

[writhziden]

Who Crashed can be accurate, but it also often points to the wrong culprit. In this case, it is probably correct, but it would still help to verify through the crash reports.

FYI: atikmpag.sys is one of your graphics card drivers.

 

[Chatta66]

I'll upload one shortly just have to get the comp started up

 

[Chatta66]

Ok so it's not letting me RAR the dump file... keeps saying that the RAR file cannot open the dmp file and that access is denied. Also when I try to zip it it says "File not found or no read permission."

 

[writhziden]

Try copying the .dmp file to your documents folder (copy it, do not try to move it because you will not have the permissions to do so). Then compress the file.

 

[Chatta66]

Alrighty I'll give that a try

 

[Chatta66]

Well I'll have to remember how to do that now. Ok it's on here.

 

[writhziden]

Loading Dump File [D:\Kingston\BSODDmpFiles\Chatta66\032612-17456-01\032612-17456-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`02e51000 PsLoadedModuleList = 0xfffff800`03095650
Debug session time: Mon Mar 26 11:13:46.589 2012 (UTC - 6:00)
System Uptime: 0 days 20:10:46.150
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80070664e0, fffff8800419c9e0, 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
Probably caused by : atikmpag.sys ( atikmpag+79e0 )

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: fffffa80070664e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800419c9e0, 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+79e0
fffff880`0419c9e0 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`06fe99c8 fffff880`042f9000 : 00000000`00000116 fffffa80`070664e0 fffff880`0419c9e0 00000000`00000000 : nt!KeBugCheckEx
fffff880`06fe99d0 fffff880`042f8d0a : fffff880`0419c9e0 fffffa80`070664e0 fffffa80`0a351850 fffffa80`096ae410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06fe9a10 fffff880`0439ff07 : fffffa80`070664e0 00000000`00000000 fffffa80`0a351850 fffffa80`096ae410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`06fe9a40 fffff880`043c9b75 : 00000000`ffffffff 00000000`00470d9e 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`06fe9b20 fffff880`043c82bb : 00000000`00000102 00000000`00000000 00000000`00470d9e 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`06fe9b50 fffff880`0439b2c6 : ffffffff`ff676980 fffffa80`096ae410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`06fe9bf0 fffff880`043c7e7a : 00000000`00000000 fffffa80`0a351850 00000000`00000080 fffffa80`096ae410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06fe9d00 fffff800`03167f7a : 00000000`fffffc32 fffffa80`08b51b60 fffffa80`06d2eb30 fffffa80`08b51b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06fe9d40 fffff800`02ebe9c6 : fffff880`009e7180 fffffa80`08b51b60 fffff880`009f1fc0 00000000`000cf7b3 : nt!PspSystemThreadStartup+0x5a
fffff880`06fe9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+79e0
fffff880`0419c9e0 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+79e0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f3b14b8

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

It may be a faulty graphics card:

• These are all stop 0x116 VIDEO_TDR_FAILURE conditions.
  
  It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.
  
  Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash. As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds. If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.
  
  If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling.

  
  The above quote was taken from http://www.sevenforums.com/crashes-debugging/25912-bsod.html#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html and proceed through each step. Let us know if you need further help.

 

[Chatta66]

Ok, but that doesn't really explain why this would happen with my onboard as well.

 

[writhziden]

Correct, it does not. I forgot about that. So we are down to the CPU or PSU being the problem. Can you try a different PSU? It is possible yours is faulty. Borrow one from a friend if you can.

I am fairly certain this is hardware, but we could try checking for any underlying driver problems:

• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 204784
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

 

[Chatta66]

Ok here's a couple more dump files.

 

[writhziden]

Loading Dump File [D:\Kingston\BSODDmpFiles\Chatta66\032812-22370-01\032812-22370-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`02e5f000 PsLoadedModuleList = 0xfffff800`030a3650
Debug session time: Wed Mar 28 19:43:42.814 2012 (UTC - 6:00)
System Uptime: 0 days 0:01:48.375
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 4bc, fffffa8009bafb30, fffff88005372530}

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+e530 )

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

2: 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: 00000000000004bc, Handle value being referenced.
Arg3: fffffa8009bafb30, Address of the current process.
Arg4: fffff88005372530, 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 fffff800033643dc to fffff80002edbd40

STACK_TEXT:  
fffff880`0b4fdf98 fffff800`033643dc : 00000000`000000c4 00000000`000000f6 00000000`000004bc fffffa80`09bafb30 : nt!KeBugCheckEx
fffff880`0b4fdfa0 fffff800`03379ae4 : 00000000`000004bc fffffa80`09bafb30 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0b4fdfe0 fffff800`03218a85 : 00000000`00000010 00000000`000004bc fffff880`0b4fe170 ffffffff`fffffd90 : nt!VfCheckUserHandle+0x1b4
fffff880`0b4fe0c0 fffff800`02edafd3 : fffffa80`0afdab60 fffff800`02f06b4b fffff8a0`08aa85d0 fffff8a0`08aa85d0 : nt! ?? ::NNGAKEGL::`string'+0x23045
fffff880`0b4fe0f0 fffff800`02ed7570 : fffff880`05372530 fffff880`0b4fe5a9 fffff880`0b4fe5a0 ffffffff`fffffd90 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0b4fe288 fffff880`05372530 : fffff880`0b4fe5a9 fffff880`0b4fe5a0 ffffffff`fffffd90 00000000`00000009 : nt!KiServiceLinkage
fffff880`0b4fe290 fffff880`0b4fe5a9 : fffff880`0b4fe5a0 ffffffff`fffffd90 00000000`00000009 00000000`00000000 : LMouKE+0xe530
fffff880`0b4fe298 fffff880`0b4fe5a0 : ffffffff`fffffd90 00000000`00000009 00000000`00000000 fffff880`00000000 : 0xfffff880`0b4fe5a9
fffff880`0b4fe2a0 ffffffff`fffffd90 : 00000000`00000009 00000000`00000000 fffff880`00000000 fffff880`0b4fe2e0 : 0xfffff880`0b4fe5a0
fffff880`0b4fe2a8 00000000`00000009 : 00000000`00000000 fffff880`00000000 fffff880`0b4fe2e0 fffff880`00000000 : 0xffffffff`fffffd90
fffff880`0b4fe2b0 00000000`00000000 : fffff880`00000000 fffff880`0b4fe2e0 fffff880`00000000 00000000`00140012 : 0x9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
LMouKE+e530
fffff880`05372530 488d4c2440      lea     rcx,[rsp+40h]

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  LMouKE+e530

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: LMouKE

IMAGE_NAME:  LMouKE.Sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a391eda

FAILURE_BUCKET_ID:  X64_0xc4_f6_LMouKE+e530

BUCKET_ID:  X64_0xc4_f6_LMouKE+e530

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

Caused by your Logitech mouse driver: LMouKE.Sys

Would it be possible to try a different mouse? Borrow one from a friend or something?

You could also try updating the Logitech drivers for the mouse you have. They are slightly out of date.

 

[Chatta66]

I updated the drivers I'll run another couple verifier runs today and uploa some more dump files after I get home