Window Server 2008 NFS BSOD
Michael Russell
for NFS questions.
I have 2 windows server 2008 boxes setup with clustering and NFS. Both of
them blue screen an reboot constantly. I installed debug tools and the 2008
symbols to look at the memory dump. Anyone know if there is an issue with
NFS and 2008? I have included the debugger information below.
--
Michael
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: .sympath
SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
Kernel base = 0x8183c000 PsLoadedModuleList = 0x81953c70
Debug session time: Fri Apr 25 12:25:47.640 2008 (GMT-5)
System Uptime: 0 days 0:34:44.101
Loading Kernel Symbols
.................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, 110b, a250409, 9e2598e0}
Probably caused by : nfssvr.sys ( nfssvr!NfsNegSidCacheCleanup+28 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad
IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000110b, (reserved)
Arg3: 0a250409, Memory contents of the pool block
Arg4: 9e2598e0, Address of the block of pool being deallocated
Debugging Details:
------------------
POOL_ADDRESS: 9e2598e0 Paged pool
FREED_POOL_TAG: NfsC
BUGCHECK_STR: 0xc2_7_NfsC
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8192a00c to 81909163
STACK_TEXT:
922d2ca4 8192a00c 000000c2 00000007 0000110b nt!KeBugCheckEx+0x1e
922d2d18 99c27fd2 9e2598e0 4373664e 00000000 nt!ExFreePoolWithTag+0x17f
922d2d2c 99c294ac 8dee0174 00000000 8c62ac60 nfssvr!NfsNegSidCacheCleanup+0x28
922d2d7c 81a11a1c 8dedd0e0 fdc2c056 00000000 nfssvr!NfsCacheThread+0x2b2
922d2dc0 8186aa3e 99c291fa 8dedd0e0 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nfssvr!NfsNegSidCacheCleanup+28
99c27fd2 3936 cmp dword ptr [esi],esi
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nfssvr!NfsNegSidCacheCleanup+28
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nfssvr
IMAGE_NAME: nfssvr.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47918ac8
FAILURE_BUCKET_ID: 0xc2_7_NfsC_nfssvr!NfsNegSidCacheCleanup+28
BUCKET_ID: 0xc2_7_NfsC_nfssvr!NfsNegSidCacheCleanup+28
Followup: MachineOwner
---------
0: kd> lmvm nfssvr
start end module name
99c03000 99c80000 nfssvr (pdb symbols) .sympath
SRV\nfssvr.pdb\F32A1C9B8B2F4B4AA91ECEAF0F8FEFF41\nfssvr.pdb
Loaded symbol image file: nfssvr.sys
Image path: \SystemRoot\system32\drivers\nfssvr.sys
Image name: nfssvr.sys
Timestamp: Fri Jan 18 23:29:44 2008 (47918AC8)
CheckSum: 00079DF4
ImageSize: 0007D000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
0: kd> lmvm nfssvr
start end module name
99c03000 99c80000 nfssvr (pdb symbols) .sympath
SRV\nfssvr.pdb\F32A1C9B8B2F4B4AA91ECEAF0F8FEFF41\nfssvr.pdb
Loaded symbol image file: nfssvr.sys
Image path: \SystemRoot\system32\drivers\nfssvr.sys
Image name: nfssvr.sys
Timestamp: Fri Jan 18 23:29:44 2008 (47918AC8)
CheckSum: 00079DF4
ImageSize: 0007D000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
Jian-Ping Zhu [MSFT]
Thank you for your post.
Blue screen issue is generally complicated to troubleshoot. We need to
debug the memory dump files to solidly locate the root cause.
Unfortunately, debugging is beyond what we can do in the newsgroups because
of the nature of newsgroup support. A support call to our product service
team is needed for the debugging service.
Therefore, I'd like to recommend that you contact Microsoft Customer
Support Service (CSS)
For more information on available CSS services, please click here:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607