Help with blue Screen Dump file

[H2SO4]

No maleware or viruses. and since my reported blue screen i didn't had another one, but I'm being cautious so I'm interesting in prevention.
By the way, i didn't do the chkdsk /r or chkdsk C: /f that was suggested, only chkdsk, and it told me that i had no bad sectors. should i do chkdsk /r? (what does it mean anyway?).

As suggested previously, typing CHKDSK /? would show you what all the switches (options) do.

CHKDSK won't even look for bad sectors unless you use the /R option. That's a low-level reliability scan which causes every sector to have its current data moved, replaced by a known pattern (0123456789... or whatever), and then subsequently read back again. If "results out" don't match the pattern that was written, obviously the sector is unreliable - "bad" - and it gets added to an NTFS metadata structure which keeps track of such unreliable locations on the disk surface so they can be avoided in the future.

Many HDDs nowadays have their own similar sector remapping features built into the firmware, and since that's underneath the OS file system a disk may be suffering from progressive substrate degradation issues even though it's not picked up by software scans (disk SMART status can pick that up though).

 

[usasma]

chkdsk /r is for repair. I prefer it /f because I understand that it's more thorough (haven't researched it in years). But it takes longer to run, so some people don't use it because they don't see a need for the extra detail it provides.

The first rule of computer repair is "If it ain't broke, don't fix it!" Since it appears that everything is working OK for you, the best thing to do would be to sit back and wait. While waiting you can google for chkdsk and will have more information than you can shake a stick at!

Good luck!

 

[H2SO4]

chkdsk /r is for repair. I prefer it /f because I understand that it's more thorough (haven't researched it in years). But it takes longer to run, so some people don't use it because they don't see a need for the extra detail it provides.

/F is "fix it" - don't just run in read-only inspection mode, which is the default.

/R does everything that /F does, plus it adds a surface scan, which is why it can take hours or even days on exceptionally large volumes.

 

[roeelo]

/R does everything that /F does, plus it adds a surface scan, which is why it can take hours or even days on exceptionally large volumes.

Even days?????....
last night i tried to run chkdsk /F but it told me that i can't run it now and it will run automatic when vista will boot next time. (i closed the PC after that).
now, i still did'nt open the PC so it did'nt start the scan. so you are telling me that when i'll open the PC it will start scaning for so long time??
How can i cancel that before it'll start scaning? or should i let it scan it all, contrary to what usasma told me that i should just sit and let it be for now?
I appreciate the help...

 

[usasma]

There's no easy way to stop it, nor is there a reason to stop it.
And it's not going to hurt anything so just let it run.

Since you typed chkdsk /f it'll do the shorter scan (not the long scan for chkdsk /r).

 

[roeelo]

OK, thank you very much mate!
I'll update if there will be any news.
Have a great week both of you!

 

[roeelo]

OK guys, i tried all that you wrote me, and that's what i got:
"Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)"
I checked Y and restarted the PC, but the same message appears.
What can i do now?...

 

[roeelo]

OK guys, i tried what you've wrote me but i got this message:
"Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time Athe system restarts? (Y/N)".
I choose Y and restarted the PC, but the same message appears.
What can i do now?...

 

[usasma]

Choose N (for no) and restart the PC. This will skip the checking on the next reboot.

Chkdsk with the /'s cannot run if another process is using the file system. When Windows is running, it's using the filesystem - so you'll always get that message when trying to run it in Windows.

The actual chkdsk will run from a blue or a black screen before your system boots into Windows. Once it's booted into Windows everything has completed. You can view a report on what it did by searching for a Winlogon entry in the event viewer (at least it was this way in earlier versions of Windows).

 

[roeelo]

oh.... that's what exactly was... a black screen appears and i didn't know why my vista isn't loading so i restart the pc, and in the second time i shut it down....
did i do some damage because of that?...

 

[usasma]

It's possible that you could have damaged the file system this way.

To be sure, do this:
- boot into Windows
- run chkdsk /r and tell it to run on the next boot
- reboot the computer
- walk away from the computer and put your hands in your pockets
- should you need to go back to the computer, sit on your hands

Let it run, no matter how long it takes. Start it up before going to bed for the night and let it run all night while you sleep. Don't shut the computer off until it's back in Windows.

 

[roeelo]

OK, i'll do it this night.
two more qustions:
where do i find the resaults of the test, and should i run chkdsk /f or chkdsk /r?

 

[roeelo]

Someone?
Usama?...
H2S04?...

 

[The Cool Guy]

Run both of them to just be sure.

 

[H2SO4]

Someone?
Usama?...
H2S04?...

As Usasma said, run CHKDSK /R. (It's a superset of /F.)

You can find the results afterwards, when the machine has finished booting and you've logged on, in the "application" section of the event log - run EVENTVWR to get there. The source of the event you're looking for is Wininit, and the code will be 1001 from memory, though I'm a bit hazy on that last part.