Note the at least 3 literal errors on the pass screen...
Edit: Votes don't matter to me, but if you missed the three obvious errors on screen, you shouldn't be a technician. The problem was failed integrated GPU capacitors.
Just an observation from someone who happened to memorize some ASCII code: from an ASCII viewpoint, 45 73 63 is hex code for "Esc", with "s" being 73 and "c" being 63. I can readily see where bits flipped: at the fifth least-significant bit (compare 73 (0111 0011) and 63 (0110 0011).
Similarly, "no0errors" where "0" should be a space. "0" is 30 while space is 20. Again, another specific flipping at the fifth least-significant bit, only difference that this time a 0 became 1 (compare 30 (0011 0000) and 20 (0010 0000)).
The delimiter from the status of "Test #0" seems like a control char-code emerged from a start bracket. If the start bracket has the same char-code as expected from ASCII (5b), and considering how the flipping of the fifth least-significant bit seems to be recurrent, it'd be 4b but this would result in uppercase K, so it's either a different char-code for bracket or a bit-flipping happening in another position.
But what renders text is the graphics card. Given that the background is slightly shifted rightwards (notice how the blue background cuts through the initial letters from the first column of text, particularly "A" from "Athlon", "L" from "L# cache" and so on), this seems a graphics glitch rather than a memory glitch. And memtest86+ isn't designed to test the GPU, so it's beyond the heuristics. It's akin to expecting memtest86+ to test for dead pixels on a LCD panel: it simply can't.
(P.S.: it's unnecessary and disrespectful to attack others just because others couldn't see what you wanted them to see; slurs won't help people see what you see)
Thank you for the breakdown, that's effectively what happened.
Sorry if I came off the wrong way for many, I'll just more or less drop this post/comment chain.
I believe, and I’m probably wrong here, so feel free to correct me, that the visual glitches are part of the video card’s implementation of this specific screen mode, which would be a graphics memory glitch. So the RAM might actually be fine, but you may have a bad video chipset instead.
You're both right and wrong. All cool.
The system's RAM was okay, but the system's VRAM was separate, but still integrated. It was the VRAM caps that were bad. After replacing those, the system worked fine.
Oh, nice! I was on the right track. :) Also, I think there’s another glitch. Shouldn’t there be a progress bar next to the 10%?
Maybe you need to look at it again. Looks like 0 actual errors.
I can't find the Ecc key...
Am I missing something? It says errors 0.
Press Ecc to exit...
for a moment I thought this was 86+, for which you could submit a lil pr to fix this typo. is this is the passmark one you can prob send them an email or something?
It was a very old version from around 2008, and what I discovered was that the onboard GPU had failing capacitors. And yes, screenshot from real hardware.
I actually managed to fix it, but like who the hell expects the literal MemTest to declare a pass when obviously something failed?..
Edit: Assumption, MemTest wasn't designed to test GPU memory back then...
oh right, I'm not sure if the GPU would really compose that differently even though it was faulty? honestly my guess was this was a typo in the program itself?
Again, please re-read my comments.
I didn't say the GPU was faulty, I said the GPU capacitors were faulty.
Please learn the difference between components.
Please.
that still doesn't explain this specific behaviour. habibi why are you so mad
I replaced the obviously exploded capacitors, and the system worked fine.
Explanation is simple, diagnostic software ain't smart enough to identify that capacitor C307 or whatever is expanding and about to explode, but putting your own human eyes on it can reveal a lot!!
Wait, you said typo?
God fucking damn, none of you new fuckers can spot a binary glitch in ASCII?
There's literally 3 on screen!
in our defence, the quality of the picture provided is jpeg af
This is OG photo from like 2011, from hardware made around 2009.
This is the only remaining photo I have, captured at work on a PlayStation Portable.
Yes I had the Chotto Shot Camera accessory.
you posted this in a tech support community, it doesn't sound as if you need support. I'm not sure what you really wanted here?
the interesting this is that you attributed this anomaly to gfx hardware, in an environment which isn't composed by gfx hardware.
Honestly, I just wanted to test the tech support community.
I have learned that people couldn't answer the enigma of why a RAM test would both pass and fail at the same time.
Answer was bad caps, which I replaced, and worked fine.
The real question is if people/techs could even notice the errors on screen?...
This was a test.
except that this blatantly isn't a test, and that wasn't the answer? baby what is you doing?
This was a test, based on proven evidence and full repair, if anyone in tech support would even think to look at or test the capacitors.
At this point, more have failed than passed my test.
NEVER IGNORE THE CAPACITORS!
that's still not making sense to me. this is an environment composed entirely in sw. I'm not sure even a failing / damaged gfx adapter would behave in this specific way.
this sounds fucking awful but you'd be surprised how far you can get into percieved 'regular functionality' when arbitrarily removing caps from the board.
show us the after screen and show us the caps replaced on the asic.
What is this supposed to mean?
Someone please actually read the ASCII binary table between Esc vs Ecc...
What's the difference between Esc (What was meant to be printed) vs Ecc (what was actually printed)...?
It's a one bit ASCII error...
s = 1110011
c = 1100011
It's a friggin one bit error, which I discovered in 2011, replaced capacitors and fixed.
show us the caps you've replaced on the board.
Do you not understand the difference between the years 2011 to 2025? You think I kept those exploded capacitors?
If you can't take my simple advice and just look at the capacitors, or ya know, even test them, then please go away. Shit is usually obvious if you just look at it.
so you took the time to photograph memtest with a psp but not the damaged hardware you were working on?
You think everyone had a camera up their ass back in 2011?
That's what I had, paid a good $200 for that and a 4GB memory card at the time.
phones with cameras were everywhere as far back as the mid 2000s
I guess you have no clue what the irony is..
Esc = Escape Key
Ecc = Error Correcting Code RAM
I happen to have ECC RAM, ChipKill compliant.
Ecc ≠ Esc
I'm familiar with ECC, don't worry.
You may be unaware that this is used in even consumer grade gfx hardware (depending on the IHV)
Again...
Capacitors.
Is it that fucking hard to figure out?
Apparently so, you seem to be berating me for advising techs to just use their friggin' eyes.
I'm laying into you for wasting people's time in a forum designed to offer help to people who are out of options by attempting to put out some sort of "gotcha" post under an extremely flimsy premise whilst being extremely rude to everyone around you.
I don't like to be mean to strangers on the internet but I feel like you deserve an exception; the posterchild of /r/iamverysmart
Wow we sure what to hang out on your post when you call us all "new fuckers"
Figure it out then, there's literally at least 3 errors on screen.
If you're offended by my words, then prove me wrong.
The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.
If something works or if you find a solution to your problem let us know it will be greatly apreciated.
Rules: instance rules + stay on topic
Partnered communities: