Error during directory enumeration

[K C]

Hi all,

Something's wrong with my system, it keeps rebooting. I get the blue
screen of death but it flashes by too quickly and I can't read it. It
starts up XP ... about 2 seconds into the startup the screen goes
black, then flashes blue and then it reboots.

I tried booting up with a windows XP CD, get into "Recover" mode and
it starts up a windows instance. I have 2 physical drives and 7
logicals on them. The strange thing is, I'm not sure where my XP
should have been. Right now in recover mode I have a C,E,F,G on one.
And a D,H,I on the other. The windows is starting off "C" in recover
mode. But my Documents and settings etc, aren't there so I'm assuming
that my XP is on "D". When I try to look at "D" it says "An error
occurred during directory enumeration".

When I try chkdsk'ing "D", it says "The coume appears to contain one
of more unrecoverable problems".

The thing is that XP starts up a little, it displays a bunch of
drivers and then stops after Mup.sys shows up, blacks out and reboots.

I can't touch anything on the "C" drive as it says "Access Denied".
And I can't get to the "D" drive due to the enumeration error.

Assuming my XP install is on "D", if I booted up off "D" normally,
would it appear as a "C"???

Some of the stuff I read up on the discussion groups indicate it could
be a corrupt registry.. or just corrupt sectors on the drive.

All this happened when my machine spontaneously rebooted during a
thunderstorm lastnight. I have a damn surge protector that's probably
a piece of garbage as it didn't protect anything.

Help!!! Any advice will be greatly appreciated!

Thanks,

Kevin

 

[Will Denny]

Hi

Right click on My Computer, select Properties and then the Advanced tab.
Click on Settings under 'Startup and Recovery' and then uncheck
'Automatically restart'. Next time your PC tries to restart you see a Blue
Screen. Could you please post the Stop Code that accompanies that BSOD?
With that your problem could be isolated.

--

Will Denny
MS-MVP Windows - Shell/User
Please reply to the News Groups


| Hi all,
|
| Something's wrong with my system, it keeps rebooting. I get the blue
| screen of death but it flashes by too quickly and I can't read it. It
| starts up XP ... about 2 seconds into the startup the screen goes
| black, then flashes blue and then it reboots.
|
| I tried booting up with a windows XP CD, get into "Recover" mode and
| it starts up a windows instance. I have 2 physical drives and 7
| logicals on them. The strange thing is, I'm not sure where my XP
| should have been. Right now in recover mode I have a C,E,F,G on one.
| And a D,H,I on the other. The windows is starting off "C" in recover
| mode. But my Documents and settings etc, aren't there so I'm assuming
| that my XP is on "D". When I try to look at "D" it says "An error
| occurred during directory enumeration".
|
| When I try chkdsk'ing "D", it says "The coume appears to contain one
| of more unrecoverable problems".
|
| The thing is that XP starts up a little, it displays a bunch of
| drivers and then stops after Mup.sys shows up, blacks out and reboots.
|
| I can't touch anything on the "C" drive as it says "Access Denied".
| And I can't get to the "D" drive due to the enumeration error.
|
| Assuming my XP install is on "D", if I booted up off "D" normally,
| would it appear as a "C"???
|
| Some of the stuff I read up on the discussion groups indicate it could
| be a corrupt registry.. or just corrupt sectors on the drive.
|
| All this happened when my machine spontaneously rebooted during a
| thunderstorm lastnight. I have a damn surge protector that's probably
| a piece of garbage as it didn't protect anything.
|
| Help!!! Any advice will be greatly appreciated!
|
| Thanks,
|
| Kevin

 

[Malke]

Hi

Right click on My Computer, select Properties and then the Advanced
tab. Click on Settings under 'Startup and Recovery' and then uncheck
'Automatically restart'. Next time your PC tries to restart you see a
Blue
Screen. Could you please post the Stop Code that accompanies that
BSOD? With that your problem could be isolated.

In addition to what Will suggested, get a diagnostic hard drive utility
from the drive mftr.'s website. You'll make a bootable floppy - boot
with this and do a full diagnostic test on your drive(s). If you get
any errors, replace the drive(s). If the drive(s) test OK, then test
your RAM with Memtest86 from www.memtest86.com.

Malke

 

[Agent327]

Start the Recovery console or..
Start the computer with the boot disks or Windows CDROM
After the Welcome to Setup dialog box appears, press R to repair, and then
press C to start Recovery console.
Choose install Windows and log on as Administrator.

At the command prompt type "disable Mup.sys"

"MUP stands for "Multiple UNC Provider" which assists Windows in locating
resources when more than one redirector is on a machine such as "Microsoft
Client for Microsoft Networks" and the "Novell Client for Novell Netware".
When a connection to a server is requested it does not know if the request
is to a Novell server or an NT server. It will start looking for the server
with the primary protocol on the primary requestor and then continue looking
for the server on each protocol bound to each redirector until the server is
found."

Restart the computer and all should be well.

 

[w_tom]

Start by first collecting basic facts. Never fix the
software (Recovery) without first confirming good hardware.

Boot from your CD and read information in the system's event
logs. BSOD (blue screen..) information is stored there for
historical reference. IOW if system was getting more
troublesome, that history is in the event log. See Windows
HELP if you don't know where system logs are located.

Also look at the Device Manager. Is all hardware and
drivers OK?

Every minimally acceptable computer manufacturer provided a
complete set of comprehensive diagnostics. Download them and
execute. Diagnostics run without Windows. And that is
exactly what you want to know. If hardware is OK, then
diagnostics will work just fine without Windows
complications. Only when hardware is confirmed good would you
be ready to fix Windows.

What are hard drive filesystems? FAT or NTFS? If FAT, then
power loss could even delete files that were previously saved
on that FAT drive. Just another in a long list of reasons why
the NTFS filesystem was preferred.

If your hardware manufacturer was trash, then you must
download comprehensive diagnostics for each peripheral.
Another mentioned hard drive diagnostic and Memtest86 for
memory. Do same for motherboard, video controller, sound
card, etc.

In the meantime, a plug-in surge protector manufacturer does
not even claim to protect computers from typically destructive
transients. They claim protection from transients that do not
typically exist. Then they hope the naive will use word
association to claim surge protector and surge protection are
same. IOW plug-in protectors are only recommended using urban
myths.

The effective surge 'protector' connects a transient less
than 10 feet to single point earth ground - also called the
surge 'protection'. That type of protector is also called a
'whole house' protector. 'Whole house' protectors are
effective. Plug-in protectors can even provide a destructive
transient to find earth ground, destructively, via your
powered off computer. Correct. A plug-in protector can even
make it easier for transients to damage the adjacent computer.

Protection is about earthing. Surge protectors neither
claim to no stop, block, or absorb surges. Ineffective
protectors are quickly identified. 1) No dedicated connection
to earth ground AND 2) it avoids all mention of earthing. No
earth ground means no effective protection - as you might,
unfortunately, have learned the hard way.

 

[K C]

Hi

Right click on My Computer, select Properties and then the Advanced tab.
Click on Settings under 'Startup and Recovery' and then uncheck
'Automatically restart'. Next time your PC tries to restart you see a Blue
Screen. Could you please post the Stop Code that accompanies that BSOD?
With that your problem could be isolated.

--

Will Denny
MS-MVP Windows - Shell/User
Please reply to the News Groups

Will, the problem is I can't get into XP. I reinstalled XP on
another partition for now to see if I could get into the "D" drive.
It installed OK but I still can't get into the "D" drive. That one
partition is unreadable.

The strange thing is that disk (device) contains 3 logical partitions,
the other two are fine! So, I'm assuming the damage to the one is
fixable.

I can get it to boot up to the damaged "XP" image but it doesn't get
very far, I can't see the "My Computer" icon to make the change you
suggested.

Thanks,

Kevin

 

[K C]

Hi

Right click on My Computer, select Properties and then the Advanced tab.
Click on Settings under 'Startup and Recovery' and then uncheck
'Automatically restart'. Next time your PC tries to restart you see a Blue
Screen. Could you please post the Stop Code that accompanies that BSOD?
With that your problem could be isolated.

--

Will Denny
MS-MVP Windows - Shell/User
Please reply to the News Groups

Will, the problem is I can't get into XP. I reinstalled XP on
another partition for now to see if I could get into the "D" drive.
It installed OK but I still can't get into the "D" drive. That one
partition is unreadable.

The strange thing is that disk (device) contains 3 logical partitions,
the other two are fine! So, I'm assuming the damage to the one is
fixable.

I can get it to boot up to the damaged "XP" image but it doesn't get
very far, I can't see the "My Computer" icon to make the change you
suggested.

Thanks,

Kevin