9 replies
by syscokid
by allnet
by aschaffer
by mckaytech
There is a tool in the NT Server Resource Kit that can give you a head start in identifying the problem: dumpexam.exe
If you have the symbol table installed, dumpexam can tell you the address fault as well as the starting addresses of each of themodules loaded at the time of the dump. From that information, you can usually isolate the problem to a particular process, module or driver. Most often, it's a driver.
But also make careful note of the error message and see if it's exactly thesame each time. If not, it's more likely a random hardware failure of some type. In any event, you'll get better advice if you can post the stop codes you see.
paul
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending