sr.sys installation failed SP2 crashes machine

I have 6 athlon xp emachines that will not accept SP2, possibly due to matrox mms drivers. (I tried removing the g450 video cards (agp and pci), the modem, and memory during 5-1 hour calls to microsoft. Matrox says they know of conflicts. Microsoft provided zero solutions, just multiple xp installs.

Maybe related, but 2 computers will not run system restore after two failed attempts to install SP1. NONE of my emachines willl accept SP2 and I am scared to keep trying SP1 because of time lost during past failures. All individual updates install fine, just SP1 or SP2 will give me a blue screen from which I have to reinstall windows xp home.

While I would like to limp by, time is not on my side as SP1 will soon be needed for windows updates. When System Restore fails (entry point not found) I have tried to install sr.inf and have provided a sy.sy_ file that the install program tries to work with. After 2 minutes I get "installation failed".

I have noticed the very kind help given to members in the past and I would really appreciated any insight you may have to either of these potentially related problems.

thank you!
ps: if you have any help that is more easily forwarded as a link, my email is <removed>l.com thank you again

-removed email address to prevent harvesting-Ron

 

Your AMD processors aren't 64's are they.

 

Thank you for a fast question. I tried to past a snapshot of the Belarc report here but I guess this form is limited to text.
xp home 2600
1.8 gig AMD athlon
emachines L7VMM2
Board: KM266-8235
Bus 133
BIOS: Phonix 6.00 PG 09-03-2002
all individual SP 1 updates took
the following SP updates did not install
tinued)
failed verification Q328310 on 11/9/2004 (details...) Reinstall!
failed verification Q329048 on 11/9/2004 (details...) Reinstall!
passed verification Q329115 on 11/9/2004 (details...)
no verification data Q329170 on 11/9/2004 (details...)
failed verification Q329390 on 11/9/2004 (details...) Reinstall!
passed verification Q329441 on 11/9/2004 (details...)
failed verification Q329834 on 11/9/2004 (details...) Reinstall!
failed verification Q810577 on 11/9/2004 (details...) Reinstall!
failed verification Q811493 on 11/9/2004 (details...) Reinstall!
passed verification Q811630 on 11/9/2004 (details...)
failed verification Q815021 on 11/9/2004 (details...) Reinstall!
failed verification Q817606 on 11/9/2004 (details...) Reinstall!
passed verification Q819696 on 11/9/2004 (details...)
failed verification KB821557 on 11/9/2004 (details...) Reinstall!
failed verification KB823182 on 11/9/2004 (details...) Reinstall!
passed verification KB823559 on 11/9/2004 (details...)
no verification data KB823980 on 11/9/2004 (details...)
failed verification KB824105 on 11/9/2004 (details...) Reinstall!
no verification data KB824141 on 11/9/2004 (details...)
no verification data KB824146 on 11/9/2004 (details...)
passed verification KB825119 on 2/12/2005 (details...)
failed verification KB826939 on 11/9/2004 (details...) Reinstall!
no verification data KB828028 on 11/9/2004 (details...)
failed verification KB828035 on 11/9/2004 (details...) Reinstall!
failed verification KB828741 on 11/9/2004 (details...) Reinstall!
passed verification KB833987 on 1/3/2005 (details...)
failed verification KB835732 on 11/9/2004 (details...) Reinstall!
passed verification KB837001 on 2/12/2005 (details...)
passed verification KB840315 on 2/12/2005 (details...)
failed verification KB840987 on 11/9/2004 (details...) Reinstall!

 

No I can see it is not a 64 bit processor. The reason I ask is that sp2 and the AMD 64 bit processors had some issues. I am still searching for anything related to your problem. Just to be sure, if you are trying to install sp2 from a disc try and make sure the info on the disc is not corrupted since it won't install on all of those computers.

bigc

 

Hi john263,

Have you tried installing sr.inf in Safe Mode? While you are in Safe Mode, I would also run System File Checker (go Start/Run, type sfc /scannow, hit Enter).

Nick

 

Nick, I did senf you a great big thank you yesterday. I emailed it directly to you not knowing my cookie setting was knocking my off line everytime I changed pages. I hope my note of thanks was forwarded to you. Sr.sys all solved and running thanks to you!

You are so knowledgable and explicitely helpful, I really do want to ask you my question as best I can.

