Question

Locked

Window XP SP-2 Login problem

By tech_dalone ·
I am facing problem with my PC, my pc work well with earlier version of XP. but it creates problem if I use Win XP Service Pack-2, It reboots continously before logging my system configuration is Prossesor - Intel Pentium 4 2.00 G hz
Main board:- KOBAIN
Model ::- PI845GLM 5.0
Chipset Intel i845GL Rev. B1
Southbridge:- Intel 82801DB (ICH4)
Sensor :- Winbond W83627HF

BIOS :- Americal Megatrends Inc.
Version 07.00T
Date :- 04/02/01

Memory:- DDR-SDRAM PC3200-256 MB
Frequency :- 133.3 MHz
FSB:DRAM 3:4
CAS # Latency 2.0 clocks
Please help me to sort out these problem

This conversation is currently closed to new comments.

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

All Answers

Collapse -

A couple of ways to do this

by Jacky Howe In reply to Window XP SP-2 Login prob ...

Boot into Safe Mode by continually pressing the function key F8.

My Computer, Properties, Advanced, Startup and Recovery and untick Automatically restart. While you are there make sure that Small memory dump (64 KB) is selected and the output is %SystemRoot%\Minidump. The Blue Screen will dump the Minidump file.

This will Blue Screen the PC. Take note of Stop 0X000000 error message and post it.

Or if you are feeling adventurous

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 Windows Forum
1 total post (Page 1 of 1)  

Related Discussions

Related Forums