I’ve been testing framework laptop with HT disabled. Reboot occurs every ~30mins of laptop at sleep/idle, charger connected. After I left the laptop alone it rebooted. Investigating Event Logs I’ve found this error:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000006, 0xffff8a0da184dab0, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP
the scheduler was re-written for Windows 11. I wonder if they have not conceived of an instances where the user would intentionally disable hyper threading. My guess is that it has something to do with that.
Interesting. Based on the bug report and the official notice (which I had missed before, and which incorrectly reports the wrong lower bound version number) it looks like this isn’t unique to the new KB.
I wonder what it was about this update that tickled the bug for me, and why it went away when I rolled back… and conversely, why that didn’t hold for you!
I might go so far as to think you’re hitting a different 0x9F bugcheck, but that seems so unlikely given the rest of the driver stack being pretty stable. Would you mind filing feedback in the Feedback Hub for correlation?
I don’t know, and I would certainly hope not.
I always run with HT disabled because it make no sense since very few task can actually benefit from more cores running at a slower speed, not even compilers and certainly not games.
I believe disabling HT will actually result in better performance as the scheduler is able to access the physical cores more directly.
It seems like the update is the cause especially since its a preview
Which also include some interesting changes (e.g., making the crach screen blue again instead of black)