Computing.Net > Forums > Windows NT > 0x0000009C (Machine_Check_Exception) Help!

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to get for your free account now!

0x0000009C (Machine_Check_Exception) Help!

Reply to Message Icon

Name: Kenneth Andrews
Date: April 8, 1999 at 21:27:54 Pacific
Comment:

Hello,

I am installing a fresh copy of NT 4.0 Server. As normal, when install begins, it copies all files to the HD and then reboots. Next, the various drivers are loaded and NT actually begins to load (blue screen with small letters). I get the normal "Windows NT Version 4.0", etc. Then, as loading continues, I get a "STOP" error message. The message is as follows:

***STOP: 0x0000009C (0x00000000,0x00000000,0xB2000100,0x00000800).
MACHINE_CHECK_EXCEPTION

The hardware is as follows:

* SuperMicro S2DGU Bios V1.3C Dual Proc
* Intel Xeon PIII 500 Mhz 512K (single)
* 256MB ECC SDRAM
* ICP Vortex Raid Controller (known to be NT compatible)
* Two Seagate Baracuda 4.3Gig HD's Raid 1
* SCSI CD-ROM
* ATI 3d AGP Card (8 MB RAM)

Through the process of elimination and testing, we have verified that all of the components are OK. I even tried an install using all of the components with a celeron and PII motherboard. Everything worked OK. There seems to be something going on with that Xeon and the MB.

Also, to test the Xeon, I loaded 98 on the machine. Worked like a champ - no problems (possibly due to 98 not checking the Machine Check Registers??!)

Please let me know if you have any feedback. I am now desperate as I've exhaused my technical knowledge and the resources of SuperMicro, Intel, and Microsoft (shouldn't have even tried MS - the rep didn't even know what the message referenced). At this point, everyone is pointing fingers.

If possible, please respond to my e-mail or e-mail me that you left a message here as it is difficult for me to visit here regularly.

Thank you *VERY* much for your time and help!

Kenneth Andrews
kandrews_1@hotmail.com
248-577-3610


Report Offensive Message For Removal

Sponsored Link
Ads by Google

Response Number 1
Name: Kurt Skjold Johannessen
Date: May 27, 1999 at 15:30:45 Pacific
Reply:

STOP: 0x0000009C (parameter, parameter, parameter, parameter)
MACHINE_CHECK_EXCEPTION

A Fatal Machine Check Exception has occurred. The computer processor detected a hardware error and reported it to Windows NT using the Machine Check Exception (MCE) feature of Pentium processors or the Machine Check Architecture (MCA) feature of some Pentium Pro processors.

Windows NT Server and Workstation version 4.0 have the ability to report exceptions generated by the MCE or MCA features.

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 NT simply reports the fact that the error occurred and displays parameters that you can use to decode the exception. Contact your hardware vendor or processor manufacturer for information regarding the Machine Check Architecture or consult the Intel Pentium Pro Family Developer's Manual - Volume 3: Operating System Writer's Manual.

Parameters:

If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:

Parameter Description
1 Low 32 bits of P5_MC_TYPE MSR
2
3 High 32 bits of P5_MC_ADDR MSR
4 Low 32 bits of P5_MC_ADDR MSR

If the processor also has MCA feature available (For example Intel Pentium Pro), the parameters are:

Parameter Description
1 Bank number
2 Address field of MCi_ADDR MSR for
the MCA bank that had the error
3 High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error


Report Offensive Follow Up For Removal

Response Number 2
Name: Allan Lauridsen
Date: March 23, 2000 at 03:43:25 Pacific
Reply:

I get the same error in win2k, but it is in games only!

Anybody have the same problems?


Report Offensive Follow Up For Removal

Response Number 3
Name: jee
Date: June 17, 2000 at 21:31:52 Pacific
Reply:

Yeah Allan, got the same thing a couple of times while playing vampires... Oh well, it's only windows :)


Report Offensive Follow Up For Removal

Response Number 4
Name: Sah
Date: July 11, 2000 at 11:11:15 Pacific
Reply:

