If the PC is set to automatically reboot on a start failure -- as most are by default -- it reboots endlessly, often so quickly that the user can't interrupt the process and enter what's called "Safe Mode" in Windows, a last-ditch way to sidestep the normal boot process for troubleshooting purposes. So Microsoft's blaming HP? It sure sounds like it. Yesterday, a Microsoft spokeswoman confirmed that the company was aware of the reboot problem, and pinned responsibility on the computer maker, but didn't name names.
Although Computerworld asked for comment on Monday and an HP spokeswoman said Tuesday that the company was investigating, no one from HP had followed up as of end-of-day on Wednesday.
However, HP has posted a document to its support site that shifts the blame right back to Microsoft. During Windows startup, computers with AMD processors may experience a blue screen error. If that is, in fact, the case, the endless rebooting is Microsoft's fault, not HP's. Is the intelppm. Those same users claim that inserting a USB flash drive or connecting another USB-based storage device before booting solves the problem.
Johansson noted that some users had seen error messages that indicate their crashes are video driver-related. How can I stop the endless reboots? To break the chain, you may first need to halt the automatic restarts.
Microsoft Corp. The document also showed that the "endless reboot" problem some users have reported after installing XP SP3 was neither unanticipated or new; Microsoft updated the document on the same day it released the service pack, and the company indicated that the same thing happened nearly four years ago when it rolled out Windows XP SP2.
On Monday, Microsoft confirmed the document's conclusions. Knowledge Base Article , last updated May 6, spelled out an error message that stops a PC's boot process -- and, depending on the machine's settings, may make it repeatedly reboot -- after installing SP3.
The fault, said the Microsoft document, is in the Windows XP image originally installed on the PC by the computer manufacturer. The best thing for anyone to do, and what I do, is subscribe to Secunia alerts. They will send you emails when there is a new MS update or patch out.
Then go to the WU site 1 , select "Custom", and check out what all is available. Go to the mitigating factors area on the info pages. They will list who really needs the patch, and usually even some workarounds to do in lieu of the patch. A big majority of the patches are not even needed if you use a firewall, something that everyone should do. I use a hardware firewall AND a software firewall. Then there's a huge amount of them that are not even needed if you have a certain Service disabled.
That's something else everyone should do; disable all Services that you don't need. If I find out that I do indeed really need a patch, then and only then do I install it. And I don't install anything else around that time so if my PC does a meltdown I'll know what caused it and I can remove it or do a restore. MS's constant "handholding" and "hijacking" of PC's is something I will not tolerate.
My PC is my PC, I own it, and I will not have someone or something dictate what is best for me when they know absolutely nothing about what they are doing, nor what I have installed or not installed, what I have enabled or disabled, my type of computing--all of which is what really dictates what you need.
Regarding restore, XP's restore is very limited. I think it's once per day, but you can at any time do a manual backup. I do this before I install anything, you can name the backup anything you want so it won't overwrite the previous one for that day. That way if the install screws up something, you can do this full restore.
It can sit in your Start Up folder and that's how it automatically creates a full backup on its own. It does this in a couple of seconds and shuts down. Nothing is running in the background and you don't even know it's happened. Investigate, research, use your heads, and you decide whether or not a patch or update is necessary for you.
I haven't tried that macro yet with SP3, I'm sure it will work, but there's the problem with SP3 trying to keep putting Auto Updates on automatic. The Services have to be on "manual" for the macro to work. If those Services are on manual on SP3, it will keep setting them to automatic.
I'll have to check into this further. Then you'll be able to try again without having to remember everything you typed! You can't do it via right click like everywhere else, you have to do it from the "Edit" menu in IE's toolbar. Another thing that's screwed up is the email notifications.
There are no more "Click here to view the post alert details", and even the text in the post is gone from the emails! All I'm seeing in them is the unsubscribe link, and "If this reply answers your question, please visit the link above and Christian Helmrich wrote: Clint D. Do you remember? Already emailed Shashank about it. Worked fine. Then installed the Radeon card before that I was using on-board SiS graphics.
Because the card is quite old, XP was able to automatically install its own drivers, i. Microsoft Corporation ". After a reboot the PC froze while showing the XP boot logo. No automatic restarts though, most likely because I disabled automatic reboot. But no BSOD either. Just a complete lock-up at every reboot. Safe mode works! And: the Radeon worked fine when I tested it under SP2 a few weeks ago. Remember that I said earlier that I can't duplicate or reproduce the problem anymore!
So when I installed SP My combo floppy drive media card reader was connected. But nothing was in it either. That reminds me of something strange that happened. I was getting BSOD's during the install and when the Desktop finally would go to load for the first time after installation.
I don't know if that means anything or not, but it may be worth noting at least. I have made some more tests. My PC also boots-up with the printer powered on. I tried disabling the Silicon Image controller by going into my BIOS and setting "Silicon Image Mode" to disabled, rebooted without my flash drive installed and it just went back to the booting loop. I was interested to read of your problems with the forum, as I am not experiencing any such.
Are you by any chance running any cookie-blocking software? That might cause such problems. Chris confirmed there are indeed problems here. It's an unrelated issue that forum folks are investigating. Interesting, thanks for that input. Yesterday I posted that the issue with me went away and I could no longer reproduce it.
Today when I started my PC, it was back! No, I emailed Shashank again and still no reply. I would guess they have absolutely no idea what's going on nor any way of fixing it, so they're going to ignore it. I find it very hard to believe that in "all of their testing" they never came across this problem. Yesterday I mentioned something about those of you using USB mice.
Emily, hopefully you're looking at this thread now, please let us know what software you "cleaned up" that seemed to help at first. Is your mouse USB? Most mice are USB these days, but not all of them. Jesper I think it was maybe you that asked a couple of times about my 0x0A error and if I was sure about it. My post above from about 2. I checked again then and it indeed was the 0x0A stop code. I just had to go to the store and I shut off my PC. When I got back and started it, I got the boot problem once again, and it was still 0x0A.
Looks like it may happen to me more so turning on the PC after it's been OFF, more than just a restart. Eric I didn't notice that was your posts! So it's edited now to reflect that]. You say to use at least a 2gb flash drive, mine was 2gb and that method did not work for me, so unfortunately that's a not a fix for all I guess it's just for the ACPI BSOD error type like you said. It could depend on whether or not the flash drive supports boot-from.
Some USB drives do, some don't. Eric do you know if your 2gb and mb flash drives support being a bootable device? What brand are they? Eric this is worth putting on this thread:. I have two because I was using a wireless network adapter. I disabled both in the bios. So are you saying that in your case it didn't have anything to after all with the USB mouse? If so, that's not good news because we're back to square one since not everyone is going to have both of those controllers.
No commonality there, at least not as far as brand or dual LAN's go. Is the common factor behind the problems on this thread that you all have nForce chipsets on your motherboard? Have you tried updating the nForce chipset drivers direct from www. I believe he did, you probably haven't see it yet Getting confusing. Still awaiting input on that regarding the mobo's. I just shut down for about 20 minutes, started up the PC, no problem. There's nothing worse than an unreproducible intermittent problem.
Hopefully the rest of you can reproduce it each time with the same results. It's those of you that are apparently going to have to do the testing since MS has obviously abandoned us Since the time of this original post, MS has been working on this. Update 2 added]. Has that method worked for everyone? Even if I could still reproduce the problem I couldn't do this because my main HD is on a 3rd-Party Promise controller. Mine had a few files on it. We know another fix for some is a USB media card reader, the kind built-in to a printer.
Does this work for any of you using a stand-alone USB card reader? Update 1: This did not work for me. See Update 3 below. We now know it's not just with ATI video cards or integrated graphics, happens also with nVidia.
Update 3: Apparently this problem may not be due to hardware, or at least not limited to hardware alone and can be caused by software. We know that "Shamx" reported that Daemon Tools was apparently the cause of his rebooting issue. He removed it, and he has not had the reboot loop issue since. Update 4: Some have reported that the only way they could boot was to remove all USB devices! Update 6: We know that replacing the usbport.
At first this was a consistent fix for me, not anymore. Update 7: We know a fix that has worked for some is replacing the sbp2port. Did not work for me. Update 8: For me, a "consistent" fix has been removing the file mentioned above, but see details below. Update 9: This fix is still working and I found a way to permanently delete the file. Anything to add to that anyone? So, a riddle: what does all this mean, what are the commonalties among them? Those of you that have success with the external USB HD method or anyone , please try it with any external FireWire storage devices you may have.
Update 4: But it worked for me only once! Some may want to try and temporarily disable their single LAN just to see if that works. I tried disabling my LAN connection, as well disabling the FW controller, this did not work for me.
I guess that's it for now. I may come back to this post with edits and updates, so please watch it. Update 1, once again, more confusion and inconsistency today. PC would not boot. Apparently, possibly, a PC or least my PC has to be turned off for X hours in order to reproduce the problem. This was NOT the case several days ago when I could reproduce the problem just be restarting. When I turned it off yesterday briefly, no problems when powering it on again.
But when I started it twice after it had been off for more than 1. But today when I had it, it would seem that nothing would make it boot! So much for that theory working for everyone! That was the first time I had tried the CF card method, but obviously that method too will not consistently work to fix the problem. My PC was set to the main HD being the first boot device. So, that method as well is not a consistent fix! Update 2: I just shut my PC down for only about 15 minutes, and today that short duration DID result in the boot problems!
So, changing those mouse settings did not work this time , the inconsistency continues! I checked, again, what the first boot device was, and for some reason it was changed again to the floppy drive! Why it keeps changing back to floppy is a total mystery, that has never happened before! I'll be watching this area closely the next few days. But it's too early to tell if that's what made it boot because changing those mouse settings seemed to work earlier, but obviously they did not.
Update 3, Previously some have reported that changing their 1st boot device to their HD worked for them. As I reported yesterday about the first boot device being changed in my BIOS, well that also happened again.
Each time I disabled the other two boot devices, 2 and 3 with the HD 1st, and each time it was changed back to 1. Floppy, 2. HD, 3. So obviously if the PC won't boot, it's changing this area to floppy 1st, apparently due to a boot failure.
So apparently we can add that to the list of possible temporary in my case methods that work. I won't know if this is a definite temp fix method until I can duplicate it several times.
Update 4 , The external FireWire enclosure method is obviously not a temp fix for me. That method only worked one time and has not worked since! It boots normally without the power cord, and I'm able to boot into safe mode with the power cord plugged in, and then restart from safe mode and it starts normally. I'm talking about the power cord for the laptop that you plug into the wall. Update 6, At first t his was the only consistent fix for me, but ended up NOT working. See the 4th post on page 25 of this same thread for more info, and be sure to see the follow-ups after it for details on what else was tried.
Some have had success after replacing the sbp2port. I also tried disabling my LAN connection, as well disabling my integrated FW controller, this did not work for me. Update 8: 7- Deleting the sbp2port. But I have tried and tried everything, but I cannot keep the file deleted from my HD! Regardless of what I do, it keeps coming back. Note that not having this file on your PC may make your FireWire devices not work.
Update 9: 7- This fix is still working, see the URL above for how I was able to remove the file. See my 5th-8th posts on page 33 of this thread for details, and how I'll recreate the file if needed for FireWire.
I told MS about this and they should have a patch out released to the public in about two weeks, IF testing of a 'beta' patch continues to be successful. Sorry Clint D. Then install SP3 under the Sata setup in bios. Then got service pack 3 from windows updates and install restarted pc and put back my microsoft usb mouse and everything working fine now. My pc been stable now since last night not had one BSOD loop error.
I restarted my pc and turn off and turn on loads of times and no sign of my 0x0A5 stop error. I just doubled checked again disabled both network controllers in bios and get same error as above. So just go into the bios reenabled the network controllers choose start windows or safe mode pc fine and working again.
Was this post helpful? Evening Reaper, please do as sugguested. Each round of release candidates people that didnt try the download candidates or Rtm there was a post minium of 3 to 6 of people that forget how programs they added are designed to work. Including Sp2 user account control, not installing from a FULL adminstrator account or safe mode, always causes problems.
This includes software that leaves baited versions of Registery to install programs to. Or you have a mixture of errors that are difficult to diagnose. Sp3 doesnt not include drivers for sata. Since the image is designed around Adding to the complexity if SATA was include. We are here to help with Sp3 experiences, post experiences.
I've discovered that I can boot into safe mode with BOTH the power cord and the wireless mouse connected, and then restart from there and it boots up fine. So, I'm not convinced it's a power supply issue like the last support engineer thought.
Before I booted into safe mode, I did try booting normally with both power cord and mouse connected, and it hung on the Windows XP screen.
I didn't move the laptop hence not moving the power cord if the cord itself was a possible issue and rebooted into safe mode, then restarted. And it booted up fine. Automatic update download of SP 3 did the same thing.
It crashed my laptop All files , pictures , documents. Thanks a lot Microsoft!!! W R Castle - I encourage you not to do anything rash. There have been steps that most of us have been able to use to get our systems up and running. Have you tried any of these?
The phone support number is. Most users don't have access to an XP installation disc only a recovery disc. Nice to find out all of these "fixes" about 6 days late , and Microsoft knew about the problem all along. Eric sorry but I don't understand all of your post below.
What's that paste from a post by "1stKnight", what are they referring to about "do as suggested", what was suggested? Also, you said you used a 2gb flash drive on that other thread, but this one you linked to is 4gb. I don't see anything mentioning that it's bootable. So do you know if it's bootable, have you ever tried it as a boot device? Then, you said: " In my case it was the onboard network controllers, Marvell Yokon and Nvidia nforce network adapters.
If you disable both in windows in Device Manager no errors. Is all of this correct, no typo's? If so, then how do you explain this? Now you're saying that your USB mouse is not causing you any of the rebooting problems. Just wondering if you can explain all this, sort of "bottom line" it for us to see if we can conclude anything from it.
The first time I tried SP3 I used the registry tweak to get it from the Update site, and it was a disaster. It took forever to download it and install it, and the PC never booted again after that and I had to start all over and that's when I hooked up the new HD. I think I might have installed drivers first, that I can't recall. Eric wrote:. See all the blue areas. Please take a look and comment if you have any. Does anyone know how we can make a post a sticky post?
Or make a post editable by everyone? So Emily, is your mouse USB? I don't understand what you mean by "power cord". If the mouse's power cord isn't connected, it won't work, right?
At least mine is that way. I agree, I don't see how the receiver's power supply would have anything to do with this issue. This would be more of a possibility if your mouse,even being hooked up, has ever not worked at one time after getting into Windows. Regarding what you said on the other thread: "Why shouldn't MS employees post problems here? Meaning, that's the first time I've ever seen any employee of any company post anything problem wise in their own forum.
You win the Darwin award this week. Tried to boot up from the Original WinXP disk, but cannot work boot from it even though the original disk. Can you give us some more detail on exactly what went wrong? What was the error code? What exact HP model are you using? Your problem sounds exactly like the one that afflicted certain ASUS motherboards, but if you have stock HP computers it does not seem likely that you have that motherboard.
I have no clue why some people don't just follow directions. What color is the sky in your world? And he or she harmed you in what way? While I agree it's not a good idea to not backup for years, insulting people and name calling is not the answer, and it's the act of a limited mind. Perhaps you're one of the Socially "Developmentally Disabled". And you need people skills. If you don't have anything constructive to add to this thread that will HELP people, then go wallpaper the Interstate.
Mikey does this have anything to do with this thread topic? Sounds like it does not. If it doesn't then it would be best to start your own thread. And when you start another thread you're going to have to give more info than that. Like exactly why it won't boot and what is happening, error messages, is the drive in which you placed the XP CD the first boot device, etc. If this does have something to do with this SP3 reboot loop issue, then sorry, and please explain your post more.
Hi everyone this is my first post so just bare with me. Now I know you all have had this rebooting problem, even I have and I have noticed that AMD processors are not the only ones affected, my Intel Celeron computer also went through with the constant rebooting but I found a way around it. Now after I installed SP3 the comp asked me to reboot and started to reload, then the rebooting problem occured, so what I did was restore back into SP2 via safe mode safe mode wouldn't load until I pressed ESC.
So then I thought maybe its a program creating issues this happened to my Windows 98SE. So what I did was I uninstalled program after program on my comp until I reach Daemon Tools, now I don't know whats wrong with Daemon Tools but after I uninstalled that and reinstalled SP3, SP3 started to work, the rebooting problem was gone.
So for everyone it might be Daemon Tools like me or another program that is causing issues. So do what I did, trial and error with uninstalling programs and then reinstalling SP3 and see what happens. That is interesting. Can you please explain exactly what you had installed, something on this page? Developers are in short supply.
Here are the skills and programming languages employers need. Windows Do these six things right away after you finish setup. The painful shame of owning an Android phone. If you use Google Chrome, you need to install this now.
Best iPhones : Which model is right for you? Best keyboard Because you deserve better.
0コメント