Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

XP ***STOP 0x0000000A ERROR!


  • Please log in to reply

#1
Jackpumpkinhead

Jackpumpkinhead

    Member

  • Member
  • PipPip
  • 29 posts
Okay so here is my problem
Last night i was surfing the web
and doing some normal computer stuff
i recently installed a program that uses java and
had just finished downloading a file when i got a warning message from avast
telling me that i something was trying to access my computer
so i told it to not allow it to access
and everything was fine...for a while
then suddenly i saw a BSOD for a brief second or two and then my computer restarted
when it tried to reboot it got all the way to the windows startup screen and i saw the same thing
a brief second of the BSOD and then restart

so i tried starting in safe mode
my computer started loading all of the SYS files and then reset again

i am completely unable to boot into widows
i have tried some of the other options ie, restart with networking, last known settings that work ect.
all with the same result

i then selected the option to not reset on system failure so that i could see what the BSOD said
and it had a 0x0000000A stop error

similar to this one
Posted Image

only under technical information my error is this

***STOP 0x0000000A (0x00000000, 0x00000001, 0x00000002,[?])

The [?] is there because i dont remember what the numbers/letters are that are in that part
i will check it again later tonight and let you know what it says exactly

about a year or so ago i had a buddy of mine image the hard drive on this computer and put it on a new hard drive with more space
it is this new hard drive with more space that is giving me the Stop Error
so i reinstalled the old drive just so that i could get my computer up and running
and i had somthing to work off of

is it possible to make the BSOD drive a slave and then try to fix the problem on that drive
by using the old drive as the master?

i would love to get the newer drive back up an running because it has all of my programs and some important files on it
and it is a bigger and newer drive so i would rather use it

i called my father-in-law (he is an IT guy) and he suggested using the install disc for XP and repairing the OS
but i would like to try some other options first cause i built this computer from the ground and i think we used one of his XP installation discs
but i am not 100% sure
he told me that if you use the wrong installation disc then you can actually cause more harm than good

so i thought i would come here for some suggestions

thanx
get back to me as soon as you can
please!!!
:)

Edited by Jackpumpkinhead, 05 November 2009 - 10:11 AM.

  • 0

Advertisements


#2
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
We will have to create a small 'fix CD' to solve this problem.
Please download RC.ISO and save it somewhere you can find it.
Also download MagicISO and install it.

Start MagicISO. You should see a window informing you about the full version of MagicISO.
In the bottom right select Try It! and the program will open.
Click on File and then on Open and navigate to the RC.ISO file you downloaded. Select it, and click Open.

First, we'll need to add a clean version of userinit.exe to the current RC.ISO
  • In the upper right pane, double click on the i386 folder.
  • Right click in the upper right pane and select Add Files...
  • Navigate to C:\Windows\System32 and select userinit.exe
  • Then click Open to add userinit.exe to the CD image.
  • Click File and select Save As...
  • Name the file RCplus and save it somewhere you can find it.
Next, we'll need to burn the newly created image to a disk that we can use to fix the problem.
  • Put a blank CD-R disk in your CD burner and close the tray. If an AutoPlay window opens, close it.
  • Click on Tools and select Burn CD/DVD with ISO.... A window will appear.
  • Click on the little folder to the right of CD/DVD Image File then navigate to the newly created RCplus.iso Image file and click Open.
  • In the CD/DVD Writing Speed drop-down menu choose the 8X setting.
  • Under Format make sure that Mode 1 is selected.
  • And finally, click on the Burn it! button to burn RCplus.iso to disk.
Once the disk is burned, put it in the machine you want to fix and restart it.
Boot to the CD just as you would with a Windows XP disk.
At the Welcome to Setup screen, press R to enter the Recovery Console.
Choose the installation to be repaired by number (usually 1) and press Enter.
When you are asked for the Administrator password, enter the password or leave it blank (default) and press Enter.

At the C:\Windows> prompt, type the following commands pressing Enter after each one. Note: Watch the spaces.D:
cd i386
copy userinit.exe c:\windows\system32
exit
After putting in the third command, you should receive the message 1 file copied which will indicate that the operation succeeded.
Now take out the CD and reboot your computer to normal mode. Try to log in and it should let you back in.
  • 0

#3
Jackpumpkinhead

Jackpumpkinhead

    Member

  • Topic Starter
  • Member
  • PipPip
  • 29 posts
just so that i know what it is that i am doing
can you explain what this does?
  • 0

#4
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
It MAY get your computer out of the loop.
  • 0

#5
Jackpumpkinhead

Jackpumpkinhead

    Member

  • Topic Starter
  • Member
  • PipPip
  • 29 posts
sorry to be annoying
and also, not to "bite the hand that feeds me"
but isn't some of this unnecessary
i mean couldn't i just make the BSOD Drive a slave drive
then just copy and paste userinit.exe from the master into the BSOD drive?
or is it extremely necessary to use Recovery Console?

