• All Community
    • All Community
    • Forums
    • Ideas
    • Blogs
Advanced

Not what you are looking for? Ask the experts!

Kudos1 Stats

Vista crash logs point to SYMEFA.SYS

Over the last 48 hours my system has rebooted itself 154 times and has created dump logs in c:\windows\minidump. All of these logs point to SYMEFA.SYS the Symantec Extended File Attributes driver. Has there been a new update to NIS 2009 in the last few days that could have caused this? Dell recommends uninstalling NIS for 1 day to monitor if the system continues to reboot. The strange this is that if I stay active on the system it does not reboot, it is only if it idles for 15-20 minutes.

Replies

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Try turning off UAC. Also are you using any other security software? What was your previous set up? 

 http://www.nortonlabs.com/inthelab/uac.php

Message Edited by Dieselman743 on 11-07-2008 07:42 PM
Real Time Protection = NIS 2009 + NATBehavior Analysis = ThreatfireOn Demand = MBAM
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

jeffhielen, there haven't been any updates to SYMEFA since the product shipped. It sounds like something has changed in your environment to be triggering this.

Are you prompted to submit these to Microsoft, and if so, have you?

Reese AnschultzSenior Software Quality Assurance Manager, Symantec Corporation
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Reese

I haven't been prompted to send a dump log to Microsoft but that is a good idea.  I will head over there now.

Thanks

Jeff

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

If you do submit it, please provide the bucket-id that they associate with it. It also could be beneficial if you provide kernel dumps instead of mini-dumps. The setting for this can be found under My Computer's Properties. Go to the Advanced tab and to the Startup and Recovery section and choose Settings. Under Write Debugging Information you can choose Kernel memory dump.

This will make it take a little longer to start up after a crash, but the additional information can be very valuable. 

Reese AnschultzSenior Software Quality Assurance Manager, Symantec Corporation
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

I turned off Idle Time Scan in NIS 2209 options and the system has not rebooted in over 12 hours. I have not yet followed up with Microsoft. For now the system is stable.
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Jeff, I'm glad to hear that you've found a work-around for the problem.
Reese AnschultzSenior Software Quality Assurance Manager, Symantec Corporation
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Jeff,

Would you be willing to assist in isolating this issue?  I've sent you a private message.

Sharon Anschultz, CISSP

SQA Specialist

Symantec Corporation

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

I have a client with the same issue with her Dell, frequent shutdowns while she is away from her computer.  It's a brand new machine.  However, it's not an NIS2009 issue, because it was happening for at least a month before she put NIS2009 on.  Her previous software was NIS2008 and I haven't ever had issues with that.

I've read about other Dell owners having similar problems, but haven't had time to pursue this.  Her machine, btw, is a Vostro.

mijN360 2013, v.20.1.0.24; Win7 Pro, SP1 (32 bit), IE 9, Firefox 14, No other active securityware
Kudos0

Re: Vista crash logs point to SYMEFA.SYS


mijcar wrote:

I have a client with the same issue with her Dell, frequent shutdowns while she is away from her computer.  It's a brand new machine.  However, it's not an NIS2009 issue, because it was happening for at least a month before she put NIS2009 on.  Her previous software was NIS2008 and I haven't ever had issues with that.

I've read about other Dell owners having similar problems, but haven't had time to pursue this.  Her machine, btw, is a Vostro.


mijcar, it sounds like this needs its own thread. SYMEFA.SYS didn't exist in the 2008 products so this would be an unrelated issue.

Reese AnschultzSenior Software Quality Assurance Manager, Symantec Corporation
Kudos1 Stats

Re: Vista crash logs point to SYMEFA.SYS


reese_anschultz wrote:

mijcar wrote:

I have a client with the same issue with her Dell, frequent shutdowns while she is away from her computer.  It's a brand new machine.  However, it's not an NIS2009 issue, because it was happening for at least a month before she put NIS2009 on.  Her previous software was NIS2008 and I haven't ever had issues with that.

I've read about other Dell owners having similar problems, but haven't had time to pursue this.  Her machine, btw, is a Vostro.


mijcar, it sounds like this needs its own thread. SYMEFA.SYS didn't exist in the 2008 products so this would be an unrelated issue.


Reese, I am saying this is probably NOT a Symantec issue for just that reason.  Re-read what I said. 

