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.
BSOD's normally include detailed error codes that don't mean anything to me but which can to others and can be looked up.
Do you have a record of exactly what error messages came up? Not "It said something like .... ' <g>
So by the general lack of response from Symantec, I'll presume that I should just ignore the problem and consider myself lucky that I could at least get rid of N360 off my system then shall I 
Its bad enough that I've paid good money for this garbage, but for Norton to ignore the problem and hope it (or I) go away really isn't good enough !
Buy another Norton product - NEVER again !
I apologize if we did not respond to your issue as quickly as you had hoped. Can you provide any information about the blue screen error that you received? Possibly the Stop Error Code? This information may provide some insight into the cause of the error. You may also wish to contact our Customer Support team through the Norton 360 Help & Support link. Or you can visit the below site to contact our free Customer Support:
http://www.symantec.com/norton/support/selectproduct_ts.jsp
If you have already done this and they could not resolve your issue, please let us know. If this is the case, please provide as many details as possible. Thanks!
OK, I've run all week without N360 on my PC and all the 'security' tests I've run are fine so I decided to give N360 one last try this weekend - same result
The BSOD message was
*** STOP: 0x0000007F (0x0000000D, 0x00000000, 0x00000000, 0x00000000)
As I've indicated, my PC has run beautifully, boots up quicker etc without N360, I reinstall it and within minutes it crashes. Needless to say, its now off my PC (yet again) but I would appreciate some assistance in getting this sorted out
I think it should be possible to assit you. However, without Norton installed I would suggest that this is not possible.
If I were in your position, I would do the following:-
1. Update using Windows updater. This should take you to sp3 and then there are some patches beyong SP3.
2. I would run Windows Malicious software tool - mrt from the command line.
3. I would run onetime scanner from Microsoft - onecare. If you are free of all virii etc, then you can remove onecare.
4. I would run restore point and ERUNT.
5. I would scan registry and hard drive for all signs of Norton - not just use cleanup tool. Cleanup tools are not 100% when it comes to liveupdate info being left, imo.
6. Remove all other Symantec/norton products including winfax etc.
6a Run windows install clean up
6b run autoruns and check for any lines that you are not completely familiar with.
7 Reinstall Norton 360 v2 from KNOWN good source. - i.e. no previous downloads.
8. Run LUALL rather than update in the usual way.
9. If you get BSOD, you need to post not only first stop line but rest of information specific to your crash.
If you need help in relation to any of the foregoing just post back here. No doubt other contributors will have other suggestions.
Thanks, I tried all that and same result !
Any possibility of some help from Symantec ???
Not quite. You see it would be useful to know eactly what is on the BSOD, what you posted was only part of the information. I suggest that if you get the BSOD you make a careful note and post the non standard text part. If you need other help then perhaps calling technical support using Chat is the best solution. You are clearly not the typical user and clearly are not unintelligent, otherwise you would have struggled to find, install and run Autoruns and Erunt. So I must presume you also were able to determine all the processes running on the Autoruns login screen. Logically therefore you surely appreciate that you have only to date provided very limited details.
If you would like to email me a hijackthis report, I would be pleased to examine if there is any obvious issue with your system.
You can google hijackthis to find the free download.
Best I can do.
CB357 wrote:OK, I've run all week without N360 on my PC and all the 'security' tests I've run are fine so I decided to give N360 one last try this weekend - same result
The BSOD message was
*** STOP: 0x0000007F (0x0000000D, 0x00000000, 0x00000000, 0x00000000)
As I've indicated, my PC has run beautifully, boots up quicker etc without N360, I reinstall it and within minutes it crashes. Needless to say, its now off my PC (yet again) but I would appreciate some assistance in getting this sorted out
I know that you have evidence pointing to N360 but FWIW a Google on that specific error message does produce a number of people saying they fixed it by reseating RAM and there is also this MKB article:
which also points to hardware causes, although they do CYA and mention software briefly but with no real suggestions.
You may be able to get something out of that MSKB -- it's way beyond me.
You ask later about Symantec help -- you had some suggestions from Tony Weiss who is the Symantec Administrator here -- did you try using the support link in N360. Give him some more details including those CGoldman suggests.
Usually you'll see an associated file as well within a STOP error message. When there isn't there's usually a command that you see. When looking at a STOP error code the main code points to the problem and the first bugcheck register points to cause. I did some looking around for 7f d STOP codes and found response all centered around hardware. Have you tried unseating and re-seating your RAM? If you have more than one stick of RAM I recommend checking with just one or the other at a time to see if you have bad RAM. If that does not resolve the problem, then we'll need to take a look at the memory dump to see what the offending file is.
CB357 wrote:Thanks, I tried all that and same result !
Any possibility of some help from Symantec ???
Names in red are Norton staffers -- see this message here
And see cgoldman's message to you
I am having exact same problem. Was running Norton 360 V2 on a MacBook Pro running Windows XP Home SP2 with no problems until a Live Update sometime in June. Then, after 10 minutes or so, BSD stop error 07F, just as described. I reboot, same thing happens after ~ 10 minutes. Even if no applications running, just sitting idle. I updated to SP3, same problem. No driver file is listed in the error message. If you go to this Microsoft Developer Network site, http://msdn.microsoft.com/en-gb/library/ms795478.aspx, they list this particular version of 07F stop error message as follows:
0x0000000D ā An exception not covered by some other exception; a protection fault that pertains to access violations for applications
So, perhaps not hardware related, but software. If I uninstall Norton 360, the problem goes away. As with other user, would appreciate help with this problem.
Matsci - I share your pain, but at the same time I am sooooooo glad someone else is experiencing the EXCAT same thing as I was beginning to think is was just me (or my PC).
Quite frankly, I gave up trying to resolve the issue because, whilst the help from others has been welcome, the really simple solution is to stop using N360 completely and the problem quite simply goes away.
I'm really questioning the value of N360 anyway, as my PC sits behind a router and is 'virtually' invisible. and I now use Avast (its free) for virus detection
CB357 - Iām glad I found your post, b/c for many days I could not find anyone else with this problem. But, there are likely many more, since problem apparently has started with the recent June update. I hope Symantec will fix the issue, or else issue a refund.
Your problem and the date it arose sounds curiously similar to my own problem.
To help the folks at Norton, I suggest that you reveal the brand of your machine. My problem only manifests itself on a Thinkpad. I have no problems on a Dell despite running the same OS.
Next, download WinDbg from Microsoft (see link below). You will also need the appropriate set of "symbols".
http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx
After experiencing a BSOD, reboot (if that is not automatic), ignore any prompt from Microsoft to send data to them and then run WinDbg. You will have to configure WinDbg to know where to find "symbols". You will also have to have it open the latest "mini dump" that resulted from the kernel crash (BSOD).
Now when you run WinDbg, you will probably see a hyperlink with a word like "Analyze". Click on that link which will cause WinDbg to spew out more data.
Scroll through the data to see if it references a Norton component. If you have a problem like mine, WinDbg will reveal the offender be pifCrawl.exe.
Good luck.
In my previous post, I neglected to offer a temporary solution if you are indeed experiencing the same problem.
If WinDbg identifies pifCrawl.exe as the offender, go to Control Panel -> Administrative Tools -> Services. Once you launch Services, locate LiveUpdate Notice. Select LiveUpdate Notice, stop this service and set it to only start manually.
As previously stated, if your problem is the same as mine, you won't see another BSOD. Of course, you also won't benefit from a basic component of some Norton products.
Have you discussed this with Lenovo/IBM?
In my experience they are absolutely first class in their support and if there is a situation that seems only to occur on Thinkpads that is triggered by some third party software they will want to know and will help track down whether it is their problem or someone else's.
If you don't know it, a first class source of Thinkpad support is Bill Morrow's website http://forum.thinkpads.com/index.php -- completely independent and very knowledgeable. Could be a good place to post a "Has anyone else run into this?" message.
I'm unclear - did you contact our Free Customer Support for Norton 360 already? What were the results? You can access it through the Help & Support section of the product, and have a chat session with out support team. They can also access your system remotely if you wish, and troubleshoot the issue.
Hello would like to let everyone know that I am experiencing this problem on one of my customers machines. I recently did an upgrade for a guy, XP upgrade, and a new HD. All was well for about a month, he called me and told me that the computer was just rebooting at random times. So I went down there and looked through the administrative logs in control panel, and sure enough, after a Norton liveupdate process ran, there was an error and the computer rebooted. I asked him if he recently installed any software and he said that he had installed Norton about a week prior to calling me. I looked through that log again and found the first time it happened. I asked him is this when the first time you experienced it and he was amazed that I knew such a thing and said yes. From that point I could only assume that it was Norton Live update issue, so I disabled it in control panel and told him to manually run liveupdate on a regular basis until Symantec can fix the issue. I thought that temporarily solved the problem.
The guy calls me this morning and says since I left, the computer has been acting really weird, I didn't get the full details cause I was half asleep, but I remember him saying that he has to use active desktop recovery a lot and Internet Explorer is doing crazy things. My first thought was that maybe he earned himself a virus somehow. But I am not too sure since he says it started happening right after I left.
Tomorrow will be in his office to deal with the situation. More than likely I will be uninstalling Norton and replacing it with avast. However I will try to get to the bottom of these new problems he is having and report back here with anything he can find. If it is Norton. I really feel that if a timely fix is not issued, then my customer should be able to get a refund. Thank god I did not sell him the software, cause I would have taken hit and let him return it to me. I guess that's just good business though, right Symantec?
Until Tomorrow... Good Day!
KTEK Computers
In order to truly determine what was at the root of things, details of the error are needed. Do you have details of a blue screen? Crash information?
If an upgrade occured was this an upgrade from Windows Me perchance? Did you choose the upgrade install or a fresh install? The system stability could be more than likely due to the upgrade.