I recently posted a crashing problem under the subject thread
"machine_check_exception". Will Dorman kindly and patiently led me through
various diagnosis and then asked me to post the results of running
Dumpchk.exe on one of the minidump files which are saved to windows\minidump
after each crash. I have pasted the results of the latest crash. Hopefully
it provides clues to the unsolved problem of frequent crashes where the
screen is only on for a split second before the machine reboots (I have
turned OFF the automatic reboot after a crash option). The only thing I have
time to read on the screen is machine_check_exception and that it is blue
but not the usual windows blue screen.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Lara>cd\windows

C:\WINDOWS>dumpchk minidump\mini042704-02.dmp
Loading dump file minidump\mini042704-02.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 00039000
PfnDataBase 81053000
PsLoadedModuleList 8054be30
PsActiveProcessHead 8054de78
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 0000009c
BugCheckParameter1 00000000
BugCheckParameter2 8053f0f0
BugCheckParameter3 cc0000ff
BugCheckParameter4 20040189
PaeEnabled 00000000
KdDebuggerDataBlock 8053dde0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000100
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002720
CallStackOffset 00002978
SizeOfCallStack 00003000
DriverListOffset 00005c08
DriverCount 000000a3
StringPoolOffset 00008c70
StringPoolSize 00001680
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack f2ebd000
DebuggerDataOffset 00005978
DebuggerDataSize 00000290
DataBlocksOffset 0000a2f0
DataBlocksCount 00000003


Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Tue Apr 27 12:57:06 2004
System Uptime: 0 days 0:05:41
start end module name
804d4000 806c6980 nt Checksum: 0020230B Timestamp: Thu Aug 29
05:
03:24 2002 (3D6DE35C)

Unloaded modules:
f309f000 f30af000 NAVENG.Sys Timestamp: unavailable (00000000)
f2dff000 f2e90000 NavEx15.Sys Timestamp: unavailable (00000000)
f2ea0000 f2eb0000 NAVENG.Sys Timestamp: unavailable (00000000)
f2dff000 f2e90000 NavEx15.Sys Timestamp: unavailable (00000000)
f78c8000 f78d8000 NAVENG.Sys Timestamp: unavailable (00000000)
f4238000 f42c9000 NavEx15.Sys Timestamp: unavailable (00000000)
f2f30000 f2f57000 kmixer.sys Timestamp: unavailable (00000000)
f38c1000 f38e8000 kmixer.sys Timestamp: unavailable (00000000)
f7de7000 f7de8000 drmkaud.sys Timestamp: unavailable (00000000)
f3abe000 f3acb000 DMusic.sys Timestamp: unavailable (00000000)
f7cb2000 f7cb4000 splitter.sys Timestamp: unavailable (00000000)
f3ace000 f3adc000 swmidi.sys Timestamp: unavailable (00000000)
f3923000 f3946000 aec.sys Timestamp: unavailable (00000000)
f7b80000 f7b85000 Cdaudio.SYS Timestamp: unavailable (00000000)
f757c000 f757f000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

C:\WINDOWS>

Report this post to a moderator

Frank wrote:

> I recently posted a crashing problem under the subject thread
> "machine_check_exception".
<snip>
> BugCheckCode 0000009c


That's pretty much indicative of a hardware problem.
Oh, FWIW, if you run dumpchk.exe -e <dumpfile.dmp> I believe it will
give you more information.

Likely causes of such an error:
Bad RAM
Bad PSU
Bad CPU
Overheating CPU
Overclocked CPU
Overclocked RAM
Bad motherboard

You said your CPU temps look "OK" with MBM5. What are they exactly?
Do the temps listed in the BIOS correspond to the temps listed by MBM5?
(To verify that you're looking at the correct sensor)

Bad PSU is tougher to troubleshoot. If you are using memtest86 version
3.1a, though, there is a test which can help determine if a PSU is
potentially at fault, though.
Make sure you've got 3.1a from:
http://www.memtest86.com/
In the memtest86 software, hit 'c' for configuration, and then '2' for
test selection, and then '2' again for extended test. Run this test
overnight. The "bit fade" test sets values in the RAM and then waits
for a very long time, and then verifies the value. If the PSU has
excessive noise or ripple, the values might change and memtest86
extended testing should detect this.

As for the CPU, there are a couple of things to check:
In the BIOS, there may be an option for L2 cache ECC. ECC should be
enabled for the L2 cache. (though I think the celeron has ECC enabled
always for the L2, it can't hurt)

Finally, you could see if there is a way to disable the L2 cache of your
CPU altogether. This would be only for troubleshooting purposes, as it
will make your CPU very slow. But if you get no more crashes with the
L2 disabled, then your CPU might be at fault.

The toughest of all to diagnose is the bad motherboard. Because of the
amount of work involved and the cost, it's usually when you've tried
everything else and the only thing left is switching out the MB.


-WD

Report this post to a moderator

> <snip>
>
>
> That's pretty much indicative of a hardware problem.
> Oh, FWIW, if you run dumpchk.exe -e <dumpfile.dmp> I believe it will
> give you more information.
>
> Likely causes of such an error:
> Bad RAM
> Bad PSU
> Bad CPU
> Overheating CPU
> Overclocked CPU
> Overclocked RAM
> Bad motherboard
>
> You said your CPU temps look "OK" with MBM5. What are they exactly?
> Do the temps listed in the BIOS correspond to the temps listed by MBM5?
> (To verify that you're looking at the correct sensor)
>
> Bad PSU is tougher to troubleshoot. If you are using memtest86 version
> 3.1a, though, there is a test which can help determine if a PSU is
> potentially at fault, though.
> Make sure you've got 3.1a from:
> http://www.memtest86.com/
> In the memtest86 software, hit 'c' for configuration, and then '2' for
> test selection, and then '2' again for extended test. Run this test
> overnight. The "bit fade" test sets values in the RAM and then waits
> for a very long time, and then verifies the value. If the PSU has
> excessive noise or ripple, the values might change and memtest86
> extended testing should detect this.
>
> As for the CPU, there are a couple of things to check:
> In the BIOS, there may be an option for L2 cache ECC. ECC should be
> enabled for the L2 cache. (though I think the celeron has ECC enabled
> always for the L2, it can't hurt)
>
> Finally, you could see if there is a way to disable the L2 cache of your
> CPU altogether. This would be only for troubleshooting purposes, as it
> will make your CPU very slow. But if you get no more crashes with the
> L2 disabled, then your CPU might be at fault.
>
> The toughest of all to diagnose is the bad motherboard. Because of the
> amount of work involved and the cost, it's usually when you've tried
> everything else and the only thing left is switching out the MB.
>
==============================
======================
I'll take a little time to follow these guidelines and get back here in a
day or two

Report this post to a moderator

Frank wrote:

> ==============================
======================
> I'll take a little time to follow these guidelines and get back here in a
> day or two
>
>



Good luck. Let us know what you find...


-WD

Report this post to a moderator

--
xx
"Will Dormann" <wdormann@yahoo.com.invalid> wrote in message
news:H_Bjc.29970$Vp5.1658@fe2.columbus.rr.com...
> Frank wrote:
>
a[color=blue]
>
>
>
> Good luck. Let us know what you find...
==============================
==========================
Meanwhile, here are the MBM5 result details, and the dumpchk with e switch -
hopefully it narrows down the problem:

case 141F/61C
cpu 30F/-1C
sensor3 32F/OC
core0 1.6v
core1 .00v
+3.3 3.39v
+5 5.00v
-12v -12.27v
-5 -4.89v
fan1 5625rpm
fan2 33750rpm
fan3 16875rpm
cpu 2424mhz
cpu0 0%
----------------------------------------------------------------------------
----------------------------
C:\WINDOWS>dumpchk -e minidump\mini042704-02.dmp
Loading dump file minidump\mini042704-02.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 00039000
PfnDataBase 81053000
PsLoadedModuleList 8054be30
PsActiveProcessHead 8054de78
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 0000009c
BugCheckParameter1 00000000
BugCheckParameter2 8053f0f0
BugCheckParameter3 cc0000ff
BugCheckParameter4 20040189
PaeEnabled 00000000
KdDebuggerDataBlock 8053dde0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000100
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002720
CallStackOffset 00002978
SizeOfCallStack 00003000
DriverListOffset 00005c08
DriverCount 000000a3
StringPoolOffset 00008c70
StringPoolSize 00001680
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack f2ebd000
DebuggerDataOffset 00005978
DebuggerDataSize 00000290
DataBlocksOffset 0000a2f0
DataBlocksCount 00000003


Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Tue Apr 27 12:57:06 2004
System Uptime: 0 days 0:05:41
start end module name
804d4000 806c6980 nt Checksum: 0020230B Timestamp: Thu Aug 29
05:
03:24 2002 (3D6DE35C)

Unloaded modules:
f309f000 f30af000 NAVENG.Sys Timestamp: unavailable (00000000)
f2dff000 f2e90000 NavEx15.Sys Timestamp: unavailable (00000000)
f2ea0000 f2eb0000 NAVENG.Sys Timestamp: unavailable (00000000)
f2dff000 f2e90000 NavEx15.Sys Timestamp: unavailable (00000000)
f78c8000 f78d8000 NAVENG.Sys Timestamp: unavailable (00000000)
f4238000 f42c9000 NavEx15.Sys Timestamp: unavailable (00000000)
f2f30000 f2f57000 kmixer.sys Timestamp: unavailable (00000000)
f38c1000 f38e8000 kmixer.sys Timestamp: unavailable (00000000)
f7de7000 f7de8000 drmkaud.sys Timestamp: unavailable (00000000)
f3abe000 f3acb000 DMusic.sys Timestamp: unavailable (00000000)
f7cb2000 f7cb4000 splitter.sys Timestamp: unavailable (00000000)
f3ace000 f3adc000 swmidi.sys Timestamp: unavailable (00000000)
f3923000 f3946000 aec.sys Timestamp: unavailable (00000000)
f7b80000 f7b85000 Cdaudio.SYS Timestamp: unavailable (00000000)
f757c000 f757f000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

C:\WINDOWS>dumpchk -e minidump\mini042704-01.dmp
Loading dump file minidump\mini042704-01.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 00039000
PfnDataBase 81053000
PsLoadedModuleList 8054be30
PsActiveProcessHead 8054de78
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 0000009c
BugCheckParameter1 00000000
BugCheckParameter2 8053f0f0
BugCheckParameter3 cc0000ff
BugCheckParameter4 20040189
PaeEnabled 00000000
KdDebuggerDataBlock 8053dde0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000100
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002720
CallStackOffset 00002978
SizeOfCallStack 00003000
DriverListOffset 00005c08
DriverCount 000000a6
StringPoolOffset 00008d50
StringPoolSize 000016e8
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack f2e4f000
DebuggerDataOffset 00005978
DebuggerDataSize 00000290
DataBlocksOffset 0000a438
DataBlocksCount 00000004


Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Tue Apr 27 12:51:10 2004
System Uptime: 0 days 3:15:36
start end module name
804d4000 806c6980 nt Checksum: 0020230B Timestamp: Thu Aug 29
05:
03:24 2002 (3D6DE35C)

Unloaded modules:
f318d000 f319d000 NAVENG.Sys Timestamp: unavailable (00000000)
f299f000 f2a30000 NavEx15.Sys Timestamp: unavailable (00000000)
f3a9e000 f3aae000 NAVENG.Sys Timestamp: unavailable (00000000)
f2a99000 f2b2a000 NavEx15.Sys Timestamp: unavailable (00000000)
f2b2a000 f2b51000 kmixer.sys Timestamp: unavailable (00000000)
f2e52000 f2e62000 NAVENG.Sys Timestamp: unavailable (00000000)
f2b51000 f2be2000 NavEx15.Sys Timestamp: unavailable (00000000)
f2b2a000 f2b51000 kmixer.sys Timestamp: unavailable (00000000)
f2b2a000 f2b51000 kmixer.sys Timestamp: unavailable (00000000)
f2d13000 f2d3a000 kmixer.sys Timestamp: unavailable (00000000)
f2e02000 f2e12000 NAVENG.Sys Timestamp: unavailable (00000000)
f2b51000 f2be2000 NavEx15.Sys Timestamp: unavailable (00000000)
f3275000 f3285000 NAVENG.Sys Timestamp: unavailable (00000000)
f2b51000 f2be2000 NavEx15.Sys Timestamp: unavailable (00000000)
f2fd1000 f2fe1000 NAVENG.Sys Timestamp: unavailable (00000000)
f2b51000 f2be2000 NavEx15.Sys Timestamp: unavailable (00000000)
f314d000 f315d000 NAVENG.Sys Timestamp: unavailable (00000000)
f2b51000 f2be2000 NavEx15.Sys Timestamp: unavailable (00000000)
f30c9000 f30d9000 NAVENG.Sys Timestamp: unavailable (00000000)
f2c82000 f2d13000 NavEx15.Sys Timestamp: unavailable (00000000)
f2fe1000 f2ff1000 NAVENG.Sys Timestamp: unavailable (00000000)
f2d3a000 f2dcb000 NavEx15.Sys Timestamp: unavailable (00000000)
f2dcb000 f2df2000 kmixer.sys Timestamp: unavailable (00000000)
f2e32000 f2e42000 NAVENG.Sys Timestamp: unavailable (00000000)
f2d3a000 f2dcb000 NavEx15.Sys Timestamp: unavailable (00000000)
f78c8000 f78d8000 NAVENG.Sys Timestamp: unavailable (00000000)
f4238000 f42c9000 NavEx15.Sys Timestamp: unavailable (00000000)
f2e92000 f2eb9000 kmixer.sys Timestamp: unavailable (00000000)
f38c1000 f38e8000 kmixer.sys Timestamp: unavailable (00000000)
f7e61000 f7e62000 drmkaud.sys Timestamp: unavailable (00000000)
f3a5e000 f3a6b000 DMusic.sys Timestamp: unavailable (00000000)
f3a6e000 f3a7c000 swmidi.sys Timestamp: unavailable (00000000)
f38e8000 f390b000 aec.sys Timestamp: unavailable (00000000)
f7cde000 f7ce0000 splitter.sys Timestamp: unavailable (00000000)
f7ac8000 f7acd000 Cdaudio.SYS Timestamp: unavailable (00000000)
f7574000 f7577000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

Report this post to a moderator

Frank wrote:

> ==============================
==========================
> Meanwhile, here are the MBM5 result details, and the dumpchk with e switch -
> hopefully it narrows down the problem:
>
> case 141F/61C
> cpu 30F/-1C
> sensor3 32F/OC

You can generally assume that the highest sensor temp is the CPU one.
(That's why I recommended comparing results to what the BIOS says)

Assuming your CPU is running at 61C when the system is not under load,
that's very hot. What are the temps when running a heavy load such as
Prime95?
http://mersenne.org/gimps/p95v238.zip

Extract the files, run the EXE and then click Test -> PrimeNet

Let it run for 10 minutes or so and check your temps. The further past
65C you go, the greater your chances of seeing stability problems.

What kind of heatsink is on the CPU? Is the airflow in the case
unobstructed by cables? What kind of thermal compound was used?


-WD

Report this post to a moderator

switch -[color=blue]
>
> You can generally assume that the highest sensor temp is the CPU one.
> (That's why I recommended comparing results to what the BIOS says)
>
> Assuming your CPU is running at 61C when the system is not under load,
> that's very hot. What are the temps when running a heavy load such as
> Prime95?
> http://mersenne.org/gimps/p95v238.zip
>
> Extract the files, run the EXE and then click Test -> PrimeNet
>
> Let it run for 10 minutes or so and check your temps. The further past
> 65C you go, the greater your chances of seeing stability problems.
>
> What kind of heatsink is on the CPU? Is the airflow in the case
> unobstructed by cables? What kind of thermal compound was used?
>
==============================
=============
I ran the Extended Memtest86 ver3.1 - not 100% sure what i was looking for
but nothing unusual or suspicious showed up. The readings were constant
after hours and hours.

There is indeed a discrepancy between MBM5 and the Bios' temp readings.
Bios:
system temp=32C/89F
cpu temp=fluctuates from 39C/100F to 41C/105F
cpu fan=3125rpm
system fan2766rpm
vcore=1.58v
+3.3=3.39v
+5=5.02v
+12=11.97v

I'm having trouble setting up and getting PrimeNet95 running (it cant
connect, create or spool files etc etc) so I have not yet been able to place
the system 'under stress".

Airflow seems good - big case, lots of air room, cables are neat, fans
working, no idea what thermal compound was used and cant see any id for
heatsink under fan - is that worth trying to disassemble to see?

With the voltage readings looking ok in the bios and mbm5, is it still worth
doing multimeter testing procedures on the psu connectors?

Could ram or cpu be overclocked without me knowing it ? The Award bios isn't
too detailed, very vague in fact.

Report this post to a moderator

>
> You can generally assume that the highest sensor temp is the CPU one.
> (That's why I recommended comparing results to what the BIOS says)
>
> Assuming your CPU is running at 61C when the system is not under load,
> that's very hot. What are the temps when running a heavy load such as
> Prime95?
> http://mersenne.org/gimps/p95v238.zip
>
> Extract the files, run the EXE and then click Test -> PrimeNet
>
> Let it run for 10 minutes or so and check your temps. The further past
> 65C you go, the greater your chances of seeing stability problems.
>
> What kind of heatsink is on the CPU? Is the airflow in the case
> unobstructed by cables? What kind of thermal compound was used?
>
>
Have posted again under "difficult hardware diagnosis". A last ditch
attempt. Have tried all except swopping cpu and/or mobo with known-good
parts.
Here's the post anyway:
Cicero Serial Number 1052118
Winxp Home. Updated except for the buggy KB835732.
Gigabyte mobo GA-8S650GXM (socket 478).
Celeron 2400
DDR 2100 - 128mb.
Purchased about Sept. 2003 - Future Shop, Richmond Hill (Have receipt).

Experiencing frequent (several times a day) hardware crashes and automatic
reboots. I have turned off the control panel option (system>advanced) to
automatically reboot after a crash, but it still does so anyway.

Machine_Check_Exception.
There is a blue screen error called Machine_Check_Exception, just prior to
the crash & reboot, but it's impossible to read it as it's only on for an
instant. Definitely not a Windows screen. I believe it's an Intel message
from the cpu diagnosing a hardware error (perhaps cpu or mobo).

There is no pattern to the crashes and no relation to what programs may be
running - sometimes it happens when the machine is standing idle.

On reboot the following is sometimes displayed (not everytime) - you have
recovered from a serious error:
BC Code:9c BCP1:00000000 BCP2: 8005366FO BCP3:CC0000FF BCP4:20040189
OSVER:5_1_2600 SP:1_0 Product 768_1


Memtest86.
I ran Memtest86 as I suspected a faulty ram module (128 & 256 installed). I
replaced the 256 module that was probably faulty but the crashes continued.
So I removed the new module and am only running the original 128 module
which tests good. Crashes continue.

PSU.
I suspected the PSU - Verified voltages - all seem ok (within 5%)- checked
the 3.3, 5 & 12v rails on the main mobo connector with a autosensing digital
multimeter - all seem ok,

Fans.
All fans are working (cpu, case and psu).

MBM5 (MotherboardMonitor).
The MBM temperature results are different from the Bios readings.
case 141F/61C
cpu 30F/-1C
sensor3 32F/OC
core0 1.6v
core1 .00v
+3.3 3.39v
+5 5.00v
-12v -12.27v
-5 -4.89v
fan1 5625rpm
fan2 33750rpm
fan3 16875rpm
cpu 2424mhz
cpu0 0%

Bios:
system temp=32C/89F
cpu temp=fluctuates from 39C/100F to 41C/105F
cpu fan=3125rpm
system fan2766rpm
vcore=1.58v
+3.3=3.39v
+5=5.02v
+12=11.97v

Event Viewer.
I looked at the Event Viewer errors and am continually getting STOP
0x0000009c errors, which point to hardware problems.

Dumpchk.
I used Dumpchk.exe to analyse Minidump files (created by XP in the
windows>minidump folder) and have copy/pasted one below as an example, and
to see if it offers any clues:

C:\WINDOWS>dumpchk minidump\mini042704-02.dmp
Loading dump file minidump\mini042704-02.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 00039000
PfnDataBase 81053000
PsLoadedModuleList 8054be30
PsActiveProcessHead 8054de78
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 0000009c
BugCheckParameter1 00000000
BugCheckParameter2 8053f0f0
BugCheckParameter3 cc0000ff
BugCheckParameter4 20040189
PaeEnabled 00000000
KdDebuggerDataBlock 8053dde0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000100
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002720
CallStackOffset 00002978
SizeOfCallStack 00003000
DriverListOffset 00005c08
DriverCount 000000a3
StringPoolOffset 00008c70
StringPoolSize 00001680
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack f2ebd000
DebuggerDataOffset 00005978
DebuggerDataSize 00000290
DataBlocksOffset 0000a2f0
DataBlocksCount 00000003


Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Tue Apr 27 12:57:06 2004
System Uptime: 0 days 0:05:41
start end module name
804d4000 806c6980 nt Checksum: 0020230B Timestamp: Thu Aug 29
05:
03:24 2002 (3D6DE35C)

Unloaded modules:
f309f000 f30af000 NAVENG.Sys Timestamp: unavailable (00000000)
f2dff000 f2e90000 NavEx15.Sys Timestamp: unavailable (00000000)
f2ea0000 f2eb0000 NAVENG.Sys Timestamp: unavailable (00000000)
f2dff000 f2e90000 NavEx15.Sys Timestamp: unavailable (00000000)
f78c8000 f78d8000 NAVENG.Sys Timestamp: unavailable (00000000)
f4238000 f42c9000 NavEx15.Sys Timestamp: unavailable (00000000)
f2f30000 f2f57000 kmixer.sys Timestamp: unavailable (00000000)
f38c1000 f38e8000 kmixer.sys Timestamp: unavailable (00000000)
f7de7000 f7de8000 drmkaud.sys Timestamp: unavailable (00000000)
f3abe000 f3acb000 DMusic.sys Timestamp: unavailable (00000000)
f7cb2000 f7cb4000 splitter.sys Timestamp: unavailable (00000000)
f3ace000 f3adc000 swmidi.sys Timestamp: unavailable (00000000)
f3923000 f3946000 aec.sys Timestamp: unavailable (00000000)
f7b80000 f7b85000 Cdaudio.SYS Timestamp: unavailable (00000000)
f757c000 f757f000 Sfloppy.SYS Timestamp: unavailable (00000000)
end.

Prime95
I ran Prime95 to put load on the system and it failed the torture test. But
no clues as to why - not necessarily cpu ?
Readout - Beginning a continuous self test to check computer.
Test1, 4000 Lucas-Lehmer iterations of M19922945 using 1024k FFT length.
FATAL ERROR:Writing to temp file.
Error opening results file to output this message:
Unable to open log file.
Torture Test ran 0 minutes_1 error.0 warnings.
Execution halted.

CPU Stability Test ver.6
I ran the Normal test mode, and it lasted about 9 minutes before crashing.
No telling if it was because of strain on the cpu as the machine crashes
like that anyway, even when not under a load.

So, definitely a hardware problem :-) But how can I be specific and sure?
Would a Post diagnostic card tell me if it's the cpu or mobo or ? I dont
have a spare cpu or mobo to swop with known-good parts.

Report this post to a moderator

Frank wrote:

> Purchased about Sept. 2003 - Future Shop, Richmond Hill (Have receipt).

Uh, I'm going to assume that it's not under warranty anymore.


> Machine_Check_Exception.
> There is a blue screen error called Machine_Check_Exception, just prior to
> the crash & reboot, but it's impossible to read it as it's only on for an
> instant. Definitely not a Windows screen. I believe it's an Intel message
> from the cpu diagnosing a hardware error (perhaps cpu or mobo).

It's your processor sending interrupt 18 to your operating system to
indicate a hardware failure.


> Memtest86.
> I ran Memtest86 as I suspected a faulty ram module (128 & 256 installed). I
> replaced the 256 module that was probably faulty but the crashes continued.
> So I removed the new module and am only running the original 128 module
> which tests good. Crashes continue.

Memtest86 crashes or reports memory errors? If it's a crash, you've
got a serious hardware problem.


> Prime95
> I ran Prime95 to put load on the system and it failed the torture test. But
> no clues as to why - not necessarily cpu ?
> Readout - Beginning a continuous self test to check computer.
> Test1, 4000 Lucas-Lehmer iterations of M19922945 using 1024k FFT length.
> FATAL ERROR:Writing to temp file.
> Error opening results file to output this message:
> Unable to open log file.
> Torture Test ran 0 minutes_1 error.0 warnings.
> Execution halted.

I've never seen that error before. Hard to say if the error is with
the test or writing to the log file.


> CPU Stability Test ver.6
> I ran the Normal test mode, and it lasted about 9 minutes before crashing.
> No telling if it was because of strain on the cpu as the machine crashes
> like that anyway, even when not under a load.

You never posted your results for your temps under load. What are they?
Is it truly a Celeron 2.4GHz, or is it something less but running at
2.4? (The part number should be etched on top of the CPU)


-WD

Report this post to a moderator

Memtest86.
installed). I[color=blue]
continued.[color=blue]
>
> Memtest86 crashes or reports memory errors? If it's a crash, you've
> got a serious hardware problem.
>

No- I meant the system still has the problem with crashes. I am running
memtest again now on the single original 1288mb and will probably leave it
overnight.


> Is it truly a Celeron 2.4GHz, or is it something less but running at
> 2.4? (The part number should be etched on top of the CPU)
>
Yes it is a 2.4

Will, I appreciate all your help to this point. I am going to go over all
the steps again one more time. I suspect the only way to get a sure
diagnosis is to replace each of the likely components with known-good parts
(psu, cpu, mb). Sinc I'm not "in the business", I dont have them on hand,
and may have to resort to taking the machine in somewhere.

Report this post to a moderator