I am currently getting Green Screen of Death errors when upgrading Windows 11 Canary to version 27718. It comes up when the upgrade reboots, then of course rolls itself back. I was able to collect the crash dump from the upgrade which identifies the IDS Core Driver idsvia64.sys as the cause. The file itself has a date of 9-24-2024, which means whatever Norton update updated the file is also a culprit.
Is there anyone running Norton 360 and Windows Canary version that is able to get this to work? Maybe in the v24 version, which I have not yet received?
On Sun 10/6/2024 7:40:35 PM your computer crashed or a problem was reported
crash dump file: C:$WINDOWS.~BT\Sources\Rollback\setupmem.dmp
This was probably caused by the following module: idsvia64.sys (IDSvia64+0x3E6DB)
Bugcheck code: 0x1A (0x380, 0xFFFFF802C00BC703, 0xFFFFDF8E568D6AF8, 0xFFFFDF8E568D6320)
Error: MEMORY_MANAGEMENT
file path: C:\Program Files\Norton Security\NortonData\22.22.1.58\Definitions\IPSDefs\20241007.001\IDSvia64.sys
product: Symantec Intrusion Detection
company: Broadcom
description: IDS Core Driver
Hello trongod. Straight away you are running an Insider Preview build of Windows. In respect to that, Norton doesn’t support BETA/Insider OS build and cannot guarantee their products will function correctly if used with them. IDS Core Driver idsvia64.sys, as detected, would be the incompatible system file that Norton isn’t compatible with. It is the Norton intrusion prevention file. The bug check code 0x1A is the memory corruption shown as a result of that incompatibility. All the other errors are related to the Canary build incompatibility.
The newest version 24.xx most likely will not garner any solution either. Norton cannot guarantee nor support Windows versions that are not official. Version 24.xx is also throttled and not yet released to everyone as of this posting.
SA
1 Like
I consider this post raising awareness because if it doesn’t get fixed, it will ultimately find its way to the mainline builds.
Yes, awareness indeed. Nothing needs fixing with your Norton software. The issue isn’t with Norton, the issue is, that BETA release OS builds, are not tested by A/V makers. There is no feasible nor cost effective way to create software that is tailored to that. Their products are designed around fully released OS versions. Microsoft is notorious for bug riddled insider releases which come and go much like the weather changes. I’ve been an insider previously and speak from first hand experience with it. Norton and other software may install and initially run on insider releases, at some point with the constant changes users will run into issues like the one you are seeing.
SA