I experienced this BSOD on Win2K systems after doing a Novell network login update of a managed Norton AntiVirus Corporate Edition 7.x and 8.x to managed Symantec AntiVirus Corporate Edition 9.0.3.1000.
Turns out that it was the network update that responsible. I managed to grab a copy of nonav9-ALL.zip that I assumed was from Symantec. Running the batch file in this zip uninstalled the previous versions completely (files, registry entries, etc.). Problem solved. If you can't get the batch uninstaller somewhere, I'll try to find a way to get a copy for you.
I actually went through a number of possible fixes before finding one that I found would work universally. I'll briefly list the steps here, but you should look at: http://service1.symantec.com/SUPPORT/sunset3.nsf/4a466c543a83dec985256c92005cb9ae/fa688feccd3d719485256c92005b5f8a?OpenDocument&src=bar_sch_nam.
1. I found that I was able to log onto the machine using the 'Last Known Good Configuration' option further down the list from the 'Safe Mode' option.
2. Open Device Manager, click View | Show hidden devices and disable (or in my case, I uninstalled every driver reference for NAV, but you may not have to go that far) the drivers listed in the first step of document above. This should allow you to reboot normally.
3. You may have to update your nVidia video adapter drivers, although it wasn't necessary in my case.
4. You may also need to update the Intel Application Accelerator application, although it wasn't necessary in my case.
5. I then completely uninstalled NAV using an uninstaller batch file mentioned above.
6. Reboot normally.
7. Install NAV/SAV.
I haven't quite gotten around to consolidating my notes to write up the fix that worked for me. Actually, our shop is now finally doing a complete update of all of our machines to WinXP via the Microsoft Software Assurance Program, so I didn't figure on ever needing this fix again! That being the case, I hope I h
