So does chkdsk or sfc/scannow actually work /g/? Ive got the

>>61929823
Try it remotely with an install dvd.

Here's a paste from my os repair cheat sheet that I keep:

Windows install disc. Choose repair. Then repair tools (or whatever) just go for more repair. Then there will be list of repair tools and choose the command prompt.

Then cd/windows/system32


sfc /scannow /offbootdir=f:\ /offwindir=f:\windows

replace 'f' with drive indicated at the top of the menu of repair tools. It will say for windows on drive 'letter'.

If that doesn't work you might have to reinstall but it usually makes it at least a bit better.

>>61929823
How about investigating the actual cause of the BSOD instead of just trying random solutions you find on the Internet?

>>61929823
That doesn't look like a drive error tho.
>>61930812
Actually, dism offers similar functionality for windows image servicing and I have no idea what's better. Just m$ things I guess.

>>61929823
>chkdsk or sfc/scannow

yeah, they do, but for different things.

See >>61930841

>>61929823
:(

>>61929823
Did you actually bother to check event viewer to find cause of bsod? Inspected minidumps from crash?

>>61929823
-use bluescreenview from nirsoft or windbg from debugging tools from microsoft to find out what's causing the blue screens

-test your memory with memtest

Upload your minidump if you have one (in C:\WINDOWS\minidump\ by default)

>computer is melting
>nothing is actually properly inserted
>hard drive is basically dead
windows users online: UM SO sfc /scannow DIDN'T FIX IT, UGH FUCK THIS WINDOWS 10 UPDATE

No wonder apple pays out the ass for a genius bar

wow i havent expected to find actual answers to his question, i am positively surprised by you guys

>>61929823
Linux doesn't have Bsod