i have got a mate to build me a computer. more often than not the computer
keeps crashing and goes to a blue screen where a message comes up stating an
error has occored and that i need to disable bios memory such as caching or
shadowing and that is is dumping physical memory then it counts up to 100 and
restarts. when the computer all loads up again windows error reporting comes
up so i click on send and it comes back with 'windows error report: a device
driver installed on comp caused windows to stop unexpectedly. This type of
error is referred to as a "stop erro". Can someone tell me why this happens
and how I can fix the computer to stop it from keep coming up with the blue
screen?

Just like the message says, a device driver is causing it. Have you added a
device (hardware or software) recently? Update all the drivers you can.

"richeo" <richeo@discussions.microsoft.com> wrote in message
news:277B3B11-957F-4894-B8B0-DC322F694F77@microsoft.com...
>i have got a mate to build me a computer. more often than not the computer
> keeps crashing and goes to a blue screen where a message comes up stating
> an
> error has occored and that i need to disable bios memory such as caching
> or
> shadowing and that is is dumping physical memory then it counts up to 100
> and
> restarts. when the computer all loads up again windows error reporting
> comes
> up so i click on send and it comes back with 'windows error report: a
> device
> driver installed on comp caused windows to stop unexpectedly. This type of
> error is referred to as a "stop erro". Can someone tell me why this
> happens
> and how I can fix the computer to stop it from keep coming up with the
> blue
> screen?

a device driver is causing your syte to crash for whatever reason.
point is to correct it.
look up stop error 0xxxxxxx in google and see what it refers to.

during this problem you might want to go into you bios set up
and disable bios and video bios caching like it says.
this runs the code from the chip intead of from memory where it can be
corrupted.
and it eliminiates a possible source of problem. when you have the problem
fixed,
certainly reenable those as your system will run faster with them cached.

do you know anything about the bios? it has your settings the computer is
told. (its a machine it dont know). if the settings were changed its
possible
there is a mismatch between bios and windows. i would be extremely careful
in there,
and dont change anything you dont know.

then boot in safe mode if you can (F8 before boot). if that works
you can check the device manager for a device giving you a problem
and disable it. so that you can boot normally and update it.

if you cant get safe mode then problem needs a different hammer.
boot up with boot logging enabled and see where the problem happens.
look up boot logging on google. you have to change the boot.ini file
and append /bootlog to it. aslo have to select F8 and boot logging enabled.
then you get the log in windows\ntbtlog.txt. boots are date-time stamped and
safemode boots are mixed with normal ones in the order they occur.

you can then boot to the recovery console and disable any specific device
you wish.
you may need the windows cd to do this.

best bet is to call your mate again, and ask him to fix it
james



"richeo" <richeo@discussions.microsoft.com> wrote in message
news:277B3B11-957F-4894-B8B0-DC322F694F77@microsoft.com...
>i have got a mate to build me a computer. more often than not the computer
> keeps crashing and goes to a blue screen where a message comes up stating
> an
> error has occored and that i need to disable bios memory such as caching
> or
> shadowing and that is is dumping physical memory then it counts up to 100
> and
> restarts. when the computer all loads up again windows error reporting
> comes
> up so i click on send and it comes back with 'windows error report: a
> device
> driver installed on comp caused windows to stop unexpectedly. This type of
> error is referred to as a "stop erro". Can someone tell me why this
> happens
> and how I can fix the computer to stop it from keep coming up with the
> blue
> screen?

nice reply but how is our mate supposed to get in to do that?
look down the chain

"Colin Barnhorst" <c.barnhorst@comcast.net> wrote in message
news:0F0DAC3B-DCD4-4714-B405-BB754E2F29BD@microsoft.com...
> Just like the message says, a device driver is causing it. Have you added
> a device (hardware or software) recently? Update all the drivers you can.
>
> "richeo" <richeo@discussions.microsoft.com> wrote in message
> news:277B3B11-957F-4894-B8B0-DC322F694F77@microsoft.com...
>>i have got a mate to build me a computer. more often than not the computer
>> keeps crashing and goes to a blue screen where a message comes up stating
>> an
>> error has occored and that i need to disable bios memory such as caching
>> or
>> shadowing and that is is dumping physical memory then it counts up to 100
>> and
>> restarts. when the computer all loads up again windows error reporting
>> comes
>> up so i click on send and it comes back with 'windows error report: a
>> device
>> driver installed on comp caused windows to stop unexpectedly. This type
>> of
>> error is referred to as a "stop erro". Can someone tell me why this
>> happens
>> and how I can fix the computer to stop it from keep coming up with the
>> blue
>> screen?
>

