alt.certification.a-plus - machine_check

Author

machine_check_exception ?

Frank

2004-04-23, 2:25 pm

WinXP Home

My daughter is experiencing unexplainable blue screen crashes and the
machine automatically reboots.
The error message is not on for long enough to read, but she did catch a
glimpse of part of the message, "machine_check_exception" .
......................
There is no pattern to what software she's using when it happens - it seems
random. I have turned off the Automatically Restart in control panel>system.

Can anyone offer a diagnosis & solution?

Tony

2004-04-23, 3:25 pm

Here is a crazy idea that worked for me when someone was getting an error message that lasted a
split second.

I pointed my camcorder at the screen and taped it. When I played the tape back, I paused it on the
frame that showed the message. I wrote it down, checked MS knowledge base and fixed the problem.

Tony

On Fri, 23 Apr 2004 13:41:26 -0400, "Frank" <anyone@anywhere.com> wrote:

>WinXP Home
>
>My daughter is experiencing unexplainable blue screen crashes and the
>machine automatically reboots.
>The error message is not on for long enough to read, but she did catch a
>glimpse of part of the message, "machine_check_exception" .
>.....................
>There is no pattern to what software she's using when it happens - it seems
>random. I have turned off the Automatically Restart in control panel>system.
>
>Can anyone offer a diagnosis & solution?
>

Will Dormann

2004-04-23, 3:25 pm

Tony wrote:

> Here is a crazy idea that worked for me when someone was getting an error message that lasted a
> split second.
>
> I pointed my camcorder at the screen and taped it. When I played the tape back, I paused it on the
> frame that showed the message. I wrote it down, checked MS knowledge base and fixed the problem.

That's um... creative.

I'd just go to the control panel, then System, and disable the option to
automatically reboot the computer if a STOP error occurs.

Or check the event viewer to get the crash info.

-WD

Will Dormann

2004-04-23, 3:25 pm

Frank wrote:

> WinXP Home
>
> My daughter is experiencing unexplainable blue screen crashes and the
> machine automatically reboots.
> The error message is not on for long enough to read, but she did catch a
> glimpse of part of the message, "machine_check_exception" .
> .....................
> There is no pattern to what software she's using when it happens - it seems
> random. I have turned off the Automatically Restart in control panel>system.
>
> Can anyone offer a diagnosis & solution?

First, check your sytem's RAM:
http://www.memtest.org/
If it doesn't pass the entire test suite, there's no reason to proceed
any further.

Turn off the option to have your computer automatically reboot if it
experiences a STOP error. (Control panel -> System) That way you can
look at the actual STOP error codes. You can also check the event viewer.

If the STOP error itself isn't enough to indicate which driver is at
fault, you may want to analyze your minidump file with dumpchk.exe
http://support.microsoft.com/defaul...kb;EN-US;315271

-WD

Frank

2004-04-23, 4:24 pm

great idea - but dont have a camcorder
:-)

--
xx
"Tony" <tonyrusso@ureach.com > wrote in message
news:vpmi8010a1u4ba5s4mpmpo5so
9kk0fqe06@4ax.com...
> Here is a crazy idea that worked for me when someone was getting an error
message that lasted a
> split second.
>
> I pointed my camcorder at the screen and taped it. When I played the tape
back, I paused it on the
> frame that showed the message. I wrote it down, checked MS knowledge base
and fixed the problem.
>
> Tony
>
>
>
> On Fri, 23 Apr 2004 13:41:26 -0400, "Frank" <anyone@anywhere.com> wrote:
>
seems[color=blue]
panel>system.[color=blue]
>

Frank

2004-04-23, 4:24 pm

>
seems[color=blue]
panel>system.[color=blue]
>
>
> First, check your sytem's RAM:
> http://www.memtest.org/
> If it doesn't pass the entire test suite, there's no reason to proceed
> any further.
>
> Turn off the option to have your computer automatically reboot if it
> experiences a STOP error. (Control panel -> System) That way you can
> look at the actual STOP error codes. You can also check the event
viewer.
>
> If the STOP error itself isn't enough to indicate which driver is at
> fault, you may want to analyze your minidump file with dumpchk.exe
> http://support.microsoft.com/defaul...kb;EN-US;315271
==============================
=======================

Thanks.
I have already unchecked the automatically reboot box in control
panel>sytem.

