If the"chmod -R 777 * " command is run on an NFS mounted file system from either Linux Redhat or HP-UX, the Windows Storage Server bugchecks with a STOP 0x7E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) with a c0000005 (Access Violation).

The issue occurs with Service Pack 2 installed, and the very latest NFS QFE 937042 for Windows Storage Server 2003 R2.

Nfssvr.sys 5.2.3790.4074 04-May-2007

KB 937042 "A socket file is shown as an FIFO file on a Windows Server 2003 R2-based computer that is running Microsoft Services for NFS"
Click here for the KB Article (http://support.microsoft.com/kb/937042/) .

Configuration

Microsoft Windows 2003, Service Pack 1 and Service Pack 2
Microsoft Windows 2003 Storage Server, Service Pack 1 and Service Pack 2
Microsoft Windows 2003 Storage Server R2, Service Pack 1 and Service Pack 2
HP ProLiant Storage Server (NAS)
HP StorageWorks All-in-One Storage System (AiO)
Microsoft Services for UNIX (SFU) version 3.5
HP ProLiant Storage Server Service Release version 6.20
HP ProLiant Storage Server Service Release version 6.40
Nfssvr.sys 5.2.3790.2930 04-May-2007 (KB 937042, Service Pack 1)
Nfssvr.sys 5.2.3790.4074 04-May-2007 (KB 937042, Service Pack 2)

Debug

Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible Product: Server, suite: Enterprise TerminalServer SingleUserTS StorageServer Built by: 3790.srv03_sp2_rtm.070216-1710 Kernel base = 0x80800000 PsLoadedModuleList = 0x808af9c8 Debug session time: Thu Aug 30 19:06:37.750 2007 (GMT+10) System Uptime: 0 days 1:25:31.828 Bugcheck code 0000007E Arguments c0000005 f57492b4 f5f7d8f8 f5f7d5f4 ExceptionAddress: f57492b4 (nfssvr!NfsGetIdForSid+0x00000074)    ExceptionCode: c0000005 (Access violation)   ExceptionFlags: 00000000 NumberParameters: 2    Parameter[0]: 00000000    Parameter[1]: 0c271134 Attempt to read from address 0c271134 ChildEBP RetAddr   f5f7d9f0 f5746f01 nfssvr!NfsGetIdForSid+0x74 f5f7db68 f57603e8 nfssvr!NfsGetOpenFileAttributes2+0x715 f5f7dcf8 f575edca nfssvr!NfsSetAttr+0xe2a f5f7dd50 f576df73 nfssvr!NfsInPacketInternal+0x970 f5f7dd64 f5f232fc nfssvr!NfsInPacket+0x19 f5f7ddac 80920833 rpcxdr!RxWorkThread+0x308 f5f7dddc 8083fe9f nt!PspSystemThreadStartup+0x2e 00000000 00000000 nt!KiThreadStartup+0x16 start    end        module name f5725000 f579c000   nfssvr     (pdb symbols)     Loaded symbol image file: nfssvr.sys     Image path: \SystemRoot\system32\DRIVERS\nfssvr.sys     Image name: nfssvr.sys     Timestamp:        Fri May 04 21:13:41 2007 (463B1565)     CheckSum:         0007D578     ImageSize:        00077000     Translations:     0000.04b0 0000.04e0 0409.04b0 0409.04e0

This issue is caused as a result of not detecting the completion of asynchronous I/O operations, and is documented in the following KB article:

KB 939767 Error message when an NFS client accesses a file on an NFS share in Windows Storage Server 2003 or in Windows Services for UNIX 3.5:
"Stop 0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)"
Click here for KB article 939767 (http://support.microsoft.com/kb/939767/) .

At present, there are hotifx updates for the following:

Windows Storage Server 2003
Nfssvr.sys 8.0.2254.19 449,024 18-Jul-2007

Windows Services for UNIX 3.5
Nfssvr.sys 8.0.2254.19 448,896 26-Jul-2007

Windows Storage Server 2003 R2
Nfssvr.sys 5.2.3790.4169 467,456 23-Oct-2007