If you get a BSOD, is it necessary to do a chkdsk? What would be the
consequence of not doing a chkdsk?

"void.no.spam.com@gmail.com" <void.no.spam.com@gmail.com> wrote:

>If you get a BSOD, is it necessary to do a chkdsk?

No...

> What would be the consequence of not doing a chkdsk?

1) Your disk wouldn't get checked
2) If caught, you'll get 90 days in jail and a $500 fine.

<void.no.spam.com@gmail.com> wrote in message
news:f099c439-ba8c-4fd9-ad20-1d3e4f3498f0@a70g2000hsh.googlegroups.com...
> If you get a BSOD, is it necessary to do a chkdsk?

No

>What would be the
> consequence of not doing a chkdsk?

Any errors your file system has may snowball over time until there are
serious errors and/or corruption occurs, so, for example the OS won't load,
or some program may crash consistently because one of it's DLL's is damaged.

You can run chkdsk from a command prompt and it will notify you if you have
any errors that need fixing. Typing chkdsk will run in read-only mode, so it
won't do any harm.

Running chkdsk after a crash isn't a bad idea, as some file/file system
corruption may occur as a result of the crash.

It would depend on the nature of the BSOD. What is the Stop Error
message?


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


void.no.spam.com@gmail.com wrote:
> If you get a BSOD, is it necessary to do a chkdsk? What would be the
> consequence of not doing a chkdsk?