Has Asus acknowledged XP SP3 issues with its boards?

Comdrpopnfresh

Golden Member
Jul 25, 2006
1,202
2
81
My circumstances are a bit complicated, but I own a socket 939 Asus A8n32-SLI Deluxe motherboard, which I found out through chance web browsing basically gets infinitely looped restarts at the XP splash screen after installing SP3. Supposedly all the iterations of xp- home, pro, and mce are affected. The "fix" is plugging in another drive, keeping a usb flash drive or device like a hub plugged in, and in some cases, enabling the parallel port in bios can alleviate the issue. However, as soon as you remove the flash drive, the reboots happen again. Any blue screens screaming of APIC incompatibilities or lack there of are an indicator of the problem. Before the usb work-around some people on forums said how they tried to do fresh installs of sp2 with no luck. Are the compaqs, and oems that use put both the intel and amd APIC-handling codes on their systems having problems too? Luckily there is some mechanism built in to the live-update to keep the possibly affected masses of people from having to deal with this.

I've been feeling as of late that Asus' internal reconfiguring in the company has been at the loss of consumer care. My circumstance is that my board died over a month and a half ago. It took me nearly half a month, with the original warranty still intact, to even get through to someone who could deal with my circumstances. And from there, I was told I'd be called back. Checking in the following two weeks yielded nothing. I'm a student, who at the moment has the use of a laptop. So the way I figure it- if they're not responsive to me when I have time to sit on the phone, repeating the same story all the way up the ladder and sliding over through offices and departments (which given the plain english of "We will call you back shortly" meaning I shouldn't even have to), then they've just made it abundantly clear they don't want my future business.

Sorry for the venting- so is anyone having this issue?
Mine died before the sp3 release, and I can't even load to bios, so I have no clue if I would be. My guess is it is because of the Nvidia SB200 on the mobo. I believe this model motherboard was one of the first AMD 939s to be given two bridge chips as opposed to just an MCH- mainly to allow for the full 16x by 2 SLI lanes. Wonder if they'll release bios for a fix. If my board worked, I wouldn't exactly be waiting with baited breath- I think it has been over a year since they released a non-beta bios. Does a 939 product fit into EOL where support is no longer required?

ACTUALLY
- I just realized why the third tier, what have you, manager/overseer didn't get back to me!! When I finally reached him and explained how I had already done 2 rmas over the last 1.5-2 years, and the board died every 6-9 months of similar symptoms like clockwork, and how I wasn't very enthused about getting a 4th board of the same model... he told me explicitly that he personally purchased, owned, and currently used around 3 systems revolving around that board- and how it was 'if not the most, one of the most stable and issue-free boards produced by ASUS in the 939 generation.' If my timetable is right, I think that week I should have been initially called back was the release of the voluntary-download ISO for the SP3 update by microsoft. Maybe he is awaiting a call from someone in the company about how his 100's of dollars and time investment had been bricked. Irony is something- I can tell you that much.

If they'll only give me the same board as an rma replacement- maybe I can get them to toss in a flashdrive for me...
 

Comdrpopnfresh

Golden Member
Jul 25, 2006
1,202
2
81
The only affected motherboard (besides amd-based hp and compaq oem desktops) seems to be the A8N32-SLI Deluxe. I'm guessing the problem only surrounds boards with 16x sli functionality (not heard of problems with the one nforce4 dfi lanparty though). Here's a link to a chart of the breakdown of Asus motherboard models for various chipsets. http://usa.asus.com/products.a...delmenu=0&share=txt/60 . Supposedly, some people have developed scripts to delete the intel APIC driver on startup to put an end to the reboots- so no need to keep usb things plugged in. However, without a fresh install of xp, a few people who used the script have reported problems with mce functionality (possibly around drm), and it may be attributed to windows thinking a hardware change has occured. But the whole thing is screwy, as some people have also reported that simply trying a fresh install of sp2 created problems with APIC compatibility, leading them to do the whole f7 or f8 thing during install. I find that odd in particular b/c if the problem was induced by SP3, then one would tend to think that a different HDD or software base would alleviate the issue.
 