I'm having problems with memtest. I d/l the floppy version and the 1.11 ver
had a missing file and couldn't install to floppy. The older one ver. 1.00
was ok. However, following the instruction to reboot with it in the drive
just brought up the invalid system disk error message. Maybe it cant work
with XP ?

I did however find TuffTest Lite and Doc Memeory - I will try one of them.

I'm ignorant about dumps and minidumps and dumpchk. I assume it's part of XP
? Where do you run it from? And looking at the MS link it aint easy to
interpret ?

Frank

2004-04-23, 5:24 pm

a[color=blue]
> seems
> panel>system.
> viewer.
> ==============================
=======================
>
> Thanks.
> I have already unchecked the automatically reboot box in control
> panel>sytem.
>
> I'm having problems with memtest. I d/l the floppy version and the 1.11
ver
> had a missing file and couldn't install to floppy. The older one ver. 1.00
> was ok. However, following the instruction to reboot with it in the drive
> just brought up the invalid system disk error message. Maybe it cant work
> with XP ?
>
> I did however find TuffTest Lite and Doc Memeory - I will try one of them.
>
> I'm ignorant about dumps and minidumps and dumpchk. I assume it's part of
XP
> ? Where do you run it from? And looking at the MS link it aint easy to
> interpret ?
==============================
======
Memory tests ok.

found this to help me run dumpchk
http://www.jsiinc.com/SUBJ/tip4600/rh4699.htm

will get back with info

Will Dormann

2004-04-23, 5:24 pm

Frank wrote:

> I'm having problems with memtest. I d/l the floppy version and the 1.11 ver
> had a missing file and couldn't install to floppy. The older one ver. 1.00
> was ok. However, following the instruction to reboot with it in the drive
> just brought up the invalid system disk error message. Maybe it cant work
> with XP ?

memtest86 is OS agnostic. You create a bootable disk (floppy or CD),
and your PC boots off of it.

Either get the ISO and burn it to a CD-RW, or get the pre-compiled
package for floppy (DOS - Win). Extract all files from the zip file
to a temporary folder somewhere. Run install.bat and it will create
the floppy for you.

-WD

Frank

2004-04-23, 11:24 pm

ver[color=blue]
1.00[color=blue]
drive[color=blue]
work[color=blue]
>
> memtest86 is OS agnostic. You create a bootable disk (floppy or CD),
> and your PC boots off of it.
>
> Either get the ISO and burn it to a CD-RW, or get the pre-compiled
> package for floppy (DOS - Win). Extract all files from the zip file
> to a temporary folder somewhere. Run install.bat and it will create
> the floppy for you.
>
------------------------------------
OK, got Memtest going - after a few hours it's still going and
going.........................
I dont know how to interpret the screen results, or whether it means it
could be a faulty ram stick?
I would like to write them up here and see if they make sense to you. The
display is in 2 lines and is shown horizontally (rows & columns).

Top Line:
walltime=3:58:21
cached=352m
RsvdMen=20M
MemMap=e820-std
cache=on
ECC=off
test=Std
Pass=29
Errors=16
Ecc Errs=0

Second Line:
Tst=3
Pass=0
Failing Address=00014fb65bc - 335.3mb
Good=80808080
Bad=80809080
Err-bits=0000010
Cont=161

(hope I transferred those correctly!) - Does this mean anything to anyone?
Looking at the Memtest page they say all you can do anyway is swop the ram
sticks with known-good modules and see if the problem goes away. Is this the
problem ?
------------------------------------------
Regarding reading the minidump file - where can I get dumpchk.exe ? I tried
from RUN and searching the hard drive - nothing. I tried Google - nothing.
Is it available?

That machine just crashed on me and when it rebooted (automatically despite
that feature being turned off in System) the message was "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

Does this mean anything to anyone?
----------------------------------------

Will Dormann

2004-04-24, 12:24 am

Frank wrote:

> Second Line:
> Tst=3
> Pass=0
> Failing Address=00014fb65bc - 335.3mb
> Good=80808080
> Bad=80809080
> Err-bits=0000010
> Cont=161
>
> (hope I transferred those correctly!) - Does this mean anything to anyone?
> Looking at the Memtest page they say all you can do anyway is swop the ram
> sticks with known-good modules and see if the problem goes away. Is this the
> problem ?

Yes, it means that your RAM is bad. Replace it.

> ------------------------------------------
> Regarding reading the minidump file - where can I get dumpchk.exe ? I tried
> from RUN and searching the hard drive - nothing. I tried Google - nothing.
> Is it available?

