Alwil avast update.exe

2.au.download.windowsupdate. com idk if it's a mistake from Avast and that's actually a legit and trustable Windows 10 update or should I be worried? what do you guys think? the process related is ''svchost.exe'' and here's a capture of the full url + the process related
the Avast alerts came out of nowhere I wasn't browsing online or anything they just appeared .
https://preview.redd.it/txdgbnhzzi0d1.jpg?width=471&format=pjpg&auto=webp&s=442ab505a6190b00c4e33149c9691a0683ee597b

The launcher works as before, but when I hit play, the EU4 icon appears in the taskbar but soon disappears. I verified game files (on Steam), checked whether I had the correct version, and I own the DLC. I also tried launching the game from the eu4.exe in game files with the same results. Now reinstalling the game to see if it works. Anyone else having the same kind of problem?
EDIT: It seems that Avast needs to be updated. I was able to launch the game after doing that.

I'm at my limits with figuring out how to read the crash logger. If anyone knows how to compare this to my load order I would greatly appreciate it. I'll post the load order in a comment.
Exception C0000005 caught!
Thread: [FNV] Main
Calltrace:
0x0019F9C8 ==> FalloutNV (0x00B5B1CD) : EntryPoint+0xFFFFFFFF
0x0019F9D8 ==> FalloutNV (0x004AB057) : EntryPoint+0xFFFFFFFF
0x0019F9F0 ==> FalloutNV (0x004AB016) : EntryPoint+0xFFFFFFFF
0x0019FA0C ==> FalloutNV (0x004AAEB8) : EntryPoint+0xFFFFFFFF
0x0019FA18 ==> FalloutNV (0x004AAE5F) : EntryPoint+0xFFFFFFFF
0x0019FA24 ==> FalloutNV (0x00418E0F) : EntryPoint+0xFFFFFFFF
0x0019FA7C ==> FalloutNV (0x00868F36) : EntryPoint+0xFFFFFFFF
0x0019FAB4 ==> FalloutNV (0x0093C178) : EntryPoint+0xFFFFFFFF
0x0019FAE8 ==> FalloutNV (0x0086F954) : EntryPoint+0xFFFFFFFF
0x0019FB40 ==> FalloutNV (0x0086E765) : EntryPoint+0xFFFFFFFF
0x0019FEC4 ==> FalloutNV (0x0086B3E8) : EntryPoint+0xFFFFFFFF
0x0019FEE4 ==> nvse_steam_loader (0x100021E4) : EntryPoint+0xFFFFFFFF
0x0019FF74 ==> FalloutNV (0x00ECC470) : EntryPoint+0xFFFFFFFF
0x0019FF84 ==> KERNEL32 (0x10017BA9) : BaseThreadInitThunk+0x19
0x0019FFDC ==> ntdll (0x1006BE3B) : RtlInitializeExceptionChain+0x6B
0x001A0020 ==> ntdll (0x1006BDBF) : RtlClearBits+0xBF
0x00000000 ==> FalloutNV (0x0050005C) : EntryPoint+0xFFFFFFFF
Registry:
REG VALUE DEREFERENCE INFO
eax 0x00000000
ebp 0x0019F9C8
ebx 0x00000001
ecx 0x2B21A0D0
edi 0xFFFFFFFE
edx 0x2B21A0D0
eip 0x00B5B1CD
esi 0x49007900 0x010ADCF8 ==> Class: , failed to get string for label
esp 0x0019F9B8
Stack:
# VALUE DEREFERENCE INFO
0 0x00000000
1 0x004AB0ED
2 0x2B21A0D0
3 0x28BEA034
4 0x0019F9D8
5 0x004AB057
6 0x2B21A0D0
7 0x28BE9FF8
8 0x0019F9F0
21 0x19DB986C 0x0102E9B4 ==> Class: TESObjectCELL: 000DAD7A (Vault19)
22 0x19DF303C 0x0102E9B4 ==> Class: TESObjectCELL: 000E1BB3 (Wilderness)
27 0x3A0BE270 0x0102F55C ==> Class: TESObjectREFR: 0013BDB2 (), Baseform 000B044E (SewerLidExit01NoMinUse)
2D 0x19DB986C 0x0102E9B4 ==> Class: TESObjectCELL: 000DAD7A (Vault19)
36 0x185B8578 0x0108AA3C ==> Class: PlayerCharacter: 00000014 (PlayerRef), Baseform 00000007 (Player)
3C 0x2003F9C0 0x010C49C4 ==> Class: bhkCharacterController: Name: ""
4F 0x3848D420 0x01037094 ==> Class: Script: 42005808 (JLMCloseContainerUDF)
5B 0x011F71A8 0x010A42B4 ==> Class: BSSystemUtility
6E 0x0D000CB0 0x010472D0 ==> Unhandled: BSSimpleArray
7B 0x0D000CB0 0x010472D0 ==> Unhandled: BSSimpleArray
7C 0x0D000CB0 0x010472D0 ==> Unhandled: BSSimpleArray
9C 0x76F666F4 0x6B6E696D ==> String: "minkernel\ntdll\ldrapi.c"
9E 0x76F667BC 0x7072644C ==> String: "LdrpLoadDllInternal"
A0 0x76F66754 0x74617453 ==> String: "Status: 0x%08lx "
A7 0x0019FDD0 0x66657250 ==> String: "Prefs.ini"
B6 0x76F666F4 0x6B6E696D ==> String: "minkernel\ntdll\ldrapi.c"
B8 0x76F66778 0x4C72644C ==> String: "LdrLoadDll"
BA 0x76F66754 0x74617453 ==> String: "Status: 0x%08lx "
E7 0x01082860 0x6C6C6146 ==> String: "Fallout: New Vegas"
F3 0x0019FDA0 0x4F5C6F72 ==> String: "ro\OneDrive\Documents\My Games\FalloutNV\FalloutPrefs.ini"
F4 0x0019FDA0 0x4F5C6F72 ==> String: "ro\OneDrive\Documents\My Games\FalloutNV\FalloutPrefs.ini"
F5 0x0019FDA4 0x7244656E ==> String: "neDrive\Documents\My Games\FalloutNV\FalloutPrefs.ini"
Memory:
MinimumWorkingSetSize: 200.00 KB
MaximumWorkingSetSize: 1.35 MB
PeakWorkingSetSize: 1.12 GB
WorkingSetSize: 1.06 GB
QuotaPeakPagedPoolUsage: 1.15 MB
QuotaPagedPoolUsage: 885.43 KB
QuotaPeakNonPagedPoolUsage: 876.07 KB
QuotaNonPagedPoolUsage: 91.81 KB
PageFaultCount: 3.98 MB
PagefileUsage: 1.24 GB
PeakPagefileUsage: 1.30 GB
Module bases:
0x74BA0000 - 0x74BB5000 ==> aswhook, C:/Program Files/Avast Software/Avast/x86/aswhook.dll
0x5ED90000 - 0x5EDB1000 ==> CSERHelper, C:/Program Files (x86)/Steam/CSERHelper.dll
0x5EC30000 - 0x5ED81000 ==> GameOverlayRenderer, C:/Program Files (x86)/Steam/GameOverlayRenderer.dll
0x5EDC0000 - 0x5EEB7000 ==> steam, C:/Program Files (x86)/Steam/steam.dll
0x6F520000 - 0x7081E000 ==> steamclient, C:/Program Files (x86)/Steam/steamclient.dll
0x73A90000 - 0x73B28000 ==> tier0_s, C:/Program Files (x86)/Steam/tier0_s.dll
0x73A00000 - 0x73A86000 ==> vstdlib_s, C:/Program Files (x86)/Steam/vstdlib_s.dll
0x5BDF0000 - 0x5C14D000 ==> DiscordHook, C:/Users/*****/AppData/Local/Discord/app-1.0.9144/modules/discord_hook-1/discord_hook/1a515a080b7897/DiscordHook.dll
0x5AE60000 - 0x5B036000 ==> nvse_dbghelp, C:/Users/*****/AppData/Local/Temp/nvse_dbghelp.dll
0x6EBC0000 - 0x6ED4A000 ==> AUDIOSES, C:/Windows/SYSTEM32/AUDIOSES.DLL
0x73740000 - 0x7377D000 ==> CFGMGR32, C:/Windows/SYSTEM32/CFGMGR32.dll
0x731A0000 - 0x731AB000 ==> CRYPTBASE, C:/Windows/SYSTEM32/CRYPTBASE.DLL
0x65FA0000 - 0x65FB5000 ==> CRYPTSP, C:/Windows/SYSTEM32/CRYPTSP.dll
0x73850000 - 0x7391E000 ==> CoreMessaging, C:/Windows/SYSTEM32/CoreMessaging.dll
0x655E0000 - 0x65871000 ==> CoreUIComponents, C:/Windows/SYSTEM32/CoreUIComponents.dll
0x5BA30000 - 0x5BDE3000 ==> D3DCompiler_47, C:/Windows/SYSTEM32/D3DCompiler_47.dll
0x73700000 - 0x73724000 ==> DEVOBJ, C:/Windows/SYSTEM32/DEVOBJ.dll
0x746D0000 - 0x74708000 ==> DINPUT8, C:/Windows/SYSTEM32/DINPUT8.dll
0x6F160000 - 0x6F1D2000 ==> DSOUND, C:/Windows/SYSTEM32/DSOUND.dll
0x74730000 - 0x7473B000 ==> HID, C:/Windows/SYSTEM32/HID.DLL
0x73D70000 - 0x73D94000 ==> IPHLPAPI, C:/Windows/SYSTEM32/IPHLPAPI.DLL
0x6EB80000 - 0x6EB99000 ==> MSACM32, C:/Windows/SYSTEM32/MSACM32.DLL
0x736F0000 - 0x736FE000 ==> MSASN1, C:/Windows/SYSTEM32/MSASN1.dll
0x6DA80000 - 0x6DAED000 ==> MSVCP140, C:/Windows/SYSTEM32/MSVCP140.dll
0x73B30000 - 0x73B81000 ==> MSWSOCK, C:/Windows/SYSTEM32/MSWSOCK.dll
0x65110000 - 0x6513D000 ==> RTWorkQ, C:/Windows/SYSTEM32/RTWorkQ.DLL
0x6F0A0000 - 0x6F139000 ==> ResampleDmo, C:/Windows/SYSTEM32/ResampleDmo.DLL
0x73B90000 - 0x73B9A000 ==> Secur32, C:/Windows/SYSTEM32/Secur32.dll
0x6F4F0000 - 0x6F51B000 ==> SspiCli, C:/Windows/SYSTEM32/SspiCli.dll
0x6F260000 - 0x6F26E000 ==> UMPDC, C:/Windows/SYSTEM32/UMPDC.dll
0x6DA60000 - 0x6DA75000 ==> VCRUNTIME140, C:/Windows/SYSTEM32/VCRUNTIME140.dll
0x74590000 - 0x74598000 ==> VERSION, C:/Windows/SYSTEM32/VERSION.dll
0x745A0000 - 0x745D1000 ==> WINMM, C:/Windows/SYSTEM32/WINMM.dll
0x73730000 - 0x73738000 ==> WSOCK32, C:/Windows/SYSTEM32/WSOCK32.dll
0x01CE0000 - 0x01CF6000 ==> XINPUT1_3, C:/Windows/SYSTEM32/XINPUT1_3.dll
0x5FAD0000 - 0x5FB76000 ==> apphelp, C:/Windows/SYSTEM32/apphelp.dll
0x6EF90000 - 0x6EF99000 ==> avrt, C:/Windows/SYSTEM32/avrt.dll
0x5F2A0000 - 0x5F668000 ==> d3dx9_38, C:/Windows/SYSTEM32/d3dx9_38.dll
0x5F060000 - 0x5F25F000 ==> d3dx9_43, C:/Windows/SYSTEM32/d3dx9_43.dll
0x66030000 - 0x66059000 ==> dbgcore, C:/Windows/SYSTEM32/dbgcore.DLL
0x6DAF0000 - 0x6DCC6000 ==> dbghelp, C:/Windows/SYSTEM32/dbghelp.dll
0x63EA0000 - 0x6403C000 ==> dcomp, C:/Windows/SYSTEM32/dcomp.dll
0x6F3E0000 - 0x6F41C000 ==> directxdatabasehelper, C:/Windows/SYSTEM32/directxdatabasehelper.dll
0x73BC0000 - 0x73BE4000 ==> dwmapi, C:/Windows/SYSTEM32/dwmapi.dll
0x73780000 - 0x737AE000 ==> dxcore, C:/Windows/SYSTEM32/dxcore.dll
0x6F420000 - 0x6F4EA000 ==> dxgi, C:/Windows/SYSTEM32/dxgi.dll
0x5B540000 - 0x5B54B000 ==> imaadp32, C:/Windows/SYSTEM32/imaadp32.acm
0x71C40000 - 0x71D8B000 ==> inputhost, C:/Windows/SYSTEM32/inputhost.dll
0x74710000 - 0x74723000 ==> kernel.appcore, C:/Windows/SYSTEM32/kernel.appcore.dll
0x6EFA0000 - 0x6EFA7000 ==> ksuser, C:/Windows/SYSTEM32/ksuser.dll
0x65140000 - 0x652D6000 ==> mfplat, C:/Windows/SYSTEM32/mfplat.DLL
0x6EB70000 - 0x6EB78000 ==> midimap, C:/Windows/SYSTEM32/midimap.dll
0x6EBA0000 - 0x6EBAB000 ==> msacm32, C:/Windows/SYSTEM32/msacm32.drv
0x5B530000 - 0x5B53A000 ==> msadp32, C:/Windows/SYSTEM32/msadp32.acm
0x6F090000 - 0x6F099000 ==> msdmo, C:/Windows/SYSTEM32/msdmo.dll
0x5B520000 - 0x5B528000 ==> msg711, C:/Windows/SYSTEM32/msg711.acm
0x5B510000 - 0x5B51C000 ==> msgsm32, C:/Windows/SYSTEM32/msgsm32.acm
0x76F60000 - 0x77111000 ==> ntdll, C:/Windows/SYSTEM32/ntdll.dll
0x65ED0000 - 0x65EF9000 ==> ntmarta, C:/Windows/SYSTEM32/ntmarta.dll
0x6F270000 - 0x6F2B5000 ==> powrprof, C:/Windows/SYSTEM32/powrprof.dll
0x5FFD0000 - 0x5FFE0000 ==> resourcepolicyclient, C:/Windows/SYSTEM32/resourcepolicyclient.dll
0x65880000 - 0x65979000 ==> textinputframework, C:/Windows/SYSTEM32/textinputframework.dll
0x6EFB0000 - 0x6EFEB000 ==> wdmaud, C:/Windows/SYSTEM32/wdmaud.drv
0x71320000 - 0x71A0F000 ==> windows.storage, C:/Windows/SYSTEM32/windows.storage.dll
0x6F140000 - 0x6F15F000 ==> winmmbase, C:/Windows/SYSTEM32/winmmbase.dll
0x71250000 - 0x71317000 ==> wintypes, C:/Windows/SYSTEM32/wintypes.dll
0x76890000 - 0x7690F000 ==> ADVAPI32, C:/Windows/System32/ADVAPI32.dll
0x74DD0000 - 0x74ED3000 ==> CRYPT32, C:/Windows/System32/CRYPT32.dll
0x60C10000 - 0x60C3A000 ==> amdihk32, C:/Windows/System32/DriverStore/FileRepository/u0402338.inf_amd64_d4de815aa579b06a/B402197/amdihk32.dll
0x5C150000 - 0x5EC22000 ==> amdxn32, C:/Windows/System32/DriverStore/FileRepository/u0402338.inf_amd64_d4de815aa579b06a/B402197/amdxn32.dll
0x74DA0000 - 0x74DC3000 ==> GDI32, C:/Windows/System32/GDI32.dll
0x76630000 - 0x76655000 ==> IMM32, C:/Windows/System32/IMM32.DLL
0x75E40000 - 0x75F30000 ==> KERNEL32, C:/Windows/System32/KERNEL32.DLL
0x762F0000 - 0x76565000 ==> KERNELBASE, C:/Windows/System32/KERNELBASE.dll
0x6EFF0000 - 0x6F06C000 ==> MMDevApi, C:/Windows/System32/MMDevApi.dll
0x76C60000 - 0x76D5F000 ==> MSCTF, C:/Windows/System32/MSCTF.dll
0x76EB0000 - 0x76F4C000 ==> OLEAUT32, C:/Windows/System32/OLEAUT32.dll
0x76D70000 - 0x76E2A000 ==> RPCRT4, C:/Windows/System32/RPCRT4.dll
0x74EE0000 - 0x7531D000 ==> SETUPAPI, C:/Windows/System32/SETUPAPI.dll
0x75490000 - 0x75B29000 ==> SHELL32, C:/Windows/System32/SHELL32.dll
0x760B0000 - 0x76259000 ==> USER32, C:/Windows/System32/USER32.dll
0x75FB0000 - 0x76007000 ==> WINTRUST, C:/Windows/System32/WINTRUST.dll
0x5B570000 - 0x5B5B1000 ==> WMASF, C:/Windows/System32/WMASF.DLL
0x5B5C0000 - 0x5B790000 ==> WMVCore, C:/Windows/System32/WMVCore.DLL
0x75F30000 - 0x75F8F000 ==> WS2_32, C:/Windows/System32/WS2_32.dll
0x6EA60000 - 0x6EB6A000 ==> Windows.UI, C:/Windows/System32/Windows.UI.dll
0x75F90000 - 0x75FAA000 ==> bcrypt, C:/Windows/System32/bcrypt.dll
0x75B50000 - 0x75BB2000 ==> bcryptPrimitives, C:/Windows/System32/bcryptPrimitives.dll
0x76260000 - 0x762E2000 ==> clbcatq, C:/Windows/System32/clbcatq.dll
0x76910000 - 0x76B8C000 ==> combase, C:/Windows/System32/combase.dll
0x5B7C0000 - 0x5B7DC000 ==> devenum, C:/Windows/System32/devenum.dll
0x5B040000 - 0x5B071000 ==> dsdmo, C:/Windows/System32/dsdmo.dll
0x76670000 - 0x76752000 ==> gdi32full, C:/Windows/System32/gdi32full.dll
0x74D80000 - 0x74D9B000 ==> imagehlp, C:/Windows/System32/imagehlp.dll
0x5B4F0000 - 0x5B506000 ==> l3codeca, C:/Windows/System32/l3codeca.acm
0x64D60000 - 0x64E68000 ==> mfperfhelper, C:/Windows/System32/mfperfhelper.dll
0x5B550000 - 0x5B568000 ==> mp3dmod, C:/Windows/System32/mp3dmod.dll
0x5B410000 - 0x5B4E4000 ==> msmpeg2adec, C:/Windows/System32/msmpeg2adec.dll
0x76E30000 - 0x76EA9000 ==> msvcp_win, C:/Windows/System32/msvcp_win.dll
0x76B90000 - 0x76C54000 ==> msvcrt, C:/Windows/System32/msvcrt.dll
0x75BC0000 - 0x75D15000 ==> ole32, C:/Windows/System32/ole32.dll
0x76D60000 - 0x76D66000 ==> psapi, C:/Windows/System32/psapi.dll
0x5B790000 - 0x5B7B4000 ==> qasf, C:/Windows/System32/qasf.dll
0x5B7E0000 - 0x5B982000 ==> quartz, C:/Windows/System32/quartz.dll
0x74BC0000 - 0x74C45000 ==> sechost, C:/Windows/System32/sechost.dll
0x74CB0000 - 0x74D71000 ==> shcore, C:/Windows/System32/shcore.dll
0x76760000 - 0x767AB000 ==> shlwapi, C:/Windows/System32/shlwapi.dll
0x75D20000 - 0x75E32000 ==> ucrtbase, C:/Windows/System32/ucrtbase.dll
0x75B30000 - 0x75B4A000 ==> win32u, C:/Windows/System32/win32u.dll
0x5F960000 - 0x5F9F1000 ==> COMCTL32, C:/Windows/WinSxS/x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.22621.2506_none_fbe8e1f07808be9b/COMCTL32.dll
0x5EEF0000 - 0x5F05E000 ==> gdiplus, C:/Windows/WinSxS/x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.22621.3085_none_9faca057e290307d/gdiplus.dll
0x66690000 - 0x66801000 ==> d3d9, C:/Windows/system32/d3d9.dll
0x745E0000 - 0x7465F000 ==> uxtheme, C:/Windows/system32/uxtheme.dll
0x01540000 - 0x01557000 ==> ActorCauseSaveBloatFix, NVSE plugin version: 1, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/ActorCauseSaveBloatFix.dll
0x5F280000 - 0x5F29A000 ==> ClimateControl, NVSE plugin version: 0, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/ClimateControl.dll
0x5F260000 - 0x5F280000 ==> CloudUpgrade, NVSE plugin version: 0, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/CloudUpgrade.dll
0x0B600000 - 0x0B678000 ==> CrashLogger, NVSE plugin version: 454, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/CrashLogger.dll
0x03890000 - 0x03896000 ==> DoF-Fix, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/DoF-Fix.dll
0x04440000 - 0x04481000 ==> DynamicReflections, NVSE plugin version: 134, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/DynamicReflections.dll
0x04490000 - 0x044A9000 ==> EngineOptimizations, NVSE plugin version: 100, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/EngineOptimizations.dll
0x0AFA0000 - 0x0AFB6000 ==> HDPipboy, NVSE plugin version: 1, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/HDPipboy.dll
0x0AFD0000 - 0x0AFD7000 ==> HighResBloom, NVSE plugin version: 510, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/HighResBloom.dll
0x0AFF0000 - 0x0AFF6000 ==> HighResWaterDepth, NVSE plugin version: 11, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/HighResWaterDepth.dll
0x0B690000 - 0x0B6B6000 ==> ImprovedLightingShaders, NVSE plugin version: 8, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/ImprovedLightingShaders.dll
0x0B8F0000 - 0x0B8FB000 ==> LOD Fixes, NVSE plugin version: 128, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/LOD Fixes.dll
0x0B910000 - 0x0B942000 ==> MCM, NVSE plugin version: 1, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/MCM.dll
0x0B960000 - 0x0B971000 ==> MoonlightNVSE, NVSE plugin version: 200, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/MoonlightNVSE.dll
0x0B990000 - 0x0B996000 ==> MuzzleFlashFix, NVSE plugin version: 1, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/MuzzleFlashFix.dll
0x0BAC0000 - 0x0BACC000 ==> NVTF, NVSE plugin version: 10, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/NVTF.dll
0x5EEC0000 - 0x5EEF0000 ==> OneTweak, NVSE plugin version: 4, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/OneTweak.dll
0x0BB00000 - 0x0BB06000 ==> PipBoyShadingFix, NVSE plugin version: 2, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/PipBoyShadingFix.dll
0x0BE70000 - 0x0BFAA000 ==> ShowOffNVSE, NVSE plugin version: 175, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/ShowOffNVSE.dll
0x0BFF0000 - 0x0BFF7000 ==> Viewmodel Shading Fix, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/Viewmodel Shading Fix.dll
0x0B6D0000 - 0x0B739000 ==> improved_console, NVSE plugin version: 3, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/improved_console.dll
0x0B750000 - 0x0B7D3000 ==> jip_nvse, NVSE plugin version: 5721, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/jip_nvse.dll
0x0B7F0000 - 0x0B847000 ==> johnnyguitar, NVSE plugin version: 501, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/johnnyguitar.dll
0x0B860000 - 0x0B8D9000 ==> kNVSE, NVSE plugin version: 20, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/kNVSE.dll
0x0B9B0000 - 0x0BAA6000 ==> nvse_stewie_tweaks, NVSE plugin version: 910, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/nvse_stewie_tweaks.dll
0x0C700000 - 0x0C750000 ==> sound_extender, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/sound_extender.dll
0x0BFD0000 - 0x0BFDB000 ==> ui_organizer, NVSE plugin version: 230, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/ui_organizer.dll
0x0C7F0000 - 0x0C7F6000 ==> weapon_lag_fix, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/weapon_lag_fix.dll
0x0C810000 - 0x0C81C000 ==> zlibUpdate, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/zlibUpdate.dll
0x00400000 - 0x0147B000 ==> FalloutNV, D:/SteamLibrary/steamapps/common/Fallout New Vegas/FalloutNV.exe
0x18000000 - 0x18068000 ==> binkw32, D:/SteamLibrary/steamapps/common/Fallout New Vegas/binkw32.dll
0x10000000 - 0x1001C000 ==> d3d9, D:/SteamLibrary/steamapps/common/Fallout New Vegas/d3d9.dll
0x01D30000 - 0x01E63000 ==> libvorbis, D:/SteamLibrary/steamapps/common/Fallout New Vegas/libvorbis.dll
0x01D00000 - 0x01D1E000 ==> libvorbisfile, D:/SteamLibrary/steamapps/common/Fallout New Vegas/libvorbisfile.dll
0x0AE50000 - 0x0AFA0000 ==> nvse_1_4, D:/SteamLibrary/steamapps/common/Fallout New Vegas/nvse_1_4.dll
0x5F930000 - 0x5F95D000 ==> nvse_steam_loader, D:/SteamLibrary/steamapps/common/Fallout New Vegas/nvse_steam_loader.dll
0x3B400000 - 0x3B41D000 ==> steam_api, D:/SteamLibrary/steamapps/common/Fallout New Vegas/steam_api.dll
GAME CRASHED AT INSTRUCTION Base+0x0075B1CD IN MODULE: D:\SteamLibrary\steamapps\common\Fallout New Vegas\FalloutNV.exe
Please note that this does not automatically mean that that module is responsible. It may have been supplied bad data or
program state as the result of an issue in the base game or a different DLL.

