Well, my computer had been running completely and 100% fine for the time, yet when I play a game on it, one that shouldn't EVER lock up on this machine due to the games inferior graphics, it locks up anyways.
Now, I'm thinking the problem is my ram, as I literally JUST got new ram for my system. It went from 512 to 768, which for a game like Sacred or Diablo 2, I should really never had problems.
So, do you think it's my ram, and should I remove it, or is there a way to fix this problem. Who knows, maybe it's just getting adjusted to the boost. But any advice would be appreciated.
Yet another Ram/Memory Question
-
Siberys
- Posts: 6207
- Joined: Sat Apr 30, 2005 7:16 pm
- Location: I live in that one place with the thing
- Contact:
Yet another Ram/Memory Question
Listen up maggots, Mr. Popo's 'bout to teach you the pecking order.
It goes you, the dirt, the worms inside of the dirt, Popo's stool, Kami, then Popo.
~Mr. Popo, Dragonball Z Abridged
It goes you, the dirt, the worms inside of the dirt, Popo's stool, Kami, then Popo.
~Mr. Popo, Dragonball Z Abridged
Well, for my last RAM purchase, I bought a 128 and a 256MB stick. The 256 turned out to be faulty, it wasn't an obvious thing, it had some light marks on it, it may have been burnt.
Anyway, when I installed it, the computer simply failed to recognise it, just delivering blue screen errors as soon as it tried to load Windows.
It's possible that there is a kind of RAM fault that would allow Windows to load, but it just seems unlikely to me, any RAM problems would probably affect the whole system, not just a few games.
And that would be the same if the faulty stick of RAM was combined with working sticks.
You could try to remove it and see if there are any differences in performance beyond those you would usually get from decreasing the RAM. As for being able to tell that difference, I'm not sure.
Anyway, when I installed it, the computer simply failed to recognise it, just delivering blue screen errors as soon as it tried to load Windows.
It's possible that there is a kind of RAM fault that would allow Windows to load, but it just seems unlikely to me, any RAM problems would probably affect the whole system, not just a few games.
And that would be the same if the faulty stick of RAM was combined with working sticks.
You could try to remove it and see if there are any differences in performance beyond those you would usually get from decreasing the RAM. As for being able to tell that difference, I'm not sure.
-
dj_venom
- Posts: 4416
- Joined: Mon Sep 27, 2004 7:00 am
- Location: The biggest island in the world
- Contact:
A couple of things:
1) Try taking it and putting it back in. Or doing a simple wiggle. You would be surprised how effective that is, as RAM has a tendency to fall out of place.
2) There could be a fault. When my brother was doing something with his RAM, he accidently partially fried it. From then on, the computer would boot up, though every now and again, it would refuse to. This was passed by wiggling the RAM. Eventually he replaced it, and it all works now.
If you do try the wiggle, don't do it after shutting your computer down, you should let it cool down. I would suggest leaving at least 2 hours, simply because RAM is easy to fry if it is still hot.
1) Try taking it and putting it back in. Or doing a simple wiggle. You would be surprised how effective that is, as RAM has a tendency to fall out of place.
2) There could be a fault. When my brother was doing something with his RAM, he accidently partially fried it. From then on, the computer would boot up, though every now and again, it would refuse to. This was passed by wiggling the RAM. Eventually he replaced it, and it all works now.
If you do try the wiggle, don't do it after shutting your computer down, you should let it cool down. I would suggest leaving at least 2 hours, simply because RAM is easy to fry if it is still hot.
In memorian: Fiona; Ravager; Lestat; Phreddie; and all of those from the 1500 incident. Lest we forget.