Yes, all the information is in the URL I first gave you:
http://support.microsoft.com/defaul...kb;EN-US;315271

You run it from the CMD prompt, from the directory with your minidump files.

-WD

Frank

2004-04-24, 12:24 am

--
xx
"Will Dormann" <wdormann@yahoo.com.invalid> wrote in message
news:c2lic.63843$B%4.32443@fe2.columbus.rr.com...
> Frank wrote:
>
anyone?[color=blue]
ram[color=blue]
the[color=blue]
>
> Yes, it means that your RAM is bad. Replace it.
>
>
>
tried[color=blue]
nothing.[color=blue]
>
> Yes, all the information is in the URL I first gave you:
> http://support.microsoft.com/defaul...kb;EN-US;315271
>
> You run it from the CMD prompt, from the directory with your minidump
files.
>
>
------------------------------------------
It is strange that Memtest showed bad memory and neither DocMemory or
TuffTest Lite showed anything?
I will now run Memtest again with one stick at a time to isolate the
culprit. Which part of the second line exactly is it that you used to
diagnose a bad stick so I can look at it again with the test on the
individual sticks?

Will Dormann

2004-04-24, 1:24 am

Frank wrote:

> ------------------------------------------
> It is strange that Memtest showed bad memory and neither DocMemory or
> TuffTest Lite showed anything?

Not strange at all. Memtest86 is much more thorough than either of
those programs.

> I will now run Memtest again with one stick at a time to isolate the
> culprit. Which part of the second line exactly is it that you used to
> diagnose a bad stick so I can look at it again with the test on the
> individual sticks?

Well, it clearly indicated that the errors are occurring at the 335.3MB
mark. So if you've got two 256MB modules, I'd say that the 2nd module
is suspect.

-WD

Frank

2004-04-24, 1:24 am

tried[color=blue]
nothing.[color=blue]
>
> Yes, all the information is in the URL I first gave you:
> http://support.microsoft.com/defaul...kb;EN-US;315271
>
> You run it from the CMD prompt, from the directory with your minidump
files.
>
We didn't get an xp cd with this system, only a 'recovery' cd which has the
OS - i will try but i suspect it may be more difficult to extract dumppchk
from this

Will Dormann

2004-04-24, 1:24 am

Frank wrote:

>
> files.
>
> We didn't get an xp cd with this system, only a 'recovery' cd which has the
> OS - i will try but i suspect it may be more difficult to extract dumppchk
> from this

Well, since you have already determined that the RAM is faulty, I don't
particularly see the need to analyze your minidumps.

-WD

Frank

2004-04-24, 1:24 am

--
xx
"Will Dormann" <wdormann@yahoo.com.invalid> wrote in message
news:7Glic.1641$3_1.1049@fe2.columbus.rr.com...
> Frank wrote:
>
>
> Not strange at all. Memtest86 is much more thorough than either of
> those programs.
>
>
> Well, it clearly indicated that the errors are occurring at the 335.3MB
> mark. So if you've got two 256MB modules, I'd say that the 2nd module
> is suspect.
>
----------------------------------
You are quite a sleuth:-) Fascinating how you are tracking down the culprit.
There are 2 sticks (slots) on this mobo. It orignally came with 1x 128mb ram
module and we added a 256mb stick So I guess it's the 256 stick then
(assuming it reads the 128 first ! ) ?

Why would good ram suddenly go bad - the system was purchased in Sept2003.
Basic specs according to Aida32 are:
Celeron 4A, 2433mhz
Gigabyte GA-85650GXM mobo
SIS 650GX chipset
PC2100DDR SDRAM
XPHome SP!

Will Dormann

2004-04-24, 2:24 am

Frank wrote:

> ----------------------------------
> You are quite a sleuth:-) Fascinating how you are tracking down the culprit.

Thanks!

> There are 2 sticks (slots) on this mobo. It orignally came with 1x 128mb ram
> module and we added a 256mb stick So I guess it's the 256 stick then
> (assuming it reads the 128 first ! ) ?

It could be either one, though I'd suspect the 256MB module since that
was added later. The RAM slots are usually numbered on the motherboard.

> Why would good ram suddenly go bad - the system was purchased in Sept2003.
> Basic specs according to Aida32 are:

