ProLiant Servers - Netservers

HP ProLiant N54L G7 bugcheck BSOD reboot since January 12 Windows Updates

 
SOLVED
Go to solution
Thomas K.H. Bittner
Occasional Contributor

HP ProLiant N54L G7 bugcheck BSOD reboot since January 12 Windows Updates

Both of our HP PL Microserver with CPU AMD Turion II and NC107i PCIe Gigabit Server Adapter with b57nd60a.sys driver get bugcheck and BSOD reboot since January 12 Windows Updates have been installed. Removing them doesn't heal it, they keep on rebooting at least once a day since then.

The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0x0000000000000000, 0x0000000000000000).

 Fault bucket 0x133_ISR_b57nd60a!UM_Isr, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 8c9fb6a3-03aa-4cf4-8a8f-9aec1a785a71

 

 

8 REPLIES 8
Mellu721
Occasional Visitor

Re: HP ProLiant N54L G7 bugcheck BSOD reboot since January 12 Windows Updates

I have the same problem on N54L and 2012R2 after January 2018 MS updates. Here are little more information:

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
	DISPATCH_LEVEL or above. The offending component can usually be
	identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT_SERVER

BUGCHECK_STR:  0x133

PROCESS_NAME:  System

CURRENT_IRQL:  d

LAST_CONTROL_TRANSFER:  from fffff800c5602e92 to fffff800c55ccea0

STACK_TEXT:  
ffffd001`65343438 fffff800`c5602e92 : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx
ffffd001`65343440 fffff800`c55276f1 : 80000000`00300121 00000000`0022f6bf 80000000`00300121 80000000`00300121 : nt! ?? ::FNODOBFM::`string'+0x1eec2
ffffd001`653434d0 fffff800`c5410ac5 : fffff800`c545ccd0 fffff780`00000320 ffffe000`5e035de0 ffffd001`65307180 : nt!KeClockInterruptNotify+0x91
ffffd001`653436f0 fffff800`c5544bb3 : ffff2a3b`aad8cf42 00000000`00000000 ffffd001`6559c4a0 ffffd001`6559c4a0 : hal!HalpTimerClockIpiRoutine+0x15
ffffd001`65343720 fffff800`c55ce3da : fffff800`c545cc30 ffffe000`5e035de0 00004757`b0e90969 ffffd001`6559c4a0 : nt!KiCallInterruptServiceRoutine+0xa3
ffffd001`65343760 fffff800`c55ce8a7 : 00000000`00000200 fffff800`c55283ea ffff2a3b`aad8cc12 ffff2a3b`aad8ce92 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd001`653437b0 fffff800`c54f961b : 00000000`00000000 ffff2a3b`aad8c112 fffff800`c545cc00 fffff780`00000320 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffd001`65343940 fffff800`c5544c52 : ffffd001`6559c400 00000000`00000000 00000000`00000206 fffff800`c55283ea : nt!KxWaitForSpinLockAndAcquire+0xf
ffffd001`65343970 fffff800`c55ce198 : ffffd001`6559c400 00000000`00000003 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x142
ffffd001`653439b0 fffff800`c55ce427 : ffffd001`65307180 00000000`00000000 00000000`00000000 fffff800`c552776e : nt!KiInterruptSubDispatch+0x108
ffffd001`65343a00 fffff800`c55cfbbe : ffffe000`5ca7e000 fffff800`c5763f00 ffffe000`5e9119d0 fffff800`c55ce3da : nt!KiInterruptDispatch+0x37
ffffd001`65343b90 fffff800`c54f5382 : 00000000`00000000 00000000`0022d8d4 00000000`00000027 fffff800`eea342d5 : nt!KiIsrLinkage+0x43d
ffffd001`65343d20 fffff800`ee8c5a6c : 00000000`00000000 00000000`00000000 ffffe000`5e9119d0 fffff800`00000000 : nt!KeInsertQueueDpc+0x62
ffffd001`65343da0 fffff800`efa6a213 : ffffe000`00000000 ffffe000`5fc8a000 ffffd001`65343ef0 00000000`00000000 : NDIS!NdisMQueueDpcEx+0xec
ffffd001`65343e20 ffffe000`00000000 : ffffe000`5fc8a000 ffffd001`65343ef0 00000000`00000000 32363033`38363533 : b57nd60a+0x5213
ffffd001`65343e28 ffffe000`5fc8a000 : ffffd001`65343ef0 00000000`00000000 32363033`38363533 00000000`00000003 : 0xffffe000`00000000
ffffd001`65343e30 ffffd001`65343ef0 : 00000000`00000000 32363033`38363533 00000000`00000003 3a494e49`4d520000 : 0xffffe000`5fc8a000
ffffd001`65343e38 00000000`00000000 : 32363033`38363533 00000000`00000003 3a494e49`4d520000 fffffd5f`3c2f2667 : 0xffffd001`65343ef0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
b57nd60a+5213
fffff800`efa6a213 ??              ???

SYMBOL_STACK_INDEX:  e

SYMBOL_NAME:  b57nd60a+5213

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: b57nd60a

IMAGE_NAME:  b57nd60a.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5150e84b

FAILURE_BUCKET_ID:  X64_0x133_b57nd60a+5213

BUCKET_ID:  X64_0x133_b57nd60a+5213

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

  

numerounosrl
Frequent Visitor

Re: HP ProLiant N54L G7 bugcheck BSOD reboot since January 12 Windows Updates

Same problem in HP Proliant DL385P Gen8

I tried to update via SPP 10.2017 all the firmwares but still have same issue, any ideas? 

Torsten.
Acclaimed Contributor

Re: HP ProLiant N54L G7 bugcheck BSOD reboot since January 12 Windows Updates

no idea about the drivers, but ssp2017.10 has no g7 firmware at all. you need to use post production g7 spp.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
numerounosrl
Frequent Visitor

Re: HP ProLiant N54L G7 bugcheck BSOD reboot since January 12 Windows Updates

Torsten.
Acclaimed Contributor

Re: HP ProLiant N54L G7 bugcheck BSOD reboot since January 12 Windows Updates

I cannot open your link.

But try this:

http://h17007.www1.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx?version=G7.1

Service Pack for ProLiant (SPP) Version G7.1


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Dennis Handly
Acclaimed Contributor

Re: HP ProLiant N54L G7 bugcheck BSOD reboot since January 12 Windows Updates

You have a junk char at the end of your URL.  You can edit it with Post Options > Edit Reply and use the link menu to fix it.

Mellu721
Occasional Visitor

Re: HP ProLiant N54L G7 bugcheck BSOD reboot since January 12 Windows Updates

Thomas K.H. Bittner
Occasional Contributor
Solution

Re: HP ProLiant N54L G7 bugcheck BSOD reboot since January 12 Windows Updates

FW and driver update solved it together with KB4077561