What's the dumbest, edge case problem you've encountered, software or hardware? I just figured out that the WiFi card I added to my desktop was interfering with my DisplayPort cable's signal causing artefacts and flickering. I tried using an older, thicker and presumably better shielded cable with no luck, I added a ferrite beads with no luck, in the end I removed the WiFi adapter and everything works perfectly.I've read about USB 3.0 interfering with 2.4GHz radios, but I've never seen DisplayPort interfering in such a way.
>>107011365Have a bump for the interesting thread idea, but I can't think of anything right now.
>>107011365Have you tried just putting it into another slot?Motherboard circuits are like the wiring in an old house or something. Shit's weird
>>107011365I remember cod4 wouldn't run on my computer unless I had something plugged into my aux port.Looked it up at the time and it was a common problem apparently. Kinda funny. Was a driver issue or something but I just always made sure to plug something in because I was a kid
>>107013163There's no other slot, I wasn't really using it anyway I only installed it because I bought a cheap M.2 to PCIe adaptor to make use of my old WiFi card.>>107013195lollmao even
>>107011365On an old system the front jacks used to connect mic and headphone had some kind of retarded hardware-based power-saving feature which piggybacked on jack-sensing being enabled for the Realtek chipset on the mobo. With jacksensing disabled or nothing plugged into the jacks, the entire front dash would automatically power down a few minutes after boot. Including the USB ports on the front.Solution? Just keep an empty converter or splitter plug plugged into the front dash at all times.
>>107011365Have you tried using more grounding crystals?
Steam game crashing on startup repeatedly with very strange visual glitches. (omelette you cook)Turned out it was because a nintendo switch controller was plugged in over USB.Happened again months later with project zomboid but it instead exhibited by opening infinite browser tabs when the game opened, thereby crashing the game. Again problem went away after unplugging usb switch controller
>>107011365fifteen years ago or so I spent three hours trying to fix my WoW guildmate's machine. Wouldn't turn on at all. Long story short it was a busted front-panel USB port. The +5v and ground pins were shorted and the mobo/PSU detected the short and refused to power up. Disconnected those and everything was fine.
>>107015700How'd you detect that?
>>107011365Nobara not liking my wifi card just because... it doesnt ok
>>107011365 On my old pc I had to turn my connection off and on to access any non-google websites.
>>107011365Had to deal with the machine from hell ~15 years ago.Constant hardware related bluescreens. I'm talking you couldn't use a browser or open word for five minutes before it'd shit itself, but it could handle stress tests and even gaming no issue.Logs indicating a different thing each time, dying hard drive (replaced), dying RAM (replaced), GPU (replaced), yada yada.In the end every component got changed, most multiple times, different driver versions, entirely different part manufacturers, we even switched it from an AMD to an Nvidia GPU at one point suspecting the stellar AMD drivers but nope it still kept bluescreening. Sometimes that thing still haunts me I'm not joking. We were dealing with this piece of shit on and off for over a year.
>>107015734I was kinda panicking and decided that I'd unplug absolutely everything that wasn't needed to boot. No drives, no peripherals but a KB and a monitor on the iGPU, no cards, no front-panel connectors (I jumped it with a screwdriver) It was dumb luck that it came right alive and so I knew that one of the trivial things I'd just taken out had to be the problem. I'd already tried a different PSU, GPU, and RAM with no luck.
>>107015785Was this at work or a home pc?
>>107011365Is once accidentally restarted instead of shutting down my pc. Then I shut it down right after it restarted and somehow it kept crashing when starting after that.
>>107011365anyone else also just keep getting some of the most retarded obscure issues every time you think something is a 30 minute job at best and then it turns into 300 minute job?
>>107015839At work. Quickly got swapped out for a working replacement obviously but we kept fucking around with it because we wanted to know what the fuck was wrong with it. Never ended up figuring it out.
>>107015862Did you also swap out the motherboard and power supply at some point?
>>107015871Went from an AssRock to an ANUS (this was shortly before they got bought) to I think Gigabyte. The original AR board also was originally replaced under warranty by the seller so yeah more than once. PSU got swapped once initially and then a few times later on when it was downgraded to a curiosity to poke at not a real issue to deal with.When I say every part was changed I mean every part down to motherboard screws, the case and every cable. It was just fucking cursed. You could have perfectly known good, working hardware, put it into that piece of shit and it'd stop working sooner rather than later.
>>107015833Well done, anon
>>107015856all the time. but often I just get sidetracked fixing some bullshit that pops up that's not strictly necessary for the original thing I wanted to do
>>107015856My last 30 minute job turned into a three day excursion. Never touch a running system.
>>107015967You are right that sounds cursed.Would have been interesting to get a bunch of secondhand pcs, the put one part in each pc to see wich one was the bearer of the curse.
my bluetooth headphones are in pairing mode 24/7, meaning any random nigger can connect and listen in on the built in microphone or play some audio. the chink responsible for the firmware at least had the decency to put a "bluetooth connected" announcement when someone connects. happened once or twice in the couple of years I've had it
>>107016060I'm not even sure you could say what parts are even part of the original PC, it's the ship of Theseus if the ship parts just had a bad tendency to spontaneously combust but only when assembled.
>>107016096Plus given the track record the curse would attach itself to a different part every time
>>107011365dock management software, like for cargo logistics, i found that if you had some text saved on your clipboard then the route closing process would be fasterie you pick a trailer, complete the shipment so it reallocates the remaining material to the next trailer for the destination and breaks all the shipments off from their origin to make one compiled shipmentthis process usually takes like 10-15 seconds when you click the button but if you had something copied or whatever it would take 2-3 secondsno fucking idea why
Just remembered another inexplicable problem from years ago.Windows XP, work PC. Every time you used the search it would BSOD, but was perfectly stable otherwise.Ended up being the ATI graphics card driver and to this day I have no idea what's the relationship between the two. One specific version caused the problem, upgrading fixed it, rolling back reintroduced the problem, it was like clockwork.>>107015848This reminds me one time I unplugged a USB drive while Windows was shutting down, no idea what system file it was writing to but I got a BSOD at boot every time after that and had to reinstall. >>107016160lol
>>107016861Had a similar problem around the XP era also related to ATI drivers. Constant bluescreens that stretched across god knows how many driver versions until the problem finally got fixed.
>>107011365>Be me >switch from AM4 to AM5>Buy a non-Asus motherboard for the first time in my PC building career>Get a 64gb kit of gskill trident z neo ram clocked at 6000mt and a CAS latency of 30>pop it into my board and turn on EXPO>takes 5mins to finish posting >People online say to turn on memory context restore>turn it on>all seems well at first, PC only spends like 5 seconds posting >boot into linux >notice bad page file errors >kernel panic >reboot into BIOS>RAM is now clocked at 5600mhz for some reason despite the EXPO profile being set >Turn off EXPO, set RAM to the JEDEC standard speed for DDR5 which is 4800mhz>PC boots up right away>Think its just a bad RAM overclock >Try to sleep my PC >Fails to wake up with the CPU and memory debug lights on >Same behavior in windows >Buy another kit of RAM>same issuesI will never buy an MSI motherboard again
>>107011365MPV will not properly interpret Rec.2100-PQ AVIF image files if the AVIF in question has an empty string as its HandlerDescription tag, and will instead interpret it as an sRGB image. This is in spite of the proper CICP and CCCM tags being present within the file and being interpreted by other programs such as Chromium or other HDR image viewers just fine. The tag in question doesn't even have any color management data, it literally just tells which program made the AVIF.Libavif versions before 1.2 apparently write this tag, while versions after it do not. All to save 7 bytes of data.
>>107016969The problem is DDR5 itself not the motherboard.t. ASUS AM5 with the same problems
>>107017043Is DDR5 just half-baked or something?
>>107011365I have an old Gigabyte X58 UDR3 system that would just shut off at random if the ambient temperature was below 70F. Sometimes it would even power cycle frequently enough to automatically trigger the dual-BIOS restore "feature." Shit was annoying AF. I've tried swapping PSUs and making sure nothing was grounding out but it just kept happening.
>>107011365Every dozen or so restarts of my computer, my bluetooth module bricks. It has to be disabled in UEFI and reenabled for it to work again. I don't know why this happens at all. It just does.