tcsenter

Lifer
Sep 7, 2001
18,893
544
126
Two different issues have been confirmed that can affect AMD64 systems.

One involves AMD64 systems shipped by an OEM with XP preloaded, primarily from Hewlett Packard but Mesh Computers has also been confirmed, where the preloaded software image was originally created on an Intel based computer then prepped for both Intel and AMD systems using a method that is unsupported by Microsoft. This can affect any AMD64 motherboard used by the OEM, not just ASUS.

There is a different issue that appears specific to the ASUS A8N32-SLI motherboard, resulting in a critical stop error and BSOD with the 'BIOS is not fully ACPI compliant' message. This is completely unrelated to the Intel processor driver (IntelPPM.sys) implicated in the OEM 'preload' issue mentioned above. The OEM preload related issue does NOT implicate 'BIOS ACPI compliance' as the problem. It reports a different 'general' stop error due to some unspecified hardware problem, usually 0x0000007E.

There has been no definitive solution reported or released for the second 'ACPI BIOS' problem specific to ASUS A8N32 Series. Some have reported temporary work-arounds but these have not proven effective in all cases and only amount to a short term fix, not a fully workable solution.

Even better, some systems may actually be affected by both issues. Mesh Computers not only used the A8N32-SLI motherboard in select gaming systems but is confirmed to have used the same unsupported OEM imaging method. lol!
 

tr1kstanc3

Senior member
Sep 25, 2001
361
0
0
my friend is having this problem with the same motherboard. we installed vista sp1 and it installed fine but windows xp sp3 does not work. the problems started occuring after he flashed to the latest BIOS.
 

ZootyGray

Member
Jul 4, 2008
37
0
0
SEE "SUPPOSED FIX" IN MY LAST POST BELOW - I deleted a lot of stuff that apparently is not really relevant. But kinda similar stories to this point.
DISCLAIMER - the "fix" is not my fix - just whatever I found - good luck.
------------------------------------------

This reminds me of a problem I had with ABITch (never again!).

It was about ACPI compliance - but older system - my board was PIC - not APIC. So I had to hit F7 and install as a "standard pc" - standard pc is a HAL - hardware abstraction layer. My problem was that ABITch was tek dumping AFTER MS had warned mobo makers about the new ACPI standards which included APIC. I did incredible research and then went to ABITch - they blew me off - I told them I would broadcast (hello!).

You have some other thing - maybe similar - but it's about APIC. It's not too clear - lotsa details not here - and this is really insane stuff.

F7 picks the best PC HAL. I tend to suggest that - but I don't know what you have or what has been done. This is pretty crazy stuff.

What was the original install - is that oem thing still on the hdd? Have you COMPLETELY FORMATTED the hdd - like lowlevel /write zeros /total clean /like brand new. That gives you a clean slate and I really don't know why you cannot just clean install XP from that clean slate beginning. So I am thinking there is some proprietary crap on the hdd (hahaha like is it somekinda ntel spyware?) maybe in a proprietary partition - you might be WAY BEYOND THIS already.

SEE "SUPPOSED FIX" IN MY LAST POST BELOW


I can only extrapolate from my own battle. This stuff is so tedious and crazy that people can't follow and think you are just nuts. It really sux.

BTW - The ABITch tek people told me they had "3 of these pc's" at home themselves and all were no problem. It's hard to find the floor that you can stand on and say - ok, this is square one - so communication is hampered because people don't know where to start, where you are, where the pc is, what's happening - so they placate and then blow you off.

That's all I got for now.

Somebody knows how to fix this - and I am interested because I learned much from chasing it before.
 

ZootyGray

Member
Jul 4, 2008
37
0
0
the following is a message about how to delete messages completely
- by one of our more patient and literate members
Take your Q
 

ZootyGray

Member
Jul 4, 2008
37
0
0
(EDIT - what a concept - sorry - I am new here - thank you for your enlightening words of infinite wisdom)

@Comdrpopnfresh

DISCLAIMER - the "fix" is not my fix - just whatever I found - good luck. :gift:


