• Happy holidays, folks! Thanks to each and every one of you for being part of the Tom's Hardware community!

GPU always crashing

Ricky Segarra

Honorable
Sep 9, 2013
7
0
10,510
The gpu is a nvidia gtx 660Ti
Operating System
Windows 7 Home Premium 64-bit SP1
CPU
Intel Core i5 3550 @ 3.30GHz 44 °C
Ivy Bridge 22nm Technology
RAM
8.00GB Dual-Channel DDR3 @ 665MHz (9-9-9-24)
Motherboard
Gigabyte Technology Co., Ltd. H77M-D3H (Intel Core i5-3550 CPU @ 3.30GHz) 28 °C
Graphics
IPS235 (800x600@1Hz)
Intel Standard VGA Graphics Adapter (Gigabyte)
Hard Drives
112GB SanDisk SDSSDX120GG25 (SSD) 37 °C
699GB Hitachi HDS721075KLA330 (SATA) 50 °C
Audio
Logitech G35 Headset
PSU Tx650m
this is without the gpu in because I have to take it out to use the computer now.
I ran oc scanner and precision X and just did the benchmark and it crashed (a lot of greenish checker pattern and artifacts) but it only got to 74C
I ran a cpu ram and psu tests and they all passed so i dont know what is causing the problem
 
Are you benchmarking the card overclocked--- just asking to rule out the obvious. A GPU doesn't have to heat up for the overclock to be unstable.


With that ruled out, have you tried bumping the voltage a little bit, and keeping the clocks at stock? I know it's not ideal, but it would show some indication of instability or perhaps faulty VRMs.

How old is this card? And what brand is it?
 

i haven't overclocked anything on this pc and how do i bump the voltage up? The card came from EVGA and I had to RMA a previous one last week because it had a similar problem but then it stopped working and the pc would restart on boot unless it was in safe mode and even then anything dark would be reddish with red lines all over the screen. I rma'ed that card and the replacement they sent me is the current one which has the problems i described in the first post pretty much the same day I got it.
 



And I assume all of these problems disappear 100% once you remove the card and use Intel graphics? If so, it does sound like a faulty card. I've had that happen to me with MSI. Had to RMA a 6950. They sent me a faulty one in exchange that similar problems (colored squares on the screen, blacking out, etc). I made them send me an advance replacement after that. That one actually worked.

Since you're using an older card, all you're going to get as a replacement is a refurb. Refurbs are fine, as long as they're tested appropriately before they ship it. The low-level "techs" generally test these refurbs and seem to use the following criteria:
1. When the monitor is connected, can you see things on the screen?
2. If yes, TEST PASSED!

After MSI sent me that first faulty replacement, I contacted their tech support staff and made sure the next card was going to be personally tested by a higher-tier tech. Whether it did or didn't, the next card I got in the mail was fully functional and overclocked well. Hopefully, the problem just lies with poor standards in those refurb replacements. Try to get a high-level tech to talk to you and agree to test your next replacement.

 
I have two updates, I received two bsods playing amnesia today and here are the two dump reports first is
http://gyazo.com/4760f2afece87f188cca74b02c607111
On Tue 9/10/2013 10:28:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091013-29468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFFA800A87FB50, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

the second is
http://gyazo.com/99dd12eb537d340dae2db506f9a87e2a
On Tue 9/10/2013 8:14:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091013-29686-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC639D)
Bugcheck code: 0x19 (0x3, 0xFFFFF900C0139260, 0xFF000000FF000000, 0xFFFFF900C0139260)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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.

 

yea it was while streaming the new amnesia game. And i installed it after i built everything in it now except at the time i had a gtx 570 then i upgraded to the 660 ti and now im using the integrated
 


ok i did that, when i booted with the gpu in, i got a lot of green lines on the screen almost like a bar code covering the screen, then in installed the nvidia driver and it would not start windows on reboot
 
Ok, it's probably time to RMA the card. There shouldn't be any kind of distortion when running without drivers -- just low res. The one thing that could confirm it's a bad video card is for you to try it in a different system -- a friend of yours, local computer shop, etc.
 

I'm not going to be able to test it in another computer for a while since im getting ready to move into a dorm room and i dont have time to go to a computer shop. I guess ill try to rma it for the third time.