[PCWorks] Updated XP SP3 info and possible patch release to fix the main issue with it
- From: "Clint Hamilton-PCWorks Admin" <PCWorks@xxxxxxxxxxxxxxxxxxxxxxxx>
- To: "PCWorks@xxxxxxxxxxxxx" <pcworks@xxxxxxxxxxxxx>
- Date: Sat, 12 Jul 2008 05:49:40 -0500
Of all people, I've (and I guess maybe a few other "civilians")
been working with M$ to find a fix for what has been dubbed the
"Reboot loop/BSOD issue" on SP3 for XP. The issue affecting
many, causes the PC to reboot in an infinite loop during the XP
splash screen just before the GUI loads. If the option to
automatically restart on system failure is DISABLED, at that
time a BSOD would appear instead of the reboot loop. The BSOD
parameters could be different for each user, there were
numerous different STOP error parameters on the BSOD screen.
Some were able to get a minidump from it, others (such as
myself) never got any .dmp files from it. Because they were
different, there was not much success in analyzing the .dmp
files. This is happening on both Intel and AMD platforms, but
the issue on AMD platforms was usually caused by another issue
which has a fix.(1)
Months ago I was aware of the potential issue, but I installed
it anyway since I knew I could always remove it. Since I did
end up having the issue, and since no one else was doing it,
I've been keeping a journal of sorts chronicling day-to-day
updates on what I've found that worked for some and not others
in efforts to find a fix for the issue. I had a particularly
stubborn case since all the temp fixes and workarounds that I
had been keeping notes of and listing that worked for others,
never worked for me. What also was strange and problematic is
that particular fixes that may work for some people, was not
working for others, they either had to try other workarounds,
or nothing at all worked and they just had to remove it.
There was about 3 months of testing, which involved requesting
users do things such as disabling/enabling integrated LAN's,
3rd-party controllers, integrated FireWire/1394, toggling
numerous BIOS settings, and replacing dozens of SP3 version
files with the SP2 versions (*usb* and firewire files), etc.,
etc., I was keeping updates thereof. Throughout this testing,
I've been keeping in contact with 2 MS employees on this issue
sending them these updates regarding the success/failures of
the workarounds and temp fixes on which I've been keeping
notes, what's worked for some, what hasn't worked for others,
and their PC configurations. Again, to try expedite a fix for
the issue.
The main problem at first appeared to be a problem with USB
binaries. But we finally narrowed down the issue to a 1394
timing issue, specifically regarding the sbp2port.sys file--I
reported on the main thread that I replaced this file with an
SP2 version and that did NOT fix the issue, I deleted the file
and it DID fix the issue, and I had been posting this info to
the main thread at the MS forums, but I could not
**permanently** delete the file. (Some may remember my
post on the list about the difficulty trying to delete the
file). I was finally able to permanently delete it. The
problem with deleting it (or renaming it), is when you do,
any FireWire devices fail to work, (so I had intended to
create two batch files for when I needed to use my FW HD;
one that would rename the file back to its default name,
then after I was through with the HD, clicking the other
which would rename the file back to some other name.
I'm not sure how this issue and deleting the file can affect
PC's without FW, or if the file is even present on PC's
without FW. Some users without FW ARE having the issue.
But the patch does more than just replace that one file).
After several days of testing without the file, I was confident
that fixed the issue. Deleting the file was the only thing
that worked for me. Since, I have yet to receive any reboot
loops or BSOD's upon GUI loading.
I emailed one of the MS employees that had been monitoring the
main thread at the MS forums, and to which I had been sending
the updates, and told him that it looked like I finally found a
working fix for myself. He said that they had been working on
a patch regarding this file (and apparently other files or
associated configuration settings). Shortly after I emailed
him and told him of the final success I had with the file's
removal, he had a patch for it that he sent me. I installed
the patch, and while it was indeed listed as being installed,
and may have changed other things, it DID NOT install a new
patched sbp2port.sys file. We didn't know why. I unpacked the
file and the "_sfx_manifest_" in it file did have it listed. I
then postulated that the existing file must have to be in the
System32/drivers folder, because few (if any at all had been
reading the posts) are going to have deleted or renamed that
file, and MS would have created the patch for the use of the
majority of users that still had the file. So I put it back in
the folder and installed the patch again, this time it worked.
The new file was added, v5536 replacing SP3's 5512 build
release version of the file.
He said that SP3 will not be released again (at least not for
this issue), so it will remain build 5512. I'm to email him
sometime next week to inform him whether or not I'm still
having success with the patch, and IF so, the patch will be
released to the public in about 2 weeks as it "goes through the
release channels", again, IF I still continue to have success
with it. I'm confident I will because I was getting the BSOD
about 98 times out of 100 when I would start the PC.
So any of you wanting to install SP3, wait a couple more weeks
until this patch is released. He said I was "the only one"
that has the patch and asked me not to give the patch out to
anyone.(2)
A search for KB955356 (which is what it was called for me)
shows interesting results:
http://translate.google.com/translate?hl=en&sl=ja&u=http://blogs.dion.ne.jp/wogota_cif_exa/pages/user/m/article%3Farticle_id%3D7246255&sa=X&oi=translate&resnum=2&ct=result&prev=/search%3Fq%3DKB955356%26hl%3Den%26lr%3D%26newwindow%3D1%26safe%3Doff%26sa%3DG%26as_qdr%3Dall
(Near the bottom). Notice that the URL for the link is (yet)
not active, http://support.microsoft.com/kb/955356/.
FAIK the KB # could be changed when released.
(1) Since I'm on a Intel platform, I don't know if this patch
will work for AMD systems that the "intelppm.sys hack" does not
fix. If any of you install SP3 on an AMD system and have this
main issue, and the patch doesn't work for you or you want to
try this fix instead, details on it can be found at
http://forums.microsoft.com/TechNet/showpost.aspx?postid=3607412&siteid=17 ,
and several other threads. If the exact fix isn't on that
thread just search for intelppm.sys at the forums and you'll
find it. I'll ask the guy from MS about the patch and AMD.
(2) There are some OTHER issues regarding SP3. Ones that
affected me I was able to fix. I do not have the internet
problem that either causes a slow down or loss of connection,
or the one where the Device Manager becomes UNPOPULATED. I did
HAVE the internet slow down problem, but I toggled some new SP3
Services regarding the internet from auto/manual/auto/manual
and it's ok now. Others are still having the issue with no fix
found. This is also at the MS forums and there may be fixes
for it now.
The other issues I know about are the missing address bar
option on the Taskbar. MS has REMOVED that from SP3! They
claim it's a "legal issue" but that's BS because the address
bar is still there on Vista SP1. There are several hacks of
putting it back, plus a program that will put the address bar
there if any of you use the address bar on the Taskbar. If any
of you install SP3 and want the address bar, just post that to
the list and I can tell you what to do.
Another issue I had was IE crashes from urlmon.dll. I was able
to fix it, if any of you have that problem just post it to the
list and I'll tell you what to do.
Another I had was seeing an annoying warning in IE: "This
page is accessing information that is not under its control".
I was able to fix this by going to Tools > Internet Options >
Security > [whatever zone] > Custom, then enable "Access data
sources across domains". This is some new (and did I mention,
annoying) security feature of SP3.
Still yet another I had is with the XP MMC (Microsoft
Management Console). Most don't even use it. It's the type of
interface you see when doing a defrag, that interface is also
used when accessing numerous other XP areas. You may get a
"snap-in" error if you use a 3rd-party defrag program. "MMC
has detected an error in a snap-in. It is recommended you shut
down and restart MMC". Then you're given 3 options: to quit,
ignore for session, ignore it permanently. You can just click
to ignore it for that session, or ignore it permanently. This
is caused by the new version of the MMC on SP3 and snap-ins
that still use the old SP2 version. There is a reg fix for it,
but it didn't work for me. If any of you see this and want to
try the fix, just ask on list and I can reply with the details
on it.
Another issue is with (no surprise), Norton, and they have a
fix for that at their website. I THINK this is the one that
causes the DM to become unpopulated, or, it may be the one
regarding numerous bogus entries in the DM regarding the
LAN/NIC controllers or cards. I don't use Norton so don't
recall all the specific details on this, but it can be found at
their website and at the MS forums.
Another is with sleep and hibernate, info on what to do about
that is also at the forums. I don't use those features so I
didn't have it.
Finally, another problem is some can't get updates from the
update site after installing SP3. I never had that issue, but
I think it has to do with an obsolete script version or Windows
Update Agent. M$ has this info at their site (and at the
forum) on how to fix that.
The main SP3 area at the M$ forums can be found here:
http://forums.microsoft.com/TechNet/ShowForum.aspx?ForumID=2010&SiteID=17 .
If you have any problems they can probably be found there, or
post it on list and I may be able to tell you what to do.
-Clint
God Bless
Clint Hamilton, Owner
http://www.OrpheusComputing.com
http://www.ComputersCustomBuilt.com
=========================
The list's FAQ's can be seen by sending an email to
PCWorks-request@xxxxxxxxxxxxx with FAQ in the subject line.
To unsubscribe, subscribe, set Digest or Vacation to on or off, go to
//www.freelists.org/list/pcworks . You can also send an email to
PCWorks-request@xxxxxxxxxxxxx with Unsubscribe in the subject line. Your
member list settings can be found at
//www.freelists.org/cgi-bin/lsg2.cgi/l=pcworks . Once logged in, you have
access to numerous other email options.
The list archives are located at //www.freelists.org/archives/pcworks/ .
All email posted to the list will be placed there in the event anyone needs to
look for previous posts.
Other related posts:
- » [PCWorks] Updated XP SP3 info and possible patch release to fix the main issue with it
