Sign in with
Sign up | Sign in
Your question

8800GTS 512MB help urgent help please!!!

Last response: in Graphics & Displays
Share
February 19, 2008 7:40:28 AM

Hi Guys,

I bought this Gigabyte Graphic card new version of 512MB 8800GTs.

I have started having issues just about 1 week now basically black screens suddenly and then computer gives beep sound from mobo while there was a black screen. I tried to put my other lcd same no screen so it is definetly noit the monitors. I have a corsair PSU 620W

How likely to have Corsair PSU's as lemon I have no idea???

I have these faults on event manager:

ID: 1000

Faulting application nvsvc32.exe, version 6.14.11.6928, faulting module nvcpl.dll, version 6.14.11.6928, fault address 0x000c0db8.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

ID: 108
The driver nv4_disp for the display device \Device\Video0 got stuck in an infinite loop. This usually indicates a problem with the device itself or with the device driver programming the hardware incorrectly. Please check with your hardware device vendor for any driver updates.

ID: 7034

The NVIDIA Display Driver Service service terminated unexpectedly. It has done this 1 time(s).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
--------------------------------------------------------------------

This is my debugger result:

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

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 8726c508, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 8a292f30, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 8757e9b0, Pointer to offending driver name.
Arg4: 00000001, Number of times this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.

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




FAULTING_THREAD: 8726c508

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: nvsvc32.exe

LAST_CONTROL_TRANSFER: from 00000000 to bf9f4902

STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 nv4_disp+0x1f902


STACK_COMMAND: .thread 0xffffffff8726c508 ; kb

FOLLOWUP_IP:
nv4_disp+1f902
bf9f4902 897c240c mov dword ptr [esp+0Ch],edi

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_disp+1f902

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 47689e86

FAILURE_BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2007_12_19

BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2007_12_19

Followup: MachineOwner


Do you guys think Graphic card problem or driver because what I tried just yesterday I put WHQL drivers same thing happened and then I tried beta release drivers this same thing happened...

Please some help here I have no idea with this system...


Thanks,

Gokhan

More about : 8800gts 512mb urgent

a b U Graphics card
February 19, 2008 7:59:18 AM

Have you completely erased your old drivers? Are you overclocking? If so, backoff on it. Clean out your old drivers first. Ive gotten this err while using ATItool going for highest clocks on overclock.
February 19, 2008 8:03:20 AM

Thanks for your reply Jaydee,

But I am not doing any overclocking at all since I have built this system.

So stock graphic card stock cpu everything stock at this stage.

So I will try to delete old drivers completely see whats going to happen...

But tell me this:

Could my new PSU which is corsair might cause all this trouble or could it be Graphic card habing problem???


Thanks,

Gokhan
Related resources
February 19, 2008 11:23:02 AM

Do you have a meter you can put onto the PS during the times where it crashes on you?
I would research acceptable variances for the power supplies, and how to test for it. Might take you an hour (or less if you post a seperate msg in THW), but then you will know or not if it is your ps.

Dont piss around with the PS...find out if it is or isn't, put it out of the mind if it isn't but dont be stubborn about it - still might be something flakky even after testing but I doubt it.

The people on here helped me a few times, I'm sure they will help you figure out the proper way to measure a PS during load and what readings you should expect.

BTW you can probably get a multimeter for under $30 at your local home depots/ lowes etc - or you could spend $20 at your local computer shop and have them test it. DONT take it to the freak squad and DO call a computer store and ask them if they have meters to test power supplies. Don't just ask if they test power supplies.

Some stores will even allow you to sign out (rent) a video card for testing purposes. Might be an option to look at.

Either way, you have issues and need to resolve them before you damage other components. But you will be the wiser for all of this and it will come in handy again. :) 

GL!
a c 147 U Graphics card
February 19, 2008 11:33:20 AM

Maybe try the other PCI-e power connector of the PSU. I am thinking you should have 2. worth a try. I still say check the drivers. Uninstall the current drivers. Download fresh ones from Nvidia and reload them.

Also, what OS are you running?
February 19, 2008 11:47:25 AM

Hardware Monitor 1.0.7.1
-----------------------------------------------------
Mainboard Vendor ASUSTeK Computer INC.
Mainboard Model P5E (0xCA - 0x53C)

LPCIO
-----------------------------------------------------
Vendor Winbond
Model W83627DHG
Vendor ID 0x5CA3
Chip ID 0xA0
Revision ID 0x23
Config Mode I/O address 0x2E

Dump config mode register space, LDN = 0xB
0 1 2 3 4 5 6 7 8 9 A B C D E F
00 FF FF FF FF FF FF FF 0B FF FF FF FF FF FF FF FF
10 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
20 A0 23 FF 00 44 00 00 FF 50 0A 00 00 1A 21 00 FF
30 01 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
40 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
50 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
60 02 90 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
70 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF


Hardware monitor
-----------------------------------------------------

Winbond W83627DHG hardware monitor

Voltage sensor 0 1.19 Volts [0x95] (CPU VCORE)
Voltage sensor 1 11.99 Volts [0xD7] (+12V)
Voltage sensor 2 3.25 Volts [0xCB] (AVCC)
Voltage sensor 3 3.25 Volts [0xCB] (+3.3V)
Voltage sensor 4 1.74 Volts [0xDA] (VIN1)
Voltage sensor 5 4.90 Volts [0xCC] (+5V)
Voltage sensor 6 1.71 Volts [0xD6] (VIN3)
Temperature sensor 0 41°C (105°F) [0x29] (SYSTIN)
Temperature sensor 1 26°C (78°F) [0x34] (CPUTIN)
Fan sensor 1 1854 RPM [0xB6] (CPUFANIN0)
Fan sensor 4 981 RPM [0x2B] (AUXFANIN1)

Dump hardware monitor
LPC Register space, base address = 0x0290

bank 0
0 1 2 3 4 5 6 7 8 9 A B C D E F
00 04 FF 04 FF 01 00 37 30 01 37 01 01 3C 3C 14 14
10 04 FF 10 00 00 01 01 3C 43 17 00 00 FF FF FF C0
20 95 D7 CB CB DA CC D6 29 FF B5 FF DA 00 91 82 B0
30 ED 82 ED 4B 9E A0 17 1C 1D 2F 24 6D 24 46 3D FF
40 03 CE 0F FF FF FF 07 95 2D 02 00 44 10 95 00 A3
50 FF FF 00 FF FF FF 00 80 C1 E4 FF FF 19 A4 04 05
60 04 FF 40 00 01 01 3C FF 14 FF 01 FF FF FF FF FF
70 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
80 04 FF 04 FF 01 00 37 30 01 37 01 01 3C 3C 14 14
90 04 FF 10 00 00 01 01 3C 43 17 00 00 FF FF FF C0
A0 95 D7 CB CB DA CC D6 29 FF B5 FF DA 00 91 82 B0
B0 ED 82 ED 4B 9E A0 17 1C 1D 2F 24 6D 24 46 3D FF
C0 03 00 00 FF FF FF 07 95 2D 02 00 44 10 95 00 A3
D0 FF FF 00 FF FF FF 00 80 C1 E4 FF FF 19 A4 04 05
E0 04 FF 40 00 01 01 3C FF 14 FF 01 FF FF FF FF FF
F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

bank 1
50 1B 00 00 4B 00 50 01 FE FF FF FF FF FF FF FF FF
bank 2
50 F3 00 00 4B 00 50 1A 0C FF FF FF FF FF FF FF FF
bank 3
50 05 01 04 03 07 05 02 05 04 00 00 30 2D 02 00 00
bank 4
50 3B 13 FF 00 00 00 00 09 6B CE 0D 3B 09 5D 20 7F
bank 5
50 CB B6 0B 2A 22 13 06 52 46 C0 00 00 EC 00 00 00


Hardware monitor
-----------------------------------------------------

Winbond W83791D hardware monitor

Voltage sensor 0 1.07 Volts [0x43] (CPU VCore)
Voltage sensor 1 1.52 Volts [0x5F] (AUX)
Voltage sensor 2 1.17 Volts [0x49] (+3.3V)
Voltage sensor 3 4.97 Volts [0xB9] (+5V)
Voltage sensor 4 3.77 Volts [0x3E] (+12V)
Voltage sensor 5 -6.77 Volts [0x63] (-12V)
Voltage sensor 6 -3.49 Volts [0x54] (-5V)
Temperature sensor 0 32°C (89°F) [0x20] (TMPIN0)
Temperature sensor 1 32°C (89°F) [0x40] (TMPIN1)
Temperature sensor 2 25°C (76°F) [0x32] (TMPIN2)

Dump hardware monitor
SMBus Register space, base address = 0x0400
SMBus request at channel 0x0, address 0x2C