I'm at my limits with figuring out how to read the crash logger. If anyone knows how to compare this to my load order I would greatly appreciate it. I'll post the load order in a comment.
​
Exception C0000005 caught!
​
Thread: [FNV] Main
​
Calltrace:
0x0019F9C8 ==> FalloutNV (0x00B5B1CD) : EntryPoint+0xFFFFFFFF
0x0019F9D8 ==> FalloutNV (0x004AB057) : EntryPoint+0xFFFFFFFF
0x0019F9F0 ==> FalloutNV (0x004AB016) : EntryPoint+0xFFFFFFFF
0x0019FA0C ==> FalloutNV (0x004AAEB8) : EntryPoint+0xFFFFFFFF
0x0019FA18 ==> FalloutNV (0x004AAE5F) : EntryPoint+0xFFFFFFFF
0x0019FA24 ==> FalloutNV (0x00418E0F) : EntryPoint+0xFFFFFFFF
0x0019FA7C ==> FalloutNV (0x00868F36) : EntryPoint+0xFFFFFFFF
0x0019FAB4 ==> FalloutNV (0x0093C178) : EntryPoint+0xFFFFFFFF
0x0019FAE8 ==> FalloutNV (0x0086F954) : EntryPoint+0xFFFFFFFF
0x0019FB40 ==> FalloutNV (0x0086E765) : EntryPoint+0xFFFFFFFF
0x0019FEC4 ==> FalloutNV (0x0086B3E8) : EntryPoint+0xFFFFFFFF
0x0019FEE4 ==> nvse_steam_loader (0x100021E4) : EntryPoint+0xFFFFFFFF
0x0019FF74 ==> FalloutNV (0x00ECC470) : EntryPoint+0xFFFFFFFF
0x0019FF84 ==> KERNEL32 (0x10017BA9) : BaseThreadInitThunk+0x19
0x0019FFDC ==> ntdll (0x1006BE3B) : RtlInitializeExceptionChain+0x6B
0x001A0020 ==> ntdll (0x1006BDBF) : RtlClearBits+0xBF
0x00000000 ==> FalloutNV (0x0050005C) : EntryPoint+0xFFFFFFFF
​
Registry:
REG VALUE DEREFERENCE INFO
eax 0x00000000
ebp 0x0019F9C8
ebx 0x00000001
ecx 0x2B21A0D0
edi 0xFFFFFFFE
edx 0x2B21A0D0
eip 0x00B5B1CD
esi 0x49007900 0x010ADCF8 ==> Class: , failed to get string for label
esp 0x0019F9B8
​
Stack:
# VALUE DEREFERENCE INFO
0 0x00000000
1 0x004AB0ED
2 0x2B21A0D0
3 0x28BEA034
4 0x0019F9D8
5 0x004AB057
6 0x2B21A0D0
7 0x28BE9FF8
8 0x0019F9F0
21 0x19DB986C 0x0102E9B4 ==> Class: TESObjectCELL: 000DAD7A (Vault19)
22 0x19DF303C 0x0102E9B4 ==> Class: TESObjectCELL: 000E1BB3 (Wilderness)
27 0x3A0BE270 0x0102F55C ==> Class: TESObjectREFR: 0013BDB2 (), Baseform 000B044E (SewerLidExit01NoMinUse)
2D 0x19DB986C 0x0102E9B4 ==> Class: TESObjectCELL: 000DAD7A (Vault19)
36 0x185B8578 0x0108AA3C ==> Class: PlayerCharacter: 00000014 (PlayerRef), Baseform 00000007 (Player)
3C 0x2003F9C0 0x010C49C4 ==> Class: bhkCharacterController: Name: ""
4F 0x3848D420 0x01037094 ==> Class: Script: 42005808 (JLMCloseContainerUDF)
5B 0x011F71A8 0x010A42B4 ==> Class: BSSystemUtility
6E 0x0D000CB0 0x010472D0 ==> Unhandled: BSSimpleArray
7B 0x0D000CB0 0x010472D0 ==> Unhandled: BSSimpleArray
7C 0x0D000CB0 0x010472D0 ==> Unhandled: BSSimpleArray
9C 0x76F666F4 0x6B6E696D ==> String: "minkernel\ntdll\ldrapi.c"
9E 0x76F667BC 0x7072644C ==> String: "LdrpLoadDllInternal"
A0 0x76F66754 0x74617453 ==> String: "Status: 0x%08lx "
A7 0x0019FDD0 0x66657250 ==> String: "Prefs.ini"
B6 0x76F666F4 0x6B6E696D ==> String: "minkernel\ntdll\ldrapi.c"
B8 0x76F66778 0x4C72644C ==> String: "LdrLoadDll"
BA 0x76F66754 0x74617453 ==> String: "Status: 0x%08lx "
E7 0x01082860 0x6C6C6146 ==> String: "Fallout: New Vegas"
F3 0x0019FDA0 0x4F5C6F72 ==> String: "ro\OneDrive\Documents\My Games\FalloutNV\FalloutPrefs.ini"
F4 0x0019FDA0 0x4F5C6F72 ==> String: "ro\OneDrive\Documents\My Games\FalloutNV\FalloutPrefs.ini"
F5 0x0019FDA4 0x7244656E ==> String: "neDrive\Documents\My Games\FalloutNV\FalloutPrefs.ini"
​
Memory:
MinimumWorkingSetSize: 200.00 KB
MaximumWorkingSetSize: 1.35 MB
PeakWorkingSetSize: 1.12 GB
WorkingSetSize: 1.06 GB
QuotaPeakPagedPoolUsage: 1.15 MB
QuotaPagedPoolUsage: 885.43 KB
QuotaPeakNonPagedPoolUsage: 876.07 KB
QuotaNonPagedPoolUsage: 91.81 KB
PageFaultCount: 3.98 MB
PagefileUsage: 1.24 GB
PeakPagefileUsage: 1.30 GB
​
Module bases:
0x74BA0000 - 0x74BB5000 ==> aswhook, C:/Program Files/Avast Software/Avast/x86/aswhook.dll
0x5ED90000 - 0x5EDB1000 ==> CSERHelper, C:/Program Files (x86)/Steam/CSERHelper.dll
0x5EC30000 - 0x5ED81000 ==> GameOverlayRenderer, C:/Program Files (x86)/Steam/GameOverlayRenderer.dll
0x5EDC0000 - 0x5EEB7000 ==> steam, C:/Program Files (x86)/Steam/steam.dll
0x6F520000 - 0x7081E000 ==> steamclient, C:/Program Files (x86)/Steam/steamclient.dll
0x73A90000 - 0x73B28000 ==> tier0_s, C:/Program Files (x86)/Steam/tier0_s.dll
0x73A00000 - 0x73A86000 ==> vstdlib_s, C:/Program Files (x86)/Steam/vstdlib_s.dll
0x5BDF0000 - 0x5C14D000 ==> DiscordHook, C:/Users/*****/AppData/Local/Discord/app-1.0.9144/modules/discord_hook-1/discord_hook/1a515a080b7897/DiscordHook.dll
0x5AE60000 - 0x5B036000 ==> nvse_dbghelp, C:/Users/*****/AppData/Local/Temp/nvse_dbghelp.dll
0x6EBC0000 - 0x6ED4A000 ==> AUDIOSES, C:/Windows/SYSTEM32/AUDIOSES.DLL
0x73740000 - 0x7377D000 ==> CFGMGR32, C:/Windows/SYSTEM32/CFGMGR32.dll
0x731A0000 - 0x731AB000 ==> CRYPTBASE, C:/Windows/SYSTEM32/CRYPTBASE.DLL
0x65FA0000 - 0x65FB5000 ==> CRYPTSP, C:/Windows/SYSTEM32/CRYPTSP.dll
0x73850000 - 0x7391E000 ==> CoreMessaging, C:/Windows/SYSTEM32/CoreMessaging.dll
0x655E0000 - 0x65871000 ==> CoreUIComponents, C:/Windows/SYSTEM32/CoreUIComponents.dll
0x5BA30000 - 0x5BDE3000 ==> D3DCompiler_47, C:/Windows/SYSTEM32/D3DCompiler_47.dll
0x73700000 - 0x73724000 ==> DEVOBJ, C:/Windows/SYSTEM32/DEVOBJ.dll
0x746D0000 - 0x74708000 ==> DINPUT8, C:/Windows/SYSTEM32/DINPUT8.dll
0x6F160000 - 0x6F1D2000 ==> DSOUND, C:/Windows/SYSTEM32/DSOUND.dll
0x74730000 - 0x7473B000 ==> HID, C:/Windows/SYSTEM32/HID.DLL
0x73D70000 - 0x73D94000 ==> IPHLPAPI, C:/Windows/SYSTEM32/IPHLPAPI.DLL
0x6EB80000 - 0x6EB99000 ==> MSACM32, C:/Windows/SYSTEM32/MSACM32.DLL
0x736F0000 - 0x736FE000 ==> MSASN1, C:/Windows/SYSTEM32/MSASN1.dll
0x6DA80000 - 0x6DAED000 ==> MSVCP140, C:/Windows/SYSTEM32/MSVCP140.dll
0x73B30000 - 0x73B81000 ==> MSWSOCK, C:/Windows/SYSTEM32/MSWSOCK.dll
0x65110000 - 0x6513D000 ==> RTWorkQ, C:/Windows/SYSTEM32/RTWorkQ.DLL
0x6F0A0000 - 0x6F139000 ==> ResampleDmo, C:/Windows/SYSTEM32/ResampleDmo.DLL
0x73B90000 - 0x73B9A000 ==> Secur32, C:/Windows/SYSTEM32/Secur32.dll
0x6F4F0000 - 0x6F51B000 ==> SspiCli, C:/Windows/SYSTEM32/SspiCli.dll
0x6F260000 - 0x6F26E000 ==> UMPDC, C:/Windows/SYSTEM32/UMPDC.dll
0x6DA60000 - 0x6DA75000 ==> VCRUNTIME140, C:/Windows/SYSTEM32/VCRUNTIME140.dll
0x74590000 - 0x74598000 ==> VERSION, C:/Windows/SYSTEM32/VERSION.dll
0x745A0000 - 0x745D1000 ==> WINMM, C:/Windows/SYSTEM32/WINMM.dll
0x73730000 - 0x73738000 ==> WSOCK32, C:/Windows/SYSTEM32/WSOCK32.dll
0x01CE0000 - 0x01CF6000 ==> XINPUT1_3, C:/Windows/SYSTEM32/XINPUT1_3.dll
0x5FAD0000 - 0x5FB76000 ==> apphelp, C:/Windows/SYSTEM32/apphelp.dll
0x6EF90000 - 0x6EF99000 ==> avrt, C:/Windows/SYSTEM32/avrt.dll
0x5F2A0000 - 0x5F668000 ==> d3dx9_38, C:/Windows/SYSTEM32/d3dx9_38.dll
0x5F060000 - 0x5F25F000 ==> d3dx9_43, C:/Windows/SYSTEM32/d3dx9_43.dll
0x66030000 - 0x66059000 ==> dbgcore, C:/Windows/SYSTEM32/dbgcore.DLL
0x6DAF0000 - 0x6DCC6000 ==> dbghelp, C:/Windows/SYSTEM32/dbghelp.dll
0x63EA0000 - 0x6403C000 ==> dcomp, C:/Windows/SYSTEM32/dcomp.dll
0x6F3E0000 - 0x6F41C000 ==> directxdatabasehelper, C:/Windows/SYSTEM32/directxdatabasehelper.dll
0x73BC0000 - 0x73BE4000 ==> dwmapi, C:/Windows/SYSTEM32/dwmapi.dll
0x73780000 - 0x737AE000 ==> dxcore, C:/Windows/SYSTEM32/dxcore.dll
0x6F420000 - 0x6F4EA000 ==> dxgi, C:/Windows/SYSTEM32/dxgi.dll
0x5B540000 - 0x5B54B000 ==> imaadp32, C:/Windows/SYSTEM32/imaadp32.acm
0x71C40000 - 0x71D8B000 ==> inputhost, C:/Windows/SYSTEM32/inputhost.dll
0x74710000 - 0x74723000 ==> kernel.appcore, C:/Windows/SYSTEM32/kernel.appcore.dll
0x6EFA0000 - 0x6EFA7000 ==> ksuser, C:/Windows/SYSTEM32/ksuser.dll
0x65140000 - 0x652D6000 ==> mfplat, C:/Windows/SYSTEM32/mfplat.DLL
0x6EB70000 - 0x6EB78000 ==> midimap, C:/Windows/SYSTEM32/midimap.dll
0x6EBA0000 - 0x6EBAB000 ==> msacm32, C:/Windows/SYSTEM32/msacm32.drv
0x5B530000 - 0x5B53A000 ==> msadp32, C:/Windows/SYSTEM32/msadp32.acm
0x6F090000 - 0x6F099000 ==> msdmo, C:/Windows/SYSTEM32/msdmo.dll
0x5B520000 - 0x5B528000 ==> msg711, C:/Windows/SYSTEM32/msg711.acm
0x5B510000 - 0x5B51C000 ==> msgsm32, C:/Windows/SYSTEM32/msgsm32.acm
0x76F60000 - 0x77111000 ==> ntdll, C:/Windows/SYSTEM32/ntdll.dll
0x65ED0000 - 0x65EF9000 ==> ntmarta, C:/Windows/SYSTEM32/ntmarta.dll
0x6F270000 - 0x6F2B5000 ==> powrprof, C:/Windows/SYSTEM32/powrprof.dll
0x5FFD0000 - 0x5FFE0000 ==> resourcepolicyclient, C:/Windows/SYSTEM32/resourcepolicyclient.dll
0x65880000 - 0x65979000 ==> textinputframework, C:/Windows/SYSTEM32/textinputframework.dll
0x6EFB0000 - 0x6EFEB000 ==> wdmaud, C:/Windows/SYSTEM32/wdmaud.drv
0x71320000 - 0x71A0F000 ==> windows.storage, C:/Windows/SYSTEM32/windows.storage.dll
0x6F140000 - 0x6F15F000 ==> winmmbase, C:/Windows/SYSTEM32/winmmbase.dll
0x71250000 - 0x71317000 ==> wintypes, C:/Windows/SYSTEM32/wintypes.dll
0x76890000 - 0x7690F000 ==> ADVAPI32, C:/Windows/System32/ADVAPI32.dll
0x74DD0000 - 0x74ED3000 ==> CRYPT32, C:/Windows/System32/CRYPT32.dll
0x60C10000 - 0x60C3A000 ==> amdihk32, C:/Windows/System32/DriverStore/FileRepository/u0402338.inf_amd64_d4de815aa579b06a/B402197/amdihk32.dll
0x5C150000 - 0x5EC22000 ==> amdxn32, C:/Windows/System32/DriverStore/FileRepository/u0402338.inf_amd64_d4de815aa579b06a/B402197/amdxn32.dll
0x74DA0000 - 0x74DC3000 ==> GDI32, C:/Windows/System32/GDI32.dll
0x76630000 - 0x76655000 ==> IMM32, C:/Windows/System32/IMM32.DLL
0x75E40000 - 0x75F30000 ==> KERNEL32, C:/Windows/System32/KERNEL32.DLL
0x762F0000 - 0x76565000 ==> KERNELBASE, C:/Windows/System32/KERNELBASE.dll
0x6EFF0000 - 0x6F06C000 ==> MMDevApi, C:/Windows/System32/MMDevApi.dll
0x76C60000 - 0x76D5F000 ==> MSCTF, C:/Windows/System32/MSCTF.dll
0x76EB0000 - 0x76F4C000 ==> OLEAUT32, C:/Windows/System32/OLEAUT32.dll
0x76D70000 - 0x76E2A000 ==> RPCRT4, C:/Windows/System32/RPCRT4.dll
0x74EE0000 - 0x7531D000 ==> SETUPAPI, C:/Windows/System32/SETUPAPI.dll
0x75490000 - 0x75B29000 ==> SHELL32, C:/Windows/System32/SHELL32.dll
0x760B0000 - 0x76259000 ==> USER32, C:/Windows/System32/USER32.dll
0x75FB0000 - 0x76007000 ==> WINTRUST, C:/Windows/System32/WINTRUST.dll
0x5B570000 - 0x5B5B1000 ==> WMASF, C:/Windows/System32/WMASF.DLL
0x5B5C0000 - 0x5B790000 ==> WMVCore, C:/Windows/System32/WMVCore.DLL
0x75F30000 - 0x75F8F000 ==> WS2_32, C:/Windows/System32/WS2_32.dll
0x6EA60000 - 0x6EB6A000 ==> Windows.UI, C:/Windows/System32/Windows.UI.dll
0x75F90000 - 0x75FAA000 ==> bcrypt, C:/Windows/System32/bcrypt.dll
0x75B50000 - 0x75BB2000 ==> bcryptPrimitives, C:/Windows/System32/bcryptPrimitives.dll
0x76260000 - 0x762E2000 ==> clbcatq, C:/Windows/System32/clbcatq.dll
0x76910000 - 0x76B8C000 ==> combase, C:/Windows/System32/combase.dll
0x5B7C0000 - 0x5B7DC000 ==> devenum, C:/Windows/System32/devenum.dll
0x5B040000 - 0x5B071000 ==> dsdmo, C:/Windows/System32/dsdmo.dll
0x76670000 - 0x76752000 ==> gdi32full, C:/Windows/System32/gdi32full.dll
0x74D80000 - 0x74D9B000 ==> imagehlp, C:/Windows/System32/imagehlp.dll
0x5B4F0000 - 0x5B506000 ==> l3codeca, C:/Windows/System32/l3codeca.acm
0x64D60000 - 0x64E68000 ==> mfperfhelper, C:/Windows/System32/mfperfhelper.dll
0x5B550000 - 0x5B568000 ==> mp3dmod, C:/Windows/System32/mp3dmod.dll
0x5B410000 - 0x5B4E4000 ==> msmpeg2adec, C:/Windows/System32/msmpeg2adec.dll
0x76E30000 - 0x76EA9000 ==> msvcp_win, C:/Windows/System32/msvcp_win.dll
0x76B90000 - 0x76C54000 ==> msvcrt, C:/Windows/System32/msvcrt.dll
0x75BC0000 - 0x75D15000 ==> ole32, C:/Windows/System32/ole32.dll
0x76D60000 - 0x76D66000 ==> psapi, C:/Windows/System32/psapi.dll
0x5B790000 - 0x5B7B4000 ==> qasf, C:/Windows/System32/qasf.dll
0x5B7E0000 - 0x5B982000 ==> quartz, C:/Windows/System32/quartz.dll
0x74BC0000 - 0x74C45000 ==> sechost, C:/Windows/System32/sechost.dll
0x74CB0000 - 0x74D71000 ==> shcore, C:/Windows/System32/shcore.dll
0x76760000 - 0x767AB000 ==> shlwapi, C:/Windows/System32/shlwapi.dll
0x75D20000 - 0x75E32000 ==> ucrtbase, C:/Windows/System32/ucrtbase.dll
0x75B30000 - 0x75B4A000 ==> win32u, C:/Windows/System32/win32u.dll
0x5F960000 - 0x5F9F1000 ==> COMCTL32, C:/Windows/WinSxS/x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.22621.2506_none_fbe8e1f07808be9b/COMCTL32.dll
0x5EEF0000 - 0x5F05E000 ==> gdiplus, C:/Windows/WinSxS/x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.22621.3085_none_9faca057e290307d/gdiplus.dll
0x66690000 - 0x66801000 ==> d3d9, C:/Windows/system32/d3d9.dll
0x745E0000 - 0x7465F000 ==> uxtheme, C:/Windows/system32/uxtheme.dll
0x01540000 - 0x01557000 ==> ActorCauseSaveBloatFix, NVSE plugin version: 1, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/ActorCauseSaveBloatFix.dll
0x5F280000 - 0x5F29A000 ==> ClimateControl, NVSE plugin version: 0, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/ClimateControl.dll
0x5F260000 - 0x5F280000 ==> CloudUpgrade, NVSE plugin version: 0, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/CloudUpgrade.dll
0x0B600000 - 0x0B678000 ==> CrashLogger, NVSE plugin version: 454, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/CrashLogger.dll
0x03890000 - 0x03896000 ==> DoF-Fix, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/DoF-Fix.dll
0x04440000 - 0x04481000 ==> DynamicReflections, NVSE plugin version: 134, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/DynamicReflections.dll
0x04490000 - 0x044A9000 ==> EngineOptimizations, NVSE plugin version: 100, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/EngineOptimizations.dll
0x0AFA0000 - 0x0AFB6000 ==> HDPipboy, NVSE plugin version: 1, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/HDPipboy.dll
0x0AFD0000 - 0x0AFD7000 ==> HighResBloom, NVSE plugin version: 510, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/HighResBloom.dll
0x0AFF0000 - 0x0AFF6000 ==> HighResWaterDepth, NVSE plugin version: 11, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/HighResWaterDepth.dll
0x0B690000 - 0x0B6B6000 ==> ImprovedLightingShaders, NVSE plugin version: 8, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/ImprovedLightingShaders.dll
0x0B8F0000 - 0x0B8FB000 ==> LOD Fixes, NVSE plugin version: 128, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/LOD Fixes.dll
0x0B910000 - 0x0B942000 ==> MCM, NVSE plugin version: 1, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/MCM.dll
0x0B960000 - 0x0B971000 ==> MoonlightNVSE, NVSE plugin version: 200, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/MoonlightNVSE.dll
0x0B990000 - 0x0B996000 ==> MuzzleFlashFix, NVSE plugin version: 1, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/MuzzleFlashFix.dll
0x0BAC0000 - 0x0BACC000 ==> NVTF, NVSE plugin version: 10, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/NVTF.dll
0x5EEC0000 - 0x5EEF0000 ==> OneTweak, NVSE plugin version: 4, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/OneTweak.dll
0x0BB00000 - 0x0BB06000 ==> PipBoyShadingFix, NVSE plugin version: 2, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/PipBoyShadingFix.dll
0x0BE70000 - 0x0BFAA000 ==> ShowOffNVSE, NVSE plugin version: 175, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/ShowOffNVSE.dll
0x0BFF0000 - 0x0BFF7000 ==> Viewmodel Shading Fix, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/Viewmodel Shading Fix.dll
0x0B6D0000 - 0x0B739000 ==> improved_console, NVSE plugin version: 3, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/improved_console.dll
0x0B750000 - 0x0B7D3000 ==> jip_nvse, NVSE plugin version: 5721, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/jip_nvse.dll
0x0B7F0000 - 0x0B847000 ==> johnnyguitar, NVSE plugin version: 501, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/johnnyguitar.dll
0x0B860000 - 0x0B8D9000 ==> kNVSE, NVSE plugin version: 20, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/kNVSE.dll
0x0B9B0000 - 0x0BAA6000 ==> nvse_stewie_tweaks, NVSE plugin version: 910, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/nvse_stewie_tweaks.dll
0x0C700000 - 0x0C750000 ==> sound_extender, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/sound_extender.dll
0x0BFD0000 - 0x0BFDB000 ==> ui_organizer, NVSE plugin version: 230, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/ui_organizer.dll
0x0C7F0000 - 0x0C7F6000 ==> weapon_lag_fix, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/weapon_lag_fix.dll
0x0C810000 - 0x0C81C000 ==> zlibUpdate, D:/SteamLibrary/steamapps/common/Fallout New Vegas/Data/NVSE/Plugins/zlibUpdate.dll
0x00400000 - 0x0147B000 ==> FalloutNV, D:/SteamLibrary/steamapps/common/Fallout New Vegas/FalloutNV.exe
0x18000000 - 0x18068000 ==> binkw32, D:/SteamLibrary/steamapps/common/Fallout New Vegas/binkw32.dll
0x10000000 - 0x1001C000 ==> d3d9, D:/SteamLibrary/steamapps/common/Fallout New Vegas/d3d9.dll
0x01D30000 - 0x01E63000 ==> libvorbis, D:/SteamLibrary/steamapps/common/Fallout New Vegas/libvorbis.dll
0x01D00000 - 0x01D1E000 ==> libvorbisfile, D:/SteamLibrary/steamapps/common/Fallout New Vegas/libvorbisfile.dll
0x0AE50000 - 0x0AFA0000 ==> nvse_1_4, D:/SteamLibrary/steamapps/common/Fallout New Vegas/nvse_1_4.dll
0x5F930000 - 0x5F95D000 ==> nvse_steam_loader, D:/SteamLibrary/steamapps/common/Fallout New Vegas/nvse_steam_loader.dll
0x3B400000 - 0x3B41D000 ==> steam_api, D:/SteamLibrary/steamapps/common/Fallout New Vegas/steam_api.dll
​
GAME CRASHED AT INSTRUCTION Base+0x0075B1CD IN MODULE: D:\SteamLibrary\steamapps\common\Fallout New Vegas\FalloutNV.exe
Please note that this does not automatically mean that that module is responsible. It may have been supplied bad data or
program state as the result of an issue in the base game or a different DLL.
​
​