Thank you in advance for any idea you may have
Second step. I trade for a living, have multiple homes, and have 4 athlon emachines (2-3 gig) at each location. All have onboard (varies, savage, nvidia) video, which is automatically disabled with I install 2 matrox g450 mms cards in each. I keep the computers clean (3 spyware), defragged (twice a week), and virus free (router & firewall) .They all perform flawlessly, UNTIL I try to install SP1 or 2. All the individual windows updates install correctly. (Now the updates get uninstalled each time I need to start over with xphome cd repair.)

The pattern is:
Computer is clean, with all windows updates installed Except SP1 or SP2.
I shut down ALL programs from msconfig, startup, taskbar, applications.
I remove the matrox cards and uninstall the drivers. (They can exist on windows drivers but need their own for maximum flexibility and to recognize mms.)
I install SP1 or SP2, and after it is installed I get two results:
1. Let windows restart normally and after the black windows green bars startup screen I get the blue screen memory dump with error code of:
stop: 0x0000007f 0x0000000d 0x00000000 0x00000000 0x00000000

If I try to reboot into safe mode the drivers stop loading at Mup.sys.

When I try enabling boot logging I cannot once I am in the blue screen as it will not boot, and it always goes to blue screen. I Can never get back.

I always take a xp home cd and restore windows to save my files. (I have well over 150 programs installed on each. I use PC relocator to originally transfer my files to each new computer. I always start with xp home, make the migration, then type in the windows code provided with each machiine. The size and complexity of my applications is why I do not just reformat and reinstall clean. PC reloactor will NOT (for me) migrate all files and setting on SP1 and SP2 machines. I must start with windows xp and ie6.)

When I compare the boot logs of two identical emachines, that run perfectly, the drivers loaded are almost identical, except the SP guinea pig has had the matrox drivers removed and boots with the on board viedo drivers.

Miicrosoft and Emachines senior support have exahausted themselves, and me too.
Machine A: Normal boot,g400 matrox, will crash on SP1 or 2, again when I view Mup.sys

not from beginning
Loaded driver NDIS.sys
Loaded driver viaagp.sys
Loaded driver Mup.sys
Loaded driver \SystemRoot\System32\DRIVERS\nic1394.sys
Loaded driver \SystemRoot\System32\DRIVERS\processr.sys
Loaded driver \SystemRoot\System32\DRIVERS\g400dhm.sys <--matrox
Loaded driver \SystemRoot\System32\DRIVERS\SlWdmSup.sys
Loaded driver \SystemRoot\System32\DRIVERS\slntamr.sys
Loaded driver \SystemRoot\System32\DRIVERS\Mtlmnt5.sys
Loaded driver \SystemRoot\System32\Drivers\Modem.SYS
Loaded driver \SystemRoot\System32\DRIVERS\RTL8139.SYS
Loaded driver \SystemRoot\System32\DRIVERS\usbuhci.sys
Loaded driver \SystemRoot\System32\DRIVERS\usbehci.sys
Loaded driver \SystemRoot\System32\Drivers\Imapi.SYS
Loaded driver \SystemRoot\System32\Drivers\AFS2K.SYS
Loaded driver \SystemRoot\System32\DRIVERS\cdrom.sys
Loaded driver \SystemRoot\System32\DRIVERS\redbook.sys
Loaded driver \SystemRoot\system32\drivers\ALCXWDM.SYS
Loaded driver \SystemRoot\System32\DRIVERS\fdc.sys
Loaded driver \SystemRoot\System32\DRIVERS\serial.sys
Loaded driver \SystemRoot\System32\DRIVERS\serenum.sys
Loaded driver \SystemRoot\System32\DRIVERS\parport.sys

Identical 1.8 gig athlon 2200 emachine B this log was taken before or after a crash and repair of windows xp home

