Hi Ilya;

I've been away from DW for some time after switching my home network to Linux, but recently I have a need to run 1 machine in XP, so I installed ver 2.56.

This machine is an NFS client, connecting to the Linux server with Windows Services for Unix, and the name mapping service. Prior to installing DW the NFS connection was very fast and stable. It ran for several weeks with no problem. Immediately after DW was installed, the first time I attempted to map the server network drive in Windows Explorer, I got a BSOD-BAD_POOL_HEADER message. I rebooted and tried again with the same result.

Uninstalling DW solved the problem, and upon reinstalling it the BSOD returned again.

I have attached two of the minidump files for the BSODs.

I see that you are on vacation. This is not an urgent issue. Please enjoy your break and we can explore this further when you return to work.

Thanks
BZ

You have to send me minidump files zipped (that's the files you can find with your c:\windows\minidump folder.

Sorry, I thought I'd already attached them.

Good, I will check it out when I get back home.

The issue is not about dwall.sys, it's about rpcxdr.sys.

http://www.suacommunity.com/forum/tm.aspx?m=13396
http://www.eggheadcafe.com/software/aspnet...-in-rpcxdr.aspx

Thanks for looking into my problem, Ilya.

I got the hotfix that was referred to, and updated the rpcxdr.sys file to the current version. Everything tested ok.

I installed DW again, and tested. The BSOD reappeared. It seems that there is a problem with rpcxdr that doesn't like what DW does, and I'm not sure why. After uninstalling DW, the problem went away as before.

Is there a way to exclude rpcxdr (or make DW appear to be transparent to rpcxdr), and would that have any effect?

bz

The only way to find out what is wrong is to send you test drivers set as minidump gives no information about this compatibility issue. So, you need to mail me to support and I'll send you test set back.