just trying to save myself some time
  • 0

#6
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
You certainly can do it your way, if it's easier for you.
  • 0

#7
Jackpumpkinhead

Jackpumpkinhead

    Member

  • Topic Starter
  • Member
  • PipPip
  • 29 posts
great thanx
i'll let you know what happens
  • 0

#8
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
:)
  • 0

#9
Jackpumpkinhead

Jackpumpkinhead

    Member

  • Topic Starter
  • Member
  • PipPip
  • 29 posts
well i tried it
and it didn't work
:)
this is the specific Stop error that i get:

***STOP: 0x0000000A (0x00000000, 0x00000001, 0x00000002, 0x804F9D36)

nothing after that
it is a IRQL_NOT_LESS_OR_EQUAL
  • 0

#10
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
If you have Windows CD...(if you don't have Windows CD, scroll down)

1. Insert your Windows XP CD into your CD and assure that your CD-ROM drive is capable of booting the CD.
2. Once you have booted from CD, do NOT select the option that states: Press F2 to initiate the Automated System Recovery (ASR) tool.
You’re going to proceed until you see the following screen, at which point you will press the “R” key to enter the recovery console:

Posted Image

3. After you have selected the appropriate option from step two, you will be prompted to select a valid Windows installation (typically number “1″).
Select the installation number, and hit Enter.
If there is an administrator password for the administrator account, enter it and hit Enter (if asked for the password, and you don't know it, you're out of luck).
You will be greeted with this screen, which indicates a recovery console at the ready:

Posted Image

4. There are eight commands you must enter in sequence to repair your problem..
NOTE. Make sure, you press Enter after each command. Make sure, all commands are exact, including "spaces".
These commands are as follows:

CD..
ATTRIB -H C:\boot.ini
ATTRIB -S C:\boot.ini
ATTRIB -R C:\boot.ini
del boot.ini
BOOTCFG /Rebuild


Note about the above command.
BOOTCFG /REBUILD command which searches for pre-existing installations of Windows XP and rebuilds sundry essential components of the Windows operating system, recompiles the BOOT.INI file and corrects a litany of common Windows errors.
It is very important that you do one or both of the following two things:
A.) Every Windows XP owner must use /FASTDETECT as OS Load Option when the rebuild process is finalizing.
B.) If you are the owner of a CPU featuring Intel’s XD or AMD’s NX buffer overflow protection, you must also use /NOEXECUTE=OPTIN as an OS Load Option.
For the Enter Load Identifier portion of this command, you should enter the name of the operating system you have installed.
If, for example, you are using Windows XP Home, you could type Microsoft Windows XP Home Edition for the identifier (it's not crucial, however what the name is, as long, as it's meaningful).
Here is your computer screen:

Posted Image

5. Following command verifies the integrity of the hard drive containing the Windows XP installation. While this step is not an essential function in our process, it’s still good to be sure that the drive is physically capable of running windows, in that it contains no bad sectors or other corruptions that might be the culprit:

CHKDSK /R

6. This last command writes a new boot sector to the hard drive and cleans up all the loose ends we created by rebuilding the BOOT.INI file and the system files. When the Windows Recovery Console asks you if you are Sure you want to write a new bootsector to the partition C: ? just hit “Y”, then Enter to confirm your decision:

FIXBOOT

7. It’s time to reboot your PC by typing
EXIT
and pressing Enter.

With any luck, your PC will boot successfully into Windows XP as if your various DLL, Hive, EXE and NTLDR errors never existed.



If you don't have Windows CD...
Download Windows Recovery Console: http://www.thecomput...om/files/rc.iso
Download, and install free Imgburn: http://www.imgburn.c...hp?act=download
Using Imgburn, burn rc.iso to a CD.
Boot to the CD...let it finish loading.
When the "Welcome to Setup" screen appears, press R to start the Recovery Console.
Then, follow instructions from Step #3 above.
  • 0

#11
Jackpumpkinhead

Jackpumpkinhead

    Member

  • Topic Starter
  • Member
  • PipPip
  • 29 posts
great!
i will try this out as soon as i get a chance
unfortunately i leave for vacation tomorrow and i probably wont get to until next monday
but i will let you know then!! :)

Edited by Jackpumpkinhead, 06 November 2009 - 11:13 PM.

  • 0

#12
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
We'll be here :)
  • 0

#13
Jackpumpkinhead

Jackpumpkinhead

    Member

  • Topic Starter
  • Member
  • PipPip
  • 29 posts

B.) If you are the owner of a CPU featuring Intel’s XD or AMD’s NX buffer overflow protection, you must also use /NOEXECUTE=OPTIN as an OS Load Option.


i have an AMD Athlon 64 Processor, and i am unsure if it has this NX buffer overflow protection.
how would i find out if i do.
  • 0

#14
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Most todays processor have that feature, so we can say, yes.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP