Post Error 1719 P410i
Contents |
Internet of Things Small and Medium Business Service Providers All Solutions Services Advise, Transform and Manage Financing and Flexible Capacity IT Support smart array p410i in slot 0 Services Education and Training Services All Services Products Integrated Systems 1783 drive array controller failure p410i Composable Systems Converged Systems Hyper Converged Systems Blade Systems Infrastructure Management Software Application Lifecycle post error 1719 a controller failure event occurred prior to this power up 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
Hp Post Error 1719
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 a controller failure event occurred prior to this power up 0x13 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
6.40 (or Earlier) May Halt with "Lockup Code = 0xAB" Around 64, 128, or 256 Days NOTICE: The information in this document, including products and software versions, is current as of the Release hp post error codes Date. This document is subject to change without notice. Release Date: 2015-06-24
Fbwc
Last Updated: 2016-03-09 DESCRIPTION Document Version Release Date Details 4 06/24/2015 Added Service Pack for ProLiant (SPP) as permanent
Uncorrectable Machine Check Exception
fix in Resolution. 3 07/11/2014 Added Windows Server as an affected operating system and added the Windows Server component for HP Smart Array Controller Firmware Version 6.48 to the Resolution. 2 http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04325462&sp4ts.oid=3883890 07/03/2014 Updated the Scope to restrict this issue to servers running Linux, and updated the Resolution with Smart Array Controller Firmware Version 6.48, which corrects this issue. 1 06/10/2014 Original Document Release. HP Smart Array Controllers listed in the Scope section (below) configured with one or more SATA Hard Disk Drives (HDDs) or Solid State Drives (SSDs) configured as Online Spare Drives and http://h20628.www2.hp.com/km-ext/content-webapp/document?docId=emr_na-c04325462 running Firmware Version 6.40 (or earlier) may halt with "lockup code = 0xab" after running around 64, 128, or 256 days. When this occurs, the following Power-On Self-Test (POST) and Integrated Management Log (IML) error messages will be generated: POST Error Message 1719-Slot 0 Drive Array - A controller failure event occurred prior to this power-up. (Previous lock up code = 0xab) IML Error Message 1719 - A controller failure event occurred prior to this power-up SCOPE Any HP ProLiant server listed under Platforms Affected configured with any of the following HP Smart Array Controllers running Firmware Version 6.40 (or earlier): HP Smart Array P212 Controller HP Smart Array P410 Controller HP Smart Array P410i Controller HP Smart Array P411 Controller HP Smart Array P711m Controller HP Smart Array P712m Controller HP Smart Array P812 Controller Note: This issue occurs only on HP Smart Array Controllers with one or more HP SATA HDDs or SSDs configured as Online Spare Drives. Smart Array Controllers configured with SAS HDDs or SSDs are NOT affected. RESOLUTION To correct and prevent this issue, update the Smart Array Controller Firmware include
THIS DISCUSSION HP 358772 Followers Follow Hewlet Packard Join the Community! Creating your account https://community.spiceworks.com/topic/347616-hpcisss2-crashing-dl370-g6-with-server-2012 only takes a few minutes. Join Now So before anyone says it I know the DL370 G6 doesn't officially support Server 2012 but the P410i are the same in the G7's and that appears to be the issue. Anyway, every now and then my both my DL370 G6's BSOD / what ever Microsoft call it now and the a bug post error check shows: Probably caused by : HpCISSs2.sys ( HpCISSs2+4c74 ) After doing some googling, I found lots of places saying check the BIOS version, controller firmware etc... which are all up-to-date. I've looked and looked but can't work out why its doing it, it hadn't done it for about two weeks then last night one of them died and post error 1719 then again this morning. No reason, backups wern't running, no updates installed, no llamas eating cables in the server room, it just doesn't make sense and its making me crazzzzzyyy and look bad :( Anyone got any thoughts? Edited Jun 13, 2013 at 12:13 UTC Reply Subscribe RELATED TOPICS: DL370 G6 Server 2012 Driver Support?? Server 2012 R2 - Authentication Issues? Server 2012 Build   19 Replies Pure Capsaicin OP akp982 Jun 13, 2013 at 9:26 UTC akp982 is an IT service provider. Full Bug Check 0: kd> !analyze -v ******************************************************************************* * * * 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: fffffa88193a2110, memory referenced Arg2: 000000000000000b, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff88000e1ec74, address which referenced memory Debugging Details: ------------------ Page 7d306f not pre