A year ago I was recommended to switch from Avast to Kaspersky because it was as I was told "better in every way" that did not quite turn out to be true, for one year I have owned Kaspersky Internet Security, one thing I have noticed is huge increase in false positives over the year.
Not only that, Kaspersky gives you no options or warning that it deletes files, at one point it deleted a Microsoft app from the Microsoft store LOL.
Usually I double check files if they are reported by AV in online scanners just to be sure. But with Kaspersky, he has not found one positive, and it really REALLY hates any file explorer replacement program, recently I tried to install Files from Microsoft Store, Kaspersky would not leave it alone even when I added an exclusion.
The final straw came when Kaspersky literally deleted a program I was midway installing, a program I know is safe, just to be sure I scanned it in an online scanner, sure enough, its false positive. But Kaspersky removing the .exe while the program was installing caused the system installer to hang and then go 100% CPU usage completely throttling my 16 core CPU and I was forced to restart causing headache as I was working there and then with a lot of stuff open.
Honestly, the only time I can remembering getting worked up so much over an anti virus being complete malware is Norton back in 2009.
Kaspersky has so little user input, its also utterly cluttered program to navigate, when it deletes stuff, you cannot recover it because Kaspersky thinks the folder stopped existing when its still there. At least with Avast, it asks you kindly if you want to delete a file or add exception, its also light years ahead on user interface, I can actually find stuff easily and quickly.
If this is what "best" AV is like, I can see why, it completely removes user input and acts autonomous based on what it thinks is the best course of action, it also keeps nagging me to restart the computer everyday to update its database, strange. I actually wonder if people are reporting stuff as virus so that Kaspersky database gets clogged with false positives, regardless the lack of user input really pisses me off and is a killer for any AV in my opinion.

