Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Technical Instruction Sure Solution 1007054.1 : How to handle Microsoft Windows panics on x64 platforms
PreviouslyPublishedAs 209735 Description How to handle Microsoft Windows panics on x64 platforms Summary This document is about Windows panics/crashes applicable to Windows versions 2k,2k3,XP, NT - it contains the key concepts needed to handle system panics. NOTE: Core dump analysis is out of scope of this document. For a detailed checklist on how to identify and manage Windows
crashes, To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - Sun x86 Systems Symptoms Windows panics, windows crashes, blue screen of death
Steps to Follow Windows crashes, core dumps, and configuration OverviewWhy does Windows crash? Windows is capable of running on several x86 platforms. This HW capability requires protection mechanisms built into the OS that lets multiple programs run simultaneously without corrupting each other data or resources. For this reason, a process should work only on its own
resources. The most important are kernel and user mode levels. All the other common applications run in user mode. Problems can happen when a kernel mode process, due to bugs in the code, interferes with the resources of a process running in the lower user mode, or in another process running in kernel mode. Other causes may be:
This kind of crash is recognizable via bugcheck 0xe2:MANUALLY_INITIATED_CRASH) According to Microsoft more than 70% of panics are caused by third-party drivers. When corruption happens (and is detected) the OS initiates a protection procedure to stop the entire system and avoid additional corruption. This procedure is necessary to save data about the fault (crash dump) for further analysis as well. What happens when Windows crashes? When a crash condition is detected, the KeBugChechEx function is
invoked.
KeBugCheckEx takes care of stopping the CPUs, paints the famous Blue Screen of Death (BsoD) and dumps (if this can be done safely) system kernel/memory status into a dump file. Examples of BSoD in Windows NT can be found at the link
below: How many kinds of dump files are there ? Windows Server 2003, 2000 and XP can create three types of dumps:
A full dump contains all possible data and executables the memory
has. This is equal to the amount of RAM in the box. IMPORTANT: Usually, a smaller kernel dump is enough.
This is equal to the amount of RAM occupied by the operating
system's kernel. Dimensions of this file may vary.
A mini dump is a 64Kb file for 32bit and 128Kb for 64bit systems.
It doesn't contain any of the binary or As already said, the full dump is overwritten every time. How to check and configure the dump type and location.Default settings can be changed via: Control Panel --> (Performance and maintenance)
-->System-->Advanced--> Startup and recovery A complete and detailed description of dump files kinds and options can be found in the following documents:
Can system crash without dumping to a file?Sometimes the dump can fail even if the setting is correct.
For a detailed description and possible solutions / workaround, check the articles below
How to collect useful configuration information about your systemIn Windows there are a couple of useful tool designed to collect system configuration data like OS version, drivers, events, etc. Msinfo32 (bundled in Windows) and Microsoft Product Support's reporting tools that need to be downloaded from Microsoft website. msinfo32: You can start it manually: [Start]->[Run]->msinfo32 MPS report (Microsoft Product Support's Reporting Tools): It is a compressed software package that contains one or more
scripts and other utilities that you can use Go to http://support.microsoft.com/kb/818742 for a detailed description and download links. Also check the following documents: <Document: 1010936.1> "Microsoft Windows and Linux operating systems: How to obtain troubleshooting information" How to collect platform specific hardware logs - Ipmitool, Sel logs, DMI logs, tdulogs.If you suspect an hardware problem you need to collect platform
specific data as well. https://support.oracle.com/handbook_private/index.html The following documents may be useful: <Document: 1008335.1> "Sun [TM] X64/X86 Guide to System Troubleshooting" <Document: 1009698.1> "How to collect data from a x86/x64 platform using Intelligent Platform Management Interface (IPMI)" Core dump analysisAs specified at the beginning, Windows crash dump analysis is out
scope of this document. References
Internal Comments This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the "Document Feedback" alias(es) listed below: Normalization team alias: [email protected] normalized, microsoft, windows, panic, crash, dump, minidump, x86, x64, windbg, BSoD Previously Published As 91520 20100906: Removed broken link http://support.microsoft.com/kb/274598/ Attachments This solution has no attachment |
||||||||||||
|