Mysterious Stop Mode Errors - Help Needed

[Curt Lindner]

I've been getting a number of stop mode errors on a machine I built
about a year ago. I've started to use the machine more lately, so the
problems are more bothersome now.

System Details:

2.8 GHz P4
1 GB Dual Channel Ram (2 sticks, of course)
Intel D865PERL Mobo
ATI All-in-Wonder 9000 Video
WinXP SP2 (although the problem was pre-SP2 also)

Latest drivers for everything

Error Codes:

0x1000000a
0x1000007f
0x100000d1
0x1000008e
0x10000050
0x100000c2

Until recently, the crashes always occured when AVG was doing its
overnight system scan, but not every time. It would crash maybe once
every two weeks and the scans are run every night. I've recently
turned those off.

I've also been using Shareaza heavily lately, version 2.0 then now
2.1. This definitely seems to be part of the problem.

I also have a couple of printers connected to this machine via USB,
and I use this as the print server for my network. I have had some
crashes while print jobs are spooling also.

I've downloaded and run the memory stress test from Microsoft. That
thing ran for about 3-4 hours without any errors. I would like to
think that this rules out any memory related problems.

What can I do??? I'd reinstall the OS from scratch, but before I do
that, I would like to be sure that it will solve the problem, because
it will take me a few days work to get everything back in shape.

Thanks for any help you folks can provide!

-Curt

 

[Malke]

I've been getting a number of stop mode errors on a machine I built
about a year ago. I've started to use the machine more lately, so the
problems are more bothersome now.

System Details:

2.8 GHz P4
1 GB Dual Channel Ram (2 sticks, of course)
Intel D865PERL Mobo
ATI All-in-Wonder 9000 Video
WinXP SP2 (although the problem was pre-SP2 also)

Latest drivers for everything

Error Codes:

0x1000000a
0x1000007f
0x100000d1
0x1000008e
0x10000050
0x100000c2

Until recently, the crashes always occured when AVG was doing its
overnight system scan, but not every time. It would crash maybe once
every two weeks and the scans are run every night. I've recently
turned those off.

I've also been using Shareaza heavily lately, version 2.0 then now
2.1. This definitely seems to be part of the problem.

I also have a couple of printers connected to this machine via USB,
and I use this as the print server for my network. I have had some
crashes while print jobs are spooling also.

I've downloaded and run the memory stress test from Microsoft. That
thing ran for about 3-4 hours without any errors. I would like to
think that this rules out any memory related problems.

What can I do??? I'd reinstall the OS from scratch, but before I do
that, I would like to be sure that it will solve the problem, because
it will take me a few days work to get everything back in shape.

We actually need the whole Stop Error, not just the address. Here's a
link to help troubleshoot your Stop Errors:

http://www.aumha.org/win5/kbestop.htm

I would do a RAM test, too. I like Memtest86 from www.memtest86.com. You
can make either a bootable floppy (get the precompiled Windows binary)
or a bootable cd (get the .iso) if you have third-party burning
software like Nero or Roxio.

Malke

 

[Curt Lindner]

We actually need the whole Stop Error, not just the address. Here's a
link to help troubleshoot your Stop Errors:

The point was that it isn't the same error over and over. I'll send
the minidumps if anyone wants them. I didn't think it would be very
helpful to post all the addresses, just the ones that one can find at
any of the pages such as the one your referenced.

I would do a RAM test, too. I like Memtest86 from www.memtest86.com. You
can make either a bootable floppy (get the precompiled Windows binary)
or a bootable cd (get the .iso) if you have third-party burning
software like Nero or Roxio.

As I indicated in my post, I ran the memory test from Microsoft. I
figured that would be sufficient. It ran a very exhaustive battery of
tests, and I let it run for hours.

I'm wondering if I should try relaxing the memory parameters (latency
and such) in my mobos bios to see if that would help.

The memory is Kingston HyperX brand....

Thanks,

-Curt

 

[NoNoBadDog!]

From the number of errors, it is almost certainly a RAM issue. And *ANY*
P2P program is an invite to disaster.

Bobby

 

[Steve Nielsen]

The point was that it isn't the same error over and over. I'll send
the minidumps if anyone wants them. I didn't think it would be very
helpful to post all the addresses, just the ones that one can find at
any of the pages such as the one your referenced.




As I indicated in my post, I ran the memory test from Microsoft. I
figured that would be sufficient. It ran a very exhaustive battery of
tests, and I let it run for hours.

I'm wondering if I should try relaxing the memory parameters (latency
and such) in my mobos bios to see if that would help.

The memory is Kingston HyperX brand....

Thanks,

-Curt

The memory test from MS is actually the same as memtest86, but it may
not be the latest build. I'd go to the memtest86 site and dl the latest
build.

Steve

 

[Curt Lindner]

The memory test from MS is actually the same as memtest86, but it may
not be the latest build. I'd go to the memtest86 site and dl the latest
build.

Steve, I did go ahead and run the memtest86 tonight. It ran 8 passes
in about 1 hour, 15 minutes. No errors.

I'm just looking for someone to give me a clue as to which direction
to look!!! Help!!!!

-Curt

 

[Steve Nielsen]

Steve, I did go ahead and run the memtest86 tonight. It ran 8 passes
in about 1 hour, 15 minutes. No errors.

I'm just looking for someone to give me a clue as to which direction
to look!!! Help!!!!

-Curt

I'm sorry if I may have missed it if you said so, but have you tested
the hard disk using CHKDSK /F, CHKDSK /R, and the drive manufacturer's
utilities? I've been seeing more and more STOP errors that appear to be
caused by file system errors and bad sectors, since these are the only
problems I've been able to uncover in some cases. Correcting the disk
errors and/or bad sectors hasn't always solved the problems and
sometimes a repair install was required to replace corrupted system
files as well.

If your system came with a utilities CD (or if utils can be downloaded
from the manufacturer) I'd also test all the system hardware you can.

Steve

 

[Curt Lindner]

I'm sorry if I may have missed it if you said so, but have you tested
the hard disk using CHKDSK /F, CHKDSK /R, and the drive manufacturer's
utilities? I've been seeing more and more STOP errors that appear to be
caused by file system errors and bad sectors, since these are the only
problems I've been able to uncover in some cases. Correcting the disk
errors and/or bad sectors hasn't always solved the problems and
sometimes a repair install was required to replace corrupted system
files as well.

Steve, this could be the case. My secondary drive did have quite a
few errors on it. I wouldn't have thought this could be the problem,
as I didn't think anything was running off of that drive, but when I
try to run an error check, it won't complete unless I run it through
command prompt, and allow the drive to be unmounted before performing
the check.

I ran it through several cycles, and everything seems to be cleaned
up. I can now run a check through the properties dialog for the
drive, and everything seems OK. I'll push the machine hard today and
see if I have more problems.

I was already planning to do a full reinstall, so hopefully this will
cure my problems before I have to go through that pain!

Thanks,

-Curt

 

[Curt Lindner]

Steve, this could be the case. My secondary drive did have quite a
few errors on it. I wouldn't have thought this could be the problem,
as I didn't think anything was running off of that drive, but when I
try to run an error check, it won't complete unless I run it through
command prompt, and allow the drive to be unmounted before performing
the check.

Well, I haven't had a single error since I corrected the errors on
this secondary hard drive. This seems to have been the problem.

That certainly explains the crashes I was having while running the
anti-virus scans at night, as it would crash when it hit a bad spot on
the drive. However, I'm still not sure why it was crashing when
nothing apparant was going on on the secondary drive.

Anyway, I'm certainly a happy camper now, and I'm sure no one is
reading this, but maybe this will help some poor soul who comes
googling along after me.

-Curt

 

[Malke]

Well, I haven't had a single error since I corrected the errors on
this secondary hard drive. This seems to have been the problem.

That certainly explains the crashes I was having while running the
anti-virus scans at night, as it would crash when it hit a bad spot on
the drive. However, I'm still not sure why it was crashing when
nothing apparant was going on on the secondary drive.

Anyway, I'm certainly a happy camper now, and I'm sure no one is
reading this, but maybe this will help some poor soul who comes
googling along after me.

-Curt

I'm reading it, and I'm glad you got it sorted. Thanks for letting us
know.

Malke

 

[Curt Lindner]

I'm reading it, and I'm glad you got it sorted. Thanks for letting us
know.

Well, the problem persists. I've now taken the extra step of turning
off the automatic reboot, although a couple of times it hasn't given
me any info on the driver that caused the crash. One time it
indicated that tcpip.sys was at fault.

Microsoft OCA has been typically reporting these as type 1055798
errors.

Today I have removed the pagefile, defragmented the drive until there
were 0% fragmented files, then recreated the swap file.

This is really, really frustrating. I would just reinstall from
scratch, but I see nothing that makes me believe that this would solve
the problem.

Is there a way to make sure my networking drivers haven't been
tampered with. I've seen some utilities out there, but I'm afraid
that they will do further damage, as they aren't from microsoft.....

Anyone have any ideas????

-Curt