Question

Locked

Can anyone decode a minidump for me?

By Alski ·
I have tried to install the secret decoder ring with all the command line stuff. Symbols are always a problem. Can I just email this to someone (it's only 100k) and see what is going on with this PC? I appreciate it.

You will have good luck for the next 7 days and possibly win the lottery (you have to buy a ticket) if you do this.

Al

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

What

by Jacky Howe In reply to Can anyone decode a minid ...

Operating System are you running. Include it when you PM me. I will have a look for you. I could do with some good luck even if for only seven days.

Collapse -

I'm game for some luck ...

by OldER Mycroft In reply to Can anyone decode a minid ...

Chuck it my way in a Peermail and I'll apply some Scottish brew to it!

Collapse -

If you want to try it yourself

by Jacky Howe In reply to Can anyone decode a minid ...

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_THREA 864f6a98

DEFAULT_BUCKET_I 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_COMMAN .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_I 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

BUCKET_I 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

Collapse -

Nifty little tidbit that...

by boxfiddler Moderator In reply to If you want to try it you ...

thanks for posting it.

Collapse -

No Probs :)

by Jacky Howe In reply to Nifty little tidbit that. ...

WinDbg is a lot easier to use than the old way. But it still has some traps for the unwary. If you dont save the workspace you have to reload the Symbols Folder.

Back to Software Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums