Tuesday, February 21, 2006
Windows STOP Error
Yesterday my network file server took a dive for no apparent reason. This is the second time in a week that it's done this.
In researching the problem I came across this blog post detailing a way to trouble-shoot the issue and determine which driver had the problem. Using this I was able to isolate the driver that caused the BSOD and removed the program (as it was no longer needed). I'll reboot my file server tonight to finish the un-installation and hopefully that'll take care of this issue.
To trouble-shoot this error, I had to download the 32-bit Microsoft Debugging Tools, then configure it to use the Internet Microsoft Symbol Server rather then download the huge 120+ MB file.
After installing the Debug tools on the server, verifying the configuration of the Symbols, I then did a CTRL+D and selected the MEMORY.DMP file from yesterday. Finally at the command line I typed "!analyze -v" to analyze the file. The driver in suspect was "hotcore.sys" used by Paragon Hard Disk Manager 6.0 that we had installed on the server, but had discontinued using.
Hopefully that'll take care of the problem.
Subscribe to:
Post Comments (Atom)
1 comment:
And now it's all rebooted and fixed =]
Post a Comment