View Full Version : Continuous BSOD

09-24-07, 06:57 PM
Everytime when I have a stable GPU clock, my com-puta BSOD's and I get this error

Error Message: STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER (Q293078)

I've tried default clocks with OC'd GPU and I get the same thing, just not as often. Does anyone know what the error means? The problem occurs when I'm playing a game; the game will freeze, and loop whatever sound it froze on, and it's annoying. I'd punch my PC but it has a side panel and I don't want to break it.

09-25-07, 12:04 AM
1. how do you know the GPU overclock is actually stable?

2. what drivers are you running

3. this isnt in the right section :p

09-25-07, 05:37 PM
1. nTune says it passes.

2.I'm using 163.44

3. It's a BSOD from something and I'm convinced it's from my GPU, so it can go here ;)

09-25-07, 08:37 PM
Try to debug the BSOD, to be sure that is the GPU, here you have a quick guide:


09-25-07, 09:09 PM
1. nTune says it passes.

2.I'm using 163.44

3. It's a BSOD from something and I'm convinced it's from my GPU, so it can go here ;)
heh i wouldnt trust ntune completely. the ultimate test for any overclock is a good old burn in.

did you try running a different driver set with the overclock? try a different driver version and try the overclock (run a game to test the overclock). if that works, you can use that driver. if it doesnt, turn off the overclock and try it again. if that doesnt work, go back to your current drivers and try it without the overclock.

09-25-07, 09:25 PM
I have no damn clue how to work this thing.

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

Loading Dump File [C:\WINDOWS\Minidump\Mini092407-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\websymbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Sep 24 22:27:33.734 2007 (GMT-7)
System Uptime: 0 days 0:15:22.444
Loading Kernel Symbols
.................................................. .................................................. ..........................
Loading User Symbols
Loading unloaded module list
Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, bfb13720, b9e82c38, b9e82934}

Probably caused by : nv4_disp.dll ( nv4_disp+13e720 )

Followup: MachineOwner

09-25-07, 10:41 PM
If you overlock your video card and then your computer crashes you've overclocked too far.

Do you have the problems at stock vid card speed?

If not then overclocking is the problem, it's not hard to understand.

09-25-07, 10:49 PM
Starscream, if I go 5MHz past the stock core clock, it crashes.....I have no problem reaching 880MHz from 725MHz on the memory clock.

09-26-07, 12:37 AM
I went as far back as the 101.02 driver and I get the same problem. I'm back at the 163.44 driver..

09-26-07, 05:12 PM
Well at this point all I can suggest is put the card in another pc and see if it overclocks any better. If it doesn't and I suspect it won't then you're done, your card simply sucks for overclocking.

09-26-07, 07:42 PM
Too bad my computer is the only one with PCI-E sockets. It's rediculous how the Foxconn product website says that the card has a 550MHz core and 725MHz (or 1450) memory. My computer says it's got 540MHz/700MHz. My other Foxconn card I had (same model, RMA'd) did the same thing, same clocks, too. The card comes with an overclock utility also! The memory is a great overclocker but the core just sucks bolas.

09-26-07, 10:59 PM
1: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
Arg1: c0000005, The exception code that was not handled
Arg2: bfb13720, The address that the exception occurred at
Arg3: b9e82c38, Exception Record Address
Arg4: b9e82934, Context Record Address

Debugging Details:

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

bfb13720 8b4154 mov eax,dword ptr [ecx+54h]

EXCEPTION_RECORD: b9e82c38 -- (.exr 0xffffffffb9e82c38)
ExceptionAddress: bfb13720 (nv4_disp+0x0013e720)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000054
Attempt to read from address 00000054

CONTEXT: b9e82934 -- (.cxr 0xffffffffb9e82934)
eax=00000000 ebx=e4ca3a20 ecx=00000000 edx=00000000 esi=e4ca3a80 edi=e1dcbb70
eip=bfb13720 esp=b9e82d00 ebp=e4c9fa00 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
bfb13720 8b4154 mov eax,dword ptr [ecx+54h] ds:0023:00000054=????????
Resetting default scope



ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

READ_ADDRESS: 00000054



LAST_CONTROL_TRANSFER: from 805ce84c to bfb13720

WARNING: Stack unwind information not available. Following frames may be wrong.
b9e82dac 805ce84c 89b98020 00000000 00000000 nv4_disp+0x13e720
b9e82ddc 8054532e b871df30 e1e01e10 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

bfb13720 8b4154 mov eax,dword ptr [ecx+54h]


SYMBOL_NAME: nv4_disp+13e720


MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll


STACK_COMMAND: .cxr 0xffffffffb9e82934 ; kb

FAILURE_BUCKET_ID: 0x7E_nv4_disp+13e720

BUCKET_ID: 0x7E_nv4_disp+13e720

Followup: MachineOwner