0x0000007E after XP an SP2 or SP3 upgrade on AMD PC

Mesh computers seem to have made their AMD PC's using Intel CPU based Sysprep'ed images. Customer today with a Mesh PC who finally upgraded to Windows Service Pack 2 got this message:-
A problem has been detected and Windows has been shut down to prevent damage to your computer...
Technical information:
*** STOP: 0x0000007E (0xC0000005, 0xFC5CCAF3, 0xFC90F8C0, 0xFC90F5C0)


The symptoms fitted everything on
KnowledgeBase Article 888372 but it seemed their solution didn't work.

Quoted from the Microsoft website it said
Change the "Start" Value data box, to 4"

I realised it may be a mistake so I modified it to
So it changed the current controlset rather than a backup one and it did the trick. I guess it was a typo on their part.


Update: 02 August 2006

Seems that on May 16, 2006 Microsoft have removed this solution from the Knowledgebase, now simply stating that they do not support this configuration.

Thanks Microsoft. I don't understand though. I don't mind if you put disclaimers stating that this fix might stain your washing blue or kill your puppies and that it wasn't Microsoft's fault in the first place that some 13 year installed your PC while playing with his whatevers... But for the love of all things holy, why remove a potential solution that may help people bring their systems back online??

OK, rant over :)


Update: 11th April 2007

Summary of contributed solutions

  • "booted up using Bart PE, went in and load the System hive and I can only see the ControlSet001, but I changed the Start value to 4 anyway and restart, and it worked !!!"
  • "renamed C:\Windows\system32\drivers\intelppm.sys to intelppm.no-sys and it booted just fine."
  • "I was able to finished repairing Windows after i deleted the Intelppm.sys in system32\drivers"
  • "it's easier just to rename or delete intelppm.sys from the recovery console."

And I believe the most elegant solution is this one from 5th April 2007 :-

"boot with the Windows CDROM and start the Recovery Console on the interested partition. then type 'disable intelppm' to disable that driver from running. Reboot"

Update: 13th May 2008

Unbelievably it appears that Microsoft have had the same problem with Windows XP Service Pack 3. Another solution has cropped up which I'm actually little annoyed I didn't think of. So if you have an AMD processor and you think you could suffer from this problem (particularly if it is a HP PC!). At the command prompt type:-

sc config intelppm start=disabled
and it should disable the redundant intelppm driver.

Update: 14th May 2008

Another solution. At the command prompt:-
reg add HKLM\System\CurrentControlSet\Services\Intelppm /v Start /d 4 /t REG_DWORD

Kudos to Jesper Johansson's blog for that little gem, and he seems to be keeping close tabs on the situation and has comprehensive page regarding this issue - I recommended a visit if you are suffering from the Windows XP SP3 0x0000007E blues(creen).

Update: 20th May 2008

Hilarious, almost two years to the day (May 16 2006-May 6 2008) after Microsoft removed the solution from KnowledgeBase Article 888372, the resolution is now back! (and updated to say SP3). I'm guessing they couldn't deal with the potential fallout of n thousand people complaining that their computers won't boot/endlessly rebooting. Or maybe they took my rant seriously! One can only hope :)



You've just given me a very successful conclusion to a very frustrating evening. Without your post of MS's old article details (which has resolved my issue BTW) - I was staring a rebuild in the face. Quite why they always do this I'll never work out, suffice it to say this isn't the first and wont be the last time that the strange behaviour of Microsoft have ruined an evening.

Thanks again,

Your welcome Jon, thanks for letting us know :)

I cant stand calling Micrsoft since they try to charge you for every little single thing. Its solutions like this that save from the hastle of windows and gets back to the important workflow.

The above solution worked well for me. Thank you. Also most people that have this error have ATi based videocards, which is why I would take nvidia any day of the week.

My error message was similar:

0x0000007E 0xC0000005 0xBA2224B0 0xF789DFC4 0xF789DCC0

