I've experienced a lot of BSOD's when NIS get update 21.1.0.18. After lot of attempts with NRT I'm currently on 21.0.2.1 because is impossible to work with latest update (BSOD) I've able to go only in Safe Mode
BSOD occurs after login screen with this:
IRQL_NOT_LESS_OR_EQUAL
Technical Information: *** STOP: 0x0000000a (0x0000000000000000, 0x0000000000000002, 0x0000000000000001, 0xfffff800032cb86f) *** ntoskrnl.exe - Address 0xfffff800032c2540 base at 0xfffff8000324e000 DateStamp 0x521ea08b
I'm able to reproduce this. Luckily I have older system image and I can revert back to older point but it is interesting that before reverting my sistem Norton was 21.1.0.18 without problem. After restoring my system and after restart (after Norton update) this happens.
Windows 7 64-bit SP1
i5 4670K, 8GB RAM @1600, Asus Sabertooth Z87
RAM and disks checked (RAm with Memtest86+)
In all this years this is my first big issue with Norton.
Hi @LazarusLong, are you able to get Full Memory Dumps? I've sent you a private message as well, with upload instructions. Please let me know if this is possible. Thanks.
Unfortunately I revert back my system with Acronis because of other issues with game (FSX)
But always and with no exception system get BSOD after update to latest version.
For example after I click on Apply Now (for patach) Norton will apply and everything is okay until reboot. After reboot and after login system seems to be almost booted and on some point will BSOD.
And always with IRQL BSOD
I didn't find other driver in stack who will point to Norton driver. Curently I'm on 21.0.1.3 without any problem and I'm wait for update with fear of BSOD.
Because I'm Symantec "veteran" I exactly know how to proper uninstall Norton AV/NIS
Here is my steps (allways perform)
Uninstall via Add/Remove Programs
Restart
Run NRT
Restart
Run NRT
Restart
Perform cleaning of remaining Symantec drivers in Device Manager in Non Plug and Play Drivers (this is possible if you add ShowNon Presnt Devices variable)
Restart
Delete folders or files in Program data, Program Files and Users
Restart
Install New version > Live Update > Quick Scan
Restart
Live Update again > Success
And now, after I've spend almost 6 hours to resolve this issue I'm certain that this is issue with update. Nothing is unusual with my system. I haven't virtual devices, my system is not overcocked, there is no start up programs who will colide with other part of AV (except Gadgets, Realtek driver, Nvidia service etc.)
As I say, I'm 99,9% sure that this is patch issue.
Sounds like he didn't remove or uninstall it -- just reverted back to a disk image he had created before updating to the newest update. Smart move.
Yeah
After spent 6 hours to resolve this with no sucess I've reverted back to 2 day older system image. I always make system images before something big (driver, AV, big and untested program..)
This is more faster for me than fixing problems all day.
Just my 2 cents - 21.1.0.18 is on limited release - basically Norton is checking on some systems randomly selected to see how well it works. My guess is that is the reason Tony is interested in the Full Memory Dumps - in order to try to have the solution to the situaton discovered and hopefully fixed prior to the worldwide release of 21.1.0.18.
On second thought, I just reread your initial post and you stated:
"I'm able to reproduce this. Luckily I have older system image and I can revert back to older point but it is interesting that before reverting my sistem Norton was 21.1.0.18 without problem. After restoring my system and after restart (after Norton update) this happens."
Please correct me if I am wrong, but it sounds like you had successfully upgraded to 21.1.0.18 and all was fine "without problem" prior to revertting back to the older system image. You restored (I assume to 21.0.2.1), and then updated to 21.1.0.18? How are you updating to 21.1.0.18 - have you received the update from Tony - curious as it is not available to everyone via LiveUpdate.
I may be missing a point somewhere, but I recall this is a 2 part update - you first receive the engine update (which we should already have) and then after the test release is accepted as good, then the 2nd part of the update is released to everyone. I am wondering if perhaps the "restored 21.0.2.1" does not have the engine update included and when you try to update to 21.1.0.18 the engine is mising - causing your situation.
When you restored, did you run LIveUpdate ( to catch up on the couple of days of updates that were not included in the image) prior to attempting to update to 21.1.0.18? The engine update may have occurred in those couple of days - and thus it may be missing when you attempt the update.
I hope you can follow what I am suggesting may be going on,
Please correct me if I am wrong, but it sounds like you had successfully upgraded to 21.1.0.18 and all was fine "without problem" prior to revertting back to the older system image. You restored (I assume to 21.0.2.1), and then updated to 21.1.0.18? How are you updating to 21.1.0.18 - have you received the update from Tony - curious as it is not available to everyone via LiveUpdate.
You're not wrong. I've noticed if (maybe) Norton updates itself (silently) will be no problem. Here is what I've done:
Situation 1:
Norton self updated to 21.1.0.18. No problems! Some other problem with FSX and I must revert system with image.
Situation 2
After success system recovery with image 2-3 days old (with Norton 21.0.2.1) on it I updated manualy via LUA to 21.1.0.18. Apply Patch > Restart > Login screen > boot is almost finished with all sys tray icons (and Norton) just one more gadget and BAM!! > BSOD
- Uninstall with NRT > restart > No BSOD
- Install > update > BSOD
- Safe mode > Uninstall with NRT > No BSOD
- many attempts and going in circle
As you see update is get via LUA. On, maybe 3rd attempt with sys. restore from image Norton "decides" to update only to 21.0.1.3 and now I'm in fear.
P.S
It doesent mater if I chose "Apply later" for this patch.
What are you calling LUA? The LUA I know of is a Limited User Account - are you perhaps calling Automatic LiveUpdate LUA? Is it by chance the donwload Tony sent you?
What are you calling LUA? The LUA I know of is a Limited User Account - are you perhaps calling Automatic LiveUpdate LUA? Is it by chance the donwload Tony sent you?
What are you calling LUA? The LUA I know of is a Limited User Account - are you perhaps calling Automatic LiveUpdate LUA? Is it by chance the donwload Tony sent you?
My bad. I mean LU not LUA
LU for Live Update
LUA was LiveUpdate Administration Utility
Thanks for the clarification.
My guess would be that your system was actually using a cached download to update to 21..1.0.18 the first couple of times you ran LU. That is how you were getting it as it is not avaiable on the LU servers at this time. 21.0.1.3 is one of the available LU updates on the server. I do believe you will be fine with that and until such time as 21.1.0.18 is released worldwide , you will not receive that update via LiveUpdate.
Curious about your answer for peterweb's question.
Is it possible that your Some other problem with FSX could be related to a Windows update?
Windows Update works just fine. FSX is not "connected" with Windows Update in no way (my problem with FSX was with incompatibility with FSX add-on)
[edit]
This attached log was in C:\ProgramData\NortonInstaller\Logs\2013-10-16-15h32m58s
Please see this (in log)
2013-10-16-15-32-58-764 : 0x0120 : Information : Instance GUID: 5D94BEA3-D87A-4286-BB63-604D9B38986A 2013-10-16-15-32-58-764 : 0x0120 : Information : Product Version: 21.0.1.3 2013-10-16-15-32-58-764 : 0x0120 : Information : Target Version (registry): 21.1.0.18 (new) <<<<
My question was not whether Windows Update was working, but whether the particular update in the thread I listed might be an issue for your system?
As the user in that thread found, what appeared to be a Norton problem, was in fact a Windows Update that was installed around the same time as the Norton update. Coincidence...and timeing is everything.
I fear you misunderstood my post in http://community.norton.com/t5/Norton-Internet-Security-Norton/Help-NIS-Update-Has-Led-To-The-Blue-Screen-Of-Death/td-p/1034473/highlight/true (probably caused by my bad English - sorry!).What I wanted to tell was, what the uninstallation of the windows update stopped the blue screens what happend after upgrade from NIS 13 to NIS 14. But the windows update is already from february 2013. So for six months my computer run with this update in combination with NIS13 without any problems. Six months later - after the upgrade von NIS13 to NIS14- the blue screens started. This problem could be solved by uninstalling the 6 month old windows update. This solution I found in the German Norton Community.
One user spotted, that the six months old windows update have had caused blue screens at computers with switchable graphics. But not at mine and not at the one who posted in the German Norton Community. Although we both have switchable graphics we faced the problem six months later after the NIS upgrade! He tried to uninstall the old windows update cause he has a switchable graphic and managed to stop the blue screen this way.
So for us the problem started with changes in the new NIS14 (V 21.0.1.3. In Germany we got until now no update to V 21.1.0.18 yet)
It could still be applicable to this thread if the user has switchable graphics.
It is still hard to lay blame, as it could be the Windows update interacting with the hardware on your system jin some way Norton was not expecting. So is it Windows, the hardware manufacturer, or Norton?
Another example of the challenge for any software developer to make their product compatible with the millions of combinations of hardware and software in the world.
Another example of the challenge for any software developer to make their product compatible with the millions of combinations of hardware and software in the world.
I don't blame Symantec for this but if I have to be 100% sure that this is Windows/hadrware or Norton issue I have to:
"freeze" my current installation with imaging program
perform clean installation of Windows + updates + drivers
install NIS 2014
But for this I haven't time.
On other hand NIS 2013 has/is working on my machines without problem. Some of that machines are on AMD and some on Intel chipset, with plenty of different hardware and I haven't any problem (except with early versions of NIS and delayed sys. tray icon but this is fixed)
And now I will not blame Symantec. This kind of issues isn't rare with big vendors like Microsoft, Adobe...
Miracles can happen. Today after restart and without any interaction from my side, with Live Update, I sow desktop.ini and NIS (desktop) icon "displaced" on other part of my screen.
Instantly I knew that there is a new version and I was right > Norton updates "itself" to 21.1.0.1.8 withot any problem or BSOD.
This problematic part with BSOD is solved but....
........ now system tray icon is delayed for about 2 minutes and in this time I can't use Outlook. If I set boot time protection to Normal or Agresive boot time will increase for plus 15 second (before was 35 sec.)
Now what? I must sufer with slowly boot times and/or I must wait 2 minutes to use Outlook.