Hi guys! This new update led to a particular problem which I know others are experiencing but I have not yet found a problem.
So, yesterday some files from tf2 got flagged by my antivirus as viruses/trojans. Avast moved these into quarantine, and as a non tech person I thought I'd just delete them, thinking if any problems occurred, I would just be able to reinstall tf2.
However, when I try to update/download tf2 from the steam library, it loads until like 95% and then just stops. If I try to resume the download, it immediately stops. When I try to launch tf2 through the tf2 icon on the windows desktop, I get an error message saying there is a disk write error, pointing specifically to a vrad.exe file or shadercompile.exe, which were the files flagged by my antivirus.
I have tried deleting and redownloading tf2, verifying integrity of game files (which shows "All 158 files successfully validated") and reparing library through steam settings, none of which has worked.
Another weird thing is in steam settings under storage, which is where I have the option to repair library, I can see the games I have downloaded and the size it occupies on my disk, where tf2 shows as 0 bytes. But in the steam library it stops downloading at around 12.5 GB, and going into manage > browse local files under tf2 I can find the tf2 folder which says its at 470 kB.
The only solutions people say they have with the "disk write error" is that they remove the Disk Write Protection through steam properties, which does not work for me, sadly.
Is there any kind soul who has a solution to my problem? I would be super thankful!!

