26 Crashes so far Caused by a Device Driver

M

m630

MADDENING!
Over past 2 weeks, suddenly without warning, XP system
crash. "Error Caused by a Device Driver" on crash
analysis. Nothing more. Nothing in MS support help to
deal with the error type code numbers: in sequence, they
have been: 671198, 209, 671198, 670228, 1633002, 216026,
4330, 209, 433.
No driver conflicts in device manager. I can't sys
restore any further back.
I've tried uninstalling programs and devices one at a
time to try to eliminate the problem, so far nothing.
Would upgrading to XP Pro help at all????
 
G

Guest

-----Original Message-----
MADDENING!
Over past 2 weeks, suddenly without warning, XP system
crash. "Error Caused by a Device Driver" on crash
analysis. Nothing more. Nothing in MS support help to
deal with the error type code numbers: in sequence, they
have been: 671198, 209, 671198, 670228, 1633002, 216026,
4330, 209, 433.
No driver conflicts in device manager. I can't sys
restore any further back.
I've tried uninstalling programs and devices one at a
time to try to eliminate the problem, so far nothing.
Would upgrading to XP Pro help at all????

Go look here coz it happen the same thing has me...
US;239924
 
W

William Ingle

Maddened

I ran into a very similar sequence of symptoms and the problem turned out to
be temperature. When the motherboard or main processor temperature reached
60 C the system rebooted and whoever had the processor at the time was
blamed. Since this temperature check was presumeably done by a regularly
occurring callout in the scheduler a driver was consistently blamed for the
reboot. I bought a new case with better temperature characteristics and
more fans. I made sure they were all running and no reboots. In your case
you may have one or more fans failing. You do not necessarily need a new
case. Many newer motherboards come with monitoring tools on their driver
cd. With it you can keep tabs on your processor temperature as you use your
system.

I hope this helps
-Bill
 
G

Guest

-----Original Message-----
MADDENING!
Over past 2 weeks, suddenly without warning, XP system
crash. "Error Caused by a Device Driver" on crash
analysis. Nothing more. Nothing in MS support help to
deal with the error type code numbers: in sequence, they
have been: 671198, 209, 671198, 670228, 1633002, 216026,
4330, 209, 433.
No driver conflicts in device manager. I can't sys
restore any further back.
I've tried uninstalling programs and devices one at a
time to try to eliminate the problem, so far nothing.
Would upgrading to XP Pro help at all????


.
 
M

mrtee

No.

--
Just my 2¢ worth
Jeff
__________in response to__________
|
| >-----Original Message-----
| >MADDENING!
| >Over past 2 weeks, suddenly without warning, XP system
| >crash. "Error Caused by a Device Driver" on crash
| >analysis. Nothing more. Nothing in MS support help to
| >deal with the error type code numbers: in sequence, they
| >have been: 671198, 209, 671198, 670228, 1633002, 216026,
| >4330, 209, 433.
| >No driver conflicts in device manager. I can't sys
| >restore any further back.
| >I've tried uninstalling programs and devices one at a
| >time to try to eliminate the problem, so far nothing.
| >Would upgrading to XP Pro help at all????
| >
| >
| >.
| >
 
R

Ramboi2

Many people complaining about XP in the past, it sure is a nice OS but not when
it failed. Microsoft is too tight on their profit plant, they won't let you
alter and poke things around.

I am glad I stayed away from it. My 2nd system is an XP, I never bother to
upgrade it, the more I upgrade the more troubles I see with XP.

Ramboi
 

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

Top