Spot checking for faults - at my wits end

2009090917h46cpu1.png

2009090917h46cpu2.png

2009090917h46cpu3.png

2009090917h46cpu4.png

2009090917h46gpu1.png

2009090917h46vcore.png

2009090917h46volt3.png

2009090917h46volt12.png
 
I'm getting the same problems with the ram voltage pushed up to 2.10. I'll upload the images if I can find where OCCT stored them.

Isn't there another way to find out what is causing the crashing? Surely it'll be easier to address then.

Did you run memtest yet?
 
Did you run memtest yet?

No I didn't, I forgot about it as it's not installed. Recommended time to run it for?

Also, in the advanced settings for startup and recover where I changed it to not auto reboot on failure, there's an option to write events to system log. Would the BSOD info be posted here? If so, where do I find it?
 
No I didn't, I forgot about it as it's not installed. Recommended time to run it for?

Also, in the advanced settings for startup and recover where I changed it to not auto reboot on failure, there's an option to write events to system log. Would the BSOD info be posted here? If so, where do I find it?

You burn memtest to a CD/USB drive, and it runs before the OS kicks in (so you can eliminate the OS as a confounding variable)

And I'd like to hear what other people have to say, but the 3.3v line seems to be dipping below a fair bit - but certainly not outside of tolerances so I don't think that is a problem. Mine doesn't deviate from 3.4V, but I'm not sure whether its reading properly on my machine.

Let's see what the other guys think, but I think they'll agree it doesn't look to be CPU/PSU.
 
You burn memtest to a CD/USB drive, and it runs before the OS kicks in (so you can eliminate the OS as a confounding variable)

And I'd like to hear what other people have to say, but the 3.3v line seems to be dipping below a fair bit - but certainly not outside of tolerances so I don't think that is a problem. Mine doesn't deviate from 3.4V, but I'm not sure whether its reading properly on my machine.

Let's see what the other guys think, but I think they'll agree it doesn't look to be CPU/PSU.

I'm tempted to try and format. The fact that Stalker ran in March/April on Vista 32, and I got one play through on DOD on Win764 just doesn't sit right with me. I just can't swallow that there might be a hardware fault that bugs out on these two games, but Crysis doesn't kick it out immediately.
 
I'm tempted to try and format. The fact that Stalker ran in March/April on Vista 32, and I got one play through on DOD on Win764 just doesn't sit right with me. I just can't swallow that there might be a hardware fault that bugs out on these two games, but Crysis doesn't kick it out immediately.

Yeah, reformatting/reinstalling will be a lot less effort than spending hours trying to figure out a problem that might not even exist
 
Yeah, reformatting/reinstalling will be a lot less effort than spending hours trying to figure out a problem that might not even exist

I'll give it a go later I think. I need to back all my stuff up off of my primary partition (Don't want to lose all my bookmarks and stuff this time) and i'll try that.

I've got a feeling something must be bugging out though, otherwise it probably wouldn't reboot upon crashing even when set to not do that.
 
I'm tempted to try and format. The fact that Stalker ran in March/April on Vista 32, and I got one play through on DOD on Win764 just doesn't sit right with me. I just can't swallow that there might be a hardware fault that bugs out on these two games, but Crysis doesn't kick it out immediately.

You claimed you've reformatted before and it made no difference, so what good will doing it again do? If it only occurs on certain games there must be a reason behind it.

CPU and PSU seem fine, GPU fine, mobo fine.
What's left?

GPU overheating in these certain games
RAM is unstable and when you boot up RAM intensive activities it makes your PC throw a hissy fit
HDD is borked

Check these things before you format.
The reason I'm going onto you about the RAM is well say for example Crysis uses 40% of your RAM and runs fine, if these 2 games in particular take your RAM usage to 80% and then your PC loses power, do you not think that could be a likely cause?

Just because Crysis has more intense graphics doesn't mean it's more RAM depandant than STALKER is, Crysis relies majorly on the GPU.
 
You claimed you've reformatted before and it made no difference, so what good will doing it again do? If it only occurs on certain games there must be a reason behind it.

CPU and PSU seem fine, GPU fine, mobo fine.
What's left?

GPU overheating in these certain games
RAM is unstable and when you boot up RAM intensive activities it makes your PC throw a hissy fit
HDD is borked

Check these things before you format.
The reason I'm going onto you about the RAM is well say for example Crysis uses 40% of your RAM and runs fine, if these 2 games in particular take your RAM usage to 80% and then your PC loses power, do you not think that could be a likely cause?

Just because Crysis has more intense graphics doesn't mean it's more RAM depandant than STALKER is, Crysis relies majorly on the GPU.

The reason I question this is, I seriously doubt Stalker is more RAM intensive on the menu screen, than Crysis or any other game is actually in game. I literally boot and fail.
 
The reason I question this is, I seriously doubt Stalker is more RAM intensive on the menu screen, than Crysis or any other game is actually in game. I literally boot and fail.

You'd be surprised, honestly.
Some programs have a set limit they just hog up as soon as it's launched.
 
I ran Prime95 blend test for 2 hours with no errors; would that have not used maximum ram?

a lot yeah, but still not as good as memtest is.

You seem really reluctant to even try it, no idea why, usually if people suggest me something I at least give it a go. I'm not going to add anything else it's your choice, you can't expect people to help if you won't do the tests to narrow down the possibilities yourself.

Good luck.
 
a lot yeah, but still not as good as memtest is.

You seem really reluctant to even try it, no idea why, usually if people suggest me something I at least give it a go. I'm not going to add anything else it's your choice, you can't expect people to help if you won't do the tests to narrow down the possibilities yourself.

Good luck.

Reluctant to open my machine and take out sticks of RAM. Apparently you run one stick at a time to check for errors; If I leave all 4 in and run it and it comes up clean, can I avoid messing with removing them?
 
You would do 1 stick at a time once you find there is an error (to isolate it)

I would try running it without removing anything first. The only cost is time (and bit of electricity).
 
I think I am about to kick myself in the face, especially as someone suggested it earlier in the thread.

I rolled back my drivers to two releases ago. So far, everything is fine.

Thanks for all your help though.
 
Back
Top Bottom