sutepanushikind
Member
looks like fixed for me in 26.1.2
Win 11 24H2 and 25H2 both bombing in Parallels 26
- Thread starter Zeos100
- Start date
sutepanushikind
Member
nvm, BSOD happened again in 26.1.2, I didn't use VM(was idle) that time. a few apps opened, so it's not a RAM full problem.
what interesting is it happens more often after Windows Update. Windows Update installs -> reboot -> ... random time ... -> BSOD.
And Paralells hung when I tried to send tech report, so I force closed it. After reboot VM seems all good.
what interesting is it happens more often after Windows Update. Windows Update installs -> reboot -> ... random time ... -> BSOD.
And Paralells hung when I tried to send tech report, so I force closed it. After reboot VM seems all good.
VoidB
Member
That sounds so cruel. Constant bluescreens + reboots under Parallels Desktop 26 with Windows 11 24H2/25H2 definitely isn't normal. To determine whether it's a Parallels bug or a Windows bug, I would try going back to a clean 24H2 install with no tweaks or mods, making sure Parallels tools are fully updated, and disabling any dubious virtual-hardware tweaks.
VoidB
Member
That sounds so cruel. Constant bluescreens + reboots under Parallels Desktop 26 with Windows 11 24H2/25H2 definitely isn't normal. To determine whether it's a Parallels bug or a Windows bug, I would try going back to a clean 24H2 install with no tweaks or mods, making sure Parallels tools are fully updated, and disabling any dubious virtual-hardware tweaks.
sutepanushikind
Member
me too, still BSOD on 26.2.0, happens every time after monthly Windows Update -> reboot -> disk cleanup -> don't use VM, give it some time in idle(for example, go eat a lunch) -> return to my Mac -> see a black screen with CRITICAL_STRUCTURE_CORRUPTION -> reboot -> wait for a month and it will happen again.
It's so stable, I don't believe in hardware issue. Maybe 8GB RAM is not enough, maybe blame Symantec Endpoint Protection, maybe another sun flare, but in reality, it's more likely to be a Parallels bug, which no one knows how to fix, and it just as is. For me it started when version number changed to all new 26.0.0.
It's so stable, I don't believe in hardware issue. Maybe 8GB RAM is not enough, maybe blame Symantec Endpoint Protection, maybe another sun flare, but in reality, it's more likely to be a Parallels bug, which no one knows how to fix, and it just as is. For me it started when version number changed to all new 26.0.0.
sutepanushikind
Member
translated above ^^
"Version 26.2 still experiences blue screens, sometimes not for several hours at a time. Other times it occurs every few minutes, with no clear pattern. However, switching to Apple's Virtual Machine Monitor seems to eliminate this issue, although performance noticeably decreases." (Google translate, dont expect high quality)
btw I had 1 more BSOD today 26.2.1 - after another Windows 11 update - not fixed yet...
"Version 26.2 still experiences blue screens, sometimes not for several hours at a time. Other times it occurs every few minutes, with no clear pattern. However, switching to Apple's Virtual Machine Monitor seems to eliminate this issue, although performance noticeably decreases." (Google translate, dont expect high quality)
btw I had 1 more BSOD today 26.2.1 - after another Windows 11 update - not fixed yet...
I REALLY need help! I loaded a new Windows 10 program into Parallels 26 on Tahoe Intel Mac Mini. Nearly always get BSOD but after 'resetting' numerous times desktop occasionally appears with a strange little box in center. Desktop is dead. Finally downloaded Windows 11 right from Parallels 26 and I get the same problem. After numerous 'resets' I FINALLY get the message that 'your device ran into a problem and couldn't be repaired. I've been at this for a couple of days and many hours. It it, too, bad there isn't someone from Parallels that can work me through this, especially considering all of the versions I've purchased over the years. This is maddening and SO frustrating. The old Windows 7 pvm's work fine. Windows 7...HELP!!! By the way, I have followed EVERY suggestion and made every suggestion regarding changing hypervisor, updating Parallels 26 AND making sure that TPM was set up. Man this is frustrating!
sutepanushikind
Member
Hello, I'm not technical support, just trying to do what I can to help.
I think Parallels knows about this problem, but they have no time to fix it yet.
In another thread some people had success downgrading to 20.4.1.
If You absolutely need stable VM, try to downgrade.
https://www.parallels.com/jp/products/desktop/download/ -> select version 20 -> Parallels Desktop 20 for Mac Image -> download dmg
Good luck!
sutepanushikind
Member
also that "another thread" is here: Since version 26.x upwards - Windows 11 blue screen - CRITICAL_STRUCTURE_CORRUPTION | Page 2 | Parallels Forums same problem.