• コミュニティ内すべて
    • コミュニティ内すべて
    • フォーラム
    • 提案
    • ブログ
高度

お探しの情報が見つからない場合、 フォーラムで質問してください。

このフォーラムスレッドには解決策が必要です。
拍手0

NIS v 22.8.1.14 crash in SYMHTML.DLL

Today, did a clean, fresh install of Norton Internet Security version 22.8.1.14 on a Windows 10 Pro 64-bit (OS Build 14393.576).

Just in one day I had 3 NIS.exe crashes related to faulting module SYMHTML.DLL.

The error reports

Faulting application name: NIS.exe, version: 13.1.2.9, time stamp: 0x57d1daa2
Faulting module name: SYMHTML.DLL, version: 10.3.0.30, time stamp: 0x57b505df
Exception code: 0xc0000005
Fault offset: 0x00082aca
Faulting process ID: 0x1714
Faulting application start time: 0x01d2682c8417a2a7
Faulting application path: C:\Program Files (x86)\Norton Internet Security\Engine\22.8.1.14\NIS.exe
Faulting module path: C:\Program Files (x86)\Norton Internet Security\Engine\22.8.1.14\SYMHTML.DLL
Report ID: 1eb8b1ca-ba30-4291-bdc3-91db43767485
Faulting package full name: 
Faulting package-relative application ID: 

Faulting application name: NIS.exe, version: 13.1.2.9, time stamp: 0x57d1daa2
Faulting module name: SYMHTML.DLL, version: 10.3.0.30, time stamp: 0x57b505df
Exception code: 0xc000041d
Fault offset: 0x00082aca
Faulting process ID: 0x1304
Faulting application start time: 0x01d26827b7a89dde
Faulting application path: C:\Program Files (x86)\Norton Internet Security\Engine\22.8.1.14\NIS.exe
Faulting module path: C:\Program Files (x86)\Norton Internet Security\Engine\22.8.1.14\SYMHTML.DLL
Report ID: 726cf618-c886-4f78-b30d-6747eac9500e
Faulting package full name: 
Faulting package-relative application ID: 

Faulting application name: NIS.exe, version: 13.1.2.9, time stamp: 0x57d1daa2
Faulting module name: SYMHTML.DLL, version: 10.3.0.30, time stamp: 0x57b505df
Exception code: 0xc0000005
Fault offset: 0x00082aca
Faulting process ID: 0x1304
Faulting application start time: 0x01d26827b7a89dde
Faulting application path: C:\Program Files (x86)\Norton Internet Security\Engine\22.8.1.14\NIS.exe
Faulting module path: C:\Program Files (x86)\Norton Internet Security\Engine\22.8.1.14\SYMHTML.DLL
Report ID: 8fbd60b7-a683-4b39-9d87-b3fac645b9c5
Faulting package full name: 
Faulting package-relative application ID: 

This is when they were created

  • Opened the Performance tab to view the Graphs: crashed NIS.
  • Opened the Performance  tab to open the Startup Manager twice: crashed NIS

Are more users experiencing this error (again) with the latest version of Norton Internet Security (version 22.8.1.14)? 

If so, is Norton Support aware of the issue?

NIS.exe dmp files are available.

Cheers,

Dave

返信

拍手0

Re: NIS v 22.8.1.14 crash in SYMHTML.DLL

Hello davepmiddleton

This is an old issue which was fixed by installing a patch. Please make sure that you have run Live Update several times manually with restarts as necessary until you have received all patches. You can also try restarting your computer several times to make sure everything gets settled in.

You can also try a fresh install of NIS. Remove NIS using the Control Panel method, restart. Then use the Norton Removal Tool and restart.

www.norton.com/nrt

Please check all folders are gone.

You can get a fresh install using this link.

www.norton.com/latestnis

You can get your key from your Norton Account.

Please run Live Update several times restarting when necessary. Keep doing this until you have all updates. Restart one more time. There should be a few patches to install also.

Thanks.

Please let us know how you made out.

Success always occurs in private and failure in full view. Windows 7 Pro 64 bit NSBU 22.17.0.183 Core Firmware 270 I E 11 Chrome latest one
拍手0

Re: NIS v 22.8.1.14 crash in SYMHTML.DLL

@davepmiddleton:

disabling fast startup is also kindly recommended. 

As for Norton-related remains, you need to make those hidden & protected items appear in your system, TEMPORARILY. Hit here to get easy-to-follow steps.

Thx and luck... :)

PUP Hunter PRO: Just TRYING to save the world (U) from cyber threats, A single blog post, at a time, and ONCE & FOR ALL. (A fan of Nadia_Kovacs)
拍手0

Re: NIS v 22.8.1.14 crash in SYMHTML.DLL

Thanks for the replies.

I am aware this was supposed to be an old problem. Moreover, I also performed a clean install using the Norton Removal Tool, so I was not expecting to see it back again in rapid succession.

Anyway, I will look into the Windows fast startup power setting option as a possible fix. 

In the meantime, no additional NIS crashes happened, so it may just be a freak incident.

Cheers,

Dave

拍手0

Re: NIS v 22.8.1.14 crash in SYMHTML.DLL

I had his problems, if you have the nVidia video card..the problems come from drivers! install the 368.81 drivers and your problems disappear

拍手0

Re: NIS v 22.8.1.14 crash in SYMHTML.DLL

Hello

I have an NVidia video card. I keep my drivers up to date. I have 376.33 driver which is the latest. I have had many different drivers since Norton fixed the issue long ago. If it was a driver issue, then it's not a Norton issue in that case.

Thanks.

Success always occurs in private and failure in full view. Windows 7 Pro 64 bit NSBU 22.17.0.183 Core Firmware 270 I E 11 Chrome latest one
拍手0

Re: NIS v 22.8.1.14 crash in SYMHTML.DLL

My Firefox used to crash and it said it was caused by SYMHTML.DLL but of course the Norton gurus denied it was Norton. I'm not sure what fixed it but it hasn't happened in awhile. I remember submitting several reports with links to the crash log from Firefox and no fix was offered. It just went away on it's own.

Windows 10 Pro 64-bit / Norton Security v.22.17.x
拍手0

Re: NIS v 22.8.1.14 crash in SYMHTML.DLL

Hello

This is when the last time this .dll issue was fixed.

https://community.norton.com/en/forums/nsbu-2260142-appcrash-symhtmldll?page=1#comments

Thanks.

Success always occurs in private and failure in full view. Windows 7 Pro 64 bit NSBU 22.17.0.183 Core Firmware 270 I E 11 Chrome latest one
拍手0

Re: NIS v 22.8.1.14 crash in SYMHTML.DLL

Thanks for the replies.

I suppose it was a freak incident as it hasn't happened again. I do have an Nvida card, so it may be related to a driver issue, instead.

With Windows 10, this will be a hard one to resolve until after the Creators Edition roll out. 

Cheers,

Dave

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