HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
cancel
Showing results for 
Search instead for 
Did you mean: 

BSOD on BL460C G1

 
Jeff Carnes
Occasional Visitor

BSOD on BL460C G1

BL460c G1 server (Windows Server 2003 x64 SP2) is randomly rebooting with BSOD or BSOD will pop up when the server is restarted. PSP 8.25 is installed, BIOS, drivers and firmware as well as Microsoft patches are all up to date.


Here is the memory dump from the most recent BSOD, any help would be greatly appreciated.

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffadcbc88ea70, The address that the exception occurred at
Arg3: fffffadcb967e760, Exception Record Address
Arg4: fffffadcb967e170, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
Npfs!NpReadDataQueue+b0
fffffadc`bc88ea70 418b4620 mov eax,dword ptr [r14+20h]

EXCEPTION_RECORD: fffffadcb967e760 -- (.exr 0xfffffadcb967e760)
ExceptionAddress: fffffadcbc88ea70 (Npfs!NpReadDataQueue+0x00000000000000b0)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000020
Attempt to read from address 0000000000000020

CONTEXT: fffffadcb967e170 -- (.cxr 0xfffffadcb967e170)
rax=0000000000000001 rbx=fffffa8008248578 rcx=fffffadcb967ea50
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffffadcbc88ea70 rsp=fffffadcb967e980 rbp=fffffa8008248578
r8=0000000000000000 r9=00000000000010b8 r10=00000000000010b8
r11=0000000000000003 r12=fffffadcdd19cf60 r13=fffffadcb967eac0
r14=0000000000000000 r15=fffffa800a7ad110
iopl=0 nv up ei pl nz ac po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010217
Npfs!NpReadDataQueue+0xb0:
fffffadc`bc88ea70 418b4620 mov eax,dword ptr [r14+20h] ds:002b:00000000`00000020=????????
Resetting default scope

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000020

READ_ADDRESS: 0000000000000020

FOLLOWUP_IP:
Npfs!NpReadDataQueue+b0
fffffadc`bc88ea70 418b4620 mov eax,dword ptr [r14+20h]

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from fffffadcbc88d555 to fffffadcbc88ea70

STACK_TEXT:
fffffadc`b967e980 fffffadc`bc88d555 : fffffadc`b967ea50 fffffa80`08248578 fffffadc`dbe2b000 00000000`00000000 : Npfs!NpReadDataQueue+0xb0
fffffadc`b967ea00 fffffadc`bc88c1cc : fffffadc`dd19cf60 fffffadc`dd19c530 00000000`00000000 fffffadc`de4a4d60 : Npfs!NpInternalRead+0x205
fffffadc`b967eaa0 fffffadc`bc88bf66 : fffffadc`b967eae0 fffffadc`dd19c520 00000000`00000000 fffffadc`dd19cf60 : Npfs!NpCommonFileSystemControl+0x20c
fffffadc`b967eae0 fffffadc`bb1fc7c5 : 00000000`00000000 fffffadc`dd19c520 fffffadc`dd19c520 00000000`00000001 : Npfs!NpFsdFileSystemControl+0x26
fffffadc`b967eb10 fffffadc`bb1888f7 : fffffadc`dd19c520 fffffadc`dd19c520 fffffadc`bb187000 00000000`00000000 : srv!SrvSmbReadAndX+0xc6b
fffffadc`b967ec40 fffffadc`bb188853 : fffffadc`dd19c520 fffffadc`dd19c520 fffffadc`dadaec70 fffffadc`dcff4500 : srv!SrvProcessSmb+0x19f
fffffadc`b967eca0 fffffadc`bb1e20f2 : 00000000`000001cf fffffadc`dd6df360 00000000`0000000a 00000000`0000000a : srv!SrvRestartReceive+0xca
fffffadc`b967ed10 fffff800`0124a972 : fffffadc`d8c32040 00000000`00000080 fffffadc`d8c32040 fffff800`011b4500 : srv!WorkerThread+0x144
fffffadc`b967ed70 fffff800`01020226 : fffff800`011b0180 fffffadc`d8c32040 fffff800`011b4500 00000000`00000001 : nt!PspSystemThreadStartup+0x3e
fffffadc`b967edd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: Npfs!NpReadDataQueue+b0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Npfs

IMAGE_NAME: Npfs.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 45d692d3

STACK_COMMAND: .cxr 0xfffffadcb967e170 ; kb

FAILURE_BUCKET_ID: X64_0x7E_Npfs!NpReadDataQueue+b0

BUCKET_ID: X64_0x7E_Npfs!NpReadDataQueue+b0

Followup: MachineOwner
1 REPLY
WFHC-WI
Honored Contributor

Re: BSOD on BL460C G1

Hi Jeff,

Make sure your Power Management Controller software is up to date (3.4c as of this moment), there are numerous advisories about this component.
Next run diagnostics on the server via the SmartStart CD, you may have faulty hardware.

Good luck!