mijN360 2013, v.20.1.0.24; Win7 Pro, SP1 (32 bit), IE 9, Firefox 14, No other active securityware
Kudos0

Re: Vista crash logs point to SYMEFA.SYS


mijcar wrote:

Reese, I am saying this is probably NOT a Symantec issue for just that reason.  Re-read what I said. 


Ok, it's unrelated because, according to the original post, the minidumps show that it's crashing in SYMEFA.SYS. SYMEFA.SYS is a part of the Norton products and short of hardware failures or other, misbehaved drivers, shouldn't crash. Once we get a chance to look at the dumps we'll know whether is a bug or one of the other causes.

Reese AnschultzSenior Software Quality Assurance Manager, Symantec Corporation
Kudos1 Stats

Re: Vista crash logs point to SYMEFA.SYS

Hello,

I found this thread via google, because I have the exact same problem.

When I don't use my system actively it is rebooting all the time. The crash reports also point to SYMEFA.SYS and if I uninstall NIS 2009 the problem is solved.

So my question is: is there any more information or solutions on this subject?

Thanks, I like NIS (the first norton I like since a long time) and wanted to buy it, but this makes it an impossible choice of course.

Edit: I see this topic is marked as 'solved', but I have the latest version and updates of NIS 2009 and I still have this problem.

Message Edited by Sebak on 11-28-2008 04:26 AM
Kudos1 Stats

Re: Vista crash logs point to SYMEFA.SYS

Hi there.  I am having the same problem with symefa.sys.  Having recently upgraded to NIS 2009.  Things seemed fine for a few days, then the computer keeps shutting down with the mssage  that symefa appears to be the problem.  I would like to try turning off idle scan as a work around but I don't have time to before the system shuts down again.  Any suggestions?

Thanks

Malcolm

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Sebak, unfortunately Jeff never responded to Sharon's request for assistance in diagnosing this problem. I believe that she'll be contacting you via e-mail or via the community Private Messenger system (please look for the in the upper right hand corner of any community page) so that we can get more information.Message Edited by reese_anschultz on 12-01-2008 06:42 PM
Reese AnschultzSenior Software Quality Assurance Manager, Symantec Corporation
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

mevs461, unfortunately we don't have any "work-arounds" at this point. I believe that Sharon will be contacting you via e-mail or via the community Private Messenger system (please look for the in the upper right hand corner of any community page) so that we can get more information.
Reese AnschultzSenior Software Quality Assurance Manager, Symantec Corporation
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Jeff,  I have sent you a private message regarding this issue. Please look for the in the upper right hand corner of any community page) so that we can get more information.

Sharon Anschultz

SQA Specialist

Symantec Corporation

Message Edited by sanschultz on 12-17-2008 03:11 PM
Kudos1 Stats

Re: Vista crash logs point to SYMEFA.SYS

could you please send a message to me with the solution as well?  I can't get Vista to load correctly, as it crashes during bootup with the same problems as other users have mentioned.  Thanks!
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Hi-

I'm getting this issue in NIS 09 on Vista Home Premium SP1.  The machine BSODs after 20-30 minutes or so, usually either with an IRQL error or kernel mode exception.  At first, the isue was in SRTSP.sys.  I uninstalled, ran symnrt, and reinstalled, and now the BSOD is in symefa.sys.  PM me if you'd like to troubleshoot.

Thanks.

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

I have just enocountered this same problem - repeated BSOD with SYMEFA.SYS listed as the cause - on WinXP-SP3. 
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

OK here's something that might be helpful... I have an external USB hard disk that's been kind of flaky - occasional delayed write errors, or not being recognized on warm reboot and requiring a power cycle of the drive.

I powered off the drive yesterday and since then haven't seen the SYMEFA.SYS reboot problem.

So, I've got my fingers crossed that replacing the ext disk will take care of things.  That said, something in SYMEFA.SYS may not be robust to some kinds of exception scenarios, so you probably want to take a look at that.

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Just to say that I have disabled idle scan in safe mode (it was the only way I could successfully log on) and since then have had no trouble. My OS is windows XP.

Thanks

Malcolm

Kudos1 Stats

Re: Vista crash logs point to SYMEFA.SYS

I've been reading some the posts on Norton about NIS 2009 and problems with SYMEFA.SYS and I began having them today after installing NIS2009 today.
 
I have a Dell XPS M170 laptop that is about 3 years old.
 
