debugging win2k stop errors

[cyberey66]

Does anyone know how I can go about dedugging stop errors in win2k. The errors are being caused by hardware, are the hex numbers listed the memory range? I want to find out what exact hardware is causeing this, is that possible? I'm new to debugging stop errors so I don't really know much about it. Next time I get a bsod I'll write it all down and post it if anyone wants to look at it.

[Jon]

Microsoft has a list of the STOP errors and what the most common ones mean in their knowledge base but that's not going to pinpoint the problem if you want to do the ACTUAL debugging. Then you will need to crack open the memory .dmp file it creates when you get one and debug all the code that's in there....all (however much RAM you have installed) of it.

No fun...

[Softwebdev]

don't even bother with debugging things...........in order for you to debug it, you have to have 2 things

1-software: forget the name of this FREE software
2-over 50mb data files: forget what it calls. What this data files do is load all the drivers and executive. file.. into the dump file........and run it.............and the software will let you know which one cause the problem........and sometimes you will see the list of drivers not LOADED for some reason..........

i haven't done it for a long time...........i forget about these things...........


WORTH IT? no.........seriously............i just delete dmp files doesn't matter what.

you can use 1 feature in w2k.................it calls DEBUG MODE..............by pressing F8 before w2k logo........try that............hope it will solve your problem

if you want to debug............USE DRWATSON in w2k.........i don't now how this thing work............try it out.........it is easier compared to above technique............

[cyberey66]

I tried debug mode, guess what, blue screened!!!! I'm useing my back-up version of 2k now, and it's working ok. I had a backup of 2k installed for emergencies and then i just thought to use that as my main. This version was an upgrade from nt4 maybe that has something to do with it being stable. I just did a fresh install of 2k yesterday and it was unstable, infact it won't boot now. Maybe I have to do a real fresh install, and format my harddrive. If this version stays good though I won't.