Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Windows XP Pro only boots in safemode


  • Please log in to reply

#1
brandynewsome

brandynewsome

    Member

  • Member
  • PipPip
  • 22 posts
Started my computere yesterday and it went to a screen that says something about possible software changes and gives me these options: safe mode, safe mode with networking, safe mode with command prompt, last known good configuration and start windows normally. I have tried the last known good configuration and nothing happened. I've tried to use a restore point, again nothing. I ran msconfig and disabled all the start up items and when I restarted my computer it started normally. So I went back to msconfig and click one of the start up items and restarted my computer. It went back to the safe mode option screen so I started up safe mode again went back to msconfig and disabled all start up items again. But it didn't work this time and I go the safe mode option screen again. I also went to msconfig and was going to disable the safemode on the boot.ini tab, but it was already deselected. I'm all out of ideas. Do you have any that I haven't tried?
  • 0

Advertisements


#2
edge2022

edge2022

    Member 2k

  • Member
  • PipPipPipPipPip
  • 2,117 posts
What happens when you try to boot into normal mode?
Is there a BSOD, or just a black screen?

Do you remember what happened before this problem stared to occur? Any new hardware or drivers installed?
  • 0

#3
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
What was that one msconfig item, you disabled/enabled?
  • 0

#4
brandynewsome

brandynewsome

    Member

  • Topic Starter
  • Member
  • PipPip
  • 22 posts

What happens when you try to boot into normal mode?
Is there a BSOD, or just a black screen?

Do you remember what happened before this problem stared to occur? Any new hardware or drivers installed?



I haven't installed anything new. And when it tries to boot into normal mode it reboots and goes to back to the option screen with safe mode.
  • 0

#5
brandynewsome

brandynewsome

    Member

  • Topic Starter
  • Member
  • PipPip
  • 22 posts

What was that one msconfig item, you disabled/enabled?



It was ctfmon. It's the first item on the list on the start up tab in msconfig, that's why it was the first one I tried to enable after I disabled all of them.
  • 0

#6
edge2022

edge2022

    Member 2k

  • Member
  • PipPipPipPipPip
  • 2,117 posts

And when it tries to boot into normal mode it reboots and goes to back to the option screen with safe mode.

Exactly when does it reboot? After the login screen, or after the boot screen?

Try the steps in this article: http://www.tweakxp.c...ticle36976.aspx
Once you disabled auto reboot, then boot into normal mode, and if a BSOD comes up, post the error code.
  • 0

#7
brandynewsome

brandynewsome

    Member

  • Topic Starter
  • Member
  • PipPip
  • 22 posts

And when it tries to boot into normal mode it reboots and goes to back to the option screen with safe mode.

Exactly when does it reboot? After the login screen, or after the boot screen?

Try the steps in this article: http://www.tweakxp.c...ticle36976.aspx
Once you disabled auto reboot, then boot into normal mode, and if a BSOD comes up, post the error code.



It reboots after the boot screen. I disabled the auto reboot and got a blue screen that said that windows had been shut down to protect my computer. Then it said DRIVER_IRQL_NOT_LESS_OR_EQUAL Then it said something about if this was the first time I saw this screen to try and restart normally. Then it had this STOP: 0X000000D1 (0XE1816000, 0X00000002. 0X00000000, 0XF25CB00)
  • 0

#8
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Do you have Windows XP CD?
  • 0

#9
brandynewsome

brandynewsome

    Member

  • Topic Starter
  • Member
  • PipPip
  • 22 posts
Unfortunately, I do not.
  • 0

#10
edge2022

edge2022

    Member 2k

  • Member
  • PipPipPipPipPip
  • 2,117 posts
Are you using a Mylex RAID Controller?
If so then: http://support.microsoft.com/kb/316208

Otherwise, try this hotfix: http://support.microsoft.com/kb/839876
  • 0

Advertisements


#11
edge2022

edge2022

    Member 2k

  • Member
  • PipPipPipPipPip
  • 2,117 posts
http://www.cakewalk....er/minidump.asp
Follow the instructions, and reproduce the BSOD.

Then in safe mode, go to the directory C:\Windows\Minidump
Make sure that hidden files are visible.
Zip up the recent minidumps (within a week) and attach the .zip archive to your next post.

Also:

How to enable minidumps
Some may choose to disable the creation of minidumps (to save space perhaps?), but they are very important when troubleshooting a problem. To enable the minidumps:

Press Win+Pause to start the System Properties dialog;
Go to Advanced\Startup and recovery;
Ensure that Write debugging information is set to Small memory dump (64 kb).


Edited by edge2022, 24 May 2009 - 01:35 PM.

  • 0

#12
brandynewsome

brandynewsome

    Member

  • Topic Starter
  • Member
  • PipPip
  • 22 posts

http://www.cakewalk....er/minidump.asp
Follow the instructions, and reproduce the BSOD.

Then in safe mode, go to the directory C:\Windows\Minidump
Make sure that hidden files are visible.
Zip up the recent minidumps (within a week) and attach the .zip archive to your next post.

Also:

How to enable minidumps
Some may choose to disable the creation of minidumps (to save space perhaps?), but they are very important when troubleshooting a problem. To enable the minidumps:

Press Win+Pause to start the System Properties dialog;
Go to Advanced\Startup and recovery;
Ensure that Write debugging information is set to Small memory dump (64 kb).


Ok, I think I did this right. Here's the compressed file.

Attached Files


  • 0

#13
edge2022

edge2022

    Member 2k

  • Member
  • PipPipPipPipPip
  • 2,117 posts
They were all caused by a core Windows component, ntoskrnl.exe.
They all occurred in the System process.
This hotfix seems right up your alley: http://support.microsoft.com/kb/839876
The 2nd and 3rd parameters are the same in your dumps and the hotfix description, so try installing that in safe mode.
  • 0

#14
brandynewsome

brandynewsome

    Member

  • Topic Starter
  • Member
  • PipPip
  • 22 posts

They were all caused by a core Windows component, ntoskrnl.exe.
They all occurred in the System process.
This hotfix seems right up your alley: http://support.microsoft.com/kb/839876
The 2nd and 3rd parameters are the same in your dumps and the hotfix description, so try installing that in safe mode.


Tried to use this hotfix, but I get a message saying "Setup has detected that the service pack version of this system is newer than the update you are applying. There is no need to install this update."

Is there an updated version I can try?
  • 0

#15
xtthew!

xtthew!

    Member

  • Member
  • PipPip
  • 44 posts
This is just a suggestion.


Boot into Safe-Mode with Command Prompt.

When the Command Prompt opens, type CHKDSK /R

It'll tell you that you need to restart your computer for it to run, do so.

Wait until the CHKDSK finishes and see if that fixes your problem.

I've found that running a CHKDSK fixes most random startup problems.
  • 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