how to troubleshoot BSOD?

mavec · Nov 29, 2003, 05:12 AM

ello..
ppl propably ask this all the time but.......
so I'm having this problem with WinXP as it throws its BSOD at me about once a day. quite annoying if you ask me. even when the computer is idle it might do it.
so I'm wondering if there's a way to know what driver/hardware is causing the error. I've tried a lot of different displaydrivers atleast and it's the same with all of them so it must be something else.
I've checked the driver/.ddl-file that it displays when BSODing but it's different almost every time.
like "page_fault_in_non_paged_area" or "irql_not_less_or_equal" .. usually one of those..
lite this..
guess I have to buy a whole new hardware system if I won't get this fixed..

so..

thanks.

- mav

PangingJr · Nov 29, 2003, 05:40 AM

pls check this ..http://aumha.org/win5/kbestop.htm

mavec · Nov 29, 2003, 10:48 AM

thanks, I'll check it out

Chaos · Nov 29, 2003, 11:01 AM

Quote:

Originally posted by panging
pls check this ..http://aumha.org/win5/kbestop.htm

I must admit that you seem to have fantastic trouble shooting skills dude

Your posts always contain something very useful

~~craig588~~ · Nov 29, 2003, 11:02 AM

Quote:

Bug Check 0x9: IRQL_NOT_GREATER_OR_EQUAL

The IRQL_NOT_GREATER_OR_EQUAL bug check has a value of 0x00000009.

This bug check appears very infrequently.

really? I get it alot, probably once every few months.

PangingJr · Nov 29, 2003, 11:36 AM

thanks Chaos.

Bane the ECF · Dec 1, 2003, 10:45 PM

My BSOD troubleshooting method: "format c: /u"

mavec · Dec 2, 2003, 12:48 AM

Quote:

Originally posted by Bane the ECF
My BSOD troubleshooting method: "format c: /u"

hehe

just that it sucks when not even that works completely.

but anyways, haven't had a BSOD yet after I switched off the video shadowing from the bios settings so it might have helped. but no saying hooraah yet though

Bane the ECF · Dec 2, 2003, 01:14 AM

Well, there's just so many things that can cause BSODs, the first instinct I have when I encounter a nagging one is just that - format and start over. It's also convenient that I have everything I absolutely can't afford to lose (PDA data, addressbooks, game and game save files, documents, erm...pictures and movies...yeah that's it

) on a completely seperate partition. Formatting and reinstalling Windows and my programs takes but a few hours. That usually fixes all my BSODs, since a lot of them are caused by a corrupted Windows.

When I encounter nagging BSODs during reinstallation or subsequent PC use, that's when I start pulling all the cables out of my system...literally. I've found that most of the time that it's not a simple Windows corruption issue, that it's usually a bad/loose IDE cable or something similar in nature. Finally, if that doesn't fix the problem I usually start suspecting either the RAM (possibly) or the hard drive (likely) failing. Then I go into one of my "OMG" paranoia frenzies and pull out the credit cards.

Bane

PoopyTheJ · Dec 2, 2003, 01:31 AM

Check the Power Supply Voltages, lot's of times Power supplies die the hard way, nagging BSOD's and other random crap that never really seems to tie in to anything. I've had a couple go bad on me and I've got to say they are the most annoying things in the world to troubleshoot. My guess is the PSU especially if a re-install doesn't fix it.

mavec · Dec 2, 2003, 05:08 AM

allright..
so if I still get BSOD:s after a while according to the similar pattern I have a few things to check after that.. before changing system completely..

first from what I've experienced if it's a problem with the RAM then I'd propably get a BSOD all the time, or of course it depends on how seriously damaged the RAM is, but usually I wouldn't even be able to complete the windows setup without getting a lot of errors.. so I will count that out for the moment as my system can work for a long time with no problem..
I could run a complete memchecking but I doubt I would find anything useful there..

then there is the thing with all the cables and sh*t that I can't be completely sure about.. I did change my case a little while ago - (only the case, PSU is the same) - and I had the problem before that also, so I think if the cables would've been loose or something I would've noticed it. but then again one can never be sure as one is always so eager to get the system up and running again

...
still there the PSU possibility still remains..
can it be checked with observing the standard voltages while making other operations? .. memory, pci, cpu etc.. ?
I'm using a few coolers which I've connected from 12V to 5V, can that corrupt the powersupply i any way?

I've had no problem with corrupted filesystems or files otherweis, and no viruses or nothing..

ahh.. a few nice lines there..

thanks!

PoopyTheJ · Dec 2, 2003, 11:19 AM

Grab Aida32 it'll give you a complete rundown of your voltages or grab something like motherboard monitor or if using a qualified Nforce2 mobo the nvidia system util. If you had the problem previously, and you've got a bunch of coolers connected the PSU just may not be up to it, what kind of PSU is in there?

mavec · Dec 2, 2003, 12:50 PM

Quote:

Originally posted by gaborn415
Grab Aida32 it'll give you a complete rundown of your voltages or grab something like motherboard monitor or if using a qualified Nforce2 mobo the nvidia system util. If you had the problem previously, and you've got a bunch of coolers connected the PSU just may not be up to it, what kind of PSU is in there?

I've got a Epox 8k3a+ motherboard so I will try one of those programs.
The PSU is a HEC 300W Ultraquiet thingy.. I might need a more powerful one actually.. though HEC PSU:s usually are quite good.. (HEC-300LR-PT(SR) it says on the retail box..
cpu Athlon XP 1700+.. GF4 TI4800SE..

mavec · Dec 2, 2003, 04:23 PM

Vcore is 1.78 .. +3.3V is 3.28-3.30 .. +5V is 5.002-5.029 .. +12V is 12.281-12.342 .. Vdimm is 2.592 .. .. .. no overclocking anywhere.. .. are these normal values? ..