Question

Locked

Reboots unexpectedly

By notorious_doom ·
Hi, this is my System Configuration.

Hardware:-
Motherboard - DG33FB Intel? G33 LGA775 ATX
RAM - Transcend Single Slot 1 GB RAM 667Mhz
Processor - E 2.33 GHz Core 2 Duo
Display Adapter - Gigabyte GV-N94TOC-1GH
SATA2 - 2 250GB Segate HDD 7200RMP
400Watt Standard SMPS(I forgot the brand)

Running Softwares at the moment:-
Norton 360
U Torrent


My computer reboots unexpectedly several times a day.

This conversation is currently closed to new comments.

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

All Answers

Collapse -

Try this

by Jacky Howe In reply to Reboots unexpectedly

First thing to do is Update all of your Motherboard Device Drivers and see how it performs.

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.

Restart the PC normally as this will allow the PC to Blue Screen. Take note of Stop 0X000000 error message and Google it or post it here along with the latest minidump.

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 Software Forum
2 total posts (Page 1 of 1)  

Related Discussions

Related Forums