An Unrecoverable System Error Has Occurred Error Code 0x0000002d 0x00000000
Contents |
Things Small and Medium Business Service Providers All Solutions Services Advise, Transform and Manage Financing and Flexible Capacity IT Support Services Education and Training Services All Services Products Integrated hp an unrecoverable system error has occurred error code 0x0000002d 0x00000000 Systems Composable Systems Converged Systems Hyper Converged Systems Blade Systems
An Unrecoverable System Error Nmi Has Occurred System Error Code 0x0000002b 0x00000000
Infrastructure Management Software Application Lifecycle Management Application Delivery Management Big Data Analytics DevOps Enterprise Security Hybrid and an unrecoverable system error has occurred error code 0x0000002b 0x00000000 Private Cloud Information Governance Information Management IT Service Management Operations Management Server Management Software as a Service (SaaS) Software-Defined Data Center Storage Management All Software Servers Rack
An Unrecoverable System Error (nmi) Has Occurred Proliant
Servers Tower Servers Blade Servers Density Optimized Mission Critical Servers Servers for Cloud Server Management All Servers Storage All-flash and Hybrid Storage Midrange and Enterprise Storage Entry Storage Systems Data Availability, Protection and Retention Software Defined Storage Management and Orchestration Storage Networking All Storage Networking Switches Routers Access Points and Controllers Wireless LAN Campus and Branch Networking Data Center Networking Wide Area Network Software Defined Networking Network Functions Virtualization Network Management All Networking About UsSupportClearType to search2086159Solutions Transform to a Hybrid Infrastructure Protect Your Digital Enterprise Empower the Data-Driven Organization Enable Workplace Productivity Cloud Security Big Data Mobility Infrastructure Internet of Things Small and Medium Business Service Providers All Solutions Services Advise, Transform and Manage Financing and Flexible Capacity IT Support Services Education and Training Services All Services Products Integrated Systems Composable Systems Converged Systems Hyper Converged Systems Blade Systems Infrastructure Management Software Application Lifecycle Management Application Delivery Management Big Data Analytics DevOps Enterprise Security Hybrid and Private Cloud Information Governance Information Management IT Service Management Operations Management Server Management Software as a Service (SaaS) Software-Defined Data Center Storage Management All Software Servers Rack Servers Tower Servers Blade Servers Density Optimized Mission Critical Servers Servers for Cloud Server Management All Servers Storage All-flash and Hybrid Storage Midrange and Enterprise Storage Entry Storage Systems Data Availability, Protection and Retention Software Defined Storage
team. Help! My Server is Shutting Down for No Apparent Reason ★★★★★★★★★★★★★★★ ntdebugMarch 19, 20093 0 0 0 Hello - Rob here with the GES team, and I have this nugget to pass on to you. I recently worked an issue where a Windows server rebooted intermittently for no apparent reason. The Windows System Event log did not yield any clues, other than this Event ID 6008- Log Name: System.evt Source: EventLog Date: 25-8-2008 19:06:58 Event ID: 6008 Task Category: None Level: Error Keywords: Classic User: N/A Computer: A2A000001 https://community.hpe.com/t5/Network-Attached-Storage-NAS/New-DL-380-G5-Server-2003-R2-x64-crashing-every-day/td-p/1048192 Description: The previous system shutdown at 6:54:04 PM on 8/25/2008 was unexpected. There were no other symptoms or patterns to which the unexpected shutdown could be related. The shutdown could occur anytime of the day. Eventually we attached a debugger to see if we could catch anything, but this wasn’t successful. Next we looked at the manufacturer’s mechanismused tolog errors and found this piece of https://blogs.msdn.microsoft.com/ntdebugging/2009/03/19/help-my-server-is-shutting-down-for-no-apparent-reason/ information - An Unrecoverable System Error has occurred (Error code 0x0000002D, 0x00000000) Note - each vendor hastheir own way to handle error codes. We noticed a one to one relationship with the vendor error aboveand the Event ID 6008 messages in the Windows System Event log. So we engaged the hardware vendor who determined this error indicated an error on the PCI bus. They also informed us that this kind of error asserts an NMI on the bus. To narrow down which component was causing the error, we set the NMICrashDump DWORD value under the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl This is described in detail in the article, “927069 How to generate a complete crash dump file or a kernel crash dump file by using an NMI on a Windows-based system” http://support.microsoft.com/default.aspx?scid=kb;EN-US;927069 This registry value causes the machine to bugcheck with a STOP 0x80 (NMI_HARDWARE_FAILURE) when Windows detects an NMI, thus producing a dump file, or, if a debugger is attached, it breaks into the debugger After setting this registry value we hooked up the debugger again and waited… after awhile we got lucky because the debugger intercepted a ST
at least the hp-wdt driver), any system hangs or panics caused by NMI's (non-maskable interrupts) will be logged to the IML (Integrated Management Log) and can be http://blog.nachotech.com/?p=81 viewed using iLO. The IML log is on the System Status page of the iLO web interface. This is great, but the error messages logged are not very user friendly. NMI's will be logged as Unrecoverable System Errors something like this: An Unrecoverable System Error has occurred (Error code 0x0000002D, 0x00000000 The first 32-bit error code can be decoded using an unrecoverable this table (which came from the man page for the hp-wdt driver): 00h (0x00000000) No source found 01h (0x00000001) Uncorrectable Memory Error 1Bh (0x0000001B) ASR NMI 20h (0x00000020) PCI Parity Error 27h (0x00000027) NMI Button Press 28h (0x00000028) SB_BUS_NMI 29h (0x00000029) ILO Doorbell NMI 2Ah (0x0000002A) ILO IOP NMI 2Bh (0x0000002B) ILO Watchdog NMI 2Ch (0x0000002C) Proc Throt NMI 2Dh (0x0000002D) an unrecoverable system Front Side Bus NMI 2Fh (0x0000002F) PCI Express Error 30h (0x00000030) DMA controller NMI 31h (0x00000031) Hypertransport/CSI Error Hopefully, this will help you narrow down the real cause of the NMI. Tags: health, HP BladeSystem, hp proliant, iLO One Comment on "Interpreting (decoding) NMI sources from IML log messages" liu March 23rd, 2015 at 10:01 pm Hi, my error code is 0x00000002, 0x00020002. Leave a Reply Name (required) Mail (will not be published) (required) Website Best Articles En masse update of iLO firmware Find all the iLO's on your network Virtual Serial Port logging with Conserver Categories BladeSystem iLO iPhone Linux Macintosh OS X Operations ProLiant scripting System Administration Telcel Uncategorized wordpress Meta Log in Valid XHTML WordPress Archives February 2010 November 2009 September 2009 August 2009 May 2009 April 2009 March 2009 December 2008 September 2008 Tag Cloud 3G Add new tag blades BladeSystem bug firewall hack health HP HP BladeSystem hp proliant iLO iPhone Linux script serial console shell stickies Telcel terminal wordpress Help Animals © 2007 NachoTech Blog - StudioPress Theme Full RSS - Comments RSS