0 1 2 3 4 5 6 7 8 9 A B C D E F
00 00 00 00 00 00 00 00 00 00 80 00 01 00 00 00 FF
10 00 00 7F 00 F8 10 0B 00 00 00 00 00 00 00 00 00
20 43 5F 49 B9 3E 63 54 20 FF FF FF BF 00 BF 00 ED
30 B0 00 00 40 00 00 00 08 00 00 00 40 00 00 FF FF
40 01 FF 6E 00 00 00 00 5F 2C 11 01 44 01 15 00 A3
50 FF FF FF FF FF FF 00 80 71 70 FF 00 00 00 05 FF
60 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
70 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
80 01 FF 01 FF 00 00 00 00 01 01 01 01 3C 3C 0A 0A
90 00 00 00 01 FF 00 00 00 01 01 3C 08 00 00 01 01
A0 FF FF FF 00 00 00 00 00 17 DC 4E 08 00 FF FF FF
B0 BA 00 7C FF 00 00 00 00 00 00 FF FF 00 00 FF FF
C0 20 80 00 4B 00 50 00 FF 19 80 00 4B 00 50 00 FF
D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
F0 FF FF 00 FF 00 01 00 FF FF 02 FF 00 00 36 00 2E



Hardware monitor
-----------------------------------------------------

Intel Core 2 Duo E8400 hardware monitor

