TechRepublic|Forums|Networks

Networks

Question

  • Creator
    Topic
  • November 5, 2008 at 9:43 am #2160942

    Windows server 2003 Blue screen error

    Locked

    by senthilstays · about 14 years, 7 months ago

    Hi all,
    How to troubleshoot Blue screen dump error in windows server 2003 .

    Topic is locked This conversation is currently closed to new comments.
  • Creator
    Topic

All Answers

  • Author
    Replies
    • November 5, 2008 at 9:43 am #2794775

      Clarifications

      by senthilstays · about 14 years, 7 months ago

      In reply to Windows server 2003 Blue screen error

      Clarifications

    • November 5, 2008 at 11:10 am #2794740

      ????

      by larryd4 · about 14 years, 7 months ago

      In reply to Windows server 2003 Blue screen error

      Umm whats the error?

    • November 5, 2008 at 3:34 pm #2794628

      WinDbg

      by rob miners · about 14 years, 7 months ago

      In reply to Windows server 2003 Blue screen error

      Minidump Files can be found here. C:\WINDOWS\Minidump\Mini******-**.dmp

      How to read the small memory dump files that Windows creates for debugging

      http://support.microsoft.com/kb/315263

      To download and install the Windows debugging tools, visit the following Microsoft Web site:

      http://www.microsoft.com/whdc/devtools/debugging/default.mspx

      Instructions on using Windbg.

      Open Windbg and select file, Symbol file path and brows to the Symbol folder that you have downloaded and installed Symbols to, select OK.

      Close the workpage and save the Workspace information. This should lock in the Symbol path.

      Open Windbg and select file and select Open Crash Dump then navigate to the minidump, highlight it and select Open.

      There are two ways to use !analyze -v the easiest is to click on !analyze -v under Bugcheck Analysis.

      When you have ran the initial dump if you look to the bottom of the screen you will see kd> to the right of that type in !analyze -v and press the Enter key.

      Ctrl + a will let you copy the information and paste it into notepad.

      Look to the bottom of the page for information like this. This was fixed by updating the Graphics Drivers.

      FAULTING_THREAD: 864f6a98

      DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

      CUSTOMER_CRASH_COUNT: 1

      BUGCHECK_STR: 0xEA

      PROCESS_NAME: logon.scr

      LAST_CONTROL_TRANSFER: from 00000000 to bfef0fea

      STACK_TEXT: f6434e6c 00000000 00000000 00000000 00000000 sgiul50!DrvBitBlt+0x585

      STACK_COMMAND: .thread 0xffffffff864f6a98 ; kb

      FOLLOWUP_IP: sgiul50!DrvBitBlt+585 bfef0fea 75f9 jne sgiul50!DrvBitBlt+0x580 (bfef0fe5)

      SYMBOL_STACK_INDEX: 0

      SYMBOL_NAME: sgiul50!DrvBitBlt+585

      FOLLOWUP_NAME: MachineOwner

      MODULE_NAME: sgiul50

      IMAGE_NAME: sgiul50.dll

      DEBUG_FLR_IMAGE_TIMESTAMP: 3b7dfec7

      FAILURE_BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

      BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

      Keep us informed as to your progress if you require further assistance.

      If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as Helpful so that others may benefit from the outcome. 😉 😀

  • Author
    Replies
Viewing 2 reply threads