Hi, motorfingers. Here's some info on the 3038,104 issue again, although I don't know if it will help, as it's been happening for a while.
https://support.norton.com/sp/en/us/home/current/solutions/v63797269_EndUserProfile_en_us
If this problem continues a chat with Support, might be worth considering. http://www.norton.com/chat
motorfingers11
I cannot remember a computer of mine ever losing more than a second on the system clock. Your purchase of a refurbished MB does not guarantee a new battery was installed. You could contact the vendor to ask the question, or for a few bucks you should just replace the battery and see if this fixes things.
F4E: The page you link to is the one that the auto-repair links to when the error occurrs. I followed that procedure a number of times before I started keepin a log and looking through Symantec support. Eventually I came here just as I was about to try the live support, figuring that e-mail works better because people have time to research a question before replying.
I did delete two copies of EppOobl.etl and rebooted. They did not come back.
peterwebb: Actually I have four CR2032's in my sight right now, one on top of a six-year-old number cruncher that I'm not using right now and three on top of its twin (which I am using), and my plan is to change the battery on the eight-core motherboard the next time I shut it down. I don't recall tracking the time drift of my computer before but 15 seconds a day is about the spec of most inexpensive 32768 Hz time clock crystals. My old Accutron drifts about 3 sconds a month but it has a $200 clock crystal in it. The motherboard is an Asus 990FX R2.0. But I think I have a software or configuration problem.
It turns out that the CR2032 battery is under the video card. Since the clock is in spec and not acting wierdly, I'll go to online support before I pull it. My experience with lithium battery backup batteries is that they never change so long as the computer is on or even plugged in, if the power supply has a backup 5 Volts to the motherboard for keep-alive when shut down. Only when you turn off the power supply or unplug the computer does the backup battery come into play, to keep the CMOS memory from losing its data and usually to keep the system clock running. I replace them every 5 years just to make sure.
Next step: long session with online support, probably tomorrow.
Hi, motorfingers. It could well be a software/hardware issue, but have you tried synching with the atomic clock ?
http://www.makeuseof.com/tag/pc-times-match-atomic-clock-sync-windows/
F4E: I moved my default Windows web syncrhonization from time.microsoft.com to time-b.nist.gov. When I found out that this synchs once a week, I started using nisttime-32bits.exe every morning to synch with time-b.nist.gov using NTP. Nothing changed; it gets a 3038,104 error every two to four days. Lately I haven't been correcting the clock and nothing changes. I don't think it's the clock.
I found that EepOobe.etl did come back, both the copy in C:\Program Data\... and the copy in C:\Users\... which I'm leaving alone. I'm not seeing the OOBE error in the event viewer now. I'm hoping that this will help but time will tell.
I am having the same problem with Norton 360 Premier Edition 21.3.0.12.
I have tried the KB, date/time fix, running sfc /scannow, Nortons' FixIt from the support menu, running Malwarebytes and so far no solution but other than a reboot and trying within 30 minutes to start the scan.
I am running Windows 8.1 U1, and wondering if this could be the cause as I am also seeing other funny side effects of upgrading to 8.1U1 such as Event Log configuration errors which are known to be related to the upgrade.
EDIT: Only scanning seems to be affected. I attempted to download the EICAR test file, and AutoProtect stepped in.
EDIT: Malwarebytes has found nothing which is very odd, as I have downloaded a couple of things that should have been flagged. Norton picked them up as I need to white list these files.
One of the Norton gurus recommended Malwarbytes and SuperAntiSpyware.com, and I got both. I find that Malwarebytes is fast, simple, rarely has a false positive, and effective if you miss-click or you find yourself on a loaner computer rife with adware. SuperAntiSpyware will have a few false positives but will flag nuisanceware, which SuperAntiSpyware and Norton do not. SuperAntiSpyware have a perfectly usable version that does not use a process or do auto-updates, but that you can update the defiitions yourself with a mouse click, and it does full system scans. It has a pro version that does real-time checking and auto-updates like Norton if you need that, as does Malwarebytes. But I don't, and the lite versions are free for 30 days and inexpensive if you buy them.
I also use Web of Trust and Ghostery, so I'm unlikely to have a malware problem. But some good sites (CPUID in my case) have ads for malware on them that you can click accidentally.
Since I last posted, I had a 8920,201 (not 8920,308) and that Norton page recommended NRnR.exe, which I ran. Both copies of EepOobe.etl are back but I am not getting the errors attributed to that file in the event viewer, so that is a good thing. Since I re-installed and booted more than once, the two-day clock started late last night.
motorfingers11 and others
If you are going to use Malwarebytes or Superantispyware be sure you only use the FREE versions. Do not use or activate any trials of the Pro versions as they have realtime scanners installed that could conflict with your Norton product and actually reduce your protection.
Just use the free scanners on demand when you feel you need an extra scan.
I had another 3038,104 tonight, dashing my hopes that another NRnR.exe re-installation would do the trick. I went into Norton Chat and got remote medical assistance for my installation and, after trying all the usual things, the tech did some things that weren't on the screen and then assured me that the problem was gone. Probably due to "bonded locksmith" type information, he didn't disclose what was done. If this holds for four days, we will declare the solution to be going to Norton remote support.
Watch this space on June 7. If I don't get another 3038,104 by then, I will post a victory message and declare a solution.
Whoops, had another one this morning. Case number is [Removed]. I'll get back on the online chat sometime today and see what they do for the next layer of the onion.
[Edit: Masking case ID to conform with the Participation Guidelines and Terms of Service]
motorfingers11 wrote:The system is about three months old. The system clock synchs automatically with time.windows.com "on a scheduled basis." I can't get any more information than that from the system. When I try to change the service to time.nist.gov I get an error, "Your changes could not be saved."
I moved the HD over from the old system; the motherboard died. I'm now running on an AMD 8-core CPU that runs at 4 GHz. Motherboard is an ASUS Sabertooth 990FX R2.0, processor AMD FX8350. I can provide just about any information you need if you just ask. For example, if you direct me to look for a specific error in the system log, I can do that.
The battery isn't old because I got a refurbished motherboard on warranty, meaning that it had the undivided attention of a tech shortly before i got it. I can change the battery if that is something that you think I ought to do.
If 15 seconds is enough to glitch out Norton 360, then I will try synching with time.nist.gov (I have an old stand-alone utility) every day. I agree that five or ten seconds a day is a bit much for a system clock.
If this was the system drive, just moving it into a system with a different motherboard is asking for troubles with drivers for the hardware on the MB.
Usually a new motherboard requires a fresh install of Windows. If you do not do this, there is no telling what bad effects you may see.
I thought about that a lot. The new motherboard is UEFI and the old HD is from 2007, I believe, migrated via Acronis from an original 1 TB under Vista that died to another 1 TB, then to a 2 TB. At the time the motherboard died the system drive was 2 TB and there was a 2 TB RAID and a 3 TB RAID. But the new UEFI BIOS is backward-compatible. I could use Acronis to move my system drive, with no drivers, to a UEFI-initialzied 2 TB empty HD and I may do that eventually.
As for the sound drivers and such, Windows Vista and later (I use Windows 7 64-bit) does a "check hardware for changes" and "update drivers" every time you boot, and all the SATA 3,RS-232, and USB III cards had all gone with the old motherboard because the new one needed nothing but a video board, which was new. The only drivers that changed were the sound drivers. I installed the video drivers from DVD as well asall the motherboard drivers, including of course the sound drivers.
The external RAID boxes have their own drivers that Windows Update maintains. I changed one of them, with its drivers, after I changed the motherboard (and case, and video card).
The problems with the Norton 360 errors, mostly 3038,104, started after a couple of months. The computer change was in December 2013. I exchanged the motherboard (dead sound chip) in mid-January. The errors started in March or April. I started keeping a log in late March.
I didn't go back to the Norton online support yesterday because I needed the computer. I will do it next time it happens during business hours so the error is active and I can leave the Norton error screens up when I get the live support. I have a big presentation on the 26th and I'm generating material for it.
The error you see can be related to temporary server issues. There can be problems with any of the servers between your computer and the Norton Update servers.
Have you checked your Network drivers are up to date? It would not hurt to restart your modem and router to help eliminate those items.
I'm on Verizon FIOS, which uses an Actiontec MI424WR designed specifically for Verizon FIOS. I've never had a lick of trouble with it. I'll try resetting it and see if that changes anything.
I don't think it's the routing because LU works fine when the 3038,104 will do it again no matter what, until I reboot. Nothing else has a problem when the 3038,104 lurches into my space. That's why I want the error to be active when I go online with Support again.
No news is good news. I haven't had a 3038,104 since June 5, and it's June 14. Nine days is enough to conclude that the work done by the remote Norton assistance did solve the problem. The 3038,104 error on June 5 was probably a server-driven error, if that is the case, and those are rare and go away by themselves in a few mintues to a few hours. I'll check in here from time to time to make sure that you know whether the 3038,104 problem is truly solved. I'm not really ready to click the "Solved" button yet, but if you must, the post regarding going to Norton online support and getting remote assistance will exercise people who are familiar with this problem and know how to do things that they can't disclose for security reasons.
Fingers crossed all is fixed for you.
At nine days and counting, when two to four days between 3038,104 errors was the norm, it's not exactly tense anymore. Another 3038,104 would be a disappointment. I think that if it goes another week we can declare vicotry and name the online open-heart surgery by Norton as the solution.
Whoops, just got another one. System clock is 19 seconds slow. I'm leaving the clock alone and not rebooting over night to see if the problem persists.
motorfingers11 wrote:Whoops, just got another one. System clock is 19 seconds slow. I'm leaving the clock alone and not rebooting over night to see if the problem persists.
The system clock should not lose that much time. Please replace the motherboard battery. Then see if you get the errors.