Getting a bunch of infrequent stop errors
Hi all - This is my latest stop in trying to find out what is going on with my machine. I bought it last March, and it was running fine until this year. Now I'm getting a stop error every x number of days. Nothing I can replicate.
01/01/08 1000008e, parameter1 c0000005, parameter2 bf8011a3, parameter3 f77fda48, parameter4 00000000.
01/07/08 100000d1, parameter1 00000001, parameter2 00000002, parameter3 00000000, parameter4 aa67fc31
01/10/08 00000019, parameter1 00000020, parameter2 e5282330, parameter3 e5282370, parameter4 0c080808.
01/26/08 000000d1, parameter1 00000000, parameter2 00000002, parameter3 00000008, parameter4 00000000
<O:p02/04/08 000000d1, parameter1 00000000, parameter2 00000002, parameter3 00000008, parameter4 00000000
<O:p02/08/08 DRIVER_IRQL_NOT_LESS_OR_EQUAL 000000d1 (was not logged)
<O:p02/17/08 1000008e, parameter1 80000003, parameter2 804ef060, parameter3 f77cd78c, parameter4 00000000
<O:pI also found a mini dump dated 12/15/07, but I don't recall the crash.
I didn't install any new hardware or software.
I'm using XP Home Edition.
Any ideas about what is going on?</O:p
<O:p</O:p
<O:p</O:p</O:p</O:p
01/01/08 1000008e, parameter1 c0000005, parameter2 bf8011a3, parameter3 f77fda48, parameter4 00000000.
01/07/08 100000d1, parameter1 00000001, parameter2 00000002, parameter3 00000000, parameter4 aa67fc31
01/10/08 00000019, parameter1 00000020, parameter2 e5282330, parameter3 e5282370, parameter4 0c080808.
01/26/08 000000d1, parameter1 00000000, parameter2 00000002, parameter3 00000008, parameter4 00000000
<O:p02/04/08 000000d1, parameter1 00000000, parameter2 00000002, parameter3 00000008, parameter4 00000000
<O:p02/08/08 DRIVER_IRQL_NOT_LESS_OR_EQUAL 000000d1 (was not logged)
<O:p02/17/08 1000008e, parameter1 80000003, parameter2 804ef060, parameter3 f77cd78c, parameter4 00000000
<O:pI also found a mini dump dated 12/15/07, but I don't recall the crash.
I didn't install any new hardware or software.
I'm using XP Home Edition.
Any ideas about what is going on?</O:p
<O:p</O:p
<O:p</O:p</O:p</O:p
0
Comments
Boot into memtest, and see if you get any errors.
Thanks for the suggestion, but I already tried that. I let if run for a few hours, and never got an error.
Something I tried today was blowing all the dust out of the CPU. I didn't think there would be much there, since it's not even a year old yet, but it caused quite a dust storm! I didn't think it was an over heating problem, because I got one error during boot up when it was off all night, and it always worked after rebooting for the other errors. Still, I read somewhere that dirty computers can cause crashes. Time will tell.
I had 2 more crashed (3/2 and 3/12). Then a couple of weeks before my warranty expired, I took my PC back to the PC-Club where I bought it. They ran continuous stress tests for nearly 3 days, and it didn't fail. I brought it home, and it crashed twice in the following week (3/16 and 3/24). After the last crash, I ran the Microsoft on-line registry cleaner (http://onecare.live.com/site/en-US/center/cleanup.htm) I don't know if that is what fixed it, but it has been stable since then.
I hope I didn't jinx it by posting this