My computer's suddenly slowed down a lot lately. It BSODs if I have more than 8 or so Google Chrome tabs open - that's how bad it's become (previously I never reached a limit that made it crash; even with 30 tabs open). Also, my games have all showed weird signs of this slow down. World of Tanks and League of Legends take an eternity to load a level. Borderlands runs fine for a few minutes, then starts to lag out horribly down to what seems like 5 FPS or less. Battlefield Bad Company crashes to desktop about 15 seconds after joining a server and runs really slow during those 15 seconds. And, most importantly, New Vegas runs perfectly fine at my regular settings - but as soon as I shoot at someone, the game becomes a slideshow. After lagging for a few minutes, it simply crashes to desktop.

Before this, I could run all the games mentioned maxed out and achieve 30 FPS or more and had quick load times. I didn't change drivers or make any drastic changes to the software or hardware of my computer. I've scanned for viruses with Malwarebytes, SuperAntiSpyware, AVG, Avast and tdsskiller. Nothing major was found, except for one rootkit with tdsskiller, which I removed.

My temps all seem normal and all my fans are running at their regular speed. I've run Seatools (all the scans it has) and all of them passed. I ran Intel's processor diagnostic and it said my processor was fine.

I've updated my GFX driver to the latest version and rolled it back to a few different 18x.xx drivers just in case, but that didn't improve anything.

I've defragged the crap out of my hard drive (several times over until it only got to the point that each defrag took less than 2 minutes and no more progress was visible) and run CCleaner and Eusing Free Registry Cleaner.

My specs are:
GeForce 9800GT
Intel Core2Duo E7300 2.66GHz
4 GB generic RAM
Seagate 500 GB (Barracuda 7200.12 SATA 3Gb/s)
I have 70 GB of space on the drive (which actually has 466 GB, not 500 GB)
Windows XP SP3
Nothing overclocked

Would anyone happen to know what's wrong? Some have said that I should replace the RAM and see what happens or replace the HDD and see what happens (or reformat it). The problem is I'm in a tight spot for money currently, so I'd rather only replace what absolutely must be replaced. I also have a job which involves using my computer a lot, so I'd rather not have to reformat it and go through the hassle of backing things up unless it's absolutely necessary.

I'm thinking that there might be a way to diagnose this by the symptoms. New Vegas runs fine normally and it's not exactly a pretty game (low res textures, lower poly count models, etc), but slows down once I shoot at something. So, possibly it slows down when AI combat calculations have to kick in. I'd assume that's something wrong with the processor, but Intel tells me it's running fine. Also, a dying processor shouldn't affect the load times of WoT or LoL should it? I dunno, I'm not particularly good at diagnosing computer problems. If anyone has any idea how to make my computer run New Vegas like it used to or knows what might be wrong, please let me know; I'd really, really appreciate it.

Thanks

Post a minidump (c:\windows\minidump).

Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0xe0ba3000 PsLoadedModuleList = 0xe0c29720
Debug session time: Thu Sep 22 17:06:54.921 2011 (UTC + 10:00)
System Uptime: 0 days 2:43:25.644
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck anolysis *
* *
*******************************************************************************

Use !anolyze -v to get detailed debugging information.

BugCheck 1000008E, {e0000001, f6198925, be4ea2f8, 0}

*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
Probably caused by : nv4_disp.dll ( nv4_disp+1db0ec )

Followup: MachineOwner
---------

1: kd> !anolyze -v
*******************************************************************************
* *
* Bugcheck anolysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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
happening.
Arguments:
Arg1: e0000001, The exception code that was not handled
Arg2: f6198925, The address that the exception occurred at
Arg3: be4ea2f8, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xe0000001 -

FAULTING_IP:
watchdog!RaiseExceptionInThread+b
f6198925 c3 ret

TRAP_FRAME: be4ea2f8 -- (.trap 0xffffffffbe4ea2f8)
ESP EDITED! New esp=be4ea6a8
ErrCode = 00000000
eax=e233c800 ebx=00000001 ecx=000001f0 edx=00000001 esi=e29a6e50 edi=0000ffff
eip=f6198925 esp=be4ea36c ebp=be4ea6c0 iopl=0 nv up ei pl nz na pe nc
cs=0000 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000206
watchdog!RaiseExceptionInThread+0xb:
f6198925 c3 ret
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: chrome.exe

LAST_CONTROL_TRANSFER: from f6198622 to f6198925

STACK_TEXT:
be4ea368 e0c130e6 be4ea37c be4ea3cc 00000001 watchdog!RaiseExceptionInThread+0xb
be4ea6c0 debb00ec e29a4c00 e29a5f40 deb556d0 nt!ExRaiseStatus+0xca
WARNING: Stack unwind information not available. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 nv4_disp+0x1db0ec


STACK_COMMAND: .trap 0xffffffffbe4ea2f8 ; kb

FOLLOWUP_IP:
nv4_disp+1db0ec
debb00ec ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nv4_disp+1db0ec

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 4e390d56

FAILURE_BUCKET_ID: 0x8E_nv4_disp+1db0ec

BUCKET_ID: 0x8E_nv4_disp+1db0ec

Followup: MachineOwner
---------

1: kd> !anolyze -v
*******************************************************************************
* *
* Bugcheck anolysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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
happening.
Arguments:
Arg1: e0000001, The exception code that was not handled
Arg2: f6198925, The address that the exception occurred at
Arg3: be4ea2f8, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xe0000001 -

FAULTING_IP:
watchdog!RaiseExceptionInThread+b
f6198925 c3 ret

TRAP_FRAME: be4ea2f8 -- (.trap 0xffffffffbe4ea2f8)
ESP EDITED! New esp=be4ea6a8
ErrCode = 00000000
eax=e233c800 ebx=00000001 ecx=000001f0 edx=00000001 esi=e29a6e50 edi=0000ffff
eip=f6198925 esp=be4ea36c ebp=be4ea6c0 iopl=0 nv up ei pl nz na pe nc
cs=0000 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000206
watchdog!RaiseExceptionInThread+0xb:
f6198925 c3 ret
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: chrome.exe

LAST_CONTROL_TRANSFER: from f6198622 to f6198925

STACK_TEXT:
be4ea368 e0c130e6 be4ea37c be4ea3cc 00000001 watchdog!RaiseExceptionInThread+0xb
be4ea6c0 debb00ec e29a4c00 e29a5f40 deb556d0 nt!ExRaiseStatus+0xca
WARNING: Stack unwind information not available. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 nv4_disp+0x1db0ec


STACK_COMMAND: .trap 0xffffffffbe4ea2f8 ; kb

FOLLOWUP_IP:
nv4_disp+1db0ec
debb00ec ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nv4_disp+1db0ec

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 4e390d56

FAILURE_BUCKET_ID: 0x8E_nv4_disp+1db0ec

BUCKET_ID: 0x8E_nv4_disp+1db0ec

Followup: MachineOwner
---------

1: kd> !anolyze -v
*******************************************************************************
* *
* Bugcheck anolysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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
happening.
Arguments:
Arg1: e0000001, The exception code that was not handled
Arg2: f6198925, The address that the exception occurred at
Arg3: be4ea2f8, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xe0000001 -

FAULTING_IP:
watchdog!RaiseExceptionInThread+b
f6198925 c3 ret

TRAP_FRAME: be4ea2f8 -- (.trap 0xffffffffbe4ea2f8)
ESP EDITED! New esp=be4ea6a8
ErrCode = 00000000
eax=e233c800 ebx=00000001 ecx=000001f0 edx=00000001 esi=e29a6e50 edi=0000ffff
eip=f6198925 esp=be4ea36c ebp=be4ea6c0 iopl=0 nv up ei pl nz na pe nc
cs=0000 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000206
watchdog!RaiseExceptionInThread+0xb:
f6198925 c3 ret
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: chrome.exe

LAST_CONTROL_TRANSFER: from f6198622 to f6198925

STACK_TEXT:
be4ea368 e0c130e6 be4ea37c be4ea3cc 00000001 watchdog!RaiseExceptionInThread+0xb
be4ea6c0 debb00ec e29a4c00 e29a5f40 deb556d0 nt!ExRaiseStatus+0xca
WARNING: Stack unwind information not available. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 nv4_disp+0x1db0ec


STACK_COMMAND: .trap 0xffffffffbe4ea2f8 ; kb

FOLLOWUP_IP:
nv4_disp+1db0ec
debb00ec ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nv4_disp+1db0ec

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 4e390d56

FAILURE_BUCKET_ID: 0x8E_nv4_disp+1db0ec

BUCKET_ID: 0x8E_nv4_disp+1db0ec

Followup: MachineOwner
---------

Hope this helps - I've got little idea what it means, except that there's something in there about nv4, which is Nvidia's program for graphics cards IIRC.

Edit: This happened when I tried to make a Youtube video go fullscreen one time. Sometimes they'll go fullscreen with no problem at all (even at 1080p), but this time it crashed, with no other programs open. I don't have any minidumps for game crashes, because they haven't BSOD'ed before - only CTD.

nv4_disp.dll is a NVIDIA file. Try a few older/newer graphic and chipset drivers. It is also possible your GPU has an error.

As I said in my post, I tried updating my driver to the latest, then I tried uninstalling it and applied various 18x.xx drivers (they've always been good to me). And since I hadn't changed drivers at all over the course of the month that my computer starting screwing up, I can't imagine that it's a drivers issue.

I'm leaning towards it being an issue with my graphics card - just after my last post I brought up a news site with lots of flash ads everywhere, which caused my computer to lock up and eventually black screen and restart itself. When it started back up the computer had set itself to have some ridiculously low color setting (if I were to guess, I'd say there were 8 colors displayed on screen, but it might have been 16) and given itself what looked like 480x360 or even 320x240. I have to assume that this is my graphics card dying - I've only ever seen something like this when I run my computer without a graphics card (and even then, it's a bit better).

So, is it definitely possible for graphics card hardware issue to cause nv4_disp.dll to have issues? If so, I'm now pretty convinced that it's my graphics card and I'll go and buy a new one. Hopefully that's what's wrong.

Thanks very much for the help, I really appreciate it