Windows XP crash

[CardinalChris]

My wife used my laptop to copy a bunch of pictures to a new digital photo frame. She completed the download, copied the pictures and turned the computer off. After it had shut down she unplugged the usb cable that attached the computer to the frame.

I tried to turn it on today and it froze. Kaspersky was attmepting to run a scan, but locked the system up. I rebooted and get this message



A problem had been detected and windows has been shut down to prevent damage to your computer.

If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Disable or uninstall and anti-virus, disk defragmentation or backup utilities. Check your hard drive configuration, and check for any updated drivers. Run CHKDSK /F to check for hard drive corruption, and then restart your computer.

Technical information:

*** STOP: 0X00000024 (0X00190203, 0X8A82F828, 0Xc0000102, 0X00000000)

The problem is that in no mode (safe modes, last working configuration or normal) will the computer get to anywhere that I can do anything listed in the steps this message has outlined. How can I get the computer to boot up? Anybody gone through this before? I had this message once before, but simply restarted and it was fine. I wonder if the Kaspersky scan has something to do with it or if it is the photo frame.

[CardinalChris]

Could this be an open registry key from the kaspersky? If so how can I shut it down to start the computer up enough to the point that XP will boot and I can troubleshoot it?

[SRTDodge05]

Sounds like something was scanning your pictures and when she turned the pc off it didnt finish the scan.

[CardinalChris]

Any ideas how to fix it?

[SRTDodge05]

Does that message come up everytime you turn your pc on?

[CardinalChris]

yes, regardless of what mode I attempt to boot in.

[Gorganzola]

Use your Windows XP CD and boot to the recovery console. Then run chkdsk /p to fix the file system corruption. If you are still having issues then you need to do a manual system restore from the recovery console. http://support.microsoft.com/kb/307545/en-us

[SRTDodge05]

Defrag and run checkdisk and that should clean things up.

[Gorganzola]

Please don't defrag before you run chkdsk. PLEASE!!!!

Originally Posted by SRTDodge05

Defrag and run checkdisk and that should clean things up.

[SRTDodge05]

Originally Posted by Gorganzola

Please don't defrag before you run chkdsk. PLEASE!!!!

Why is that?

[ctal]

Assuming your wife turned it off properly, via the Start button and not the hardware power button, my instinct is that it has nothing to do with either Kaspersky or the photo thing. A key thing that you said is that you saw the problem happen once before. Go ahead and try the recovery console suggestions, but if they don't get you anywhere I would consider the possibility that it is a hardware problem (hard drive or its controller, graphics card or circuit, etc.), which has gotten worse since you first saw the symptom and were able to recover by rebooting.

The next step I would do would be to see if the machine can boot from bootable media, preferably a BartPE CD -- http://www.nu2.nu/pebuilder/
(essentially a stripped down version of Windows bootable from a CD), or if it is not convenient for you to prepare one, then from Linux on a bootable CD (Ubuntu, Puppy Linux, many others as well which can be booted from CD), or even a dos diskette. You could then use that OS, assuming it boots, to get some idea of the functionality of the different parts of the machine. Or if it doesn't boot, it would mean that the problem is not related to your Windows installation, and may be due to hardware.

Another thing to be aware of is that chkdsk, as run from a command line prompt such as in the Recovery Console (as opposed to running it from Windows/My Computer) tends to indicate errors when there really aren't any (I've read that and seen that).

Finally, I wouldn't take the error message's suggestions too literally -- like many Windows error messages, they could be completely off the mark.
-- Al

[Gorganzola]

While NTFS is a journaling file system, moving the bits on the hard drive around further for the sole purpose of organization risks further corruption of files. CHKDSK is designed to look for errors in the filesystem and to some extent on the physical hard disk.

My request to not run defrag before chkdsk is soley in cases like this where the disk is currently in error. Under normal circumstances it is fine to run defrag whenever.

Originally Posted by SRTDodge05

Why is that?

[Gorganzola]

Link please.

Originally Posted by ctal

Another thing to be aware of is that chkdsk, as run from a command line prompt such as in the Recovery Console (as opposed to running it from Windows/My Computer) tends to indicate errors when there really aren't any (I've read that and seen that).

[ctal]

Originally Posted by Gorganzola

Link please.

Annoyances.org - Question about 'Prevent file corruption problems' (Windows XP Discussion Forum)
(Note particularly the posts of 1/7/03, 12/22/04, and 2/23/06, among many others).

Chkdsk Finds Incorrect Security IDs After You Restore or Copy a Lot of Data

"CHKDSK detected minor inconsistencies" error message in Windows 2000 and in Windows NT

(These two kb's are claimed by some to apply to XP, in addition to W2K which is addressed in the articles).

A Google search of Usenet Newsgroups will turn up additional posts along these lines.

Regards,
-- Al

[Gorganzola]

Thanks Al.

NTFS file system glitch

Interesting read that bit.