About 2 weeks ago I upgraded the hard drive to a 250GB hard drive and installed a clean copy of Windows Vista Ultimate, MS Office Ultimate, MS Visio, and MS Project.
 
I have waited to install NIS 2009 because I wanted to make sure the system was stable.  I must confess, I have been impressed with how fast Vista is compared to XP and the system has been running very well.
 
So today, 1/4/2009, I decided to install NIS 2009.  Then I got all the online updates from Norton.
 
NIS 2009 started having problems right away and wanted me to get more updates.  When I did, it said my system was up to date.
 
I re-booted a couple of times hoping it might clear up the problem but it did not.  The I shut down the machine for the afternoon to do some other stuff.
 
Now I cannot boot the laptop in any mode.  I get the following message:
 
-----------------------------------------------------------------------------
Windows Boot Manager
 
Windows failed to start.  A recent hardware or software change might be the cause.  To fix the problem:
 
1. Insert your Windows installation disk and restart your computer.
2. chose your language settings, and click "Next."
3. Click "Repair your computer."
 
If you do not have this disk, contact your system administrator or computer manufacturer for assistance.
 
File: \Windows\system32\drivers\NIS\1002000.007\SYMEFA.SYS
 
Status: 0xc0000098
 
Info: Windows failed to load because a critical system driver is missing, or corrupt.
----------------------------------------------------------------------------------------------
 
I really don't want to wipe the hard drive and start again.
 
I have been satisfied with Norton products for about 20 years now and I hope you can help me with this.
Kudos1 Stats

Re: Vista crash logs point to SYMEFA.SYS

Hate to be the bearer of bad news, but I had to uninstall NIS09 from my system in order to get it to load up normally.  I also had those critical errors.  My only recourse was to enter in Safe Mode and uninstall NIS09.  Right after that?  My computer booted up normally!!!

Don't believe the hype of what previous members have said.  This *IS* a Norton problem.  That they fail to acknowledge it is, to be honest, deceitful.

Unlike you, I am in the process of taking off Vista and installing XP 64.  I hope to have better performance and stability.

And for the record, although I asked for a PM on the "solution" to the problem, I never received one.  The true solution is to disable or uninstall the buggy thing.

Kudos1 Stats

Re: Vista crash logs point to SYMEFA.SYS

As I mentioned, I am unable to boot in any mode.

I am concerned that my only recourse will be to wipe the hard drive, reinstall Vista from scratch, and purchase an anti-virus product from another company.

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Worse news, I just spoke with Norton tech support and they say I have to do a complete system restore to factory condition. 

I chose my name because Norton Ghost did the same thing to me 3 years ago and I still use Norton products. 

I installed NIS 2009 Dec 1 2008, and yesterday after a month of NIS use when firefox dissappeared and I tried to reboot I could not.  The windows startup utility found FileC:  \Windows\system32\drivers\NIS\1002000.007\SYMEFA.SYS was corrupted.

Naturally when the Vista utility found it was a Norton file it being a windows utility it was unable to fix a norton problem.  I even tried putting the Norton CD in and great news I have no viruses.  I thought I could use it as a boot disc, but NO. Why does Norton add a boot file?

I tried it all, safe mode, system restore points, last known good configuration, I cannot boot up.  The deadly combination of Vista and Norton killed me.  Now I have to start from scratch after two years.  Thanks Norton.

I was extremely mpressed with Norton tech support, unfortunately they could not help.  I would guess unless more people have this problem no fix will be made.  

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

At least the restore to new worked, now I am having the fun of restoration.
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

I disabled idle time scan. I am still having the repeated BSOD with the log saying it is caused by symefa.sys.

Please find a solution quickly. This is horrible.

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Me again. Saw someone else said they tried to open Windows Minidump files. can someone tell me what software to use to open the dump file? Thanks

I tried, computer said didn't know what program to use, clicked on Microsoft help, and Microsoft said this about dump files:

"Windows has the following information about this file type. This page will help you find software needed to open your file.

File Type: Unknown

Description: Windows does not recognize this file type. "

Brilliant! It is their bloody file.

Sorry getting grouchy dealing with this computer problem since midnight last night.

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

The short version is that to resolve the problem, I have wiped the hard drive clean and started again from scratch. The 1st time I started with a clean hard drive, loaded Windows Vista Ultimate, loaded Office and most of my other applications, transferred all my data, and ran the system for about 2 weeks.  As I mentioned in an earlier post, I was impressed with Vista and how fast and stable it was.  Then after about 2 weeks, I loaded NIS 2009 and immediately started having problems.  After I Shut Down the system I could not re-boot, in spite of following the recommended solutions. So, the 2nd and current time, I wiped clean the hard drive and started again from scratch.  Very painful. I re-loaded Windows Vista Ultimate and ran it for about 24 hours to make sure it was stable.  Then I re-installed NIS 2009 and ran it for about 24 hours to make sure it was stable.  Then I re-loaded Office and some of the other applications.  So far, everything seems ok but I have not finished re-building my system. Perhaps NIS 2009 is affected by the order of the software to be installed and wants to be installed immediately after the OS. 
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Symantec is researching this issue, but needs additional information. If you would like to assist Symantec in its research please email Tony Weiss to get access to the information and test files (his email address is listed on his profile).
Kudos1 Stats

Re: Vista crash logs point to SYMEFA.SYS

Hi,

I've been getting the BlueScreen issue (with error msg. including SYMEFA.SYS file) on my HP Pavilion DV6226us laptop since 2 days and each time it used to automatically restart the laptop and I was going mad to understand whats wrong with the laptop suddenly. Spending hours and hours online to see the cause and solutions, I've tried many recommended option that were suggested by different people but didnt help. At last, my wife got to this site luckily and pointed to a similar concern raised by other people and the recommended solution was to deactivate Idle Time of Norton Anti-Virus 2009. I've tried this option hoping it would work but unfortunately didnt prove me lucky.

After searching for more complaints in this forum, realised that one other option is to deactivate or uninstall Norton 2009 Anti Virus. Without thinking a moment, I decided to uninstall the Norton 2009 and this is the best decision I've taken and I'm now very happy to send you all this msg. from the same laptop and I'm writing this after observing the laptop for about 2 hours and it didnt show me the BlueScreen error so far and hope it wouldn't. One more thing is that I recently upgraded my Norton from 2008 version to 2009 and hence the bad story started there I believe. So, I'm now pretty sure that Norton has to own this issue and try to see if their new release (2009) has any loop holes that needs to be fixed.

I've never had any complaints against Norton but this is the first time I'm writing unwillingly something pointing my finger at Norton.

Santhosh

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Yesterday had unrelenting BSOD for SYMESFA.sys.   No new hardware attached.  Installed new driver and synch software from Sprint for new Samsung Instinct cell phone 3 days ago. Tried using multiple system restore points for up to 1 month prior without success...still receive same BSOD.

Took in to locak technican shop. Logs point to NIS2009 per technician.  Booted into Safe Mode and deleted NIS2009.  System rebooted without problem.

Have just re-installed NIS but am worried about another incident.

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Hi baconchip and santhosh,

I have contacted you through email about this issue. Please let me know if you are able to help. Thanks!

Tony Weiss | Norton Forums Global Community Manager | Symantec Corporation
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Since you upgraded from NIS 2008 to NIS 2009 take your NIS 2008 CD and reinstall 2008 and use your 2009 code so you will have the remaining subscription from 2009 on your safe 2008.  That is what I have done and I am happy with 2008.
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

I just started having this same problem today.  Vista OS about 1 year old and have had NIS 09 installed for over 2 months - it's been working pretty good until now.  Anyone come up with a usable solution?
Kudos1 Stats

Re: Vista crash logs point to SYMEFA.SYS

yeah, uninstall it

i'm being serious with you.

uninstall NIS09, reinstall it but disable idle time scan.  

NIS screwed up my system so bad, the only thing I could do was uninstall it, reformat my computer, reinstall Vista with SP1 to get it operational.  After that, I reinstalled NIS09, took the advice of some of the previous posters and disabled idle time scan, and so far, no problems.  I'm somewhat skeptical that this is a permanent solution, so I have been backing up my work just in case.

Norton really dropped the ball on this one.
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

I've never had idle time scan enabled...so I don't know if that will help in my situation.
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Hi RC,

I've sent you a private message.

Sharon Anschultz, CISSP

SQA Analyst

Symantec Corporation

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Moved dumdum;s post to a new thread of it's own for better exposure.
Kudos1 Stats

Re: Vista crash logs point to SYMEFA.SYS

Sharon Anschultz, care to explain why i never got a pm after asking for one?

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Hello,

