- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers - Netservers
- >
- Re: ML350 G3 Stop Error 0x0000000A (0BAD0b0e4
ProLiant Servers - Netservers
1755661
Members
3570
Online
108837
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
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
тАО04-29-2005 07:49 AM
тАО04-29-2005 07:49 AM
ML350 G3 Stop Error 0x0000000A (0BAD0b0e4
A Windows 2000 sever has been rebooting at the beginning of the workday. This started 2 weeks ago.
0x0000000A (0BAD0b0e4,0x00000000, 0x804518D2, 0x000000000)
Windows 2k4 sp4
ML350 G3 1-2.2 gHz proc
542 RAID controller- Not other adds or NonHP equip
1gb HP MEM
HP driver set 7.40 Updated to most recent as of 4/26/2005)
Original BIOS
AD Primary
DNS
DHCP
Notes Server 6.5.1
CA eTrust AV 7.1.192 w/Mail option.
RE:BAD0B0E4 memory space?? Does anyone know driver occupies that space?
0x0000000A (0BAD0b0e4,0x00000000, 0x804518D2, 0x000000000)
Windows 2k4 sp4
ML350 G3 1-2.2 gHz proc
542 RAID controller- Not other adds or NonHP equip
1gb HP MEM
HP driver set 7.40 Updated to most recent as of 4/26/2005)
Original BIOS
AD Primary
DNS
DHCP
Notes Server 6.5.1
CA eTrust AV 7.1.192 w/Mail option.
RE:BAD0B0E4 memory space?? Does anyone know driver occupies that space?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-29-2005 07:51 AM
тАО04-29-2005 07:51 AM
Re: ML350 G3 Stop Error 0x0000000A (0BAD0b0e4
Stop Error revision
0x0000000A (0BAD0b0e4,0x000000002, 0x00000001, 0x8006543A)
0x0000000A (0BAD0b0e4,0x000000002, 0x00000001, 0x8006543A)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-29-2005 08:58 AM
тАО04-29-2005 08:58 AM
Re: ML350 G3 Stop Error 0x0000000A (0BAD0b0e4
Hi Glenn,
STOP 0x0000000A indicates a kernel mode process or driver attempted to access a memory address that it did not have permission to access. The most common cause of this error is a bad or corrupt pointer that references an incorrect location in memory
Therefore, the cause of the problem could be two
1. A driver is trying to reference an invalid or incorrect memory adress
or
2. You have a bad memory module in your system
You can check the IML(Integrated Management Log) or from the windows system event view to mention a few
Resolution
1. Try to update the dirver for all controllers you have in the system. Latest driver can be downloaded from this link
http://h18023.www1.hp.com/support/files/server/us/family/model/4678.html?lang=en&cc=us
Select you operating system you have in your server
2. Check if you have a bad memory stick
Regards
Amha Kassa
STOP 0x0000000A indicates a kernel mode process or driver attempted to access a memory address that it did not have permission to access. The most common cause of this error is a bad or corrupt pointer that references an incorrect location in memory
Therefore, the cause of the problem could be two
1. A driver is trying to reference an invalid or incorrect memory adress
or
2. You have a bad memory module in your system
You can check the IML(Integrated Management Log) or from the windows system event view to mention a few
Resolution
1. Try to update the dirver for all controllers you have in the system. Latest driver can be downloaded from this link
http://h18023.www1.hp.com/support/files/server/us/family/model/4678.html?lang=en&cc=us
Select you operating system you have in your server
2. Check if you have a bad memory stick
Regards
Amha Kassa
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP