B00kWyrm
Posts: 992 +39
Hi all...
recently used resources here to resolve one problem.
now another has cropped up.
I have had two bsod events, spaced about a week apart, each pointing (minidump analysis with windbg) to symsnap. Using google I have learned that this is a component of Norton Ghost, a program I had installed but have not used in ages...
Before bsod events, I had upgraded ram, and upgraded Harddrive.
All this is in a Gateway... 4525gz.
Now the ram is maxed and the hd is a wd scorpio blue 160gb
What I have done since bsod is...
regedit to remove all references to Norton Ghost...
(as the uninstall routine would not work).
then removed all files and folders related to Norton Ghost.
I may or may not choose to reinstall.
So, here are the questions... (finally! )
1. Have I properly interpreted the windbg report as pointing to Ghost?
2. Would migrating to the new hd have caused this program to break?
The two pertinent Minidump / WIndbg reports are attached.
recently used resources here to resolve one problem.
now another has cropped up.
I have had two bsod events, spaced about a week apart, each pointing (minidump analysis with windbg) to symsnap. Using google I have learned that this is a component of Norton Ghost, a program I had installed but have not used in ages...
Before bsod events, I had upgraded ram, and upgraded Harddrive.
All this is in a Gateway... 4525gz.
Now the ram is maxed and the hd is a wd scorpio blue 160gb
What I have done since bsod is...
regedit to remove all references to Norton Ghost...
(as the uninstall routine would not work).
then removed all files and folders related to Norton Ghost.
I may or may not choose to reinstall.
So, here are the questions... (finally! )
1. Have I properly interpreted the windbg report as pointing to Ghost?
2. Would migrating to the new hd have caused this program to break?
The two pertinent Minidump / WIndbg reports are attached.