I am seem to be having the same problem as many have described above. My laptop  (Dell Inspiron 1525, the OS is Vista Home Premium began to give me a blue screen of death every seven or eight minutes two days ago. As in jeffthielen's original message, I can go for longer if I am active, but I found running a full system scan with Norton Internet Security would trigger the screen as well. The blue screen says the culprit is the same symefa.sys.

The computer was doing something similar back in December and January when I first received it, but never so frequently. The last time it happened before was January.

Has anyone found a solution for this? Deactivating idle time scan did not work, so I have for the moment uninstalled. (Only 45 minutes on right now, but no reboot.)

Thanks,

   ---Marcos

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Marcos, which Norton product and version do you have? AntiVirus or Internet Security? 16.0, 16.1, 16.2 or 16.5? The version number can be found under Help & Support->About...

From your description of the problem, it probably is fixed in the 16.5 releases.

Reese AnschultzSenior Software Quality Assurance Manager, Symantec Corporation
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

  Reese,

  Thanks for the reply. Since I uninstalled the program, I can't see what version it is anymore. Any suggestions on how to find out?

   ---Marcos

Kudos0

Re: Vista crash logs point to SYMEFA.SYS


MBG26 wrote:

  Reese,

  Thanks for the reply. Since I uninstalled the program, I can't see what version it is anymore. Any suggestions on how to find out?

   ---Marcos


How did you install it initially? If from CD, it should tell you whether it's Norton Internet Security or Norton AntiVirus. If you purchased online, it should be indicated by the receipt. Once you know whether you purchased NIS or NAV, you can downloaded the latest version from the Norton Update Center and use the key that you original received to install that 16.5 version.

Reese AnschultzSenior Software Quality Assurance Manager, Symantec Corporation
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

  Hi Reese,

  Thanks much! I downloaded and installed version 16.5 this morning and things have been running fine since then.

  Best,

  ---Marcos

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

This SYMEFA.SYS BSOD occurred about 24 hours (maybe the 3rd boot) after I re-installed Ghost 14,  My laptop had been running under Home Premium but I installed and upgraded to Ultimate last October.  I usually update NIS daily first from the Symantec web-site and follow-up with the auto routine in NIS.

Interesting - it seemed to progressively get worse.  By that I mean the first instance after I went to Safe Mode and back it worked for about 5 minutes, then POOF!

The BSOD message pointed to SYMEFA.SYS and also said it occurred in a non-paged area.

Second time boot lasted about 2 minutes.  Starting to look like a RAM issue, but check is still OK.

Now........since this morning.......no chance for regular boot and only Safe Mode.  Microsoft recovery diagnostics memory check report still OK.  Uninstalled Ghost.  Restored system settings to a week old.  No luck.

There must be a fix for this since it is obviously a security issue between Norton and Vista.

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Hello All

Could anyone tell me how I am supposed to apply "the patch" when I can't run in anything but Safe Mode anymore?  I cannot do installs and I want that to be the 2nd to last straw before I to have to uninstall NIS.

Looks like I might be going to a different A/V if this is not cleared up soon.  This "glitch" has been floating around since last Fall 2008. 

No.......... it is not a feature.....

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

After finally clearing out all remnants (other than subscription account and password, etc.) of NIS 2009 I started fresh and installed 16.5 from scratch.  This problem has been occurring on my Turion64 laptop with 1.5 GB RAM.

SAME PROBLEM.  16.5 HAS NOT FIXED THE ISSUE AS STATED

I believe it is a RAM issue that attempts to go to an address beyond paged memory and may require a minimum 2GB installed, as my desktop with 2GB (and Intel) has not had this issue arise.

Tom Urich

Common Sense Consulting

Wiesbaden, Germany

Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Tom, thanks for the update. We have been unable to reproduce this problem in-house. If you are interested in helping us diagnose this problem, please see the previous message regarding contacting Tony Weiss.
Reese AnschultzSenior Software Quality Assurance Manager, Symantec Corporation
Kudos0

Re: Vista crash logs point to SYMEFA.SYS

Hi, I had a similar problem running XP, spontaneous rebooting and a bluescreen message pointing to SYMEFA.SYS. Symantec online help diagnosed file corruption as the problem, downloaded and used the Norton Removal Tool and reinstalled NIS09. That sorted the problem and my PC is a lot faster. Hope this helps

This thread is closed from further comment. Please visit the forum to start a new thread.