Reboot during network file copy

  • Thread starter Thread starter George
  • Start date Start date
G

George

I'm looking for help to resolve PC auto reboot problem.

Configuration:
Hardware:
New PC: 2.6G Pentium 4, 256M Ram, 40G hard drive, realtek
8139 NIC
Software:
Windows XP home; Ran windows update and updated all
critical & drivers updates as of 12/1/03.
Microsoft office 2000 with updates thru SP3
Wordperfect 2000 with updates thru SP3
Norton Internet Security 2003 (with LiveUpdates)
pcAnywhere version 11 (with LiveUpdates)

Problem:
While performing a network copy of a folder (contains
multiple subfolders & files around 700M) to this PC; the
copy will begin but after 1 or 2 minutes of copying
files, the PC will automatically reboot.

This happened repeatedly whether I started copy from
target PC or from source PC.

On reboot you get "serious problem" message whether to
send info to Microsoft.

One of the times got the
BSOD "DRIVER_IRQL_NOT_LESS_OR_EQUAL"
There was a reference to VOLSNAP.SYS also.

Not having access to internet with this machine and not
really having any clue other than the reboot seems to
happen with fairly high input/output file transfer over
network, I removed the NIC card and replaced with a new
one and its driver. Hoping maybe that was the problem.
No luck.

I also "disabled" Norton Internet security, but still had
problem. I did not have time to try disable Norton
virusscan; so I don't know if that was causing problem.

Other possible important info.
Another identical PC (HW & loaded SW) does not exhibit
this reboot problem. I copied the same folder to it; no
problem.

Any help to diagnosis & resolve this problem would be
much appreciated. Thanks in advance for your help.

George
 
BSOD "DRIVER_IRQL_NOT_LESS_OR_EQUAL"
There was a reference to VOLSNAP.SYS also.
Click to expand...
I see:
http://www.aumha.org/win5/kb.htm Has:

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article, or see Windows
2000 Professional Resource Kit, p. 1539.)
Typically due to a bad driver, or faulty or incompatible hardware or
software. Use the General Troubleshooting of STOP Messages checklist above.
Technically, this error condition means that a kernel-mode process or driver
tried to access a memory location to which it did not have permission, or at
a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode
process can access only other processes that have an IRQL lower than, or
equal to, its own.)
a.. Troubleshooting "Stop 0x0A" Messages in Windows {KB 165863} Win NT,
Win 2000, Win XP
b.. Troubleshooting a Stop 0x0000000A Error in Windows XP {KB 314063} Win
XP
a.. Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors {KB 183169}
Win NT, Win 2000, Win XP
b.. During upgrade to Win XP {KB 311564} Win XP
c.. STOP 0x0000000A Error Message When You Change from AC Power to DC
Power {KB 316676} Win XP
d.. "Stop 0x0000000A" Error Message When You Fast Switch Between Users {KB
310918} Win XP
e.. While booting NT on same partition as Win 2000 or XP {KB 227301} Win
NT, Win 2000, Win XP
f.. Partial List of Driver Error Codes That the Driver Verifier Tool Uses
to Report Problems {KB 315252} Win XP
g.. Windows XP Restarts When You Try to Shut Down Your Computer {KB
311806}
h.. "Fatal System Error" When You Try to Use a Hewlett-Packard 5100C
ScanJet {KB 307129} Win XP (with Brother printer)
i.. Computer May Hang During a Heavy Load with an Ericsson HIS Modem {KB
319810} Win 2000, Win XP
j.. STOP 0x4E, STOP 0x1A, STOP 0x50, and STOP 0xA Errors Occur When You
Try to Start the Computer {KB 271955} Win NT 4.0 (corrupt physical RAM)

Good Luck,
Kent
 
Hi, George,

I am an engineer at Microsoft. As the first step in debugging this,
we'd like to gather a mini dump from your computer.

(1) Launch windows explorer (Click Start > Run... type explorer, click
OK)
(2) Right click "My Computer" > Properties
(3) Click the Advanced tab
(4) You will see "Startup and Recovery" at the bottom. Click Settings
(5) Within "System failure," you will see "Write debugging
information"
-- Select "Small memory dump (64KB)"
-- Type %SystemRoot%\Minidump
(6) Click OK to exit all dialog boxes

With this, every time your machine crashes, a small memory dump will
be written to a file at %SystemRoot%\Minidump. Please repeat what you
did and email us the Minidump file once your computer crashes
(reboots).

(Note: you may already have this Minidump file from you previous
reboots, if the above settings had been in effect before.)

Thanks,

minglei

(e-mail address removed)

P.S. This posting is provided "AS IS" with no warranties, and confers
no rights.
 
Back
Top