Image description:
A memory test screen that claims the test passed with no errors, while somehow the display itself has at least three errors on it.
The issue turned out to be bad capacitors.
Nah, it's says there's no0errors at the bottom. It's all good!
I'm surprised that it ran through even one full test with no errors. IME when RAM has any issues, you get a flood of errors during testing.
It can't even display a screen full of text without 3 errors, how did it get past an entire test without catching any?
A theory I have about why that happened that way and didn't get detected...
The bad caps might have been for the GPU slot power, and the glitch might have actually occurred in the GPU VRAM, not the system RAM.
Sigh, we'll never know for sure...
I know right? That's the only time I've ever seen such a thing, and I probably would have totally missed it if it wasn't for the no0errors glitch.
A few new capacitors fixed it right up.
Weird huh?
Also I ask:
~~Damn, I think you spotted two more errors that I hadn't even noticed. I hadn't noticed Test #0 or DDR669.~~
But you did miss one, "Press Ecc to exit" Should be Esc
I found that one extra funny, along with no0errors 😂🤣
I don't believe either of those are errors, unless I missed something on the test count. Counting starts at 0 and you already covered the DDR rate.
Also L3 cache "none" isn't an error. The CPU has no L3 cache.
Memtest does start at Test #0?
Okay, it's been forever since I've needed to run Memtest, I kinda forget these days.
That Ecc is definitely an error though, should be Esc
DDR669
N0ice
Just... Take my upvote and GTFO... 😂
This PC is anywhere from 2003-2008. Pretty sure K8 didn't have L3. And DDR2 RAM tends to show as mhz+mhz=DDRmhz.
The "DDR669" might be DDR2-667 with a slightly inaccurate clock
I did a little number crunching to see about that DDR669 thing...
If indeed the CPU speed is correct at 3014MHz, then the clock multiplier must be 4.5, yielding a RAM speed of 669.777MHz.
That part just might check out, but I dunno, I took that photo back in like 2011.
Public Blue Screens Of Death
Public displays and digital infrastructure software failing to do their job because of blue screens, crashes or other problems