- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Proliant DL380 G3 Memory Problems
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
06-07-2004 12:09 AM
06-07-2004 12:09 AM
Proliant DL380 G3 Memory Problems
When I try to boot a dual Xeon box, I get an error message: NMI Parity check, memory parity error, sys has halted
I have tried different memory (which I know works), reseating the memory but still no luck. Has anyone got any ideas? Also tried the usual bios update.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2004 12:21 AM
06-07-2004 12:21 AM
Re: Proliant DL380 G3 Memory Problems
Well sems to be memory problem Use the HP Online Daignostics tool from HP website to scan memory under continious loops.
Check for memory part number :
34 256-MB PC2100 Registered DDR SDRAM 300699-001
35 512-MB PC2100 Registered DDR SDRAM 300700-001
36 1-GB PC2100 Registered DDR SDRAM 300701-001
2-GB PC2100 Registered DDR SDRAM 300702-001
Regards,
Prashant S
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2004 12:34 AM
06-07-2004 12:34 AM
Re: Proliant DL380 G3 Memory Problems
First of all, memory error does not necessarily mean errors on the physical DIMMs only, there is memory on the motherboard too (!!).
Last time, I ran into a similar scenario on a Proliant DL580 G2 with the same memory/parity error (hardware malfunction) HP had to replace the motherboard to fix the problem. Hows this for a thought?
As Prashant indicated the server diagnostics (INSPECT) utility, you could try that but I would be seriously considering a motherboard replacement test with the same memory modules as a troubleshooting step.
Hope it was of help and don't forget to assign points:)
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2004 02:31 AM
06-07-2004 02:31 AM
Re: Proliant DL380 G3 Memory Problems
I have awarded the points thus:
2 points for taking the time and effort to answer
5 points for closest answer to solving problem
Will award remaining points if it resolves issue
Thanks again for helping!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2004 07:47 AM
06-07-2004 07:47 AM
Re: Proliant DL380 G3 Memory Problems
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2004 04:38 PM
06-07-2004 04:38 PM
Re: Proliant DL380 G3 Memory Problems
We had the same problem, we tried replaceing all the components (Processor, memory, Raid controller etc.) but no luck, But the problem solved after replaceing the Motherboard.
Regards
Robin