Recently, whenever I play fullscreen 3d games (World of Warcraft and Serious Sam are my test cases), I'll crash with a nasty BSOD:
STOP: 0x0000007A KERNEL_DATA_INPAGE_ERROR
...this happens with a subcode of 0xC000000E, which seems to be "device not available".
Now, according to many posts on the net, this is probably due to a slowly-failing hard drive--and indeed when this occurs, it usually involves a "click" which seems to be coming from the case (can't verify this).
...I ran a diagnostic on the hard drive, with no real problems.
...the computer is fully usable and can stay on for hours if I don't play games.
...I tried moving the swapfile to a different partition, with no change.
...if the game DOES start, it'll be fine for the duration. But a successful start seems to be about 1 out of 10.
...yet once a game starts doing fullscreen 3d (again, only WoW and SS2E are my test cases), it's an INSTANT crash (the login screen for WoW barely has time to show before it crashes). For a bit I was trying to imagine it being a power surge problem, but not sure (incidentally, BIOS reports my 5v line as being just over 4.5V; is that bad or only sorta-bad?).
Now obviously this is bad. But I'd also like to zero in on the solution before trying a new hard drive, new vid card etc.
Could this be the vid card? If so, how could I test? If it is the culprit, is there anything to do but replace it?
MB: Asus A7N8X deluxe
CPU: Barton 2500 (not overclocked ATM)
Mem: 512M of Corsair XMS (something up to 400MHz)
HD: Maxtor DiamondMax 9 60G SATA
Vid: Ati 9800 Pro (Sapphire)
PS: Antec TruePower 450
Just do a Sandra Burn-In wizard. It is very good and while it stresses your system enough to detect problems, if any, it is unlikely to kill your system. Before running any burn-in software though, make sure that you set system shut down temps in the BIOS if your BIOS has this feature -- you want your PC to shut down if something reaches critical temps, not go up in smoke.
Good luck :smile:
<font color=green>"The creative powers of English morphology are pathetic compared to what we find in other languages." (Steven Pinker, The Language Instinct)</font color=green> :cool:
Since its 3D application related Id say you are looking at a bad video card or faulty power supply (most likely the former). If I am not mistaken, im pretty sure AGP voltage is 3.3v and your card uses a +12V line from the Power supply directly. Make sure that 12V line is dedicated to the Vid card (no other devices on it).
If I were you, I would take a trip to best buy or even wal mart and buy the cheapest AGP card they sell (preferrably ATI so you dont end up messing with other drivers). Then take it home and test it in your system. If it works then you have discovered your R9800pro is the problem. If not, youve eliminated one variable. When youre done, just return the card (best buy has a 30 day return policy with the reciept. I used to work there a few years back, they wont ask questions. Wal mart is even more relaxed about it.)
Give that a shot, and if you still have the problems with the new card let us know.
"Who is General Failure, and why is he reading my drive?"
P4 3.0C HT, Intel D865GBF, 1GB Crucial PC3200 DDR, 2x WD 36GB Raptor 10kRPM, BBA Radeon 9800PRO, SB Audigy, Hauppage WinTV
The plug to the vid card is its own cable (no other devices on it).
I haven't had time to run some of the other benches, but I did try starting up the same games in windowed mode. When I did, they worked fine, but my 5V rail dropped as low as 4.38V, according to MBM.
Now to me, a 12.4% variation on something which I think is nominally supposed to be within 5% of rated voltage sounds bad. I'm going to poke at it some more and see what happens before trying a new card (rendering in the windowed mode of games was fine and fast, AND to make things better if I start the game in windowed mode and then change to fullscreen I still get low 5v rail readings but the game plays).
So I still like my idea that it's the combination hit of a resolution change and shoot to 3d mode that is causing the line to pull low, forcing a reboot. But I'm not positive yet...