RAM can start to show errors if it is not seated properly, or if there
are manufacturing defects. Especially so with the cheaper / generic
modules. Aida32 can actually give you quite a bit of info on the
RAM. Go to Motherboard -> SPD. When you add RAM to a PC, you always
want to exactly match what is currently in the machine. Brand, speed,
voltage, CAS, module type. If there are differences, you increase
your possibility of them not cooperating properly. (where the modules
may possibly test OK when used individually) Of those properties I
listed, are there any differences between your two modules?

Whatever you end up doing, just make sure your configuration has passed
memtest86. (Preferably overnight, if you have the time)

-WD

Tom MacIntyre

2004-04-24, 9:24 am

On Fri, 23 Apr 2004 18:08:00 GMT, Tony <tonyrusso@ureach.com > wrote:

>Here is a crazy idea that worked for me when someone was getting an error message that lasted a
>split second.
>
>I pointed my camcorder at the screen and taped it. When I played the tape back, I paused it on the
>frame that showed the message. I wrote it down, checked MS knowledge base and fixed the problem.
>
>Tony
>

It isn't crazy if it works... :-)

Tom

Tom MacIntyre

2004-04-24, 9:24 am

On Sat, 24 Apr 2004 04:21:07 GMT, Will Dormann
<wdormann@yahoo.com.invalid> wrote:

>Frank wrote:
>
>
>
>Well, since you have already determined that the RAM is faulty, I don't
>particularly see the need to analyze your minidumps.
>

Unless you suspect digestive problems... :-)

Tom

>
>-WD

Frank

2004-04-24, 11:24 am

--
xx
"Will Dormann" <wdormann@yahoo.com.invalid> wrote in message
news:TWlic.1789$3_1.5@fe2.columbus.rr.com...
> Frank wrote:
>
the[color=blue]
dumppchk[color=blue]
>
>
> Well, since you have already determined that the RAM is faulty, I don't
> particularly see the need to analyze your minidumps.
>
>
> -WD

I ran Memtest86 overnight on individual ram modules, and 1 stick (128) is
good and the other (256) is bad. Just a thought though, could it be the slot
and not the ram stick? I could try to verify and run the bad stick in the
other slot (where the good stick tested good)? If it were to be the slot, is
that necessarily symptomatic of a bigger issue - like the motherboard and/or
psu ?

Will Dormann

2004-04-24, 1:24 pm

Frank wrote:

> I ran Memtest86 overnight on individual ram modules, and 1 stick (128) is
> good and the other (256) is bad. Just a thought though, could it be the slot
> and not the ram stick?

Not impossible, but very unlikely.

> I could try to verify and run the bad stick in the
> other slot (where the good stick tested good)? If it were to be the slot, is
> that necessarily symptomatic of a bigger issue - like the motherboard and/or
> psu ?

Go ahead and try. But my money is on the module itself.
Just out of curiosity, what brand and type is the failed module? (You
can get this info from the SPD section in AIDA32, as I mentioned
previously.)

-WD

Frank

2004-04-24, 2:24 pm

--
xx
"Will Dormann" <wdormann@yahoo.com.invalid> wrote in message
news:c%vic.5770$3_1.1810@fe2.columbus.rr.com...
> Frank wrote:
>
is[color=blue]
slot[color=blue]
>
> Not impossible, but very unlikely.
>
slot, is[color=blue]
and/or[color=blue]
>
> Go ahead and try. But my money is on the module itself.
> Just out of curiosity, what brand and type is the failed module? (You
> can get this info from the SPD section in AIDA32, as I mentioned
> previously.)
>

The same stick was bad in both slots. I've just bought another stick and it
tests good. So I'm hoping this is the end of the story. Thanks for helping
me find my way - much appreciated !!!
(the failed stick was AzenRam DDR 2100 133mhz unbuffered 2.5V CAS 2.5)

Joel

2004-04-25, 10:24 am

This sounds like a registry fault, I would suggest two courses of action.
(1) Got to Microsoft TechNet and search for this error message, or (2) save
time and reload the OS.

"Frank" <anyone@anywhere.com> wrote in message
news:Xxcic.37783$CO3.1319459@news20.bellglobal.com...
> WinXP Home
>
> My daughter is experiencing unexplainable blue screen crashes and the
> machine automatically reboots.
> The error message is not on for long enough to read, but she did catch a
> glimpse of part of the message, "machine_check_exception" .
> .....................
> There is no pattern to what software she's using when it happens - it
seems
> random. I have turned off the Automatically Restart in control
panel>system.
>
> Can anyone offer a diagnosis & solution?
>
>

Will Dormann

