- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- BugCheck,STOP:0x0000000A(0x00000000,0xD000001F,0x0...
ProLiant Servers (ML,DL,SL)
1819800
Members
3044
Online
109607
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-21-2009 12:58 PM
тАО02-21-2009 12:58 PM
BugCheck,STOP:0x0000000A(0x00000000,0xD000001F,0x00000000,0xE065B523)
One of our ProLiant DL580 G3, rebooted unexpected with BugCheck,STOP:0x0000000A(0x00000000,0xD000001F,0x00000000,0xE065B523)
ASR Detected by System ROM and hence we could not get the memory dump file created.
We also had number of following warning events
Event Type: Warning
Event Source: NfsSvr
Event Category: None
Event ID: 1021
Date: 2/2/2009
Time: 4:02:01 AM
User: N/A
Computer: xxxxx01
Description:
There was a mapping failure.
Event Type: Error
Event Source: crypt32
Event Category: None
Event ID: 8
Date: 2/20/2009
Time: 12:47:51 PM
User: N/A
Computer: xxxxx01
Description:
Failed auto update retrieval of third-party root list sequence number from:
<> with error: This operation returned because the timeout period expired.
With the above information can anyone suggest what could be the reason for the server reboot un-expected.
ASR Detected by System ROM and hence we could not get the memory dump file created.
We also had number of following warning events
Event Type: Warning
Event Source: NfsSvr
Event Category: None
Event ID: 1021
Date: 2/2/2009
Time: 4:02:01 AM
User: N/A
Computer: xxxxx01
Description:
There was a mapping failure.
Event Type: Error
Event Source: crypt32
Event Category: None
Event ID: 8
Date: 2/20/2009
Time: 12:47:51 PM
User: N/A
Computer: xxxxx01
Description:
Failed auto update retrieval of third-party root list sequence number from:
<> with error: This operation returned because the timeout period expired.
With the above information can anyone suggest what could be the reason for the server reboot un-expected.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-21-2009 08:20 PM
тАО02-21-2009 08:20 PM
Re: BugCheck,STOP:0x0000000A(0x00000000,0xD000001F,0x00000000,0xE065B523)
I some times think people should mention what they have done first since for these errors I usually google them so maybe you already googled it and found this
http://support.microsoft.com/kb/836049
http://support.microsoft.com/kb/910835
is everything up to date?
proliant support pack?
firmwate CD?
http://support.microsoft.com/kb/836049
http://support.microsoft.com/kb/910835
is everything up to date?
proliant support pack?
firmwate CD?
Didn't your momma teach you to say thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-25-2009 01:06 PM
тАО02-25-2009 01:06 PM
Re: BugCheck,STOP:0x0000000A(0x00000000,0xD000001F,0x00000000,0xE065B523)
Every thing on the server was upto date, inclding PSP verion, BIOS, Antivirus etc.
No such activity was recorded on the server.
One thing we noticed was /3GB and /PAE switch enabled.
nfssvr.sys on the server
File Version 8.0.2254.1
Number of failure audit
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537
Date: 2/20/2009
Time: 11:53:10 AM
User: NT AUTHORITY\SYSTEM
Computer: XXXXXXX
Description:
Logon Failure:
Reason: An error occurred during logon
User Name:
Domain:
Logon Type: 3
Logon Process: SFU NFS
Authentication Package: Kerberos
Workstation Name: XXXXXXX
Status code: 0xC000018B
Substatus code: 0x0
Caller User Name: XXXXXXX$
Caller Domain: HA
Caller Logon ID: (0x0,0x3E7)
Caller Process ID: 4
Transited Services: -
Source Network Address: -
Source Port: -
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 535
Date: 2/20/2009
Time: 11:53:10 AM
User: NT AUTHORITY\SYSTEM
Computer: XXX
Description:
Logon Failure:
Reason: The specified account's password has expired
User Name: xxxxxxx
Domain: XXX
Logon Type: 3
Logon Process: SFU NFS
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Workstation Name:
Caller User Name: xxxxx$
Caller Domain: HA
Caller Logon ID: (0x0,0x3E7)
Caller Process ID: 4
Transited Services: -
Source Network Address: -
Source Port: -
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
No such activity was recorded on the server.
One thing we noticed was /3GB and /PAE switch enabled.
nfssvr.sys on the server
File Version 8.0.2254.1
Number of failure audit
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537
Date: 2/20/2009
Time: 11:53:10 AM
User: NT AUTHORITY\SYSTEM
Computer: XXXXXXX
Description:
Logon Failure:
Reason: An error occurred during logon
User Name:
Domain:
Logon Type: 3
Logon Process: SFU NFS
Authentication Package: Kerberos
Workstation Name: XXXXXXX
Status code: 0xC000018B
Substatus code: 0x0
Caller User Name: XXXXXXX$
Caller Domain: HA
Caller Logon ID: (0x0,0x3E7)
Caller Process ID: 4
Transited Services: -
Source Network Address: -
Source Port: -
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 535
Date: 2/20/2009
Time: 11:53:10 AM
User: NT AUTHORITY\SYSTEM
Computer: XXX
Description:
Logon Failure:
Reason: The specified account's password has expired
User Name: xxxxxxx
Domain: XXX
Logon Type: 3
Logon Process: SFU NFS
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Workstation Name:
Caller User Name: xxxxx$
Caller Domain: HA
Caller Logon ID: (0x0,0x3E7)
Caller Process ID: 4
Transited Services: -
Source Network Address: -
Source Port: -
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP