A problem with XP sp3 update.
hello:
I have just updated my pc from xp sp2 to sp3. The installation was sucessful, but when I reboot my pc after the installation finished, my pc started to reboot again and again.
i choose "don't restart pc automatically ......" then i see a bluescreen show following
stop:c0000139
the procedure entry point SMapLS_IP_EBP_24 could not be located in the daynamic link library Kernel32.dll
Before the update, everything work smoothly on my pc. The update was downloaded from technet of ms website and my friend use the same update file and sucessfully updated to sp3
Answers
This issue happens with 3311 build of XP SP3.
RC2 Refresh build 5508 does not encounter this issue.
It happens because KB948590 stops installation of SP3 version of gdi32.dll on the system due to file version differences.
In case you are already hittting the blue screen, please follow these steps:
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
Thanks
Shashank
All Replies
Try using the friends computer since it seems to be better
...................................................
- Whose computer should my friend use?
Can you please share the following information from the affected system?
1. Does a safe mode boot succeed?
2. What is the file version of kernel32.dll on the system?
3. Please share svcpack.log from c:\windows
4. Please follow the instructions mentioned in KB316450 and gather a complete memory dump.
Please contact us by email and we would set a mechanism for sharing information up.
Thanks
Shashank
Shashank Bansal [MSFT] wrote: Can you please share the following information from the affected system?
1. Does a safe mode boot succeed?
2. What is the file version of kernel32.dll on the system?
3. Please share svcpack.log from c:\windows
4. Please follow the instructions mentioned in KB316450 and gather a complete memory dump.
Please contact us by email and we would set a mechanism for sharing information up.
Thanks
Shashank
1. Safe mode also cannot boot succeed
2. kernel32.dll is the version 2.11.2008,and i checked with my friend's pc(updated to sp3) it's the same as mines.
I found the solution. Although my bluescreen show "SMapLS_IP_EBP_24 could not be located in the daynamic link library Kernel32.dll", this is the same problem as another case previous resolved.
I copy the "gdi32.dll" from service package file folder to windows\system32 the problem gone.
However, i want to know what cause this happened and how to prevent it.
This issue happens with 3311 build of XP SP3.
RC2 Refresh build 5508 does not encounter this issue.
It happens because KB948590 stops installation of SP3 version of gdi32.dll on the system due to file version differences.
In case you are already hittting the blue screen, please follow these steps:
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
Thanks
Shashank
Thank you very mcuh for the solution, I was having the
stop: c0000139 {entry point not found} The procedure entry point GdiGetBitmapBitsize could not be located in the dynamic link library GDI32.dll
Same thing, I was able to solve it by booting the system using BartPE (Windows XP that boots from a CD), opened up a command line
-
cd'd into the path where my service pack file was stored.
ran
Code Snippetwindowsxp-kb936929-sp3-x86-enu.exe /?
That extracted the contents of the SP3 into the following folder
\7a975a67c61538ac281edb -
cd'd into the system folder so I could rename the original files to back them up
Code Snippetcd \windows\system32
ren gdi32.dll gdi32.dll.orig
cd \windows\system32\dllcache
ren gdi32.dll gdi32.dll.orig
-
cd'd into the folder that holds the extracted SP3 files and expanded them into the system folders.
Code Snippetcd \7a975a67c61538ac281edb\i386
expand gdi32.dl_ \windows\system32\gdi32.dll
expand gdi32.dl_ \windows\system32\dllcache\gdi32.dll
That's it, then just reboot and everything is fine!
- Proposed As Answer bysantosh84 Sunday, March 29, 2009 3:15 PM
-
"It happens because KB948590 stops installation of SP3 version of gdi32.dll on the system due to file version differences."
what caused the version differences?
The KB mentioned was released post 3311
As 3311 build carried updated released till the date it went public, the new KB was not included.
The KB carried a version of gdi32 higher than 3311 (as it was released later). This caused the difference.
Using a later SP3 build (5508) would ensure the issue would not happen.
Thanks
Shashank
ok, i get it.
thank you for your reply.
Shashank Bansal [MSFT] wrote: This issue happens with 3311 build of XP SP3.
RC2 Refresh build 5508 does not encounter this issue.
It happens because KB948590 stops installation of SP3 version of gdi32.dll on the system due to file version differences.
In case you are already hittting the blue screen, please follow these steps:
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
Thanks
Shashank
I just installed SP3 RC2 and I still got this issue. I am working at fixing it hopefully if the Admin Console allows me to log in.
- Worked, thanks
That procedure was very hellphull for me, ... very thanks I thoth to install again my WXP imagine...!
Thank
Julius
Shashank Bansal [MSFT] wrote: This issue happens with 3311 build of XP SP3.
RC2 Refresh build 5508 does not encounter this issue.
It happens because KB948590 stops installation of SP3 version of gdi32.dll on the system due to file version differences.
In case you are already hittting the blue screen, please follow these steps:
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
Thanks
Shashank
Can this file replace been done if the hard drive is run as a slave on a separate computer?Shashank Bansal [MSFT] wrote: This issue happens with 3311 build of XP SP3.
RC2 Refresh build 5508 does not encounter this issue.
It happens because KB948590 stops installation of SP3 version of gdi32.dll on the system due to file version differences.
In case you are already hittting the blue screen, please follow these steps:
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
Thanks
Shashank
It seems the solution given above works for everybody but not for me.
After all necessary files of the boot CD are loaded and the setup should be ready, I receive the following error.
STOP 0x0000007B (0xF78D663C, 0XC00000034,
I was pleased to learn about this quick solution but unfortunately it seems I have to reinstall Windows XP SP2
NOTE: IF YOU RECEIVE THIS ERROR DON'T FORGET TO LOAD YOUR RAID OR SATA DRIVERS FOR YOUR HARDDISK. THE FIX MENTIONED ABOVE WORKS PERFECT BUT IN MY CASE I FORGOT TO LOAD THE NVRAID DRIVERS.- I had exactly the same problem a few days ago. I had to load my most recent backup which luckily was only a couple of days old. Yesterday sp3 came down with windows auto updates. Knowing that my last attempt ended in near disaster I applied the update fully expecting another night of frustration. Not in the slightest. Everything went smoothly and the pc is now very stable. It seems to me that "trying out" the pre-release version is causing some problems with certain pc`s. The pc is much improved and the speed is about 50% up. No doubt another can of worms has been opened by Mr Gates with this upgrade. Some will like it some will loath it but I for one love it.
PS got vista ultimate on my other machine and sp1 won`t work on that either!! SIGH. Sounds like you have a failing hard drive. It most likely was failing prior to update.
- Im prettty sure the same scritkiddies who craped out Windows Me made Rc3
- I am having exactly that same problem, but I don't clearly understand your solution. Can you elaborate?
How do you tell what build you have downloaded? I dont see it in properties \ version.
Thank you,
Marianne
Max41 wrote: How do you tell what build you have downloaded? I dont see it in properties \ version. Max41,
Download this tool HashCalc 2.02, and install it. The checksum for build 5508 is
Size: 316 MB (331,774,504 bytes)
MD5: 458890e635ef9c8103b524cb5a8e1a34
SHA1: c1996fe3afe721f3962a15d6666603ec857f4095
Or extracts the downloaded file using winrar or 7-zip. There is an "update.inf" file inside the (i386\update\) folder. It should said ThisServicePackBuild=5508
Regards,
Thomas
I feel stupid asking, but how can I get a Windows CD to boot from... I have original XP discs, Symantec recovery discs, but I don't get the chance to boot from them - it goes straight to the BSOD... I've hit the F5 on startup, but none of the options avoid the deep blue....
Any help really appreciated, my machine seems dead...
PedroBlanco, the boot device preference is a BIOS setting. You need to change your BIOS settings to specify the boot device is the CD-ROM. Please consult the documentation that came with your PC to find out how to do that.
Shashank Bansal [MSFT] wrote: Using a later SP3 build (5508) would ensure the issue would not happen.
Then WHY is Microsoft still offering the earlier build on their website as of April 23rd, 2008?
Just so we can all waste hours of our time with this, even though its been fixed already?
I had to go to an internet cafe to find this, with my computer not booting.
FURTHER: My unattended windows install disk with SP 2 integrated, will NOT give me a REPAIR option at any point... I can press F2 for the ASR, but that wants a floppy disk, I don't even have a freaking floppy disk on my computer!
so, once I arrive at the input screen, it only gives me an option of installing anew on the various partitions.
There's no repair option. You think you could account for that in your instructions on fixing this?
Tsais wrote: Shashank Bansal [MSFT] wrote: Using a later SP3 build (5508) would ensure the issue would not happen.
Then WHY is Microsoft still offering the earlier build on their website as of April 23rd, 2008?
Just so we can all waste hours of our time with this, even though its been fixed already?
I had to go to an internet cafe to find this, with my computer not booting.
Absolutely incredible...I downloaded the file from Microsoft about 8 hours ago and it was still v3311.
I managed to sort mine out (gdi32.dll problem), I hope you can sort your problem out eventually although Microsoft must take the blame surely for supplying a bugged version and not updating SP3.
Hey.
And easy way, is to copy (gdi32.dll) from C:\windows\servicepackfiles\gdi32.dll to C:\windows\system32 before you restart pc after installing sp3. (Remember to rename gdi32.dll to old before copying).
Works great.
arvter
i keep trying the copy file trick that seems to work for everyone, but it keeps telling me file not found 0 files copied....
uh oh
what now?
Alright, I ran into the BSoD issue, and I didn't get the 5500 build of sp3 apparently. Well anyways, I tried that whole method of copying the verison from ServicePack folder and copying into System32. It didn't seem to work for me, and I looked up and saw that the RC2 Refresh 5500 build had GDI32.dll version 6.0.2900.3316. So for anyone who has this verison of GDI32.DLL, would you send me it via email or upload onto rapidshare.com or megaupload.com I'll really be happy if someone helps me out. No one seems to have that verison of it up anywhere. Or if someone at Microsoft could have it available for standalone download not with the whole pack, because I can't do anything that would work.Nevermind, I was searching thru the forum more and found someone who had uploaded the latest verison. Thanks to anyone who does post
\paulenski wrote: Nevermind, I was searching thru the forum more and found someone who had uploaded the latest verison. Thanks to anyone who does post I guessed you're talking about me...
Thank you! I too was getting the
STOP: c0000139 {entry point not found} The procedure entry point GdiGetBitmapBitsize could not be located in the dynamic link library GDI32.dll
BSOD using the outdated version (3311) just downloaded today ( 3 May 2008). Microsoft should really replace the file - it would save end-users countless hours of frustration. I can't beleive Microsoft is actually being so irresponsible about this!
Anyways, renaming and replacing GDI32.DLL did the trick. Luckily, I bought a copy of Winternals ERD Commander 4 or 5 years ago, and it allowed me to boot to a GUI where I was then able to rename and replace GDI32.DLL using a Windows Explorer-type interface.
awlevinson wrote: i keep trying the copy file trick that seems to work for everyone, but it keeps telling me file not found 0 files copied....
uh oh
what now?
In the same boat here. C:\Windows\Servicepackfiles\i386\ doesn't contain any files. Any ideas?
For what it's worth, I downloaded SP3 from
http://download.windowsupdate.com/msdownload/update/software/svpk/2008/04/windowsxp-kb936929-sp3-x86-enu_c81472f7eeea2eca421e116cd4c03e2300ebfde4.exe
It installed fine on one machine, but the other has the reboot problem mentioned here.Wishdiak wrote: awlevinson wrote: i keep trying the copy file trick that seems to work for everyone, but it keeps telling me file not found 0 files copied....
uh oh
what now?
In the same boat here. C:\Windows\Servicepackfiles\i386\ doesn't contain any files. Any ideas?
Could you please tell us, what size and date the "gdi32.dll" in \windows\system32 shows? (Recovery Console -> dir /system32/gdi32.dll)
Which XP edition are you runnig? Home Edition, Professional, Media Center (which version)?
Bye,
Freudi- Freudi,
Thanks for your reply.
I was running XP Pro SP2 until yesterday. Now I seem to be stuck without a usable system. I tried restoring gdi32.dll from a SP2 install disc with no luck.
Currently, C:\Windows\system32\gdi32.dll -> 08/03/04 06:56p -a----- 278016 gdi32.dll
Thanks in advance for any help that will help me avoid a full reinstall. Wishdiak wrote:
Currently, C:\Windows\system32\gdi32.dll -> 08/03/04 06:56p -a----- 278016 gdi32.dll
Hm, strange, I'm not aware of any gdi32.dll of that date.
Anyhow, in case SP3 installed on your machine and the machine git unaccessible afterwards, you may want to boot into Recovery Console and type the following into the prompt - In case you've decided to put the $ntservicepackuninstall$ folder onto another drive or patch during the installation process of SP3, please let us know and don't run the following commands:
You'll have to hit [Enter] after each line.Code Snippetcd \windows\$ntservicepackuninstall$\spuninst
batch spuninst.txt
That should uninstall the service pack stored in that folder. After Windows reboots, you may want to look for any SP3 entry under "Software" in the Control Panel and uninstall that one too.
HTH,
FreudiYanglaoshih and Shashank--My compliments and gratitude, at a time when all the MS forums are full of frustrated XP heretics and defensive loyalists on SP3's "official' release...you have given us the only thread that seems to consistently provide the real knowledge on the technical problems these forums were created for. Keep talking to us!
Darrel
- Freudi,
Thanks for your advice. I've already done a repair install using a SP2 disc and that succeeded. I have this rebooting problem on a Desktop with XP Pro. However, I have no Floppys or CDs as my computer came with XP installed so I can't use this method.
What should I do to solve the problem?
for some reason both gdi32.dll in servicepackfiles and system32 folders are the exact same file versions.. this repair did not work for me. are there any other fixes?I had the same problem found fix in MS data base hrere
CAUSE
Most computers include an image that the manufacturer created by using the System Preparation (Sysprep) tool. Sysprep lets the computer manufacturer generate an image that can be used on different computers. The problem that is described in the "Symptoms" section may occur if the original Windows XP Service Pack 1 (SP1) Sysprep image is created on an Intel-processor-based computer and if the Sysprep image is then deployed on a non-Intel-processor-based computer. Under this configuration, after the computer is upgraded to Windows XP SP2 or SP3, the Intel processor driver (Intelppm.sys) may try to load because an orphaned registry key remains from the original Sysprep image.
This issue may also occur if the original Windows XP SP2 or Windows XP SP3 Sysprep image is created on an Intel-processor-based computer and if it is then deployed onto a non-Intel-processor-based computer. Again, the Intel processor driver (Intelppm.sys) may try to load because an orphaned registry key remains from the original Sysprep image.
For more information about unsupported scenarios when you deploy a Sysprep image on a destination computer that has a different vendor's processor than what the original image is based on, click the following article number to view the article in the Microsoft Knowledge Base:828287 (http://support.microsoft.com/kb/828287/) Unsupported Sysprep scenarios
Note We do not support using Sysprep to install an operating system from an image if the image was created by using a computer that has a different processor. For example, you cannot create a Sysprep image on a computer that has an Intel processor and deploy the image to a computer that has an AMD processor.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.RESOLUTION
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:322756 (http://support.microsoft.com/kb/322756/) How to back up and restore the registry in Windows
To resolve this issue, follow these steps:1. Restart your computer in Safe Mode.
For additional information about Safe Mode in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:315222 (http://support.microsoft.com/kb/315222/) A description of the Safe Mode Boot options in Windows XP2. Click Start, click Run, type regedit, and then click OK. 3. Locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Intelppm4. In the right pane, right-click the Start entry, and then click Modify. 5. In the Value data box, type 4, and then click OK. 6. Quit Registry Editor. 7. Restart your computer.
APPLIES TO
• Microsoft Windows XP Professional Service Pack 2 (SP2) • Microsoft Windows XP Service Pack 3, when used with: Microsoft Windows XP Professional Microsoft Windows XP Home Edition Keywords:
kbsetup kberrmsg kbtshoot KB888372 Thanks for the info Dan, I will give it a try.
It is interesting that Acer tech guys didn't know about this problem and how to fix it. My desktop was on warranty and it was shipped back to Toronto twice to solve the problem and all they did was put a new hard drive in it. I guess they would have tested it each time and then reloaded XP and sent it back. As soon as I got it back, I uploaded the updates and the problem started again!
It has cost them 2 hard drives plus 4 freight trips to Toronto at $63 each.
Dan, I did what you suggested but unfortunately it didn't solve the problem. Computer is still rebooting.
Microsoft: I don't care whose fault this is, YOU need to be sued for this ***!!!! I didn't ask for your lousy update. You had no business released this thing in the condition that it's in and messing up my computer!
I couldn't agree more! Come on Micosoft, give us an easy fix for this problem you have created. I need a fix that doesn't require a CD or a Floppy. I have spent dozens of frustrating hours trying to solve this problem - FIX IT FOR US!
From a user:
Most of the problems are that HP and others supplied the intelppm.sys module on AMD systems. DO NOT RENAME INTELPPM.SYS NOR ISSUE THE COMMAND IF YOU ARE AN INTEL SYSTEM - IT WILL PREVENT BOOTING, AND YOU MIGHT NOT EVEN BE ABLE TO GET INTO SAFE MODE. AMD USERS: One fix is to come up in safe mode and rename intelppm.sys. The fix I USED is to come up in safe mode with command prompt and issue EXACTLY this (with spaces where I put them):
sc config intelppm start= disabled
You should get a completed message.
This cured my AMD X2 HP media center. I read about this on some blogs, etc. Also, if you have a certain high ASUS board, then they say to plug a USB "thumb drive", etc., into a usb port. This might get you to safe mode, I don't know. This is also an AMD issue, or as the story goes. As I said, the command above fixed my HP AMD system by stopping the Intel power management. I have powered off and on several times, and I am stable on XP SP3 now. P.S. If you install SP3, I have seen where it INSTALLS THE IE7 BROWSER, and you must remove SP3 to go back to IE6.Note that I have now updated the intelppm setting in my registry to 4 as other suggestuons say to do, in hopes that if the command I used (above) is negated somehow by future updates, that I will still be covered.
- Hi,
I have the same problem.
Could you please give me the exact syntax for the above fix, from the beginning to end since I am not a pro.
e.g. what do you mean by cd'd?
Appreciate every help, thanks in advance.
have a good day. Same Problem here. I installed SP# from the Windows Update site last night to a Compaq machine and it is giving me the endless reboot.
MB
If you look at Microsoft support for XP, they now tell you to back up your system before you download SP 3 in case it damages your program. This sure doesn't help us poor suckers who were on automatic update (which Microsoft recommends!).
I'll bet anything that this warning wasn't on the site before we started having problems.
They cause the problem and then they warn you after it's too late and then they don't provide a sollution - such a fine Company!
Shashank
Hi, My computer did not get the BSOD but it keeps on re-booting after the SP3 was installed from the Update website. I don't know the RC version but I tried the above with no results. I can boot in to the SAFE mode but dont know what to do from here.
I have an HP Desktop with AMD processor and my XP was fully updated with all the patches and SP2 until date. I tried to go back to a previous known good configuration (an option on my Boot Screen) but this does not work and it still comes back to rebooting.
Urgent assistance is appreciated and any known workarounds would be appreciated.
Raven
- I had the same problem with spontaneous rebooting. The SP3 did not load completely as well. I the tried to repair windows xp with my original XP disk but all it did was make my computer unbootable and stated that my system files were missing. I am still working on this and trying to get my original windows back. But I may have to reinstall windows
XP and reinstall all my programs again. I am also looking for a solution. I sympathize with your problem. Hope someone in this forum can help.
For what it's worth, I got a reply from Microsoft as follows. I have tried it several times and I thought it had worked as my computer ran for several hours before it rebooted. I am also getting a screen constantly, "your computer has recovered from a serious problem". I reported it to MS about 25 times but it still keeps coming up over and over.
Here is the MS reply:
Actually, this kind of issue can be caused by the following factors.
1. There were some programs running in the background when installing Service Pack 3, which may damage system files.
2. If the system is preinstalled by the computer manufacturer, the issue can occur since the same image to Intel-based computers is deployed on the computer which is non-Intel-based. Hence, the computer cannot boot up properly.
3. The CPU of this computer is AMD, which may have potential issue with IntelPPM service.
4. Outdated drivers and BIOS version.
At this time, let us try to resolve the issue in the safe mode.
Step 1: Boot into safe mode
======================
1. Restart the computer and start pressing the F8 key on the keyboard. On a computer that is configured to boot multiple Operating Systems, press the F8 key when you see the boot menu.
2. When the Windows Advanced Options menu appears, select Safe Mode, and then press Enter.
3. Log onto Windows by using the Administrator account or any user account with Administrator privileges.NOTE: In Safe Mode, your system display and Desktop will look and perform differently than in Normal Mode. This is only temporary. To go back to Normal Mode, we just need to restart the computer.
Step 2: Disable the IntelPPM service using the relevant command:
===============
1. In Safe Mode, please go to Start, Run, and type CMD. Click OK to open a DOS like command window.
2. In the window, please enter the following command:
sc config intelppm start= disabled
3. Press the Enter key to execute the command.
Step 3: Modify registry keys to disable the IntelPPM service
===============
1. Please go to Start, Run, and type REGEDIT. Click OK to open Registry Editor.
2. In the left pane, please locate the following key:
My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\intelppm
3. Right click the above key and choose Export. Please save the file as backup in .reg format. If any unexpected issue occurs, we can restore the registry keys.
3. Highlight the above key and double click the subkey named "Start" in the right pane.
4. In the open window, please change the value to 4.
5. Click OK to save the change.
6. Quit Registry Editor and restart the computer.
Please try the above steps and let me know the results at your earliest convenience. If there are any questions or concerns, feel free to contact me.
I look forward to your reply.
Sincerely,
Tony Gu
This happened to me today (automatic update overnight) and I have been going round for round with microsoft. While working with their support group, my pc bsod again and now my drive isnt being recognized as being bootable, so they immediatly say the boot-sectors on my drive is bad and they cant do anything about it. So I went into the setup menu and I've noticed that my drives aren't showing up as partitioned space, neither of them. Microsoft is supposed to give me a callback, but I'm not holding my breath. And I'm Damn sure that my drives aren't bad since they were fine last night.
Shashank Bansal [MSFT] wrote: This issue happens with 3311 build of XP SP3.
RC2 Refresh build 5508 does not encounter this issue.
It happens because KB948590 stops installation of SP3 version of gdi32.dll on the system due to file version differences.
In case you are already hittting the blue screen, please follow these steps:
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
Thanks
Shashank
Has anyone got an idiots guide to the above, I can boot from windows disk and get the DOS style prompt, how do we go from there, I am unfamiliar with how to continue from this DOS style screen. For info I cant POST, boo in safe mode or get 'last good known configuration to work' which I think is really bad of MS! Any guidance or link would be appreciated.
Swiftsnr,
What is the actual problem you are trying to solve? The old advice you quoted above related to a problem only in pre-release versions of SP3, and it is believed that the final public release does not have the problem that this solution was trying to address. Which version (build number) of SP3 are you trying to install, and what problem are you trying to solve?
Swiftysnr wrote: Shashank Bansal [MSFT] wrote: This issue happens with 3311 build of XP SP3.
RC2 Refresh build 5508 does not encounter this issue.
It happens because KB948590 stops installation of SP3 version of gdi32.dll on the system due to file version differences.
In case you are already hittting the blue screen, please follow these steps:
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
Thanks
Shashank
Has anyone got an idiots guide to the above, I can boot from windows disk and get the DOS style prompt, how do we go from there, I am unfamiliar with how to continue from this DOS style screen. For info I cant POST, boo in safe mode or get 'last good known configuration to work' which I think is really bad of MS! Any guidance or link would be appreciated.
The above worked exactly as expected, and has solved my GDIGetBitmapsizeBitsSize BSOD.
For idiots guide to XP Repair, start here: http://support.microsoft.com/kb/307654
Cheers
Neil
ned_bolton wrote: The above worked exactly as expected, and has solved my GDIGetBitmapsizeBitsSize BSOD. In which case, you must have applied an obsolete pre-release version of SP3, as the publicly released version does not have this problem.
rdhw wrote: ned_bolton wrote: The above worked exactly as expected, and has solved my GDIGetBitmapsizeBitsSize BSOD. In which case, you must have applied an obsolete pre-release version of SP3, as the publicly released version does not have this problem.
If only Microsoft had made a clearer distinction between the "beta" versions of SP3 and the final version. Given them a different name, for example.
- Can you elaborate on what to do here, I'm lost. Please email me at
djhyde@verizon.net
Thanks!
~Dan - Can you please elaborate on this, I have the same error, but I couldn't quite figure out what to do. Please help me, email is djhyde@verizon.net
Thanks!
~Dan Hyeguy wrote: Can you please elaborate on this, I have the same error. The same error as what? Please be more specific. There are over 60 preceding posts on this thread and no-one can tell what you are referring to.
Shashank,
You seem to be knowledgeable about SP3 issues, I am running Micrsoft XP Professional on a DELL tower. After having my wireless setup with linksys (which is working fine), and then updating to SP3, my USB ports are no longer being recognized for my iTunes, iPhone, my external drive, my webcam.
ALL worked before w/o issue....I am not sure what I need to do if I'm missing firmware or if my BIOS needs to be reset.
Can you assist?
Bob
There are a few things that Sp3 did not do well.
With power off disconnect every thing. And check the connections. And reconnect the mouse and keyboard to the ps/2 ports with an adaptor. A cheap 10 powered hub might be at fault here. You did not specify which devices you are troubleshooting.
Certain dsl adaptors do not work with Sp3 until there device drivers are brough up to date.
1) First reffer to your printed manual or one download from Dell to make sure your USB bios setting are turned on for both plug n play OS. and Usb ports are on and usually set to high speed.
2) a) Download this file and run it. You might need to uninstall higher versions of dot net.
To get USB devices working. If you can move your Keybopard and mouse to the PS/2 ports using an adaptor And disconnect all your other devices
b) www.support.microsoft.com/kb/309531
Apply the above kb to show hidden system files and folders
c) Click on your "my computer icon"
Navigate to this folder c:\windows\inf"
Right click on USB.inf and then click on install.
Reconnect your devices one by one. Untill something faults.
Certain older key drives may not have a unique serial number. And plugging two of the same device in may cause problems.
navigate to this link to troubleshoot the rest of your devices
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3832188&SiteID=17
http://support.microsoft.com/default...b;en-us;310575
http://support.microsoft.com/default...b;en-us;314634
Since some one pointed out about the ACPI being buggy. The answer is here. Depends. Usually the MB manufacters instll manual will have the answer here. With out ACPI dual core procs will not detect. Not will quad cores. Loosing out on there added functionality.
Hopefully this helps out
Keith
could you possibly tell me where to find this file that fixed your computer, or have it to email to coronalvrr@hotmail.com? I am having what sounds like the same problem you had. I have a compaq with an AMD 3100+ processor. I installed xp sp3 and now my computer won't boot up.
Randallhow do i start it off the xp disk?
- Hello Shashank,
I thought you might be able to help i get the message "The parameter is not valid" at the command prompt once i type the message.
Thanks - Hi I have exactly same error message will it be possible to explain in easier terminology to sort it out i am unable to understand the procedure you mentioned above. Help is appreciated. Thanks in advance
Hi I have exactly same error message will it be possible to explain in easier terminology to sort it out i am unable to understand the procedure you mentioned above. Help is appreciated. Thanks in advance
Santosh84, the "same error message" as what? What are you referring to? This is a long thread and your posts are not sufficiently clear. Please define your problem precisely. Unless you quote the previous text to which you are replying, we cannot tell to which you are referring.
Robin Walker
