On my new FW 13 Pro, I got now three BSOD showing hypervisor error (0x20001) over the last roughly three weeks. All at very light tasks (like reading a Wikipedia article).
Never had that with previous laptops (all Lenovo X1 Carbon).
Gemini suggested to turn off core isolation, which I have just done. However that shouldn’t be a long-term solution afaik.
I just wondered whether other users also experienced the same error, and whether that is known to Framework staff? Maybe this is a BIOS issue.
OS: Windows 11 Pro, 25H2, up-to-date
FW 13 Pro, Intel 358H, 64GB RAM, 4TB SSD (all supplied by FW).
BIOS: 3.02
All FW provided drivers installed, plus additional drivers as shown by the Intel Driver & Support assistant.
Where is “core isolation” adjusted? Is that a BIOS option? Did that resolve it permanently, or does it happen less often? Has this caused a knock-on problem?
That is a strange error. Might be good to check the integory of windows using a sfc scan and dism check. If it has managed to corrupt itself (sadly it can happen easier than one might have thought) it could be throwing a fault like that. Strange that it comes up as a hypervisor error unless the OP is running virtual machines in Windows.
Core isolation: This is a setting with Windows Security: usually, memory integrity it turned on (default), which I also had turned on until that BSOD just recently occurred the third time. Now it is off. Hard to tell if that will make a difference, as the BSOD only appears about once a week.
Weird error, nobody should need to disable core isolation unless unsigned drivers are required and usually a blue screen shows differently not such a fine print. Any hints from Event Viewer after the restart just before the “Critical” event that was the BSOD? Did you test the memory using memtest86?
Memtest86 didn’t reveal any issues, see screenshots below.
Core isolation: Gemini suggested it as a temporary fix to see whether the error disappears.
It also suggested that it may be caused by a low power CPU state that hasn’t been correctly supported by BIOS. That is the main reason why I posted it here:
I had hoped that Framework would pick it up and would improve the BIOS version.
There have been reports of freezes and then reboot (FTR) on FW13 and FW16 AMD.
These may be associated with various power save modes.
Your problem is with intel so the cause might be different.
Memtest unfortunately does not test for memory faults while changing power modes so unlikely to pinpoint the problem.
What cards did you have plugged into the slots? Remove them all and see if the problem re-occurs.
I have two USB-C slots, one HDMI, one USB-A.
Only one USB-C is used, but I cannot just remove that one as otherwise I cannot work with the laptop any more. If the FW13 Pro cannot reliably be used with the cards, I think I have to return it.
Why did you suggest removing the cards in the first place? Is there an indication that the cards malfunction?
Without the cards, I cannot power it any more, so of course, without battery, the laptop will no longer show this error as I cannot turn it on.
Note that I said this error occurred 3 times over 3 weeks, so not really frequently, and I cannot directly reproduce it.
I am just another user like you.
Some faulty slot cards have caused problems for others, so i was just suggesting remove them to maybe discount that as a cause.
For official FW support, fill in the support form on their web site.
Like it was mentioned before we are all end users here on the forums. Nobody else has reported a similar case so far however the Core 3 series boards of the Framework Pro are really pretty new.
Not nearly as many of them in the wild as of yet. Definitely work with support on the issue. Even then they probably do not have a lot of data points on this specific issue if any right now.
Especially being intermittent it sounds like it could be a firmware thing and may not even be the fault of Framework but an issue with drivers or system calls triggering the panic in the kernel instead of a fault state.
Any AI answers right now are probably going to be grasping at straws again as there are not a lot of widespread Core 3 series boards on the market. So take them with a grain of salt.
If it is bothersome enough a clean install of Windows is another “this might help” solution. Turning off the core isolation and memory integrity is not a good choice long term, those protections are there for a reason. Understandably, they can be turned off in test cases to isolate issues but it is safer to have them on than disabled long term in this instance. Again these are just some of my thoughts on this topic.
Congrats on the new system. Others have reported the speed and performance of the new pro boards are remarkable from the Intel side of things. Nice to see Intel putting out some new technology to compete with AMD on the portable front again.
