Printable View
Right, so as stated before in what i previously thought was my 8800gtx overheating, dx10 games crash.
I downloaded everest trial, and have created some logs and im trying to work out what causes my system to hang.
Can I just have some people glance over them to see if anything jumps out?
This one crysis lasted for about 5 mins, then crashed
This one, about 30 seconds
Can upload the stats with all the min+max stats if you want too.
Any ideas? I'm stumped!
it doesnt look like a hardware problem cos all of those results look ok, except your20C CPU, somethings up there. If it is a hardware problem, theres nothing you can do about it, your card is messed up.
If youve tried new drivers, and updating direct x, etc then its looking quite hopeless now
You could try a system restore maybe?? Sometimes, when im OCing and failing a lot, and i get a lot of BSODs, my comp gets corrupted, and every now and then it randomly shuts off, and i have to restore to before i started overclocking. I doubt its that simple, but anythings worth a go at this stage, right?
At a second glance, why do you have a 2.5v rail, and no 12v rail monitoring. Am i missing something?
I've done new drivers, can't find new directx stuff though. I've not done OCing so can't system restore, and haven't got any BSODs - the computer just freezes.
And, i have no idea why the 12v rail is missing - i have one obviously :p On Asus PC Probe reporst it at 12.22V though.
Has happened on desktop a few times, has just done it now and did it the other week too. Not as much, but every now and then it will lock up.
maybe a bit late, but ive had the same problem, i think, crysis crashed in dx10 but not dx9. In the system log it said there was an error in d3d10.dll, which is a dx10 component. I solved it by installing the latest direct x here. Install it, then find the setup file, and run it.
If your error is in a dx file (you didnt post an error report did you?) then here is your culprit
edit: its not the same, my pc crashed to desktop, but its still worth a try.
Your voltages are very odd. My Everest logs 3.3V, 5V & 12V, which is as it should be. Yours appears to log 2.5V (which shouldn't exist) and 3.3V. I presume Everest picks its data up from the mobo, so maybe there's where the problem lies.