Hi Frogeye,
I got the same blue screen error message. Do you have an Inspiron 6000?
I Called Dell when I checked the timing of the problem I suspected the error
was being caused by a recent Windows update download. The download acts as a
spyware removal tool. I have Spybot too and didn't want this Microsoft tool
so I did a system restore to back before I started having the problem. The
system restore solved the problem for a few days. I didn't turn off
automatic updates, though, so a few days later I got the same error message
and found that the same tool was the culprit. Did another system restore and
turned off Auto Updater to notify me of updates rather than just install them
automatically.
It doesn't seem to be a driver problem at all but rather the update is
falsly recognizing the driver as a problem. Dell doesn't have an final
answer yet but they're "working on it". This solution might work well for
you too.
Good luck,
Brian
"TheEvilThing" wrote:
> Thanks, I've narrowed it down to (surprise, surprise) hardware drivers. It
> seems WinUp was trying to downgrade some drivers for the dodgy old integrated
> sound card on my MoBo, which the system clearly didn't like.
>
> Thanks for the help.
>
>
> "Jupiter Jones [MVP]" wrote:
>
> > To stop the automatic reboot when error is detected:
> > Right click My Computer and click Properties.
> > Click Advanced tab.
> > Under "Startup and Recovery" click Settings button.
> > Uncheck "Automatically restart".
> > Click OK and follow prompts.
> > If the Stop Error returns, you will be able to read the error message.
> >
> > Do you have a Dell computer?
> > A recent Dell video driver was pushed as a Critical Update and caused issues
> > for many so many the driver was pulled and sent back to Dell for rework.
> >
> > --
> > Jupiter Jones [MVP]
> > http://www3.telus.net/dandemar
> > http://www.dts-l.org
> >
> >
> > "TheEvilThing" <> wrote in message
> > news:CFA3BB79-B7B7-4795-8CC8-...
> > >I can't find the error code because whenever I get a BSOD the computer
> > > IMMEDIATELY reboots, ergo it is impossible to see the problem, except that
> > > there is one. I guess I have no real evidence that it's a stop error
> > > other
> > > than this is the behaviour exhibited by stop errors (on my computer) in
> > > the
> > > past.
> > >
> > > Also, I believe it is related to the critical updates because I remember
> > > trying to update and those being the only updates I downloaded. I was
> > > pretty
> > > sure it WAS a driver. Now I'm not so sure, considerin that. Anyway, I
> > > don't
> > > want to have to spend any more time reinstalling Windows to see if that's
> > > the
> > > case. Most of the programs already crash intermittently for no
> > > discernable
> > > reason since I first updated.
> > >
> > >
> > > "Jupiter Jones [MVP]" wrote:
> > >
> > >> For the Stop Error, try this page:
> > >> http://aumha.org/win5/kbestop.htm
> > >>
> > >> Are you installing any Driver Updates? Don't.
> > >> Instead get the drivers directly from the manufacturers website.
> >
> >
> >