Valve has kicked out a second update which should see better behavior from affected antivirus solutions; therefore NO ALERT anymore.

It was a rather great run for users of Avast's antivirus, as although in the distant past it had a reputation for occasionally triggering false positive detections with TF2 updates, Avast has since behaved itself quite well for several years.
With today's MAJOR TF2 update for 4/18/24 that brings in x64/AMD64 support, a pile of the game's executable files have been updated for the AMD64 architecture. However, this appears to have done an exceptionally good job at getting Avast's alarm bells to ring when they shouldn't.
There are also a few reports that users of Bitdefender's antivirus solution are also affected this go around as well. AVG users appear to also be affected (AVG has been owned by Avast for several years, but have different products).

Reporting files as false positives - for avast! users

Presuming you're on a recent version of Avast from the past several years, you may have gotten a blue dot on its Windows system tray icon indicating you've got new notifications to look at.

1. Open avast!
2. Click "Notifications"
3. Check for a "Threat blocked" notification that should state that avast! picked up either vrad.exe and/or shadercompile.exe
4. Click the green "Open Quarantine" button
5. Click the checkboxes on the left side of one or both files
6. Go to the 3 dots in the bottom right, then hit "Send for analysis"
7. Select the "False positive" radio button
8. Fill in the description by saying these were files recently changed as part of an update to TF2 that are legitimate (or feel-free to copy and paste this blurb in there if you're lazy: "False positive caused by new Team Fortress 2 update.")
9. (optional, but recommended) Include a link to this thread in the description of your report
10. Hit the Send button

Afterwards, feel free to use the "Restore and add exception" button to get playing again.

Reporting files as false positives - for Bitdefender users

Before reporting false positives, Bitdefender users will need to fetch affected files out of their quarantine. See https://www.bitdefender.com/consumesupport/answe2092/ for instructions.
Once you've done that:

1. Head to https://www.bitdefender.com/consumesupport/answe29358/
2. Select "False Positive" as a category
3. Put in a name (although it says full name, in theory nothing stops you from using a nickname instead)
4. Put in a good email address to be contacted at
5. Select "File" for your sample type
6. Hit "Choose file" and navigate to where you extracted affected files from Bitdefender's quarantine
7. Write in the detection name from Bitdefender's Notification/Events window
8. If you'd like, fill in the description by saying these were files recently changed as part of an update to TF2 that are legitimate (or feel-free to copy and paste this blurb in there if you're lazy: "False positive caused by new Team Fortress 2 update.")
9. (optional, but recommended) Include a link to this thread in the description of your report
10. Click the reCAPTCHA checkbox and hit the Submit button

