![]() In that case, be sure to select the most recent one, which may be either a full or small (minidump) file:įigure 7: Step 5 of running Crash Analyzer on a computer that won’t boot.Ĭlicking next causes the symbol files to be downloaded from Microsoft, after which the debugging tools automatically analyze the memory dump file:įigure 8: Step 6 of running Crash Analyzer on a computer that won’t boot. Note that there may be more than one memory dump file on your system. The next screen lets you browse to select the memory dump file on your failed system:įigure 6: Step 4 of running Crash Analyzer on a computer that won’t boot. The next screen lets you download the symbol files needed to map memory addresses to names so you can better understand the results of the debugging process:įigure 5: Step 3 of running Crash Analyzer on a computer that won’t boot. The next screen lets you browse to select the Debugging Tools for Windows, which should be located in memory on X: drive in the path shown below:įigure 4: Step 2 of running Crash Analyzer on a computer that won’t boot. This launches the Crash Analyzer Wizard:įigure 3: Step 1 of running Crash Analyzer on a computer that won’t boot. To run the Crash Analyzer tool on the problem computer, click the link by that name on the above screen. We’ll begin by booting the failed system using the DaRT CD we created in Part 2 of this series, then proceed through the various dialogs until the MSDaRT Tools screen is displayed: The important thing is that my computer won’t boot, so before I attempt a repair using other DaRT tools, I should first run Crash Analyzer to try to find out why the system won’t boot. You can download NotMyFault from the Book Tools section of this page on TechNet. Instead, I installed and ran NotMyFault, a freely available Windows Sysinternals tool, to install a driver that crashes the system. To be honest, this isn’t a real-world situation. Running Crash Analyzer on the Crashed Computerīelow is an example of a blue screen from a Windows 7 computer that won’t boot:įigure 1: This computer won’t boot and displays a blue screen (stop screen). You’ll need access to the symbol files for the installed version of Windows, which can be downloaded from Microsoft if you have Internet connectivity on the network where your problem computer resides since DaRT automatically acquires an IP address from a DHCP server if there is one, or if needed you can manually configure an IP address using the TCP/IP Config tool on the MSDaRT Tools screen.įor the walkthrough below we’ll assume the Debugging Tools for Windows are already included on our DaRT CD and that DaRT has access to the Internet so the symbol files can be downloaded.You’ll need the Debugging Tools for Windows, which you can include on your DaRT CD as described in Part 2 of this series.That’s because there are two prerequisites for running Crash Analyzer: The second approach is useful if the computer you are analyzing doesn’t have access to the Debugging Tools for Windows or to the symbol files for the installed version of Windows. Then launch the standalone version of Crash Analyzer by clicking Start, All Programs, Microsoft Diagnostics and Recovery Toolset, ERD Commander Boot Media Wizard. Copy the memory dump file from the problem computer to the computer you installed DaRT 6.5 on (see Part 2 of this series).This is the approach used in the section below. Boot the problem computer using your bootable DaRT media and launch Crash Analyzer from the MSDaRT Tools screen.There are two different ways you can use Crash Analyzer to analyze a memory dump: And to configure memory dump settings on a Windows Server Core installation, see this TechNet article. Of course, if you’ve configured Windows to not save a memory dump file, then Crash Anaylzer won’t be of any use to you! To learn how to configure memory dump settings on Windows, see this KB article. This final article examines one more DaRT tool, the Crash Analyzer, which you can use to troubleshoot Windows-based computers that blue-screen when you try to boot them.Ĭrash Analyzer works by analyzing the memory dump file saved on your hard drive when your Windows-based computer fails to boot properly and blue screens (displays a stop message). In the previous articles of this series we’ve learned about Microsoft’s Diagnostic and Recovery Toolset (DaRT), how to install DaRT, how to create a bootable DaRT CD, and how you can use the DaRT tools on your DaRT CD to try to resolve issues preventing Windows-based computers from booting successfully. Diagnostic and Recovery Toolset (Part 4).Diagnostic and Recovery Toolset (Part 3).Diagnostic and Recovery Toolset (Part 2).Diagnostic and Recovery Toolset (Part 1).If you would like to read the other parts in this article series please go to ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |