MACHINE_CHECK_EXCEPTION errors

[lantierl]

I am unable to determine the root cause of my system crashes that show the
following on the blue screen crash page summary:
MACHINE_CHECK_EXCEPTION
STOP: 0x0000009C (0x00000004, 0x8054D570, 0xB2000010, 0x00010C0F) I built
this machine from scratch about a year ago, and have experienced infrequent,
untimely crashes such as this with varying degrees of frequency. When it
first occurred, I ran MEMTEST386 and found bad memory, which Kingston
replaced free of charge. Even with the new memory, the crashes have continued.
I have run MEMTEST386 and other memory checks and see no issues with the new
memory. I am running Windows XP Home on an AMD ATHLON 64 CPU on an ABIT UL8
motherboard with a 420W power supply and 1GB of RAM (two 512 MB dual channel
DDR Kingston KVR400AK2/1GR).
I have run a multitude of system checks including Norton Systemworks,
MacAfee scan, Kaspersky scan, Trendmicro scan, Adware SE scan, Ewidoscan, and
Spybot scan.
How do I determine what the problem is to decided what to do to make this
frsutrating error STOP?
I don't know what else to check and need help resolving the issue.
Microsoft's web pagefor this kind of stop is:
http://support.microsoft.com/kb/329284
But... the cause refers to Pentium, not AMD (and I have an AMD processor,
not a Pentium).
System information is as follows:
OS Name Microsoft Windows XP Home Edition Version 5.1.2600 Service Pack 2
Build 2600 OS Manufacturer Microsoft Corporation System Name TEAM-H_AND_L
System Manufacturer AWARD_ System Model AWRDACPI System Type X86-based PC
Processor x86 Family 15 Model 47 Stepping 2 AuthenticAMD ~2249 Mhz BIOS
Version/Date Phoenix Technologies, LTD 6.00 PG, 3/10/2006 SMBIOS Version 2.3
Windows Directory F:\WINDOWS System Directory F:\WINDOWS\system32 Boot Device
\Device\HarddiskVolume1 Locale United States Hardware Abstraction Layer
Version = "5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)"
User Name TEAM-H_AND_L\Lance
Time Zone Eastern Daylight Time
Total Physical Memory 1,024.00 MB
Available Physical Memory 657.45 MB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB
Page File Space 2.41 GB
Page File F:\pagefile.sys

Help????

[David B.]

First, just having Norton and MacAfee on the machine would make me want to
format and reload. Seriously though, If you were having windows issues, and
determined you were running on a bad stick of ram, even after replacing the
ram problems can remain from the bad ram causing corruption. If you have not
I would try at the least a repair install, preferable a format and fresh
install, maybe on a second spare hard drive, to see if the problems clear
up.

--

----
Crosspost, do not multipost http://www.blakjak.demon.co.uk/mul_crss.htm
How to ask a question http://support.microsoft.com/kb/555375
How to Post http://www.dts-l.org/goodpost.htm
__________________________________________________ _______________________________


"lantierl" > wrote in message
...
>I am unable to determine the root cause of my system crashes that show the
> following on the blue screen crash page summary:
> MACHINE_CHECK_EXCEPTION
> STOP: 0x0000009C (0x00000004, 0x8054D570, 0xB2000010, 0x00010C0F) I built
> this machine from scratch about a year ago, and have experienced
> infrequent,
> untimely crashes such as this with varying degrees of frequency. When it
> first occurred, I ran MEMTEST386 and found bad memory, which Kingston
> replaced free of charge. Even with the new memory, the crashes have
> continued.
> I have run MEMTEST386 and other memory checks and see no issues with the
> new
> memory. I am running Windows XP Home on an AMD ATHLON 64 CPU on an ABIT
> UL8
> motherboard with a 420W power supply and 1GB of RAM (two 512 MB dual
> channel
> DDR Kingston KVR400AK2/1GR).
> I have run a multitude of system checks including Norton Systemworks,
> MacAfee scan, Kaspersky scan, Trendmicro scan, Adware SE scan, Ewidoscan,
> and
> Spybot scan.
> How do I determine what the problem is to decided what to do to make this
> frsutrating error STOP?
> I don't know what else to check and need help resolving the issue.
> Microsoft's web pagefor this kind of stop is:
> http://support.microsoft.com/kb/329284
> But... the cause refers to Pentium, not AMD (and I have an AMD processor,
> not a Pentium).
> System information is as follows:
> OS Name Microsoft Windows XP Home Edition Version 5.1.2600 Service Pack 2
> Build 2600 OS Manufacturer Microsoft Corporation System Name TEAM-H_AND_L
> System Manufacturer AWARD_ System Model AWRDACPI System Type X86-based PC
> Processor x86 Family 15 Model 47 Stepping 2 AuthenticAMD ~2249 Mhz BIOS
> Version/Date Phoenix Technologies, LTD 6.00 PG, 3/10/2006 SMBIOS Version
> 2.3
> Windows Directory F:\WINDOWS System Directory F:\WINDOWS\system32 Boot
> Device
> \Device\HarddiskVolume1 Locale United States Hardware Abstraction Layer
> Version = "5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)"
> User Name TEAM-H_AND_L\Lance
> Time Zone Eastern Daylight Time
> Total Physical Memory 1,024.00 MB
> Available Physical Memory 657.45 MB
> Total Virtual Memory 2.00 GB
> Available Virtual Memory 1.96 GB
> Page File Space 2.41 GB
> Page File F:\pagefile.sys
>
> Help????

[Leonard Grey]

To my knowledge, the single source with the most information on the STOP
error is here:
http://www.aumha.org/a/stop.php#0x9c

Excerpt:
"Most commonly it results from overheating, from failed hardware (RAM,
CPU, hardware bus, power supply, etc.), or from pushing hardware beyond
its capabilities (e.g., overclocking a CPU)."

---
Leonard Grey
Errare humanum est

lantierl wrote:
> I am unable to determine the root cause of my system crashes that show the
> following on the blue screen crash page summary:
> MACHINE_CHECK_EXCEPTION
> STOP: 0x0000009C (0x00000004, 0x8054D570, 0xB2000010, 0x00010C0F) I built
> this machine from scratch about a year ago, and have experienced infrequent,
> untimely crashes such as this with varying degrees of frequency. When it
> first occurred, I ran MEMTEST386 and found bad memory, which Kingston
> replaced free of charge. Even with the new memory, the crashes have continued.
> I have run MEMTEST386 and other memory checks and see no issues with the new
> memory. I am running Windows XP Home on an AMD ATHLON 64 CPU on an ABIT UL8
> motherboard with a 420W power supply and 1GB of RAM (two 512 MB dual channel
> DDR Kingston KVR400AK2/1GR).
> I have run a multitude of system checks including Norton Systemworks,
> MacAfee scan, Kaspersky scan, Trendmicro scan, Adware SE scan, Ewidoscan, and
> Spybot scan.
> How do I determine what the problem is to decided what to do to make this
> frsutrating error STOP?
> I don't know what else to check and need help resolving the issue.
> Microsoft's web pagefor this kind of stop is:
> http://support.microsoft.com/kb/329284
> But... the cause refers to Pentium, not AMD (and I have an AMD processor,
> not a Pentium).
> System information is as follows:
> OS Name Microsoft Windows XP Home Edition Version 5.1.2600 Service Pack 2
> Build 2600 OS Manufacturer Microsoft Corporation System Name TEAM-H_AND_L
> System Manufacturer AWARD_ System Model AWRDACPI System Type X86-based PC
> Processor x86 Family 15 Model 47 Stepping 2 AuthenticAMD ~2249 Mhz BIOS
> Version/Date Phoenix Technologies, LTD 6.00 PG, 3/10/2006 SMBIOS Version 2.3
> Windows Directory F:\WINDOWS System Directory F:\WINDOWS\system32 Boot Device
> \Device\HarddiskVolume1 Locale United States Hardware Abstraction Layer
> Version = "5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)"
> User Name TEAM-H_AND_L\Lance
> Time Zone Eastern Daylight Time
> Total Physical Memory 1,024.00 MB
> Available Physical Memory 657.45 MB
> Total Virtual Memory 2.00 GB
> Available Virtual Memory 1.96 GB
> Page File Space 2.41 GB
> Page File F:\pagefile.sys
>
> Help????

[lantierl]

Dave,
Thanks. Unfortunately, I do not have a spare hard drive. I would like to
avoid reformatting, unless it is a last resort only option, as I would have
to, of course, reload everything on the machine and back up all of my data
files.

How would having a previously bad stick of RAM affect current machine
operation with the new RAM received?

My initial thoughts are that I may have a bad BIOS setting and not know it,
but the manuals are so generic that I have no way of verifying the correct
seetings for the AMD ATHLON 64/ABIT UL8 motherboard combo other than the fact
that the machine has operated for several days at a time without a crash, and
then might crash three times in one day.

[lantierl]

Thanks, Leonard.

The Microsoft article I found was very simialr. Unfortunately, not all of
the error codes show up on Microsoft's site. I tried to isolate it to somne
of the potential problems listed such as memory errors (by running
MEMTEST386) and have verified the temperatures are within parameters. I
don't know how to check for items such as system bus errors, though.

[Leonard Grey]

