xp xrashing

[Guest]

i have xp crashing on me and i think it is because of a driver conflict,
though i am not sure which driver is causing the crash.
what would be the best way to isolate the dirver that is causing xp to crash

i'm thinking of using device manager to disable drivers one at a time,
crossing one off the ones that dont crash the system

has anyone got a more efficent way of tracking down which diver is the
culprit?

is using the device manager the right way to go, all recommendations
appreciated.

 

[Plato]

I, I'm, Has, Is, What

i have xp crashing on me and i think it is because of a driver conflict,
though i am not sure which driver is causing the crash.
what would be the best way to isolate the dirver that is causing xp to crash

i'm thinking of using device manager to disable drivers one at a time,
crossing one off the ones that dont crash the system

has anyone got a more efficent way of tracking down which diver is the
culprit?

is using the device manager the right way to go, all recommendations
appreciated.

 

[Brian A.]

What makes you think it's a device driver? Don't you get any type of error
message when it crashes? Crashes can be caused by numerous problems from either
software or hardware.

Boot to Safe Mode, it only loads the minimal drivers needed to boot.

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

 

[Guest]

yeah pretty sure its a driver, if its not the blue screens, xp is
spontainously restarting on me or just haning till i hit restart. i really am
having trouble with this one

i have recovered one of these messages for the events viewer

BCCode : 24 BCP1 : 001902F8 BCP2 : F2F6E454 BCP3 : F2F6E154
BCP4 : 80040003 OSVer : 5_1_2600 SP : 0_0 Product : 256_1

Error code 00000024, parameter1 001902f8, parameter2 f2f6e454, parameter3
f2f6e154, parameter4 80040003.

anyone understand this?

Faulting application explorer.exe, version 6.0.2600.0, faulting module
wmvcore.dll, version 10.0.0.3646, fault address 0x00042158.

or this

Faulting application explorer.exe, version 6.0.2600.0, faulting module ,
version 0.0.0.0, fault address 0x00000000.

or how about that?

any pointer would be tops!

 

[Brian A.]

The first thing to do is check the memory module/s and make sure they are
seated properly. If they are and there are more than one installed, try
removing one to see if it resolves the issue. If it doesn't, replace it with
the module that was removed and see if it resolves the issue. If after removing
a module resolves the issue then that is a bad module.

If after checking the modules did not help, test the memory with:
http://www.memtest86.com/
If you want a second opinion: http://oca.microsoft.com/en/windiag.asp

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

 

[Guest]

Brian A i think you have hit the nail on the head

i ran memtest and while an error didnt come up, it did trip the system into
a restart after about 17 mins of testing. I guess the next question is how to
accertain which is responsible the slot or the memory, possibly some rotation
is required?

What would you reccommend?

 

[Brian A.]

As stated before although maybe not clearly, if you have more than 1 module
pull all except one. If no problems arise, add another, then another and so on.
That will help isolate which module or slot (not likely but possible). To check
the slot you may think is bad, simply put one of the other modules in it that
didn't produce the problem. If the problem arises then the slot is bad, if not,
the module that produced the problem is bad. To double check put the suspect
module in another slot.

If the problem arises no matter how many modules or which slots are used, time
to look at the power supply.

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375