This link
http://club.cdfreaks.com/f3/wi...ead-244475/index3.html

Apparently the "proprietary hardware" is a piece of intel shrappnel software - it must be an active lil beast almost-virus-like thing (interesting) - it apparently installs on AMD systems even though there is no intel hardware - and that is described as a Microsoft issue. (that's handy) :)

Anyway disabling intelppm.sys is major part of the fix - read it yourself. They have a tool created by jesper to do this for you. - trying to goto that site revealed "certificate warning" about site masquerading bla bla bla but my pc hasn't been hijacked yet - I think. And jesper apparently has his own claims to fame. Beyond the intelppm.sys fix there is also the usb discussion. That's your job to figure out.

It's not clear if disabling the offending file intelppm.sys is an easy thing or if it requires using the 'tool'. If it recreates itself, the tool is required, I suppose. It might be tempting to 'cripple' the file by renaming it to intelsuxppm.s1s - BUT if it self-replicates from a registry command - wow - who knows. (some people have multiple instances of the file!)

I wonder why it is even there. (xfiles?) Someone said microslop was going to fix this sp3 issue with a patch. (??) Perhaps more will be revealed.

Good luck. :beer:
 

AmdInside

Golden Member
Jan 22, 2002
1,355
0
76
I have an Asus A8N32-SLI Deluxe and no problems here with SP3. USB is another matter but that occurs with any OS.
 

Capt Caveman

Lifer
Jan 30, 2005
34,543
651
126
Originally posted by: AmdInside
I have an Asus A8N32-SLI Deluxe and no problems here with SP3. USB is another matter but that occurs with any OS.

same here. No problems with SP3 and Asus A8N32-SLI Deluxe.
 

Comdrpopnfresh

Golden Member
Jul 25, 2006
1,202
2
81
Do any of you with the board have a usb hub connected, any usb devices connected, an external drive, or the parallel port enabled?
 

lizrdfishr

Junior Member
Aug 16, 2008
3
0
0
This is the fine help I got from ASUS for my A8N32-SLI Deluxe.
[Problem Description]
After installing XP SP3 I get a BSOD for a non ACPIP compliant BIOS. From the
forums I can see that there is no fix only work arounds. I do not have any USB devices I
can plug in to make this go away. What can I do?

The answer I got:
WTM20080723055597034 Re: Motherboard A8N32-SLI Deluxe [ID=RWTM20080723055597034-260] 2008-07-23 01:35:11
Hello,

We recommend rolling back to SP2. Otherwise you will need to contact Microsoft at 1-800-Microsoft.

Best Regards,

Rob
Level 3/Lead Tech Support Engineer
ASUS Technology
Phone: (812)-282-ASUS
RMA: 510-739-3777 opt. 2
http://www.asus.com
http://support.asus.com
http://livesupport.asus.com


 

Nocturnal

Lifer
Jan 8, 2002
18,927
0
76
I just installed SP3 on my ASUS A8N32-SLI Deluxe motherboard and I have not encountered any problems.

I have two more boxes at work that use the same exact motherboard and both did not have any problems after installing SP3.
 

QuixoticOne

Golden Member
Nov 4, 2005
1,855
0
0
ASUS / nVidia never even bothered to fix many of the ORIGINAL severe BIOS / driver / utility bugs on this board. I was one of the first people to get one when it was released. I've been through several BIOSes, several of which basically make major features unusuable, none of which quite work right.

NVIDIA apparently couldn't even be bothered updating their own NTUNE so as not to instantly blue-screen-of-death on what was at the time their premiere deluxe chipset on this board.

Installing Vista on this board was a nightmare of driver / BIOS hell and instability. LINUX just about the same.

Nice board hardware, horrible, horrible support, which is about what I expect from ASUS given all their BIOS bugs in most of their models that they never seem to fix even when they're pointed out and numerous subsequent BIOS updates occur even without fixing simple long known problems.

And the ASUS www site could HARDLY be worse if they tried. About 98% of the time I get an error screen about there being too high of a volume of traffic, try again later. Nice.