I cannot tell where the conflict occurs, but the last item I can READ iduirng the boot is Mup.sys
from beginning
Loaded driver \WINDOWS\system32\ntoskrnl.exe
Loaded driver \WINDOWS\system32\hal.dll
Loaded driver \WINDOWS\system32\KDCOM.DLL
Loaded driver \WINDOWS\system32\BOOTVID.dll
Loaded driver ACPI.sys
Loaded driver \WINDOWS\System32\DRIVERS\WMILIB.SYS
Loaded driver pci.sys
Loaded driver isapnp.sys
Loaded driver ohci1394.sys
Loaded driver \WINDOWS\System32\DRIVERS\1394BUS.SYS
Loaded driver viaide.sys
Loaded driver \WINDOWS\System32\DRIVERS\PCIIDEX.SYS
Loaded driver MountMgr.sys
Loaded driver ftdisk.sys
Loaded driver PartMgr.sys
Loaded driver VolSnap.sys
Loaded driver atapi.sys
Loaded driver disk.sys
Loaded driver \WINDOWS\System32\DRIVERS\CLASSPNP.SYS
Loaded driver sr.sys
Loaded driver KSecDD.sys
Loaded driver Ntfs.sys
Loaded driver NDIS.sys
Loaded driver viaagp.sys
Loaded driver Mup.sys <<<<<<----the last item I view
Loaded driver \SystemRoot\System32\DRIVERS\nic1394.sys
Loaded driver \SystemRoot\System32\DRIVERS\processr.sys
Loaded driver \SystemRoot\System32\DRIVERS\s3gnbm.sys <<savage OB
Loaded driver \SystemRoot\System32\DRIVERS\RTL8139.SYS
Loaded driver \SystemRoot\System32\DRIVERS\usbuhci.sys
Loaded driver \SystemRoot\System32\Drivers\Imapi.SYS
Loaded driver \SystemRoot\System32\DRIVERS\cdrom.sys
Loaded driver \SystemRoot\System32\DRIVERS\redbook.sys
Loaded driver \SystemRoot\System32\DRIVERS\fdc.sys
Loaded driver \SystemRoot\System32\DRIVERS\serial.sys
Loaded driver \SystemRoot\System32\DRIVERS\serenum.sys
Loaded driver \SystemRoot\System32\DRIVERS\parport.sys
Loaded driver \SystemRoot\System32\DRIVERS\i8042prt.sys
Loaded driver \SystemRoot\System32\DRIVERS\mouclass.sys
Loaded driver \SystemRoot\System32\DRIVERS\kbdclass.sys
Loaded driver \SystemRoot\System32\DRIVERS\audstub.sys
Loaded driver \SystemRoot\System32\DRIVERS\bridge.sys
Loaded driver \SystemRoot\System32\DRIVERS\rasl2tp.sys
Loaded driver \SystemRoot\System32\DRIVERS\ndistapi.sys
Loaded driver \SystemRoot\System32\DRIVERS\ndiswan.sys
Loaded driver \SystemRoot\System32\DRIVERS\raspppoe.sys
Loaded driver \SystemRoot\System32\DRIVERS\raspptp.sys
Loaded driver \SystemRoot\System32\DRIVERS\msgpc.sys
Loaded driver \SystemRoot\System32\DRIVERS\psched.sys
Loaded driver \SystemRoot\System32\DRIVERS\ptilink.sys
Loaded driver \SystemRoot\System32\DRIVERS\raspti.sys
Loaded driver \SystemRoot\System32\DRIVERS\termdd.sys
Loaded driver \SystemRoot\System32\DRIVERS\swenum.sys
Loaded driver \SystemRoot\System32\DRIVERS\update.sys
Loaded driver \SystemRoot\System32\Drivers\NDProxy.SYS
Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS
Loaded driver \SystemRoot\System32\DRIVERS\usbhub.sys
Loaded driver \SystemRoot\System32\DRIVERS\flpydisk.sys
Did not load driver \SystemRoot\System32\Drivers\lbrtfdc.SYS
Did not load driver \SystemRoot\System32\Drivers\Sfloppy.SYS
Loaded driver \SystemRoot\System32\Drivers\i2omgmt.SYS
Did not load driver \SystemRoot\System32\Drivers\Changer.SYS
Did not load driver \SystemRoot\System32\Drivers\Cdaudio.SYS
Loaded driver \SystemRoot\System32\Drivers\Fs_Rec.SYS
Loaded driver \SystemRoot\System32\Drivers\Null.SYS
Loaded driver \SystemRoot\System32\Drivers\Beep.SYS
Did not load driver \SystemRoot\System32\DRIVERS\kbdhid.sys
Loaded driver \SystemRoot\System32\drivers\vga.sys
Loaded driver \SystemRoot\System32\Drivers\mnmdd.SYS
Loaded driver \SystemRoot\System32\DRIVERS\RDPCDD.sys
Loaded driver \SystemRoot\System32\Drivers\Msfs.SYS
Loaded driver \SystemRoot\System32\Drivers\Npfs.SYS
Loaded driver \SystemRoot\System32\DRIVERS\rasacd.sys
Loaded driver \SystemRoot\System32\DRIVERS\ipsec.sys
Loaded driver \SystemRoot\System32\DRIVERS\tcpip.sys
Loaded driver \SystemRoot\System32\DRIVERS\netbt.sys
Loaded driver \SystemRoot\System32\drivers\afd.sys
Loaded driver \SystemRoot\System32\DRIVERS\netbios.sys
Did not load driver \SystemRoot\System32\DRIVERS\amdk7.sys
Did not load driver \SystemRoot\System32\Drivers\PCIDump.SYS
Loaded driver \SystemRoot\System32\DRIVERS\rdbss.sys
Loaded driver \SystemRoot\System32\DRIVERS\mrxsmb.sys
Loaded driver \SystemRoot\System32\DRIVERS\arp1394.sys
Loaded driver \SystemRoot\System32\DRIVERS\wanarp.sys
Loaded driver \SystemRoot\System32\Drivers\Fips.SYS
Loaded driver \SystemRoot\System32\Drivers\Cdfs.SYS
Loaded driver \SystemRoot\System32\DRIVERS\ndisuio.sys
Did not load driver \SystemRoot\System32\DRIVERS\rdbss.sys
Did not load driver \SystemRoot\System32\DRIVERS\mrxsmb.sys
Loaded driver \SystemRoot\System32\DRIVERS\mrxdav.sys
Loaded driver \SystemRoot\System32\Drivers\ParVdm.SYS
Loaded driver \SystemRoot\System32\DRIVERS\srv.sys
Loaded driver \SystemRoot\System32\Drivers\Fastfat.SYS

 

