- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: STOP messages on Dual CPU Systems
ProLiant Servers (ML,DL,SL)
1753272
Members
5219
Online
108792
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
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
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
03-22-2001 04:00 PM
03-22-2001 04:00 PM
STOP messages on Dual CPU Systems
Hello,
We have 4 Compaq proliant systems, 3 with dual CPU and 1 with single CPU. On the systems with dual cpu we get different stop messages (oxA, 0xE, 0x1E, 0x7A and 0x7E). Because the systems have 768 MB memory and less memory free on C:, we can't save debug info. I saw the last STOP error was 0xA in HAL.DLL. We get these STOP erros approx 2 times a month on each system. The single CPU system has no problem (this system is used as file and print server and exchange server). The dual CPU systems are used as application servers with Citrix metaframe 1.8. All systems have terminal server SP6 and metaframe SP2. There are also reboots with no stop messages, these are logged in the event log with event ID 4203. All other reboots are logged with event ID 4188.
Thanks in advance and kind regards,
Peter Hazelaar
We have 4 Compaq proliant systems, 3 with dual CPU and 1 with single CPU. On the systems with dual cpu we get different stop messages (oxA, 0xE, 0x1E, 0x7A and 0x7E). Because the systems have 768 MB memory and less memory free on C:, we can't save debug info. I saw the last STOP error was 0xA in HAL.DLL. We get these STOP erros approx 2 times a month on each system. The single CPU system has no problem (this system is used as file and print server and exchange server). The dual CPU systems are used as application servers with Citrix metaframe 1.8. All systems have terminal server SP6 and metaframe SP2. There are also reboots with no stop messages, these are logged in the event log with event ID 4203. All other reboots are logged with event ID 4188.
Thanks in advance and kind regards,
Peter Hazelaar
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2001 04:00 PM
05-26-2001 04:00 PM
Re: STOP messages on Dual CPU Systems
Peter,
I looked up Event ID 4188 and 4203 in MS Technet and found NO information.
Because the problem occures in Hal.dll, i would try to reseat the processor and Voltage Regulator modules in the suspect units. There are only 6 files that change when the Multi-Processor HAL is installed and this is one of them.
Along similar lines you could manually extract all 6 files from the appropriate service pack and copy them to the unit. These files are listed in Q156358 at support.microsoft.com
I looked up Event ID 4188 and 4203 in MS Technet and found NO information.
Because the problem occures in Hal.dll, i would try to reseat the processor and Voltage Regulator modules in the suspect units. There are only 6 files that change when the Multi-Processor HAL is installed and this is one of them.
Along similar lines you could manually extract all 6 files from the appropriate service pack and copy them to the unit. These files are listed in Q156358 at support.microsoft.com
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