Bug ??? XP crashes when copying large file to network

[tcm1998]

Hi, first of all, I'm new here (just registered my copy and found out about this forum)

I'm not sure, but it seems I found a bug. When I copy a full DVD image file (about 4.5 GB) to my laptop over wireless lan (not mapped the drive, just using 'my networkplaces') total commander causes win XP to crash (BSOD).

Doing the same in explorer wasn't a problem. After I completed the copy from explorer, I tried again with the same result.

Anyone daring enough to confirm ?

[ghisler(Author)]

This is certainly not normal. What module name is shown in the BSOD?

[tcm1998]

Since I have windows automaticaly reboot after such a crash I had to reproduce the problem first, unfortunately that was far TOO easy.
It's wasn't a BSOD like I was used seeing in NT4, and I don't think there's much usefull info on it. Anyway, here's (part of) the text:

A problem has been detected and Windows has been shut down to prevent damage to your computer.
Then a lot of blablabla
And finally:
Techical Information:
***STOP: 0x0000008E (0xC0000005,0x00000000,0xEF0B7AB8,0x00000000)

Being a programmer myself, the only (far too well) known number there is 0xC0000005 (memory exception).
Even when I setup drwatson the result was the same, no log, no dump NOTHING. I guess the security of XP overrides all.

I wonder if I'm really the only one who has this problem.

[sqa_wizard]

The mentioned address looks more like a defect memory module.

I had the same problem some time ago. It happens only if I work with large files (using the upper memory range).

You may use a memory checker tool just to be sure ...

[ghisler(Author)]

You should check what Microsoft writes about it:
msdn link

To me it looks like a faulty network driver not liking the buffer size used by Total Commander. You should try to activate compatibility mode for copying to the network, by specifiying a backslash (and/or the network drive letter) in Configuration - Copy/Delete - use compatibility mode for these drives.