Puzzler: saving file across network causes blue screen

OK, here's a puzzler. I only had about 15 minutes to play with this the other day, but it's been nagging at me ever since. Hope to get back to this problem early next week so I thought I would use the collective wisdow of the Internet to glean an answer

Small workgroup with two XP laptops. All shared data is stored in the public share on machine A.

When a user on Machine B connects to the share and opens a WordPerfect Document on Machine A it opens fine. However, when the user on Machine B SAVES the document, Machine A crashes with a blue screen of

BAD_POOL_HEADER.

However, a user on machine B can open and save Microsoft Word documents without incident.

Machine A and B are using WordPerfect 12---both programs are completed updated.

Machine A and B are using Word 2003---both programs are completed updated.

Both machines have all Windows Updates and have all driver updates.

Otherwise, all machines are stable. Event Viewer shows nothing but the afforementioned Bad Pool Header (error code 19)

My initial reaction was bad driver, but the fact it crashes with Wordperfect but not Word is very odd to me. Machine B can also print to a shared printer on Machine A, we have a fairly stable network or it would be crashing for that to.

Windows shares should be program agnostic and not care whether it is Word or Wordperfect accessing a file since networking occurs below the application layer (OSI model).

So, any thoughts? If it weren't for the Wordperfect Word issue, I'd say bad network card, but the software angle throws a quirk in--I wish I'd have thought to simply copy and drag a file from A and back to A just to see if the overwrite would cause a crash but I ran out of time....

Dang, I wish I'd had more time to play with this issue.

 

Were there any error parameters with the stop code?

There's a catch-all page on MSDN that covers Bug Check 0x19: BAD_POOL_HEADER; unfortunately, it covers a lot of ground, and the error parameters should give more specificity.

From what I saw with a quickie google, this sort of error covers many different things, but typically appears to be a driver problem. Are the network-related drivers on both machines all up-to-date?

 

Both machines are up to date with most recently MANUFACTURER supplied network card drivers--but it is worth noting that the drivers from the manufacturer date back to 2007. I didn't have enough time to track down the network card chipset so their may be an OEM driver I can get. Windows Update did not have a more recent driver.

Driver was my original idea, too, but the WordPerfect v. Word issue muddies the water.


Bad Pool Header codes
There were additional codes in event viewer but I didn't write them down...I was heading out the door when the problem was presented...it was one of those things where I went to fix one thing, and they said "That was great. We've been having issues with that for months...since you're here, we have this other issue...could you take a look?

Only had time to take a quick perusal. I will take a look at that link and see if anything jogs the memory.