Be aware however that you shouldn't add the TF2 directory to the exclusions list in the event of a real emergency, even if having to deal with the odd false positive once a while is annoying.
Even if done for supposed "performance benefits", these benefits would be extraordinarily miniscule on a modern system with solid-state storage.

Via the Steam Community:

• Added 64-bit support for Windows/Linux client and server
  
  • Should include performance improvements for most users
  • Bugs can be reported here: https://github.com/ValveSoftware/Source-1-Games/issues
• Fixed an exploit related to uploading invalid custom decals that would crash other clients
  

Rumor has it:

• avast!, AVG, and Bitdefender users should all be aware that false positives are likely to be triggered with the x64 .exes included as part of today's update (including vrad.exe and shadercompile.exe)
  
  • Valve has shipped a fix with update #2
• As mentioned above, the addition of 64-bit support is exclusive to Windows and Linux, and the x86-64/AMD64 architecture
  
  • The status quo of TF2 being unplayable for macOS users on Intel Macs running macOS Catalina (10.15) or later, and Macs with Apple Silicon still remains true after this update. There is no word on whether an AMD64 and/or ARM64 port will occur for Mac users, but given inaction up to now plus Counter-Strike 2's abandonment of the Mac, it appears unlikely
• Additionally, a round of updated localization files have snuck in, made possible in part by contributions from Translators Like You - Thank You
  
• Size is ~315 MB - data capped users should be aware
  

So, after years of safely using The Internet, I had an idiot moment yesterday and downloaded and run an infected setup. Only realized what I've done after the installation finished and nothing had happened, there was no installation folder in Program Files where it was supposed to be. Thing asked me if I wanted to install some sketchy AV program in the process, I refused.
Found out it's a virus. Panicked.
I did my best to remove it, but am still worried it could be hidden somewhere and would like to avoid doing a complete Windows reinstall. Do you think I'll be fine?
Tried all of this:
Perma deleted the setup application.
Went through the whole drive (the second one too), all hidden folders including AppData and perma deleted all files that had changed that day. While doing this, I found a suspicious .exe in the Temp folder that some googling confirmed to be malicious (clearRemnants.exe). It should be technically gone, but I'm still paranoid.
Went through installed programs, nothing that appeared recently.
Ran an Avast full scan. Nothing. (Considering switch ing to BitDefender after this.)
Went through every process in Task Manager, nothing suspicious.
Installed Malwarebytes, did a scan (not sure if complete). Nothing.
Updated Windows Defender, ran an offline scan. Found something that modifies file activity? (Misleading:Win32/Lodi) Deleted, presumably.
Checked the hosts file in System32/drivers/etc. Looks fine. Checked network connection - all set to get IP address/DNS automatically. One had an IPv6 filled in, but that could've been by the program that mediated the connection. Disabled. Disabled remote access while I was at it.
Checked the registry keys. None named suspiciously/registered to the company, but I wasn't very thorough - that would take hours. Not too sure if safe.
Reset settings in all web browsers to default.
Went into Safe mode. Cleaned temp files, cache, temp internet files. Currently running Malwarebytes complete scan. Plan to do RogueKill, KVRT & HitmanPro later. Also, Win Defender full online scan, though idk if it will do much (doesn't even load properly rn).
(changed my Google pass already, probably should change the rest as well)
The PC seems to run fine - the start-up & login is a bit slower than usual, but that might just be my laptop getting old. Do you think there could be any risk of transferring the virus if I were to plug in an external drive and back up my stuff?
Thank you!

I've been using Ubuntu 22.04LTS on WSL for years now, but a couple weeks ago I have gotten this and haven't been able to fix: At WSL Startup: *Installing, this may take a few minutes... WslRegisterDistribution failed with error: 0x80070422 Error: 0x80070422 The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.*

• I've uninstalled and reinstalled WSL+Ubuntu using the MS Store. during some installs I get that updates to kernel needs to happen, I do the wsl.exe --update with no issues.
• LxssManager is running fine and doesn't need manual starting, this seems to be the most common solution like in this thread: https://github.com/microsoft/WSL/issues/3815
  • I'm not running Kapersky which can cause this issue. I am running Avast, but even if I disable it same issue.
  • BIOS has virtualization enabled.
• I've done all these steps as admin.

In Windows services: WSL startup=automatic, but it is not running. I'm not sure if that is normal or not? If I start it it says "started and topped, some services stop automatically if they are not in use by other services or programs" I'm not sure if this is normal or not?

• To see if that is normal, this thread https://github.com/microsoft/WSL/issues/2851 says do this
  • Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux: I get online=true, restarneeded=false. Which I believe is the expected successful result.

Help very much appreciated, thanks for reading!

bought this week the THR30II Wireless and I would like to use a pc to tweak the tones and check if the THR has the latest firmware.
have a windows 11 pro (with enough free space 50GB)
this windows is updated with the latest updates
I also investigated with the windows devicemanager the 2 devices 'microphone (THR30II Wireless)' and 'speakers (THR30II Wireless)', which were already equipped with the latest drivers.
THR connected via a new UBS B - USB C cable
THR Remote exe 1.3.2.0 (latest version for windows)
configured an exception in my Avast virus scanner : added the folderpath in exceptions so that this exe is not interfered by the virus scanner.
​
if I start the software and then attach the THR from the moment I attach it, I see that the THR is attached but the executable disappears after a few seconds.
Even if I start the program when the THR is already connected.
Does anyone have a workaround for that ?
Is it true that you can only connect the desktop application via cable and not via usb ?
I also have an iphone with which I can pair the THR via bluetooth, but I see no possibility to upgrade the firmware.
​

I have a laptop with windows XP, and yesterday when booting all it played was the splash screen, and then just pure black, not even the mouse showed up, I still could hear audio
I've tried all of the following solutions 1- remove the battery and let it rest, I've done it a few times for hours, it didn't change anything
2-safe mode When booting on safe mode it seems to get stuck loading on a driver on system32 named "aswbidshx.sys" which may be causing the problem, but I'm not sure if I should delete it on the manual repairing, specially considering it's for system32
3-shortcuts to open explorer.exe, since not even the mouse would appear, nothing happened, and I doubt explorer.exe is the problem
I could try to remove the graphics card drivers manually on the command line, but i would need a guide since I suck at it
(UPDATE) I've found a 3GB empty partition in my SSD, I've installed another windows XP copy there, I copied a few files to an USB in case I had to format, and I deleter the aswbidshx.sys file, it's only an Avast antivirus driver, I've deleted it, I'll try to boot on safe mode and change the graphic card drivers so it'll hopefully work

Hello-
In the last 48hrs I've had issues pop up with my memory (it seems). I first noticed that Helldivers 2 started crashing on start up, when joining a game, or now it just runs super choppy. I've had no issues before yesterday. I tried running Midnight Sons to see if its just HD2's bugginess, but now Midnight Sons crashes when I try to load a game and gives me a memory error. I've had the game since launch and never had a single issue. Here are my specs:
Nvidia GTX 1070TiAMD Ryzen 7 2700 8-coreAS Rock X470 Master SCI16gb RAMWin 10
Here is benchmark: https://www.userbenchmark.com/UserRun/67410809
Here are temps: https://imgur.com/E6MR5II
Here's a pic of my memory situation: https://imgur.com/IFcDQie
Here's some background:
I had a very old mechanical external HD fail. I installed a few programs including diskdrill to try and recover it. Turned out it was unrecoverable. I uninstalled the programs. I added a new SSD (it is the same model as another external SSD I'm using). I installed PureVPN. Read its trash. Uninstalled it. I uninstalled AVAST and set up Window Defender to be my primary. Went to Bleeping Computer forum to get some help to determine if I have a bug. So far they are suggesting no.
I've updated drivers across the board. Updated my bios. Tried the Gameinput Service fix. Nothing I do seems to have an impact. 2 days ago games ran fine. Noticed last night that trying to play Helldivers 2 I kept crashing at start or when I began to enter a game instance. Then tried to boot up Midnight Sons and it crashes when I load game. I get an error that reads:
"Out of video memory trying to allocate a rendering resource. Make sure your video card has the minimum required memory, try lowering the resolution and/or closing other applications that are running. Exiting..."
Around the time that all this was going on last night, I was also getting Chrome errors that said "Aw snap" and something about being low on memory or something.
When I open event viewer I see a few memory related messages:
1) Application popup: Windows - Out of Virtual Memory : Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help.
2) Resource-Exhaustion-Detector: Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: MidnightSuns-Win64-Shipping.exe (2636) consumed 11467534336 bytes, MsMpEng.exe (5100) consumed 405340160 bytes, and steamwebhelper.exe (19264) consumed 393285632 bytes.
Again, what's baffling is that I've never had any issue running any game on high settings. This just happened yesterday. I've included what I can think to include that I've done that might have affected the PC. I can't imagine why any of that would have led to memory issues, which seem to be the heart of the problem. The benchmark seems to agree.
​
Any guidance is welcomed.
​

