13900HX BSOD with 24H2

[Intrepidity]

I experience BSOD issues with TS running regardless of UV applied after updating to 24H2. Ideas appreciated.

(Guessing it might be a system setting, incompatible driver or something else related to my system that doesn't play well with TS after the 24H2 update. If so it might be solved be a reinstall, but I hope to avoid that.)

 

[AleXXX666]

I experience BSOD issues with TS running regardless of UV applied after updating to 24H2. Ideas appreciated.

(Guessing it might be a system setting, incompatible driver or something else related to my system that doesn't play well with TS after the 24H2 update. If so it might be solved be a reinstall, but I hope to avoid that.)

if it ain't 24H2 LTSC if I were you i'd reinstall to 23h2 or even 22h2 if hw compatible. had to agree 24h2 is still buggy and has some sw issues which really annoy. also f...ed up "updates" which install with error is a nonsense. and i've read some info that 23h2 has same "buggy" updates as 24h2, so if i were specifically installing win11 knowing that i'd choose 22h2 and blocking feature updates with GP until good.

 

[Valour549]

I experience BSOD issues with TS running regardless of UV applied after updating to 24H2. Ideas appreciated.

(Guessing it might be a system setting, incompatible driver or something else related to my system that doesn't play well with TS after the 24H2 update. If so it might be solved be a reinstall, but I hope to avoid that.)

Try disable "Virtualization Technology" in the BIOS, if you have updated to 24H2. See if it fixes the BSOD.

 

[iameatingjam]

Yeah... not the first time I've heard something like this which is why I am hesitant to do the update yet.

As for you though, are you able to get back how you were before through a restore point? I think it deletes itself after a period of time so if you are going to do this, I would do it as soon as possible.

 

[Intrepidity]

Try disable "Virtualization Technology" in the BIOS, if you have updated to 24H2. See if it fixes the BSOD.

Virtualization has been disabled through the BIOS all along. Sounds very plausible due to core isolation changes in 24H2, just unfortunately not the solution.



Anyone have ideas in regards to settings I could attempt in TS? Perhaps settings that need changing in relation to some OS default parameters changing in 24H2..?

 

[iameatingjam]

Virtualization has been disabled through the BIOS all along. Sounds very plausible due to core isolation changes in 24H2, just unfortunately not the solution.



Anyone have ideas in regards to settings I could attempt in TS? Perhaps settings that need changing in relation to some OS default parameters changing in 24H2..?

Does it work with throttlestop closed? I mean just for diagnostic purposes.

 

[Intrepidity]

Does it work with throttlestop closed? I mean just for diagnostic purposes.

Not quite sure what you are asking. As some settings might persist after TS is closed I tested with TS running vs TS not started at all (removed from startup). No issues if TS isn't started at all. I didn't test starting TS, then closing it. I suppose I could attempt that if relevant to perhaps figure out if the parameter that cause issues is persistant after TS close or not..? Doesn't help me a lot though as I don't know what parameters persist when closed and which do not.

 

[iameatingjam]

Not quite sure what you are asking. As some settings might persist after TS is closed I tested with TS running vs TS not started at all (removed from startup). No issues if TS isn't started at all. I didn't test starting TS, then closing it. I suppose I could attempt that if relevant to perhaps figure out if the parameter that cause issues is persistant after TS close or not..? Doesn't help me a lot though as I don't know what parameters persist when closed and which do not.

Oh no if already tested with it not even started then thats fine, and I don't think its persistent, at least the undervolts, unless something has changed since last time I used it.

Don't forget the clock is ticking on that restore point. It might already be too late.... I mean you can always upgrade again but that downgrade image will disappear after 10 days or something. Since you're RL its not like you have that much to gain from the upgrade anyway.... unless there was some feature you wanted.

 

[Valour549]

Virtualization has been disabled through the BIOS all along. Sounds very plausible due to core isolation changes in 24H2, just unfortunately not the solution.

When you open msinfo32 , does it show Virtualization-based Security as off? If not then:

• Double check "Virtual Machine Platform", "Hyper-V", "Windows Sandbox" and other Virtual Machine-related settings in Windows features are off.

• If somehow doing that still doesn't work. Then turn off Tamper Protection. Then open regedit and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard . Find or add EnableVirtualizationBasedSecurity and set the value to 0.

Let me know what changes worked, if any.

 

[Intrepidity]

When you open msinfo32 , does it show Virtualization-based Security as off? If not then:

• Double check "Virtual Machine Platform", "Hyper-V", "Windows Sandbox" and other Virtual Machine-related settings in Windows features are off.

• If somehow doing that still doesn't work. Then turn off Tamper Protection. Then open regedit and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard . Find or add EnableVirtualizationBasedSecurity and set the value to 0.

Let me know what changes worked, if any.

Appreciate the info, but virtualization based security, hyper-v, virtual machine platform and windows sandbox were all disabled already. Had my hopes up the components related to virtualization were still enabled for a moment.

(Seems to be identical to 23H2 if UV isn't enabled. I won't roll back as that will just be a temporary workaround.)

 

[Valour549]

What laptop model do you have? Disabling "Virtualization Technology" in the BIOS has worked for most people who've updated to 24H2, so this is indeed strange.