If you can backup (or even better, image) your hard disk, do a clean
install of Windows (and nothing else - don't connect to the internet.)
If the problems persist, you know it's hardware. Bring your PC to a
professional technician (not some shlemiel at BestBuy or Circuit City.)
---
Leonard Grey
Errare humanum est

lantierl wrote:
> Thanks, Leonard.
>
> The Microsoft article I found was very simialr. Unfortunately, not all of
> the error codes show up on Microsoft's site. I tried to isolate it to somne
> of the potential problems listed such as memory errors (by running
> MEMTEST386) and have verified the temperatures are within parameters. I
> don't know how to check for items such as system bus errors, though.

[Gerry]

How often to these crashes occur? Do you they arise during the boot
process or later?

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?

Try Start, Run, type "sigverif.exe" without quotes and hit OK. What
drivers are listed as unsigned? Disregard those which are not checked.

Please post copies of all Error and Warning Reports appearing in the
System and Application logs in Event Viewer for the last time the
problem occurred. No Information Reports please.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer. When researching the meaning
of the error, information regarding Event ID, Source and Description
are important.

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/kb/308427/en-us

Part of the Description of the error will include a link, which you
should double click for further information. You can copy using copy
and paste. Often the link will, however, say there is no further
information.
http://go.microsoft.com/fw.link/events.asp
(Please note the hyperlink above is for illustration purposes only)

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.

Not too helpful but provided for the record:
http://msdn2.microsoft.com/en-us/library/ms795775.aspx

Another link which may be helpful:
http://www.elephantboycomputers.com/page2.html#Hardware_Tshoot

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

lantierl wrote:
> Thanks, Leonard.
>
> The Microsoft article I found was very simialr. Unfortunately, not
> all of the error codes show up on Microsoft's site. I tried to
> isolate it to somne of the potential problems listed such as memory
> errors (by running MEMTEST386) and have verified the temperatures are
> within parameters. I don't know how to check for items such as
> system bus errors, though.

[Chris]

"lantierl" wrote:

> I am unable to determine the root cause of my system crashes that show the
> following on the blue screen crash page summary:
> MACHINE_CHECK_EXCEPTION
> STOP: 0x0000009C (0x00000004, 0x8054D570, 0xB2000010, 0x00010C0F) I built
> this machine from scratch about a year ago, and have experienced infrequent,
> untimely crashes such as this with varying degrees of frequency. When it
> first occurred, I ran MEMTEST386 and found bad memory, which Kingston
> replaced free of charge. Even with the new memory, the crashes have continued.
> I have run MEMTEST386 and other memory checks and see no issues with the new
> memory. I am running Windows XP Home on an AMD ATHLON 64 CPU on an ABIT UL8
> motherboard with a 420W power supply and 1GB of RAM (two 512 MB dual channel
> DDR Kingston KVR400AK2/1GR).
> I have run a multitude of system checks including Norton Systemworks,
> MacAfee scan, Kaspersky scan, Trendmicro scan, Adware SE scan, Ewidoscan, and
> Spybot scan.
> How do I determine what the problem is to decided what to do to make this
> frsutrating error STOP?
> I don't know what else to check and need help resolving the issue.
> Microsoft's web pagefor this kind of stop is:
> http://support.microsoft.com/kb/329284
> But... the cause refers to Pentium, not AMD (and I have an AMD processor,
> not a Pentium).
> System information is as follows:
> OS Name Microsoft Windows XP Home Edition Version 5.1.2600 Service Pack 2
> Build 2600 OS Manufacturer Microsoft Corporation System Name TEAM-H_AND_L
> System Manufacturer AWARD_ System Model AWRDACPI System Type X86-based PC
> Processor x86 Family 15 Model 47 Stepping 2 AuthenticAMD ~2249 Mhz BIOS
> Version/Date Phoenix Technologies, LTD 6.00 PG, 3/10/2006 SMBIOS Version 2.3
> Windows Directory F:\WINDOWS System Directory F:\WINDOWS\system32 Boot Device
> \Device\HarddiskVolume1 Locale United States Hardware Abstraction Layer
> Version = "5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)"
> User Name TEAM-H_AND_L\Lance
> Time Zone Eastern Daylight Time
> Total Physical Memory 1,024.00 MB
> Available Physical Memory 657.45 MB
> Total Virtual Memory 2.00 GB
> Available Virtual Memory 1.96 GB
> Page File Space 2.41 GB
> Page File F:\pagefile.sys
>
> Help????



Hi,

From the sounds of it you have pretty much ruled out RAM in this issue. If
you have run multiple RAM testers odds are the RAM is good. The knowledge
base article you listed gives pretty good advice on what your next steps
should be. It does not however only say it's for pentium processors like you
said. It mentioned a mechanism for testing hardware errors with that type of
processors. So I would still try the other suggestions the article gave.

• 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.

If you over clocked your processor the first item could be a reason why it
isn't working.

Try a different surge protector, I personally have seen many issues caused
by an old surge protector that isn't working well. And if you're plugged in
directly to a wall that could definetly be a possible cause to your problem.

Abit motherboards have a temperature monitor built into their bios'. I
would just sit in your bios screen and monitor how hot your machine is
getting.

You will also want to check out your event viewer. Right click on my
computer and go to manage. On the left hand side of the window there should
be an menu stating event viewer. System events and applications events may
give you many more hints on to what the problem could be.

If those items don't help you. Power could still be an issue. It's possible
420 watts aren't enough for your system. What kind of video card do you
have? It could pull a lot of power. Maybe you need to go up to a bigger
power supply.

Lastly, I have one more question. Why is your system installed on F:?
Normally it's C:, that could also be a cause of your problem but doubtful.
Hope this info helps you.

[lantierl]

Gerry,
These crashes occur at random intervals. Sometimes they don't happen for a
few days, and sometimes they may happene several times in a day.
Rarely do they occur during the boot process, but I have had it happen at
least once during boot up.

I just learned about the Event Viewer today, and will try it out tonight.

As for devices, no yellow exclamation points, no hardware errors or devie
driver issues appear. I will also try the sigverif.exe tonight.



"Gerry" wrote:

> How often to these crashes occur? Do you they arise during the boot
> process or later?
>
> Are there any yellow question marks in Device Manager? Right click on
> the My Computer icon on your Desktop and select Properties,
> Hardware,Device Manager. If yes what is the Device Error code?
>
> Try Start, Run, type "sigverif.exe" without quotes and hit OK. What
> drivers are listed as unsigned? Disregard those which are not checked.
>
> Please post copies of all Error and Warning Reports appearing in the
> System and Application logs in Event Viewer for the last time the
> problem occurred. No Information Reports please.
>
> You can access Event Viewer by selecting Start, Control Panel,
> Administrative Tools, and Event Viewer. When researching the meaning
> of the error, information regarding Event ID, Source and Description
> are important.
>
> HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
> http://support.microsoft.com/kb/308427/en-us
>
> Part of the Description of the error will include a link, which you
> should double click for further information. You can copy using copy
> and paste. Often the link will, however, say there is no further
> information.
> http://go.microsoft.com/fw.link/events.asp
> (Please note the hyperlink above is for illustration purposes only)
>
> A tip for posting copies of Error Reports! Run Event Viewer and double
> click on the error you want to copy. In the window, which appears is a
> button resembling two pages. Click the button and close Event
> Viewer.Now start your message (email) and do a paste into the body of
> the message. Make sure this is the first paste after exiting from
> Event Viewer.
>
> Not too helpful but provided for the record:
> http://msdn2.microsoft.com/en-us/library/ms795775.aspx
>
> Another link which may be helpful:
> http://www.elephantboycomputers.com/page2.html#Hardware_Tshoot
>
> --
>
>
>
> Hope this helps.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
> lantierl wrote:
> > Thanks, Leonard.
> >
> > The Microsoft article I found was very simialr. Unfortunately, not
> > all of the error codes show up on Microsoft's site. I tried to
> > isolate it to somne of the potential problems listed such as memory
> > errors (by running MEMTEST386) and have verified the temperatures are
> > within parameters. I don't know how to check for items such as
> > system bus errors, though.
>
>
>

[lantierl]

Chris,
Thanks for the response.
To answer some of the questions:
- I bought a new power strip with EMI/RF protection, based on the chance
that part of the problem may be due to "dirty" power from my old power strip.
But, I see no noticeable difference in crash frequency.
- I have been using the ABIT EQ monitor to watch temperatures, and all
appear to be in specifications.
- As for overclocking, I am using the default settings from the motherboard.
I have read everything I can on the AMD ATHLON 64 pages and the ABIT UL8
motherboard pages to find out the exact BIOS settings for the DDR, HTT, and
CPU speeds and voltages, as most are set to autmoatic or default. I also
e-mailed Abit and AMD asking for technical assistance in getting the correct
settings for these and other SoftMenu BIOS settings that I was not familiar
with and had used the defaults for, in the off chance that it is a BIOS
setting that is causing my crash errors.
- With regard to the F: instead of C: drive, great question! I am using a
SATA hard drive instead of IDE, and the system would not let me rename it to
C: (forced to use F:). Thereofre, I had to alias all C: references to F: so
that anything looking for C: finds it on the F:, if that makes sense. Of
course, I forget the command I used to do that, and had to research that when
I first built the machine. The only thing I have on IDE is a ZIP disk master
with no slave.
- Video card is a Radeon 9550. Older card, PCI, not PCI-express.
-Lastly, I learned of the Event Viewer today and will try that out tonight,
then post error messages here, if I can figure out how to use it with the
information provided by both you and Gerry.


"Chris" wrote:

>
>
> "lantierl" wrote:
>
> > I am unable to determine the root cause of my system crashes that show the
> > following on the blue screen crash page summary:
> > MACHINE_CHECK_EXCEPTION
> > STOP: 0x0000009C (0x00000004, 0x8054D570, 0xB2000010, 0x00010C0F) I built
> > this machine from scratch about a year ago, and have experienced infrequent,
> > untimely crashes such as this with varying degrees of frequency. When it
> > first occurred, I ran MEMTEST386 and found bad memory, which Kingston
> > replaced free of charge. Even with the new memory, the crashes have continued.
> > I have run MEMTEST386 and other memory checks and see no issues with the new
> > memory. I am running Windows XP Home on an AMD ATHLON 64 CPU on an ABIT UL8
> > motherboard with a 420W power supply and 1GB of RAM (two 512 MB dual channel
> > DDR Kingston KVR400AK2/1GR).
> > I have run a multitude of system checks including Norton Systemworks,
> > MacAfee scan, Kaspersky scan, Trendmicro scan, Adware SE scan, Ewidoscan, and
> > Spybot scan.
> > How do I determine what the problem is to decided what to do to make this
> > frsutrating error STOP?
> > I don't know what else to check and need help resolving the issue.
> > Microsoft's web pagefor this kind of stop is:
> > http://support.microsoft.com/kb/329284
> > But... the cause refers to Pentium, not AMD (and I have an AMD processor,
> > not a Pentium).
> > System information is as follows:
> > OS Name Microsoft Windows XP Home Edition Version 5.1.2600 Service Pack 2
> > Build 2600 OS Manufacturer Microsoft Corporation System Name TEAM-H_AND_L
> > System Manufacturer AWARD_ System Model AWRDACPI System Type X86-based PC
> > Processor x86 Family 15 Model 47 Stepping 2 AuthenticAMD ~2249 Mhz BIOS
> > Version/Date Phoenix Technologies, LTD 6.00 PG, 3/10/2006 SMBIOS Version 2.3
> > Windows Directory F:\WINDOWS System Directory F:\WINDOWS\system32 Boot Device
> > \Device\HarddiskVolume1 Locale United States Hardware Abstraction Layer
> > Version = "5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)"
> > User Name TEAM-H_AND_L\Lance
> > Time Zone Eastern Daylight Time
> > Total Physical Memory 1,024.00 MB
> > Available Physical Memory 657.45 MB
> > Total Virtual Memory 2.00 GB
> > Available Virtual Memory 1.96 GB
> > Page File Space 2.41 GB
> > Page File F:\pagefile.sys
> >
> > Help????
>
>
>
> Hi,
>
> From the sounds of it you have pretty much ruled out RAM in this issue. If
> you have run multiple RAM testers odds are the RAM is good. The knowledge
> base article you listed gives pretty good advice on what your next steps
> should be. It does not however only say it's for pentium processors like you
> said. It mentioned a mechanism for testing hardware errors with that type of
> processors. So I would still try the other suggestions the article gave.
>
> • 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.
>
> If you over clocked your processor the first item could be a reason why it
> isn't working.
>
> Try a different surge protector, I personally have seen many issues caused
> by an old surge protector that isn't working well. And if you're plugged in
> directly to a wall that could definetly be a possible cause to your problem.
>
> Abit motherboards have a temperature monitor built into their bios'. I
> would just sit in your bios screen and monitor how hot your machine is
> getting.
>
> You will also want to check out your event viewer. Right click on my
> computer and go to manage. On the left hand side of the window there should
> be an menu stating event viewer. System events and applications events may
> give you many more hints on to what the problem could be.
>
> If those items don't help you. Power could still be an issue. It's possible
> 420 watts aren't enough for your system. What kind of video card do you
> have? It could pull a lot of power. Maybe you need to go up to a bigger
> power supply.
>
> Lastly, I have one more question. Why is your system installed on F:?
> Normally it's C:, that could also be a cause of your problem but doubtful.
> Hope this info helps you.

[lantierl]

Gerry,
The following are the drivers that showed as not signed when I ran the
sigverif.exe:
btaudio.sys
btkrnl.sys
btwhid.sys
btwmodem.sys
btwusb.sys
marinbus.sys
acdpdf.txt
acpdf250.dll
acpdfui250.dll
nsui.dll
nsuni.dll
oem.gpd
pdf.ini

The following are the errors listed in the event log:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 8/2/2007
Time: 7:17:42 PM
User: N/A
Computer: TEAM-H_AND_L
Description:
The following boot-start or system-start driver(s) failed to load:
Cdr4_xp

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: MPSampleSubmission
Event Category: None
Event ID: 5000
Date: 8/2/2007
Time: 2:09:13 AM
User: N/A
Computer: TEAM-H_AND_L
Description:
EventType mptelemetry, P1 80072ee2, P2 endsearch, P3 search, P4 1.1.1593.0,
P5 mpsigdwn.dll, P6 1.1.1593.0, P7 windows defender, P8 NIL, P9 NIL, P10 NIL.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 6d 00 70 00 74 00 65 00 m.p.t.e.
0008: 6c 00 65 00 6d 00 65 00 l.e.m.e.
0010: 74 00 72 00 79 00 2c 00 t.r.y.,.
0018: 20 00 38 00 30 00 30 00 .8.0.0.
0020: 37 00 32 00 65 00 65 00 7.2.e.e.
0028: 32 00 2c 00 20 00 65 00 2.,. .e.
0030: 6e 00 64 00 73 00 65 00 n.d.s.e.
0038: 61 00 72 00 63 00 68 00 a.r.c.h.
0040: 2c 00 20 00 73 00 65 00 ,. .s.e.
0048: 61 00 72 00 63 00 68 00 a.r.c.h.
0050: 2c 00 20 00 31 00 2e 00 ,. .1...
0058: 31 00 2e 00 31 00 35 00 1...1.5.
0060: 39 00 33 00 2e 00 30 00 9.3...0.
0068: 2c 00 20 00 6d 00 70 00 ,. .m.p.
0070: 73 00 69 00 67 00 64 00 s.i.g.d.
0078: 77 00 6e 00 2e 00 64 00 w.n...d.
0080: 6c 00 6c 00 2c 00 20 00 l.l.,. .
0088: 31 00 2e 00 31 00 2e 00 1...1...
0090: 31 00 35 00 39 00 33 00 1.5.9.3.
0098: 2e 00 30 00 2c 00 20 00 ..0.,. .
00a0: 77 00 69 00 6e 00 64 00 w.i.n.d.
00a8: 6f 00 77 00 73 00 20 00 o.w.s. .
00b0: 64 00 65 00 66 00 65 00 d.e.f.e.
00b8: 6e 00 64 00 65 00 72 00 n.d.e.r.
00c0: 2c 00 20 00 4e 00 49 00 ,. .N.I.
00c8: 4c 00 2c 00 20 00 4e 00 L.,. .N.
00d0: 49 00 4c 00 20 00 4e 00 I.L. .N.
00d8: 49 00 4c 00 0d 00 0a 00 I.L.....

Event Type: Error
Event Source: Ci
Event Category: CI Service
Event ID: 4126
Date: 7/30/2007
Time: 11:29:18 PM
User: N/A
Computer: TEAM-H_AND_L
Description:
Cleaning up corrupt content index metadata on f:\system volume
information\catalog.wci. Index will be automatically restored by refiltering
all documents.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I had one shutdown tonight at approximately 7:30 p.m. EST but it does not
show in any of the error logs.


"Gerry" wrote:

> How often to these crashes occur? Do you they arise during the boot
> process or later?
>
> Are there any yellow question marks in Device Manager? Right click on
> the My Computer icon on your Desktop and select Properties,
> Hardware,Device Manager. If yes what is the Device Error code?
>
> Try Start, Run, type "sigverif.exe" without quotes and hit OK. What
> drivers are listed as unsigned? Disregard those which are not checked.
>
> Please post copies of all Error and Warning Reports appearing in the
> System and Application logs in Event Viewer for the last time the
> problem occurred. No Information Reports please.
>
> You can access Event Viewer by selecting Start, Control Panel,
> Administrative Tools, and Event Viewer. When researching the meaning
> of the error, information regarding Event ID, Source and Description
> are important.
>
> HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
> http://support.microsoft.com/kb/308427/en-us
>
> Part of the Description of the error will include a link, which you
> should double click for further information. You can copy using copy
> and paste. Often the link will, however, say there is no further
> information.
> http://go.microsoft.com/fw.link/events.asp
> (Please note the hyperlink above is for illustration purposes only)
>
> A tip for posting copies of Error Reports! Run Event Viewer and double
> click on the error you want to copy. In the window, which appears is a
> button resembling two pages. Click the button and close Event
> Viewer.Now start your message (email) and do a paste into the body of
> the message. Make sure this is the first paste after exiting from
> Event Viewer.
>
> Not too helpful but provided for the record:
> http://msdn2.microsoft.com/en-us/library/ms795775.aspx
>
> Another link which may be helpful:
> http://www.elephantboycomputers.com/page2.html#Hardware_Tshoot
>
> --
>
>
>
> Hope this helps.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
> lantierl wrote:
> > Thanks, Leonard.
> >
> > The Microsoft article I found was very simialr. Unfortunately, not
> > all of the error codes show up on Microsoft's site. I tried to
> > isolate it to somne of the potential problems listed such as memory
> > errors (by running MEMTEST386) and have verified the temperatures are
> > within parameters. I don't know how to check for items such as
> > system bus errors, though.
>
>
>

[lantierl]

Chris,
I posted this under Gerry's reply as well, but the remaining answer to your
question regarding event log errors are as follows:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 8/2/2007
Time: 7:17:42 PM
User: N/A
Computer: TEAM-H_AND_L
Description:
The following boot-start or system-start driver(s) failed to load:
Cdr4_xp

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: MPSampleSubmission
Event Category: None
Event ID: 5000
Date: 8/2/2007
Time: 2:09:13 AM
User: N/A
Computer: TEAM-H_AND_L
Description:
EventType mptelemetry, P1 80072ee2, P2 endsearch, P3 search, P4 1.1.1593.0,
P5 mpsigdwn.dll, P6 1.1.1593.0, P7 windows defender, P8 NIL, P9 NIL, P10 NIL.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 6d 00 70 00 74 00 65 00 m.p.t.e.
0008: 6c 00 65 00 6d 00 65 00 l.e.m.e.
0010: 74 00 72 00 79 00 2c 00 t.r.y.,.
0018: 20 00 38 00 30 00 30 00 .8.0.0.
0020: 37 00 32 00 65 00 65 00 7.2.e.e.
0028: 32 00 2c 00 20 00 65 00 2.,. .e.
0030: 6e 00 64 00 73 00 65 00 n.d.s.e.
0038: 61 00 72 00 63 00 68 00 a.r.c.h.
0040: 2c 00 20 00 73 00 65 00 ,. .s.e.
0048: 61 00 72 00 63 00 68 00 a.r.c.h.
0050: 2c 00 20 00 31 00 2e 00 ,. .1...
0058: 31 00 2e 00 31 00 35 00 1...1.5.
0060: 39 00 33 00 2e 00 30 00 9.3...0.
0068: 2c 00 20 00 6d 00 70 00 ,. .m.p.
0070: 73 00 69 00 67 00 64 00 s.i.g.d.
0078: 77 00 6e 00 2e 00 64 00 w.n...d.
0080: 6c 00 6c 00 2c 00 20 00 l.l.,. .
0088: 31 00 2e 00 31 00 2e 00 1...1...
0090: 31 00 35 00 39 00 33 00 1.5.9.3.
0098: 2e 00 30 00 2c 00 20 00 ..0.,. .
00a0: 77 00 69 00 6e 00 64 00 w.i.n.d.
00a8: 6f 00 77 00 73 00 20 00 o.w.s. .
00b0: 64 00 65 00 66 00 65 00 d.e.f.e.
00b8: 6e 00 64 00 65 00 72 00 n.d.e.r.
00c0: 2c 00 20 00 4e 00 49 00 ,. .N.I.
00c8: 4c 00 2c 00 20 00 4e 00 L.,. .N.
00d0: 49 00 4c 00 20 00 4e 00 I.L. .N.
00d8: 49 00 4c 00 0d 00 0a 00 I.L.....

Event Type: Error
Event Source: Ci
Event Category: CI Service
Event ID: 4126
Date: 7/30/2007
Time: 11:29:18 PM
User: N/A
Computer: TEAM-H_AND_L
Description:
Cleaning up corrupt content index metadata on f:\system volume
information\catalog.wci. Index will be automatically restored by refiltering
all documents.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I had one shutdown tonight at approximately 7:30 p.m. EST but it does not
show in any of the error logs.


"lantierl" wrote:

> Chris,
> Thanks for the response.
> To answer some of the questions:
> - I bought a new power strip with EMI/RF protection, based on the chance
> that part of the problem may be due to "dirty" power from my old power strip.
> But, I see no noticeable difference in crash frequency.
> - I have been using the ABIT EQ monitor to watch temperatures, and all
> appear to be in specifications.
> - As for overclocking, I am using the default settings from the motherboard.
> I have read everything I can on the AMD ATHLON 64 pages and the ABIT UL8
> motherboard pages to find out the exact BIOS settings for the DDR, HTT, and
> CPU speeds and voltages, as most are set to autmoatic or default. I also
> e-mailed Abit and AMD asking for technical assistance in getting the correct
> settings for these and other SoftMenu BIOS settings that I was not familiar
> with and had used the defaults for, in the off chance that it is a BIOS
> setting that is causing my crash errors.
> - With regard to the F: instead of C: drive, great question! I am using a
> SATA hard drive instead of IDE, and the system would not let me rename it to
> C: (forced to use F:). Thereofre, I had to alias all C: references to F: so
> that anything looking for C: finds it on the F:, if that makes sense. Of
> course, I forget the command I used to do that, and had to research that when
> I first built the machine. The only thing I have on IDE is a ZIP disk master
> with no slave.
> - Video card is a Radeon 9550. Older card, PCI, not PCI-express.
> -Lastly, I learned of the Event Viewer today and will try that out tonight,
> then post error messages here, if I can figure out how to use it with the
> information provided by both you and Gerry.
>
>
> "Chris" wrote:
>
> >
> >
> > "lantierl" wrote:
> >
> > > I am unable to determine the root cause of my system crashes that show the
> > > following on the blue screen crash page summary:
> > > MACHINE_CHECK_EXCEPTION
> > > STOP: 0x0000009C (0x00000004, 0x8054D570, 0xB2000010, 0x00010C0F) I built
> > > this machine from scratch about a year ago, and have experienced infrequent,
> > > untimely crashes such as this with varying degrees of frequency. When it
> > > first occurred, I ran MEMTEST386 and found bad memory, which Kingston
> > > replaced free of charge. Even with the new memory, the crashes have continued.
> > > I have run MEMTEST386 and other memory checks and see no issues with the new
> > > memory. I am running Windows XP Home on an AMD ATHLON 64 CPU on an ABIT UL8
> > > motherboard with a 420W power supply and 1GB of RAM (two 512 MB dual channel
> > > DDR Kingston KVR400AK2/1GR).
> > > I have run a multitude of system checks including Norton Systemworks,
> > > MacAfee scan, Kaspersky scan, Trendmicro scan, Adware SE scan, Ewidoscan, and
> > > Spybot scan.
> > > How do I determine what the problem is to decided what to do to make this
> > > frsutrating error STOP?
> > > I don't know what else to check and need help resolving the issue.
> > > Microsoft's web pagefor this kind of stop is:
> > > http://support.microsoft.com/kb/329284
> > > But... the cause refers to Pentium, not AMD (and I have an AMD processor,
> > > not a Pentium).
> > > System information is as follows:
> > > OS Name Microsoft Windows XP Home Edition Version 5.1.2600 Service Pack 2
> > > Build 2600 OS Manufacturer Microsoft Corporation System Name TEAM-H_AND_L
> > > System Manufacturer AWARD_ System Model AWRDACPI System Type X86-based PC
> > > Processor x86 Family 15 Model 47 Stepping 2 AuthenticAMD ~2249 Mhz BIOS
> > > Version/Date Phoenix Technologies, LTD 6.00 PG, 3/10/2006 SMBIOS Version 2.3
> > > Windows Directory F:\WINDOWS System Directory F:\WINDOWS\system32 Boot Device
> > > \Device\HarddiskVolume1 Locale United States Hardware Abstraction Layer
> > > Version = "5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)"
> > > User Name TEAM-H_AND_L\Lance
> > > Time Zone Eastern Daylight Time
> > > Total Physical Memory 1,024.00 MB
> > > Available Physical Memory 657.45 MB
> > > Total Virtual Memory 2.00 GB
> > > Available Virtual Memory 1.96 GB
> > > Page File Space 2.41 GB
> > > Page File F:\pagefile.sys
> > >
> > > Help????
> >
> >
> >
> > Hi,
> >
> > From the sounds of it you have pretty much ruled out RAM in this issue. If
> > you have run multiple RAM testers odds are the RAM is good. The knowledge
> > base article you listed gives pretty good advice on what your next steps
> > should be. It does not however only say it's for pentium processors like you
> > said. It mentioned a mechanism for testing hardware errors with that type of
> > processors. So I would still try the other suggestions the article gave.
> >
> > • 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.
> >
> > If you over clocked your processor the first item could be a reason why it
> > isn't working.
> >
> > Try a different surge protector, I personally have seen many issues caused
> > by an old surge protector that isn't working well. And if you're plugged in
> > directly to a wall that could definetly be a possible cause to your problem.
> >
> > Abit motherboards have a temperature monitor built into their bios'. I
> > would just sit in your bios screen and monitor how hot your machine is
> > getting.
> >
> > You will also want to check out your event viewer. Right click on my
> > computer and go to manage. On the left hand side of the window there should
> > be an menu stating event viewer. System events and applications events may
> > give you many more hints on to what the problem could be.
> >
> > If those items don't help you. Power could still be an issue. It's possible
> > 420 watts aren't enough for your system. What kind of video card do you
> > have? It could pull a lot of power. Maybe you need to go up to a bigger
> > power supply.
> >
> > Lastly, I have one more question. Why is your system installed on F:?
> > Normally it's C:, that could also be a cause of your problem but doubtful.
> > Hope this info helps you.