Sick of the crashes, please help!

[mikejd1]

This is it, ive had it. My XP machine continues to keep rebooting itself and blue screen after blue screen.. I could be briwsing the internet, or playing music, or just sitting here looking at the screen, and from time to time, all the time, the dang thing reboots itself, or i get a blue screen.

I read soemwhere there was a utility that helps you determine what the cause f the crash is. Now windows "thinks" its a device driver but cannot point out which one is causing the issue. Does anyone here know of a utility that will do this? id really appreciate it.

Thanks neowin

Mike

[John Veteran]

what video card drivers do you have installed? they are often to blame.

[mikejd1]

Cat. 3.9 any suggestions?

Edited November 21, 2003 by lebmike

[mikejd1]

anyone?

[davemania]

Sounds like a memory problem but first have you tried reinstalling WinXP ?

--

Are you overclocking your CPU ?

[+BudMan MVC]

few things to check - your memory, and I would sugget you look at your powersupply voltages - are they solid, or is there some fluctuation. Large enough fluctuations in the voltages could cause weird problems.

[Antichrist]

1 - Did you install any hardware lately?

2 - Is it a old motherboard?

3 - Does it heat to much?

4 - Overclocked anything? (CPU, Ram, Vid Card?)

5 - Did you tweaked windows in ANY ways to make it faster or more "stable"?

6 - Is your anti-viruses Norton and not updated?

To point out the problem, I would remove all hardware except the vid card, ram and hd (Yes unplug the cd-rom if it's a burner of any kind)... If it's not happening, then it's one of your other periphical that cause the problem.

Also try to updated your windows via the windows update and all your drivers from the manufacturer website.

GL and pm me if that didn't help you!

[rabidmunkee]

Is it a old motherboard?

if it is an old motherboard check the capacitors.

a few years back there were dodgy caps going around.

[mikejd1]

all these replys ive done,w ith the execption of removing all hardware except the vid card. i guess i oculd try that. What do i need to do, use the machine for a day or so, if i dont get a crash, plug each one in one by one?

[SimplyPotatoes]

!WURD! you can try to disable auto-reboot on critical erro in startup and recovery options

[mahiles]

I don't know if you're having the same problem that I've just had so this might help but then again it might not. I used to get what you describe quite a lot and it turned out to be them Cat 3.9 drivers so I downgraded the drivers to the ones that were shipped on the CD and now everything works fine. Hope this helps..

[mikejd1]

i get errors like

atapi.sys

win32k.sys

usb2.sys

IRQL_Not_Equal

etc...

and some blue screens dont even tell what caused the error

Also, I dont think its the ATI drivers this time, because i didnt even install them and the system started doing this, and it was right after ia nice clean reinstall.

[YaZoR]

do a memory test, i cant remember which prog i used to do it. it was a dos bootable disk with its own memcheck on it.

or

try a different stick of memory in, see how long it lasts.

[mikejd1]

do a memory test, i cant remember which prog i used to do it. it was a dos bootable disk with its own memcheck on it.

or

try a different stick of memory in, see how long it lasts.

what will the memory test produce?? in my first post, i stated that i saw software out there that finds what caused the crash in the system, does anyone know of this program?

[SimplyPotatoes]

DID YOU TRY DISABLE AUTO REBOOT ON CRITICAL ERROR?

[mikejd1]

DID YOU TRY DISABLE AUTO REBOOT ON CRITICAL ERROR?

yes, and when i do that, all i get are the blue screens. how does this help?

[eds]

Is there anything on your event log? Sometimes that might give a clue on whats going on. If its been going on for a long time, I would think you may have a faulty mem module. If its happening recently, its probably best to work backwards and remove software and hardware that youve recently installed. Test by doing what you normally do to get a crash/reboot.

[davemania]

do a memory test, i cant remember which prog i used to do it. it was a dos bootable disk with its own memcheck on it.

or

try a different stick of memory in, see how long it lasts.

what will the memory test produce?? in my first post, i stated that i saw software out there that finds what caused the crash in the system, does anyone know of this program?

A faulty memory stick generally produces the error you are describing, random reboots etc.

I did a quick google search and this is what i found, don't know if its right

http://home.earthlink.net/~alegr/download/memtest.htm

[Spyder Veteran]

next time you get a blue screen, write down the STOP error .. the filename doesn't help, but the actual error code will let us look up whats causing the problem.

[John Veteran]

windows memory diagnostic - use this to make a bootable floppy you can use to run a memory test. let it run for a while and see if it has any crashes.

http://oca.microsoft.com/en/windiag.asp

[Frank]

next time you get a blue screen, write down the STOP error .. the filename doesn't help, but the actual error code will let us look up whats causing the problem.

The stop error will look like 00x00000050. Like spyder said, this will help us find the problem.

[mikejd1]

The stop error will look like 00x00000050. Like spyder said, this will help us find the problem.

just got home, had myself a nice blue screen waitin for me. this time the error was...

"Driver_IRQL_Not_Less_Or_Equal"

Stop: 0x000000D1

Can someone help me now?????

Mike

[antally]

Does it blame a driver? if so there should be a file name about 3/4 down the screen, if there is then that is the driver to blame.

-A

[Frank]

Is this a XP, or a 2K machine?

/Edit: NM, re-read your first post

[mikejd1]

No, no file name this time. Sometimes i Get file names.

This is an XP pro Slipstreamed with SP1.