BSOD STOP x50 errors when running Windows 2008. ExtremeZ-IP.exe may be referenced as the process victimized in the MEMORY.DMP file.
Update on Windows 2008 BSOD Stopx50 error.
A Microsoft hot fix addressing this issue and a knowledge base article have been published. They can be found at: http://support.microsoft.com/kb/965497
If you are running Windows 2008, Group Logic recommends you:
- Install ExtremeZ-IP Hot Fix 5.3.2x3 or a later version of ExtremeZ-IP
- Install the official Microsoft hot fix
Microsoft has found a problem processing the "exchange files" command which some applications use to swap out the "temporary file" with the original during a save operation. As far as we can tell, Microsoft Office for Mac (both 2004/2008) use this command in the particular way which causes the BSOD, while Adobe and Quark won't cause the condition.
While Microsoft is working the issue as a high priority from their side, we have released a code change to ExtremeZ-IP which has proven to work around the issue. ExtremeZ-IP uses NTFS File IDs internally to access files because the Macintosh client uses its own version of File IDs to open and access files (because they do not change when the file is moved). The problem seems to be triggered only when using a File ID based version of the command. The workaround for the problem involves ExtremeZ-IP first resolving the File ID to a full path and then using the path based version of the command. The performance hit for this change should be negligible since the ExchangeFile command is rarely issued (only on saves).
Other BSOD issues on 2008 are listed here: Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA