Graphic Card issue

Mirlind · Jul 27, 2012

Hi, so guys, I got a new PC etc.. (it's a lame one but it does the job), anyways. I got an issue with my graphic card an "6670HD Sapphire 1GB DDR5", it gives me some errors like "Blue screen of death" which happens rare, and before it did give me the "AMD driver has stopped responding and has successfully recovered...", now it just freezes my PC and I need to restart it. And the most weird thing is that it happens in windows or an browser (never while playing games, or doing anything demanding). I know for sure this is not the graphic cards fault itself as an hardware, I think its more related to "TDR (Timeout Detection and Recovery)". So I would like you guys to either help me config the TDR's registry keys, or someone could upload them (specially those who have same Graphic Card as I), and also if someone has an HD6670 Graphic Card please let me know what drivers he's using, cause it might be driver related too. At the moment I'm using BETA drivers, which didn't make it worse neither better.

Hengis · Jul 27, 2012

Hi

Click on the BSOD link below and let's see you logs...

Mirlind · Jul 28, 2012

Here you go, and just reply if I haven't done something correctly, btw to assist you a bit:

* It never happens ingame (except for CS 1.6) all other games run smoothly I can play days without a problem.
* It only happens while browsing windows and sometimes while browsing the internet,
* 95% of the time it happens in the morning (when I start PC for the first time that day).
* Also,, when I remove the drivers completely from my PC (with the help of "DriveSweeper"), and even if I install the same ones again, during that session (PC being turned on after driver installation), it will never occur to have issues (BSOD).
* Most of the time, after my PC "can't respond and sometimes turns all black", I just restart it and it runs smoothly like it never had any problems... Oo"
* I am a little bit confused, but I know for sure it is no hardware failure whatsoever.

Thanks in advance Hengis (you helped me before and I appreciate it more then you think)

Peace

Hengis · Jul 28, 2012

Moved to the BSOD forum.

madmonkey · Jul 28, 2012

Hello Mirlind, welcome to PCHF.

Please don't mess with the TDR values in the registry, as TDR is not the cause of your problems (otherwise we would all be having the same problem). All you would be doing is working around the problem in some cases, delaying the time between freeze and reset and not actually fixing the underlying cause. If DirectX (the feature responsible for providing TDR) detects a lockup, then it will recover from that condition by resetting both driver and GPU. A successful reset will show as a successfully recovered error in the system tray. A failed reset will then result in a BSOD. Failed reset's are more commonly hardware related, but certainly try a different version of the graphics driver just to rule that out as a possibility. Also, recommend updating your system via Control Panel > System and Security > Check for updates. Updates not only include security updates to your system, but fixes to known problems as well.

In the logs you provided, there was only a single log file from the BSOD's you received, and these were not caused by the GPU. The problem was detected by the CPU (effectively hardware problem) in the form of an MCE (Machine Check Exception). Problem was an internal Bus error (see also WHEA record below). So if related, I don't believe the graphics card is directly the cause of your problems either, but there is definitely a hardware issue we need to resolve. It would certainly explain why you don't have any problems whilst gaming, which are usually heat related problems. Was this graphics card (or any other hardware) installed after you purchased the PC? What is the make and model of the PC, or is this a custom built PC?

To get more information about your system, including configuration, voltages and temperates, please can you upload a CPU-Z log. After it has been downloaded, click on the About tab, followed by Save Report (TXT). This will produce a readable log file which you'll be able to upload here.

BUGCHECK

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Users\admin\Desktop\PCHF\072712-23524-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
WARNING: Inaccessible path: 'C:\Program Files\Debugging Tools for Windows (x64)\symbols'
Symbol search path is: C:\Program Files\Debugging Tools for Windows (x64)\symbols;http://msdl.microsoft.com/download/symbols;symsrv*symsrv.dll*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82c3f000 PsLoadedModuleList = 0x82d87810
Debug session time: Sat Jul 28 03:20:39.100 2012 (GMT+1)
System Uptime: 0 days 0:00:06.910
Loading Kernel Symbols
...............................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 124, {0, 8660d024, 0, 0}
 
Probably caused by : hardware
 
Followup: MachineOwner
---------
 
1: kd> !analyze -v
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************
 
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 8660d024, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.
 
Debugging Details:
------------------
 
 
BUGCHECK_STR:  0x124_GenuineIntel
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
STACK_TEXT: 
8df27cc4 82d0dfc5 8660d008 82da6c28 82da6c20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8df27ce4 82d0edef 82da6c20 8660d008 82da6c50 nt!WheapProcessWorkQueueItem+0x56
8df27d00 82cacf2b 82da6c20 00000000 857aa020 nt!WheapWorkQueueWorkerRoutine+0x1f
8df27d50 82e4d66d 00000001 be2dcc15 00000000 nt!ExpWorkerThread+0x10d
8df27d90 82cff0d9 82cace1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: hardware
 
IMAGE_NAME:  hardware
 
DEBUG_FLR_IMAGE_TIMESTAMP:  0
 
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV
 
BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV
 
Followup: MachineOwner
---------
 
1: kd> !whea
Error Source Table @ 82d75ae8
0 Error Sources
1: kd> !analyze -v -hang
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************
 
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 8660d024, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.
 
Debugging Details:
------------------
 
Scanning for threads blocked on locks ...
82d79698: Unable to get value of ExpSystemResourcesList
 
BUGCHECK_STR:  0x124_GenuineIntel
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
BLOCKED_THREAD:  857aa020
 
STACK_TEXT: 
8df27cc4 82d0dfc5 8660d008 82da6c28 82da6c20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8df27ce4 82d0edef 82da6c20 8660d008 82da6c50 nt!WheapProcessWorkQueueItem+0x56
8df27d00 82cacf2b 82da6c20 00000000 857aa020 nt!WheapWorkQueueWorkerRoutine+0x1f
8df27d50 82e4d66d 00000001 be2dcc15 00000000 nt!ExpWorkerThread+0x10d
8df27d90 82cff0d9 82cace1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: hardware
 
IMAGE_NAME:  hardware
 
DEBUG_FLR_IMAGE_TIMESTAMP:  0
 
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV
 
BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV
 
Followup: MachineOwner
---------

WHEA Record

Code:

===============================================================================
Common Platform Error Record @ 8660d024
-------------------------------------------------------------------------------
Record Id    : 01cd6c679123e362
Severity      : Fatal (1)
Length        : 928
Creator      : Microsoft
Notify Type  : Machine Check Exception
Timestamp    : 7/28/2012 2:20:39
Flags        : 0x00000002 PreviousError
 
===============================================================================
Section 0    : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ 8660d0a4
Section      @ 8660d17c
Offset        : 344
Length        : 192
Flags        : 0x00000001 Primary
Severity      : Fatal
 
Proc. Type    : x86/x64
Instr. Set    : x86
Error Type    : BUS error
Operation    : Generic
Flags        : 0x00
Level        : 0
CPU Version  : 0x000000000001067a
Processor ID  : 0x0000000000000000
 
===============================================================================
Section 1    : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ 8660d0ec
Section      @ 8660d23c
Offset        : 536
Length        : 128
Flags        : 0x00000000
Severity      : Fatal
 
Local APIC Id : 0x0000000000000000
CPU Id        : 7a 06 01 00 00 08 02 00 - bd e3 00 0c ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
 
Proc. Info 0  @ 8660d23c
 
===============================================================================
Section 2    : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ 8660d134
Section      @ 8660d2bc
Offset        : 664
Length        : 264
Flags        : 0x00000000
Severity      : Fatal
 
Error        : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xb200004000000800

Mirlind · Jul 29, 2012

The PC was bought seperately, I bought the graphic card after receiving my PC, anyways, I still hardly believe its Hardware related, as I did the following:

1. Removed all AMD related drivers (Cataclyst)
2. Reinstalled them, but did a Costum installation, and I installed only the basics
3. After doing so, its been I think 3 days, without any problems.
4. Anyways the only issue I'm yet having is, how come my PC can handle any kind of game on High settings, except CS 1.6, where I play for like half-hour sometimes even more, and then it just freeze's and I need to close application using Task Manager.

Thanks in advance

madmonkey · Jul 29, 2012

Look at it this way, there's no way that re-installing a graphics driver would only temporarily fix a problem for a few days. That graphics driver would not have changed during that time unless you had installed something else. So many times have I thought a problem was fixed after making a change only to find out it was still there hours or days later .. it's just something you get used to when your trying to resolve a problem such as this. The best way to rule out software completely would be on a clean installation. Install nothing else but the essentials - Windows and whatever bare minimum software you need to test.

As I mentioned previously though, this doesn't appear to be a stress (such as overheating) problem, and the CPU-Z log has confirmed that. You voltage rails though do look impossibly low, confirming my original suspicions but these readings are not always right. You didn't answer my earlier questions about the PC?

Mirlind · Jul 29, 2012

Which question are you referring to?
Btw the fix is not temporary fixed it's gone for like 4 days now... not a single freeze,
Anyways now that I recall, I had some Beta Drivers installed and I did remove them to install normal ones that may helped but I doubt that was it, cause I had normal drivers before and the freeze did happen. My primary suspect which may resolved the problem is that I did install only the very essentials of the "Cataclyst" software, and ofc removed all the Registry Keys that I did customize.

Thanks in advance

madmonkey · Jul 29, 2012

OK, so 4 days, no problem, it looks like the problem may have been solved?

Mirlind · Jul 29, 2012

I'm preety sure, the only issue atm is that. only CS 1.6 out of any application, game or w.e else that's on the PC, it freeze's my PC... Only CS 1.6... Oo"

madmonkey · Jul 29, 2012

I'm not really familiar with Counter Strike (I'm assuming this is the CS 1.6 your talking about). I'll move this into the Crashes section of the forum if that's OK, or would you like to start a separate thread for that issue?