2004-04-25, 1:24 pm

Joel wrote:

> This sounds like a registry fault, I would suggest two courses of action.
> (1) Got to Microsoft TechNet and search for this error message, or (2) save
> time and reload the OS.

You obviously haven't bothered to read the other posts in this thread.

-WD

Frank

2004-04-25, 4:24 pm

--
xx
"Will Dormann" <wdormann@yahoo.com.invalid> wrote in message
news:tmRic.13443$3_1.7881@fe2.columbus.rr.com...
> Joel wrote:
>
action.[color=blue]
save[color=blue]
>
>
> You obviously haven't bothered to read the other posts in this thread.
>
>
Hey Will, guess I can toss DocMemory and TuffTest Lite now :-) MemTest86 is
all I need.

Will Dormann

2004-04-25, 5:24 pm

Frank wrote:

>
> Hey Will, guess I can toss DocMemory and TuffTest Lite now :-) MemTest86 is
> all I need.

Yeah, it's good stuff. It's always in my toolkit!

-WD

LadyTech

2004-04-28, 11:34 pm

Tom MacIntyre

2004-05-01, 11:27 pm

On Wed, 28 Apr 2004 22:08:06 -0400, "LadyTech"
<spamhater@fakemail.com> wrote:

>
>"Tom MacIntyre" <tom__macintyre@hotmail.com> wrote in message
> news:fsnk80lc366huvvl9hk24ipm1
hi60qoeas@4ax.com...
>| On Sat, 24 Apr 2004 04:21:07 GMT, Will Dormann
>| <wdormann@yahoo.com.invalid> wrote:
>|
>| >Frank wrote:
>| >
>| >>>Yes, all the information is in the URL I first gave you:
>| >>>http://support.microsoft.com/defaul...kb;EN-US;315271
>| >>>
>| >>>You run it from the CMD prompt, from the directory with your
>minidump
>| >>
>| >> files.
>| >>
>| >> We didn't get an xp cd with this system, only a 'recovery' cd
>which has the
>| >> OS - i will try but i suspect it may be more difficult to extract
>dumppchk
>| >> from this
>| >
>| >
>| >Well, since you have already determined that the RAM is faulty, I
>don't
>| >particularly see the need to analyze your minidumps.
>| >
>|
>| Unless you suspect digestive problems... :-)
>|
>| Tom
>
>Tom, you crack me up! :-) *LMAO*!
>

Thank you.

The sad fact is that those who are subjected to a lot of my wit
(friends, family, co-workers) have a radically different opinion than
you. :-)

Tom

LadyTech

2004-05-03, 5:27 pm

"Tom MacIntyre" <tom__macintyre@hotmail.com> wrote in message
news:afn2901no47ns1kf0b09vcr56
0a84qdtq0@4ax.com...
| On Wed, 28 Apr 2004 22:08:06 -0400, "LadyTech"
| <spamhater@fakemail.com> wrote:
|
| >
| >"Tom MacIntyre" <tom__macintyre@hotmail.com> wrote in message
| > news:fsnk80lc366huvvl9hk24ipm1
hi60qoeas@4ax.com...
| >| On Sat, 24 Apr 2004 04:21:07 GMT, Will Dormann
| >| <wdormann@yahoo.com.invalid> wrote:
| >|
| >| >Frank wrote:
| >| >
| >| >>>Yes, all the information is in the URL I first gave you:
| >| >>>http://support.microsoft.com/defaul...kb;EN-US;315271
| >| >>>
| >| >>>You run it from the CMD prompt, from the directory with your
| >minidump
| >| >>
| >| >> files.
| >| >>
| >| >> We didn't get an xp cd with this system, only a 'recovery' cd
| >which has the
| >| >> OS - i will try but i suspect it may be more difficult to
extract
| >dumppchk
| >| >> from this
| >| >
| >| >
| >| >Well, since you have already determined that the RAM is faulty,
I
| >don't
| >| >particularly see the need to analyze your minidumps.
| >| >
| >|
| >| Unless you suspect digestive problems... :-)
| >|
| >| Tom
| >
| >Tom, you crack me up! :-) *LMAO*!
| >
|
| Thank you.
|
| The sad fact is that those who are subjected to a lot of my wit
| (friends, family, co-workers) have a radically different opinion
than
| you. :-)
|
| Tom

I am used to witty people like you and it just makes my day to hear
comments like yours.... I can't help but laugh :-)

Sponsored Links