Temperature sensor 0 40°C (103°F) [0x41] (core #0)
Temperature sensor 1 40°C (103°F) [0x41] (core #1)

Dump hardware monitor



Hardware monitor
-----------------------------------------------------

GeForce 8800 GTS 512 hardware monitor

Temperature sensor 0 60°C (139°F) [0x3C] (GPU Core)

Dump hardware monitor



Hardware monitor
-----------------------------------------------------

ST3320620AS hardware monitor

Temperature sensor 0 38°C (100°F) [0x26] (HDD)

Dump hardware monitor



Hardware monitor
-----------------------------------------------------

ST3320620AS hardware monitor

Temperature sensor 0 41°C (105°F) [0x29] (HDD)

Dump hardware monitor


Processors Map
------------------------------------------------------------------------------------

Number of processors 1
Number of threads 2

Processor 0
-- Core 0
-- Thread 0
-- Core 1
-- Thread 0


Processors Information
------------------------------------------------------------------------------------

Processor 1 (ID = 0)
Number of cores 2 (max 2)
Number of threads 2 (max 2)
Name Intel Core 2 Duo E8400
Codename Wolfdale
Specification Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Package Socket 775 LGA (platform ID = 0h)
CPUID 6.7.6
Extended CPUID 6.17
Core Stepping C0
Technology 45 nm
Core Speed 3005.7 MHz (9.0 x 334.0 MHz)
Rated Bus speed 1335.9 MHz
Stock frequency 3000 MHz
Instructions sets MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, EM64T
L1 Data cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
L1 Instruction cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
L2 cache 6144 KBytes, 24-way set associative, 64-byte line size
FID/VID Control yes
FID range 6.0x - 9.0x
max VID 1.225 V
Features XD, VT


Thread dumps
------------------------------------------------------------------------------------

CPU Thread 0
APIC ID 0
Topology Processor ID 0, Core ID 0, Thread ID 0
Type 01008001h
Max CPUID level 0000000Ah
Max CPUID ext. level 80000008h

Function eax ebx ecx edx
0x00000000 0x0000000A 0x756E6547 0x6C65746E 0x49656E69
0x00000001 0x00010676 0x00020800 0x0008E3FD 0xBFEBFBFF
0x00000002 0x05B0B101 0x005657F0 0x00000000 0x2CB4304E
0x00000003 0x00000000 0x00000000 0x00000000 0x00000000
0x00000004 0x04000121 0x01C0003F 0x0000003F 0x00000001
0x00000004 0x04000122 0x01C0003F 0x0000003F 0x00000001
0x00000004 0x04004143 0x05C0003F 0x00000FFF 0x00000001
0x00000005 0x00000040 0x00000040 0x00000003 0x00022220
0x00000006 0x00000001 0x00000002 0x00000001 0x00000000
0x00000007 0x00000000 0x00000000 0x00000000 0x00000000
0x00000008 0x00000400 0x00000000 0x00000000 0x00000000
0x00000009 0x00000000 0x00000000 0x00000000 0x00000000
0x0000000A 0x07280202 0x00000000 0x00000000 0x00000503
0x80000000 0x80000008 0x00000000 0x00000000 0x00000000
0x80000001 0x00000000 0x00000000 0x00000001 0x20100000
0x80000002 0x65746E49 0x2952286C 0x726F4320 0x4D542865
0x80000003 0x44203229 0x43206F75 0x20205550 0x45202020
0x80000004 0x30303438 0x20402020 0x30302E33 0x007A4847
0x80000005 0x00000000 0x00000000 0x00000000 0x00000000
0x80000006 0x00000000 0x00000000 0x18008040 0x00000000
0x80000007 0x00000000 0x00000000 0x00000000 0x00000000
0x80000008 0x00003024 0x00000000 0x00000000 0x00000000

Cache descriptor Level 1 D 32 KB 1 threads
Cache descriptor Level 1 I 32 KB 1 threads
Cache descriptor Level 2 U 6 MB 2 threads

MSR 0x0000001B edx = 0x00000000 eax = 0xFEE00900
MSR 0x000000E8 edx = 0x000000CB eax = 0x3CAC22F5
MSR 0x00000017 edx = 0x04000000 eax = 0x88848920
MSR 0x000000CD edx = 0x00000000 eax = 0x00000804
MSR 0x0000003F edx = 0x00000000 eax = 0x00000000
MSR 0x000000CE edx = 0x001A0920 eax = 0x19190718
MSR 0x000001A0 edx = 0x00000040 eax = 0x60972489
MSR 0x000000EE edx = 0x00000000 eax = 0x867D1300
MSR 0x0000011E edx = 0x00000000 eax = 0xBE702111
MSR 0x0000019C edx = 0x00000000 eax = 0x88410000
MSR 0x00000198 edx = 0x061A0920 eax = 0x06000920
MSR 0x00000199 edx = 0x00000000 eax = 0x00000920

CPU Thread 1
APIC ID 1
Topology Processor ID 0, Core ID 1, Thread ID 0
Type 01008001h
Max CPUID level 0000000Ah
Max CPUID ext. level 80000008h

Function eax ebx ecx edx
0x00000000 0x0000000A 0x756E6547 0x6C65746E 0x49656E69
0x00000001 0x00010676 0x01020800 0x0008E3FD 0xBFEBFBFF
0x00000002 0x05B0B101 0x005657F0 0x00000000 0x2CB4304E
0x00000003 0x00000000 0x00000000 0x00000000 0x00000000
0x00000004 0x04000121 0x01C0003F 0x0000003F 0x00000001
0x00000004 0x04000122 0x01C0003F 0x0000003F 0x00000001
0x00000004 0x04004143 0x05C0003F 0x00000FFF 0x00000001
0x00000005 0x00000040 0x00000040 0x00000003 0x00022220
0x00000006 0x00000001 0x00000002 0x00000001 0x00000000
0x00000007 0x00000000 0x00000000 0x00000000 0x00000000
0x00000008 0x00000400 0x00000000 0x00000000 0x00000000
0x00000009 0x00000000 0x00000000 0x00000000 0x00000000
0x0000000A 0x07280202 0x00000000 0x00000000 0x00000503
0x80000000 0x80000008 0x00000000 0x00000000 0x00000000
0x80000001 0x00000000 0x00000000 0x00000001 0x20100000
0x80000002 0x65746E49 0x2952286C 0x726F4320 0x4D542865
0x80000003 0x44203229 0x43206F75 0x20205550 0x45202020
0x80000004 0x30303438 0x20402020 0x30302E33 0x007A4847
0x80000005 0x00000000 0x00000000 0x00000000 0x00000000
0x80000006 0x00000000 0x00000000 0x18008040 0x00000000
0x80000007 0x00000000 0x00000000 0x00000000 0x00000000
0x80000008 0x00003024 0x00000000 0x00000000 0x00000000

Cache descriptor Level 1 D 32 KB 1 threads
Cache descriptor Level 1 I 32 KB 1 threads
Cache descriptor Level 2 U 6 MB 2 threads

MSR 0x0000001B edx = 0x00000000 eax = 0xFEE00800
MSR 0x000000E8 edx = 0x00000090 eax = 0xD3F9E657
MSR 0x00000017 edx = 0x04000000 eax = 0x88848920
MSR 0x000000CD edx = 0x00000000 eax = 0x00000804
MSR 0x0000003F edx = 0x00000000 eax = 0x00000000
MSR 0x000000CE edx = 0x001A0920 eax = 0x19190718
MSR 0x000001A0 edx = 0x00000040 eax = 0x60972489
MSR 0x000000EE edx = 0x00000000 eax = 0x867D1300
MSR 0x0000011E edx = 0x00000000 eax = 0xBE702111
MSR 0x0000019C edx = 0x00000000 eax = 0x88410000
MSR 0x00000198 edx = 0x061A0920 eax = 0x06000920
MSR 0x00000199 edx = 0x00000000 eax = 0x00000920



Drive
-----------------------------------------------------
Name ST3320620AS

Drive
-----------------------------------------------------
Name ST3320620AS





---------------
C2D 8400 3.0ghz -Not Overclocked
4GB A-DATA RAMS 5-5-5-15
Asus P5E
CORSAIR 620WH PSU


PS: UNISTALLED THE DRIVERS REMOVED ALL DRIVERS WITH DRIVER CLEANER PRO SAME THING HAPPENED IN MIDDLE OF NBA 2006 EVEN HAPPENED WITH COMMAND AND CONQUER AS WELL SOMETIMES HAPPENS EVEN WATCHING DIVX MOVIES.

!