Forum Home
Press F1
 
Thread ID: 122156 2011-12-05 00:52:00 Perhaps my ram is broken? skeptile2 (16539) Press F1
Post ID Timestamp Content User
1247135 2011-12-05 00:52:00 hey people,
recently my computer has been freezing mid game. I just got a reasonably new CPU, it's (I think) not the graphics because the screen looks normal, except not moving. the only thing I can think of is the RAM. I have done prime 95 on each of the sticks individually (3x 512 mb) and each of the sticks have an error: "fatal rounding error - expected to be 0.4, was above 0.5" which makes me think that perhaps it's not the ram. I'm going round in circles here. any help???

edit: occasionally, it even freezes mid test.
skeptile2 (16539)
1247136 2011-12-05 01:27:00 Use MS RAM DIagnostics or the popular for some reason but incredibly slow memtest to test properly. pctek (84)
1247137 2011-12-05 02:11:00 Prime 95 is more of a CPU test than a memory one, and should not have errors. Is your CPU clocked correctly and is the cooler properly attached? try using realtemp or speedfan and check temps while running prime95, even on a stock cooler anything over 70 is a worry and if it goes into the 90s something is really wrong.

Also use the tools pctek mentioned to check the RAM.

It pays to be methodical when fault finding and eliminate things one by one, don't make 6 changes then try and figure out which one worked. Try running with a single RAM chip for a while, if that doesn't help try the other. If neither helps move onto the next suspect. Myself though I would look at the CPU based on your prime 95 comments.
dugimodo (138)
1247138 2011-12-05 03:25:00 Prime 95 is more of a CPU test than a memory one, and should not have errors. Is your CPU clocked correctly and is the cooler properly attached?

my CPU is definetly properly attached. the cooler is only a stock one, but it has worked fine before my PC started crashing.


try using realtemp or speedfan and check temps while running prime95, even on a stock cooler anything over 70 is a worry and if it goes into the 90s something is really wrong.

I did RAM test, (the test that mainly tests RAM, and not much CPU) and the CPU was only running at about 56% of its capacity, and it maxed out at about 55 degrees. BTW I use coretemp.


It pays to be methodical when fault finding and eliminate things one by one, don't make 6 changes then try and figure out which one worked. Try running with a single RAM chip for a while, if that doesn't help try the other. If neither helps move onto the next suspect. Myself though I would look at the CPU based on your prime 95 comments.

I have tested each of my RAM sticks individually, and in pairs, and each way it still comes up with the error. The thing is, this didn't start only when I got the *new* CPU (it was second hand), I had it for a while before it started to freeze???
skeptile2 (16539)
1247139 2011-12-05 03:48:00 Test the RAM with what we said, then come back and tell us what happened. pctek (84)
1247140 2011-12-05 04:09:00 Had a customers PC similar, would freeze at random times, The mouse sometimes moved other times it locked solid, but it passed all the stress tests, as well as Prime, memtest, as well as several others which should have made it fail.

One sure fire way to make it freeze was watch a video. It ended up being a faulty CPU. Changed it and it ran sweet as after that.
wainuitech (129)
1247141 2011-12-05 04:18:00 Take all of your overclocks off and try the game again. icow (15313)
1247142 2011-12-05 08:58:00 Quick update: I have memtested 2 of the RAM sticks, both are fine. Icow, it is a lot like that with me. Whenever you do anything stessful, (e.g. a game) it freezes. Btw, I have not overclocked anything. skeptile2 (16539)
1247143 2011-12-05 09:49:00 Ok sorry got that from your last thread. Tried using only 1 stick of ram? icow (15313)
1247144 2011-12-05 19:50:00 For me personally freezing issues have been RAM related, but the odds of all 3 of your RAM sticks being faulty seems pretty small, perhaps try setting the BIOS back to defaults in case anything is set wrong. dugimodo (138)
1 2