XP Pro PC reboots when directory renamed from other PC

[Guest]

I have two PC's (XP Pro SP2) which have been successfully networked using a
router.
I've recently reinstalled rebuilt the PCs disks, and all appeared well -
each PC seeing the workgroup and sharing files OK.
When I create a directory on the remote PC to the one I'm using, and then
rename it, the remote PC crashes right back to a warm start. Happens in
either direction. If the Windows dump file is "reported to Microsoft" it
suggests a "driver" problem, but absolutely no indication as to which driver.
Starting one PC in "Safe Mode + Networking" allows the remote PC to
create/rename directories, so I guess a driver could be the culprit.
I'm going back to square one re-installing incrementally until I have a win
or the problem recurrs - any feedback as to what to look for would be
appreciated.

 

[Nepatsfan]

I don't have a solid answer as to why you're having that problem
but here are a few suggestions on maybe finding out why it's
happening.

Look in Event Viewer in the System area to see if there are any
items listed around the time you have this problem. Start ->
Administrative Folder -> Event Viewer.

If by "the remote PC crashes right back to a warm start" you mean
that it reboots then you might want to change the way XP responds
to System Failures. Go to Start -> Control Panel and select
System. On the Advanced page Settings in the Startup and Recovery
section. Under System Failure uncheck the box next to
Automatically restart. Click OK twice. The next time this problem
occurs the message that appears may provide some clues as to what
exactly is happening. Note: Once you get this problem fixed put
the check back in that box.

If you follow these suggestion, post back with whatever new clues
you get.

Nepatsfan

 

[Guest]

Thanks -

Tried as you suggested. I disabled "Automatically Restart", and the blue
error screen said the shutdown was caused by a "BAD_POOL_HEADER", and
suggested I check installed hardware/software. Also gave a few Hex values
(Stop 0x00000019, . . .)

The event viewer didn't apear to show any obvious culprit

Gregor

 

[Malke]

Thanks -

Tried as you suggested. I disabled "Automatically Restart", and the
blue error screen said the shutdown was caused by a "BAD_POOL_HEADER",
and
suggested I check installed hardware/software. Also gave a few Hex
values (Stop 0x00000019, . . .)

The event viewer didn't apear to show any obvious culprit

Update the drivers on your network card on the machine with the problem.
If there are no updated drivers (get them from the device mftr.'s
website or the OEM's site if you have that sort of computer, not from
Windows Update), then uninstall the nic and try a different one.

Malke