Question

Locked

I Got BSOD! can someone help me?

By enzoferari_90 ·
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale I 1033

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000010
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFFA6000C49C5E
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini031209-03.dmp
C:\Users\Dashield\AppData\Local\Temp\WER-49687-0.sysdata.xml
C:\Users\Dashield\AppData\Local\Temp\WEREFAF.tmp.version.txt

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409


OS: VIsta Ultimate sp1
Board: XFXg31i
PR: dual-core e5200
RAM: team elite 2x2gb 800
GPU: ATI 3870 radeon
FAN: 7 freezer pro

All new, almost 2weeks

This conversation is currently closed to new comments.

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

All Answers

Collapse -

Any recent changes to hardware/software?

by robo_dev In reply to I Got BSOD! can someone h ...

What OS is this?
What PC hardware?

BSODs can occur for many reasons, either hardware or software.

Collapse -

Lots of reasons

by Jay217 In reply to Any recent changes to har ...

Take a look here for more info if its a winxp station..

http://www.aumha.org/a/stop.php

Collapse -

Use windbg.exe

by Jacky Howe In reply to I Got BSOD! can someone h ...

Minidump Files can be found here. C:\WINDOWS\Minidump\Mini122707-02.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_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

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

Related Discussions

Related Forums