Thank you James. Much more of an interesting and informative answer than
Colin's. I suspected it had something to do with the bios settings but alas I
haven't a clue about the ins and outs of bios and would probably cause more
damage by tinkering around with the bios settings. I'll ask my mate. He is
apparently very good with computers and if I remember rightly I'm sure I did
ask him about bios settings before which lead to a very quizzed and akward
look on his face with just as much of a colourless answer so not sure if he
quite understands how to configure the bios settings or he just couldn't be
bothered to explain it to me. I'll take a good look around on the internet to
see if I can brush up on bios which I'd imagine would take far to long and
would probably be better of just asking on this community or looking in
forums for building computers from scratch or save myself a whole lot of time
and go buy a brand new computer but this isn't really an option for me so
I'll keep trying.

"James W. Long" wrote:

> a device driver is causing your syte to crash for whatever reason.
> point is to correct it.
> look up stop error 0xxxxxxx in google and see what it refers to.
>
> during this problem you might want to go into you bios set up
> and disable bios and video bios caching like it says.
> this runs the code from the chip intead of from memory where it can be
> corrupted.
> and it eliminiates a possible source of problem. when you have the problem
> fixed,
> certainly reenable those as your system will run faster with them cached.
>
> do you know anything about the bios? it has your settings the computer is
> told. (its a machine it dont know). if the settings were changed its
> possible
> there is a mismatch between bios and windows. i would be extremely careful
> in there,
> and dont change anything you dont know.
>
> then boot in safe mode if you can (F8 before boot). if that works
> you can check the device manager for a device giving you a problem
> and disable it. so that you can boot normally and update it.
>
> if you cant get safe mode then problem needs a different hammer.
> boot up with boot logging enabled and see where the problem happens.
> look up boot logging on google. you have to change the boot.ini file
> and append /bootlog to it. aslo have to select F8 and boot logging enabled.
> then you get the log in windows\ntbtlog.txt. boots are date-time stamped and
> safemode boots are mixed with normal ones in the order they occur.
>
> you can then boot to the recovery console and disable any specific device
> you wish.
> you may need the windows cd to do this.
>
> best bet is to call your mate again, and ask him to fix it
> james
>
>
>
> "richeo" <richeo@discussions.microsoft.com> wrote in message
> news:277B3B11-957F-4894-B8B0-DC322F694F77@microsoft.com...
> >i have got a mate to build me a computer. more often than not the computer
> > keeps crashing and goes to a blue screen where a message comes up stating
> > an
> > error has occored and that i need to disable bios memory such as caching
> > or
> > shadowing and that is is dumping physical memory then it counts up to 100
> > and
> > restarts. when the computer all loads up again windows error reporting
> > comes
> > up so i click on send and it comes back with 'windows error report: a
> > device
> > driver installed on comp caused windows to stop unexpectedly. This type of
> > error is referred to as a "stop erro". Can someone tell me why this
> > happens
> > and how I can fix the computer to stop it from keep coming up with the
> > blue
> > screen?
>
>
>

chances are greater finding out whats in the bios looking
in the book that came with the motherboard than on the internet.

basically the only parts you are interested in are the caching of the system
bios
caching of video bios, and the trick part,
enabling or disabling hardware on the motherboard (such as sound card).
the only reason to disable these things, are that they exist in another
form..
did your friend put in a soundblaster or other sound card? then, if the
the motherboard has one built in, you would disable it.
sound cards come with joystick ports, so you would want to disable any on
the motherboard.
if your friend put in a video card, you would also want to disable any on
the motherboard.

its like that. determine whats in the box and where it comes from.


and just for kicks, your bios will have a "safe settings" selection,
in case of emergency.

but...usually that setting is too safe so you end up enabling a few more
things.
for instance if your bios has hyperthreading, the "safe setting" would
disable it.
and you would want to reneable that.

James





"richeo" <richeo@discussions.microsoft.com> wrote in message
news:BEE90258-E418-40AE-8F16-8324B08868A8@microsoft.com...
> Thank you James. Much more of an interesting and informative answer than
> Colin's. I suspected it had something to do with the bios settings but
> alas I
> haven't a clue about the ins and outs of bios and would probably cause
> more
> damage by tinkering around with the bios settings. I'll ask my mate. He is
> apparently very good with computers and if I remember rightly I'm sure I
> did
> ask him about bios settings before which lead to a very quizzed and akward
> look on his face with just as much of a colourless answer so not sure if
> he
> quite understands how to configure the bios settings or he just couldn't
> be
> bothered to explain it to me. I'll take a good look around on the internet
> to
> see if I can brush up on bios which I'd imagine would take far to long and
> would probably be better of just asking on this community or looking in
> forums for building computers from scratch or save myself a whole lot of
> time
> and go buy a brand new computer but this isn't really an option for me so
> I'll keep trying.
>
> "James W. Long" wrote:
>
>> a device driver is causing your syte to crash for whatever reason.
>> point is to correct it.
>> look up stop error 0xxxxxxx in google and see what it refers to.
>>
>> during this problem you might want to go into you bios set up
>> and disable bios and video bios caching like it says.
>> this runs the code from the chip intead of from memory where it can be
>> corrupted.
>> and it eliminiates a possible source of problem. when you have the
>> problem
>> fixed,
>> certainly reenable those as your system will run faster with them cached.
>>
>> do you know anything about the bios? it has your settings the computer is
>> told. (its a machine it dont know). if the settings were changed its
>> possible
>> there is a mismatch between bios and windows. i would be extremely
>> careful
>> in there,
>> and dont change anything you dont know.
>>
>> then boot in safe mode if you can (F8 before boot). if that works
>> you can check the device manager for a device giving you a problem
>> and disable it. so that you can boot normally and update it.
>>
>> if you cant get safe mode then problem needs a different hammer.
>> boot up with boot logging enabled and see where the problem happens.
>> look up boot logging on google. you have to change the boot.ini file
>> and append /bootlog to it. aslo have to select F8 and boot logging
>> enabled.
>> then you get the log in windows\ntbtlog.txt. boots are date-time stamped
>> and
>> safemode boots are mixed with normal ones in the order they occur.
>>
>> you can then boot to the recovery console and disable any specific device
>> you wish.
>> you may need the windows cd to do this.
>>
>> best bet is to call your mate again, and ask him to fix it
>> james
>>
>>
>>
>> "richeo" <richeo@discussions.microsoft.com> wrote in message
>> news:277B3B11-957F-4894-B8B0-DC322F694F77@microsoft.com...
>> >i have got a mate to build me a computer. more often than not the
>> >computer
>> > keeps crashing and goes to a blue screen where a message comes up
>> > stating
>> > an
>> > error has occored and that i need to disable bios memory such as
>> > caching
>> > or
>> > shadowing and that is is dumping physical memory then it counts up to
>> > 100
>> > and
>> > restarts. when the computer all loads up again windows error reporting
>> > comes
>> > up so i click on send and it comes back with 'windows error report: a
>> > device
>> > driver installed on comp caused windows to stop unexpectedly. This type
>> > of
>> > error is referred to as a "stop erro". Can someone tell me why this
>> > happens
>> > and how I can fix the computer to stop it from keep coming up with the
>> > blue
>> > screen?
>>
>>
>>

and did you get in in safe mode,
and what was the STOP Error number?

and assuming you can get in, you can check your progress in the device
manager, esp. in safe mode.

james

"richeo" <richeo@discussions.microsoft.com> wrote in message
news:BEE90258-E418-40AE-8F16-8324B08868A8@microsoft.com...
> Thank you James. Much more of an interesting and informative answer than
> Colin's. I suspected it had something to do with the bios settings but
> alas I
> haven't a clue about the ins and outs of bios and would probably cause
> more
> damage by tinkering around with the bios settings. I'll ask my mate. He is
> apparently very good with computers and if I remember rightly I'm sure I
> did
> ask him about bios settings before which lead to a very quizzed and akward
> look on his face with just as much of a colourless answer so not sure if
> he
> quite understands how to configure the bios settings or he just couldn't
> be
> bothered to explain it to me. I'll take a good look around on the internet
> to
> see if I can brush up on bios which I'd imagine would take far to long and
> would probably be better of just asking on this community or looking in
> forums for building computers from scratch or save myself a whole lot of
> time
> and go buy a brand new computer but this isn't really an option for me so
> I'll keep trying.
>
> "James W. Long" wrote:
>
>> a device driver is causing your syte to crash for whatever reason.
>> point is to correct it.
>> look up stop error 0xxxxxxx in google and see what it refers to.
>>
>> during this problem you might want to go into you bios set up
>> and disable bios and video bios caching like it says.
>> this runs the code from the chip intead of from memory where it can be
>> corrupted.
>> and it eliminiates a possible source of problem. when you have the
>> problem
>> fixed,
>> certainly reenable those as your system will run faster with them cached.
>>
>> do you know anything about the bios? it has your settings the computer is
>> told. (its a machine it dont know). if the settings were changed its
>> possible
>> there is a mismatch between bios and windows. i would be extremely
>> careful
>> in there,
>> and dont change anything you dont know.
>>
>> then boot in safe mode if you can (F8 before boot). if that works
>> you can check the device manager for a device giving you a problem
>> and disable it. so that you can boot normally and update it.
>>
>> if you cant get safe mode then problem needs a different hammer.
>> boot up with boot logging enabled and see where the problem happens.
>> look up boot logging on google. you have to change the boot.ini file
>> and append /bootlog to it. aslo have to select F8 and boot logging
>> enabled.
>> then you get the log in windows\ntbtlog.txt. boots are date-time stamped
>> and
>> safemode boots are mixed with normal ones in the order they occur.
>>
>> you can then boot to the recovery console and disable any specific device
>> you wish.
>> you may need the windows cd to do this.
>>
>> best bet is to call your mate again, and ask him to fix it
>> james
>>
>>
>>
>> "richeo" <richeo@discussions.microsoft.com> wrote in message
>> news:277B3B11-957F-4894-B8B0-DC322F694F77@microsoft.com...
>> >i have got a mate to build me a computer. more often than not the
>> >computer
>> > keeps crashing and goes to a blue screen where a message comes up
>> > stating
>> > an
>> > error has occored and that i need to disable bios memory such as
>> > caching
>> > or
>> > shadowing and that is is dumping physical memory then it counts up to
>> > 100
>> > and
>> > restarts. when the computer all loads up again windows error reporting
>> > comes
>> > up so i click on send and it comes back with 'windows error report: a
>> > device
>> > driver installed on comp caused windows to stop unexpectedly. This type
>> > of
>> > error is referred to as a "stop erro". Can someone tell me why this
>> > happens
>> > and how I can fix the computer to stop it from keep coming up with the
>> > blue
>> > screen?
>>
>>
>>

Firstly, thank you very much for your help. I have got into the Bios set up
by restarting my comp then clicking on delete which took me to a screen that
comes up with a list such as 'standard cmos set up, advanced cmos set up,
power managment' etc. I entered into the advanced cmos set up and disabled
internal cache and external cache (which were set to writeback) and system
bios cacheable. After disabling these I then restarted the comp and although
the comp is running very slow the comp has not crashed as yet and has been
running for about 30 mins now with various applications running. I have
checked device manager and there is nothing there to suggest anything is
wrong. I'm not to sure what or how device manager is going to indicate what
is wrong after disabling the things in the bios as I would have thought it
would have told me anyway? But your clearly far more knowledgable about
computer than me. I don't know what my mate installed on the motherboard and
would have to have a look inside the computer as getting hold of my mate is
very hard. He gave me no manual for the motherboard and I very much doubt he
has one. I think the motherboard is an amd 3000? I think I'm a bit lost here
on what I need to do to correct the problem of the computer keep crashing and
coming up with the blue screen. But from reading what you have very kindly
told me I need to disable any piece of hardware that is installed on the
motherboard that is not being used? What does it mean that now I have
disabled the internal and external cache and system bios cacheable in the
bios that has now stopped my computer from crashing?

"James W. Long" wrote:

