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:
Faulting application nvsvc32.exe, version 18.104.22.16828, faulting module nvcpl.dll, version 22.214.171.12428, fault address 0x000c0db8.
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.
The NVIDIA Display Driver Service service terminated unexpectedly. It has done this 1 time(s).
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.
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.
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.
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.
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.
Processor 1 (ID = 0)
Number of cores 2 (max 2)
Number of threads 2 (max 2)
Name Intel Core 2 Duo E8400
Specification Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Package Socket 775 LGA (platform ID = 0h)
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
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.