Ghost 14 and Norton 360 BSOD

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.

This is an ongoing problem.  I use XP SP3.  I have not changed partition.  I back up to an external drive.  I hope that helps.

 

The problem occurs I think after Ghost tries to its weekly recovery set point.

We'll need the crash dump.  Try the steps in the following document:

 

http://service1.symantec.com/SUPPORT/tsgeninfo.nsf/docid/2007081601291939

 

Let me know once you have a full dump. 

I have Ghost 14 and 360 installed.  I use the back up from Ghost 14 to get complete Drive Snap Shot and incremental updates onto one drive and 360 for AV, Firewall, and back up of important files to a different drive. 

 

I get the BSOD on starts or restarts with error caused by symsnap.sys.  After BSOD, when I reboot, Ghost starts up but not 360.  The error codes on BSOD are

 

Stop 0x0000008E (0XC000000F, OXBA68A5CD, OXBAC3728, OX00000000)

SYMSNAP.SYS ADDRESS  BA68A5D BASE AT BA682000 

 

Any suggestions?

Is this Windows Vista?  Do you have SP1 installed?  Have you changed your partition recently?  Have you been able to use N360 and Ghost 14 concurrently and is this a recent issue?  Did this error occur after performing any specific actions that you can think of?  Did this occur after running a Virus scan?