That’s a bit too optimistic for me. Honestly, the quickest and smartest move is just to back up your vital files and reinstall Windows. You've got a whole mess of errors popping up tied to a few different drivers, plus some random glitches you can't even pin down...
Screw me, all the women are gathering 🤦 Now I'm gonna be 🙂 and 🙂
from 🐔 😂
Anyway, back to the point—there's a huge difference between being an open book and knowing exactly how much to reveal. Most people just don't get it... they're too naive. They overshare and then blame everyone else for knowing too much. 🤷 You gotta know when to hold back.
Wouldn't it be fair to just ask the users on Reddit if they'd prefer sterilization or an incognito mode for PDFs? 🤔 I'm pretty sure they'd pick the exact same solution as LjES and MK... 🤷
I might be running a little late. Liverpool plays right around then, plus I gotta factor in the trek over to Central Park this weekend. Probably won't roll up until after 4:30 PM... hope you guys are still around by then.
Grab the manual for the laptop or motherboard and figure out what that beep code actually means. That’s honestly the best advice anyone can give you. Once you know, go check the specific component it's flagging, along with the power supply and those power rails.
This is a pretty vague issue. Could be macOS, could be drivers, maybe even hardware... kernel errors aren't really a thing on their own, they just reflect whatever was running above them. Get a pro to look over those drivers and check your hardware. Hope you know someone who actually knows what they're doing...
Check which channels the other Wi-Fi networks are sitting on nearby, then just grab an empty one. Once you've done that, try connecting again. Also, maybe the driver isn't playing nice with your OS... worth checking that too.
Noah Sanchez39 said:I think there's a thing called a "max length" for Ethernet cables, but adding a few dozen feet shouldn't be much of a headache if you need it... find it.... 😁
Yeah, I'm thinking it's just those few dozen meters—maybe 50 feet or so... but at that distance, you'd be using different cables anyway, so it shouldn't even be an issue... 🙂
As far as I can tell, it’s totally possible your GPU is just dying... maybe some part of the chip fried itself somewhere. FurMark doesn't really explain that specific error, though. Based on everything else, you should just check if Speccy even recognizes the card. If it doesn't show up there, it's toast.