Mirlind · Aug 18, 2012

Do as you wish mate, I need it to be fixed don't care how, do which one is easier for you

mkey82 · Aug 18, 2012

Pardon me, but why not stress test the machine and see what's what?

Mirlind · Aug 19, 2012

mkey82 you don't understand all the games work fine except CS 1.6 and even that game works sometimes flawlessly and other times it crashes within 5 minutes of gameplay.

mkey82 · Aug 19, 2012

No, you do not understand something is wrong with your machine.

Log in or Join Us

Graphic Card issue

Mirlind Gold Member

Hengis PCHF Manager

Mirlind Gold Member

Attached Files:

PCHF.rar

Google Advertisement

Hengis PCHF Manager

madmonkey Site Manager

Mirlind Gold Member

Attached Files:

MIRLIND-PC.txt

madmonkey Site Manager

Mirlind Gold Member

madmonkey Site Manager

Mirlind Gold Member

madmonkey Site Manager

Mirlind Gold Member

mkey82 Je ne sais quois

Mirlind Gold Member

mkey82 Je ne sais quois

Graphic Card issue

Log in or Join Us

Graphic Card issue

Mirlind Gold Member

Hengis PCHF Manager

Mirlind Gold Member

Attached Files:

PCHF.rar

Google Advertisement

Hengis PCHF Manager

madmonkey Site Manager

Mirlind Gold Member

Attached Files:

MIRLIND-PC.txt

madmonkey Site Manager

Mirlind Gold Member

madmonkey Site Manager

Mirlind Gold Member

madmonkey Site Manager

Mirlind Gold Member

mkey82 Je ne sais quois

Mirlind Gold Member

mkey82 Je ne sais quois

Graphic Card issue

Useful Searches