Windows 2000 reboots when copying files across network

[Guest]

I'm trying to network a desktop machine (Windows 2000 Pro) and a Windows XP
Pro laptop...I've tried a wireless network setup (Netgear router & wireless
PC card) and tried direct Ethernet cabling (to eliminate the wireless network
as a potential source of trouble).

In both cases I have the same problem: Windows 2000 *always* reboots within
a couple seconds after initiating the copying of more than 1 or 2 files from
the Win XP laptop. (When *not* on the network, the Windows 2000 machine is
rock solid when copying files among its own local drives.)

I've tried:
* Updated all my virus scanning software, and scanned both machines.
* Updated drivers for my Ethernet cards
* Installed the recent Win 2000 Service Pack 4 Update Rollup 1
* Updated firmware in the router.
* Copying different sets of files from the laptop.

Notes:
* Though I have Windows 2000 set to show a blue-screen message instead of
auto-rebooting, I never see a blue screen...it just flat out reboots.
* The event log doesn't reveal anything--nothing of interest gets recorded
there related to the reboot.
* No file is written to \Winnt\Minidump.

What are my options...except to pull out my two remaining hairs?<g>

 

[Dave Patrick]

If no BSOD's occur (Event ID: 1001 Source: Save Dump), then it may be a
power problem. I would look at a possible faulty (or undersized) pc power
supply, UPS, bad battery, or the circuit feeding the outlet that the pc is
plugged into.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| I'm trying to network a desktop machine (Windows 2000 Pro) and a Windows
XP
| Pro laptop...I've tried a wireless network setup (Netgear router &
wireless
| PC card) and tried direct Ethernet cabling (to eliminate the wireless
network
| as a potential source of trouble).
|
| In both cases I have the same problem: Windows 2000 *always* reboots
within
| a couple seconds after initiating the copying of more than 1 or 2 files
from
| the Win XP laptop. (When *not* on the network, the Windows 2000 machine is
| rock solid when copying files among its own local drives.)
|
| I've tried:
| * Updated all my virus scanning software, and scanned both machines.
| * Updated drivers for my Ethernet cards
| * Installed the recent Win 2000 Service Pack 4 Update Rollup 1
| * Updated firmware in the router.
| * Copying different sets of files from the laptop.
|
| Notes:
| * Though I have Windows 2000 set to show a blue-screen message instead of
| auto-rebooting, I never see a blue screen...it just flat out reboots.
| * The event log doesn't reveal anything--nothing of interest gets recorded
| there related to the reboot.
| * No file is written to \Winnt\Minidump.
|
| What are my options...except to pull out my two remaining hairs?<g>
|
|
|

 

[Guest]

Another note...

After each reboot, Windows 2000 scans the hard drive to which the files were
being copied, and finds usually up to a dozen or so orphaned files. But
oddly, there is *never* any empty directory in the drive's directory tree.

This makes me wonder if the problem always occurs upon accessing hard drive
directory services (the shell?) during the file copy process...that is,
several files have been written to the disk, and attempting to update the
disk directory during the copy process causes the reboot.

Anyway, just a hunch, but I don't know how to go further to diagnose it.

Thanks for any ideas.

 

[Guest]

If no BSOD's occur (Event ID: 1001 Source: Save Dump), then it may be a
power problem. I would look at a possible faulty (or undersized) pc power
supply, UPS, bad battery, or the circuit feeding the outlet that the pc is
plugged into.

Thanks Dave,

Since I'm grasping for straws by now I'll check out your suggestions. But
I'm doubtful power is an issue. If it were, I'd be having problems during
other writes to the hard drive, not just during writes of data that has come
across the network. And, the pattern of failure would not be so
consistent--Windows 2000 always restarts after a few files have been copied
to the target local drive, and before any of them can be recorded into the
directory of that drive.

It has to be something else, like a problem accessing shell services to
write the directory, etc. But I don't know how to diagnose the problem.

 

[Dave Patrick]

A long shot here but you may be led astray in the absence of anything new in
the system log. To test if the system.evt is corrupt restart the machine and
then verify that the 'system' log of Event Viewer logs at least the event
6005 source 'eventlog'

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Thanks Dave,
|
| Since I'm grasping for straws by now I'll check out your suggestions. But
| I'm doubtful power is an issue. If it were, I'd be having problems during
| other writes to the hard drive, not just during writes of data that has
come
| across the network. And, the pattern of failure would not be so
| consistent--Windows 2000 always restarts after a few files have been
copied
| to the target local drive, and before any of them can be recorded into the
| directory of that drive.
|
| It has to be something else, like a problem accessing shell services to
| write the directory, etc. But I don't know how to diagnose the problem.