- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Netservers
- >
- LXR 8500 hangs with blue screen
Netservers
1754355
Members
4815
Online
108813
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
11-26-2004 02:13 AM
11-26-2004 02:13 AM
LXR 8500 hangs with blue screen
Hello, I am Panos,
an lxr-8500 server hangs suddenly with a blue screen and the following text: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009c (0x00000004, 0x00000000, 0xb2000000, 0x00020151). Microsoft Windows 2000 [v15.2195]. A full dump was not saved. (eventid 1000)
Thanks & Regards
an lxr-8500 server hangs suddenly with a blue screen and the following text: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009c (0x00000004, 0x00000000, 0xb2000000, 0x00020151). Microsoft Windows 2000 [v15.2195]. A full dump was not saved. (eventid 1000)
Thanks & Regards
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2004 01:36 AM
11-27-2004 01:36 AM
Re: LXR 8500 hangs with blue screen
Panos, looks again like hardware to me, maybe bad memory, cache or pagefile....
STOP: 0x0000009C (0x00000004, 0x00000000, 0xb2000000, 0x00020151) ...
Article ID : 329284
Last Review : June 8, 2004
Revision : 1.0
This article was previously published under Q329284
For a Microsoft Windows NT 4.0 and Microsoft Windows 2000 version of this article, see 162363.
On this Page
SYMPTOMS
CAUSE
STATUS
MORE INFORMATION
SYMPTOMS
You may receive the following Stop error message:
STOP: 0x0000009C (0x00000004, 0x00000000, 0xb2000000, 0x00020151)
"MACHINE_CHECK_EXCEPTION"
The four parameters inside the parentheses may vary.
CAUSE
This behavior occurs because your computer processor detected and reported an unrecoverable hardware error to Windows XP. To do this, the processor used the Machine Check Exception (MCE) feature of Pentium processors or the Machine Check Architecture (MCA) feature of some Pentium Pro processors. The following factors may cause this error message: â ¢ System bus errors
â ¢ Memory errors that may include parity or Error Correction Code (ECC) problems
â ¢ Cache errors in the processor or hardware
â ¢ Translation Lookaside Buffers (TLB) errors in the processor
â ¢ Other CPU-vendor specific detected hardware problems
â ¢ Vendor-specific detected hardware problems
STATUS
This behavior is by design.
MORE INFORMATION
A machine check exception occurs when Windows XP and your hardware platform cannot recover from a hardware error so that the system can continue to run successfully and reliably. More specific diagnosis of machine check exceptions is difficult, and there is no general solution. Contact your hardware manufacturer or a computer hardware technician for help with troubleshooting this issue.
Machine check exceptions are frequently caused by one of the following conditions: â ¢ You are running the processor or mainboard beyond its specifications. For example, you are overclocking the processor or bus. We recommend that you run your hardware at the manufacturer-rated speeds.
â ¢ Noisy power, overstressed power strips, outmatched power supplies and failing power supplies can destabilize your computer. Make sure that you have a stable, reliable power supply to your computer.
â ¢ Extreme thermal conditions caused by the failure of cooling devices such as fans may damage your computer. Make sure that your cooling devices are all working.
â ¢ You have damaged memory or memory that is not the correct type for your computer. If you recently changed the memory configuration, revert to the previous configuration to determine what is wrong. Make sure that you are using the correct memory for your computer.
Note Your hardware may support additional error logging features that capture the machine check exception and suggest a more specific solution.
The Pentium and Pentium Pro processors provide a mechanism to detect and to report hardware-related problems such as memory parity errors and cache errors. To signal a hardware error, the processor signals the detection of a machine check error by generating a machine check exception (Interrupt 18). Windows XP reports that the error occurred and displays parameters that you can use to decode the exception. Contact your hardware vendor or processor manufacturer for information about the Machine Check Architecture, or see the Intel Pentium Pro Family Developer's Manual - Volume 3: Oper
STOP: 0x0000009C (0x00000004, 0x00000000, 0xb2000000, 0x00020151) ...
Article ID : 329284
Last Review : June 8, 2004
Revision : 1.0
This article was previously published under Q329284
For a Microsoft Windows NT 4.0 and Microsoft Windows 2000 version of this article, see 162363.
On this Page
SYMPTOMS
CAUSE
STATUS
MORE INFORMATION
SYMPTOMS
You may receive the following Stop error message:
STOP: 0x0000009C (0x00000004, 0x00000000, 0xb2000000, 0x00020151)
"MACHINE_CHECK_EXCEPTION"
The four parameters inside the parentheses may vary.
CAUSE
This behavior occurs because your computer processor detected and reported an unrecoverable hardware error to Windows XP. To do this, the processor used the Machine Check Exception (MCE) feature of Pentium processors or the Machine Check Architecture (MCA) feature of some Pentium Pro processors. The following factors may cause this error message: â ¢ System bus errors
â ¢ Memory errors that may include parity or Error Correction Code (ECC) problems
â ¢ Cache errors in the processor or hardware
â ¢ Translation Lookaside Buffers (TLB) errors in the processor
â ¢ Other CPU-vendor specific detected hardware problems
â ¢ Vendor-specific detected hardware problems
STATUS
This behavior is by design.
MORE INFORMATION
A machine check exception occurs when Windows XP and your hardware platform cannot recover from a hardware error so that the system can continue to run successfully and reliably. More specific diagnosis of machine check exceptions is difficult, and there is no general solution. Contact your hardware manufacturer or a computer hardware technician for help with troubleshooting this issue.
Machine check exceptions are frequently caused by one of the following conditions: â ¢ You are running the processor or mainboard beyond its specifications. For example, you are overclocking the processor or bus. We recommend that you run your hardware at the manufacturer-rated speeds.
â ¢ Noisy power, overstressed power strips, outmatched power supplies and failing power supplies can destabilize your computer. Make sure that you have a stable, reliable power supply to your computer.
â ¢ Extreme thermal conditions caused by the failure of cooling devices such as fans may damage your computer. Make sure that your cooling devices are all working.
â ¢ You have damaged memory or memory that is not the correct type for your computer. If you recently changed the memory configuration, revert to the previous configuration to determine what is wrong. Make sure that you are using the correct memory for your computer.
Note Your hardware may support additional error logging features that capture the machine check exception and suggest a more specific solution.
The Pentium and Pentium Pro processors provide a mechanism to detect and to report hardware-related problems such as memory parity errors and cache errors. To signal a hardware error, the processor signals the detection of a machine check error by generating a machine check exception (Interrupt 18). Windows XP reports that the error occurred and displays parameters that you can use to decode the exception. Contact your hardware vendor or processor manufacturer for information about the Machine Check Architecture, or see the Intel Pentium Pro Family Developer's Manual - Volume 3: Oper
most time the day i have to mask my contempt for the a-holes in charge......
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