08-25-2024 03:12 AM - edited 08-25-2024 03:51 AM
Hi,
I've notice that my system (i7 14700kf + asus z790-h + kingston renegate 2x16gb 6000 cl32) is registering in system logs error that it is unable to start wirtualization - this was couse by disable wirtualization in bios and removed hyper-v function in windows 11. This error was connected with core izolation security option that was at the start a activated but later i've disable wirtualization rather turning off this feature first. So i wanna to fix it and after enabling wirtualization in bios (tehe lates one with microcode 0x129) system didnt even could pass initial post with orange led on dram (it was looping betwen passing cpu led and then proceed to dram and again). So i've disable wirtualization but that didnt help. Restoring bios to defoult let me boot to windows but after re-enablig all setting (mainly including my undervolting that was good and stable) it was still working but just when i enable xmp it started to crash again.
I'm not sure what happend but currently i'm able to use system only without xmp. Turning on wirtualization couse somphing that crash xmp. I was using xmp profile 1 but testong it with 2 or auto didnt change anything. Ram is located in A2 and B2. I could test if its gonna post with one of them or in slots A1 B1.
I'm aware of intel 14 gen problems but on my undervolt settings i've got stable and not overheating system when checking in C24.
Is my RAM broken or even worst motherboard or cpu (i've got psu 1000W be quiet platinium so it dont think that is the problem).
08-25-2024 04:49 AM
I've got update on this problem:
- when i remove all ram from the slots system act the same as with the xmp turn on (stuck on dram led) but when rams are in slots system try to re-enable post and starting few time to post
- when only 1 ram is in oryginal slot A2 it act the same and loop post (second ram is out)
- when only 1 ram is in slot A2 but i will use the second one it post without any problems
- when that working ram is in A2 slot and will add second ram to B2 it loop again
For me it looks like that one ram is cousing problem - i will do memtest and add results here