techsupport

3093 readers

1 users here now

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:

You Should Know

Software gore

Recommendations

founded 2 years ago

MODERATORS

GatoB@lemmy.world

Win10 custom PC stopped booting (infosec.pub)

submitted 3 weeks ago by dotCody@lemmy.world to c/techsupport@lemmy.world

52 comments fedilink hide all child comments

Just started today. Was able to let it automatic repair and boot up. Was on for like 10 hours, shut down and tried to boot up some hours later. Now its completely stuck on automatic repair. Have unplugged all additional hdd's and then all unnesscarry USB's. Still doing this. Also removed my ethernet card. Still the same.

I cannot lose my data. I have several SSD's and HDD's with important files across several of them.

you are viewing a single comment's thread
view the rest of the comments

[–] FartsWithAnAccent@fedia.io -2 points 3 weeks ago (31 children)

Switch to Linux!

Seriously though, if it boots, update your drivers, probably your graphics card. Try downloading the latest from Nvidia or AMD or whoever makes your card. Your BIOS might have built in diagnostics too, try running them to see if anything throws an error should the driver update not do the trick.

Edit: Thought the "seriously though" would tip people off but I guess the crowd was too dense? Oh well, comedy is hard.

[–] Honytawk@discuss.tchncs.de 0 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

As if Linux can't have hardware failures ... Which is the main reason for blue screens.

Why are so many Linux fanboys so notoriously dense?

[–] FartsWithAnAccent@fedia.io 1 points 3 weeks ago

Funny how you are talking shit about "obviously dense" when you missed what was very clearly a joke literally followed by "seriously though" and then actual troubleshooting steps. Seems pretty dense...

load more comments (29 replies)