I for one am beginning to feel that most of these problems are XP bugs.
I have been getting exactly the same error messages, my pc started rebooting
for no apparent reason several weeks ago. Occassionally I get feedback from
Microsoft stating the error lies with Iomegaware ( I have a zip 250 scsi
attached to an Adaptec 2940 scsi card), Microsoft recommended I use a patch
supplied by Iomega, which I did, however this did not solve the problem. I
sunsequently contacted Iomega, who advised me to revert to a previous
version of Iomegaware and then use the patch. This I also did to no avail.
I also get the problem of XP not remembering folder views, which also seems
a common problem.
I recently posted a message listing some of the problems I was experiencing
with XP, but had no replies.
One thing I do know is that most of my problems started after downloading
and installing a few updates from the Microsoft update site, perhaps it is
one of these that is causing the problem, who knows and I feel that
Microsoft themselves will never admit their software is at fault. The only
thing they have admitted to me is that one of the updates, causes Microsoft
Photodraw to stop working...... their answer to this problem was to withdraw
Photodraw... sucks really.
Maybe some day, someone will find a cure for these problems, till then I
like others will no doubt keep posting and asking the questions.
T. Morton said:
I too, have the dreaded random reboots, for about 2 weeks now. I have an
eMachines with an Athlon 2200+. I'm pretty certain it's hardware related,
since I've done a full restore, and even changed hard disks, and still get
the same errors. I've also ruled out the power supply (bought a new one),
and the video adapter (switched from my GeForce in the AGP slot back to
onboard graphics for the restore. The XP site tells me after the error
message is sent that it's an unknown device driver each time.
Nels, XP by default does an automatic restart instead of a blue screen.
You have to go to cotrol panel>system>advanced>startup & recovery settings
and uncheck the box by "automatic restart" in order to see the blue screen.
But Carey's post will get you the same relevant info in an easier to read
format. Here's the most recent error message I got. The descritions on the
BSOD are nearly random, though, it seems to be a slightly different error
each time.
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 2/26/2004
Time: 3:36:23 AM
User: N/A
Computer: YOUR-KUH1EVX06W
Description:
Error code 000000c2, parameter1 00000007, parameter2 00000cd4, parameter3 e108fb80, parameter4 e10d4fa8.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 63 000000c
0020: 32 20 20 50 61 72 61 6d 2 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 37 2c 20 000007,
0038: 30 30 30 30 30 63 64 34 00000cd4
0040: 2c 20 65 31 30 38 66 62 , e108fb
0048: 38 30 2c 20 65 31 30 64 80, e10d
0050: 34 66 61 38 4fa8
Any ideas? Also, a layman's explanation on how to try to isolate the
alleged device driver that is causing the problem would be appreciated. I
found the MS article on troubleshooting, but it's a bit thick for me.
