Blue screening

File: windows question.png (656KB, 1366x768px) Image search: [Google]

656KB, 1366x768px

>>62127887
Donate it to the EFF.

>>62127944
Posted here because their forum will take days for response

>>62127958
Nobody from here is going to know what all that shit means. You can google just as well as us, and I'm guessing you already have, and realized that there's no answer.

You want an answer faster than that? Use a multimeter, and find out what's wrong.

>>62127887
1. Format everything
2. Install an OS that respects your ability to fix a computer

This is the best and fastest way to solve any Windows issue.
>b-b-b-b-b-but my data!!!
Your fault for not having backups.

>>62127887
basic recovery first:
try repair in recovery mode
chkdsk
try memtest (usually bundled with live (x)ubuntu, checks if the ram is allright)
reinstall (use recovery mode/ live Linux to copy data)

hardware shenanigans:
disconnect as much crap as you can and turn on computer, connect one crap at a time and check if one of them is causing problems

voodo recovery below:
search for broken/blown capacitors
replace CMOS battery

It seems that Windows could be broken somehow because recovery is still working (or hardware failure that allows PC to work in basic ways)

disable every "extra" thing you can in bios, like sound card, igpu, network card, and then see if you can boot in normally. If yes, just enable shit one by one and see which one kills your PC.

>when the answer is literally, unironically to install gentoo
also what kind of username is trent. Sounds gay