Overclock.net › Forums › Graphics Cards › Graphics Cards - General › TROUBLESHOOT HELP: BSOD, Catalyst failure, artifacts.
New Posts  All Forums:Forum Nav:

TROUBLESHOOT HELP: BSOD, Catalyst failure, artifacts.

post #1 of 17
Thread Starter 
Sup guys,

last week i bought a 2nd 6950 2GB Sapphire Dirt 3 unlocked and i have been having problems.

here's my rig:
Here's my rig, feel free to comment on what i should upgrade if i had $300 to spend.

Motherboard: Biostar TZ68A+
CPU: i5-2500k
Memory: 16GB GSKILL ripjaws 2133
GPU: 2x Sapphire 6950 2gb Dirt 3
Cooling: Corsair H80
PSU: Antec 620 neo eco
Boot Drive: Crucial M4 128gb
Storage: Seagate Baracuda 2TB


the problem:

While it appears to work smoothly, and it passes furmark (60seconds) and 3dmark11 i have the following problems
  1. once or twice i noticed something like artifacts but not really. for a couple seconds different numbers would appear on the BF3 game when i'm shooting ppl. it's like numbers or letters from the top-left chat got moved elsewhere. that happened once the 2nd day and then once today
  2. a couple times so far when playing BF3 and having youtube open in the left monitor i'll get a message (SEE IMAGE) from catalyst saying it failed, then the BF3 and the youtube screen go blank, even though the game and video are still playing
  3. the most concerning is twice today i got BSOD right after the above issue happened. within a minute or two later.

i've been trying to replicate this but i dont know how.

the 1 card is under warranty and the second one is USED. i would feel much better returning the card to Amazon and waiting a couple more months and buy a 6970. just to avoid two-card solutions entierly. i dont NEED the 2 GPU's right now, but my intention was to future-proof my computer.

btw, when i get the BSOD i have to power down. i can't just use the restart.

http://img846.imageshack.us/img846/2650/failrg.png

169
Hummingbird
(12 items)
 
  
CPUMotherboardGraphicsRAM
Intel® Core i5-2500K, 3.30 GHz EVGA Z68 FTW E-ATX Sapphire Radeon HD 6950, 2GB DiRT 3 Edition G.SKILL Ripjaws X Series 2 x 4GB - 2133 (PC3 17... 
Hard DriveHard DriveCoolingOS
Seagate Barracuda 2 TB Crucial M4 128 GB SSD  Corsair H80 Windows 8 6bit 
MonitorPowerCaseAudio
Asus VH238H Black 23" Full HD HDMI LED Backligh... Seasonic x860 Corsair Carbide 500R Logitech X-540 5.1 Surround Sound 
  hide details  
Reply
Hummingbird
(12 items)
 
  
CPUMotherboardGraphicsRAM
Intel® Core i5-2500K, 3.30 GHz EVGA Z68 FTW E-ATX Sapphire Radeon HD 6950, 2GB DiRT 3 Edition G.SKILL Ripjaws X Series 2 x 4GB - 2133 (PC3 17... 
Hard DriveHard DriveCoolingOS
Seagate Barracuda 2 TB Crucial M4 128 GB SSD  Corsair H80 Windows 8 6bit 
MonitorPowerCaseAudio
Asus VH238H Black 23" Full HD HDMI LED Backligh... Seasonic x860 Corsair Carbide 500R Logitech X-540 5.1 Surround Sound 
  hide details  
Reply
post #2 of 17
Hi smile.gif

Can you please navigate to C:/Windows/Minidump and zip / rar up your latest dump files? Once you've done that, please attach the zip / rar to your post by clicking the paperclip icon in the reply / post box.

If there are no files there, you may have it set to writing Kernel Memory Dumps rather than Small. If so, the DMP will be located in C:/Windows itself and named MEMORY.DMP.
post #3 of 17
Thread Starter 
Quote:
Originally Posted by E-Peen View Post

Hi smile.gif
Can you please navigate to C:/Windows/Minidump and zip / rar up your latest dump files? Once you've done that, please attach the zip / rar to your post by clicking the paperclip icon in the reply / post box.
If there are no files there, you may have it set to writing Kernel Memory Dumps rather than Small. If so, the DMP will be located in C:/Windows itself and named MEMORY.DMP.

check your PM.


feel free to respond in this thread rather than the PM. would probably benefit others
Hummingbird
(12 items)
 
  
CPUMotherboardGraphicsRAM
Intel® Core i5-2500K, 3.30 GHz EVGA Z68 FTW E-ATX Sapphire Radeon HD 6950, 2GB DiRT 3 Edition G.SKILL Ripjaws X Series 2 x 4GB - 2133 (PC3 17... 
Hard DriveHard DriveCoolingOS
Seagate Barracuda 2 TB Crucial M4 128 GB SSD  Corsair H80 Windows 8 6bit 
MonitorPowerCaseAudio
Asus VH238H Black 23" Full HD HDMI LED Backligh... Seasonic x860 Corsair Carbide 500R Logitech X-540 5.1 Surround Sound 
  hide details  
Reply
Hummingbird
(12 items)
 
  
CPUMotherboardGraphicsRAM
Intel® Core i5-2500K, 3.30 GHz EVGA Z68 FTW E-ATX Sapphire Radeon HD 6950, 2GB DiRT 3 Edition G.SKILL Ripjaws X Series 2 x 4GB - 2133 (PC3 17... 
Hard DriveHard DriveCoolingOS
Seagate Barracuda 2 TB Crucial M4 128 GB SSD  Corsair H80 Windows 8 6bit 
MonitorPowerCaseAudio
Asus VH238H Black 23" Full HD HDMI LED Backligh... Seasonic x860 Corsair Carbide 500R Logitech X-540 5.1 Surround Sound 
  hide details  
Reply
post #4 of 17
For future reference, a dump file does not show any personal information or information that you yourself wouldn't likely want the general public to see smile.gif

Regardless, I have analyzed your dump files:

Both dumps are your traditional TDR *116 bugcheck, both point to atikmpag.sys which is the ATI video card driver. There are a multitude of things that can cause this specific bugcheck. Before going into that, I should mention this:

When taking a look at your drivers list, dtsoftbus01.sys is listed. This is a Daemon Tool driver, and Daemon Tools is a very large cause of BSODs, please fully uninstall Daemon Tools.

NOTE: If overclocking, please reset the system to default values while troubleshooting it. This includes CPU, RAM, GPU overclocking. You're more than welcome to put your stocks back to clock after we've diagnosed your issues!!!!!

The first thing I recommend doing if overclocks aren't the issue is fully uninstalling and reinstalling your AMD video card drivers, as a bad driver installation can cause 116 bugchecks, especially since the culprit is being pointed to atikmpag.sys (ati video card drivers). If these issues started happening after a driver update, rollback the video card drivers you installed to an earlier version that worked previously without issue.

If drivers do not help, your issue may be heat related, inadequate cooling, dust buildup in the fans or pci-e slot, so make sure your rig is being cooled adequately.

Run Furmark to test your video card to ensure that the card(s) itself is running as intended:
Quote:
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

The following hardware issues can cause a TDR event:
Quote:
- Failing overclock on CPU or GPU (stop overclocking)
- Bad sector in memory resulting in corrupt data being communicated between GPU and the system (either video or system memory) ( MemTest and a video memory stress test: |MG| Video Memory Stress Test 1.7.116 Download )
- Corrupt hard drive/windows install resulting in corruption to the system registry or the page file (Hard drive diagnostics ( HD Diagnostic ), reset your pagefile

Memtest download to test your RAM: http://www.memtest86.com/

To "reset" the pagefile, follow these instructions:
Quote:
Use this technique to "reset" your pagefile:
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step b ). Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.

Run System File Checker:
Quote:
SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.

- Over heating of GPU or CPU again resulting in corrupt data being communicated. (Point a house fan at the video card, take temperature readings from the card with an IR detector (or your finger - but be very, very careful!!!)

- GPU failure due to any sort of issue from insufficient power(VERY common) to heat. (check the power leads, use a multimeter to check the power output, try another, more powerful PSU)

The following software issues can cause a TDR event:
Quote:
-Incompatible drivers of any sort (either GPU, sound, etc) ( http://www.microsoft.com/windows/com...s/default.aspx )
-Messy registry (I doubt this and don't approve of registry cleaners)
-Known vista issues resounding around multiple displays, aero, dreamscape, and various display drivers. (none known for this OS)
-Known vista issues that sometimes cause corrupt information to be sent to the video card from system memory (will be addressed completely in SP2, has had various fixes applied since vista's release) (none known for this OS)
-Bad direct x files (uninstall, then reinstall DirectX)
-bad system files (System File Checker - was run above)
-Bad driver (some drivers will cause an event due to internal bugs, however these are not nearly as common as many think due to all of the previous things causing the same symptom) - (remove all 3rd party programs and check to be sure drivers aren't loading. Then install only the necessary 3rd party stuff, and ensure it's the latest version and that it's compatible with Windows 7)

Dumps for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\New folder\040612-10842-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`03290e70
Debug session time: Fri Apr  6 14:53:13.366 2012 (UTC - 4:00)
System Uptime: 0 days 4:45:07.646
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8012add010, fffff88003f9f9e0, 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
---------

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8012add010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003f9f9e0, 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`03f9f9e0 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`121e1a28 fffff880`04154000 : 00000000`00000116 fffffa80`12add010 fffff880`03f9f9e0 00000000`00000000 : nt!KeBugCheckEx
fffff880`121e1a30 fffff880`04153d0a : fffff880`03f9f9e0 fffffa80`12add010 fffffa80`11a0e010 fffffa80`108ff010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`121e1a70 fffff880`0400ff07 : fffffa80`12add010 00000000`00000000 fffffa80`11a0e010 fffffa80`108ff010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`121e1aa0 fffff880`04039b75 : fffffa80`ffffffff 00000000`0010bb32 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`121e1b80 fffff880`0400b2d5 : fffffa80`108ff010 fffffa80`00000005 00000000`0010bb32 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`121e1bb0 fffff880`04037e7a : 00000000`00000000 fffffa80`12fe86a0 00000000`00000080 fffffa80`108ff010 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
fffff880`121e1cc0 fffff800`03363726 : 00000000`fffffc32 fffffa80`1091f4d0 fffffa80`0d96a740 fffffa80`1091f4d0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`121e1d00 fffff800`030a2ac6 : fffff880`02fd5180 fffffa80`1091f4d0 fffff880`02fdffc0 fffff880`012452b4 : nt!PspSystemThreadStartup+0x5a
fffff880`121e1d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+79e0
fffff880`03f9f9e0 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
---------


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\New folder\040612-11232-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03064000 PsLoadedModuleList = 0xfffff800`032a0e70
Debug session time: Fri Apr  6 23:57:21.058 2012 (UTC - 4:00)
System Uptime: 0 days 9:03:14.338
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80125924e0, fffff880040579e0, 0, 2}

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80125924e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880040579e0, 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`040579e0 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`0a1dc818 fffff880`04102000 : 00000000`00000116 fffffa80`125924e0 fffff880`040579e0 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a1dc820 fffff880`04101d0a : fffff880`040579e0 fffffa80`125924e0 fffffa80`10a50670 fffffa80`10992010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0a1dc860 fffff880`0533bf07 : fffffa80`125924e0 00000000`00000000 fffffa80`10a50670 fffffa80`10992010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0a1dc890 fffff880`05369d5a : fffffa80`ffffffff 00000000`001fe10e fffff880`0a1dc9f0 fffffa80`10992010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0a1dc970 fffff880`053658f0 : 00000000`00000000 ffffffff`feced300 fffffa80`107a6c00 fffff880`05366a72 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`0a1dc9b0 fffff880`053644fd : fffffa80`10992128 00000000`00022a76 fffffa80`10992010 fffff880`0a1dccc0 : dxgmms1!VidSchiWaitForFence+0xf4
fffff880`0a1dcaa0 fffff880`05364398 : fffff800`00b96080 fffff880`05363dc0 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0xe1
fffff880`0a1dcc90 fffff880`05363e96 : 00000000`00000000 fffffa80`10771670 00000000`00000080 fffffa80`10992010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`0a1dccc0 fffff800`03373726 : 00000000`fffffc32 fffffa80`109ed620 fffffa80`0d984740 fffffa80`109ed620 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0a1dcd00 fffff800`030b2ac6 : fffff800`0324de80 fffffa80`109ed620 fffff800`0325bc40 fffff880`0125d2b4 : nt!PspSystemThreadStartup+0x5a
fffff880`0a1dcd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+79e0
fffff880`040579e0 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
---------



post #5 of 17
Thread Starter 
jesus christ. gotta read thru all that.

btw, i'm not overclocking and when i play games i always have speedfan on monitoring temps. it NEVER goes beyond 63 degress for the cards OR the cpu. i got a great air cooling configuration ;-p
Hummingbird
(12 items)
 
  
CPUMotherboardGraphicsRAM
Intel® Core i5-2500K, 3.30 GHz EVGA Z68 FTW E-ATX Sapphire Radeon HD 6950, 2GB DiRT 3 Edition G.SKILL Ripjaws X Series 2 x 4GB - 2133 (PC3 17... 
Hard DriveHard DriveCoolingOS
Seagate Barracuda 2 TB Crucial M4 128 GB SSD  Corsair H80 Windows 8 6bit 
MonitorPowerCaseAudio
Asus VH238H Black 23" Full HD HDMI LED Backligh... Seasonic x860 Corsair Carbide 500R Logitech X-540 5.1 Surround Sound 
  hide details  
Reply
Hummingbird
(12 items)
 
  
CPUMotherboardGraphicsRAM
Intel® Core i5-2500K, 3.30 GHz EVGA Z68 FTW E-ATX Sapphire Radeon HD 6950, 2GB DiRT 3 Edition G.SKILL Ripjaws X Series 2 x 4GB - 2133 (PC3 17... 
Hard DriveHard DriveCoolingOS
Seagate Barracuda 2 TB Crucial M4 128 GB SSD  Corsair H80 Windows 8 6bit 
MonitorPowerCaseAudio
Asus VH238H Black 23" Full HD HDMI LED Backligh... Seasonic x860 Corsair Carbide 500R Logitech X-540 5.1 Surround Sound 
  hide details  
Reply
post #6 of 17
Quote:
Originally Posted by Simplynicko View Post

jesus christ. gotta read thru all that.
btw, i'm not overclocking and when i play games i always have speedfan on monitoring temps. it NEVER goes beyond 63 degress for the cards OR the cpu. i got a great air cooling configuration ;-p

Take your time smile.gif

As far as the overclocking goes, I just include it in every diagnosing situation just in case the user has no rig in their signature, etc.
post #7 of 17
Thread Starter 
ill do it tmw. too beat.
Hummingbird
(12 items)
 
  
CPUMotherboardGraphicsRAM
Intel® Core i5-2500K, 3.30 GHz EVGA Z68 FTW E-ATX Sapphire Radeon HD 6950, 2GB DiRT 3 Edition G.SKILL Ripjaws X Series 2 x 4GB - 2133 (PC3 17... 
Hard DriveHard DriveCoolingOS
Seagate Barracuda 2 TB Crucial M4 128 GB SSD  Corsair H80 Windows 8 6bit 
MonitorPowerCaseAudio
Asus VH238H Black 23" Full HD HDMI LED Backligh... Seasonic x860 Corsair Carbide 500R Logitech X-540 5.1 Surround Sound 
  hide details  
Reply
Hummingbird
(12 items)
 
  
CPUMotherboardGraphicsRAM
Intel® Core i5-2500K, 3.30 GHz EVGA Z68 FTW E-ATX Sapphire Radeon HD 6950, 2GB DiRT 3 Edition G.SKILL Ripjaws X Series 2 x 4GB - 2133 (PC3 17... 
Hard DriveHard DriveCoolingOS
Seagate Barracuda 2 TB Crucial M4 128 GB SSD  Corsair H80 Windows 8 6bit 
MonitorPowerCaseAudio
Asus VH238H Black 23" Full HD HDMI LED Backligh... Seasonic x860 Corsair Carbide 500R Logitech X-540 5.1 Surround Sound 
  hide details  
Reply
post #8 of 17
Quote:
Originally Posted by Simplynicko View Post

169

Crashing on flash videos? Disable hardware accel. Right click the vid settings...
The 3930
(26 items)
 
Junior's 3930
(22 items)
 
DATA/HTPC
(20 items)
 
  hide details  
Reply
The 3930
(26 items)
 
Junior's 3930
(22 items)
 
DATA/HTPC
(20 items)
 
  hide details  
Reply
post #9 of 17
Quote:
Originally Posted by tsm106 View Post

Crashing on flash videos? Disable hardware accel. Right click the vid settings...

Except BF3 isn't Flash, and that's not crashing, it's green, not the actual content. It's more than likely a very simple driver issue that can be solved with a driver uninstall and reinstall, or the 2nd card he's received is bad.
post #10 of 17
Thread Starter 
just as an update i used driver sweeper to get rid of everything and went for a clean install.

is there anyway i can replicate a BSOD? i dont want to have to play hours of BF3. don't have the time. lol.
Hummingbird
(12 items)
 
  
CPUMotherboardGraphicsRAM
Intel® Core i5-2500K, 3.30 GHz EVGA Z68 FTW E-ATX Sapphire Radeon HD 6950, 2GB DiRT 3 Edition G.SKILL Ripjaws X Series 2 x 4GB - 2133 (PC3 17... 
Hard DriveHard DriveCoolingOS
Seagate Barracuda 2 TB Crucial M4 128 GB SSD  Corsair H80 Windows 8 6bit 
MonitorPowerCaseAudio
Asus VH238H Black 23" Full HD HDMI LED Backligh... Seasonic x860 Corsair Carbide 500R Logitech X-540 5.1 Surround Sound 
  hide details  
Reply
Hummingbird
(12 items)
 
  
CPUMotherboardGraphicsRAM
Intel® Core i5-2500K, 3.30 GHz EVGA Z68 FTW E-ATX Sapphire Radeon HD 6950, 2GB DiRT 3 Edition G.SKILL Ripjaws X Series 2 x 4GB - 2133 (PC3 17... 
Hard DriveHard DriveCoolingOS
Seagate Barracuda 2 TB Crucial M4 128 GB SSD  Corsair H80 Windows 8 6bit 
MonitorPowerCaseAudio
Asus VH238H Black 23" Full HD HDMI LED Backligh... Seasonic x860 Corsair Carbide 500R Logitech X-540 5.1 Surround Sound 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Graphics Cards - General
Overclock.net › Forums › Graphics Cards › Graphics Cards - General › TROUBLESHOOT HELP: BSOD, Catalyst failure, artifacts.