Win 11 Crashing - Probably Excel Related

Thank you, I hope that goes well.
I have not used the machine enough since upgrading to 26.4 to notice any trend although yesterday I came back from lunch to find that Windows had rebooted.
That is different to before, as previously it always crashed whilst I was working in it (usually Excel) and also it would just leave me back at the Mac desktop. Of course yesterday could have been coincidental.

I am also following this interesting thread, which I presume may be related:
https://forum.parallels.com/threads/vm-running-mac-memory-out-to-100gb.369767/
 
May not be the same issue I was experiencing. But might be worth a try to fall back to 26.2.2 version in my other post. I had to do an uninstall, then install the downlevel version.

I am on 16in MBP M5 Max with 48GB memory. I upped my VM from 4 vCPU to 6 vCPU, 16GB memory to 24GB memory. I beat the heck out of the Win 11 VM daily. Multiple Excel workbooks open right now. One of them is 185k rows and 29 columns. Filtering, pivots, and xlookups. (4) Other Excel workbooks, one is only 36k rows, but loads of pivots and tables calculating stuff from the Pivots. Also have Access open with linked tables, and the local table that created that giant workbook. (6) PowerPoints. Of course Outlook, OneNote, CoPilot...No Visio opened right now. Just wanted you to understand my workload.

If you fall back and still have issues I would open a case. For me throughout the day the VM memory usage would grow and grow. On days where I would hit 240-250GB memory usage, it would crash. Guessing some sort of a barrier at 256GB. I was rebooting every morning to help avoid it, which was an inconvenience. I knew it had to be a bug as I had a 14in MBP I took back after a week, that had the same issue. They had me build a fresh VM using the MS Download. Took me about a week to fully cut over to the new VM. They also provided detailed instructions for collecting all the data they needed. Was easy to do and upload.
I also had the same issue, and the sudden jump in Parallels memory usage is the part that really stands out to me. A crash after scrolling in Excel could point toward some interaction between Excel, Windows ARM, Parallels Tools, and the graphics/display layer, but seeing the Parallels process grow from around 8 GB to more than 120 GB even while the VM is mostly idle sounds like something more unusual than normal workload-related memory consumption. I would be interested to know whether the memory continues increasing if Excel is completely closed, because that could help separate an Excel-related problem from a Parallels/Windows VM issue. Checking Activity Monitor for memory pressure and the Parallels VM process while reproducing the problem might also reveal whether the allocation is being reclaimed or simply continues growing until macOS runs out of resources.
 
Back
Top