I was trying to play Starcraft II, and it worked for a while, and all of a sudden it would give me something like
occurred at 001B:00D8F596. The memory at '0x00000000' could not be read. (it was very similar to this message, if not the exact same)
Afterwards, I figured it may be the game, so I test out some games that I've had working in the past, and they all start smoothly enough, running for upwards of 5-15 minutes or so, and then booting to the desktop. Some of them didn't give me error messages, but I made the assumption that it was the same type of error.
Anyway, after I thought it was the hardware, I tested the memory, because it sounded like a memory issue, with memtest86, and went through upwards of 20 cycles, and the memory tested perfect, with no errors. Next, I decided to stress test with Prime95, and I'm not sure exactly what it's telling me, but here's what it says after most tests:
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware Failure Detected, consult stress.txt
So, at this point, it's at some point in the data moving that is screwing up, and I want to say CPU is the issue, but I'd like to be 100% sure. In the case that the path to the CPU is messed up, it could cause numbers to change on the way; in turn, screwing up complicated processes like games, but not seeing many issues in regular OS function.
I think I've covered everything, but if there's something else I should post, let me know. Thanks!
Edited by Mechanimal, 13 October 2010 - 02:46 AM.