>
> chances are greater finding out whats in the bios looking
> in the book that came with the motherboard than on the internet.
>
> basically the only parts you are interested in are the caching of the system
> bios
> caching of video bios, and the trick part,
> enabling or disabling hardware on the motherboard (such as sound card).
> the only reason to disable these things, are that they exist in another
> form..
> did your friend put in a soundblaster or other sound card? then, if the
> the motherboard has one built in, you would disable it.
> sound cards come with joystick ports, so you would want to disable any on
> the motherboard.
> if your friend put in a video card, you would also want to disable any on
> the motherboard.
>
> its like that. determine whats in the box and where it comes from.
>
>
> and just for kicks, your bios will have a "safe settings" selection,
> in case of emergency.
>
> but...usually that setting is too safe so you end up enabling a few more
> things.
> for instance if your bios has hyperthreading, the "safe setting" would
> disable it.
> and you would want to reneable that.
>
> James
>
>
>
>
>
> "richeo" <richeo@discussions.microsoft.com> wrote in message
> news:BEE90258-E418-40AE-8F16-8324B08868A8@microsoft.com...
> > Thank you James. Much more of an interesting and informative answer than
> > Colin's. I suspected it had something to do with the bios settings but
> > alas I
> > haven't a clue about the ins and outs of bios and would probably cause
> > more
> > damage by tinkering around with the bios settings. I'll ask my mate. He is
> > apparently very good with computers and if I remember rightly I'm sure I
> > did
> > ask him about bios settings before which lead to a very quizzed and akward
> > look on his face with just as much of a colourless answer so not sure if
> > he
> > quite understands how to configure the bios settings or he just couldn't
> > be
> > bothered to explain it to me. I'll take a good look around on the internet
> > to
> > see if I can brush up on bios which I'd imagine would take far to long and
> > would probably be better of just asking on this community or looking in
> > forums for building computers from scratch or save myself a whole lot of
> > time
> > and go buy a brand new computer but this isn't really an option for me so
> > I'll keep trying.
> >
> > "James W. Long" wrote:
> >
> >> a device driver is causing your syte to crash for whatever reason.
> >> point is to correct it.
> >> look up stop error 0xxxxxxx in google and see what it refers to.
> >>
> >> during this problem you might want to go into you bios set up
> >> and disable bios and video bios caching like it says.
> >> this runs the code from the chip intead of from memory where it can be
> >> corrupted.
> >> and it eliminiates a possible source of problem. when you have the
> >> problem
> >> fixed,
> >> certainly reenable those as your system will run faster with them cached.
> >>
> >> do you know anything about the bios? it has your settings the computer is
> >> told. (its a machine it dont know). if the settings were changed its
> >> possible
> >> there is a mismatch between bios and windows. i would be extremely
> >> careful
> >> in there,
> >> and dont change anything you dont know.
> >>
> >> then boot in safe mode if you can (F8 before boot). if that works
> >> you can check the device manager for a device giving you a problem
> >> and disable it. so that you can boot normally and update it.
> >>
> >> if you cant get safe mode then problem needs a different hammer.
> >> boot up with boot logging enabled and see where the problem happens.
> >> look up boot logging on google. you have to change the boot.ini file
> >> and append /bootlog to it. aslo have to select F8 and boot logging
> >> enabled.
> >> then you get the log in windows\ntbtlog.txt. boots are date-time stamped
> >> and
> >> safemode boots are mixed with normal ones in the order they occur.
> >>
> >> you can then boot to the recovery console and disable any specific device
> >> you wish.
> >> you may need the windows cd to do this.
> >>
> >> best bet is to call your mate again, and ask him to fix it
> >> james
> >>
> >>
> >>
> >> "richeo" <richeo@discussions.microsoft.com> wrote in message
> >> news:277B3B11-957F-4894-B8B0-DC322F694F77@microsoft.com...
> >> >i have got a mate to build me a computer. more often than not the
> >> >computer
> >> > keeps crashing and goes to a blue screen where a message comes up
> >> > stating
> >> > an
> >> > error has occored and that i need to disable bios memory such as
> >> > caching
> >> > or
> >> > shadowing and that is is dumping physical memory then it counts up to
> >> > 100
> >> > and
> >> > restarts. when the computer all loads up again windows error reporting
> >> > comes
> >> > up so i click on send and it comes back with 'windows error report: a
> >> > device
> >> > driver installed on comp caused windows to stop unexpectedly. This type
> >> > of
> >> > error is referred to as a "stop erro". Can someone tell me why this
> >> > happens
> >> > and how I can fix the computer to stop it from keep coming up with the
> >> > blue
> >> > screen?
> >>
> >>
> >>
>
>
>

Go ask here microsoft.public.windowsxp.hardware


"richeo" <richeo@discussions.microsoft.com> wrote in message
news:277B3B11-957F-4894-B8B0-DC322F694F77@microsoft.com...
>i have got a mate to build me a computer. more often than not the computer
> keeps crashing and goes to a blue screen where a message comes up stating
> an
> error has occored and that i need to disable bios memory such as caching
> or
> shadowing and that is is dumping physical memory then it counts up to 100
> and
> restarts. when the computer all loads up again windows error reporting
> comes
> up so i click on send and it comes back with 'windows error report: a
> device
> driver installed on comp caused windows to stop unexpectedly. This type of
> error is referred to as a "stop erro". Can someone tell me why this
> happens
> and how I can fix the computer to stop it from keep coming up with the
> blue
> screen?