6 replies
by obmuloc Accepted solution
by older mycroft Accepted solution
Now - given the predication of the standard M$ Error Message - it usually comes with a series of numbers attached.
They're not just there for SHOW!!!! ;)
by wanttocancel Accepted solution
You could have a bad/corrupt driver of sorts. If you updated any driver recently that could be the culprit. You should boot into Safe Mode (by pressing F8 before the Windows Logo screen) and remove the driver there.
This could also mean bad or mismatched RAM. You can try to remove one stick of RAM and see if the computer will boot without the BSOD. If it does then you probably have bad RAM. You can also rum Memtest to check the health of your RAM. This includes video cards so if you have an add-on video card you might want to try and remove it to see if the computer can boot.
If you can take down the error (it will look like this 0000000x0 where the zeros might be another number and/or letter) that will help us narrow your problem down.
by rob miners Accepted solution
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.
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. ;) :D
by obmuloc Accepted solution
Thanks guys for the swift responses to my first post and my apologies for not giving you more info in the first instance. I hope this rectifies things, I hope the following info makes my situation a little clearer.
I am unable to boot into XP when using any of the options available under the F8 key, I geet the same result on every attempt and that is as follows:
IRQL_NOT_LESS_OR_EQUAL
STOP:0x0000000A (0x00001008,0x000000002,
0x00000000,0x0804EB5CF) Occasionally, the first one following STOP reads 0x00000008.
I do not know if any hardware or drivers have been installed in the recent past, the PC has just come into my possession and the previous owner does not know either. The memory however passes all diagnostics tests with flying colours so does not appear to be the problem.
I hope the above will be of assistance to you in helping to resolve my BSOD problem.
Thanks in advance
rumpy
by rob miners Accepted solution
You can use the Hard Drive Makers Testing Utility to Test the Drive
Hitachi / IBM - DFT "Drive Fitness Test"
http://www.hgst.com/hdd/support/download.htm
Works with all manufacturers
Western Digital "Data Lifeguard"
http://support.wdc.com/download/index.asp#dlgtools
Works with WD drives only
Fujitsu "FJDT"
http://www.fel.fujitsu.com/home/drivers.asp?L=en&CID=1
Works with fujitsu models only
Samsung "hutil"
http://www.samsung.com/Products/Hard...ties/hutil.htm
Compatability unknown...
Seagate "Seatools"
http://www.seagate.com/support/seatools
Works with Seagate drives only
Insert your XP CD and when you see ?Press any key to boot from CD? press a key. Now wait for the XP installer to finish loading up and you will be presented with the option to press R to Repair.
Press R.
The next screen will ask you which Windows installation you would like to log on to. Normally the following will be listed:
1: C:\WINDOWS
Press 1, then Enter to continue.
You may now be asked for the Administrator password. If you know this type it and press Enter. If you don't know the Administrators password it may be blank. Just press Enter or type your username and password.
At the command prompt type:
chkdsk /r
Let it run through the 5 stages.
Darik's Boot and Nuke can be used to completly erase the drive.
Autonuke should do it by running it at least 3 times.
Recreate your Partitions. Then install the Operating System.
Keep us informed as to your progress if you require further assistance. ;) :D
This discussion is closed to new replies.
Trending Hardware posts
Sort by Trending