Blue Screen Error......

[John Morley]

Hi All,

On the advise of my antivirus vendor (Kaspersky), I ran 'chkdsk /f' on
my harddrive to correct a "corrupted" file problem. It appears that
chkdsk corrected some file "indexing" issues... Now, though, when I boot
the machine (Windows XP Pro SP3), I see the Windows 'splash screen' and
then the BSOD, followed by an automatic reboot.

I figured that I could repair my Windows installation using the original
installation CD, but when I select the Repair Console, it runs for a
short time and then abruptly terminates (no errors), without
(apparently) fixing anything. The other option, Setup Windows XP,
worries me because I'm afraid it will nuke all the existing application
info I have when it runs......

Isn't there a way to just fix the problem without a full blown
re-installation of Windows XP? Older Windows XP installers seemed to
give more options in this area (ie. "a previous Windows installation has
been detected, would you like to repair?")

Any advise to get my system running with a minimal amount of pain?

John

 

[Peter Foldes]

What does the BSOD say . Can you post the BSOD message that is shown

 

[Mark Adams]

Hi All,

On the advise of my antivirus vendor (Kaspersky), I ran 'chkdsk /f' on
my harddrive to correct a "corrupted" file problem. It appears that
chkdsk corrected some file "indexing" issues... Now, though, when I boot
the machine (Windows XP Pro SP3), I see the Windows 'splash screen' and
then the BSOD, followed by an automatic reboot.

I figured that I could repair my Windows installation using the original
installation CD, but when I select the Repair Console, it runs for a
short time and then abruptly terminates (no errors), without
(apparently) fixing anything. The other option, Setup Windows XP,
worries me because I'm afraid it will nuke all the existing application
info I have when it runs......

Isn't there a way to just fix the problem without a full blown
re-installation of Windows XP? Older Windows XP installers seemed to
give more options in this area (ie. "a previous Windows installation has
been detected, would you like to repair?")

Any advise to get my system running with a minimal amount of pain?

John

Reboot the machine and press F8 to bring up the boot menu. Is there an
option to disable restart on system failure? If so, use that and repost the
message.

 

[Daave]

Hi All,

On the advise of my antivirus vendor (Kaspersky), I ran 'chkdsk /f' on
my harddrive to correct a "corrupted" file problem.

What is the name of this corrupted file and what caused it to become
corrupted in the first place? If it was malware, what was the name of
the infection?

It appears that
chkdsk corrected some file "indexing" issues... Now, though, when I
boot the machine (Windows XP Pro SP3), I see the Windows 'splash
screen' and then the BSOD, followed by an automatic reboot.

I figured that I could repair my Windows installation using the
original installation CD, but when I select the Repair Console, it
runs for a short time and then abruptly terminates (no errors),
without (apparently) fixing anything.

That sounds like the Recovery Console. It requires active input from
you. Were you given specific instructions to run specific commands while
in RC? If not, don't use it.

The other option, Setup Windows
XP, worries me because I'm afraid it will nuke all the existing
application info I have when it runs......

If you choose to perform a Clean Install, then that is exactly what will
happen. However, if you decide to perform a Repair Install, everything
(programs and data) *should* remain intact. But it always best to back
everything up just in case.

Isn't there a way to just fix the problem without a full blown
re-installation of Windows XP?

Maybe. Then again, your system might be so compromised that the
"full-blown" Clean Install might be your best option.

Older Windows XP installers seemed to
give more options in this area (ie. "a previous Windows installation
has been detected, would you like to repair?")

XP gives you the same option; this is what we call a Repair Install.

Any advise to get my system running with a minimal amount of pain?

First, tell us everything you can about this particular problem. Answer
all my earlier questions:

What is the name of this corrupted file and what caused it to become
corrupted in the first place?

If it was malware, what was the name of the infection?

Also, you should copy your data right now to keep it safe. Do you have
access to an external hard drive? If you have questions, we can guide
you so that you may copy the data.

Finally, what kind of PC is this -- a desktop or a laptop? What is the
make and model number?

 

[Gerry]

John

You need to post the complete Stop Error report.

Disable automatic restart on system failure. This should help by
allowing time to write down the STOP code properly. Keep pressing the F8
key during Start-Up and select option - Disable automatic restart on
system failure. Do not re-enable automatic restart on system failure.

Do you have important data you need to recover. If yes you should do
this before attempting a repair. Do you have access to a second
computer?

What is the make and model of the problem computer? What is the make and
model of the second computer?

Recovery can be done without booting the computer but needs a second
computer to be available to carry out the operation. In essence the hard
drive is removed from the problem computer and is, either placed in the
second computer as a slave drive or is placed in an external cradle
connected to the second computer. Either way you bypass the damaged
operating system on the first computer and use the operating system of
the second computer to read and copy the data files to removable media
such as a CD.

--


Hope this helps.

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

 

[John Morley]

Hi All,

I was never able to find a menu where Disable Automatic Restart was an
option. The only options I had were Safe Mode, Last Known Good Config,
and Windows XP (normal)......

I didn't have any non-recoverable data on the disk, so I decided to play
with the Repair Console. After getting the C:\ prompt, I ran Chkdsk /f
and the utility found, ansd repaired, several issues. I then was able to
boot to Safe Mode with no issues. Next, I tried a 'Normal' boot, and all
is well, and the computer is now back to 100%.

I don't think the original corrupted file was a virus or malware thing,
rather I think it was a Kaspersky bug of some kind. They appear to know
about the issue, but don't seem to have a handle on an exit stategy.....

BTW, the BSOD error was Unmountable_Boot_Volume......

Thanks for the input!

John

 

[John A]

As a Kasperski user, I would like to know what version of Kasperski you are
using, and whether KAV or KIS.

Thanks

 

[Randem]

In that case you HD may be bad and a re-installation is a waste of time. SO
boot from a CD like the Linux System Rescue CD and run TESTDISK to see if
your drive is bad or download the testing tool from your drives
manufacturer.

Mind you that a drive going bad may report that it is good for the testing
software tries multiple times to re-read sectors and if just one read is
good then it may report that the sector is good but we know it is going to
go sooner or later so that makes it BAD! In that case replace your HD and be
done with it.

--
Randem Systems
Your Installation Specialist
The Top Inno Setup Script Generator
http://www.randem.com/innoscript.html
Find Out What Your VB Program is Really Doing
http://www.randem.com/rstools.html

 

[John Morley]

John,

It's Kaspersky Anti-Virus 6.0 for Windows Workstations.

John

 

[John Morley]

Hi,

That thought also occurred to me, so I bought a 2nd SATA drive and made
an image of the original drive using Western Digital Data Lifeguard
tools. I'm now running the new drive in the PC.

Thanks!

John

 

[Gerry]

John

You seemed to have solved your problem. Using chdsk is one of the
remedies suggested in KB 555302.

Unmountable Boot Volume
http://support.microsoft.com/kb/555302

Background information on Stop error code
http://msdn2.microsoft.com/en-us/library/ms797142.aspx

0x000000ED: UNMOUNTABLE_BOOT_VOLUME
The kernel mode I/O subsystem attempted to mount the boot volume and it
failed. This error also might occur during an upgrade to Win XP on
systems that use higher throughput ATA disks or controllers with
incorrect cabling. In some cases, your system might appear to work
normally after you restart.
Source: http://aumha.org/a/stop.htm

--


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