this post was submitted on 08 Jul 2023
329 points (99.1% liked)

PC Master Race

14934 readers
1 users here now

A community for PC Master Race.

Rules:

  1. No bigotry: Including racism, sexism, homophobia, transphobia, or xenophobia. Code of Conduct.
  2. Be respectful. Everyone should feel welcome here.
  3. No NSFW content.
  4. No Ads / Spamming.
  5. Be thoughtful and helpful: even with ‘stupid’ questions. The world won’t be made better or worse by snarky comments schooling naive newcomers on Lemmy.

Notes:

founded 1 year ago
MODERATORS
 

Earlier this week, I bought myself a new 2TB NVMe drive on sale, and had planned today to install it. Knowing that the computer, built in Dec 2021 had an issue with PCIe at the time that prevented 4x drives from running at 4x, but now had a BIOS update that fixed that (and introduced support for two additional CPU generations), I thought I should go ahead and flash the BIOS too.

Sparing unnecessary details, everything went fine. I unseated the 3060Ti to get at the M.2 ports, swapped out the old drive for the new one. Plugged in a spinner I had laying around while I was in there. Machine wouldn't boot - so I reinstalled GRUB (yes, I'm a Linux user) and that was fixed. The disk had everything copied over from the old one, so that was fine too, other than some power management spam in the journal that was fixed with a kernel param. Seems fine, right?

So I spin up Minecraft to have a quick session. Frame rates are like, 3-20 fps for about 2 full minutes, then they get up to 60fps (Vsync'd). But every few minutes, they keep dropping and creep back up. Sometimes they bounce up.

There are a dozen potential problems at least that could cause something like this. So I went back into the newly flashed BIOS knowing that all my settings were reset, and started poking around and fixing settings. This was good either way, but it didn't fix my sporadic fps dips. The game ALWAYS started at sub-10 fps, but it would get to 60 eventually. Sometimes in a handful of seconds, sometimes in minutes. One time, all the textures refused to load. Another time, the GPU fell off the bus.

This was not a problem at all prior to the work, so I started reviewing what I'd done so far. I'd added a disk with all copied data.. but there's a nvidia cache in there... cleared that. No dice. I looked at heat. No problem. Same drivers as before, but maybe I have to roll back drivers, or kernel, or BIOS. I dunno. Frustrated as fuck.

Could also be a power issue. Or a reseating the card issue. I hadn't added any devices with more power consumption and I have ~100W of buffer on a good PSU, so it really should be a problem, but I reseat the card and replug the power cables anyway.

The problem is worse.

So I spend another hour and a half poking around forums looking at every possible thing I could do on the software side to fix this, before I decide to reseat the card one more time. I mean, the first time changed SOMETHING, even if it was for the worse.

Popping out the card, I blew into the slot as I thought I saw a tiny speck of dust. I used canned air the first time but this was really an afterthought by this point...

The body of a tiny moth popped out of the slot.

I reseated the card, spun up Minecraft, and everything is fine. Perfect frame rates, just like before.

I'll never get the hours back that I spent troubleshooting this today. At least several other items were improved along the way, such as RAM timings. But in the event this story helps anyone in the future, it's worth the time it took to type it.

you are viewing a single comment's thread
view the rest of the comments
[–] Sunspear 17 points 1 year ago (3 children)

Has anyone mentioned the origin of the term, computer bug? It is not a story a Jedi would tell you.

In the days of yore, when the marvels of computation were in their infancy, there arose a curious tale of a most peculiar occurrence. Lo and behold, within the realms of the great Harvard Mark II computer, a glitch did manifest itself. And this glitch, verily, was likened unto a pestilence that did plague the workings of the machine.

Now, the diligent engineers sought to uncover the source of this disturbance, to fathom the cause behind the malfunction. And as they delved deeper into the intricate labyrinth of wires and circuits, their eyes beheld a most astonishing sight—a tiny creature, not of flesh and blood, but of the insect kind.

With great astonishment, they did identify this creature as a moth, a small winged being that had inadvertently made its abode within the sacred confines of the machine. Thus, they spake among themselves, saying, “Behold, a bug hath infiltrated our realm of computation, and caused this mighty disturbance.”

And so, the tale of the computer bug was born, a term coined to describe those minute creatures that wrought havoc upon the intricate mechanisms of these contraptions. Though time hath passed and technology hath advanced, the legacy of this tale remains, reminding us of the humble origins of our digital dominion.

[–] [email protected] 1 points 1 year ago

Ok cool but why wouldn't a Jedi tell me that? Pretty sus.

[–] [email protected] 1 points 1 year ago

even today those damn moths keep getting in our computers, pretty fascinating

[–] [email protected] 1 points 1 year ago

I had a similar story with a real bug, going back many years.

I helped a customer with a setup that used OCR to import financial records. This was when statements were still paper based.

At some point I'm called in because one client wasn't getting billed.

Turned out a dead bug smooshed onto the scanner glass was knocking out their line.