I got to 2x, and my eyes glazed over.
Is my new ram deffective?
- Thread starter Maniacal
- Start date
Maniacal
the green Napoleon
Tested the sticks again, ran memtest86 to test it out and see how it works with my origional 2 sticks in, it was fine. Tested one of the new sticks by itself, its fine. Put in the stick I think had caused issues before, and it came up with a couple of errors.
One, when I started Mass Effect it blue screened due to "IRQL_NOT_LESS_OR_EQUAL" and some bug code string at the bottom it doesn't give you time to write down (ie several things like this where # stands for a number between 1-9: 0X000000###).
Second, during the test it recorded two ECC Correctable Errors.
3. The test was 100% complete with 90% completed on what I assume is the last thing it was doing (so I guess it was really more like 99.99% done, but it said 100% but did not finish), however it stopped due to a CPU interruption? There was also a number of strings of code (like the BSOD one but less 0s) on the screen but I have no idea what they meant.
One, when I started Mass Effect it blue screened due to "IRQL_NOT_LESS_OR_EQUAL" and some bug code string at the bottom it doesn't give you time to write down (ie several things like this where # stands for a number between 1-9: 0X000000###).
Second, during the test it recorded two ECC Correctable Errors.
3. The test was 100% complete with 90% completed on what I assume is the last thing it was doing (so I guess it was really more like 99.99% done, but it said 100% but did not finish), however it stopped due to a CPU interruption? There was also a number of strings of code (like the BSOD one but less 0s) on the screen but I have no idea what they meant.
Maniacal
the green Napoleon
Well yes I figured it was defective, but I'd like to understand the error a bit more.
Genocidicbunny
Bug squasher
It means its bad. Check the old RAM in the same slot as this new one was. If its not causing issues, one of the ram banks on the new module is probably bad. If you have errors all over the place, as in the addresses arent largely sequential but bounce around the whole module, then its likely a problem with the memory controller. But in this case, both the old and new RAM would be erroring out.
Similar threads
