Results 1 to 11 of 11
  1. #1
    New Lounger
    Join Date
    Dec 2009
    Location
    OKC, Oklahoma
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Unhappy Cannot get into windows

    I was getting the BSOD when I rebooted unless I used "a good previous setting." It was the win32k.sys as the problem. So I did something really dumb, as it turns out, I renamed that file to win 33k.sys. Now I cannot get into windows at all to change it back. I've tried loading Windows XP again - get the BSDO. Tried using a 3.5" floppy with MSDOS 5.0 as boot up, but could not get into the C drive. Tried loading Windows XP SP2, another BSOD. Frankly I'm at a loss on how to proceed. Any help is GREATLY appreciated.

    Ben (don't rename files agin)

  2. #2
    Lounge VIP
    Join Date
    Apr 2011
    Location
    Scotland
    Posts
    1,168
    Thanks
    44
    Thanked 134 Times in 115 Posts
    Ben, using the PC you used to post the request for help, download and burn a copy of Hirens' Boot CD. That will allow you to boot the dead machine off the CD and fix the renamed file. It will also allow you to fix the underlying issue by performing a Blue Screen View / system restore / registry repair / disk repair etc.

    Just be careful in choosing which tools to run from the boot CD: some can damage an installation in unwary hands.

    Once you have the machine running again, use the Boot CD to take a full PC image backup.
    In God we trust; all others must bring data.

    - William Edwards Deming. 1900 - 1993

  3. The Following User Says Thank You to Tinto Tech For This Useful Post:

    ruirib (2012-08-01)

  4. #3
    New Lounger
    Join Date
    Dec 2009
    Location
    OKC, Oklahoma
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Do you have another program that you would recomend? I've downloaded the Hirens Boot CD 3 times and each time I go to execute it, I get a corrupted setup file, please try later. Also, when you first click on the program, it send you to the internet where it want to load a bunch of other stuff . .

    Thanks,
    Ben

  5. #4
    Lounge VIP
    Join Date
    Apr 2011
    Location
    Scotland
    Posts
    1,168
    Thanks
    44
    Thanked 134 Times in 115 Posts
    An alternative download location for Hirens is here. Check the MD5's to be certain that the download is correct. Refer to the CD burning instructions here.

    If that still doesn't work for you, perhaps try Universal Boot CD for Windows (UBCD Win) from here.

    Both can do very similar work for you.
    In God we trust; all others must bring data.

    - William Edwards Deming. 1900 - 1993

  6. #5
    Super Moderator CLiNT's Avatar
    Join Date
    Dec 2009
    Location
    California & Arizona
    Posts
    6,121
    Thanks
    160
    Thanked 609 Times in 557 Posts
    Any bootable dos disk should allow you to rename the file in question.
    Even the command prompt from within the recovery console of the Windows XP disk should suffice.
    Type help for the appropriate commands.
    Bootdisk.com

  7. #6
    New Lounger
    Join Date
    Dec 2009
    Location
    OKC, Oklahoma
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts
    I have tried every thing that has been suggested and I still get the BSOD with this message:

    STOP: c000021a {Fatal System Error}
    The Session Manages Initialization system process terminated unexpectedly with a
    status of 0xc0000034 (0x00000000 0x00000000).
    The system has been shut down.

    Any ideas besides putting the whole thing in the trash are welcome.

    Ben

  8. #7
    Lounge VIP
    Join Date
    Apr 2011
    Location
    Scotland
    Posts
    1,168
    Thanks
    44
    Thanked 134 Times in 115 Posts
    That's very strange, because before renaming win32k.sys you could boot by returning to last known good settings.

    Renaming win32k.sys back to its original and running a system restore from one of the boot disks should get you to the same point as the "Last Known Good Configuration" as per the boot menu.

    Does the machine boot from the boot CD's suggested, or are you still having problems with that? Were there any other changes that you need to roll back?

    Do you have an XP installation disk so that you could consider running a non-destructive re-installation?
    In God we trust; all others must bring data.

    - William Edwards Deming. 1900 - 1993

  9. #8
    New Lounger
    Join Date
    Dec 2009
    Location
    OKC, Oklahoma
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Also, I get the same message when I try to boot from the windows CD.

    Ben

  10. #9
    Lounge VIP
    Join Date
    Apr 2011
    Location
    Scotland
    Posts
    1,168
    Thanks
    44
    Thanked 134 Times in 115 Posts
    The error same message when booting on the Windows installation CD?

    I know it's a silly question, but are you sure it's booting off the CD and not falling through the BIOS boot sequence to the hard drive?

    If you are sure it's occurring when you are booting of the CD, then I think you have a problem that we won't be able to fix on the forum: it would needs hands on from a reliable local repair shop.
    In God we trust; all others must bring data.

    - William Edwards Deming. 1900 - 1993

  11. #10
    New Lounger
    Join Date
    Dec 2009
    Location
    OKC, Oklahoma
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts
    I went into the BIOS and made sure that it only booted from the CD if I were going to use one, or the floppy drive if I was going to try to use a DOS boot.
    I finally ended up taking it to the Geek Squad as my school has an account there. We'll see what they find out.

    Thanks for all the thoughtful suggestions.

    Ben

  12. #11
    Uranium Lounger
    Join Date
    Mar 2001
    Location
    New Jersey
    Posts
    6,684
    Thanks
    1
    Thanked 11 Times in 11 Posts
    A little late to the party here, but thought I'd offer one other option. It's a down and dirty, old school technique. Pull the problem HD and slave it to another machine. Then simply open the "bad" drive, navigate to the win33k.sys file you made and rename it win32k.sys. Reinstall the drive in it's case and your system should start unless what you've been doing has fouled up something else or the drive itself has issues.

    Good luck.
    <IMG SRC=http://www.wopr.com/w3tuserpics/DocWatson_sig.gif>

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •