G
Guest
For a few weeks now, my PC almost always takes 2 attempts to boot: the first,
it stops at Verifying DMI Pool (which I think means it can't see the HDD);
press Reset and it boots fine. For the first time last night, I got the
dreaded “ntoskrnl.exe missing or corruptâ€, which usually means death...
pressed reset and it came back!
Now, normally at this point I’d say it was the disk, for sure. However,
neither Scandisk, nor Event Viewer, nor Western Digital’s diagnostics show
any disk problems... I’m stumped. It's worrying because I KNOW that one day
I’ll press Reset and it won’t... :-(((
I thought it might be a corrupt BIOS, so took the battery out and re-did all
the settings – then it worked. But it usually does on the 2nd attempt, so I
don’t think this proves anything. I’ll find out tonight, maybe.
I also thought maybe the MBR might be corrupt, so I started a recover
console, and tried FIXMBR... but it told me my MBR was either non-standard or
corrupt, and gave me dire warnings about proceeding, so I didn’t. Now, if
it's corrupt, great – I've found the problem. But if it’s “non-standardâ€,
perhaps due to my booting off a SATA drive (boot is C:, the first of 4
partitions on the SATA drive) rather than the IDE controllers, I might screw
everything up.
So my official MS-related question is – do you think I’ll wreck everything
if I do FIXMBR?
Unofficial responses to any other likely cause of the problem will be very
welcome too!
Thanks
Roger
it stops at Verifying DMI Pool (which I think means it can't see the HDD);
press Reset and it boots fine. For the first time last night, I got the
dreaded “ntoskrnl.exe missing or corruptâ€, which usually means death...
pressed reset and it came back!
Now, normally at this point I’d say it was the disk, for sure. However,
neither Scandisk, nor Event Viewer, nor Western Digital’s diagnostics show
any disk problems... I’m stumped. It's worrying because I KNOW that one day
I’ll press Reset and it won’t... :-(((
I thought it might be a corrupt BIOS, so took the battery out and re-did all
the settings – then it worked. But it usually does on the 2nd attempt, so I
don’t think this proves anything. I’ll find out tonight, maybe.
I also thought maybe the MBR might be corrupt, so I started a recover
console, and tried FIXMBR... but it told me my MBR was either non-standard or
corrupt, and gave me dire warnings about proceeding, so I didn’t. Now, if
it's corrupt, great – I've found the problem. But if it’s “non-standardâ€,
perhaps due to my booting off a SATA drive (boot is C:, the first of 4
partitions on the SATA drive) rather than the IDE controllers, I might screw
everything up.
So my official MS-related question is – do you think I’ll wreck everything
if I do FIXMBR?
Unofficial responses to any other likely cause of the problem will be very
welcome too!
Thanks
Roger