but the source TURNED OUT TO BE a corrupted vsmon.exe file -- a Zone Alarm component had gotten corrupted. This supports Microsoft's contention that a bad driver COULD cause the 0x0000007E error.

I had a new system-board installed and it had a bad NIC. In addition, the WinXP event manager in safe mode indicated that vsmon.exe [Zone Alarm's "TrueVector Internet Monitor"] had exhibited numerous failures prior to the time the system ultimately failed. The driver had become corrupted.
Later, when it tried to run, the corrupted driver caused the BSOD, producing the above error. I do not know the source of the corruption. However, I ...

  1. Uninstalled the software that was using the corrupted driver (ZoneAlarm);
  2. Searched for and destroyed any registry keys referencing the offending driver
    (ZoneAlarm cleaned itself up nicely, leaving nothing to delete), and
  3. Rebooted Normally

The BSOD disappeared and I was back up in Normal Mode. A system with this 0x0000007E error should show, in Event Manager in Safe Mode [control panel -> administrative tools] for a few days PRIOR to system failure, a bad driver failing DAYS before the system actually went down.
Another forum listed "VSO software" for a DVD burner being the culprit of the BSOD - ptapi.sys. I suspect that the failure could result from ANY bad or corrupted driver.

The Event Manager should indicate the origin of the offending driver that needs to be removed or fixed.

This was such a simple solution to such a frustrating problem, I can't (actually, I can) believe Microsoft would provide, then remove the solution to this. I just upgraded from an Intel to an AMD motherboard/CPU and this described my problem and the solution exactly. THANK YOU!

Wow, thank you so much for the solution,

I've tried everything and this fix my problem of bsod after I tried to upgrade a computer from XP home to XP pro. It finished the update step in window and then restart, and then it keep the restart loop with the (0x000007... blah blah error).

Anyway, I booted up using Bart PE, went in and load the System hive and I can only see the ControlSet001, but I changed the Start value to 4 anyway and restart, and it worked !!! No more BSOD and Window XP Pro keep on updating my system !!! Strange that Microsoft removed this solution...

THANK YOU, this fixed saved me even more time than I had already wasted on it. And what is up with M$ taking down helpful KB information? I had a similar issue with them doing that when a server crashed and they wanted $245.00 for the solution they deleted off their website.

Thank you very much, this is very very good, save much my time. Regards, Kevin.

All this helped.

I just want to say thanks this post steered me in the right direction. I was getting a *** STOP: 0x0000007E (0xC0000005, etc. after replacing my ASUS P4S8X P4 2.533GHz. motherboard with a MSI Athlon 64 X2 5200+ motherboard. It blue screened every time on boot right after the XP logo. I tried to set the HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Intelppm START value in the Registry to "4" using a Bart PE boot CD and editing the HIVE but I'm not sure it took. I then went in and renamed C:\Windows\system32\drivers\intelppm.sys to intelppm.no-sys and it booted just fine. However other issues caused me to have to do a Repair install from the Widows XP CD and it replaced intelppm.sys and the problem occurred all over again until I deleted intelppm.sys (still had the intelppm.no-sys copy). So I now asked MicroSucks how to prevent any future Repairs from replacing intelppm.sys. I do not believe intelppm.sys is necessary with an AMD processor. To bolster this belief, my AMD Sempron Laptop running Windoze XP does *not* have intelppm.sys installed. (When I boot my Laptop into Windoze, it's usually running Linux.) Stuff like this is exactly why I like UNIX/Linux so much more and only run Windoze as an evil necessity due to some applications I need to use.

Strange thing, i only have IntelIde instead of Intelppm but i've changed the "start" to "4" restart and it still won't work... Anyone could enlighten me? I was upgrading my P4 to AMD X2 and i got this error message everytime i start the Windows

Finally... I was able to finished repairing Windows after i deleted the Intelppm.sys in system32\drivers surprisingly :) Thanks runpcrun

Thanks a lot!!!!! The same problem - image with symantec, made on Intel pc, moved to AMD pc. You helped me a lot and this solution is going to help me more by the time i do my work!!!! Thanks!

Phew, after 6 hours of increasingly bad language and desk abuse and countless dead ends this fix has got me back into my PC. Many many thanks.

I LOVE YOU!!! Wow Everything works again :). I Successfully deployed on to my AMD pc... SWEET!!!!!!

These type of fixes are real gems. Thanks !

WHY DID MICROSOFT REMOVE THIS!? I first stumbled on to the kb article and noticed they didn't have a solution, then found this site some hour later. Thankfully this fixed everything!

Can't thank you enough, we just imaged 10 intel machines and restored them to AMD chipsets.

Glad to be of help - I would not like to have to reinstall 10 computers and then find out there was a 5 minute fix!

Thanks for this. I have been trying to upgrade to SP2 since it came out. Came accross your site today had a go at updating to XP SP. Edit the reg as described and hey prest Ive updated my machine. Thanks Microsoft for not helping. Thanks to this site.

My error was 0x0000007E (0xC0000005, 0xF784C750,0xF7A23430,0xF7A2312C) You saved the day!! Thanks, Elio

Just wanted to say "THANKYOU!" as this fix worked for me on my Compaq Presario SR1519. Actually, as someone mentioned, it's easier just to rename or delete intelppm.sys from the recovery console. But I would not have worked this out without your help, so thank you!

I have to add my thanks to this list. A recent motherboard failure made me reconsider my options, and I decided on the same motherboard brand, but with an AMD processor. To my delight, the swap worked without having to reinstall windows. Giddy with my success, I went ahead and *finally* decided to put SP2 on my XP Pro. BSOD ensued. I too, ended up at the microsoft page you mentioned, and recognized the 'FU for having a non-Intel processor' nature of the article. One little registry change has saved my computer. Thanks!

"To my delight, the swap worked without having to reinstall windows. Giddy with my success..." That was your problem right there - When you think you've done everything correctly, and you 'have your coat on and are ready to leave', Windows has the habit of ruining your night! Glad you fixed everything in the end

After seeing the MS KB article, I thought "well its possible to do (build SP2 image on Intel and deploy on AMD) since somebody did it on SP1." Fortunately you archived the solution for all of us thankful AMD adopters. Many thanks for hosting this solution.

Hi, I just wanted to say thank you - I've just had to swap out a motherboard from an Intel to an AMD - and had exactly this problem. Sorted with the help of people here. Brill Martin

There's another solution which worked for me: boot with the Windows CDROM and start the Recover Console on the interested partition. then type 'disable intelppm' to disable that driver from running. reboot and you are ready. This solution is better when you are forced to move the harddisk to an AMD machine and you can't access the old intel one. cheers.

Thank you man, you saved me a lot of time on AMD PC.

I just wanted to say THANK YOU! I used in safe made: "renamed C:\Windows\system32\drivers\intelppm.sys to intelppm.no-sys and it booted just fine." I had alos changed from an Intel processor to AMD when I had to change my mother board. I had backed up my info, but it was nice not to have to reinstall. This could also help those who may otherwise lose valuable data. Felix07

Much thanks to everyone again. This fix was a life saver. DFK

I'm a tech and this fix was a real lifesaver for me. I was about to pull my hair out of my head. Upgrading a board for a customer and this stupid little file was the whole problem. I did the disable intelppm from recovery console and also deleted it from the system32/drivers directory and it started installing windows as it should have. Microsoft was no help here. Thanks for the solution. This is one I won't forget!

