Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
I may have the same issue. I have the same graphics card and can’t boot with NIS2009.
Ok, I can confirm this one. I could never get my Dell to boot with NIS2009 but after I removed the ATI drivers for my X800 card it boots just fine...
So now I can run NIS2009 but not my games, which is why I upgraded from NIS2008 in the first place.
So is this an ATI problem or a Symantec problem?
Sounds like you all have the same problem indeed. Are there any signs off ATI in your History in NIS?
Could be NIS accidentally stopped some files
Thanks Stu, I have tried a couple of X800 driver installations. The only NIS History event that occurs between loading the X800 driver and the reboot hang is:
Risk: : Low
Activity: No user is logged in.
I'm not sure this is at all relevant because the problem first evidenced itself when the well established and functioning ATI drivers were thrust together with the NEW NIS2009.
The ATI driver load dialogue throws up some text that says there will be up to one minute's delay while there are tests done to check "stability". There is quite heavy disk and CPU activity after the WIN XP splash screen but then the system goes silent. Again this is an anomaly to me because initially the driver was in place and working for many years before I updated to NIS 2009 from NIS 2008.
I have used boot logging to view what is happening when the XP boot hangs.
Under normal boot conditions the following transition takes place at agp440.sys when the kernel has loaded and then the \system32\drivers\... are loaded.
....
Loaded driver Ntfs.sys
Loaded driver NDIS.sys
Loaded driver Mup.sys
Loaded driver agp440.sys
Loaded driver \SystemRoot\system32\DRIVERS\intelppm.sys
Loaded driver \SystemRoot\system32\DRIVERS\usbuhci.sys
Loaded driver \SystemRoot\system32\DRIVERS\usbehci.sys
Loaded driver \SystemRoot\system32\drivers\ctoss2k.sys
....
In the failed boot scenario the following transition occurs
....
Loaded driver Ntfs.sys
Loaded driver NDIS.sys
Loaded driver Mup.sys
Loaded driver agp440.sys
Did not load driver ACPI Multiprocessor PC
Did not load driver Audio Codecs
Did not load driver Legacy Audio Drivers
Did not load driver Media Control Devices
Did not load driver Legacy Video Capture Devices
Did not load driver Video Codecs
Did not load driver Audio Codecs
Did not load driver Legacy Audio Drivers
Did not load driver Media Control Devices
Did not load driver Legacy Video Capture Devices
Did not load driver Video Codecs
Did not load driver Intel Processor
Did not load driver Intel Processor
Did not load driver Audio Codecs
Did not load driver Legacy Audio Drivers
Did not load driver Media Control Devices
Did not load driver Legacy Video Capture Devices
Did not load driver Video Codecs
Did not load driver Intel Processor
Did not load driver Intel Processor
Did not load driver Audio Codecs
Did not load driver Legacy Audio Drivers
Did not load driver Media Control Devices
Did not load driver Legacy Video Capture Devices
Did not load driver Video Codecs
Did not load driver Intel Processor
Did not load driver Intel Processor
Did not load driver Audio Codecs
The boot goes on in a loop, as you can see, not loading drivers, sometimes reporting that is has loaded a driver or two that did not appear in the normal boot and going back into the loop. It seems to be terribly lost and confused.
It seems to be terribly lost and confused.
===========================================
Thank you ever so much. I needed that. I feel terribly lost and confused today.
Is it possible to change boot order so that those drivers load before NIS. I realize that prevents NIS from doing its thing completely and making sure the drivers are safe; but it might be a worthwhile experiment if possible to do.
Excuse me, too, if I missed the answer to this earlier. What if Norton is completely disabled (AV, Firewall, etc); and you boot up. Does that work? And if it does, what happens after you're up and then reenable Norton? Will your computer work then (at least until reboot)?
Thanks for your input mijcar. Is it possible to change boot order so that those drivers load before NIS? This is a very good suggestion. I do not know how to do this but if you can point me in the right direction I will give it a try.
Completely disabling NIS2009 has no effect. Using MSCONFIG to come up in diagnostic mode has no effect.
Jo, you’re going to have to wait for an actual Norton tech to help you with this one. I suspect they really, really don’t want Norton loading out of order, so you may not have the opportunity to change that sequence. I know you can change behavior with the system configuration utility, but … wait for the technician’s advice.
Hi,
I have seen a lot of people having trouble booting their system due to an error with the agp440.sys file. Same symptoms where people uninstalled their graphic drivers and the system would boot. In many cases it seems that it was problems with the disk and that running checkdisk solved the issue. However, In those cases Norton was not involved.
I can't say if it will help you but running a chkdsk is something to try. The others ran chkdsk through the recovery console but I guess you can try and set it to run on reboot first.
Just open command prompt and type
chkdsk /f /r
Also, google on agp440.sys and you will get a bit of reading. :)
jAW
Hey Jo;
Has Symantec fixed your problem yet?
I also use a ATI X800 graphics card and XP Pro SP3. I'm getting ready to upgrade from NIS 2008 to NIS 2009 and now you have me scared. Maybe I should wait until this issue is solved.
Please let me/us know what is happening!
Hi harris,
No, there is no fix or workaround from Symantec at this time. I have completely rebuilt my XP Pro SP3 system with a brand new, SATA HDD so I have eliminated any extraneous factors or registry corruptions. I am not running any other security software. I have not used any registry cleaning or optimising utilities.
The post from jAW above is very interesting and has some positive leads. I have followed his advice and pursued the Google line of research which has been fruitful. I will be trying out what I have learned tonight.
Based on my experience and that of RESEDIT I expect you will encounter problems rebooting if you upgrade to NIS2009 with ATI X800 drivers installed.
There is already a second thread on this same issue. We are currently researching why the '09 products seem to be exacerbating the agp440.sys driver load failure. So far it appears that saying ATI X800 is not good enough because we haven’t been able to reproduce the issue on our systems with the latest drivers. It would help to get the specific flavors, such as XL, XT, XT Platinum Pro, etc. so that we can find a further isolating factor.
I’m running an ATI Radeon X800 XT Platinum Edition
As an update to this, I just attempted to install the Norton Antivirus 2009 on my computer. I do not have an ATI graphics card and experienced the same problem with the NVidia Geforce 6100 nForce 430 drivers. I cannot remove this as it is part of the systemboard and had to uninstall the NAV 2009 under Safe Mode and then reinstall NAV 2008.
Thanks Reese. My card is a Gigabyte X800 PRO. I am running XP Pro SP3 32 bit OS.
Running chkdsk didn't help. It took about the same time as a full disk format so it was a looong time.
The google search turned up the following Microsoft article
http://support.microsoft.com/kb/324764
I tried disabling agp440 using the instructions provided and I was able to reboot with NIS2009 and the ATI drivers in place. The problem seems to be that I cannot see the card in the system using device manager or display properties. So I am not sure what has been achieved until I do more testing. It was a very late night.
An unexpected outcome was that my Canopus DVStorm2 card's drivers loaded. This is a PCI card used for Video capture and editing. The drivers were on the system but were not being loaded. With agp440 disabled the card went into working status in device manager and found the right driver. I need to test this card before I can say it is returned to the full working condition it was in before I rebuilt XP.
This development and the comment from Reece_anshultz that Symantec cannot reproduce this on their systems sent me off on what turned out to be a tangent. I enabled agp440 (enable agp440 service_boot_start). I removed as many recent MS patches, including SP3, that I could. This did not solve the boot hang problem.
So in summary I would conclude: Reece_anschultz is on the right track when he says "the '09 products seem to be exacerbating the agp440.sys driver load failure." And jAW, well done! Good pick up.
Hi Reese,
A further isolating factor would be chipset. I have the North Bridge: Intel® 865PE chipset on the Gigabye GA-8IPE775 Pro motherboard.
Regards,
For the last two days I've suffered this issue. Started when I got the update offer of Norton IS 2009 and said "why not". Turned out to be more like, "What the heck"?
I have a ATI X800Pro platinum and a VIA chipset on my K8TPRO-939 motherboard. Oh yeh, XP sp 3.
Disabling the video drivers stopped the booting hang. Thanks to you folks for this one.
So after reading what all you folks said and reading the Microsoft fix, I thought about what Microsoft claims is the cause or what they wrote in "cause", wrong AGP driver or something to that affect.
I went to the VIA chipset site and downloaded the latest drivers for my motherboard. I'd already installed the latest Catalyst drivers. The VIA drivers for AGP I downloaded today were newer than the version I had on my machine.
This fixed my hang ups. I've rebooted cold and also restarts for a couple of hours and can't get it to come back. So maybe this will help some.
Joe
ResEdit, Sharon has sent you a message via the community Private Messenger system, please look for the 
in the upper right hand corner of any community page.