I have recently been having issues with windows 7 BSOD'ing on me. I reformatted the drive and did a fresh install, but I still get BSOD's
I am running memtest86 right now to figure out if/what sticks need removed. What would be the maximum number of errors(if any) that a non-eec stick of ram would be allowed to have and still function?
I got 24 errors total. All the errors are in the 3100-3300 mb block. I have 3 2gb sticks. Removing If the memory is bad, I should take out the 2nd stick?
I pulled the bad stick of ram, ran memtest86 and everything works fine now. It was a g skill stick(about 3-4 years old) and it has a lifetime warranty on it.
Debating whether to try the RMA runaround to get a new stick and save $35.
Well, it would be wise to get an rma going, but the bad part is if it is a dual channel kit, they will want both sticks back.
Count_Chocu1a;5394217Well, it would be wise to get an rma going, but the bad part is if it is a dual channel kit, they will want both sticks back.
It is a single channel kit. It is DDR2, so I don't know if they will give me a new stick or just some money.
18th November 2004
Might as well do it anyway. It's kind of a win-win situation for you.
I would replace both at once, RMA the other, keep old one for stash.
Red_Fist;5394462I would replace both at once, RMA the other, keep old one for stash.
The other 2 sticks were from a dual channel corsair kit. Memtest86 showed no issues with them.
Pethegreat;5394179What would be the maximum number of errors(if any) that a non-eec stick of ram would be allowed to have and still function??
0. Good ram should not give you any errors at all.
*The.Doctor;53946990. Good ram should not give you any errors at all.
"Bad RAM" can function perfectly well for years, with the end user never really noticing a problem. However, if (or when) your OS tries to write to the bad sectors, bad things occur. I've seen this manifest as everything from artefacting in games to slower-than-usual operations (where the CPU will, I assume, redo tasks that have output saved to the bad block). The only time I've ever encountered a fatal error in a situation like this, however, was when installing a very large game. It unpacked the downloaded game install image and cached it to memory. The install failed when it attempted to read the bad sectors. Based on other changes I noticed when I replaced the bad RAM, I think that I'd been running with a bad stick for two or three months at the time.
Anyway, point is that you're probably functional, but not perfectly so any may have some pretty large problems. As others have said, replace, RMA and keep a spare (if you can). Most memory manufacturers that target enthusiasts are very good about replacing bad products, and I think that there's an expectation of higher-than-usual failure rates in performance memory.