>computer crashes >OS won't start >do startup repair

>>61281910
I hear that if you throw a flash drive really really fast, it can damage it. So yes, the speed of the flash drive can be an issue.

when my computer did this it was t he stock mobo failing

>>61281930
It seems like you're implying that referring to drives as having "speed" is a peeve here, like referring to magazines as clips is elsewhere. Is that correct?

>>61281935
Did the startup repair finish for you though? I'm using the computer right now, seems fine. Just played a game. Should I still be worried?

File: He12-Web-400x500.png (167KB, 400x500px) Image search: [Google]

167KB, 400x500px

>>61281910
Microsoft's idea to allow startup repair to run
chkdsk /r
was pure genius
it works great on full multi-terabyte drives

can't wait to get a crash on one of these babies filled to the brim with data.

>>61282403
In the future if this happens should I run chkdsk from the command prompt instead of doing startup repair? I still can't believe it took almost 4 fucking days.

>>61281955
No, they're saying that if a flash drive is subjected to hard impacts it may no longer be able to transfer data as rapidly.

>>61281973
Yes, /v/tard. You should worry about your clueless life.

>>61282783
You don't understand the difference between knowledge and intelligence which in itself is a red flag that you have sub-par intelligence. Fortunately for you there's a board specifically meant for retard containment.

>>>/pol/

>>61282663
chkdsk /f should be enough. it just checks the integrity the file system

chkdsk /r scans every file (all the bytes), then all the free space. freaking retarded.

File: 2343253453245.gif (140KB, 790x548px) Image search: [Google]

140KB, 790x548px

>>61281910
>How can anything on a modern computer take that long?
>The hard drive

Rly meks u fink

>>61282926
Is chkdsk /r essentially what automated startup repair is doing?