ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Blue Screen; HP Proliant g9 380

 
Duahimanshu
Occasional Visitor

Blue Screen; HP Proliant g9 380

Hello Experts,

 

We have HP G9 server with windows server 2012 installed. 

we upgraded the RAM last year and last week blue screen started coming, then we removed the old memories and its workiring fine since last week saturday with the new memories. please find below the  dump files output  for your reference kindly let me know why it is happening? is there HDD issue?  

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffd001df8d7070, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff800fe9370eb, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 1

    Key  : Analysis.Elapsed.Sec
    Value: 1

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 66


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  9600.18505.amd64fre.winblue_ltsb.160930-0600

SYSTEM_MANUFACTURER:  HP

SYSTEM_PRODUCT_NAME:  ProLiant DL380 Gen9

SYSTEM_SKU:  719064-B21

BIOS_VENDOR:  HP

BIOS_VERSION:  P89

BIOS_DATE:  09/13/2016

BASEBOARD_MANUFACTURER:  HP

BASEBOARD_PRODUCT:  ProLiant DL380 Gen9

DUMP_TYPE:  2

BUGCHECK_P1: ffffd001df8d7070

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff800fe9370eb

WRITE_ADDRESS: GetUlongPtrFromAddress: unable to read from fffff8026fde7298
GetUlongPtrFromAddress: unable to read from fffff8026fde7520
 ffffd001df8d7070 

CURRENT_IRQL:  2

FAULTING_IP: 
USBXHCI!memcpy+2b
fffff800`fe9370eb 488941f8        mov     qword ptr [rcx-8],rax

CPU_COUNT: 18

CPU_MHZ: 95d

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3f

CPU_STEPPING: 2

CPU_MICROCODE: 6,3f,2,0 (F,M,S,R)  SIG: 38'00000000 (cache) 38'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT_SERVER

BUGCHECK_STR:  AV

PROCESS_NAME:  System

ANALYSIS_SESSION_HOST:  HIMANSHU_DUA

ANALYSIS_SESSION_TIME:  07-29-2019 09:19:15.0116

ANALYSIS_VERSION: 10.0.18914.1001 amd64fre

TRAP_FRAME:  fffff802714d9510 -- (.trap 0xfffff802714d9510)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=000000010400b200 rbx=0000000000000000 rcx=ffffd001df8d7078
rdx=00000ffe6636df90 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800fe9370eb rsp=fffff802714d96a8 rbp=0000000000000001
 r8=0000000000000008  r9=0000000000000000 r10=0000000000000040
r11=ffffd001df8d7070 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
USBXHCI!memcpy+0x2b:
fffff800`fe9370eb 488941f8        mov     qword ptr [rcx-8],rax ds:ffffd001`df8d7070=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8026fbe4ee9 to fffff8026fbd93a0

STACK_TEXT:  
fffff802`714d93c8 fffff802`6fbe4ee9 : 00000000`0000000a ffffd001`df8d7070 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff802`714d93d0 fffff802`6fbe373a : 00000000`00000001 ffffe000`45b0c890 00000000`00000000 ffffe000`43dfe2a0 : nt!KiBugCheckDispatch+0x69
fffff802`714d9510 fffff800`fe9370eb : fffff800`fe929e82 ffffe000`45b0c890 ffffe000`45b0c910 ffffe000`45ad1e90 : nt!KiPageFault+0x23a
fffff802`714d96a8 fffff800`fe929e82 : ffffe000`45b0c890 ffffe000`45b0c910 ffffe000`45ad1e90 fffff802`714d97d0 : USBXHCI!memcpy+0x2b
fffff802`714d96b0 fffff800`fe917067 : 00000000`00000780 ffffe000`43e5c210 00000000`00000000 ffffe000`45ad6838 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x362
fffff802`714d9760 fffff800`fcd4fc81 : ffffe000`43ed8830 fffff802`714d98d0 00001fff`bc1a3fd8 00000000`00000046 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0x427
fffff802`714d9860 fffff802`6fac7c60 : fffff802`6fd8af00 fffff802`714d9b20 ffffe000`43e5c020 fffff802`6fd8d5c0 : Wdf01000!FxInterrupt::DpcHandler+0xc1
fffff802`714d9890 fffff802`6fac6fa7 : 00000000`00000000 fffff800`fe8ec6d7 00000000`00000000 fffff802`6fd88180 : nt!KiExecuteAllDpcs+0x1b0
fffff802`714d99e0 fffff802`6fbdceea : fffff802`6fd88180 fffff802`6fd88180 fffff802`6fde0a00 ffffe000`43ed9880 : nt!KiRetireDpcList+0xd7
fffff802`714d9c60 00000000`00000000 : fffff802`714da000 fffff802`714d4000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


THREAD_SHA1_HASH_MOD_FUNC:  d815cf17389c1b48072697e702093a8bbb1d8d7b

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  7910024ef3adbb04942d15ab720cdf4161ed04f8

THREAD_SHA1_HASH_MOD:  806cf8a12c50abcbde9d22747b4898f5489011b8

FOLLOWUP_IP: 
USBXHCI!memcpy+2b
fffff800`fe9370eb 488941f8        mov     qword ptr [rcx-8],rax

FAULT_INSTR_CODE:  f8418948

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  USBXHCI!memcpy+2b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBXHCI

IMAGE_NAME:  USBXHCI.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  5527309b

IMAGE_VERSION:  6.3.9600.17795

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  2b

FAILURE_BUCKET_ID:  AV_USBXHCI!memcpy

BUCKET_ID:  AV_USBXHCI!memcpy

PRIMARY_PROBLEM_CLASS:  AV_USBXHCI!memcpy

TARGET_TIME:  2019-03-01T19:44:16.000Z

OSBUILD:  9600

OSSERVICEPACK:  18505

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

OSEDITION:  Windows 8.1 Server TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-09-30 14:31:28

BUILDDATESTAMP_STR:  160930-0600

BUILDLAB_STR:  winblue_ltsb

BUILDOSVER_STR:  6.3.9600.18505.amd64fre.winblue_ltsb.160930-0600

ANALYSIS_SESSION_ELAPSED_TIME:  5ea

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_usbxhci!memcpy

FAILURE_ID_HASH:  {97a76950-b70a-8c5a-ed5c-b6610ae1f09c}

Followup:     MachineOwner
---------

0: kd> !analyze 

 

1 REPLY 1
Bunsol
HPE Pro

Re: Blue Screen; HP Proliant g9 380

Hi Duahimanshu,

 

If BSOD has occured and suspect are Dimms then hardware entries needs to be checked if this is pointing to memory registry. You also need to make sure that the firmware of the server is updated as multiple fixes are available for memory in the BIOS. Since an outage has occured we recommend you to log a case with HPE as hardware logs also needs to be checked and if the issue is caused by Dimms needs to be isolated.

 

Regards,

Bunsol

Accept or Kudo