Since earlier this year, I have been having trouble restarting after an apparently clean shutdown/power down. Some symptoms include occasional disk corruption (both drives) requiring CHKDSK on restart, occasional BIOS complaints on restart ("Memory size decrease" or something to that effect) that go away after I do an F10, similar aggravations.
The system is (apparently) reliable and stable while running; whatever is wrong happens only during a shutdown/power-down/restart sequence.
Yesterday, after another clean shutdown, I got the dreaded black screen with "Missing Operating System" message when I tried to restart. This was solid during multiple attempts to restart yesterday afternoon and evening.
This morning, when I tried to boot from the recovery CD, the system hung at the blue startup screen (after recognizing the CD). When it hung, the floppy drive light was stuck on (no floppy in the drive). The floppy hasn't worked, and I haven't used it, for years.
I removed the recovery CD and put it in the other DVD reader (I have two) and rebooted. This time, the system booted from the HD. It began running chkdsk on a memory stick inserted in one of the USB ports. I pulled the stick, chkdsk stopped, and the system booted to a clean and stable desktop.
Except ... it added an *extra* floppy drive. The system now reports *both* A: and B:, both floppy drives, when there is only one.
I'm running a full backup now, and typing this from a different machine.
Any ideas about what might be causing these failures? The power supply is a few months old. Am I looking at a motherboard issue? Is this related to the failed floppy drive, and if so, what should I do about it? The BIOS looks fine. I expected the "Missing Operating System" complaint to mean that I needed to run fixmbr (from the recovery CD), but then the OS loaded just fine (other than the apparently-corrupted thumbdrive). Surely a corrupted HD won't fix itself -- is this a hard drive spin-up timing issue?
BTW, based on comments I found on another site, I've turned off ctfmon (from MSOffice 2003). Some folks have reported that it causes problems during shutdown.
Finally, my problems began last winter when NAV2009 was attempting to nag me about my subscription expiring at the same time that Windows Update was in the middle of installing SP3 (I think!). Both happened overnight, and that was the first time that the system forced chkdsk to run on startup. At that time, the result was that I lost all my user information (Outlook express settings and data, Office registrations, etc.). I've been seeing these shutdown/powerdown problems since then. Could NAV2009 be doing something nasty during shutdown/powerdown? Oh, and yes, the NAV2009 full scan runs clean with no issues found.
I eagerly await any suggestions...
Edited by BrooklineTom, 09 June 2009 - 12:04 PM.