XP SP3 Cripples Some PCs With Endless Reboots

[stinger608]

Originally Posted by Parker

Hey now, look at you! 8,477 freaking posts!?!?!??!?! You shouldn't preach what you don't practice..

JK!

Ummm, you better look again, I have 2,155 posts, well lets see now, 2,156 upon this post, and I have been a HL member since 1936

[Parker]

Originally Posted by stinger608

Ummm, you better look again, I have 2,155 posts, well lets see now, 2,156 upon this post, and I have been a HL member since 1936

Oh shoot! I was looking at the Points not your Posts.....

Well, wateva...

[screwballl]

4 systems with XP SP3, 2 of them with AMD and ZERO problems... there has to be something else causing this and I suspect it is not actually related to AMD. This is just a convenient excuse.

[JazzyJake]

Originally Posted by screwballl

4 systems with XP SP3, 2 of them with AMD and ZERO problems... there has to be something else causing this and I suspect it is not actually related to AMD. This is just a convenient excuse.

Perhaps...Also do we have any more info on these systems aside from AMD?
like OEM particular vs homebuilt?

[Panda Man]

SP2 did the same thing :P I actually slipstreamed the beta into my install CD, and it's gone without a hitch so far.

[Reloadron]

I have it downloaded, just sitting in a folder. Maybe tomorrow I'll pull the trigger and see what it does. Don't think I'll try it on the one AMD box I have.

Ron

[Lead Head]

On another certain forum, the problem was found to be because of OEM installs. It only happens to OEMs that use the same OS image for both their Intel and AMD systems. Apparently an Intel power saving driver is to blame. Had the OEMs thought about this and had two different images, none of this would happened.

For once its not microsofts fault, but somoneon elses

[Reloadron]

Originally Posted by Lead Head

On another certain forum, the problem was found to be because of OEM installs. It only happens to OEMs that use the same OS image for both their Intel and AMD systems. Apparently an Intel power saving driver is to blame. Had the OEMs thought about this and had two different images, none of this would happened.

For once its not microsofts fault, but somoneon elses

That's right. I remember reading that also. Hmmm, nothing OEM around here. I saw refrence to OEM and AMD processors.

Ron

[Gig-O-Ram]

I was checking on updates, and I got offered SP3. I was this close to taking it, but I thought I would check around here and see what people had to say about it first.

I was just basically trying to find out if it would be worth it to update to the new SP. But I also wasn't sure if I needed to do any system driver updates or something like that first, like going from SP1 to SP2. M$ says that it has cumulative updates, including updates that have already gone out (unless I misunderstood them). Does that mean I'll get new AND older updates together if I take it?

[Reloadron]

Originally Posted by Gig-O-Ram

I was checking on updates, and I got offered SP3. I was this close to taking it, but I thought I would check around here and see what people had to say about it first.

I was just basically trying to find out if it would be worth it to update to the new SP. But I also wasn't sure if I needed to do any system driver updates or something like that first, like going from SP1 to SP2. M$ says that it has cumulative updates, including updates that have already gone out (unless I misunderstood them). Does that mean I'll get new AND older updates together if I take it?

The fact that it was offered through Windows Update or Microsoft Update means it should have no problems installing. When the wife ran it at work her machine was current and there were no issues. Any patches & fixes within the cumulative update that are already installed won't be installed.

Worth a read:

Release notes for Windows XP Service Pack 3

Ron