Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Troubleshooting Sure Solution 1017889.1 : Analyzing System panics on x64 platforms running Microsoft Windows
PreviouslyPublishedAs 229136
Applies to:Sun Fire X4200 ServerSun Fire X4440 Server Sun Fire X4500 Server Sun Fire X4540 Server Sun Fire X4600 M2 Server All Platforms PurposeThis document will advise on how to confirm and handle panics on x64 systems running the Microsoft Windows operating system. Symptoms: - System displayed a blue screen. Please validate that each troubleshooting step below is true for your environment.
Last Review DateOctober 8, 2009Instructions for the ReaderA Troubleshooting Guide is provided to assist
in debugging a specific issue. When possible, diagnostic tools are included in the document
to assist in troubleshooting.
Troubleshooting DetailsStep 1 - Confirm it is a panicIf system was not booted in debug mode, you can see the Blue Screen of Death followed by system reboot. If you merely see the Blue Screen of Death, you may have a system hang. Details on handling system hangs can be found in: Document: 1017776.1 "What to do on Microsoft Windows Hangs on any X64 Sun Microsystems systems". If dump was successful you will find minidumps or memory dumps in the pre_configured locations. Refer to the section on “How to check and configure the dump type and location?” in Document: 1007054.1 "How to handle Microsoft Windows Panics on x64 platforms" Have you seen a BSoD (blue screen of death) ? For example, see: http://www.microsoft.com/technet/archive/winntas/tips/techrep/bsod.mspx?mfr=true Did system reboot but you weren't present when it happened? (usually the BSoD is followed by a system reboot) Check your dump settings and look into the specified locations for
minidumps C:\windows\memory.dmp or C:\windows\minidump\minixxxxxx-xx.dmp. Refer to the section on “How to check and configure the dump type and location” in Document: 1007054.1 "How to handle Microsoft Windows Panics on x64 platforms" Step 2 - Perform a Data collection Take notes of what system was doing at the moment of the crash, date and time. Have there been any SW or HW recent change to the system configuration ? Collect minidumps or memory dumps created after the system crash and save them on a stable system. Collect useful information about your system configuration
by running msinfo32 and/or MPS report as described in Document: 1007054.1 "How to handle Microsoft Windows Panics on x64 platforms" Collect HW platform specific data using ipmitool or ILOM snapshots (preferred if available on your platform) Refer to the section on “How do I collect platform specific hardware logs?” in Document: 1007054.1 "How to handle Microsoft Windows Panics on x64 platforms" By Default, after a reboot, Windows usually prompts you to send information to Microsoft. This can be configured with Computer Properties->Advanced->Error Reporting. If your system prompts you such option... do it if you can. You
will be redirected to Windows Error Reporting website that helps
provide additional information about a crash. Step 3 - How to get a Core dump analysis. You need to contact your OS provider. Refer to the section on “Core dump analysis” in Document: 1007054.1 "How to handle Microsoft Windows Panics on x64 platforms" for some references and links. Step 4 - Raise a Service request. At this point, if you have validated that each troubleshooting step above is true for your environment, and the issue still exists, further troubleshooting is required. For additional support contact Sun Support. Internal Comments The following is strictly for the use of Sun employees:
This document contains normalized content and is managed by the the Domain Lead(s) of the x64, normalized, microsoft, windows, panic, crash, dump, minidump, x86, x64, windbg, BSoD Previously Published As 91515 Change History Date: 2007-12-31 User Name: 31620 Action: Approved Attachments This solution has no attachment |
||||||||||||
|