I kept my computer on overnight, and I did not have a BSOD occur. When I re-installed Nero 11 Platinum a couple of days ago, I did not check for updates for it. I assume I am running an older version of Nero 11 Platinum, and that the Blu-Ray Player in this version is not causing a conflict with NIS. Previously I was running the latest version of Nero 11 Platinum when the issues started to occur.
Well, if Symantec has identified a conflict then hopefully things will get fixed. I have not had time to do what I'm suggesting here so try at your own risk.... The Nero Blue Ray player is a .exe file. For it to be in memory, something has to load it. Perfrom a fresh boot (not logout). Do not start anything. Use a utility such as WhatsRunning to see what is loaded in memory. Look at what is loading the Blue Ray player at startup, and stop that process from loading at start up. If there is a memory conflict with the Blue Ray player, this should prevent it. FYI - Nero pushed an update to the Blue Ray player last weekend for Nero 11 Platinum. Have been running NIS in silent mode, so do not know if this affected the BSOD.
Have not had time to test with disabling things tonight - maybe tomorrow. However, Nero Back It Up (NBAgent.exe v6.2.2.100) is being loaded at boot time on my machine.
I have Nero Multimedia Suite 10 and am having the same problem, BSOD from SYMEFA.SYS. It started around Oct.9. After several unsuccessful attempts to fix the problem, I uninstalled NIS2012, ran the Norton Removal Tool twice, then reinstalled (Oct.16). I had no more BSODs until Nov.7, after doing an update check from Nero ControlCenter. There was one update which I installed. It was for the Nero Blu-ray Player. I now have Blu-rayPlayer.exe version 12.0.4.11, and am getting BSODs from SYMEFA.SYS again (only when I stop using the PC (WinXP Pro) for 15 minutes or so). I do not have a Blu-ray player, and have even attempted to use the Nero Blu-ray player software. I'm quite sure that when the BSODs first started Oct.9, it was right after doing a Nero update.
I am having the same issue here and after 2 weeks am VERY frustrated and annoyed.
Can Symantec please confirm that they are working on a fix for this?
I do not even want to begin to say here the work and hours, installing uninstalling etc I have done in an endeavour to fix this problem.
I have always used Norton and it has saved my bacon a number of times from some real nasties out there. I don't want to have this experience sullied by this ongoing saga with Norton vs Nero.
See message from Symantec (sanschultz) further up this post. They are aware of it and are working on it.
Yep saw that.
Just hanging on seeing the solution turn up here ASAP. 
It's 3+ weeks since I started this thread. Pretty sad they still don't have a fix for this.
Prevented Nero Back It Up (NBAgent.exe v6.2.2.100) from loading a boot time and still got a BSOD. This is the only Nero .exe file being loaded at boot time (as far as I and several software programs can determine). At this point, I am running with a daily reset of Silent Mode. Have not tried downgrading the Nero Blue Ray player .exe file as Symantec has suggested. Just thought I'd let people know how my suggestion turned out.
TiredOfProblems wrote:Prevented Nero Back It Up (NBAgent.exe v6.2.2.100) from loading a boot time and still got a BSOD. This is the only Nero .exe file being loaded at boot time (as far as I and several software programs can determine). At this point, I am running with a daily reset of Silent Mode. Have not tried downgrading the Nero Blue Ray player .exe file as Symantec has suggested. Just thought I'd let people know how my suggestion turned out.
I think the issue with Nero is a support file that gives BluRay support. It is the whole Nero suite that needs to be downgraded.
If you uninstall it, and reinstall but do not allow it to update for now. That will keep all the associated files and .dlls frombeing updated to the problem version.
I agree with peterweb's advice, as I un-installed Nero 11 Platinum, which was up to date, and then I re-installed it, but did not update it. I have not had any BSOD's since then, and it has been now a week without any issues. Hopefully this helps some other users facing the same issues.
I agree with bcotter, the time that this is taking in unacceptable, at least I am in the position that my subscription on 3 of my machines falls due in 3 weeks the 3 machines in 90 days, may just cut my losses and look for an alternative
nordea wrote:I agree with bcotter, the time that this is taking in unacceptable, at least I am in the position that my subscription on 3 of my machines falls due in 3 weeks the 3 machines in 90 days, may just cut my losses and look for an alternative
As frustrating as the time being taken to bring a fix, it is better than rushing something out that would end up breaking even more computers. The fix may be ready, but it has to be tested to see that it does not conflict with the millions of combinations of hardware and software in use by the users.
This is happening to me also. Running Nero 11 Platinum with latest updates. Only difference is I'm still running NIS 2012 (19.9.0.9) so it looks like it's happening to both the new and old versions. Just an FYI.
Ed
Peter, with all due respect, if this was happening to you on a regular and repeatable basis for a MONTH you likely wouldn't feel very kindly towards Symantec right now. It's been proven that there is a problem, that it impacts multiple people, and they apparently know the cause. It's very hard to believe that they cannot fix it though. It's especially annoying when they have been so silent about it. I haven't heard anything from them for a week now.
Nordea is not the only one moving to a Plan B so they can get their systems back to a stable configuration.
peterweb wrote:
As frustrating as the time being taken to bring a fix, it is better than rushing something out that would end up breaking even more computers. The fix may be ready, but it has to be tested to see that it does not conflict with the millions of combinations of hardware and software in use by the users.
Peter thanks for your comments, put I run a small photography business and it is very frustrating to wake in the morning after a long shoot to find that none of your images have been imported or no previews have been generated do to a blue screen from SYMEFA.SYS.(wasted hours)
It is now more than 10 days since sanschultz posted “We've determined the cause of the issue, which is a conflict with the latest version of Nero. We're currently working on a fix for it. “ Since then silence!
nordea wrote:
Peter thanks for your comments, put I run a small photography business and it is very frustrating to wake in the morning after a long shoot to find that none of your images have been imported or no previews have been generated do to a blue screen from SYMEFA.SYS.(wasted hours)
It is now more than 10 days since sanschultz posted “We've determined the cause of the issue, which is a conflict with the latest version of Nero. We're currently working on a fix for it. “ Since then silence!
As I have not run into this issue on my system, I can only imagine the frustration, irritation, and yes, anger being felt by users afflicted with this.
It is often little solice to know that there is a fix in the works, when you are dealing with this on a daily basis.
In the mean time, have the users taken advantage of the temporary work around of reinstalling Nero and holding off on allowing it to update?
Has anyone given notice to the fact that it was a Nero update that started this issue, not Norton? But everyone is blaming Norton for not coming out with a fix sooner. Has anyone complained as loudly to Nero?
Peter, it's Norton that crashes my system, not Nero. Yes, I know that there is some sort of tie-in here, but I've played with the products of two other competitors and they are not crashing while Norton is. If Norton would let people turn off background scans that might help, but they insist on making them run, and when they do, systems crash. The BSOD clearly says it's a Norton product causing it. Stop using Norton and you're ok.
With that sort of evidence, I think the onus is on Symantec to get this fixed. They said 10 days ago they knew what was happening and were working on it, but since then, nothing. It's been a month since it was reported, and some of us have spent a good deal of time getting logs, etc. for them. I'm in the IT business myself and if I just let something go that was crashing systems for a month I would be in a great deal of trouble, so I find this really disappointing.
If I could just get a refund I would give up on them at this stage. The lack of any communication at all just is really unforgiveable.
Bill
bcotter wrote:Peter, it's Norton that crashes my system, not Nero. Yes, I know that there is some sort of tie-in here, but I've played with the products of two other competitors and they are not crashing while Norton is. If Norton would let people turn off background scans that might help, but they insist on making them run, and when they do, systems crash. The BSOD clearly says it's a Norton product causing it. Stop using Norton and you're ok.
With that sort of evidence, I think the onus is on Symantec to get this fixed. They said 10 days ago they knew what was happening and were working on it, but since then, nothing. It's been a month since it was reported, and some of us have spent a good deal of time getting logs, etc. for them. I'm in the IT business myself and if I just let something go that was crashing systems for a month I would be in a great deal of trouble, so I find this really disappointing.
If I could just get a refund I would give up on them at this stage. The lack of any communication at all just is really unforgiveable.
Bill
Norton has given a work around to protect users while they properly test the fix they are working on.
How well did Nero test their update before releasing it?
As you are in IT, you are fully aware of the number of combinations of hardware and software out there. Norton is working to fix something someone else messed up. They are taking the necessary time to test it so they don't have the same situation of breaking someone elses programs.
Trying not to make a bad situation worse.
I think a little more communication (as in "any") from Symantec would go a long way. I would also think they might want some of us with the problem to help them with their testing, as they did want help from us in identifying the issue, but that's just one man's opinion.