Advanced Crash Dump Analysis The preceding section leverages the Driver Verifier to create crashes that the debugger's automated analysis engine can resolve. You might still encounter cases where you cannot get a system to produce easily analyzable crashes and, if so, you will need to execute manual analysis to try and determine what the problem is.Use the !process 0 0 debugger command to look at the processes running and make sure that you understand the purpose of each one. Try disabling or uninstalling unnecessary applications and services.Use the lm command with the kv option to list the loaded kernel-mode drivers. Make sure that you understand the purpose of any third-party drivers and that you have the most recent versions.Use the !vm command to see whether the sys... in winternalswith winternalsprecedingsectionleveragesdriververifiercrashesdebuggers
Logging program crashes and freezes using Inspector IIXII - Opera Knowledge Base Logging program crashes and freezes using Inspector IIXII Important note: Inspector IIXII version 3.0 and up can be used to create a report when a program freezes/hangs or uses too much CPU. Details can be found towards the end of this article. You can upgrade from previous versions by simply replacing your current inspectr.exe file. Inspector IIXII is a small assembler program written by Axel Siebert to log crash data which is more useful than the standard Windows crash reports, and can also be used to write the state of a running process into a log, making it possible to analyze why a program freezes/hangs or uses too much CPU. It can be used with any program, including Opera. Inspectorr IIXII logs can be useful to find out why a program crashes or fre... in Public bookmarkswith crashesfreezesiixiiinspectorloggingnoteprogramversion