XP x64 BSOD Writing to Mapped Drive? [SOLVED]
I've been tracking this problem down for months on end but can't seem to find a cause, let alone a resolution.
I'm running XP x64 on a 2-processor Dell Workstation with a few mapped drives. I've been getting lots of blue screens, often in clumps. I'll get 2 one Tuesday, be fine for a week, and then get 6 the next Tuesday.
The minidump files include a bunch of different bug check strings and codes and a variety of "caused by" drivers. The bug check codes include 0x1000007E, 0xC2, 0x9C, 0x50, 0x3B, and others. I've attached a .zip of the last 10 minidumps. By far, the most common "caused by" is ntoskrnl.exe.
The recurring theme about these crashes is that they all seem to happen when I'm writing files to a mapped drive. It's hardly deterministic too. I wrote a batch script that writes a small text file to any one of my network drives, sleeps for a half second, and does it again. Sometimes, the script will write 100 times before crashing. Sometimes, it get through 8 iterations. I should point out that this is caused by any network drive, and it makes no difference whether or not the server is running Linux or Windows.
I've tried replacing the network card in the PC, thinking perhaps there was something funky going on there, to no avail. I've also done multi-day passes (Friday evening to Monday morning a few times) with Memtest86 with no errors.
Is there anyone out there who can give me some further insight? Appreciated.
I've been tracking this problem down for months on end but can't seem to find a cause, let alone a resolution.
I'm running XP x64 on a 2-processor Dell Workstation with a few mapped drives. I've been getting lots of blue screens, often in clumps. I'll get 2 one Tuesday, be fine for a week, and then get 6 the next Tuesday.
The minidump files include a bunch of different bug check strings and codes and a variety of "caused by" drivers. The bug check codes include 0x1000007E, 0xC2, 0x9C, 0x50, 0x3B, and others. I've attached a .zip of the last 10 minidumps. By far, the most common "caused by" is ntoskrnl.exe.
The recurring theme about these crashes is that they all seem to happen when I'm writing files to a mapped drive. It's hardly deterministic too. I wrote a batch script that writes a small text file to any one of my network drives, sleeps for a half second, and does it again. Sometimes, the script will write 100 times before crashing. Sometimes, it get through 8 iterations. I should point out that this is caused by any network drive, and it makes no difference whether or not the server is running Linux or Windows.
I've tried replacing the network card in the PC, thinking perhaps there was something funky going on there, to no avail. I've also done multi-day passes (Friday evening to Monday morning a few times) with Memtest86 with no errors.
Is there anyone out there who can give me some further insight? Appreciated.