Hello, I am currently having this problem and none of the suggested solutions mentioned in this thread seem to be working for me. Thus I am either doing something wrong or am missing something. I swapped hard drives on two HP desktop computers. My older one has an AMD processor and the newer one an Intel processor. The older hard drive from the AMD machine worked fine in the new Intel machine. However, I am having the same nightmarish blue screen of death boot error in the older AMD machine with the hard drive that came from the Intel one. Thus I am sure that this whole Intel image won't work on an AMD machine thing is my problem. However, changing the start value in either CurrentControl location didn't work. Renaming the driver didn't work. Deleting the driver didn't work. And I don't have the original Windows CD so I can't try the restore idea (although the recover feature is stored on the D drive of this computer having the problem - would that work?). Could someone please walk me through, step-by-step, the detailed solution to this problem? Keep in mind I am not a tech or even a computer expert. I know enough to be dangerous, which is exactly what got me in this predicament. Any help is greatly appreciated. I want to get the rig up and running so I can sell it. I do not want to have to take it somewhere and throw good money after bad. Thank you all in advance!! Mac

Please disregard my last message (above), I finally solved my own problem. Like an idiot I had used the wrong System Restore disks which kept putting that stupid drive in; after using the correct restore disks, the system booted up and worked like a dream! Thanks anyway.

