Fairly Sudden Onset of extreme instability.

Fantastic new status update!

I initially turned off turbo boost, and found some stability. After doing some more research I actually turned it back on and just set all my Performance Cores to a ratio of 55 down from the default of 57 and 60. I also set all the E-Cores to 44. I made these changes in the BIOS, and I have not a had a crash since. and today, Windows Update actually pulled down the latest windows patch.

So I ran: "sfc /scannow" and it was still corrupt and failed to fix itself.

So I ran: "dism /online /cleanup-image /restorehealth /source:f:\windows /limitaccess"
where F:\ is the SSD that had working install of windows 11 pro.

and SUCCESS! No more corrupt system files. Now, I just have to finish my Masters (Capstone Presentation and Final day is April 22nd), then I will start the RMA process to get my 14900K replaced with one that can run at full speed.

1712771508411.png

I feel it is important to note: the regular command "dism /online /cleanup-image /restorehealth" failed twice this time before I pointed it to the other install and used the "/LimitAccess" flag. I had tried all of this before and it did not work.
 
Thanks for the update. I'm not entirely convinced that the CPU issue and the SFC issue were related however, but I'm happy the later is sorted and the former has a decent workaround.
 
ubuysa said:
Thanks for the update. I'm not entirely convinced that the CPU issue and the SFC issue were related however, but I'm happy the later is sorted and the former has a decent workaround.
Click to expand...
I tend to agree with you. I do believe the system files could have become corrupt from a BSOD during an update. But the whole refusal to fix itself, I blame on Windows.

@Maxstar ,@ubuysa ,@axe0 , and anyone that helped that I may have missed...
I really want to thank all of you for the help and support. The time and energy y'all put into this community is evident throughout this website, and it is appreciated. You are wonderful humans.

I'm still fine with leaving this open, can we pin post 41 for anyone looking for the workaround?
 
fedup-fromAZ said:
I do believe the system files could have become corrupt from a BSOD during an update. But the whole refusal to fix itself, I blame on Windows.
Click to expand...
BSOD's and/or unexpected system shutdowns are definitely a cause of file corruptions. Please note that Windows uses multiple compression levels for system files, and decompress them when needed to apply newer updates. If a system crashed some system files may have been updated / modified, but not the associated registry keys which will ending in trouble with DISM / SFC.
 
Today I updated to the latest BIOS version thinking it would have updates that fix the issue. Unfortunately it did not. I submitted a support ticket for RMA with Intel. We'll see what they say.
 
The mitigation BIOS updtaes will prevent a 13th/14th gen CPU becing damaged, but they will NOT fix a CPU that is already damaged. If you think yours is damaged then you need to RMA it - but be sure you have the very latest BIOS update installed before installing the new CPU, that's the one containming the 0x12B microcode update. That BIOS should also contain the earlier 0x125 and 0x129 microcode updates, all of which are required to mitigate against the flaw in these CPUs.
 
fedup-fromAZ said:
Today I updated to the latest BIOS version thinking it would have updates that fix the issue. Unfortunately it did not. I submitted a support ticket for RMA with Intel. We'll see what they say.
Click to expand...

Did you install also Intel Dynamic Tuning Technology (2024/09/24) and chipset drivers (2024/08/7) from asus?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top