Was working fine till it seems Windows 10 did an update. Both of windows and the Nvidia Geforce GTX 1660 super driver. (FU ms.) Not it seems to connect but no screen output to it. Mouse doesn’t even go over to that screen. Screen is connected wirelessly and has been for a year plus.
System Specs Windows 10 Pro Version 21H2 OS BUild 19044.3930
Spacedesk shows 1 connected Local Area network. Under connection time shows connection ongoing. Connected at 11.08.53 AM.
Network Adapter Interface shows Interface alias WiFI Interface type Wireless802.11 IP Addy 192.168.x.xxx SPeed 72Mbps Network Profile Private Active connections 1 192.168.x.xxx:28252<==> 192.168.x.xxx:45996
Third party security products shows Products 2 Windows Defender Avast Antiviruus Firewall products 1 Avast Antivirus AntiSpyware 0 No Third party antispyware software detected.
Incompatible Products X nvidia shadowplay/in game overlay/ screen recording X Ch Product (joystick and other control device drivers
Incompatible Legacy Display Hook Drivers X lci (uninstall is greyed out) x mctdesktopsever.exe (greyed out) x FlxHClv.sys (greyed out) Bottom is version 2.1.11 expiry of free dec 31 2024
I’ve searched entire net/reddit/Ms.Cleo. Can’t find a solution that works or figure it out. Hope theres someone here that can. Thanks

Recently a new malware has hit the grey and not so grey areas of the internet. It can be found within freeware, hacked apps and games, updates and more. Even if you never touch any pirated things you can still end up with this nasty piece of code without even knowing! I tried all the major contenders, Malwarebytes, Avast, Kaspersky and then some - none were able to detect Main.EXE as a concern, let alone that it is stealing data. The ONLY indication of something going wrong came from my firewall when it asked about Main.EXE getting internet access.
For me it came with a 'free PDF Editor but since I discovered the issue and details I found over 20 freely available apps and a list of 'free' games containing not just the ads to make it free. The good Malware protection apps WILL notify you about Main.EXE being suspicious but not that it is a real threat. Removing it however fails as the Main.Exe is created in sub-folder of your TEMP folder during the Windows start. You can remove it as often as you like but it keeps coming back. This is because the malware uses a hidden update feature for the long gone Internet Explorer. And the USERS App data folder there will be a section for the Internet Explorer. In there you find either an Update.EXE or an Updater.EXE -both work. ONLY ONCE this file is removed the malware is gone.
Removal or just figuring out that you are infected is a bit tricky. As no tool (at the point of writing) is able to properly detect AND REMOVE this malware.... Here is a way to get going: Go into your Windows settings and delete the TEMP folder contents. On many systems you will find TWO folders, one TEMP, the other TMP. If in doubt check your system path and use the Windows Explorer to delete whatever is in there. There will be several items refusing to be deleted. Some are from running process that are legit, but if it is in some cryptic folder it is most likely malware. In the leftovers you will then find this Main.Exe and see that you can't delete it. By using the Task manager to end the Main.Exe process you can delete the file and folder it is in. Deleting the Update.Exe in the USERS app data folder does not work this way as the malware won't show up in the Task manager, means you can't end the program. The FREE Process Explorer from Microsoft can show you the running Main.Exe and also that it is called and created by the Update.Exe - together with the actual path as this can slightly vary. End both using the Process Explorer and you can delete all traces of this nasty malware from your system for good. Or until you try to install some infected things again...
Ok, but what does this malware do and why is it not detected? It starts by gaining full administrator rights on the Windows computer. Edge long replaced the Internet Explorer but Windows still supports it. Oh! Look! There is an update for the Internet Explorer, we better start it before the user needs the Internet Explorer.... And so the Malware does it's job..... No matter the browser you use it will quickly find all websites you visit that use a login of any kind. These login details are intercepted and stored in a text file inside the malware's temp folder. You then even check and see how many of you accounts already got compromised...... Means, once the malware is gone you should change all those passwords right away! On top of that it also intercepts the usual Email clients one might have installed. Stealing security certificates, login credentials and details about the server connections the client uses. It does all this and then some by running as hidden task and acting like a smart key logger. For you Email client and other apps it is often able to not only get the required (encrypted) details but also to decrypt them to get all vital things in plain text. Nasty indeed.
Detection is next to impossible as the initiating malware, our fake updater, runs so hidden and so clean no anti-malware solution finds anything wrong. All the bad code is downloaded on the fly and will only be detected once getting active - and here most protection suites fail to prevent the upload of your data. The updater creates the Main.Exe in the Temp folder and it is then executed with elevated privileges. First thing it does is to download more code, which is called upon directly - again fooling anti-malware suites because the files with the bad code are encrypted and only once executed in memory they can be detected. So even if you protection suit prevented the worst, it won't be able to remove the thing. Only a good firewall blocking it from all internet access will help. Sadly the settings for it need to be right as otherwise it runs .... Means you need to make sure that ALL new apps and process require a manual confirmation. Without this the malware will be seen as a legit Windows process that has full access.
Any variations out there? Sadly yes :( So far I found 5 different names in use for the temp folder being created. And on top of that not just Main.Exe, but also Run.Exe, Scheduler.Exe and Start_XXXX.Exe where the XXXX can be literally anything. They all share the same creator in the Internet Explorer's FAKE Update.Exe in the user's app data folder. They also share very similar file sizes and they all create the same text files filled with your vital data.

So, I first noticed about a week ago that on my (Microsoft Windows 11, HP Omen 45L gaming Desktop GT22-0xxx, X-64-base PC, System SKU: 3K1G6AV) computer in Settings>Network & Internet> Advanced network Settings> Data usage that the "System" was using a lot of network data. Like 100GB a month or 2.5gb a day... which seemed insane and not okay. I'll go ahead and skip the part where i was 100% convinced that this was malware and frantically Used Malwarebytes, Windows Defender, Task Manager, Virus Total, GlassWire, Avast Antivirus, Volatility Workbench, WinDirStat, and countless other Applications and programs to find the malware, becasue guess what, I didn't find shit! and realize now how that's what you don't do. Anyway... when I open task manager I see that the process "System" is using like .01% or less of network data pretty frequently. When I click on the process and click "Open File Location" it directs me to "ntoskrnl.exe" which seems like a normal Windows applications... I think? I did some googling and saw a couple potential fixes, but nothing exactly describing the problem that I am having. I saw that it may be windows constantly looking for updates or failing updates, or a variety of potential causes.
I went in and tried to find the cause, and I never could(because I don't know shit about this stuff) I tried to be as careful as I could because I know playing around with system files is dangerous, but I think I may have messed up my system even worse. I have had two BSOD which I have never had in my life, let alone on this 2 year old Computer. Looking in Event logs I see my computer has many critical Events but I don't know how to interpret this data...
​
My questions are...
what is using the network data within System?
How can I submit Error Reports? To y'all here on this sub or to Microsoft support
Is there a way to "Factory Reset Windows 11" Without Erasing all my dad and information currently on this PC. (I know I could create a backup, But im very busy at the moment and dont know how long this whole process will take or if it will delete any of my important work files/projects.
Any insight is greatly appreciated other than "It's not malware bro. MalwareBytes Scan and you're good"
Thanks,
​

Recently, I've installed simplewall on my main system and I couldn't help but notice that Avast has a whole bunch of executable files that are asking for internet access:

C:\program files\avast software\avast\aswtoolssvc.exe C:\program files\avast software\avast\avastsvc.exe C:\program files\avast software\avast\avastui.exe C:\program files\avast software\avast\avemupdate.exe C:\program files\avast software\avast\setup\instup.exe C:\program files\common files\avast software\overseer\overseer.exe 

I allowed all of them for the time being. But on a second thought, are all of these really required for the core functionality, such as receiving updates?

Recently, I've installed simplewall on my main system and I couldn't help but notice that Avast has a whole bunch of executable files that are asking for internet access:

C:\program files\avast software\avast\aswtoolssvc.exe C:\program files\avast software\avast\avastsvc.exe C:\program files\avast software\avast\avastui.exe C:\program files\avast software\avast\avemupdate.exe C:\program files\avast software\avast\aswidsagent.exe C:\program files\avast software\avast\setup\instup.exe C:\program files\common files\avast software\overseer\overseer.exe 

I allowed all of them for the time being. But on the second thought, are all of these really required for the core functionality, such as getting updates and identifying threats that are not yet in the virus definitions?