Man thats good. Thank you. Just replaced an Intel 865 board with an MSI K9NBPM2 AMD AM2 with Sempron. Did the usual 0x0000007B mergeide.reg hive load trick (google it, if anyone hasn't found it) but the system still gave 0x07E (0xc0..05,...). Removed all startup items and renamed intelppm.sys in safe mode and it booted fine next go. Champion post to all contributors. Rob.

Many thanks - disable intelppm worked like a charm to get my intel based sysprep image onto a new amd\nforce 4 machine. kudos

Hey Dan! Thanks! I haven't been able to have SP2 until this point, I couldn't use photoshop cs3, i was forced to use cs1, and now I am starting a college class in CS3 so I worked really hard to fix this, and this information was what I needed. Thanks again man

Had to join the throngs in thanking you for this post. Rename intelppm.sys saved me! Thanks very much! Greg

I had to rename the intelppm.sys file. Using disable intelppm did not seem to work for me. This particular issue (Intel motherboard to AMD motherboard upgrade) was very difficult to diagnose as there are a number of solutions or suggestions on the Internet which do not apply to this problem. Now I have a stop 0xfc error but at least I'm a bit farther :) Thanks!

It is amazing to finally be able to upgrade to Service Pack 2..just by deleting/modifying one stupid file.... intelppm.sys I was just about to give up yet again and found this solution...thanks...Halelluia!!!!!

As another tech guy who had drawn a complete blank while trying to upgrade a client's computer to SP2, many many thanks for this article. One thing I would point out is that it is no use pre-empting the issue and looking for intelppm.sys in the SP1 system as it is not there. The registry entry is there however. Intelppm.sys is added by the SP2 upgrade and it is this coupled with the registry entry which triggers the problem. Similarly it is also of no use setting the registry entry to 4 before the upgrade as it will be reset to 1 by the SP2 installation. Thanks to all for this gem. Rob.

Dan, you have no idea what this fix means to me. You have literally saved my life, lol. Thank you very much.

I tried to upgrade my Mesh Athlon PC to SP2 a couple of years ago and got the BSOD... reverted back to SP1. Tried again last year armed with a bunch of troubleshooting and MS Hotfix tips, but same problem... reverted back to SP1. Tried again today and got the BSOD, finally came across this article, applied the "4" registry fix and... success!! Many thanks for posting this informative solution, I can now install apps which are SP2-only.

renaming intelppm.sys to dud.misc worked perfectly thank you so much :') i nearly cried after a repair install resulted in the bsod-reboot-loop again, thank you so much!!!! <3

THANK YOU! THANK YOU! THANK YOU! You guys saved my back-end from the fire. I sure am glad Apple OSX migrates aren't this difficult! Al

The 0000007e (xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx) error happened after installing SP2 on XPHome using the restore disk (Cicero-futureshop)motherboard MS-6741(MSI). I edited the reg file as instructed in Safe Mode and rebooted. Worked like a charm and I didn't delete any files, so maybe skip the deleting intelppm.sys or renaming part of the operation until you try rebooting after the registry correction first. Just my 2 cents. Thanks a bunch guys! Mikeyd

I just wanted to say "thank you" for this post. after a motherboard replacement from Dell the system would not boot to safe mode/etc. I ran a repair from XP SP2 and realized I couldn't boot again. After much headache I also received the error "The file Asms on windows XP SP2 could not be found...basically telling me that the machine was not seeing the CD drive. I ran their fix and I am back in business. Beats having to restore. I could have done that 6 times over on how much time I have spent but the data on this machine had to be restored. Here is the link for the Asms files. Hope this helps someone! You guys are lifesavers Houston, Texas

Thanks for this simple and effective solution to what seems a well known issue to all but the mindless twits at Microsoft. The problem occurred last week when I upgraded from a P4 system to an AMD 5600+ system. I followed your advice then and it worked like a charm. Today I installed XP SP3 and the problem re-occurred. This time I deleted all occurrences of intelppm.sys from my system and here I am to tell the tale. Thanks once again. Cheers, Peter J

Ironically, the main reason for moving my OS off of a Gateway was because of unsolved BOSD after SP1. Then when I moved OS to an AMD 3000+ MOBO STILL BOSD when upgrading (SP2). Assumed it was the same issue. Spent 3 days in frustration before finding this thread which led to solution: renamed intelppm.sys to intelppm.bak while in safe mode. Did the trick!!! THANK YOU, THANK YOU, THANK YOU!!! (Guess the Gateway BOSD was something else because it was an Intel MOBO.)

Thank you very very much!

I just installed the official (read: non-beta) XP SP3 on my HP Pavilion a1600n AMD-based Media Center PC and had this exact same issue, stop 0x0000007e. The originally proposed solution from Microsoft for fixing SP2 installs back in 2006 still holds true now in 2008 with SP3, assuming you can get to safe mode (I could): In regedit: "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Intelppm" Change the "Start" Value data box, to 4" After rebooting, the PC reboots like there was never a problem. Thanks for the heads up.

Same exact problem here with a AMD based Compaq Presario SR-2039X after downloading and installing SP3 for Media Center XP, stop error 0x0000007E. The fix in the post above worked great for me also, took about 2 minutes. Thanks!!!!!

While starting a system repair to (hopefully) overwrite a viral infection of winlogon.exe and an associated dll, I received the install error "Setup can not set the required Windows XP configuration information," (support.microsoft.com/kb/316425) halting the restore process just after the setup files were copied to the hard disk.

Rebooted. Tried many solutions. Safe mode would not boot because I was locked into the repair cycle. Regular boot threw a 0x07e error as described here. Using the 'disable intelppm' console command resolved the supposed 'hardware conflict' and allowed the repair to continue successfully.

System is a HP Pavilion a1267c running an AMD 3800+ Athlon 64 on an 'MS-7184 VER:1.0 ROHS' motherboard with latest BIOS at time of post; repairing Windows XP Media Center 2005 from SP3 back to SP2. Many thanks to the author and contributors of this article.

It appears KnowledgeBase Article 888372 (which your "Update: 20th May 2008" left off the "2", though the link is right) is still wrong, as it still suggests changing ControlSet001 instead of CurrentControlSet. This was "reviewed" 28 May 2008, and it is on Revision 6.1.

So these appear to be the best three solutions, if one can boot to Safe Mode:

reg add HKLM\System\CurrentControlSet\Services\Intelppm /v Start /d 4 /t REG_DWORD


sc config intelppm start=disabled


cd /d %systemroot%\system32\drivers\
ren intelppm.sys intelppm.non-sys

...and that last file extension I pronounce as "nonsense".

The boot to Recovery Mode (from an XP startup disk) can be complicated by having to load SATA and RAID drivers from a *^&^$& floppy disk, particularly on systems that didn't ship with a floppy drive (or leave room for one). If you have one, I suggest using a Vista startup disk to get to Recovery Mode, as it allows for other locations for those drivers.

Greg Kirkpatrick

Thanks for the info Greg, and the KB link has been corrected.

I am an intern technician at a computer repair shop and I ran into this problem. I could not sleep that night because I was dreading having to transfer the client's personal data, reinstall XP, then reload the data and *some* programs. This fix has saved me hours upon hours of work and headache, and my boss was very pleased that I was able to find this solution. (I goofed up, did not save a backup or ghost image before repairs, etc...) Thank you very much. Dylan Houston

I performed: "If you booted into safe mode you can run "sc config intelppm start= disabled" but it didn't correct the boot failure. After a Safe Boot, I ran Regedit and searched for all "intelppm" entries and Renamed those in the left column by prefixing "DISABLED(space)" and Edited the ones in the right column and prefixed ""DISABLED(space)" During the Regedit, I saw several entries that matched "sc config intelppm start= disabled" but many of them were unchanged. Probably many of these didn't have to be changed, but it worked. The PC boots and runs okay now. It would probably be much faster to just rename or delete the intelppm entry in the System32\Drivers folder. Don't you wonder how Microsoft can be so consistently clueless? All they really have to do to make XP SP3 work is check for an Intel CPU and not enable intelppm if it isn't present. What a bunch of jerks! Thanks for your help. Bob Petrie

Just to add that i have had the same problem time and time again with customers machines (PC shop) ... leading me to back up and reinstall from scratch. Thanks to you , customers will now be more likely to get a system back "in tact" (as it was prior to motherboard replacement), I take my hat off to all concerned ! Thankyou, Martin in Wales

I cant help but notice a common medium for this blue screen error. Most of them are HP pc and have Windows xp service pack 3 installed. Just boot into safe mode and uninstall service pack 3. Problem fixed.

I am having this problem today with the XP update. I can't get it to do anything but the blue screen. It won't boot into safe mode period. I can even get it to boot in safe mode to the command prompt so i can try some of the above suggestions. XP came preloaded and there are no recovery CD's and i never made a boot disk (dummy!). Any suggestions????

Dan White I just want to kiss you... and I swear that I'm a straight man. Thank you for solving my headache. Given I had already my sysprepped image, the solution that worked for me is to delete the intelppm.sys and voilâ... magical solution. THANKS THANKS THANKS, Matt

You are perfect. Thankkkkkkkkkkkkkkkkkkksssssss. Long live :)

