Diagnostic Tool for XP

  • Thread starter Thread starter Melvin F
  • Start date Start date
M

Melvin F

I built my own PC. I've built several over the last few years. I used to
run Win2K. I upgraded over the last month to XP pro.

I'm starting to run into blue screens. The message varys. Some times
they're 0XD1 or 0X0A.

I've been doing a lot of reading to resolve this. I've disabled a boatload
of drivers that weren't "signed". Still got the errors. I then booted up
into safe mode. This time, got a 0X7F. I started thinking hardware??

I'd like to run a diagnostic utility to test the CPU and RAM. Can someone
tell me where I can find one? Should one have come with my mainboard?

M
 
I agree the ram is suspect. If you want to check the memory, there are free
programs here:

http://www.simmtester.com/page/products/doc/download.asp
http://oca.microsoft.com/en/windiag.asp

Could be the results of overclocking as well - check that all MB settings
are on defaults for the system hardware. If the system was OC'ed at one
point, the damage it did may be permanent. WinXP is particularly sensitive
to this sort of damaged hardware and does not react well to it.

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Windows
Windows isn't rocket science! That's my other hobby!

Associate Expert - WinXP - Expert Zone
 
Hey, thanks for the link to the RAM diag. program.

But that doesn't appear to be it. I've let this program diagnose for
hours and hours. No problems detected.

I've never overclocked this machine. Is there another utility that will
stress / test the CPU and report problems? There's a program I run that
is a real CPU hog, it can run about 2 minutes or so and then blue
screen. It's not usuing up memory, at least task manager show's that.
It also works flawlessly on Win2K and Win98.

Any ideas?

M
 
Since the RAM checks out and the system has never been overclocked, is
there a way to make XP not so "sensitive" or should I consider replacing
the mainboard and CPU?

Right now I'm using a Biostar mainboard and an AMD Athlon XP 2100. I wish
I could find a utility that would help diagnose the mainboard before I put
the cash out to replace it.

M
 
Hi,

Well, there's no way to "de-sensitize" WindowsXP, but you might want to run
through this first:

Troubleshooting a Stop 0x0000000A Error in Windows XP [Q314063]
http://support.microsoft.com/?kbid=314063

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Windows
Windows isn't rocket science! That's my other hobby!

Associate Expert - WinXP - Expert Zone
 
I agree the ram is suspect. If you want to check the memory, there are
free programs here:

http://www.simmtester.com/page/products/doc/download.asp
http://oca.microsoft.com/en/windiag.asp

Could be the results of overclocking as well - check that all MB
settings are on defaults for the system hardware. If the system was
OC'ed at one point, the damage it did may be permanent. WinXP is
particularly sensitive to this sort of damaged hardware and does not
react well to it.

Rick (or whomever can help),

I put this PC in the closet for a few months because it kept blue
screening. I ran the RAM diags and found nothing. I found a copy of the
cpustress program from the resource kit. When I stress the CPU to 100%, it
will blue screen after about 15 seconds. Running an AMD Athlon 2100
*never* overclocked this guy. All the MB setting are at default. A couple
questions:

1) Would it be the CPU or motherboard that needs replacing?
2) Could it be heat related?

M
 
Melvin said:
Rick (or whomever can help),

I put this PC in the closet for a few months because it kept blue
screening. I ran the RAM diags and found nothing. I found a copy of
the
cpustress program from the resource kit. When I stress the CPU to
100%, it
will blue screen after about 15 seconds. Running an AMD Athlon 2100
*never* overclocked this guy. All the MB setting are at default. A
couple questions:

1) Would it be the CPU or motherboard that needs replacing?
2) Could it be heat related?

M

1) Could be either one.
2) Yes.

Sorry not to be more specific, but you really need to test your
hardware. Best to take it to a good local shop where they will have the
equipment and facilities to do this.

Malke
 
1) Could be either one.
2) Yes.

Sorry not to be more specific, but you really need to test your
hardware. Best to take it to a good local shop where they will have the
equipment and facilities to do this.

Malke

Found out what the problem was. It WAS heat. The CPU heat sink was
clogged with dust bunnies. Blew out the chasis and installed an
additional fan - all is fine now.

Mel
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top