Debugging Minidump files
I have a laptop that blue screens randomly. I came across the following information:
Don't install dumpchk. windbg is the offical tool to format the minidumps.
http://msdn.microsoft.com/msdnmag/issues/05/07/Debugging/
Debugging Tools from Microsoft
1) Create folder c:\symbols
2) Download and install the http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
3) Locate your latest memory.dmp file- C:\WINDOWS\Minidump\Mini01
4) open a CMD prompt and cd\program files\debugging tools for windows\
5) type the following stuff:
Code:
c:\program files\debugging tools>kd -z C:\WINDOWS\Minidump\Mini01
kd> .logopen c:\debuglog.txt
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
kd> .reload;!analyze -v;r;!thread;lmnt;.logclos
You now have a debuglog.txt in c:\, open it in notepad and post to this thread.
My problem is that there is no c:\program files\debugging tools directory on this PC. What am I missing?
Thanks
Don't install dumpchk. windbg is the offical tool to format the minidumps.
http://msdn.microsoft.com/msdnmag/issues/05/07/Debugging/
Debugging Tools from Microsoft
1) Create folder c:\symbols
2) Download and install the http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
3) Locate your latest memory.dmp file- C:\WINDOWS\Minidump\Mini01
4) open a CMD prompt and cd\program files\debugging tools for windows\
5) type the following stuff:
Code:
c:\program files\debugging tools>kd -z C:\WINDOWS\Minidump\Mini01
kd> .logopen c:\debuglog.txt
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
kd> .reload;!analyze -v;r;!thread;lmnt;.logclos
You now have a debuglog.txt in c:\, open it in notepad and post to this thread.
My problem is that there is no c:\program files\debugging tools directory on this PC. What am I missing?
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Do you want to upload some of those minidump (.dmp)files here .
Did you follow step #2 in your post and install the debugging tools?
Then you may have changed the installation directory.
The easiest way to find the correct folder is by checking your Start menu > Programs folder for "Debugging Tools for Windows", right-click on any of the entries inside and select 'Properties': it will show you where the tools are installed.
Then replace the "c:\program files\debugging tools" in your "Code" above by the actual installation directory.
On a side note:
If you are not experienced in analyzing minidumps, this may not help you at all. It is a far better option to create a thread describing your problem here on E-E and attach your minidump files; this way, experts will analyze them.
Then you may have changed the installation directory.
The easiest way to find the correct folder is by checking your Start menu > Programs folder for "Debugging Tools for Windows", right-click on any of the entries inside and select 'Properties': it will show you where the tools are installed.
Then replace the "c:\program files\debugging tools" in your "Code" above by the actual installation directory.
On a side note:
If you are not experienced in analyzing minidumps, this may not help you at all. It is a far better option to create a thread describing your problem here on E-E and attach your minidump files; this way, experts will analyze them.
Alternatively, you could use the 'Blue Screen Viewer': http://www.nirsoft.net/utils/blue_screen_view.html
It is a breeze to set up. But still, you may not know what to do with the information.
It is a breeze to set up. But still, you may not know what to do with the information.
ASKER
A first glance at the files indicates that the problems are related to Hewlett Packard programs, like the Power Assistant or the Wireless Assistant.
If this is a HP computer, check out the HP support site for updated versions of the HP assistants, utilities and drivers.
If this is a HP computer, check out the HP support site for updated versions of the HP assistants, utilities and drivers.
Alternatively, you may consider disabling the HP assistants.
Windows itself has inbuilt features that take care of power options and wireless connectivity, normally, additional vendor tools are not required, although - sometimes - they may offer more options or comfort. But sometimes they also create instable systems.
Windows itself has inbuilt features that take care of power options and wireless connectivity, normally, additional vendor tools are not required, although - sometimes - they may offer more options or comfort. But sometimes they also create instable systems.
ASKER
I will try removing those. We don't need the power assistant, but we've had problems with the wireless adapter becoming disabled out of nowhere - but is not shown as disabled in devmgmt. The only way to turn it back on is with Wireless Assistant. I'll give this a shot though.
As has been suggested, there are many programs out there that will provide analysis of your dumps - I wrote a web page you can use as well - http://www.lwcomputing.com/minidumps/minidumpup.asp
ASKER
Leew:
Sweet site! That will be very useful looking forward.
Sweet site! That will be very useful looking forward.
That is why I suggested posting the minidump files in another thread: Now we have a mix in here of people still replying to the original question ("Debugging Minidump files") and those commenting on your actual BSOD problem.
You cannot fairly finalize a question that is dealing with two separate issues, which is why there is a rule on E-E to try and avoid such a situation.
You cannot fairly finalize a question that is dealing with two separate issues, which is why there is a rule on E-E to try and avoid such a situation.
ASKER
No more blue screens yet.
Leew, your site says a file belonging to Altiris Recovery Solution is the culprit.
Torimar, how did you come to the conclusion it was the agents?
Leew, your site says a file belonging to Altiris Recovery Solution is the culprit.
Torimar, how did you come to the conclusion it was the agents?
ASKER
Torimar, The Power Manager & Connection Manager I mean, sorry.
To be fair, it should be the LIKELY culprit.
It does appear that RSAFAL.sys has caused at least 3 of your crashes. I would (as should have been suggested after the analysis) look at getting an upgrade or even downgrade for that file/the program that uses that file. Temporarily, you could RENAME the file (RSAFAL.sys.bad) and see what breaks and if the crashing stops.
It does appear that RSAFAL.sys has caused at least 3 of your crashes. I would (as should have been suggested after the analysis) look at getting an upgrade or even downgrade for that file/the program that uses that file. Temporarily, you could RENAME the file (RSAFAL.sys.bad) and see what breaks and if the crashing stops.
ASKER
I'll give that a shot if it blue screens again. That's a great idea. I know that file belongs to our Altiris Recovery Solution. I can always reinstall the client software on this laptop. Unfortunately, this laptop belongs to a member of the outside sales force, so my time with it is limited.
LogMeIn, GoToAssist, and other options exist for remote management.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The blue screens have stopped with the removal of the HP agents.
Torimar - Did not see your post about using a separate thread, but now see why it was suggested. My apologies for that.
Torimar - Did not see your post about using a separate thread, but now see why it was suggested. My apologies for that.
http://support.microsoft.com/kb/315263