Graphics Problem... See contents

[tankbuster1221]

So, I just finished up a new build

AMD FX8350
ASUS SABERTOOTH 990FX R.2
Radeon HD 7970 DD
Corsair 16G DDR3 1866
Zalman 9500 Heatsink
Kingston 120GB Hyper X 3 SSD
1TB Seagate Barracuda HDD
750W NZXT HALE PSU


Having some issues though....

Mainly I have been getting these small horizontal black lines that litter my screen after the system is idleing for awhile (just browsing the internet). The lines move as I interact with the system, changing location very erratically and sometimes parts of the screen will stretch across the entire display... for example (I'l do my best to describe) the google chrome taskbar at the top will just stretch in a pointed manner down toward the bottom of the screen. I haven't even played a single game yet! I just noticed that the banner ad at the top of the forum for IBM is flickering......... hmmmm

On top of that CPU core temps are all low 20Cs and GPU is sitting around 39C


I'm using an Monster HDMI cable running from my ASUS VE 248 to the system... should I try a DVI..????????


Thoughts?


**UPDATE** Think I've found the fix and feel silly having posted when I probably should have looked to the drivers first. Just installed the Beta 13.2 drivers, working fine so far.

 

[tankbuster1221]

So, It's seems that the 13.2 beta drivers didn't remedy the problem. I thought everything was fine but, then I tried to run planetside 2.

Everything was fine until I entered the game at which point the screen started flickering, and it looked like there were black and white square beams coming from the sun. Textures, flickered.... everything flickered. I'm surprised I didn't seizure. Any thoughts..... I'm running a Radeon HD 7970 DD. I've never had this many problems with a build! Are the drivers that bad on the AMD side?

**more info** My core clock is around 925mhz and memory clock is around 1375mhz

 

[Jaydip]

Undo any overclocking and run at stock and see if the problem persists.

 

[tankbuster1221]

Well AMD overdrive is disabled within CCC. How else would I know if my card is overclocked? Sorry, I know I'm being noobish but, first build in a long long time.

 

[Jaydip]

Actually it seems you card is running at stock(missed your edit).It seems to be a issue with your 2D clocks.Can you check via GPU-Z what is your idle clocks?

 

[Rvenger]

Do you have the 7970 DD with the revised shorter PCB? I have been seeing a lot of complaints that the card artifacts at stock speeds.

 

[BrightCandle]

It sounds like you have a memory chip partially failing. Which normally you see when you push the memory past the maximum overclock. You get these lines of artifacts or blocks of them depending on the thing you are looking at. Sounds like the card is faulty.

 

[tankbuster1221]

According to GPU-Z

When the system is idleing

GPU Core Clock :300.0 MHz
GPU Memory Clock: 150.0 Mhz



So........ RMA?

 

[Jaydip]

That is the correct 2D clocks.So it happens when your system is less stressed right?it never occurs when you are playing games?

 

[tankbuster1221]

That is the correct 2D clocks.So it happens when your system is less stressed right?it never occurs when you are playing games?

See above in my description of Planetside 2. It happens....it happens alot! Everything I've thrown at it has some of the same graphical issues and they carry over onto the desktop after I exit from the app.

 

[tankbuster1221]

It sounds like you have a memory chip partially failing. Which normally you see when you push the memory past the maximum overclock. You get these lines of artifacts or blocks of them depending on the thing you are looking at. Sounds like the card is faulty.

RMA?

 

[Jaydip]

See above in my description of Planetside 2. It happens....it happens alot! Everything I've thrown at it has some of the same graphical issues and they carry over onto the desktop after I exit from the app.

Before you RMA make sure your system (proc,ram) is running at stock and the temps are normal.Download heaven/3d mark 11 and see if it continues.If it does well rma the card.

 

[tankbuster1221]

Alright so.... interesting, tried running 3dmark 11 and it went well up until the Combined test at which point it went on the fritz and completely froze on me.


Then windows crashed (something about Mem.dump)

Thoughts? Insights? RMA this bad boy?

 

[Jaydip]

Just the last one Go to control panel->administrative tools->event viewer->windows logs->system Now check for any critical events.See if you can find the faulting module name there.

 

[tankbuster1221]

No critical errors other than when I hard shutdown my machine after it froze.

 

[Jaydip]

Download whocrashed and report

 

[tankbuster1221]

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 3/15/2013 5:55:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031513-12277-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x40C90)
Bugcheck code: 0x24 (0xB50019060B, 0xFFFFF8800E53DD28, 0xFFFFF8800E53D560, 0xFFFFF803BC67EA35)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 3/15/2013 5:55:43 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x40C90)
Bugcheck code: 0x24 (0xB50019060B, 0xFFFFF8800E53DD28, 0xFFFFF8800E53D560, 0xFFFFF803BC67EA35)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

[tankbuster1221]

More ......


On Fri 3/15/2013 4:33:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031513-12682-01.dmp
This was probably caused by the following module: luafv.sys (luafv+0x1670C)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A0004176A0, 0xFFFFF8A000417880, 0x51E0104)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\luafv.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: LUA File Virtualization Filter Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 3/15/2013 8:17:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031513-12464-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0xAE72A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800659672A, 0xFFFFF8800E5454A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. SYSTEM_SERVICE_EXCEPTION



On Fri 3/15/2013 8:11:40 AM GMT your computer crashed
crash dump file C:\Windows\Minidump\031513-12136-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x4C4E5)
Bugcheck code: 0xF5 (0x68, 0xFFFFF8A00141ADB0, 0xFFFFF8A00141AE00, 0x0)
Error: FLTMGR_FILE_SYSTEM
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that an unrecoverable failure occurred in the Filter Manager.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.





Conclusion


5 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

 

[MeldarthX]

Hmmm.....which beta drivers are you using and did you come from 13.1s? just trying to eliminate everything......

If still doing it; then rma time..... sucks but sadly it happens;

 

[Jaydip]

You system is unstable while running any 3D apps and I would advise a rma.Sorry for boring you for all kinds of information but I wanted to ensure everything else is fine.

 

[Tweak155]

Might be dumb but it IS a beta... have you tried a non beta driver?