Solved

HP Proliant ML350 G5 server blue screen debug minidump help

Posted on 2013-01-03
4
881 Views
Last Modified: 2013-01-31
Microsoft (R) Windows Debugger Version 6.2.8229.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\System Administrator\Desktop\Mini010313-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.120503-0334
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x808af9c8
Debug session time: Thu Jan  3 08:09:20.406 2013 (UTC - 10:00)
System Uptime: 9 days 22:57:57.068
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
Loading unloaded module list
..................................................
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86\triage\oca.ini, error 2
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86\winxp\triage.ini, error 2
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D0, {8, d0000002, 0, 80899707}

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2
Probably caused by : ntkrnlmp.exe ( nt!KiTrap0E+2a7 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_CORRUPTED_MMPOOL (d0)
Arguments:
Arg1: 00000008, memory referenced
Arg2: d0000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 80899707, address which referenced memory
      An attempt was made to access a pageable (or completely invalid) address at an
      interrupt request level (IRQL) that is too high.  This is
      caused by drivers that have corrupted the system pool.  Run the driver
      verifier against any new (or suspect) drivers, and if that doesn't turn up
      the culprit, then use gflags to enable special pool.  You can also set
      HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\ProtectNonPagedPool
      to a DWORD 1 value and reboot.  Then the system will unmap freed nonpaged pool,
      preventing drivers (although not DMA-hardware) from corrupting the pool.

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

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2

READ_ADDRESS: GetUlongFromAddress: unable to read from 808b41c8
 00000008

CURRENT_IRQL:  2

FAULTING_IP:
nt!MiFreePoolPages+8a3
80899707 8b4608          mov     eax,dword ptr [esi+8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD0

PROCESS_NAME:  System

TRAP_FRAME:  f78ee07c -- (.trap 0xfffffffff78ee07c)
ErrCode = 00000000
eax=86001000 ebx=00000005 ecx=81800000 edx=00000000 esi=00000000 edi=00000000
eip=80899707 esp=f78ee0f0 ebp=f78ee118 iopl=0         nv up ei ng nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010297
nt!MiFreePoolPages+0x8a3:
80899707 8b4608          mov     eax,dword ptr [esi+8] ds:0023:00000008=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 80899707 to 80836e17

STACK_TEXT:  
f78ee07c 80899707 badb0d00 00000000 85e21000 nt!KiTrap0E+0x2a7
f78ee118 8089c36d 86001000 86006000 87491b48 nt!MiFreePoolPages+0x8a3
f78ee170 f71727d9 3966744e 00000000 f78ee374 nt!ExFreePoolWithTag+0x277
f78ee180 f7172817 8742fa20 86001000 f7177f4b Ntfs!NtfsDeleteMdlAndBuffer+0x31
f78ee374 f71767d0 f78ee384 87491b48 0108070a Ntfs!NtfsCommonWrite+0x180b
f78ee4f0 80840153 8a1e33a8 87491b48 87491b48 Ntfs!NtfsFsdWrite+0x16a
f78ee504 f729fd28 87daf390 8a33c940 00000000 nt!IofCallDriver+0x45
f78ee530 80840153 8ab4bcc0 87491b48 87491b48 fltMgr!FltpDispatch+0x152
f78ee544 f729fb25 89bd0ee8 87491b48 89bd0ae0 nt!IofCallDriver+0x45
f78ee568 f729fcf5 f78ee588 89bd0ee8 00000000 fltMgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x20b
f78ee5a0 80840153 89bd0ee8 87491b48 0015f000 fltMgr!FltpDispatch+0x11f
f78ee5b4 80843b55 00000000 8ab3d040 f78ee5f0 nt!IofCallDriver+0x45
f78ee5c8 8084368f 8aacb209 f78ee5f0 f78ee6ac nt!IoSynchronousPageWrite+0xaf
f78ee6d8 80844413 e16dd57c e16dd590 8ab3d040 nt!MiFlushSectionInternal+0x67e
f78ee71c 80844c5c 8ab3d008 f78ee800 00005000 nt!MmFlushSection+0x23f
f78ee7a4 f7172db7 8aacb384 f78ee850 00005000 nt!CcFlushCache+0x1ed
f78ee874 f71aed93 e16a1e48 5c02c8b4 00000064 Ntfs!LfsFlushLfcb+0x229
f78ee8c8 f71bf2b5 016a1e48 5c02c8b4 00000064 Ntfs!LfsFlushToLsnPriv+0x199
f78ee928 f71aeea2 e16a1e48 000000e0 00000001 Ntfs!LfsWriteLfsRestart+0x171
f78ee974 f71ae92a e16b7480 00000068 f78ee9cc Ntfs!LfsWriteRestartArea+0x149
f78eebf4 f71adb2d f78eec28 8a1e3488 00000000 Ntfs!NtfsCheckpointVolume+0x129e
f78eed80 8082db10 00000000 00000000 8ab8b8b8 Ntfs!NtfsCheckpointAllVolumes+0xd2
f78eedac 8092072b 00000000 00000000 00000000 nt!ExpWorkerThread+0xeb
f78eeddc 8083fe9f 8082da53 00000000 00000000 nt!PspSystemThreadStartup+0x2e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!KiTrap0E+2a7
80836e17 833d40ee8a8000  cmp     dword ptr [nt!KiFreezeFlag (808aee40)],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiTrap0E+2a7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4fa2dddc

FAILURE_BUCKET_ID:  0xD0_nt!KiTrap0E+2a7

BUCKET_ID:  0xD0_nt!KiTrap0E+2a7

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

All I can see is that the blue screen is being caused by ntkrnlmp.exe.  Is there anything else anyone can discern from this minidump?

Also the server itself within the HP integrated management log is experiencing multiple errors regarding the redundant power supplies.  Could this blue screen be related?
0
Comment
Question by:OBESEJESUS
  • 2
  • 2
4 Comments
 
LVL 4

Accepted Solution

by:
Haslerct earned 500 total points
ID: 38742615
What is version of the bios?
0
 

Author Comment

by:OBESEJESUS
ID: 38742618
I'm not at the location so I can't get that exact info right now.
0
 

Author Comment

by:OBESEJESUS
ID: 38742767
I re-ran the minidump  at home and this is what I came up with, weird:


Microsoft (R) Windows Debugger  Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [G:\Mini010313-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*x:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.120503-0334
Kernel base = 0x80800000 PsLoadedModuleList = 0x808af9c8
Debug session time: Thu Jan  3 08:09:20.406 2013 (GMT-10)
System Uptime: 9 days 22:57:57.068
Loading Kernel Symbols
.........................................................................................................................
Loading unloaded module list
..................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D0, {8, d0000002, 0, 80899707}

Probably caused by : fltMgr.sys ( fltMgr!FltpDispatch+152 )

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

2: kd> !analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D0, {8, d0000002, 0, 80899707}

Probably caused by : fltMgr.sys ( fltMgr!FltpDispatch+152 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_CORRUPTED_MMPOOL (d0)
Arguments:
Arg1: 00000008, memory referenced
Arg2: d0000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 80899707, address which referenced memory
      An attempt was made to access a pageable (or completely invalid) address at an
      interrupt request level (IRQL) that is too high.  This is
      caused by drivers that have corrupted the system pool.  Run the driver
      verifier against any new (or suspect) drivers, and if that doesn't turn up
      the culprit, then use gflags to enable special pool.  You can also set
      HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\ProtectNonPagedPool
      to a DWORD 1 value and reboot.  Then the system will unmap freed nonpaged pool,
      preventing drivers (although not DMA-hardware) from corrupting the pool.

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


READ_ADDRESS:  00000008

CURRENT_IRQL:  2

FAULTING_IP:
nt!MiFreePoolPages+8a3
80899707 8b4608           mov     eax,[esi+0x8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0xD0

LAST_CONTROL_TRANSFER:  from 8089c36d to 80899707

TRAP_FRAME:  f78ee07c -- (.trap fffffffff78ee07c)
ErrCode = 00000000
eax=86001000 ebx=00000005 ecx=81800000 edx=00000000 esi=00000000 edi=00000000
eip=80899707 esp=f78ee0f0 ebp=f78ee118 iopl=0         nv up ei ng nz ac po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010297
nt!MiFreePoolPages+0x8a3:
80899707 8b4608           mov     eax,[esi+0x8]     ds:0023:00000008=????????
Resetting default scope

STACK_TEXT:  
f78ee118 8089c36d 86001000 86006000 87491b48 nt!MiFreePoolPages+0x8a3
f78ee170 f71727d9 3966744e 00000000 f78ee374 nt!ExFreePoolWithTag+0x277
f78ee180 f7172817 8742fa20 86001000 f7177f4b Ntfs!NtfsDeleteMdlAndBuffer+0x31
f78ee18c f7177f4b 87491b48 f78eed30 00000000 Ntfs!NtfsCommonWrite+0x180b
f78ee374 f71767d0 f78ee384 87491b48 0108070a Ntfs!NtfsCommonWrite+0x17b1
f78ee4f0 80840153 8a1e33a8 87491b48 87491b48 Ntfs!NtfsFsdWrite+0x16a
f78ee504 f729fd28 87daf390 8a33c940 00000000 nt!IofCallDriver+0x45
f78ee530 80840153 8ab4bcc0 87491b48 87491b48 fltMgr!FltpDispatch+0x152
f78ee544 f729fb25 89bd0ee8 87491b48 89bd0ae0 nt!IofCallDriver+0x45
f78ee568 f729fcf5 f78ee588 89bd0ee8 00000000 fltMgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x20b
f78ee5a0 80840153 89bd0ee8 87491b48 0015f000 fltMgr!FltpDispatch+0x11f
f78ee5b4 80843b55 00000000 8ab3d040 f78ee5f0 nt!IofCallDriver+0x45
f78ee5c8 8084368f 8aacb209 f78ee5f0 f78ee6ac nt!IoSynchronousPageWrite+0xaf
f78ee6d8 80844413 e16dd57c e16dd590 8ab3d040 nt!MiFlushSectionInternal+0x67e
f78ee71c 80844c5c 8ab3d008 f78ee800 00005000 nt!MmFlushSection+0x23f
f78ee7a4 f7172db7 8aacb384 f78ee850 00005000 nt!CcFlushCache+0x1ed
f78ee874 f71aed93 e16a1e48 5c02c8b4 00000064 Ntfs!LfsFlushLfcb+0x229
f78ee8c8 f71bf2b5 016a1e48 5c02c8b4 00000064 Ntfs!LfsFlushToLsnPriv+0x199
f78ee928 f71aeea2 e16a1e48 000000e0 00000001 Ntfs!LfsWriteLfsRestart+0x171
f78ee974 f71ae92a e16b7480 00000068 f78ee9cc Ntfs!LfsWriteRestartArea+0x149
f78eebf4 f71adb2d f78eec28 8a1e3488 00000000 Ntfs!NtfsCheckpointVolume+0x129e
f78eed80 8082db10 00000000 00000000 8ab8b8b8 Ntfs!NtfsCheckpointAllVolumes+0xd2
f78eedac 8092072b 00000000 00000000 00000000 nt!ExpWorkerThread+0xeb
f78eeddc 8083fe9f 8082da53 00000000 00000000 nt!PspSystemThreadStartup+0x2e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
fltMgr!FltpDispatch+152
f729fd28 5b               pop     ebx

SYMBOL_STACK_INDEX:  7

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  fltMgr!FltpDispatch+152

MODULE_NAME:  fltMgr

IMAGE_NAME:  fltMgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45d697cc

STACK_COMMAND:  .trap fffffffff78ee07c ; kb

FAILURE_BUCKET_ID:  0xD0_fltMgr!FltpDispatch+152

BUCKET_ID:  0xD0_fltMgr!FltpDispatch+152

Followup: MachineOwner
---------
0
 
LVL 4

Assisted Solution

by:Haslerct
Haslerct earned 500 total points
ID: 38743108
Hi, you can check the bios version using HP System Management Homepage.

Reason I asked, coz, I resolved same issue on DL580G5 and it is due to old BIOS.

Once update the BIOS, problem resolved.

Furthermore, you can do the BIOS upgrade online and remotely (eg: using RDP)

Thanks
0

Featured Post

Want to promote your upcoming event?

Attending an event? Speaking at a conference? Or exhibiting at a tradeshow? Easily inform your contacts by using a promotional banner in your email signature. This will ensure your organization’s most important contacts are in the know.

Join & Write a Comment

On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
Excel styles will make formatting consistent and let you apply and change formatting faster. In this tutorial, you'll learn how to use Excel's built-in styles, how to modify styles, and how to create your own. You'll also learn how to use your custo…
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now