So for a while now my computer has been randomly crashing so after some tinkering I decided to run memtest to see if I could learn anything. I did find errors but I was hoping someone could help me interpret them. After running the full test overnight twice I got the following results.
https://www.dropbox.com/s/yhy1z4g3ebelkux/MemTest86-Report-20211118-043106.html?dl=0
https://www.dropbox.com/s/e3qo1z1mla7ihpg/MemTest86-Report-20211119-000137.html?dl=0
just the relevant parts
2021-11-18 04:34:36 - [Data Error] Test: 7, CPU: 4, Address: 1A67F3670, Expected: 00200000, Actual: 00000000
2021-11-19 01:25:17 - [Data Error] Test: 8, CPU: 4, Address: 1A67F3670, Expected: C1A471F7, Actual: C18471F7
2021-11-19 00:37:30 - [Data Error] Test: 7, CPU: 4, Address: 1A67F3670, Expected: F7FFFFFF, Actual: F7DFFFFF
My big question is do these indicate a bad cpu or bad ram? Or something else entirely?
So for a while now my computer has been randomly crashing so after some tinkering I decided to run memtest to see if I could learn anything. I did find errors but I was hoping someone could help me interpret them. After running the full test overnight twice I got the following results.
https://www.dropbox.com/s/yhy1z4g3ebelkux/MemTest86-Report-20211118-043106.html?dl=0
https://www.dropbox.com/s/e3qo1z1mla7ihpg/MemTest86-Report-20211119-000137.html?dl=0
just the relevant parts
2021-11-18 04:34:36 - [Data Error] Test: 7, CPU: 4, Address: 1A67F3670, Expected: 00200000, Actual: 00000000
2021-11-19 01:25:17 - [Data Error] Test: 8, CPU: 4, Address: 1A67F3670, Expected: C1A471F7, Actual: C18471F7
2021-11-19 00:37:30 - [Data Error] Test: 7, CPU: 4, Address: 1A67F3670, Expected: F7FFFFFF, Actual: F7DFFFFF
My big question is do these indicate a bad cpu or bad ram? Or something else entirely?
try testing the sticks individually, maybe just one of them is faulty. and they might indicate bad ram, I'd also test the ram at default speeds (no xmp profile), since oc might give some shenanigans
try testing the sticks individually, maybe just one of them is faulty. and they might indicate bad ram, I'd also test the ram at default speeds (no xmp profile), since oc might give some shenanigans
I'm not that experienced with memtest and related things so this is all just an educated guess:
Since all the errors occur on the exact same address and all the errors are just "bitflips" (e.g the value 00200000 is just one bit flip off 00000000; surprisingly all the bitflips occur on exactly the same bit), I'd guess it's a ram issue.
That being said I'm not entirely sure if that would bring down your whole system (depends on if your OS is using that address for something critical). Definitely do what Rockz said it is very likely just one stick of RAM acting up since it's the same address each time.
But I'd also recommend booting up Windows' Event Viewer and look for the most recent crash. It could state something interesting or it might just say something like "unexpected shutdown" definitely worth a shot though :)
I'm not that experienced with memtest and related things so this is all just an educated guess:
Since all the errors occur on the exact same address and all the errors are just "bitflips" (e.g the value 00200000 is just one bit flip off 00000000; surprisingly all the bitflips occur on exactly the same bit), I'd guess it's a ram issue.
That being said I'm not entirely sure if that would bring down your whole system (depends on if your OS is using that address for something critical). Definitely do what Rockz said it is very likely just one stick of RAM acting up since it's the same address each time.
But I'd also recommend booting up Windows' Event Viewer and look for the most recent crash. It could state something interesting or it might just say something like "unexpected shutdown" definitely worth a shot though :)
It should be noted that it's not a bitflip, the bit is supposed to be 1 but is 0 in all three cases.
Since this only happens for a single address then it's very likely that the bit at that address is simply dead.
In that case you can only remove the affected stick, and either run with just 8GB from now on or buy a replacement.
However, I'd like to point out something else.
CPU Temperature Min/Max/Ave 45C/98C/56C
98°C is extremely concerning, especially compared with the other one.
Unless the file you uploaded is corrupted or memtest86 somehow managed to get a wrong readout, or the sensor itself is dying (also extremely concerning) something went very wrong with cooling for a moment. Just a moment though, considering the average.
It should be noted that it's not a bit[b]flip[/b], the bit is supposed to be 1 but is 0 in all three cases.
Since this only happens for a single address then it's very likely that the bit at that address is simply dead.
In that case you can only remove the affected stick, and either run with just 8GB from now on or buy a replacement.
However, I'd like to point out something else.
[quote]CPU Temperature Min/Max/Ave 45C/98C/56C[/quote]
98°C is extremely concerning, especially compared with the other one.
Unless the file you uploaded is corrupted or memtest86 somehow managed to get a wrong readout, or the sensor itself is dying (also extremely concerning) something went very wrong with cooling for a moment. Just a moment though, considering the average.
I ran another test with xmp disabled last night and got an error in the same bit. I will run another trial with only one stick to find out which it is and decide how I want to handle that thank you for the help.
On the temps, thank you for pointing it out I hadn't caught that when I looked over them originally. In the past I did have a cooler issue that resulted in extremely high temps in the cpu so I could be having the same thing. I will look into it.
I ran another test with xmp disabled last night and got an error in the same bit. I will run another trial with only one stick to find out which it is and decide how I want to handle that thank you for the help.
On the temps, thank you for pointing it out I hadn't caught that when I looked over them originally. In the past I did have a cooler issue that resulted in extremely high temps in the cpu so I could be having the same thing. I will look into it.