Hi john263,

I did a quick Google and found this thread: Mup.sys. It offers many possible solutions, including disabling mup.sys, removing USB devices, and updating chipset drivers. Let me know if any of it is useful.

Nick

 

Nick

Thanks again, at least for a VERY useful thread. I could see as I worked my way through how my symptoms had very different results when experienced by so many different people. I delayed responding for a week hoping that I would luckily stumble upon something that worked for me from the thread. Sadly, I did not. I have phoned Microsoft every other day and no promised call back has yet occurred. Thusfar it is "on the job training" for them. It is sad when I have NO problem except for SP1 or 2 and Microsoft twice has considered their job done when they asked me to phone emachines. When I bring up the prior conference call with Microsoft and emachines they sadly refered it to someone else who never phones back (I have been disconnected several times during the attempted transfers.)

For other readers:
Review: All windows updates SP1 and 2 install individually
SP1 or 2 generate stop 0x0000007f 0x0000000d 0x00000000 0x00000000
hardeware is not the problem-video, modem, memory removed or tested
F8 stops at mup.sys. That was disabled in registry and recognized as disabled in the NEXT windows Repair or (about 25 to date).
F8 then stops on viaagp.sys
Did install 4 in 1 drivers for via km 266 chipset
All my emachines are Athlon computers, generally with S3 integrated video.
The thing that should make it easier to find is that:
1. The same errors occur with multiple emachines.
2. The computers run clear and test perfectly BEFORE SP1 or SP2 only, meaning possibly there is a similarity in both SPacks that cause the problem.
3. I can always repair from the xp home cd, reinstall my original drivers, and go on with life.
The inability to obtain further updates without SP1 is the incentive to keep trying. (Along with large HD recognition.)
4. The knowledge of Microsoft appears pathetic and empty compared to the experience of the others I read through and copied from the thread you sent.
5. I think if Microsoft stayed with myself or any of the others with the same problem long enough to determing the cause that the time would be so much sbetter spent than periodic short term attempts with no solution.

 

Actually A long time back, I remember SP1 and SP2 wouldn't install on Windows if certain parts of the OS like the Activation part were corrupted either by file corruption or registry corruption.

 

Ok, I'm going to cover quite a bit of ground, but I can't guarantee results.

Mup.sys. The other thread linked to provided a lot of dubious information. "MUP" stands for Multiple UNC Provider Driver. It has nothing to do with .NET as one person in that thread stated. It is not something only relevant to Novell networking. "UNC" stands for Uniform Naming Convention, which is a method of identifying resources such as share names and/or files on a network. Basically, a UNC is when you type something like "\\server\sharename\". For example, when you go to select "Map Network Drive..." in Windows Explorer. So, Mup.sys is a Windows service that assists applications, such as Windows Explorer, in mapping these UNC's to the proper network resources.