I have all the same symptoms and error code (0X0000007E) and an AMD processor (not HP computer) and got the BSOD on install of SP2 (including the relooping boot which I was able easily stop). I've read Johannsson's webpage, and many other articles HOWEVER, in the registry I am unable to locate the "intelppm" entry in either ControlSet001, ControlSet002, or CurrenControlSet. I did a full search of my hard drive from Windows for this file and came up empty that route as well. Entered the command prompt (sc config intelppm start=disabled) simply to see if it would work and I just wasn't finding the file. That failed too. I need to get SP2 installed for several of my other programs to work. Has anyone else experienced this (no intelppm file) or have any other ideas I can try. ALL the symptoms and error codes I have fit this problem to a tee yet I can't fix it. I'm stuck in SP1!.... Any help would be greatly appreciated!! Thanks again, CJ

If you do not have Services\Intelppm in your registry anywhere then I'd say you have a different 0x0000007E error.

I'd read the Microsoft page on the 0x0000007E error very slowly and carefully and work through your problem.

Thanks so much, Booting from a windows CD going into repair console and using disable intelppm has just for me running again on a repair install that failed after I took a hard disk from an intel PC and put it in an AMD based one. I was at the point of backing up all the data and then formatting.

tahnks a ton!! intelppm workeed like a charm!!

thank so much!! i almost formatted my PC...

Thanx a lot people, disable intelppm solved my problem permanently... THANX!!!!!!


Mate, You're a deadset legend, removed intelppm.sys loads of times before no problem but this particular machine just wouldn't play the game. Tried your solution and bingo were on! Cheers Aussie Trev

no worries mate but I think putting 'Aussie' before your name is kinda superfluous - deadset legend gives the game away!