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

BenMc said:
I have also been having this problem, and rather than replying at the time I just downgraded to 20.x That does seem to have fixed it.

What I had fogotten though was that a few years back I suffered a lot of slowdown issues - the VM would run normally and then suddenly freeze for 10-20 seconds, then come back. I delved into system logs and found I was getting hard drive timeout errors.
After suffering this for months and nearly driving me to my wits end, I stumbled across a post mentioning Time Machine snapshots. And lo and behold, deleting them completely fixed it.
While I have fixed it for now and don't need to go back to the latest version, I suspect that this may be the same issue. Here's past detailing how to remove the TM snapshots. Definitely woth a try. Please post back to let us know if it did or did not work.

https://forum.parallels.com/threads...-screen-critical_structure_corruption.368907/
Click to expand...

In my case I was not using ANY VM snapshots as using Mac Time Machine. After the corruption hit I did some which does not change the status too much. For my situation only fall-back to the Parallels version 20.4.1 works now stable for weeks (Windows-10 and WIndows-11 VMs both failing with 26.x and both flawless now with 20.4.1) , HENCE I am not willing to make any upgrades until Parallels will CONFIRM officially that the issue has been found and solved.
Who knoes the currents status from PARALLELS for this critical problem?
 
OK @MarekC1! Just to clarify, these are not VM snapshots I am talking about. The Time Machine software on a mac automatically creates AFPS drive snapshots as part of the backup process. These are not mentioned anywhere and I didn't even know they were there until I read the artlcle and looked. Apparently they are automatically removed after a period of time (weeks, I think, not hours). These are what cause the issue.
I had posted and participated in mutiple issues on this forum but Parallels support didn't seem to be interested in incorporating this into their knowledge base (possibly because it is not their doing, although it causes extrememly serious issues with their software). I doubt they have made the link, if this indeed is the solution. I do have TM snapshots present which, if my theory is correct, may have caused the issue. Like you, I am back on v20.x and don't really want to spend the time got forward again to test, until I absolutely have to. I was hoping someone still experiencing the issue might try this.
 
High Ben, I am not using VM snapshots at all. Once a day after finishing work I am doing a manual backup (pretty old school - I know). So my problem appears to be 100% caused by the Parallels version as the situation was
- Version 20 - No issues at all (daily VM backups)
- Version 26 - Issues appeared in 2 independent VMs (Win-10 and WIn-11) (Daily VM backups)
- back to version 20 - all back to normal - no issues (Daily VM backups)
So daring to say it IS parallels 26 version causing the problems.
(as additional information I am on Mac Pro with Inter processors).
 
How the hell is this still happening! FFS Parallels - get it together. I can't even log into a completely vanilla W11 install, or W11 template that works fine on previous versions without it completely locking up my mac to the point i have to hard reset. Totally unacceptable. Reeks of "I've got my money F off consumer, we have no accountability."
 
@SaltH, did you check for the Time Machine snapshots as per above? Still curious to see if that might be the issue. @MarekC has I believe repeatedly misunderstood what I'm taking about.
 
Same issue here. Opened a ticket and sent all of the debug info and they just closed the ticket saying basically it's a long term issue they'll get round to. All versions of 26 cause all of my Windows 10 & 11 VMs to blue screen randomly; sometimes immediately after booting, sometimes within the first hour and sometimes after half a day. I have Windows 2000, XP & 7 VMs and even would you believe an OS/2 VM for some jobs - none of which suffer crashes on 26. Every time a new sub-version of 26 is released I update, wait for the crash then revert back to the rock-steady 20.4.1.
 
I've been having the same problem, with my VMs randomly blue-screening. At first, I didn't even realize that the VMs were crashing, since autoreboot was on. I'd walk away, and come back and none of my applications were running. So I shut off autoreboot, which made it a lot easier to notice when VMs crashed. After reading this post I decided to go back to Parallels 20.4.1, and my VMs are now stable again. I wonder how I will know when it is safe to start using current versions of Parallels again?
 
As of now, the 26.3.2 update still hasn't solved this problem. It seems there's absolutely no need to buy an annual subscription in the future, because the new version is completely meaningless.
 
I accidentally updated to the latest version again and was able to test removing the AFPS snapshots as I suggested earlier in this discussion. No difference, still get BSODs every few hours. Have reverted to 20.4.1. Parallels is unusable at its current version for me.
 
Thank you @Glen_Parallels for your feedbck.
Then I will wait with the update to 26.4 until further confirmation as I am using both 10/11-Windows-VMs for the business work and can't afford any BluesCreens or other negative experiments here ;-) (20.x is verystable).
Looking forward to any feedback from the community - whoever dares to try - thank you.
 
You must log in or register to reply here.
Back
Top