Slashdot Mirror


XP SP3 Crashes Some AMD Machines

Stony Stevenson alerts us to new information on the XP SP3-induced crashes that we discussed a few days back. Jesper Johansson, a former program manager for security policy at Microsoft, is maintaining an ongoing log and support site for users affected by any of several problems triggered by XP3. Machines using AMD hardware, particularly HP desktops, seem to have several modes of failure; others affect Intel machines.

16 of 267 comments (clear)

  1. Re:Frist Pr0st by Anonymous Coward · · Score: 5, Funny

    Bah, you beat me to it. I was trying to get it, but I have SP3 installed on my computer and it crashed >.

  2. Rename the topic to say INTEL drivers on AMD systm by Joe+The+Dragon · · Score: 5, Informative

    Rename the topic to say INTEL drivers on HP AMD systems is the cause.
    The topic you have makes AMD look bad.

    Why is HP useing the same basic image for there amd and intel systems?

    What other driver bloat is in OEM systems?

    Is INTEL coding there drivers to mess up AMD systems?

    AMD legal should take a look at this.

    I have SP3 running on my AMD right now and it's works 100%

  3. BAD_POOL_POINTER, HID problem, standyby problem by PerfectSmurf · · Score: 5, Informative

    I installed SP3 Sunday and three problems immediately cropped up that I haven't seen in the years since I first installed XP. First is a stop, BAD_POOL_POINTER 0x00000019 (0x00000020,0x8a231120, 0x8a231158, 0x1a070000). Second is a problem with the HID service not starting. Third is that PaintShop Pro (V7) now cancels all attempt to enter standby mode. Sigh...

    --
    I smurf everything and everything I smurf is perfect.
  4. Re:Hey, wait a minute! by TheSHAD0W · · Score: 5, Informative

    Apparently it's mostly AMD machines that had some Intel-specific drivers installed.

    Easiest way to fix the problem, before installing SP3, open a CMD window, and type "sc config intelppm start= disabled".

  5. Re:Typical Microsoft by mrbluze · · Score: 5, Funny

    i still don't see where slashdot covered how feisty fawn fucked hp tablet owners That wasn't a bug, that was a feature!
    --
    Do it yourself, because no one else will do it yourself. [beta blockade 10-17 Feb]
  6. Limited impact by Mostly+a+lurker · · Score: 5, Funny

    As I understand it, this only impacts Windows XP users who are running computers with AMD or Intel processors. There is no evidence of SP3 introducing problems on XP machines with alternative architectures.

  7. Re:Only one crash by BlueCollarCamel · · Score: 5, Funny

    My machine works fine with SP3, not a single problem. How's two anecdotes for ya, bitch?

    --
    1&1 - Cheap domain and web hosting.
  8. Re:Typical Microsoft by truthsearch · · Score: 5, Funny

    Wow, you're right. With the Linux HP tablet market being about the same size as the Windows desktop + laptop market I'm surprised it didn't get more press.

  9. Re:Only one crash by PacoCheezdom · · Score: 5, Funny
  10. Im waiting.. by rossdee · · Score: 5, Funny

    I'm waiting for Service Pack 3.11

  11. Re:Wintel Conspiracy by harryjohnston · · Score: 5, Informative

    It may also be worth pointing out that (according to TFA) folks had this exact same issue when service pack 2 came out, so it isn't as if HP's configuration wasn't already known to cause problems.

  12. There is only one problem with this theory by zappepcs · · Score: 5, Insightful

    Quite simply, if MS wanted to keep customers they would create a product with zero problems (or as close as they can get) and push it out at a VERY competitive price. That is how the marketplace is supposed to work. When your namebrand is trashed, you have to compete extra hard. MS seems unwilling to do this, or at least has failed to show that they are trying to do so.

    That might just be bad business decisions on their part, but whether it was malicious or stupidity does not matter. In either case the end result is that MS loses more customers. Nobody wanted to hear that MS was losing or soon to be dead a year ago when predictions were rife, but here it is, in your face. MS is consistently failing to either impress or produce quality product. The dragon^H^H^H^H^Hcathedral is near death... is it time for the penny market to celebrate?

    Not on your life, it will be time to celebrate when the dried bones of the dragon are used up as party favors. Until then, it is time to keep competing aggressively, and nothing short of that will do. Competition, not patents, drives innovation. Innovation will bring us secure computing at home. A kind of secure that behaves friendly to the end user.

    Now, am I bashing MS for pleasure? No, it is because MS products are in their deathbed and nothing short of a complete restart will get them out of it. It does not appear that MS will do that. There is nothing in current or near future activity that shows MS will do anything different from what got them in the death bed to start with. The beast is dieing. There is nothing more to say.

    Call that a troll if you will, but the truth hurts sometimes. Do I want it to die? NO! Emphatically NO!!!! Without competition, quality dies. Would I like to see MS slide into a comfortable second place? Yes.... and the reasons are simple, just ask any Linux fanboi for them.

    SP3 failed utterly in the face of the current market that MS faces. There is NO excuse for that in business. If you believe the art of war extends to business, MS deserves to be beheaded ungracefully. That is how business goes, so don't bother telling me that I'm a troll.

  13. Re:Hey, wait a minute! by Anonymous Coward · · Score: 5, Funny

    You see, that's why Windows will never be ready for the desktop: Until you get rid of all that command line gibberish, I'll never be able to install it on my grandmother's computer.

  14. Re:Ulterior motive by WaroDaBeast · · Score: 5, Funny

    No, no, and no again. SP3 is meant to prepare XP users to an unstable environment.

    --
    "The body may heal, but the mind is not always so resilient." -- Deus Ex: Human Revolution
  15. Stop code 0x0000007E is not a new problem by fragMasterFlash · · Score: 5, Informative

    Anyone who build Windows XP images that are rolled out onto both AMD and Intel machines should have long ago learned about the stop code 0x0000007E perils that come from the intelppm driver. The root of all evil here is that processors are not plug and play devices as far as XP is concerned and their associated drivers are hardcoded to start at boot time. Why the hell Microsoft has not taken the time to update intelppm.sys to check for a GenuineIntel x86 Family XX Model YY Stepping ZZ ID before touching HW specific registers is a mystery to me (I hope the conspiricy theorists amongst you will regale me with much food for thought).

  16. Re:Frist Pr0st by dotgain · · Score: 5, Funny

    Sorry I'm late. I was playing an mp3, drove the latency right up.