re: agp440.sys (also mup.sys)
Saturday, August 30, 2003 at 12:43 pm
Windows 2000 Annoyances Discussion Forum
Posted by Michael
(1 messages posted)
agp440.sys and it's predecessor in load sequence, mup.sys (multiple UNC provider
- a networking component) are both notoriously shaky parts of the Win2k/XP load
sequence.
Contrary to MS limited KB articles on these two, there is no single cause, and no
single solution. In my experience, the problem is worse with XP, possibly though
not certainly due to the Windows Product Activation code and the way it monitors
hardware changes.
The most common problem is some form of hardware change - RAM, video card, CD, even
changing the same cards into different PCI slots (I had this happen once when I moved
a network card.)
Electrical zaps can also occasionally cause problems, if they are severe enough to
cause erasure or alteration of ROM'd data, but that's a fairly rare cause. Bad sector
or file corruption problems in the related system files is also a possibility, particularly
if users don't shut down properly or are forced to hard shut down because of a hang.
In other words, almost any problem can cause load failures in these NT services,
and the solutions are often just about as random as you can get. Don't expect that
another user's problem is your problem, or that his solution will work for you.
Despite the MS KB article's bit about video drivers being incompatible, I've had
this problem occur when there's been no change in videocard and I have a current
WHQL certified driver. The most recent case was from removing an Adaptec 29160 Ultra
160 SCSI adapter and replacing it with an Adaptec29320 Ultra320 SCSI adapter.
Some people commenting on this have slammed refurbished comps by some vendors, but
this is not a specific vendor problem or a specific hardware problem - it is a persistent
but intermittent problem with these particular Win NT services.
If you have the original bootable CD and administrator password, you can play with
switching these services off from the repair console, sometimes that helps, sometimes
it doesn't.
If you have spare hardware, you can tweak around with changing configurations around,
sometimes the problem will be solved with a huge number of reboot attempts, and one
time, the service will load itself successfully.
In almost all cases (only one exception I know of), once you get it to boot, it will
continue to do so.
To avoid the problem when making hardware changes, if you go into the administrative
tools (you need to have some understanding of NT services and which ones are essential
and which can be stopped) and changed their modes from automatic to manual and start
to stopped, you can trim down you 2k/XP configuration to a sort of "safer than safe"
mode, then shut off and make your hardware changes.
On Tuesday, July 22, 2003 at 10:48 pm, Eric wrote:
>
>Well I still don't have a solution to my problem, but i have eliminated non-factors
>and narrowed it down. I suspect a thunderstorm that occured while i was away.
Long
>story short, i believe my motherboard might be causing the problem since the only
>thing not surge protected was the cat5e cable running straight from the network
jack
>in the wall into the i/o panel on my mobo. Anyways, I'm having it looked at tomorrow.
> I doubt anymore advice could help, but if anyone feels they have some useful information,
>it couldn't hurt to post. Thanks again, Eric...
>
>PS - my system was working fine before my problem occured, so it couldn't be a BIOS
>that doesn't support ACPI causing my problem, but thanks...that probably is infact
>the case with many others.
>
- Written in response to:
- re: agp440.sys (Eric: Tuesday, July 22, 2003 at 10:48 pm)
Responses to this message:
|
|
All messages in this thread [show all]
 | agp440.sys (kobie wilburg: Thu, Feb 14, 2002, 1:18 pm) |
 | | | | | | | re: agp440.sys (also mup.sys) (Michael: Sat, Aug 30, 2003, 12:43 pm) |
| |
| |
| |
Return to the Windows 2000 Discussion Forum
|
|
