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

{BSoD] Assistance with kernel32.dll (made a stupid move)


  • Please log in to reply

#1
sourceblitz

sourceblitz

    New Member

  • Member
  • Pip
  • 2 posts
Hi guys - I originally had a problem with kernel32.dll where a few programs are not detecting the entry point and what not...

However, I made the mistake of replacing the kernel32.dll

I took a floppy that I had kernel32.dl_ in it, and expanded it into my system32 folder - and now, on reboot, I have a blue screen, telling me I have an entry point error. From what I can understand, the kernel32.dl_ I used wasn't the same as the original, and now won't load up anything else: and now I can't get back to a command prompt to fix it. Currently, I have a back-up of the original, renamed in the folder.

Thanks in advance.
  • 0

Advertisements


#2
anzenketh

anzenketh

    BSOD Warrior/Computer Surgeon

  • Technician
  • 2,854 posts
Hello sourceblitz,

What is the exact error message that you are receiving.
  • 0

#3
sourceblitz

sourceblitz

    New Member

  • Topic Starter
  • Member
  • Pip
  • 2 posts
It's an stop error, with the code c0000139 - and references entry point and kernel32.dll // any form of OS loading, including safe mode will not work.

I know what I need to do to solve the problem - and that's to delete the new kernel32.dll that I expanded, and rename the original back to kernel32.dll - but I have no way of accessing the files via DOS prompt or anything. Safe mode with command prompt also results the same error.

The file that calls the error is ntdll.dll and references the procedurer entry point rtlencodepointer, not being located.

Edited by sourceblitz, 08 August 2007 - 09:26 PM.

  • 0

#4
anzenketh

anzenketh

    BSOD Warrior/Computer Surgeon

  • Technician
  • 2,854 posts
Have you tried booting to the recovery console from the XP disk?
  • 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