This issue has occurred in the latest version of Norton 360 for windows.
Is there a hot fix being worked on?
Norton is able to recover, the program shuts down and reopens with the icon repopulating in the tray.
I just noticed it after the latest update and this post is for information about this issue.
It's only after you check to see something in Norton or run Norton manually that you notice it.
Good news. That same driver on my new HP laptop caused me issues upon issues. Thus the reason for my post here about OEM drivers:
https://community.norton.com/en/comment/8540266#comment-8540266
Always glad to help.
SA
Indeed, removing the Intel driver and reinstalling OEM from HP appears to have alieviated the issue. It has not crashed in an hour. Posting it here in the case anyone else sees this or maybe Norton support can learn from it. BIG THANKS to SA for you continued support in helping me track down the problem. You should work in support! 
I am running this same version on multiple PCs without the problem so I think it is likely NOT. I have been running insiders for years and only one hit a problem with Norton. In any case... BTW- I have two of the same model HP desktops running and this is the only one having the issue. However, I did key into something you said and am testing the hypothesis. I was running Intel ARC control for my video driver. It does apparently modifly the OEM video driver. That is the only difference between the two systems showing the error. I have uninstalled, and for the moment at least it seems to not have crashed again. I will update back here tomorrow if that resolved the issue (so others will know the problem) Thanks again SA for your help. Better than Norton support ;-)
Windows build is 25295.1000 just happens to be an insider build. That is more likely than not the reason for your Werfault issue. Norton does not support that its products will perform correctly on BETA OS builds.
https://support.norton.com/sp/en/us/home/current/solutions/v71210910
https://www.elevenforum.com/t/windows-11-insider-dev-build-25295-1000-rs_prerelease-feb-9.12521/
SA
This a new HP system running 12 gen cpu. I have scanned multiple times and no issue. I have upgraded to the latest version of norton, 22.23.11.12, exact windows build is 25295.1000 . Note I am running this version on multiple other systems with no problem. All OEM drivers are up to date.
Also the key to what is going on appears to be the exception code: Exception code: 0xc0000374. This is caused by heap corruption. What is heap corruption which is a known issue with Windows 11. Make sure ALL your OEM drivers are up to date.
https://answers.microsoft.com/en-us/msoffice/forum/all/exception-code-0xc0000374/bcde56c9-3077-4987-8286-10b7c3f1e68b
https://answers.microsoft.com/en-us/windows/forum/all/kernel-mode-heap-corruption/ba20ed6e-047d-4594-81f5-ebcf2e910339
SA
Here is my update with my Windows 11 Home 22H2 machine: NO WERFAULT issues at boot-time.
Before updating the system: Windows is Home 22H2 build 22621.1105 / Norton 360 was version 22.22.11.12
Updated Norton 360 first. There was 1 patch available, which brought the version to 22.23.1.21 with the patch install and reboot. After reboot there were no more updates or patches available. This is the latest N360 version that was presented.
Windows Update run #1 : Installed KB5022404 / KB4023057 / 1 Intel and 2 HP chipset driver updates. Rebooted and the Windows build remained at 22621.1105
Windows Update run #2 : Installed KB5022360 and rebooted. Windows build changed to 22621.1194
Windows Update run #3 : No more update were available, performed a final reboot for good measure.
Performed a manual quicks scan which completed without any issues.
Checked N360 history for any log entries I may not have seen, there aren't any issues recorded.
Checked System Event Viewer logs: NOTHING is logged there
** Throughout the entire process there were no notifications presented or otherwise that are related to WerFault.exe or ntdll.dll
Stumped as I am at the present time, please confirm that you have scanned your system to ensure there isn't any funny business going on under the hood. I also have to ask whether you are running W11 on unsupported hardware as well.
SA
Pardon me for being redundant but what is your exact BUILD in Windows 11? Personally I am behind with updating my Windows 11 machine due to other pressing things going on so I cannot say yeah or neigh as to whether my current builds of Windows and Norton do not have the same issue. I will check this evening for you so we have a comparison.
Have you scanned the computer with other software to ensure you have a clean image?
For Windows: https://www.malwarebytes.com/
Since you have removed Norton, did you do so using the R&R tool and doing a "removal only" scenario and a reboot? Then manually search for ALL folders in Windows related to Norton and manually remove them. There will be some left. Restart.
https://support.norton.com/sp/en/us/home/current/solutions/v60392881
To only remove your Norton device security product, click Advanced Options and then click Remove Only. Pay close attention to step # 5 in the Norton article.
If you are downloading Norton from your account you SHOULD be able to get the latest version of 22.23.1.21. There will be more than one patch, I would restart as each patch is installed before going to the next one. That will complete the patch installation properly vice a reboot when you arrive at the latest version. Lets see if that latest Norton version release corrects this or doesn't.
SA
NOTE that I tried to unload ntdll.dll and replace on several other computers that are working fine with same level of software. Same error at noted above. regsvr32 does not work with windows 11 the way you noted. I also tried in safe mode. Same results.
I am not convinced the module is the problem, rather as you see in the details the norton .exe is causing the crash. See details. I will also note that I completely uninstalled norton.. ran for for a few hours and not a single error in the event logs. I reinstalled Norton and the error has resumed as has the crashing.
So what is next?
No problem with sfc scan before or after dism
unloading the module received the following error...
will try image repair now
I was not able to install the module either. Same error as above.
Thank you for the suggestions. I had run sfc and dism a month of so ago, with no problems reported. Will do so again. Thank you for the pointer. I will let you know how it goes.
I don't believe Norton is the cause of the crashing but is the after effect of it, ntdll.dll is the faulting module. Have you ran system file checker, sfc/ scannow, to have the OS detect and replace any bad files? Has DISM been performed to check the health of/repair the OS?
Repair Windows Update Errors:
https://support.microsoft.com/en-us/help/947821/fix-windows-update-error...
Repair a Windows Image
https://support.microsoft.com/en-us/help/947821/fix-windows-update-error...
https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/re...
I would also consider the below as a possible solution:
@Gayathri_R The Norton team looking at this would be much appreciated
SA
Hi SA.
Unfortunately I do no think this is a solution for me. I only have a single account used on this system, which is a microsoft live account. This account is the admin account and I do not log in with local account. Any other ideas? I know I need to call support just have not had time to spend hours with them on the phone with no results. It took me almost an hour with support logged on to my system to convince them it was even crashing.. even though it does so right in front of their eyes like 60 seconds after service is restarted. They then said they would raise to level 2 support. I received 2 missed calls over the weekend and they closed our the ticket as unable to reach me. As a former software developer and someone who manages teams of engineers it is sad to see this lack of support. I was hoping this forum was monitored by support.. but apparently not. Again, I appreciate your suggestions.. happy to try other things. It is odd. I disableed windows error reporting and it crashed with nothing listed in the norton history log. Still showed the repeated crashed in MS event viewer. I re-enable error reporting and it started crashing again imediately after the werfault.exe error stating " Unauthorized access blocked" The access is to NortonSecurity.exe. The service does sometimes restart but then crashes again minutes later. It finally stops trying to restart after a half dozen crashed.
Faulting application name: NortonSecurity.exe, version: 17.2.3.65, time stamp: 0x61f2cd8e
Faulting module name: ntdll.dll, version: 10.0.25290.1000, time stamp: 0xf827eb0c
Exception code: 0xc0000374
Fault offset: 0x000000000010d105
Faulting process id: 0x0x67A8
Faulting application start time: 0x0x1D937F156D3D5B1
Faulting application path: C:\Program Files\Norton Security\Engine\22.22.11.12\NortonSecurity.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 8e4122a2-eb04-4f7e-ac17-f6da3f147cb0
Faulting package full name:
Faulting package-relative application ID:
Log off ALL APPLICATIONS that are running, IF, there are other users with "local" non-admin accounts logged into the machine also log them off, then log out of Windows and perform a system restart.
Log back in under an admin account that uses a Microsoft account and its credentials. I've seen local admin accounts that do not use MS account logins cause issues that are similar. Log in once with MS credentials and see if there are any local permission issues causing ntdll.dll to crash when the service manager attempts to restart that service and its drivers.
SA
Yes, logging in as admin.
Just to ask you are logging into Windows with an account having admin credentials?
SA
I disable window error reporting. Now norton just terminates. No associated error. Nothing. Just terminate every 30 seconds or so. 
Hi. Yes I am see exactly the problem I posted in the thread being referenced. werfault.ext gets blocked access in the nortorn history log, then norton crashes. Happens every 60 seconds or so.. most times nortorn will not restart on it's own. I posted a thread with lots of snapshots of my problem here -> https://community.norton.com/en/forums/norton-360-constantly-crashing-every-60-seconds-after-blocking-access-werfaultexe#comment-8539113
There are a LOT of crashing events related to norton in the event log (applications). Is that what you are looking for. 
Here is another with more details
Log Name: Application
Source: Windows Error Reporting
Date: 1/24/2023 7:23:13 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: Robs-HP-Touch
Description:
Fault bucket 2279045703742407642, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: NortonSecurity.exe
P2: 17.2.3.65
P3: 61f2cd8e
P4: StackHash_e523
P5: 10.0.25281.1000
P6: 63e247a7
P7: c0000374
P8: PCH_65_FROM_ntdll+0x00000000000A10E4
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6d30cd85-3eda-401f-a886-c40568935a27.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d8fd639c-36bb-4587-8442-d79c61b305fd.tmp.WERInternalMetadata.xml
WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20230123_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.bb5a2540-dc41-4472-a29e-d9d7ffb1daf0.tmp.etl
WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.3253eb36-5476-4183-936c-1e53c6053127.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.be7db718-9dcb-4938-b178-4e73f3234628.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1035b9df-124e-48da-85b7-ed42ab0e7b4a.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.881108a3-0128-4736-b0fb-5747db2f3a18.tmp.xml
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_NortonSecurity.e_a33d3bd7995d0342e4cc944770c9e1544a1135_ef37af20_122a0059-a9ef-4b66-8505-50603445a279
Analysis symbol:
Rechecking for solution: 0
Report Id: c6df0cca-8cb9-451a-aa64-86af0d13fc65
Report Status: 268435456
Hashed bucket: 3f964eab99a1f21affa0cbfe1e7243da
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" Guid="{0ead09bd-2157-539a-8d6d-c87f95b64d70}" />
<EventID>1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2023-01-25T03:23:13.3517322Z" />
<EventRecordID>1371</EventRecordID>
<Correlation />
<Execution ProcessID="5732" ThreadID="11808" />
<Channel>Application</Channel>
<Computer>Robs-HP-Touch</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Bucket">2279045703742407642</Data>
<Data Name="BucketType">4</Data>
<Data Name="EventName">APPCRASH</Data>
<Data Name="Response">Not available</Data>
<Data Name="CabId">0</Data>
<Data Name="P1">NortonSecurity.exe</Data>
<Data Name="P2">17.2.3.65</Data>
<Data Name="P3">61f2cd8e</Data>
<Data Name="P4">StackHash_e523</Data>
<Data Name="P5">10.0.25281.1000</Data>
<Data Name="P6">63e247a7</Data>
<Data Name="P7">c0000374</Data>
<Data Name="P8">PCH_65_FROM_ntdll+0x00000000000A10E4</Data>
<Data Name="P9">
</Data>
<Data Name="P10">
</Data>
<Data Name="AttachedFiles">
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6d30cd85-3eda-401f-a886-c40568935a27.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d8fd639c-36bb-4587-8442-d79c61b305fd.tmp.WERInternalMetadata.xml
WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20230123_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.bb5a2540-dc41-4472-a29e-d9d7ffb1daf0.tmp.etl
WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.3253eb36-5476-4183-936c-1e53c6053127.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.be7db718-9dcb-4938-b178-4e73f3234628.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1035b9df-124e-48da-85b7-ed42ab0e7b4a.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.881108a3-0128-4736-b0fb-5747db2f3a18.tmp.xml</Data>
<Data Name="StorePath">\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_NortonSecurity.e_a33d3bd7995d0342e4cc944770c9e1544a1135_ef37af20_122a0059-a9ef-4b66-8505-50603445a279</Data>
<Data Name="AnalysisSymbol">
</Data>
<Data Name="Rechecking">0</Data>
<Data Name="ReportId">c6df0cca-8cb9-451a-aa64-86af0d13fc65</Data>
<Data Name="ReportStatus">268435456</Data>
<Data Name="HashedBucket">3f964eab99a1f21affa0cbfe1e7243da</Data>
<Data Name="CabGuid">0</Data>
</EventData>
</Event>
AND______________________________
Log Name: Application
Source: Application Error
Date: 1/24/2023 7:23:11 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: SYSTEM
Computer: Robs-HP-Touch
Description:
Faulting application name: NortonSecurity.exe, version: 17.2.3.65, time stamp: 0x61f2cd8e
Faulting module name: ntdll.dll, version: 10.0.25281.1000, time stamp: 0x63e247a7
Exception code: 0xc0000374
Fault offset: 0x000000000010d085
Faulting process id: 0x0xFB8
Faulting application start time: 0x0x1D9306C187722C9
Faulting application path: C:\Program Files\Norton Security\Engine\22.22.11.12\NortonSecurity.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: c6df0cca-8cb9-451a-aa64-86af0d13fc65
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
<EventID>1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2023-01-25T03:23:11.7876272Z" />
<EventRecordID>1370</EventRecordID>
<Correlation />
<Execution ProcessID="5732" ThreadID="11808" />
<Channel>Application</Channel>
<Computer>Robs-HP-Touch</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="AppName">NortonSecurity.exe</Data>
<Data Name="AppVersion">17.2.3.65</Data>
<Data Name="AppTimeStamp">61f2cd8e</Data>
<Data Name="ModuleName">ntdll.dll</Data>
<Data Name="ModuleVersion">10.0.25281.1000</Data>
<Data Name="ModuleTimeStamp">63e247a7</Data>
<Data Name="ExceptionCode">c0000374</Data>
<Data Name="FaultingOffset">000000000010d085</Data>
<Data Name="ProcessId">0xfb8</Data>
<Data Name="ProcessCreationTime">0x1d9306c187722c9</Data>
<Data Name="AppPath">C:\Program Files\Norton Security\Engine\22.22.11.12\NortonSecurity.exe</Data>
<Data Name="ModulePath">C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data Name="IntegratorReportId">c6df0cca-8cb9-451a-aa64-86af0d13fc65</Data>
<Data Name="PackageFullName">
</Data>
<Data Name="PackageRelativeAppId">
</Data>
</EventData>
</Event>
Hello Stepnup. Have you looked into the system event viewer for any information there regarding werfault.exe being blocked? The information there will be in greater detail and possibly reveal fault bucket info and additional error codes. To access Event Viewer select the keyboard shortcut Win+R, type eventvwr.msc and press the ENTER key. Please take a screenshot of anything you can find in event viewer for us to review. Follow this guide to post screenshots:
https://community.norton.com/en/forums/how-post-image-forums-0
Optionally you can disable Windows error reporting in system services then do a restart to see if the issue persists. Werfault.exe is nothing more than Windows error reporting so the error more likely than not is within the windows file system.
SA