Copying files across the LAN = BSOD

[Kerry Brown]

Post the details of the BSOD. Also post the details of any associated errors
in the event logs.

 

[marco]

Copying large files TO or FROM my Vista Ultimate PC to other PC's across the
LAN causes
my PC to Blue Screen after a few minutes. I get the same result if I disable
the Wired LAN and enable the
wireless instead. I've tried it from a Vista laptop, an XP PC and and NT4
pc. Same result every time.

Can anyone suggest how I might troubleshoot this?

 

[Kerry Brown]

The most common cause of that error is bad RAM. It can also be caused by a
bad driver. What network card are you using and do you have the latest
drivers for it? Are there any errors in the event logs?

http://windowshelp.microsoft.com/Windows/en-US/Help/1bcadb98-7479-4fad-82dd-7f30a80dfa4f1033.mspx

Please post the Source: and the EventID: from any errors that occurred
around the same time as the BSOD.

 

[marco]

Thanks for the attention

Well I don't know what to say. I'm copying files and then - Blam! the system
re-boots. After the system re-starts nothing appears in the event log before
the crash but afterwards I can find "The computer has rebooted from a bug
check. The bugcheck was: 0x0000007f (0x0000000d, 0x00000000, 0x00000000,
0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP."

It doesn't mean anything to me.

 

[Richard Urban]

http://support.microsoft.com/kb/137539

--


Regards,

Richard Urban MVP
Microsoft Windows Shell/User

 

[marco]

Well it only happens when copying across the network so I'd be surprised if
ram were the problem. As for network drivers - the same happens whether I
use the wireless adapter or the on board Marvell Yukon 88E8053 PCI-E Gigabit
Ethernet Controller so it's unlikely that the specific adapter drivers both
cause the same fault. But what do I know? The event log only mentions the
bug check stated in my previous post.

But I thank you for taking the time to think about this

 

[Kerry Brown]

The 0x0000000D in the first parameter means that an application may be
involved. Here's from the documentation for that STOP error.

0x0000000D - An exception not covered by some other exception; a protection
fault that pertains to access violations for applications

http://msdn2.microsoft.com/en-us/library/ms795478.aspx

What firewall, AV, antispyware and other programs that may intercept network
communications are you running? Bad RAM can cause all sorts of seemingly
unrelated problems. It wouldn't hurt to test the RAM. It's easy and free.

http://www.memtest.org/

Make sure you run it for several hours at least. One error means something
is wrong.