Since version 26.x upwards - Windows 11 blue screen - CRITICAL_STRUCTURE_CORRUPTION

Hi!

Since I upgraded Parallels Desktop for Mac (Intel) to a version higher than 20.4.1-55996 (beginning with the first public 26.x version) I get CRITICAL_STRUCTURE_CORRUPTION blue screens in my Windows 11 VM at least one time per day.

I read about problems with Norton 360, and as we are using Symantec Endpoint Protection (SEP) I assume, this might have something in common. But as the basic machine configuration and software is provided via our data center, I am unable to dive deeper into it, ie. uninstall the Symantec stuff or whatever - I am simply not allowed to. And as the Windows event log is really HUGE I am not exactly sure where to look for any information that might help.

A bit of history to this...
It all started with the first public version of 26 (before the Norton 360 fix) and I decided to downgrade back to the last 20.x version. That did the trick for some time. But when 26.x with the Norton fix came out, I thought it might be a good idea to try 26.x again. It was successful at first, but after our data center initiated our monthly system infrastructure update, problems came back. So I am tempted to step back to 20.x again now if I don't find a solution - but if I downgrade again, I am stuck with my current MacOS version, so I am biased...

Maybe someone has an idea what I can do about it, as a blue screen or two during a Teams meeting is rather annoying. If not, I will downgrade to Parallels 20.x and stay with my current MacOS version Sequoia 15.7.2 for now.

Regards,
Holger

 

I have also experienced this multiple times since upgrading.

 

Had several crashes with CRITICAL_STRUCTURE_CORRUPTION bluescreen as well.
I downgraded yesterday to v20 and the VMs run stable again

 

@Ashley Chumun As I am unable to answer your emails you sent to rechnung@... (it is only a incoming mailbox for invoices and official notices I cannot use for outgoing mails), here my answer to your last support mail - and sorry, I cannot always respond as fast as you might expect :

It was so kind that someone filed a ticket because of my forum post, but I am unable to reproduce the error atm.
History:
* After having posted my problem last week I downgraded to 20.x.
* Then, on last Tuesday, our data center pushed some regular updates to our client machines, including Symantec Endpoint Protection.
* After that, I thought it might be worth trying 26.x again, upgraded and did not experience any BSOD up to now.

But I wanted to test in different situations (working via VPN, from LAN, with different kind of external hardware attached and such) until I can say that it seems to be solved. This test will last at least up to next week until I can say anything further.

So I am sorry that I cannot provide a dump atm. What I can do is to promise that I will send some in case it happens again.