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.

  • Vik@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    5 days ago

    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?

    • over_clox@lemmy.worldOP
      link
      fedilink
      arrow-up
      1
      arrow-down
      8
      ·
      5 days ago

      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!

        • over_clox@lemmy.worldOP
          link
          fedilink
          arrow-up
          1
          arrow-down
          10
          ·
          5 days ago

          Figure it out then, there’s literally at least 3 errors on screen.

          If you’re offended by my words, then prove me wrong.

        • over_clox@lemmy.worldOP
          link
          fedilink
          arrow-up
          1
          arrow-down
          5
          ·
          5 days ago

          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.

          • Vik@lemmy.world
            link
            fedilink
            English
            arrow-up
            5
            arrow-down
            1
            ·
            edit-2
            5 days ago

            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.

            • over_clox@lemmy.worldOP
              link
              fedilink
              arrow-up
              1
              arrow-down
              6
              ·
              5 days ago

              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.

              • Vik@lemmy.world
                link
                fedilink
                English
                arrow-up
                4
                ·
                5 days ago

                except that this blatantly isn’t a test, and that wasn’t the answer? baby what is you doing?

                • over_clox@lemmy.worldOP
                  link
                  fedilink
                  arrow-up
                  1
                  arrow-down
                  5
                  ·
                  5 days ago

                  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!

                  • Vik@lemmy.world
                    link
                    fedilink
                    English
                    arrow-up
                    4
                    arrow-down
                    1
                    ·
                    5 days ago

                    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.

    • over_clox@lemmy.worldOP
      link
      fedilink
      arrow-up
      2
      arrow-down
      5
      ·
      edit-2
      5 days ago

      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…

      • Vik@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        5 days ago

        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?

        • over_clox@lemmy.worldOP
          link
          fedilink
          arrow-up
          1
          arrow-down
          6
          ·
          5 days ago

          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.

          • Vik@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            5 days ago

            that still doesn’t explain this specific behaviour. habibi why are you so mad

            • over_clox@lemmy.worldOP
              link
              fedilink
              arrow-up
              1
              arrow-down
              2
              ·
              5 days ago

              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!!