r3 6970m overclock bsod

[jimbo312]

ever since i installed a my 6970m in my r3 i haven't been able to overclock because of bsod. its stable through the burning of furmark but once a game loads up i get an instant bsod. also my temps aren't just too terrible bad but i think may be just a little high at stock temps.as im typing this my sensors trhough gpu-z are GPU Temperature: 62-64 GPU Temp. #1: 63-65 GPU Temp #2: 63-65 GPU Temp #3: 67-69

i used the two long pads from my 6870m and for the rest i used the pads that came with my 6970m from upgradeyourlaptop on ebay. Should i buy the 1mm fujipoly pads to use instead of the pads that came with my card. would bad thermal pad contact cause my system to bsod on an overclock? thanks for your time.


Edit: and its not an extreme oc btw. i should be able to get a core clock of 750 stable but i can't get 720 stable and i haven't tried anything lowere because not much of a point to oc much less than that since my stock clocks are 680

[mark_j]

You're idle temps are similar to mine. I think it's because the fan is set to off/super slow rpm until it the card heats up.

My card only gets to 72c under load and 73c overclocked to 800/1000 because the fans ramp up quickly.

Find something to prop up the rear of your machine to get better ventilation. It dropped my oc temps 8c !!

Sent from my DROID RAZR using Tapatalk 2

[jimbo312]

i keep mine elevated at all times using a plastic coaster. i hit 79 or 80 on my hottest sensor when under a load. my main concern is my bsod when overclocking. thanks for the reply

[SlickDude80]

what is the bsod error code?

[jimbo312]

ill check it later and post it

[aznpos531]

Zip and upload your dump files from C:\Windows\Minidump and I'll analyze them for you.

[jimbo312]

here are the dump files from the specified folder.

[aznpos531]

All three of the dumps that you uploaded were graphics related. Two of them were 116 TDR errors caused by your ATI GPU Driver:

Spoiler :

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8007951010, fffff88009a0744c, 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+744c )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8007951010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88009a0744c, 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+744c
fffff880`09a0744c 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`088bd888 fffff880`02ec3000 : 00000000`00000116 fffffa80`07951010 fffff880`09a0744c 00000000`00000000 : nt!KeBugCheckEx
fffff880`088bd890 fffff880`02ec2d0a : fffff880`09a0744c fffffa80`07951010 fffffa80`0c378010 fffffa80`0b683010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`088bd8d0 fffff880`02f69f07 : fffffa80`07951010 00000000`00000000 fffffa80`0c378010 fffffa80`0b683010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`088bd900 fffff880`02f93b75 : 00000000`ffffffff 00000000`000037ed 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`088bd9e0 fffff880`02f922bb : 00000000`00000102 00000000`00000000 00000000`000037ed 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`088bda10 fffff880`02f652c6 : ffffffff`ff676980 fffffa80`0b683010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`088bdab0 fffff880`02f91e7a : 00000000`00000000 fffffa80`0c378010 00000000`00000080 fffffa80`0b683010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`088bdbc0 fffff800`03127fee : fffff880`039b1b10 fffffa80`0bad2b60 fffffa80`07307040 fffff800`02e84757 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`088bdc00 fffff800`02e7e5e6 : fffff880`031d7180 fffffa80`0bad2b60 fffff880`031e20c0 fffff880`01239cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`088bdc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+744c
fffff880`09a0744c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+744c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4df18388

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

The other was a 0x1000007E Stop Error caused by igdpmd64.sys which is your integrated Intel graphics driver:

Spoiler :

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88005c048ba, fffff880035626a8, fffff88003561f00}

Probably caused by : igdpmd64.sys ( igdpmd64+3ac8ba )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88005c048ba, The address that the exception occurred at
Arg3: fffff880035626a8, Exception Record Address
Arg4: fffff88003561f00, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
igdpmd64+3ac8ba
fffff880`05c048ba 83b86803000000  cmp     dword ptr [rax+368h],0

EXCEPTION_RECORD:  fffff880035626a8 -- (.exr 0xfffff880035626a8)
ExceptionAddress: fffff88005c048ba (igdpmd64+0x00000000003ac8ba)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000002966368
Attempt to read from address 0000000002966368

CONTEXT:  fffff88003561f00 -- (.cxr 0xfffff88003561f00)
rax=0000000002966000 rbx=fffff8a0017f3450 rcx=0000000000000000
rdx=fffff8a0006d7558 rsi=fffff8a001dd4b50 rdi=fffff88003562a40
rip=fffff88005c048ba rsp=fffff880035628e0 rbp=fffff8a0017f3450
 r8=0000000000000004  r9=fffffa800a4e5000 r10=00000000ffffffff
r11=fffff80002c52000 r12=0000000000000000 r13=0000000000000001
r14=0000000000000001 r15=fffff80002e6bf20
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
igdpmd64+0x3ac8ba:
fffff880`05c048ba 83b86803000000  cmp     dword ptr [rax+368h],0 ds:002b:00000000`02966368=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000002966368

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f01100
 0000000002966368 

FOLLOWUP_IP: 
igdpmd64+3ac8ba
fffff880`05c048ba 83b86803000000  cmp     dword ptr [rax+368h],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from ffffe499747eb684 to fffff88005c048ba

STACK_TEXT:  
fffff880`035628e0 ffffe499`747eb684 : 00000000`00000000 fffff800`02dd52c0 00000000`00000000 00000000`02966000 : igdpmd64+0x3ac8ba
fffff880`035628e8 00000000`00000000 : fffff800`02dd52c0 00000000`00000000 00000000`02966000 fffffa80`0a4e5000 : 0xffffe499`747eb684


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  igdpmd64+3ac8ba

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdpmd64

IMAGE_NAME:  igdpmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cd2d2f3

STACK_COMMAND:  .cxr 0xfffff88003561f00 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_igdpmd64+3ac8ba

BUCKET_ID:  X64_0x7E_igdpmd64+3ac8ba

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

I don't know much about overclocking but if you're convinced that it's not the cause of you BSOD then you may want to try reinstalling your GPU drivers. Uninstall your existing drivers and use CCleaner or DriverSweeper in safe mode to clear out the remaining registry entries. Then on the a fresh restart, install the latest version of the drivers using a clean installation option (if available on ATI drivers).

[jimbo312]

ill try that and then ill try it again and if it does it again ill upload the dmp from it. thanks.

[aznpos531]

Let us know how it works out