So now you know what Mup.sys is... but, unfortunately, this information is probably totally irrelevant to your problem. Why? Because more than likely there is no inherent problem with Mup.sys on your system, rather it just happens to be the last driver that gets loaded prior to everything grinding to a halt. Stopping at Mup.sys is a symptom rather than the illness. This seems to be confirmed since disabling it just means that the system grinds to a halt at the next driver up, viaagp.sys, in your case apparently.

To me the most critical piece of information is instead the bluescreen stop code (also sometimes called a bugcheck code). In your case the code is 0x0000007F (the first of the four numbers on the STOP line). Stop code 0x0000007F identifies an unexpected kernel mode trap. What is a "kernel mode trap", you ask? Well, the term "trap" refers to the processor's mechanism for halting an executing thread of instruction when an "exception" or an "interrupt" occurs and transferring control to specialized handler code for said exception or interrupt. An interrupt is an asynchronous, essentially external event that requires immediate attention from the CPU (eg, hardware device, I/O signals, timers, etc.) An exception, in contrast, is a synchronous condition that results from the execution of a CPU instruction which happens to represent an error or otherwise unusual condition (eg, divide-by-zero error, memory access violations, etc). In your case, the second number on the STOP line, 0x0000000D, indicates that the CPU encountered a "General Protection" exception. Without getting too much further carried away, all this just means that the CPU encountered an unusual and unexpected situation... which in this case is usually indicative of a hardware problem.

But clearly you aren't experiencing a real hardware problem because everything works fine pre-SP1/SP2 and the same situation is happening with multiple machines. Ok, it's not a real hardware problem, but it kinda looks like one... what might cause that? Here is where it gets tricky. I searched the 'net for problems similar to yours and found that some people have luck by going into the BIOS and resetting everything to system defaults. Others monkey around with the Advanced Configuration and Power Interface (ACPI) settings in the BIOS and through trial-and-error they get their systems to work. What's all this about?

Here's my personal theory, but since I haven't had this problem myself I can't be sure. There is a key piece of Windows OS code called the Hardware Abstraction Layer, or HAL. Hal.dll provides the low-level, foundational glue that matches the rest of the OS to the particulars of your motherboard, chipset, and CPU. Hal provides a measure of portability to the rest of the OS. The way it works, though, is that several HALs -- a "standard" one; one for PCs that support the Advanced Configuration and Power Interface, ACPI; one that supports Advanced Programmable Interrupt Controller, APIC, PC's; one that supports APIC and ACPI PCs; one that supports multiprocessor PCs; one that supports multiprocessor ACPI PCs; etc. -- are included on the Windows CD, but only one of these is copied to your computer's harddrive at installation time and given the name Hal.dll. If the wrong HAL were to be copied to your harddrive at installation, then of course your OS is going to come to a screeching halt soon into the boot phase and it is largely going to look like a hardware failure of some sort. My theory is that for some reason the SP1/SP2 upgrade process is perhaps detecting your system components incorrectly and upgrading the HAL.dll file with the wrong version, or a version that mismatches your BIOS settings. Perhaps you have ACPI disabled in the BIOS and, yet, the SP upgrade code detects that your motherboard is compatible with ACPI and installs that version anyway.

So, my suggestion is to try and set all of your BIOS settings to system defaults, if they aren't currently, and installing the Service Pack with these defaults in place. If you are 100% positive that the BIOS has always been at system default settings then go into the BIOS and try to find somewhere where perhaps you can enable/disable ACPI, it might be under "Power Management" or something similar. It might have a setting saying whether or not the OS is ACPI-aware. Try changing that setting from it's default and re-doing the install. Moreover, I would suggest to not go overboard in trying to pull out things from msconfig and from your driver list. I know that you have some fear of the Matrox drivers, but I would first try to not make any changes to your working system prior to the SP install process. Just make sure no other taskbar applications are running, but for the most part ignore everything else. In fact, I usually install SPs with my resident AV fully active and in place, even though many people will tell you that this causes problems (this was more true in the past and not so much of an issue today, IMHO). The other thing you may wish to do is, prior to the upgrade, check which HAL you are running... you can check this two ways: 1) open the file "\windows\repair\Setup.log" and search for "Hal.dll", you should find a line saying something like "\WINDOWS\system32\hal.dll = 'halacpi.dll','203bd'"; or 2) you can open Device Manager (right click on My Computer, select Properties | Hardware tab | Device Manager) and then look at the desciption under "Computer" when you expand that listing in Device Manager. None of this may help, but I still suspect that you have some sort of BIOS/HAL conflict or BIOS non-compliance issue.