I have the same problem while upgrade from windows 98 to Windows 2000..
it says Machine_Check_Exception and some junks of addresses.
and following the line: Begining of physical memory dump
Please help...someone.


Report Offensive Follow Up For Removal

Response Number 5
Name: Sisu
Date: July 28, 2000 at 02:54:41 Pacific
Reply:

I have the same problem in WinNT4 Workstation SP6 and HP colorado 14GB and my problem appears when I'm making backups, after some minutes to copy appears in my computer the typical winNT blue screen with an MACHINE_CHECK_EXCEPTION STOP at 0x0000009c(0x00000000,0x00000000,0xb2000100,0x00000800)
If somebody can help me I will be very pleased


Report Offensive Follow Up For Removal

Related Posts

See More



Response Number 6
Name: Martin Jordan
Date: August 31, 2000 at 11:22:18 Pacific
Reply:

I have an NT 4.0 Server that is starting to generate a similar error every few days (3-5 days between errors). I am getting

0x0000009C 0x00000001 0xB2000000 0x000000115

It is a H/W error of some sort, but is there any way to track down where this is occurring?


Report Offensive Follow Up For Removal

Response Number 7
Name: James Hill
Date: September 1, 2000 at 10:37:38 Pacific
Reply:

I have the same 0x9C error and have been able to narrow it down to something in my computer overheating. I am running win2k server and I will get this error within 5-15 minutes after bootup. In order to troubleshoot I opened the case and set up a household reciprocating fan blowing directly into the case. The problem never occured again. If I turned the fan off, within 5-10 minutes the MCE would happen again. I have since bought a brand new case with 3 well positioned fans for proper ventilation and I still get the error. What I want to know is what piece of actual hardware is overheating, RAM, CPU, Cache, Chipset, Video Card, ect. The parameters of the error somehow tell where the error is generated from which it should follow which device that is overheating. However, I do not understand the hex code nor do I understand the parameter definitions given in an earlier post. Hope I have been a little help for some of you and if anyone knows how I can determine which piece of HW is overheating please let me know. My email is jrhill@pmail.net. Thanks.


Report Offensive Follow Up For Removal

Response Number 8
Name: Edward Thompson
Date: October 17, 2000 at 13:57:47 Pacific
Reply:

We have a Compaq Proliant 7000 Server with
Windows NT Server 4.0 and was getting same
error.
We have 264MB memory and final trace to one of the 64MG sims and seems to have fixed the problem.


Report Offensive Follow Up For Removal

Response Number 9
Name: David Thomas
Date: October 24, 2000 at 11:55:06 Pacific
Reply:

I am receiving Bugcheck errors with parameters as follows: 0x0000009c (0x00000004, 0x00000000, 0xb2000000, 0x00040151). This occurs intermittently with two batches of systems in seperate locations all purchased 2-3 months ago. The only common hardware components is the CPU (Intel P3 700e, one batch are Flip Chip and the other batch are SEC), RAM (1 pc. Viking 128 MB PC100 SDRAM), and OS (NT 4 & SP6a pre-installed).
You can find the meaning of the parameters in KB article Q103059 which I found on the Technet CD (but not online).

You can find the Intel System Guide at:
http://developer.intel.com/software/idap/media/pdf/system_guide.htm
With a little help from Intel it translated into "Level 1 Instruction Cache Error" but Intel still blamed the memory. A different brand did not help. I replaced 4 out of 38 CPU's last week and have not yet had a failure in those systems but since failures can be two weeks apart I am still waiting to draw my conclusions.


Report Offensive Follow Up For Removal
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows NT Forum Home


Sponsored links

Ads by Google


Results for: 0x0000009C (Machine_Check_Exception) Help!

0X0000009C ERROR www.computing.net/answers/windows-nt/0x0000009c-error/357.html

Help - NT Blue Screen www.computing.net/answers/windows-nt/help-nt-blue-screen/1314.html

machine check exception www.computing.net/answers/windows-nt/machine-check-exception/1601.html