Guest PleaseHelpME Posted February 7, 2008 Posted February 7, 2008 I have not been able to match specific events to a particular error. Has anyone resolved a similar problem? I have had 6 servers randomly reboot with the following event information: Event Type: Information Event Source: Save Dump Event Category: None Event ID: 1001 Date: 2/3/2008 Time: 12:57:55 AM User: N/A Computer: PHQOCR01 Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x00000020, 0x88455670, 0x884557a0, 0x1a260008). A dump was saved in: C:\WINDOWS\MEMORY.DMP. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Warning Event Source: USER32 Event Category: None Event ID: 1076 Date: 2/4/2008 Time: 7:21:07 AM User: PPSB\mpeterso Computer: PHQOCR01 Description: The reason supplied by user PPSB\MPeterso for the last unexpected shutdown of this computer is: System Failure: Stop error Reason Code: 0x805000f Bug ID: Bugcheck String: 0x00000019 (0x00000020, 0x88455670, 0x884557a0, 0x1a260008) Comment: 0x00000019 (0x00000020, 0x88455670, 0x884557a0, 0x1a260008) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 0f 00 05 08 .... Event Type: Error Event Source: System Error Event Category: (102) Event ID: 1003 Date: 2/4/2008 Time: 7:21:39 AM User: N/A Computer: PHQOCR01 Description: Error code 00000019, parameter1 00000020, parameter2 88455670, parameter3 884557a0, parameter4 1a260008. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 53 79 73 74 65 6d 20 45 System E 0008: 72 72 6f 72 20 20 45 72 rror Er 0010: 72 6f 72 20 63 6f 64 65 ror code 0018: 20 30 30 30 30 30 30 31 0000001 0020: 39 20 20 50 61 72 61 6d 9 Param 0028: 65 74 65 72 73 20 30 30 eters 00 0030: 30 30 30 30 32 30 2c 20 000020, 0038: 38 38 34 35 35 36 37 30 88455670 0040: 2c 20 38 38 34 35 35 37 , 884557 0048: 61 30 2c 20 31 61 32 36 a0, 1a26 0050: 30 30 30 38 0008
Guest Robert L. \(MS-MVP\) Posted February 7, 2008 Posted February 7, 2008 Re: 2003 SP2 Servers rebooting from a bugcheck/system failure: stop er We need more information to help, but these links may give you some help too. Server shutdown unexpected with ...Recently, the server has been shutdown unexpected with different Reason Code: 0x806000c, 0x8000005 and 0x805000f. He doesn’t remember any thing change. ... http://www.chicagotech.net/netforums/viewtopic.php?p=4255 - Similar pages Event ID 1076 - Reason Code 0x805000f The reason supplied by user User for the last unexpected shutdown of this computer is: System Failure: Stop error Reason Code: 0x805000f ...http .... http://www.chicagotech.net/troubleshooting/eventid1076.htm -- Bob Lin, MS-MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com "PleaseHelpME" <PleaseHelpME@discussions.microsoft.com> wrote in message news:B7153C96-5C9D-4E62-926D-55B3C91DDC0E@microsoft.com... >I have not been able to match specific events to a particular error. Has > anyone resolved a similar problem? > > I have had 6 servers randomly reboot with the following event information: > > Event Type: Information > Event Source: Save Dump > Event Category: None > Event ID: 1001 > Date: 2/3/2008 > Time: 12:57:55 AM > User: N/A > Computer: PHQOCR01 > Description: > The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 > (0x00000020, 0x88455670, 0x884557a0, 0x1a260008). A dump was saved in: > C:\WINDOWS\MEMORY.DMP. > > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > > Event Type: Warning > Event Source: USER32 > Event Category: None > Event ID: 1076 > Date: 2/4/2008 > Time: 7:21:07 AM > User: PPSB\mpeterso > Computer: PHQOCR01 > Description: > The reason supplied by user PPSB\MPeterso for the last unexpected shutdown > of this computer is: System Failure: Stop error > Reason Code: 0x805000f > Bug ID: > Bugcheck String: 0x00000019 (0x00000020, 0x88455670, 0x884557a0, > 0x1a260008) > Comment: 0x00000019 (0x00000020, 0x88455670, 0x884557a0, 0x1a260008) > > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > Data: > 0000: 0f 00 05 08 .... > > Event Type: Error > Event Source: System Error > Event Category: (102) > Event ID: 1003 > Date: 2/4/2008 > Time: 7:21:39 AM > User: N/A > Computer: PHQOCR01 > Description: > Error code 00000019, parameter1 00000020, parameter2 88455670, parameter3 > 884557a0, parameter4 1a260008. > > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > Data: > 0000: 53 79 73 74 65 6d 20 45 System E > 0008: 72 72 6f 72 20 20 45 72 rror Er > 0010: 72 6f 72 20 63 6f 64 65 ror code > 0018: 20 30 30 30 30 30 30 31 0000001 > 0020: 39 20 20 50 61 72 61 6d 9 Param > 0028: 65 74 65 72 73 20 30 30 eters 00 > 0030: 30 30 30 30 32 30 2c 20 000020, > 0038: 38 38 34 35 35 36 37 30 88455670 > 0040: 2c 20 38 38 34 35 35 37 , 884557 > 0048: 61 30 2c 20 31 61 32 36 a0, 1a26 > 0050: 30 30 30 38 0008 > > >
Guest Pedro M. Leite Posted February 8, 2008 Posted February 8, 2008 Re: 2003 SP2 Servers rebooting from a bugcheck/system failure: stop er hi usual question any recent new hardware or software installed ?? had that on my sbs 2k3 after installing software firewall. sygate was the thing. never installed afterwards, no more stop errors. PLeite from Portugal -------------------------------------------------------------- "Robert L. (MS-MVP)" <blinNoEmailplease@mvps.org> escreveu na mensagem news:e%23%23yhlcaIHA.4880@TK2MSFTNGP03.phx.gbl... > We need more information to help, but these links may give you some help > too. > > Server shutdown unexpected with ...Recently, the server has been shutdown > unexpected with different Reason Code: 0x806000c, 0x8000005 and 0x805000f. > He doesn't remember any thing change. ... > http://www.chicagotech.net/netforums/viewtopic.php?p=4255 - Similar pages > > Event ID 1076 - Reason Code 0x805000f > The reason supplied by user User for the last unexpected shutdown of > this computer is: System Failure: Stop error Reason Code: 0x805000f ....http > ... > http://www.chicagotech.net/troubleshooting/eventid1076.htm > > > -- > Bob Lin, MS-MVP, MCSE & CNE > Networking, Internet, Routing, VPN Troubleshooting on > http://www.ChicagoTech.net > How to Setup Windows, Network, VPN & Remote Access on > http://www.HowToNetworking.com > > > "PleaseHelpME" <PleaseHelpME@discussions.microsoft.com> wrote in message > news:B7153C96-5C9D-4E62-926D-55B3C91DDC0E@microsoft.com... > >I have not been able to match specific events to a particular error. Has > > anyone resolved a similar problem? > > > > I have had 6 servers randomly reboot with the following event information: > > > > Event Type: Information > > Event Source: Save Dump > > Event Category: None > > Event ID: 1001 > > Date: 2/3/2008 > > Time: 12:57:55 AM > > User: N/A > > Computer: PHQOCR01 > > Description: > > The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 > > (0x00000020, 0x88455670, 0x884557a0, 0x1a260008). A dump was saved in: > > C:\WINDOWS\MEMORY.DMP. > > > > For more information, see Help and Support Center at > > http://go.microsoft.com/fwlink/events.asp. > > > > Event Type: Warning > > Event Source: USER32 > > Event Category: None > > Event ID: 1076 > > Date: 2/4/2008 > > Time: 7:21:07 AM > > User: PPSB\mpeterso > > Computer: PHQOCR01 > > Description: > > The reason supplied by user PPSB\MPeterso for the last unexpected shutdown > > of this computer is: System Failure: Stop error > > Reason Code: 0x805000f > > Bug ID: > > Bugcheck String: 0x00000019 (0x00000020, 0x88455670, 0x884557a0, > > 0x1a260008) > > Comment: 0x00000019 (0x00000020, 0x88455670, 0x884557a0, 0x1a260008) > > > > For more information, see Help and Support Center at > > http://go.microsoft.com/fwlink/events.asp. > > Data: > > 0000: 0f 00 05 08 .... > > > > Event Type: Error > > Event Source: System Error > > Event Category: (102) > > Event ID: 1003 > > Date: 2/4/2008 > > Time: 7:21:39 AM > > User: N/A > > Computer: PHQOCR01 > > Description: > > Error code 00000019, parameter1 00000020, parameter2 88455670, parameter3 > > 884557a0, parameter4 1a260008. > > > > For more information, see Help and Support Center at > > http://go.microsoft.com/fwlink/events.asp. > > Data: > > 0000: 53 79 73 74 65 6d 20 45 System E > > 0008: 72 72 6f 72 20 20 45 72 rror Er > > 0010: 72 6f 72 20 63 6f 64 65 ror code > > 0018: 20 30 30 30 30 30 30 31 0000001 > > 0020: 39 20 20 50 61 72 61 6d 9 Param > > 0028: 65 74 65 72 73 20 30 30 eters 00 > > 0030: 30 30 30 30 32 30 2c 20 000020, > > 0038: 38 38 34 35 35 36 37 30 88455670 > > 0040: 2c 20 38 38 34 35 35 37 , 884557 > > 0048: 61 30 2c 20 31 61 32 36 a0, 1a26 > > 0050: 30 30 30 38 0008 > > > > > > >
Guest Jon Posted February 8, 2008 Posted February 8, 2008 Re: 2003 SP2 Servers rebooting from a bugcheck/system failure: stoper Re: 2003 SP2 Servers rebooting from a bugcheck/system failure: stoper Hi there, The best way to deal with this is to run the crash dump through a debugger - this will normally tell you exactly where the problem lies. This article describes how to get started with the debugger: http://www.microsoft.com/whdc/devtools/debugging/debugstart.mspx It can be a bit unintuitive to begin with, but once you get the hang of it, it makes dealing with crashes much easier. Regards Jon On Feb 7, 7:19 pm, PleaseHelpME <PleaseHel...@discussions.microsoft.com> wrote: > I have not been able to match specific events to a particular error. Has > anyone resolved a similar problem? > > I have had 6 servers randomly reboot with the following event information: > > Event Type: Information > Event Source: Save Dump > Event Category: None > Event ID: 1001 > Date: 2/3/2008 > Time: 12:57:55 AM > User: N/A > Computer: PHQOCR01 > Description: > The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 > (0x00000020, 0x88455670, 0x884557a0, 0x1a260008). A dump was saved in: > C:\WINDOWS\MEMORY.DMP.
Guest PleaseHelpME Posted February 11, 2008 Posted February 11, 2008 Re: 2003 SP2 Servers rebooting from a bugcheck/system failure: sto Re: 2003 SP2 Servers rebooting from a bugcheck/system failure: sto If this check worked properly...it looks like the problem may be a hardware driver. Here is the output: Opened log file 'c:\debuglog.txt' Microsoft ® Windows Debugger Version 6.8.0004.0 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Mini020608-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: C:\WINNT;C:\WINNT\system32;C:\WINNT\system32\drivers Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible Product: Server, suite: Enterprise TerminalServer SingleUserTS Built by: 3790.srv03_sp2_gdr.070304-2240 Kernel base = 0x80800000 PsLoadedModuleList = 0x808af9c8 Debug session time: Wed Feb 6 21:00:37.485 2008 (GMT-7) System Uptime: 1 days 16:57:47.734 Loading Kernel Symbols ............................................................................................................................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 19, {20, 881a3a48, 881a3b78, 1a260005} *** WARNING: Unable to verify timestamp for cpqasm2.sys *** ERROR: Module load completed but symbols could not be loaded for cpqasm2.sys Probably caused by : cpqasm2.sys ( cpqasm2+2662 ) Followup: MachineOwner --------- 2: kd> !analyze -v;r;kv;lmtn;.logclose;q ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. This may or may not be due to the caller. The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. Arguments: Arg1: 00000020, a pool block header size is corrupt. Arg2: 881a3a48, The pool entry we were looking for within the page. Arg3: 881a3b78, The next pool entry. Arg4: 1a260005, (reserved) Debugging Details: ------------------ BUGCHECK_STR: 0x19_20 POOL_ADDRESS: 881a3a48 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP PROCESS_NAME: cqmgserv.exe CURRENT_IRQL: 1 IRP_ADDRESS: 891ca668 LAST_CONTROL_TRANSFER: from 8089c8ff to 8087c480 STACK_TEXT: b91d0a28 8089c8ff 00000019 00000020 881a3a48 nt!KeBugCheckEx+0x1b b91d0a90 80841805 881a3a50 00000000 891ca6a8 nt!ExFreePoolWithTag+0x477 b91d0ae4 80840ac9 891ca6a8 b91d0b30 b91d0b24 nt!IopCompleteRequest+0xf9 b91d0b34 80a80199 00000000 00000000 00000000 nt!KiDeliverApc+0xbb b91d0b54 80a803d9 88eb2d01 00000000 00000000 hal!HalpDispatchSoftwareInterrupt+0x49 b91d0b70 80a80456 00000001 88eb2d00 b91d0b9c hal!HalpCheckForSoftwareInterrupt+0x81 b91d0b80 8083d60c 88eb2db0 891ca6a8 4501004c hal!KfLowerIrql+0x62 b91d0b9c 80840d7f 891ca6a8 891ca668 00000000 nt!KiExitDispatcher+0x130 b91d0bbc 80840055 891ca6a8 88ba7c28 00000000 nt!KeInsertQueueApc+0x57 b91d0bf0 ba41e662 8977c030 8977c0ec 891ca668 nt!IopfCompleteRequest+0x200 WARNING: Stack unwind information not available. Following frames may be wrong. b91d0c24 ba41d55a 8977c030 891ca668 891ca668 cpqasm2+0x2662 b91d0c3c 80840153 8977c030 891ca668 88ba7c28 cpqasm2+0x155a b91d0c50 8092b50f 891ca720 88ba7c28 891ca668 nt!IofCallDriver+0x45 b91d0c64 8092b444 8977c030 891ca668 88ba7c28 nt!IopSynchronousServiceTail+0x10b b91d0d00 8092b564 000005a0 00000000 00000000 nt!IopXxxControlFile+0x60f b91d0d34 80833bdf 000005a0 00000000 00000000 nt!NtDeviceIoControlFile+0x2a b91d0d34 7c8285ec 000005a0 00000000 00000000 nt!KiFastCallEntry+0xfc 00e1fb70 00000000 00000000 00000000 00000000 0x7c8285ec STACK_COMMAND: kb FOLLOWUP_IP: cpqasm2+2662 ba41e662 ?? ??? SYMBOL_STACK_INDEX: a SYMBOL_NAME: cpqasm2+2662 FOLLOWUP_NAME: MachineOwner MODULE_NAME: cpqasm2 IMAGE_NAME: cpqasm2.sys DEBUG_FLR_IMAGE_TIMESTAMP: 455544d1 FAILURE_BUCKET_ID: 0x19_20_cpqasm2+2662 BUCKET_ID: 0x19_20_cpqasm2+2662 Followup: MachineOwner --------- eax=f772f13c ebx=881a3a48 ecx=00000000 edx=00000101 esi=f772f120 edi=000001ff eip=8087c480 esp=b91d0a10 ebp=b91d0a28 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286 nt!KeBugCheckEx+0x1b: 8087c480 5d pop ebp ChildEBP RetAddr Args to Child b91d0a28 8089c8ff 00000019 00000020 881a3a48 nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo]) b91d0a90 80841805 881a3a50 00000000 891ca6a8 nt!ExFreePoolWithTag+0x477 (FPO: [Non-Fpo]) b91d0ae4 80840ac9 891ca6a8 b91d0b30 b91d0b24 nt!IopCompleteRequest+0xf9 (FPO: [Non-Fpo]) b91d0b34 80a80199 00000000 00000000 00000000 nt!KiDeliverApc+0xbb (FPO: [Non-Fpo]) b91d0b54 80a803d9 88eb2d01 00000000 00000000 hal!HalpDispatchSoftwareInterrupt+0x49 (FPO: [Non-Fpo]) b91d0b70 80a80456 00000001 88eb2d00 b91d0b9c hal!HalpCheckForSoftwareInterrupt+0x81 (FPO: [Non-Fpo]) b91d0b80 8083d60c 88eb2db0 891ca6a8 4501004c hal!KfLowerIrql+0x62 (FPO: [Non-Fpo]) b91d0b9c 80840d7f 891ca6a8 891ca668 00000000 nt!KiExitDispatcher+0x130 (FPO: [Non-Fpo]) b91d0bbc 80840055 891ca6a8 88ba7c28 00000000 nt!KeInsertQueueApc+0x57 (FPO: [Non-Fpo]) b91d0bf0 ba41e662 8977c030 8977c0ec 891ca668 nt!IopfCompleteRequest+0x200 (FPO: [Non-Fpo]) WARNING: Stack unwind information not available. Following frames may be wrong. b91d0c24 ba41d55a 8977c030 891ca668 891ca668 cpqasm2+0x2662 b91d0c3c 80840153 8977c030 891ca668 88ba7c28 cpqasm2+0x155a b91d0c50 8092b50f 891ca720 88ba7c28 891ca668 nt!IofCallDriver+0x45 (FPO: [Non-Fpo]) b91d0c64 8092b444 8977c030 891ca668 88ba7c28 nt!IopSynchronousServiceTail+0x10b (FPO: [Non-Fpo]) b91d0d00 8092b564 000005a0 00000000 00000000 nt!IopXxxControlFile+0x60f (FPO: [Non-Fpo]) b91d0d34 80833bdf 000005a0 00000000 00000000 nt!NtDeviceIoControlFile+0x2a (FPO: [Non-Fpo]) b91d0d34 7c8285ec 000005a0 00000000 00000000 nt!KiFastCallEntry+0xfc (FPO: [0,0] TrapFrame @ b91d0d64) 00e1fb70 00000000 00000000 00000000 00000000 0x7c8285ec start end module name 80800000 80a7a000 nt ntkrnlmp.exe Mon Mar 05 06:02:02 2007 (45EC14CA) 80a7a000 80aa6000 hal halmacpi.dll Fri Feb 16 22:48:26 2007 (45D6972A) b80a1000 b80a2a00 PROCEXP100 PROCEXP100.SYS Fri Jan 06 15:04:34 2006 (43BEE972) b85fc000 b8627000 RDPWD RDPWD.SYS Fri Feb 16 22:44:38 2007 (45D69646) b8947000 b89571a0 mfeavfk mfeavfk.sys Wed Aug 29 15:14:54 2007 (46D5EFDE) b8958000 b89802c0 mfehidk mfehidk.sys Wed Aug 29 15:13:10 2007 (46D5EF76) b8f11000 b8f1f060 mfeapfk mfeapfk.sys Wed Aug 29 15:14:07 2007 (46D5EFAF) b9011000 b901c000 TDTCP TDTCP.SYS Fri Feb 16 22:44:32 2007 (45D69640) b9741000 b979e000 srv srv.sys Fri Feb 16 23:27:20 2007 (45D6A048) b98b6000 b9906000 HTTP HTTP.sys Fri Feb 16 23:28:12 2007 (45D6A07C) b9b5e000 b9b76000 clusnet clusnet.sys Fri Feb 16 23:02:57 2007 (45D69A91) b9d6e000 b9d78000 ndisuio ndisuio.sys Fri Feb 16 22:58:25 2007 (45D69981) b9ea6000 b9eb7000 Fips Fips.SYS Fri Feb 16 23:26:33 2007 (45D6A019) b9eb7000 b9f2d000 mrxsmb mrxsmb.sys Fri Feb 16 23:28:15 2007 (45D6A07F) b9f55000 b9f85000 rdbss rdbss.sys Fri Feb 16 23:27:37 2007 (45D6A059) b9f85000 b9faf000 afd afd.sys unavailable (00000000) b9faf000 b9fe0000 netbt netbt.sys Fri Feb 16 23:28:57 2007 (45D6A0A9) b9fe0000 ba070000 tcpip tcpip.sys Tue Oct 30 10:34:10 2007 (47276B12) ba070000 ba089000 ipsec ipsec.sys Fri Feb 16 23:29:28 2007 (45D6A0C8) ba0a9000 ba0afa60 mfebopk mfebopk.sys Wed Aug 29 15:15:21 2007 (46D5EFF9) ba0f9000 ba110000 ClusDisk ClusDisk.sys Fri Feb 16 23:02:55 2007 (45D69A8F) ba1d8000 ba1ed000 usbhub usbhub.sys Fri Feb 16 23:13:05 2007 (45D69CF1) ba26d000 ba277000 Dxapi Dxapi.sys Tue Mar 25 00:06:01 2003 (3E7FFFD9) ba2d0000 ba32f000 update update.sys Mon May 28 05:15:16 2007 (465AC7D4) ba32f000 ba356000 ks ks.sys Fri Feb 16 23:30:40 2007 (45D6A110) ba37e000 ba3b5000 rdpdr rdpdr.sys Fri Feb 16 22:51:00 2007 (45D697C4) ba3b5000 ba3c7000 raspptp raspptp.sys Fri Feb 16 23:29:20 2007 (45D6A0C0) ba3c7000 ba3e0000 ndiswan ndiswan.sys Fri Feb 16 23:29:22 2007 (45D6A0C2) ba3e0000 ba3f4000 rasl2tp rasl2tp.sys Fri Feb 16 23:29:02 2007 (45D6A0AE) ba3f4000 ba409000 serial serial.sys Fri Feb 16 23:06:46 2007 (45D69B76) ba409000 ba41c000 i8042prt i8042prt.sys Fri Feb 16 23:30:40 2007 (45D6A110) ba41c000 ba462000 cpqasm2 cpqasm2.sys Fri Nov 10 20:34:41 2006 (455544D1) ba462000 ba47e000 VIDEOPRT VIDEOPRT.SYS Fri Feb 16 23:10:30 2007 (45D69C56) ba47e000 ba4d3600 ati2mpad ati2mpad.sys Mon Mar 22 09:22:19 2004 (405F12BB) ba4d4000 ba4fe000 USBPORT USBPORT.SYS Fri Feb 16 23:12:59 2007 (45D69CEB) ba4fe000 ba511000 CPQCISSE CPQCISSE.sys Fri Mar 23 10:23:08 2007 (46040CFC) ba511000 ba53c000 q57xp32 q57xp32.sys Fri Dec 15 15:44:55 2006 (45832567) ba641000 ba6417c0 AlKernel AlKernel.sys Fri Aug 24 15:31:42 2001 (3B86D5CE) baec0000 baece000 HIDCLASS HIDCLASS.SYS Tue Mar 25 00:10:17 2003 (3E8000D9) baed0000 baedb0a0 mfetdik mfetdik.sys Wed Aug 29 15:13:57 2007 (46D5EFA5) baee0000 baee9000 mssmbios mssmbios.sys Fri Feb 16 22:59:12 2007 (45D699B0) baf00000 baf0e000 NDProxy NDProxy.SYS Fri Feb 16 22:59:21 2007 (45D699B9) baf10000 baf19000 raspti raspti.sys Fri Feb 16 22:59:23 2007 (45D699BB) baf20000 baf2c000 vga vga.sys Fri Feb 16 23:10:30 2007 (45D69C56) baf30000 baf3d000 Npfs Npfs.SYS Fri Feb 16 22:50:36 2007 (45D697AC) baf70000 baf7f000 raspppoe raspppoe.sys Fri Feb 16 22:59:23 2007 (45D699BB) baf80000 baf8a000 mouclass mouclass.sys Tue Mar 25 00:03:09 2003 (3E7FFF2D) bafa0000 bafab000 TDI TDI.SYS Fri Feb 16 23:01:19 2007 (45D69A2F) bafb0000 bafbb000 Msfs Msfs.SYS unavailable (00000000) bafd0000 bafdd000 wanarp wanarp.sys Fri Feb 16 22:59:17 2007 (45D699B5) bafe0000 bafef000 termdd termdd.sys Fri Feb 16 22:44:32 2007 (45D69640) baff0000 baffb000 kbdclass kbdclass.sys Fri Feb 16 23:05:39 2007 (45D69B33) bf800000 bf9cf000 win32k win32k.sys Thu Mar 01 07:59:28 2007 (45E6EA50) bf9cf000 bf9e6000 dxg dxg.sys Fri Feb 16 23:14:39 2007 (45D69D4F) bf9e6000 bfa3d100 ati2drad ati2drad.dll Mon Mar 22 09:23:41 2004 (405F130D) bff60000 bff7e000 RDPDD RDPDD.dll Sat Feb 17 07:01:19 2007 (45D70AAF) f703b000 f705a000 Mup Mup.sys Fri Feb 16 23:27:41 2007 (45D6A05D) f705a000 f7072b80 RAIDISK RAIDISK.sys Wed May 19 02:22:02 2004 (40AB273A) f7073000 f70b2000 NDIS NDIS.sys Fri Feb 16 23:28:49 2007 (45D6A0A1) f70b2000 f7147000 Ntfs Ntfs.sys Fri Feb 16 23:27:23 2007 (45D6A04B) f7147000 f716d000 KSecDD KSecDD.sys Fri Feb 16 22:46:32 2007 (45D696B8) f716d000 f7192000 fltmgr fltmgr.sys Fri Feb 16 22:51:08 2007 (45D697CC) f7192000 f71a5000 CLASSPNP CLASSPNP.SYS Fri Feb 16 23:28:16 2007 (45D6A080) f71a5000 f71c0000 adpu160m adpu160m.sys Mon Sep 29 11:14:03 2003 (3F78766B) f71c0000 f7200000 storport storport.sys Mon Feb 12 05:23:49 2007 (45D05C55) f7200000 f7325000 ql2300 ql2300.sys Thu Oct 05 10:24:35 2006 (45253FD3) f7325000 f7344000 SCSIPORT SCSIPORT.SYS Fri Feb 16 23:28:41 2007 (45D6A099) f7344000 f736b140 LsiCsb6 LsiCsb6.sys Thu Jul 31 13:38:06 2003 (3F297E2E) f736c000 f7389000 atapi atapi.sys Fri Feb 16 23:07:34 2007 (45D69BA6) f7389000 f73b3000 volsnap volsnap.sys Fri Feb 16 23:08:23 2007 (45D69BD7) f73b3000 f73df000 dmio dmio.sys Fri Feb 16 23:10:44 2007 (45D69C64) f73df000 f7406000 ftdisk ftdisk.sys Fri Feb 16 23:08:05 2007 (45D69BC5) f7406000 f741c000 pci pci.sys Fri Feb 16 22:59:03 2007 (45D699A7) f741c000 f7450000 ACPI ACPI.sys Fri Feb 16 22:58:47 2007 (45D69997) f7450000 f7466000 sacdrv sacdrv.sys Fri Feb 16 23:06:42 2007 (45D69B72) f7487000 f7490000 WMILIB WMILIB.SYS Tue Mar 25 00:13:00 2003 (3E80017C) f7497000 f74a6000 isapnp isapnp.sys Fri Feb 16 22:58:57 2007 (45D699A1) f74a7000 f74b4000 PCIIDEX PCIIDEX.SYS Fri Feb 16 23:07:32 2007 (45D69BA4) f74b7000 f74c7000 MountMgr MountMgr.sys Fri Feb 16 23:05:35 2007 (45D69B2F) f74c7000 f74d2000 PartMgr PartMgr.sys Fri Feb 16 23:29:25 2007 (45D6A0C5) f74d7000 f74e3000 symc8xx symc8xx.sys Thu Oct 14 14:29:38 2004 (416EEFC2) f74e7000 f74f2000 sym_hi sym_hi.sys Fri Oct 29 15:09:18 2004 (4182BF8E) f74f7000 f7501000 cpqcissm cpqcissm.sys Fri Feb 23 20:48:45 2007 (45DFB59D) f7507000 f7517000 symmpi symmpi.sys Wed May 26 09:30:13 2004 (40B4C615) f7517000 f7527000 disk disk.sys Fri Feb 16 23:07:51 2007 (45D69BB7) f7527000 f7532480 vsp vsp.sys Tue Nov 08 11:45:43 2005 (4370F257) f7537000 f7543000 Dfs Dfs.sys Fri Feb 16 22:51:17 2007 (45D697D5) f7547000 f7550000 RdFil RdFil.sys Wed Mar 03 21:05:55 2004 (4046AB23) f7557000 f7561000 crcdisk crcdisk.sys Fri Feb 16 23:09:50 2007 (45D69C2E) f7597000 f75a4000 netbios netbios.sys Fri Feb 16 22:58:29 2007 (45D69985) f75a7000 f75b0000 hidusb hidusb.sys Tue Mar 25 00:10:17 2003 (3E8000D9) f75c7000 f75d2000 ptilink ptilink.sys Fri Feb 16 23:06:38 2007 (45D69B6E) f75d7000 f75e1000 serenum serenum.sys Fri Feb 16 23:06:44 2007 (45D69B74) f7607000 f7612000 fdc fdc.sys unavailable (00000000) f7617000 f7625000 msgpc msgpc.sys Fri Feb 16 22:58:37 2007 (45D6998D) f7627000 f7630000 watchdog watchdog.sys Fri Feb 16 23:11:45 2007 (45D69CA1) f7637000 f7641000 dump_cpqcissm dump_cpqcissm.sys Fri Feb 23 20:48:45 2007 (45DFB59D) f7657000 f7660000 ndistapi ndistapi.sys Fri Feb 16 22:59:19 2007 (45D699B7) f7677000 f7681000 dump_diskdump dump_diskdump.sys Mon Feb 12 05:23:51 2007 (45D05C57) f7687000 f7692000 CpqCiDrv CpqCiDrv.sys Fri Mar 09 11:16:50 2007 (45F1A492) f76b7000 f76c6000 intelppm intelppm.sys Fri Feb 16 22:48:30 2007 (45D6972E) f7707000 f770f000 kdcom kdcom.dll Tue Mar 25 00:08:00 2003 (3E800050) f770f000 f7717000 BOOTVID BOOTVID.dll Tue Mar 25 00:07:58 2003 (3E80004E) f7717000 f771e000 pciide pciide.sys Tue Mar 25 00:04:46 2003 (3E7FFF8E) f771f000 f7726000 dmload dmload.sys unavailable (00000000) f773f000 f7747000 mnmdd mnmdd.SYS Tue Mar 25 00:07:53 2003 (3E800049) f7757000 f775f000 RDPCDD RDPCDD.sys Tue Mar 25 00:03:05 2003 (3E7FFF29) f7767000 f776f000 rasacd rasacd.sys Tue Mar 25 00:11:50 2003 (3E800136) f776f000 f7775300 HIDPARSE HIDPARSE.SYS Fri Feb 16 23:12:35 2007 (45D69CD3) f7777000 f777f000 mouhid mouhid.sys Tue Mar 25 00:03:12 2003 (3E7FFF30) f77a7000 f77ae000 dxgthk dxgthk.sys Tue Mar 25 00:05:52 2003 (3E7FFFD0) f77bf000 f77c4180 usbuhci usbuhci.sys Fri Feb 16 23:13:02 2007 (45D69CEE) f77c7000 f77cdb80 usbehci usbehci.sys Fri Feb 16 23:12:56 2007 (45D69CE8) f77cf000 f77d7000 OPRGHDLR OPRGHDLR.SYS Tue Mar 25 00:16:25 2003 (3E800249) f77df000 f77e6000 sysmgmt sysmgmt.sys Fri Nov 10 20:34:41 2006 (455544D1) f77e7000 f77ef000 audstub audstub.sys Tue Mar 25 00:09:12 2003 (3E800098) f780f000 f7817000 Fs_Rec Fs_Rec.SYS unavailable (00000000) f7817000 f781e000 Null Null.SYS unavailable (00000000) f781f000 f7826000 Beep Beep.SYS Tue Mar 25 00:03:04 2003 (3E7FFF28) f7897000 f789af80 symc810 symc810.sys Fri Dec 08 10:40:59 2000 (3A311D2B) f789b000 f789e460 cpqarry2 cpqarry2.sys Mon Nov 05 14:47:33 2001 (3BE708F5) f7999000 f799a280 swenum swenum.sys Fri Feb 16 23:05:56 2007 (45D69B44) f79a1000 f79a2580 USBD USBD.SYS Tue Mar 25 00:10:39 2003 (3E8000EF) f7a61000 f7a61d00 ldmirror ldmirror.sys Tue Jun 21 09:32:10 2005 (42B8410A) f7a62000 f7a62e80 mirrorflt mirrorflt.sys Tue Jun 21 09:32:28 2005 (42B8411C) Unloaded modules: f75e7000 f75f5000 imapi.sys Timestamp: unavailable (00000000) Checksum: 00000000 b9f71000 b9f85000 redbook.sys Timestamp: unavailable (00000000) Checksum: 00000000 ba0fb000 ba110000 cdrom.sys Timestamp: unavailable (00000000) Checksum: 00000000 f7807000 f780f000 Sfloppy.SYS Timestamp: unavailable (00000000) Checksum: 00000000 f75f7000 f7601000 Flpydisk.SYS Timestamp: unavailable (00000000) Checksum: 00000000 Closing open log file c:\debuglog.txt "Jon" wrote: > Hi there, > > The best way to deal with this is to run the crash dump through a > debugger - this will normally tell you exactly where the problem lies. > > This article describes how to get started with the debugger: > http://www.microsoft.com/whdc/devtools/debugging/debugstart.mspx > > It can be a bit unintuitive to begin with, but once you get the hang > of it, it makes dealing with crashes much easier. > > Regards > Jon > > > On Feb 7, 7:19 pm, PleaseHelpME > <PleaseHel...@discussions.microsoft.com> wrote: > > I have not been able to match specific events to a particular error. Has > > anyone resolved a similar problem? > > > > I have had 6 servers randomly reboot with the following event information: > > > > Event Type: Information > > Event Source: Save Dump > > Event Category: None > > Event ID: 1001 > > Date: 2/3/2008 > > Time: 12:57:55 AM > > User: N/A > > Computer: PHQOCR01 > > Description: > > The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 > > (0x00000020, 0x88455670, 0x884557a0, 0x1a260008). A dump was saved in: > > C:\WINDOWS\MEMORY.DMP. >
Guest Jon Posted February 11, 2008 Posted February 11, 2008 Re: 2003 SP2 Servers rebooting from a bugcheck/system failure: sto Re: 2003 SP2 Servers rebooting from a bugcheck/system failure: sto That seems to point to a problem with the Compaq system management software. I would first check out Insight Manager to see if that shows any specific problems and then upgrade all the compaq software (drivers, insight manager agents) - if you have Insight Manager setup and configured this should allow you to upgrade them all easily Regards Jon On Feb 11, 9:20 pm, PleaseHelpME <PleaseHel...@discussions.microsoft.com> wrote: > If this check worked properly...it looks like the problem may be a hardware > driver. Here is the output: > > Opened log file 'c:\debuglog.txt' > > Microsoft ® Windows Debugger Version 6.8.0004.0 X86 > Copyright © Microsoft Corporation. All rights reserved. > > Loading Dump File [C:\Mini020608-01.dmp] > Mini Kernel Dump File: Only registers and stack trace are available > > Symbol search path is: > SRV*c:\symbols*http://msdl.microsoft.com/download/symbols > Executable search path is: > C:\WINNT;C:\WINNT\system32;C:\WINNT\system32\drivers > Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free > x86 compatible > Product: Server, suite: Enterprise TerminalServer SingleUserTS > Built by: 3790.srv03_sp2_gdr.070304-2240 > Kernel base = 0x80800000 PsLoadedModuleList = 0x808af9c8 > Debug session time: Wed Feb 6 21:00:37.485 2008 (GMT-7) > System Uptime: 1 days 16:57:47.734 > Loading Kernel Symbols > ............................................................................................................................. > Loading User Symbols > Loading unloaded module list > ..... > ******************************************************************************* > * > * > * Bugcheck Analysis > * > * > * > ******************************************************************************* > > Use !analyze -v to get detailed debugging information. > > BugCheck 19, {20, 881a3a48, 881a3b78, 1a260005} > > *** WARNING: Unable to verify timestamp for cpqasm2.sys > *** ERROR: Module load completed but symbols could not be loaded for > cpqasm2.sys > > Probably caused by : cpqasm2.sys ( cpqasm2+2662 ) > > Followup: MachineOwner > --------- > > 2: kd> !analyze -v;r;kv;lmtn;.logclose;q > ******************************************************************************* > * > * > * Bugcheck Analysis > * > * > * > ******************************************************************************* > > BAD_POOL_HEADER (19) > The pool is already corrupt at the time of the current request. > This may or may not be due to the caller. > The internal pool links must be walked to figure out a possible cause of > the problem, and then special pool applied to the suspect tags or the driver > verifier to a suspect driver. > Arguments: > Arg1: 00000020, a pool block header size is corrupt. > Arg2: 881a3a48, The pool entry we were looking for within the page. > Arg3: 881a3b78, The next pool entry. > Arg4: 1a260005, (reserved) > > Debugging Details: > ------------------ > > BUGCHECK_STR: 0x19_20 > > POOL_ADDRESS: 881a3a48 > > CUSTOMER_CRASH_COUNT: 1 > > DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP > > PROCESS_NAME: cqmgserv.exe > > CURRENT_IRQL: 1 > > IRP_ADDRESS: 891ca668 > > LAST_CONTROL_TRANSFER: from 8089c8ff to 8087c480 > > > STACK_COMMAND: kb > > FOLLOWUP_IP: > cpqasm2+2662 > ba41e662 ?? ??? > > SYMBOL_STACK_INDEX: a > > SYMBOL_NAME: cpqasm2+2662 > > FOLLOWUP_NAME: MachineOwner > > MODULE_NAME: cpqasm2 > > IMAGE_NAME: cpqasm2.sys > > DEBUG_FLR_IMAGE_TIMESTAMP: 455544d1 > > FAILURE_BUCKET_ID: 0x19_20_cpqasm2+2662 > > BUCKET_ID: 0x19_20_cpqasm2+2662 > > Followup: MachineOwner
Recommended Posts