Nprotect.vxd causes a fatal exception on boot-up

[alexh110]

Fatal Exception OE at 0177:xxxxxxxx or 0157:xxxxxxxx occurs almost every time I boot up. When I used Msconfig to prevent Nprotect.vxd loading at startup, the blue screens went away. Unfortunately so did the Norton Protection of my recycle bin, which has saved my life on frequent occasions (e.g. when files have become corrupted, and I have needed to recover an earlier version of them from the recycle bin).
Although my computer will still function, it often takes 3 or 4 attempts to boot up, every day: very irritating!
How can I find out what is causing this clash with Nprotect? Could it be mis-registered hardware; or is it more likely to be a software clash?

These protection errors are also associated with SCSI adapter cards and rewritable CDROMs apparently, both of which I have. My DVDRAM drive uses the SCSI bus, and the CDROM is slaved to my second hard-drive on the secondary IDE bus.
Could the problem be caused by a clash between Nprotect and one of these drives?

N.B. My mobo is a Biostar M7VKB with a 750MHz Duron CPU, and 128 Mb RAM.

 

[XPisfree]

NAV has totally crashed my Win installation on a big program installation that tried too NEAR the boot sector at start, even though I disabled NAV at systray. There are (intentionally) so many Norton backgound apps scattered through Windows that can be volatile to potential "threats" at boot time. Ever seen Norton jump up a (thankful) virus alert even when its been "disabled"? They build a wall around the boot files early and defend from there. If the SCSI BIOS options are enabled at all, NAV won't attempt to blindly deflect activity from a legit bootable add-in card type device set before the HDD in the PC BIOS, but the SCSI hands over the DVD install process which continues on with loading of the device drivers or other system files for the DVD dragging the activity near the point in time/resource/file location to the booting system files requests. NAV shoots first and asks later. Any "outside" file activity near the boot process can get targeted for shutdown as a potential threat and this can end up wrecking the Hard Drive even! Suggestions - Poss. alter process commands for the DVD loading drivers to flow in after the main HDD is booting, keeping SCSI dumb at load OR -Something in your SCSI setup option at boot is set to be "faster loading" but too "risque" and alien for NAV's hen-clucking, monitoring of the precious boot files loading. I hate SCSI tho, and the one I had worked best when I turned off all the options (basic setup) in the SCSI BIOS config and let the devices boot up through Plug and Play awareness of the SCSI from Windows, which comes after NAV lowers the shotgun.. I don't use Nortons anymore sadly, after 10 years, NU is recycling the same software from 6 years ago and my NAV got corrupted by viruses 3x that targeted it especially, telling me all was OK right up until the screen died... back to McAfee (shudder)