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.
Sounds like these two are the problem. Where did you downwload them from?
I've never seen this but you might want to check out Dependency Walker v 2, which may allow you to see which dll's are being accessed. I wonder if a core dll that Symantec uses has been overriden with different version.
It certainly is not unknown for Microsoft updates to break things .... 8:(
I decided I didn't want Search 4 so I declined it so I can't say if I would have suffered or not.
I've flagged your message for one of the Norton Staff to jump in on -- watch for name in red ...
While waiting would you post what version of Windows you are using and whether you have N360 ver 1 or ver 2 (Help & Support / About)
Ok, so I've determined the issue isn't with the 4.0 search update but with Visual Studio 2008,
With vs2008 installed norton will produce this error, and games seem to crash very frequently, unfortunately, vs is a massive application and installs a boatload of stuff so I don't know how easy it'll be to pin down.
This is on Vista x64 using Norton 360 v2.
That extra information will help I'm sure as will eliminating the Windows Search 4.
I see there's a Service Pack for it although beta ......
It uses NET which may be related to a cause; also do a search here on SQL and see what that turns up since I think I've seen references to problems involving it.
But it's outside my sphere. I did flag the message for a Norton Staffer to check.
Try a Google on [ Visual Studio 2008 +VISTA +64 ] Looking at the first that came up when I did gives someone with the problem and a solution ..... [And I did this after mentioning NET .....]
Well interestingly, I uninstalled everything related to VS2008 except for .net 3.5. however perhaps as nothing else is using .net 3.5 the issue wouldn’t crop up without 2008 installed regardless?
louiswu wrote:
Well interestingly, I uninstalled everything related to VS2008 *except* for .net 3.5. however perhaps as nothing else is using .net 3.5 the issue wouldn't crop up without 2008 installed regardless?
Not clear whether you still get the problem now with only Net 3.5? If so what happens if you uninstall that?
Ok problem solved!
Turns out it was a faulty RAM module which was causing both the crashes and the N360 error message, the two problems were in the end disjunct, and n360 was causing 0 problems by itself. It was pure coincidence that the error message didn't appear after I uninstalled vs2008.
Perhaps the N360 error message could change to
DLL Loading problem
or
Debugger detected
or
Integrity violation
or
RAM Failure
Cheers for the help though.
Good news indeed!
Thanks for posting the feedback and the solution.
RAM, like video drivers, can cause totally unexpected problems .....