STOP: C0000139 GDI32.dll
I installed the Windows XP SP3 on my laptop and I am now getting the BSOD mentioned in the Subject line. It appears that the only way to recover from this is going through the Recovery Console. When going through the Recovery Console it is prompting me for the admin password. It is not accepting my admin password so now what?
I just need to replace that file I think and all hopefully will be good to go but I cannot get access to the C: drive and the files on it. So what else can I do to get to the C: Drive?
This is extremely frustrating because I do have a backup of my drive but only the credentials on this current system can access the backup files. If I have to rebuild, that backup data will not be accessible to the new system and its new accounts because all the SIDs will be different.
Any suggestions would be greatly appreciated. I have years of research on this system.
The message went something like the following:
stop:c0000139
the procedure entry point GDIGETBITMAPBITSIZE could not be located in the daynamic link library GDI32.dll
Answers
Solution already mentioned at http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3151626&SiteID=17
1. boot from a Windows CD and go for the repair option.
2. Copy gdi32.dll from c:\windows\servicepackfiles\i386\gdi32.dll to c:\windows\system32\gdi32.dll. (Do keep a backup copy of the old gdi32.dll in c:\windows\system32 directory)
3. Reboot normally
Shashank Bansal [MSFT] wrote: Solution already mentioned at http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3151626&SiteID=17
1. boot from a Windows CD and go for the repair option.
2. Copy gdi32.dll from c:\windows\servicepackfiles\i386\gdi32.dll to c:\windows\system32\gdi32.dll. (Do keep a backup copy of the old gdi32.dll in c:\windows\system32 directory)
3. Reboot normally
Worked.
Thank You.
All Replies
- Same exact problem here, identical:
STOP: c0000139 {Entry Point Not Found} The procedure entry point GdiGetBitmapBitSize could not be located in the dynamic link library GDI32.dll.
??? - Ditto, same error here as well.
Boot to XP CD, replaced RPCRT4.dll and GDI32.dll, still same error Solution already mentioned at http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3151626&SiteID=17
1. boot from a Windows CD and go for the repair option.
2. Copy gdi32.dll from c:\windows\servicepackfiles\i386\gdi32.dll to c:\windows\system32\gdi32.dll. (Do keep a backup copy of the old gdi32.dll in c:\windows\system32 directory)
3. Reboot normally
You obviously did not read my posting completely. I have attempted to do what you described but for some reason it is not accepting my password so HOW do I get past the password issue?Let me ask you another question on this same issue since you stated you are part of the group that built the SP3. At what process point does the gdi32.dll file get moved by the program from c:\windows\servicepackfiles\i386\gdi32.dll to c:\windows\system32\gdi32.dll without the human intervention. Does this happen before the reboot process or during the reboot process or after the reboot process?
- Thanks Shashank, works a treat, will remember the new ServicePackFiles dir.
JimAZ, have a look on the net here for a solution. just type nothing, Try "ENTER"
Shashank Bansal [MSFT] wrote: Solution already mentioned at http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3151626&SiteID=17
1. boot from a Windows CD and go for the repair option.
2. Copy gdi32.dll from c:\windows\servicepackfiles\i386\gdi32.dll to c:\windows\system32\gdi32.dll. (Do keep a backup copy of the old gdi32.dll in c:\windows\system32 directory)
3. Reboot normally
Worked.
Thank You.- Bad news for me - I just found my XP CD-rom in a box in the attic and it's got a crack on it. It's not working.
I tried to copy gdi32.dll direct to my PC from my laptop. Both are windows XP Pro but my Laptop is still running SP2.
Unfortunaltely this didn't work. I was able to copy the file across but when I rebooted I got the same error concerning gdi32.dll.
Does using recovery mode do something other than just copy the file across?
One last thing, I didn't keep a copy of the old gdi32.dll. Any special reason why I should have?
Thanks to anyone that can help, and thanks to Shashank for the tips so far. JMcMillan wrote: I tried to copy gdi32.dll direct to my PC from my laptop. Both are windows XP Pro but my Laptop is still running SP2.
Unfortunaltely this didn't work. I was able to copy the file across but when I rebooted I got the same error concerning gdi32.dll.JMcMillan,
I had uploaded many versions/builds of "gdi32.dll" file to this url. If you trust me, download the file to help you out, otherwise don't. http://www.mediafire.com/?nncyycsdgdz
Regards,
Thomas
- ThomasLee,
Thanks you very much.
I downloaded the suggested file and used the GDI32.dll from SP3_RC2_b5508. It worked a treat. PC rebooted upon first attempt after that.
As we say in Glasgow, you've done me a really good turn.
Thanks again. ThomasLee wrote: JMcMillan,
I had uploaded many versions/builds of "gdi32.dll" file to this url. If you trust me, download the file to help you out, otherwise don't. http://www.mediafire.com/?nncyycsdgdz
Regards,
Thomas
Sorry, I mainly use macs and I've got the same problem on my wife's computer. How do you use the "gdi32.dll" thing? How do you know which version to use?Thanks,MattMatt5709 wrote: Sorry, I mainly use macs and I've got the same problem on my wife's computer. How do you use the "gdi32.dll" thing? How do you know which version to use? Matt5709,
Follow the instructions given by Shashank Bansal [MSFT] at this thread http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3151626&SiteID=17. I can't help you if you don't have the original Windows XP CD. Without the said CD, neither would you be able to create a WinPE or BartPE disk too. You can try the old 4 to 6 boot diskettes method. Download the utility from Microsoft or bootdisk.com website to create the boot diskettes. Or you can also try the Live USB or CD methods http://en.wikipedia.org/wiki/Live_USB and http://en.wikipedia.org/wiki/List_of_LiveDistros. Good luck!
Regards,
Thomas
Shashank Bansal [MSFT] wrote: Solution already mentioned at http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3151626&SiteID=17
1. boot from a Windows CD and go for the repair option.
2. Copy gdi32.dll from c:\windows\servicepackfiles\i386\gdi32.dll to c:\windows\system32\gdi32.dll. (Do keep a backup copy of the old gdi32.dll in c:\windows\system32 directory)
3. Reboot normally
Worked like a charm. Are there any known issues before I uninstall this service pack? Just wondering if I'll have the same issue as when I installed it.
Thanks shashank it works.- Just stopped by to say I have the problem too with RC2. Did not have the problem on my laptop, but did on my desktop.
- Thank you sooo much for posting this. It worked great. My recovery cd didnt work, so I just put the hardrive to another computer and copied the files to the right directory.
You are one reason not to hate Microsoft. Thanks Thanks Thanks und danke - Shouldn't be any uninstall issues, let us know in a new discussion thread here if you see any, please.
Dear TomasLee. THANKS A LOT!
Version SP3_RC2_b5508 have helped! My sincerely appreciation!
I have been too lazy to back up with ghost ....
( Your solution worked for me, too 
)- Hi
I've got the samer problem but i've never used the recovery console before and I'm having trouble following the instructions does any one have this broken down action by action so that a total novice can follow it Now it Works. Thanks
Some background information follows:
Dell D610 running XP sp2 upgraded to sp3 v3244. Nod32 av 2.7. Cisco vpn 5 client. vodafone mobile connect 9.2 office 2k3 with sp.
I began the repair process then it wanted my Product Key which I could not find anywhere. I ended up upgrading to Vista and just move on.
Good luck to you all.
- Well, I am getting farther along now. However when I start up all seems to be going ok. Then, after it seems to boot properly it comes to the login screen, I type in my password and it looks like it is going to start up only to come to what appears to be the login screen again but now it has just my icon and name and it freezes.
Any ideas? On the final screen of the WinXP SP3 RC2 installation, check the *** Do Not Restart box and then click Finish. Open c:\windows\system32\ and locate gdi32.dll. If it is the version dated 2/20/08 with size of 276 KB, it will not work and you must replace it before you restart your computer. I know that an earlier version of WinXP SP3 RC2 contained a version of gdi32.dll dated 2/12/08 with size of 278 KB and that version will work for you. Other versions may work also, but I found this 2/12/08 gdi32.dll in a prior install of WinXP SP3 RC2 on another computer and it got me through.
To repeat for emphasis, do not restart your computer with the 2/20/08 version of gdi32.dll in place in the system32 folder.
In my case, because I had the previously mentioned PW issue in Recovery Console, I had to mount my C: drive as a slave drive in the other computer in order to copy the good 2/12/08 gdi32.dll into the system32 folder. With the right adapter and jumpers, this can be done with the drive from your laptop as well.
The suggestion to try no PW (Just hit Enter) in Recovery Console is a good one because often there is no password for the built-in Administrator account and you may get lucky.
- The low iq scriptkiddies ("oh sorry meant programmers") who could not pass grade school who did this <explicative> should be fired and fined
Butcer,
We want to hear your problems, opinions, and issues, but we do have rules of conduct in these forums. Please refrain from cursing and "name calling" in your posts. We do reserve the right to ban anyone who violates the rules of conduct.
Thanks for your consideration.
-Tony Mann
- Well you guys have obviously no skill at programing that is for sure and do not belong in such a job , how the hell did this get released is what i have to ask?
- Did the guys who made Windows ME make rc3?
Butcer wrote: Well you guys have obviously no skill at programing that is for sure and do not belong in such a job , how the hell did this get released is what i have to ask? It seems like you're really unhappy about SP3...
- I am certainly gd unhappy. I installed this buggy POS and got the same error BSOD on restart. My SP2 install disk doesn't even give me an option for recovery console, just asks to install to whatever partition and an old pre SP1 disk gives me the recovery console but says an error prevents access to the drive so I can't even move files around. Looks like the only option I'll have is to yank the drive out of the computer and hopefully get my laptop to access it and see if it will boot up after I get the file swapped. Take this garbage SP3 file down before you damage anyone else's XP setups!
- Well duh the low iq scriptkiddies who made this beta did not even test this. When i test a system beta i dont expect a full fledge desurction of it.
Butcer wrote: Well duh the low iq scriptkiddies who made this beta did not even test this. When i test a system beta i dont expect a full fledge desurction of it.
First: Get a life and go away.
Second: If you are such an 733t programmer, where is your operating system that you created? Oh thats right, you don't have one because you suck at programming and must attack others in attempt to make yourself feel better about your inept abilities.
I expect you to be banned from here rather quickly, if not hacked or both.Thank you so much for the fix Shashank! I was down for an evening until I could remove my harddrive and remotely copy the file, but the fix worked.
I really appreciate your help!
phew
- you know the feeling when that happens - fix worked great - thanks .
cheers, John
Marvelous.Worked well.
Thanks. You shall be richly rewarded in a future life...in accordance with the prophecy.
Now I can get back to trying to resolve the original error logged by my unappreciative End lUser..... before XPsp3 sent the lil Dell Latitude 530 sLaptop into a neverending restart loop.
Shashank Bansal [MSFT] wrote: Solution already mentioned at http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3151626&SiteID=17
1. boot from a Windows CD and go for the repair option.
2. Copy gdi32.dll from c:\windows\servicepackfiles\i386\gdi32.dll to c:\windows\system32\gdi32.dll. (Do keep a backup copy of the old gdi32.dll in c:\windows\system32 directory)
3. Reboot normally
Worked for me too. Replaced GDI32 seems to be a minor revision, not a SP3 revision. Is that right?
is there any way i can download a working gdi32.dll. I am able to replace any file nessacary.
thanks in advance
j_bosson wrote: cheers, John
Loaded SP3 today same error - can we get this dll issue fixed so I don't have clients ringing me day and night ?
bad thing is some clients have repaired/reloaded their SP2 from disk > naturally the auto update wants to load all the updates since last year which invariably fails due to SP3 dates
I noticed one machine shows 73+ updates at 0 BytesShashank Bansal [MSFT] wrote: Solution already mentioned at http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3151626&SiteID=17
1. boot from a Windows CD and go for the repair option.
2. Copy gdi32.dll from c:\windows\servicepackfiles\i386\gdi32.dll to c:\windows\system32\gdi32.dll. (Do keep a backup copy of the old gdi32.dll in c:\windows\system32 directory)
3. Reboot normally
Thank you very much, it worked,
Yep only thing i have on 3 seperate machines is their inability to update.I applied SP3 RC-2 on a number of hardware and they produced this error. So is Microsoft expecting everyone to perform this workaround on all machines in my enterprise which is about 8,000 computers? I thought build 5508 resolved this BSOD issue. Is there going to be a permanent fix for this issue?
Thanks,
Abed
aaonwona, Build 5508 does not cause this problem, so I infer that you in fact applied an earlier version. SP3 RC2 is build 3311, and does cause this problem. Build 5508 is "SP3 RC2 Refresh" and is only available from Windows Update, not from the download centre. The final public version is build 5512, and should not cause this problem.
Well that's what I thought but I searched for build 5508 and saw a link so I assumed that's what it is. So basicallt what you are saying is build 5508 is not yet available because I have seen people on this thread saying RC2 produced same error when they applied it on their machine. Where can I get a true copy of build 5508?
Thanks
aaonwona, Build 5508 is available only from Windows Update, and not from the Download Centre. You can trigger Windows Update to offer you Build 5508 (SP3 RC2 Refresh) by downloading the registry patch offered at the Download Centre. You might now care to wait until after April 29, when Build 5512 will be available.
Ok thank you. I was just trying to proactively test this before we decide to deploy it in our enviroment
Regards
I got this link from an answer from you from a post I entered. It worked perfect. Now is this the correct SP3 R2 to use? Just leave the way it is or is there another SP3 I need???
Thanks William Worth
smy13 wrote: Hi
I've got the samer problem but i've never used the recovery console before and I'm having trouble following the instructions does any one have this broken down action by action so that a total novice can follow it1. Use the Windows cd to boot the computer up. You may need to go to the bios setup first and make the cdrom the first bootup priority. Usually pressing DEL at the startup will get you there
2. Failing the above. Make a bootdisk floppy from www.bootdisk.com just the WinME bootdisk is fine (just make the floppy the first boot priority in the BIOS) or if you only have a cd rom then this will boot from the cdrom, it's a xp boot cd. http://www.answersthatwork.com/Download_Area/Downrights/ATW_Windows_XP_SP2_Boot_CD.zip
you just have to get a C:\ prompt up, Heck a win 98 boot floppy or such.
3. Once the c:\ prompt is up you first need to rename the bug file by typing
REN c:\windows\system32\gdi32.dll gdi.dll.org
4. Then type
copy c:\windows\servicepackfiles\i386\gdi32.dll c:\window\system32\
IMPORTANT: replace "C" as in c:\ with your own system drive.
5. Install WIndow XP SP3 RC2 Refresh v.5508, which has the latest and updated GDI.dll version 6.0.2900.3316 installed by KB948590.
- Hi,
does anyone can send me the gdi32.dll, which I need, because I've delete it.
Thanks a lot. I have the same problem as mentioned. Will not boot into safe mode or any other options listed when I press F8. Tried booting from Windows CD, went through all the loading drivers etc then said starting windows and then the screen is black. Nothing else happens. So what can I do now?
Shashank Bansal [MSFT] wrote: Solution already mentioned at http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3151626&SiteID=17
1. boot from a Windows CD and go for the repair option.
2. Copy gdi32.dll from c:\windows\servicepackfiles\i386\gdi32.dll to c:\windows\system32\gdi32.dll. (Do keep a backup copy of the old gdi32.dll in c:\windows\system32 directory)
3. Reboot normally
Thank you! it works!
- NikD, can you send me please the right file, becaus I've deleted it not reading this thread before.
Mail: ms.marian@onlinehome.de
Thanks a lot. Marianp wrote: NikD, can you send me please the right file, becaus I've deleted it not reading this thread before. Marianp,
Read this thread for your answer --> (http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3191203&SiteID=17).
Regards,
Thomas
ThomasLee wrote: Marianp wrote: NikD, can you send me please the right file, becaus I've deleted it not reading this thread before. Marianp,
Read this thread for your answer --> (http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3191203&SiteID=17).
Regards,
Thomas
With the *.dll of your link I could rescue my computer, thank you!Thank you this worked for me too.. After a lot of work, my DOS is not so good.
I must beg the question though, how on earth did Microsoft let this happen?? Thousandsif not Millions of people are extremely upset at the moment.
- Exact same problem as dsmith90, except my screen stays blue and hangs on SETUP IS STARTING WINDOWS. However an ERD disc will boot in CD rom, if i could only get SP3 uninstalled, i'll never update again. when i try spuninstall.exe in SP3 folder, i get error. can't find any way around this. I even copied GDI32.dll from ERD disc, to C:Windows/System32/dll cache folder; and it still won't boot up. Disgusted & totally bummed out. 8 years of good programs & data.......gone.
- ok......i think my problem is simualr to evreyone elses..
i installed SP3 ON my laptop and restarted the computer! the computer boots and just stops at a blue screen and this is what it says:
STOP: c0000139 {Entry Point Not Found} The procedure entry point GdiGetBitmapBitSize could not be located in the dynamic link library GDI32.dll.
i cant even log in.. my computer wont even move. it stays at the screen! i tried evrey keyboard i knew, but non of them worked!
the i tried changing the log. i did. but dat didn;t help because i dont have the windows xp cd.
My laptop doesn't have a a floppy drive! i tried wid the botting wid the ether net cable! but dat didn;t work either!
please help me! thnks!
any one gets a answer please email me at:
Muaz820@Gmail.com Muazhaue,
Since you have found this thread in order to post your message, then all the information to help you is already in this thread, and there is no further help available. You have to be able to boot your PC by some means other than your hard disk in order to correct the situation. You need either an installation CD-ROM, or a third-party product such as Bart-PE.
I also note that the official release of SP3 does not have the problem you are describing, so it sounds as if you have installed a pre-release or unofficial version which were only provided for users to beta-test. From where did you find the version of SP3 that got you into this trouble? Once you have your PC running again, you should uninstall the old version of SP3, and delete the installer that you downloaded so that you cannot install it again.
Shashank Bansal [MSFT] wrote: Solution already mentioned at http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3151626&SiteID=17
1. boot from a Windows CD and go for the repair option.
2. Copy gdi32.dll from c:\windows\servicepackfiles\i386\gdi32.dll to c:\windows\system32\gdi32.dll. (Do keep a backup copy of the old gdi32.dll in c:\windows\system32 directory)
3. Reboot normally
it works! thank you very much!Hi Muffinz,
I tried to make the cd rom boot cd from your answersthatwork link, seemed to work making the cd, but then it did nothing when i tried to boot from that drive on my dead desktop....
i don't have a floppy on my functioning laptop- is there somewhere else i can make a boot disk (i don't have one) so that i can get to the c:\ propmt?
I can get to the black screen that asks if i want to run in safe mode, etc, or boot from one of the drives, etc but nothing seems to work.
thanks
hello shashank
i keep trying to copy the file you state, but it keeps telling me that "file not found"
i'm typing
C:\>copy c:\windows\servicepackfiles\i386\gdi32.dll c:\windows\system32\gdi32.dll
obviously without the C:\>
but still no files found, no copies made...
what now?
thanks
Worked for me too but I had to boot in Safe mode menu using the "Don't reboot on failure" first to see problem. That how I managed to get to this point. What a nightmare. Thanks to you all for your help
TriumphBoy
For those of you having trouble getting in to your Hard drive, there is a program on the net called "Bart PE preinstalled environment" (Microsoft Doesn't like this program, I believe), but it enables you to use a live CD that you create to boot from. Then you can look at all the folders / files etc. This disc takes a bit of nous but I guess you wouldn't be this far if you didnt. It might be easier than using the DOS type commands for some. You just need another PC to produce this. Always worth having one handy for the future.
Hope this helps.
Well! Here's a fine how d'ya do! I put SP3 on my HP 6400 and got the same BSOD as everyone else. Tried the steps mentioned in all these threads. When I go into Repair, I get a message that Windows did not detect any HD attached to this machine. I went into the BIOS and there it is 80gb WD SATA drive. I installed XP on the machine when I first got it but, now....... Is there anything special someone could recommend. Right now I'm dead out of the water and need some help.... Anybody?
- I am getting the same message asking for a password and when I put in the Windows password for that machine I am told it is wrong. Did you ever figure out how to get around it or find out what password it wants. Any help is apreciated. I also turned off all passwords in the BIOS. Same as many here, all happened after SP3 upgrade So I know how to replace the .dll file but can't get passed the password line. Thanks
Stuckw/BSOD, if you are trying to use the Recovery Console on an XP installation CD, then the password that it is asking for is the Windows login password for username "Administrator", not the password for any other username that you might be using. If you are using XP Home, then the chances are that the password for username "Administrator" has never been set up, and you can just press the "Enter" key to get past.
This is nothing to do with BIOS passwords.
- Thanks, tried that first. Very strange, of course it is my son's computer so he may have set an admin password that I don't know about, just hope he knows. If he doesn't know it is there any work around? TIA
This is the worst SP Ever I'll even go as far as to say this is the worst beta software that I have ever test and I have tested many beta versions of software before this. I’m beginning to think M.S. is trying to cripple XP down to Vista status just so users would want or feel like they had to switch over to the Dark Side First I couldn't even boot into Safe Mode nor Debug mode. Then the GDI32 Dynamic library link was missing and yes I know the directory to which the file is suppose to be located in and there weren’t any files in the c:/windows/service..... Oh wrong format I was just daydreaming about Linux. c:\windows\servicepackfiles\i386 directory. Then I looked in the backup Directory which there wasn't a GDI32 dll file ether. I can’t even Repair the Windows Directory with the repair option with original WinXP MCE Disk. I have to now reinstall Windows thank you very much MS!. I have no time to fool around with something that worked so well until I made the foolish decision to try the SP. This SOB Service Pack caused unbelievable damage to my Laptop (Dell 1705 With WindowsXP MCE 2005 Update Rollup 2). The install process went fine, no hiccups. The reboot is whole different story.
Here’s some simple advice to all software engineers decision makers that are responsible for the testing phase of software. Make Sure the APP doesn’t cripple the whole system in house first before sending it off to be beta tested.
Are you kidding me?
"Your the reason not to hate Microsoft". Listen this Stop Error shouldn't have happened in the first place and look at all of the steps you had to do in order to get your OS up and running and how much time was wasted on a resolution. My friend, it like you just shot in the head and the person that shot you said oh here’s a band aid just patch it up and you’ll be OK, and then you jumped up with glee and gave him a hugs and kisses and said "thank you very much kind sir, my I have another".
My god!! you had to rip out your hard drive and install it into another machine just so you could transfer 1 File!!! and you thanked Him!!!!!!? He was one reason not to hate Microsoft. COME ON PLEASE!!!!. The reality of it is He only responded because there were more than 5 posts on the same subject. Make a post that has less than 3 of the same subject and you will not hear a thing from anybody from MS and that’s reality. “Thank you sir may I have another and another and another......
rdhw wrote: Muazhaue,
I also note that the official release of SP3 does not have the problem you are describing, so it sounds as if you have installed a pre-release or unofficial version which were only provided for users to beta-test. From where did you find the version of SP3 that got you into this trouble? Once you have your PC running again, you should uninstall the old version of SP3, and delete the installer that you downloaded so that you cannot install it again.
Sorry, but that is not correct and worse still, there seems to be more than one cause with the official release as I managed to repair a computer from Safe Mode while others can't even get to Safe Mode. Also the Gdi32.dll fix does not always work so even the released version is bringing a set of problems. Out of 4 computers (2 with XP Pro, 2 with XP Home, all with SP2 and all available updates), 1 failed and went into a continual reboot cycle. This was not with an RC, this was with the release version that appeared on the Microsoft servers last week.
Best advise I can give is use something like Ghost to back up before installing, just in case anything goes wrong.
Ok, only 1 out of 4 computers I have installed the release version of SP3 had this problem, but in reality it is still 1 computer too many.
Ok, I have been reading all these post trying to see how this relates to my problem. I have not found one issue where someone was getting this error on Server 2003 R2. I rebooted my server this morning after a automatic update, and this is the error I got. Since my domain controller is now down, I sure could use some help on this one.worked fine with my XP home edition
- Well, I instaled SP3 tonight, through regular windows update. Now, when it reboots, it just keeps rebooting. I read through this whole thread, and accomplished the file replacement as instructed, but it did not help, it still just reboots, reboots, reboots. Any other suggestions please?
- The "file replacement" described in this thread is specifically ONLY for STOP C0000139. If you did not get that message, then you should not attempt that "fix". Use the boot menu of XP to select "disable automatic re-boot" so that you see a blue screen with error messages instead of the reboot. Then, in a new thread, post the line of error numbers with any text messages underneath. If you search this forum with the error numbers you might find a solution already posted.
Man I don't understand one thing, people are making a noise in search of 5512 build. Now it is supposed to be available only to the WGA checked computers. So everybody can't get it. Which means that the beta version I download 6 months ago is gone. Then what the hell is this: http://www.microsoft.com/downloads/details.aspx?FamilyID=2fcde6ce-b5fb-4488-8c50-fe22559d164e&displaylang=en??
I thought this must be an XP installation CD with SP3 (available to everybody!!!)! But on double clicking it, it started installing only the SP3. But then it is also available to anyone.
Either there is something I don't understand, or Microsoft has accidentally made it available for everyone.
Thx.
Shashank Bansal [MSFT] wrote: Solution already mentioned at http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3151626&SiteID=17
1. boot from a Windows CD and go for the repair option.
2. Copy gdi32.dll from c:\windows\servicepackfiles\i386\gdi32.dll to c:\windows\system32\gdi32.dll. (Do keep a backup copy of the old gdi32.dll in c:\windows\system32 directory)
3. Reboot normally
got the same stop error, your solution did'nt work, I would not brag about building this POS service pack.
Uwanker wrote: got the same stop error, your solution did'nt work, I would not brag about building this POS service pack. The solution you quote (which did not work for you) is specific for STOP C0000139. If you did not get that error code, then you should not apply this fix. If you get a different error code, or none at all, then this fix will not work, and should not be attempted. You have picked up a very old thread which related to stop C0000139 which is only exhibited by some pre-release versions of SP3. It is thought that the public release of SP3 does not have this problem, so this is not an appropriate procedure for the public release. What symptoms are you actually seeing?
Went here http://www.microsoft.com/downloads/details.aspx?FamilyID=5b33b5a8-5e76-401f-be08-1e1555d4f3d4&DisplayLang=en this morning Monday, May 12th 2008 downloaded, installed and got the error STOP C0000139 GDI32.dll. The posted solution did not work. Is this the final release of SP3?
The final version of SP3 is 331,805,736 bytes long, if that helps you. What version of XP are you trying to install it on to? Previous betas or pre-release of SP3 need to be uninstalled before applying the final version of SP3.
- Thx for putting full info. very curtious of you
This solution did not work for me. First, I was unable to read the BSOD because it passed by in less than a second, so I really could not confirm the error code. However my circumstances matched the rest of the participant’s experiences. I downloaded SP3 on 5/14 through Windows Update and encountered this problem.
Second, I was unable to replace the GDI32.dll through Windows Explorer in Safe Mode, error: file was in use. The same error occurred when tying to delete it.
Third, in the repair option step 2 above, I did not have a gdi32.dll in the c:\windows\servicepackfiles\i386 folder to copy to the c:\windows\system32 folder.
I eventually copied the gdi32.dl_ from the i386 folder on the installation CD... that copied but the same problem reoccurred.
I have tried to reinstall the OS selecting the repair option when installation detected an existing Windows installation... but the same problem reoccurred. I'm currently in the process of reinstalling the OS.
Thanks MS for a day and a half of lost productivity.
Mark
- This worked for me. I to had the reboot problem after installing sp3. I booted my computer with a Linux Live Fedora CD OS and copied the file over and my system booted back up when I restarted.
jrkenn wrote: This worked for me. I to had the reboot problem after installing sp3. I booted my computer with a Linux Live Fedora CD OS and copied the file over and my system booted back up when I restarted.
I'm downloading a copy of Linux Ubuntu to see if I can boot from that. I've also arranged for a friend to lend me a copy of Vista tomorrow, to see if that will boot.
These are last resorts after finally reaching the point of loading a clean install of XP Pro but only gets as far as formating, copying files, auto reboot (required) then when it starts up it goes back to looping again. Is this just a way to move everyone away from XP and onto Vista? I read that XP won't be available soon and updates won't be available from next January.
Maya- i see your solution but im at a loss, im at the c:windows> prompt how do i type this solution?
manhands22 wrote: i see your solution but im at a loss, im at the c:windows> prompt how do i type this solution? Exactly what problem are you seeking to solve? This thread is ONLY for STOP messages C0000139 associated with a message identifying GDI32.DLL, and it is thought that this problem only happened with pre-release versions of SP3. If your problem is different from the stop message C0000139 and GDI32.DLL, then do not attempt any of the solutions in this thread, and instead post in a new thread with all your symptoms in details. If you are getting C0000139 and the related messages explicitly mention GDI32.DLL, then please check that you are actually installing the public release of SP3, and not a pre-release version.
My computer came with WinXP Preinstalled. There's no Windows CD to use for repair. Is there a workaround for that???
- I did that and my AMD Athlon 3000+ PC finally stopped auto rebooting.
It runs fine now. It was down for 5 days until I read your post.
Thank You! Shashank Bansal [MSFT] wrote: Solution already mentioned at http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3151626&SiteID=17
1. boot from a Windows CD and go for the repair option.
2. Copy gdi32.dll from c:\windows\servicepackfiles\i386\gdi32.dll to c:\windows\system32\gdi32.dll. (Do keep a backup copy of the old gdi32.dll in c:\windows\system32 directory)
3. Reboot normally
WITH A RAID SYSTEM
For me this worked.
BSOD stopped computer operating in all modes including safe modes.
XP CD used to boot from and the RAID information was placed on the root of a floppy (yes, still have one). [RAID info copied from the ASUS install CD). Selected R for repair options and then F6 to load RAID drivers. Note that XP accessess this later in the repair, not when you press F6. (This seems to be automatic so IF you don't have a floppy I don't know what you would do.)
This all gives access to C drive starting at C:\windows.
Copied gdi32.dll from a system working fine on SP3. Found in c:\windows\servicepackfiles\i386 to A:\ on my floppy.
Then on faulty computer >> CD system32 to change directory; RENAME gdi32.dll gdi32.old
then COPY a:\gdi32.dll c:\windows\system32\gdi32.dll. (XP Dos mode won't tell you that it has been copied.)
Rebooted and back to normal (FOR ME).
Yes - an afternoon thinking a reinstall of XP was needed - so thanks for the posting.
Mike
- Thank you for the solution it's working perfect on Laptop Compaq Presario 2500
What's the lowdown on this problem? Originally it was associated with some of the earlier Release Candidate versions of SP3 but was supposedly banished in later releases. Now here we are in June and it would seem that a few people are still meeting the same problem and finding that the solution given for the RC still works for them. Surely they can't all be mistakenly installing the Release Candidate rather than the final version of SP3? So what is causing this manifestation of the problem?
Thank you , tried this using win pe disk as I could not remember recovery console password and it worked like a charm
Thank you
- This could possibly happen if you are updating from the Beta's of XP SP3 without uninstalling the beta builds. If you start with SP2 and move to SP3 straight- this will not happen
This problem has happened on two of the office computers I have been upgrading. I am using the latest release of SP3, and this fix worked for both. We have updated about 10 computers successfully without issue, very similar computers, if not identical. so what's causing this?
Lorne1525,
Had the affected PCs previously been trialling the SP3 betas or RCs?
Had all the PCs been kept up to date with post-SP2 updates?
No trials, and yes they were all up to date.
- Lorne1525, the fix is to replace one version of GDI32.dll with a different version of GDI32.dll. Can you post what the version was that caused the crash and what version you replaced it with? How does that compare with your other computers that did not have the problem?
- Thanks Thomas, worked for me too.
- It happened again on another workstation, so I downloaded the latest version of the SP3 installer. Turns out the original one on our network was from Oct 2007, I replaced it with a newer file which had a digital signature from April 2008. Suprisingly, it was 20 megs smaller than the old SP3 installer....Looks like that might have done the trick
Yes this was my problem - used an older version of the SP3 installer. This has been a very thorough thread.Lorne1525 wrote: It happened again on another workstation, so I downloaded the latest version of the SP3 installer. Turns out the original one on our network was from Oct 2007, I replaced it with a newer file which had a digital signature from April 2008. Suprisingly, it was 20 megs smaller than the old SP3 installer....Looks like that might have done the trick To the best of my knowledge there is only one version of the SP3 installer and you can find it here http://www.microsoft.com/downloadS/details.aspx?familyid=5B33B5A8-5E76-401F-BE08-1E1555D4F3D4&displaylang=en
Anything prior to this was a beta or a release candidate or some such. Perhaps Microsoft should have used file names that make this more obvious?
Agreed. I wasnt the one who downloaded the file, I just trusted that my coworker had the correct one.
File names were exactly the same.... File sizes werent, which was a dead giveaway.
MS definately could have made things easier on me with some sort of naming convention for the file. Everyone else knows to put ther version in the file name ...
Solution already mentioned at http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3151626&SiteID=17
1. boot from a Windows CD and go for the repair option.
2. Copy gdi32.dll from c:\windows\servicepackfiles\i386\gdi32.dll to c:\windows\system32\gdi32.dll. (Do keep a backup copy of the old gdi32.dll in c:\windows\system32 directory)
3. Reboot normally
Spot on. Booted into the machine with BartPE and did as instructed starting with # 2. Rebooted the machine and all is working perfectly.
Thanks for the help.Alan,
That isn't exactly true. At first the XP SP3 RTM was exclusively released to TechNet Subsribers and SP3 beta testers and only later released to the at large public and Partner communities simultaneously (eek!). So that initial version during the exclusive rollout is the one that gives fits if used. Why is a great question but it is likely some change was made to it prior to the WU release date. Just download the current version and all the problems are erased.
DU IT Dale wrote: Alan,
That isn't exactly true. At first the XP SP3 RTM was exclusively released to TechNet Subsribers and SP3 beta testers and only later released to the at large public and Partner communities simultaneously (eek!). So that initial version during the exclusive rollout is the one that gives fits if used. Why is a great question but it is likely some change was made to it prior to the WU release date. Just download the current version and all the problems are erased.
That is very interesting. How can you spot the difference between the two versions? Did Microsoft announce that they had made changes?
Alan B wrote: That is very interesting. How can you spot the difference between the two versions? Did Microsoft announce that they had made changes?
If you right click them and > Properties > Version tab > File Version, they all say the same thing. The only way I know of to find out (if you've gotten the downloads mixed up or want to know what you have), is to unpack the download, then look for a new SP3 DLL file. So after unpacking the download search that i386 folder for cabinet.dll (the first one I saw that was new to SP3 with the correct build/version), hover that file( or right click it & Properties) and you'll see the last 4 digits which are the build. 5512 if you have the latest release.
Clint D wrote: Alan B wrote: That is very interesting. How can you spot the difference between the two versions? Did Microsoft announce that they had made changes?
If you right click them and > Properties > Version tab > File Version, they all say the same thing. The only way I know of to find out (if you've gotten the downloads mixed up or want to know what you have), is to unpack the download, then look for a new SP3 DLL file. So after unpacking the download search that i386 folder for cabinet.dll (the first one I saw that was new to SP3 with the correct build/version), hover that file( or right click it & Properties) and you'll see the last 4 digits which are the build. 5512 if you have the latest release.
So what was the build number of "the XP SP3 RTM [that] was exclusively released to TechNet Subsribers and SP3 beta testers" that DU IT Dale says actually differs from the current version?
- Sorry, that I don't know. You can ask someone that has it installed, open any folder, go to "Help", then "About...." and it will be listed as (SP3, v.xxxx). I don't know why that would differ though, I heard there was only one RTM, v5512.
Clint D wrote: Sorry, that I don't know. You can ask someone that has it installed, open any folder, go to "Help", then "About...." and it will be listed as (SP3, v.xxxx). I don't know why that would differ though, I heard there was only one RTM, v5512. So we are back to the mystery of why this error message still crops up every so often. Sometimes it is down to somebody accidentally installing a pre-RTM version of SP3, but always???
- I haven't been following this entire thread from its inception, but if you're talking about the BSOD that's related to the gdi32.dll file, yes, apparently it's still a mystery. I heard that MS fixed this in the release version (5512). I thought I had this issue, and I replaced my gdi32.dll SP3 version file with an SP2 version, and my PC would not boot. I had to delete the SP2 file and rename the SP3 file back in DOS in order to get the PC to boot again. (I have long since found out my problem was due to the infamous reboot loop/BSOD issue which I have fixed).
If anyone can determine the different build versions (positively, if any), between all of the RTM's of SP3, and find out which one(s) are definitely not having this problem, it may prove helpful to get the gdi32.dll file from these said unaffected builds/versions and try them on an affected PC. (But keep in mind what happened to me when I replaced mine with the SP2 version. That could have happened because it was an SP2 version of the file instead of another SP3 build of the file). Clint D wrote: If anyone can determine the different build versions (positively, if any), between all of the RTM's of SP3 There was and is only one RTM build of SP3, and that is build 5512. The RTM/5512 build has a Digital Signature dated 14 April 2008.
There was a build 5508, but that was entitled an "RC2 Refresh", and not an RTM. That had a Digital Signature dated 21 March 2008. It was available only from Windows Update, not from the Download Centre. The Download Centre retained the RC2 build for download even when advertising "RC2 refresh" (a cause of much confusion).
The files gdi32.dll were (apart from version numbers, compilation times, and checksums affected by those) identical in builds 5508 and 5512.
Neither build 5508 nor 5512 should exhibit the STOP C0000139 reboot loop when installed over SP2. Builds 5508 and 5512 incorporated the MS08-021 (KB http://support.microsoft.com/kb/948590 ) fix which had been released for SP2 in the April 2008 Patch Tuesday. The build level of gdi32.dll in the April SP2 fix was 3312, dated 20 February 2008.
The previous public RC release of SP3 had been RC2, build 3311, digitally signed 12 February 2008. If this, or any earlier, build of SP3 was installed on top of an SP2 which had been patched up to date with MS08-021, then that would cause the C0000139 re-boot loop with GDI32.DLL problems.
So the C0000139 reboot loop required two conditions:
- an SP2 which had already received MS08-021 in the April updates;
- an SP3 update of build 3311 or earlier.
It is my belief that all those reporting C0000139 in GDI32.DLL were using an outdated version of SP3. It is very difficult for an end-user to tell the different SP3 versions apart (they all have the same file name and the same external updater version number 6.2.0029.0), unless they check the date of the Digital Signature. Many people took downloads of RC2 from the Download Centre believing that they were getting build 5508, when they in fact got build 3311.
rdhw wrote: Clint D wrote: If anyone can determine the different build versions (positively, if any), between all of the RTM's of SP3 There was and is only one RTM build of SP3, and that is build 5512. The RTM/5512 build has a Digital Signature dated 14 April 2008.
Mine shows April 13, 2008.
I wonder why.
Alan (or anyone else), in case you don't know, you can find what Robin is talking about by right clicking, > Properties > Digital Signatures tab.
- My GDI32.dll shows version 5512 and date modified 14 April 2008 05:41:56 . There is no Digital Signatures tab under Properties (XP Home). Does the date get adjusted for your time zone so if you are far enough to the east (I am in the UK, GMT +1) it becomes 13 April?
Alan B wrote: My GDI32.dll shows version 5512 and date modified 14 April 2008 05:41:56 . There is no Digital Signatures tab under Properties (XP Home). Does the date get adjusted for your time zone so if you are far enough to the east (I am in the UK, GMT +1) it becomes 13 April? Just to be clear, we're not talking about the DLL file, we're talking about the entire SP3 300mb+ download--that's where you right click, > Properties > Digital Signatures tab.
I think the time there (on the SP3 download) is "encoded" and won't be changed and can't be changed. The DLL file may show a different created or modified date depending on when it was installed.
Clint D wrote: Mine shows April 13, 2008. I wonder why. The apparent date/time in the signature is presented to you as it would be in your time-zone. I was quoting the dates as they appear to be in time-zone GMT+1.
rdhw wrote: Clint D wrote: Mine shows April 13, 2008. I wonder why. The apparent date/time in the signature is presented to you as it would be in your time-zone. I was quoting the dates as they appear to be in time-zone GMT+1.
So then what I said here: "I think the time there (on the SP3 download) is "encoded" and won't be changed and can't be changed. The DLL file may show a different created or modified date depending on when it was installed", ..........is wrong? Or that's correct, and you mean regardless of when that SP3 file was or will be downloaded, it will show ~April 14th +/- a day?
Clint D wrote: rdhw wrote: Clint D wrote: Mine shows April 13, 2008. I wonder why. The apparent date/time in the signature is presented to you as it would be in your time-zone. I was quoting the dates as they appear to be in time-zone GMT+1.
So then what I said here: "I think the time there (on the SP3 download) is "encoded" and won't be changed and can't be changed. The DLL file may show a different created or modified date depending on when it was installed", ..........is wrong? Or that's correct, and you mean regardless of when that SP3 file was or will be downloaded, it will show ~April 14th +/- a day?
I think it has to be April 13th or April 14th (because 15th April is more than 18 hours beyond the GMT +1 time stamp and you cannot get more than 12 hours ahead of GMT [+/- 1 or 2 hours for "daylight saving"])
- Ok I gotcha.
I tried twice as you indicated. It did not work. I then booted with a utility disk and manually copied and pasted the gdi32.dll into the systems 32 directory. It then worked OK.
Thanks for the help.TheRealMcCoy wrote:
I tried twice as you indicated. It did not work. I then booted with a utility disk and manually copied and pasted the gdi32.dll into the systems 32 directory. It then worked OK.
Thanks for the help.The general opinion is that you got this error because you mistakenly installed a "beta" or "release candidate" version of SP3, rather than the final version.
Alan B wrote: TheRealMcCoy wrote:
I tried twice as you indicated. It did not work. I then booted with a utility disk and manually copied and pasted the gdi32.dll into the systems 32 directory. It then worked OK.
Thanks for the help.The general opinion is that you got this error because you mistakenly installed a "beta" or "release candidate" version of SP3, rather than the final version.
Actually, I believe that happens due to the WFP/SFC function which prevents system files from being deleted or renamed. In MS-DOS that is bypassed so one can then modify system files. But without an explanation of what "it did not work" exactly means, it's hard to say. If you were getting the typical XP message about not being able to delete/move/rename/replace a file because it's "in use" or something like that, that's the WFP/SFC causing it.
Clint D wrote: Alan B wrote: TheRealMcCoy wrote:
I tried twice as you indicated. It did not work. I then booted with a utility disk and manually copied and pasted the gdi32.dll into the systems 32 directory. It then worked OK.
Thanks for the help.The general opinion is that you got this error because you mistakenly installed a "beta" or "release candidate" version of SP3, rather than the final version.
Actually, I believe that happens due to the WFP/SFC function which prevents system files from being deleted or renamed. In MS-DOS that is bypassed so one can then modify system files. But without an explanation of what "it did not work" exactly means, it's hard to say. If you were getting the typical XP message about not being able to delete/move/rename/replace a file because it's "in use" or something like that, that's the WFP/SFC causing it.
We are writing at cross purposes here, Clint. I mean that the fundamental cause of the stop error associated with gdi32.dll is failure to use the correct, current, final version of SP3. At least that is the considered opinion. Nobody who has replaced gdi32.dll has said what file version they replaced and what file version they replaced it with.
Alan B wrote: We are writing at cross purposes here, Clint. I mean that the fundamental cause of the stop error associated with gdi32.dll is failure to use the correct, current, final version of SP3. At least that is the considered opinion. Nobody who has replaced gdi32.dll has said what file version they replaced and what file version they replaced it with.
Ahhhhhhh! Sorry, I understand now.
In that case, let me be the first to do so...after being helped here how to fix my problem.
Before the fix, i had file version 5.1.2600.3316 which i replaced with version 5.1.2600.5512 and problem was solved
- Well version 5512 is the version that should have been installed by the SP3 update so your fix was to do manually what should have been done automatically.
Yeah, 3316 is some pre-release SP3, like one of the RC2 or "Refresh" versions. 5512 is the final release version. So you apparently installed a pre-release SP3 version. You should probably remove it and install the 5512 build/version.
As I'm a lazy *** sysadmin, I'll just leave it at this...the box works, doesn't have a network connection, so why bother?
But thanks again for the info!
Ogri01 wrote: so why bother? Maybe the beta releases are time-bombed?
rdhw wrote: Ogri01 wrote: so why bother? Maybe the beta releases are time-bombed?
SP3 in general seems to be time-bombed.
It doesn't have a network connection because that's the way it's supposed to be, or is that another issue with it?
Hi Matt,
Usually you will find varios versions of GDI32.DLL in various backup folders.
To find out wich version of GDI32.DLL you have to copy to the SYSTEM32 folder, look at the file USER32.DLL in this folder. The version number of the GDI32 must match this USER32 file. In the folder servicepackfiles\i386 they do match, but in SYSTEM32 the mismatch causes the BSOD (stop) problem.
If you can't boot from CD or the console goes wrong, take the hard disk out and connect it to another working system, so you can do it using explorer.
Cheers and good luck.
Nils
GREAT ! works a treat. Thankyou.- If you have web access, and a CD burner, you can download a ISO file to create a bootable linux CD that will allow you to change the Admin Pwd. It's named pwd_chg.iso. I'm sure if you search for it you will find it.
Recovery console fix worked for me - 2 minute fix.
Replaced with GDI32.dll version 5.1.2600.3311 if that helps...
Beanie_again wrote: Replaced with GDI32.dll version 5.1.2600.3311 if that helps...
Just FYI, v3311 is not from SP3 release, it's an RC2 or "Refresh" version. v5512 is the release version.
I have yet to find a solution that works for the Dell D620 laptop other than reimaging my machines.
I receive the endless reboot with the Stop: C0000139 error. I am not able to boot from Windows CD -- I can select the option, but then the machines hang, and start up the boot loop process again. I cannot boot into any form of Safe Mode either -- same issue, hangs and then goes through the boot loop process again. I have contacted Dell about this and they have been overwhelmed with phone calls and no solution.
I do not have this issue with my Dell D630 models. Luckily I have more D630 machines than D620 machines.
VLizzle wrote: I receive the endless reboot with the Stop: C0000139 error. Please check that you are using the correct publicly released version of the SP3 updater, by direct download from Microsoft only. The stop C0000139 quoting gdi32.dll occurs only with beta and pre-release versions of the SP3 updater. This stop does not occur with the publicly released version of the SP3 updater.
Thanks for the suggestion but I was trying to update with the direct dowload from Microsoft only. On one machine, I was prompted by Windows Updates to install SP3 and I still have the same problem. It only happens with Dell D620 laptops. I have had success with every other model machine that we use.VLizzle, with your C0000139 stop, what is the name of the DLL referenced?
- In my case, I could not even get to the Repair console - after I selected the right windows install directory: c:\windows the machine would reboot. So the Repair option on the CD was useless...
UBCD to the rescue - I have an old one v2.51 - it booted OK, then I followed the gdi32.dll replacement suggestions and added a step to rename c:\windows\dllcache\gdi32.dll to something else...
And all is good! Saved me several hours of a reinstall... Thanks!
\eYeks - It worked like a charm. Thanks for the tip.C.
