|
I just used it, and wow, I'm surprised, there are about 3000 or more errors in my ram.
|
Not the amount is interesting, but how the errors are distributed in the memory. Do you have two modules installed, or only one?
|
Since my laptop couldnt use ddr, I have no choice but to stick with this till I could afford new laptop. ;_;
|
I assume that the system uses SDRAM-SODIMM (144 pin). I can find a lot of these modules on the german ebay site (I think there are even more on the US homepage). So you can still find replacement RAM.
|
to be honest I'm confused what you meant with this, I'm totally noob for this stuff, is there any good tutorial to show me how to do this?
|
I want to be honest too. If you haven't understood anything I told you, you should really get some replacement RAM or live on with the permanent risk of loosing your data. I should mention that you're exposed to two types of risk. One is mechanical damage from the frequent power cycles, the other is filesystem corruption from bitrot in your memory. An operating system can just do anything if memory changes zeros to ones and vice versa at random. NTFS is relavitely safe when it comes to system lockups or power outage. But no filesystem is safe from software errors... and bad memory triggers a lot of these.
|
thanks in advance liquidacid. Now I want to try seagate seatools, I hope this hdd not broken already, because just today, I hard reset it about... 6 times or more (these bsod keep coming, sigh)
|
You can't expect any software which uses memory to work reliable on your system. If you choose to run any kind of harddrive diagnostic software on this system it could report false errors or corrupt the drive even more. If you have any important data on the drive I recommend you back it up now (NOT using the system with the bad memory) and don't use the backup media (if read-write media) with the system.
Additional Spam:
|
Because of the way Windows manages RAM it is not possible to "hide" the bad bits like in Linux. With 3000 (!) errors in your RAM you should throw it away NOW before you corrupt any data on your PC.
|
It's just that MS isn't really interested in this feature. You can 'hide' RAM from Windows, but only by telling it that it should only use that much of it. So you can define a maximum amount, but not the exact locations like with the badram patch - where you only loose the bytes that are bad.
So if your error is like in the first 10MB of the module, you only have this one and it has a size of 512MB... you're fucked.
|
BSOD and GPF will be your closest friends until you replace the broken parts.
|
Or switch to linux
This thing is sticky, and I don't like it. I don't appreciate it.