Win2K Server - Machine check exception
Norm Frechette
I have a Abit LX6 motherboard running a 300Mhz PII processor, that I
am using as part of a Win2k home server. I am posting this problem and
solution, so that it may help others.
Problem:
The system was running fine until this past weekend. While
reinstalling Win2k Server on a temporary hard drive, I began seeing
some unsual errors. During installation I would occassionally get
"Disk I/O Error: Status = 00008000"
and the system seem to run really slow. Somehow I managed to install
Server but whenever the system was left idling, it would all of a
sudden crash to a blue screen and display
*** STOP: 0x0000009C (0x00000003, 0x00000000, 0xB2000000, 0x00080A01)
MACHINE_CHECK_EXCEPTION
I did a search on Google and found the attached posting. After reading
the post and it's complete thread, I began to suspect that the
processor may have been overheating. So I pulled out the processor and
examined the fan/heatsink. Although the fan was working, the heat sink
had plenty of dust embedded with the fins.
Solution:
Carefully removing the CPU then using some compressed air, I removed
the dust, then reinstalled the processor. Now the system seems to be
stable.
>From: pjwo...@my-deja.com (pjwo...@my-deja.com)
>Subject: Re: NT4 Machine check exception
>View: Complete Thread (7 articles)
>Original Format
>Newsgroups: intel.microprocessors.pentium_ii
>Date: 1999/06/30
>
>
>Hi Tom,
>
>The top of processor has the following etched on
>
>Pentium II Processor 80523PY350512 SL2S6
>with mmx Technology 98230431-0481 MALAY
>
>I hope I got the right numbers for you. I also recreated the error
and
>noted down some other details, the error is as follows.
>
>*** STOP: 0x0000009C (0x00000003, 0x00000000, 0xB2000000, 0x00080A01)
>MACHINE_CHECK_EXCEPTION
>CPUID: GenuineIntel 6.3.4 irql:1f SYSVER 0xF0000565
>
>And then the list of Dll bases etc. And it says dumping the memory.
I
>have tried putting the /checkdebug switch on, but the only difference
I
>can see is a flashing SND (I think) message at the top of the error
>message and from what I gather it lets you attach a device to a COM
>port to debug the system, but obviously I dont have any specialised
>equipment for that.
>
>Peter.