Annoyances.org
Home » Windows 2000 Discussion Forum » Message 1108935421 Search | Help | Home
  
Tip: Run a free scan for common Windows errors ad

re: agp440.sys (also mup.sys)
Sunday, February 20, 2005 at 1:37 pm
Windows 2000 Annoyances Discussion Forum
Posted by John (1 messages posted)


I also had a problem where my Windows XP system was stuck at the spinning bar (3 boxes) screen. I looked at the ntbtlog.txt and agp440.sys was the last thing that properly loaded. The system would boot fine in safe mode. Multiple boot attempts showed that this was the last thing that loaded correctly even when other different things failed to load after it. The system seemed to repair itself however. Things just started booting ok. I don't think this is hardware related. I think it is Windows XP related mainly because through this message board/list I've seen the problem happen on both Dell and Compaq, and my system is an Asus motherboard, with various components from other manufacturers. One weird thing is that I was having other problems with applications before I rebooted and think that memory was somehow corrupted -- that was why I rebooted. I've seen that Windows XP actually repairs itself sometimes (like notepad.exe gets restored if you delete it from the Windows directory) It is possible that whatever was causing the problem was fixed by this repair mechanism. Any thoughts on this?


On Saturday, August 30, 2003 at 12:43 pm, Michael wrote:
>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.
>
>
>


Written in response to:
re: agp440.sys (also mup.sys) (Michael: Saturday, August 30, 2003 at 12:43 pm)

Responses to this message:
*re: agp440.sys (also mup.sys) (SD: Sunday, June 17, 2007 at 12:32 am)

All messages in this thread [show all]
-agp440.sys (kobie wilburg: Thu, Feb 14, 2002, 1:18 pm)
-re: agp440.sys (Peter: Tue, Oct 22, 2002, 12:09 pm)
-re: agp440.sys (Software Guru: Thu, Jun 12, 2003, 9:29 am)
-re: agp440.sys (Software Guru: Thu, Jun 12, 2003, 10:40 am)
*re: agp440.sys (Boris Svetnikov: Mon, Jun 16, 2003, 10:52 am)
-re: agp440.sys (David Straight: Mon, Jun 16, 2003, 4:41 pm)
-re: agp440.sys (mbioman: Sat, Jul 19, 2003, 7:10 am)
-re: agp440.sys (Eric: Mon, Jul 21, 2003, 7:04 pm)
-re: agp440.sys (mbioman: Tue, Jul 22, 2003, 6:55 am)
-re: agp440.sys (Eric: Tue, Jul 22, 2003, 10:48 pm)
-re: agp440.sys (also mup.sys) (Michael: Sat, Aug 30, 2003, 12:43 pm)
-re: agp440.sys (also mup.sys) (Eric: Sat, Aug 30, 2003, 3:05 pm)
*re: agp440.sys (also mup.sys) (dz: Tue, Mar 2, 2004, 2:13 pm)
-re: agp440.sys (also mup.sys) (John: Sun, Feb 20, 2005, 1:37 pm)
*re: agp440.sys (also mup.sys) (SD: Sun, Jun 17, 2007, 12:32 am)
Return to the Windows 2000 Discussion Forum


All content at Annoyances.org is Copyright ©1995-2012 Creative Elementtm All rights reserved.
Please do not plagiarize; redistributing these pages without permission is strictly prohibited.