alisvolat - Thank you thank you thank you!!

We have run into this problem several times when upgrading MOBO in systems, in particular when going to an Nvidia chipset. It has been most frustrating, and up until now, we wound up redoing XP from scratch, because we had no solution. I knew there had to be a "simple fix", and someday we would find it.

Would like to know where you found this answer...

Renaming that file allowed the repair to continue, just like you said. Now I got to go and clean up the mess from trying to remove drivers.....

Did I say thank you? Your fix prompted me to join TS immediately.

Al S. in Colo Springs

I have sort of the same problem, but when i put it my xp pro disk (dell reinstall) and then press r, it says at the bottom grey bar:scanning 19087 MB disk at location 0 on bus 0... it does that for about 21 hours, and its still going. What should i do?

is it an OEM windows disk, or a recovery disk? You can also rename the intelppm.sys file from dos, or safe mode with cmd prompt if you can get that far. If your machine is automaticly restarting, press f8 when its booting and disable automatic restart should be an option, then try booting it into safe mode. see if any of that helps

Its a Dell SP1 Pro Reinstall disk. I cant get past the boot screen. It looks like everythings fine, then blue screen of death!! How do you get into dos with xp? I am in the process of creating a disk with the ultimate boot cd for windows. Would this avoid the bsod? then i could do some work on fixing my computer.

Alisvolat
Can you give me the steps you ve done at a repair option?
C:\windows? that where i am having the trouble.
mine it shows the logo of emachine then the logo of xp pro. keeps going back to emachine then xp pro, then goes black. if i try to format from a xp cd at the last step of finalizing installation it goes black.
help please.

I'm sort of relieved to know I'm not alone with this BSOD. Mine started yesterday after I connected my iPod to update. I hit F8 during restart but starting in SafeMode didn't work. However, when I selected the option to Restart Using the Last Settings that Worked, I was able to get back to Windows. Somewhere along the way my Norton Internet Security became corrupt (auto AntiVirus wouldn't load), so I had to uninstall all my Norton products and then reinstall and run live updates.
I tried Windows System Restore, but each one failed (conflict with Norton for setpoints?). I periodically got the BSOD when trying to shut down as well as at startup and once when trying to remove iTunes using Windows Add/Remove programs.
What seems to be working right now (knock wood) is that I went to RUN and entered msconfig. First I restarted using the Diagnostic Startup. Good startup; no blue screen. Then I just sat here, shutting down and starting up, each time adding another component. First I added the System.ini, then Win.ini, and next Load System Services. All went well -- no blue screen at startup or shutdown.
Then after disabling all the items in Startup, I began checking them off, one at a time, manually shutting down and restarting after each one. When I got to LifeDrive Manager (for my Palm Pilot), I got the BSOD. I unchecked it and restarted -- all is OK. I've already removed iTunes and reinstalled. Tomorrow I'll uninstall LifeDrive Manager and reinstall. Will also run a complete backup, just in case. Gradually I'll start plugging in peripherals and adding more startup items.
Not sure this is a permanent solution, but at least I'm back in business for the moment. Sure sounds as if a driver became corrupt.
(Dell Dimension 4700, Pentium4, 3.0Ghz, 2.5 GB RAM, 80 GB harddrive; 18.1 GB free)
I'll be back if it turns out my success today was just a fluke.
Mary Ann

Whenever you get a crash, are you actively sending the crash information to Microsoft when you are presented with a message, "The system has recovered from a serious error"? If so, what response are you getting?

>>Whenever you get a crash, are you actively sending the crash information to Microsoft when you are presented with a message, "The system has recovered from a serious error"? If so, what response are you getting?<<

I clicked on "send error report." Then I got a Microsoft page that told me that there wasn't enough information to figure out my problem. It told me to go into Control Panel | System | Advanced | Startup & Recovery and click on "settings" and then at the bottom set it to "kernel memory dump". Presumably if I get the BSOD again, it will collect the information needed for Microsoft to help with the problem. Touch wood, it's been two days now and I haven't had another episode (after at least 6-8 BSODs over the course of two days). After I posted my message, I also went in and removed the AOL Spyware program because it occurred to me that I kept getting a message that it was blocking some low level problem. Since I have Norton Internet Security it seemed likely that it might be a problem. I'm still selectively loading items at startup, but at least for me things seem to be working well.

Did you also just recently install AOL version 9.0VR (for Vista Ready, but runs on XP too)?

>>Did you also just recently install AOL version 9.0VR (for Vista Ready, but runs on XP too)?

No, I'm running AOL 9.0SE and WinXP Pro. I haven't knowingly made any upgrades to AOL. I'm keeping the free AOL for my email addresses; otherwise I'm using a wireless modem (ethernet connection) for Internet access. I'm not sure whether they recently did any upgrades on the program or not.

I'm having a similar problem on a server with server 2003 service pack 2 version 5.2.3790. This is the bug check message 0x1000007e (0xc0000005, 0x80908071, 0xf78ea874, 0xf78ea570). This is on an HP Proliant server ML 350 G5, 1 Gig mem, 20 Gig HD. We image these, so there's not much in the way of frills for software except office and a few other things. Any help would be really appreciated. Thanks.

Andy

Amdarden,

BTW only few people likes reading 3 pages in order to understand your problem. Open a new thread for a new problem as you are not owner of this thread. If you post your problem here, all the persons involved in this thread will get notification message. You are welcome to prvoide more information to resolve the original problem.

Will do.

Am

Thread closed due to number of replies. It just gets confusing when there`s more than one poster asking for help with a BSOD issue.

Each poster who has a BSOD problem should open a new thread in our Windows OS forum.

Regards Howard