• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

AMD-V not recognized on B550 Phantom Gaming-ITX/ax with R7-3800x

Joined
Jul 30, 2019
Messages
3,741 (1.77/day)
System Name Still not a thread ripper but pretty good.
Processor Ryzen 9 7950x, Thermal Grizzly AM5 Offset Mounting Kit, Thermal Grizzly Extreme Paste
Motherboard ASRock B650 LiveMixer (BIOS/UEFI version P3.08, AGESA 1.2.0.2)
Cooling EK-Quantum Velocity, EK-Quantum Reflection PC-O11, D5 PWM, EK-CoolStream PE 360, XSPC TX360
Memory Micron DDR5-5600 ECC Unbuffered Memory (2 sticks, 64GB, MTC20C2085S1EC56BD1) + JONSBO NF-1
Video Card(s) XFX Radeon RX 5700 & EK-Quantum Vector Radeon RX 5700 +XT & Backplate
Storage Samsung 4TB 980 PRO, 2 x Optane 905p 1.5TB (striped), AMD Radeon RAMDisk
Display(s) 2 x 4K LG 27UL600-W (and HUANUO Dual Monitor Mount)
Case Lian Li PC-O11 Dynamic Black (original model)
Audio Device(s) Corsair Commander Pro for Fans, RGB, & Temp Sensors (x4)
Power Supply Corsair RM750x
Mouse Logitech M575
Keyboard Corsair Strafe RGB MK.2
Software Windows 10 Professional (64bit)
Benchmark Scores RIP Ryzen 9 5950x, ASRock X570 Taichi (v1.06), 128GB Micron DDR4-3200 ECC UDIMM (18ASF4G72AZ-3G2F1)
According to https://www.techpowerup.com/cpu-specs/ryzen-7-3800x.c2129 and https://en.wikichip.org/wiki/amd/ryzen_7/3800x AMD-V should be supported by this CPU but on my B550 Phantom Gaming-ITX/ax I can't get HWiNFO64 or VMWare Workstation to recognize it even though I have it enabled in UEFI/BIOS. Oddly enough Task Manager indicates virtualization is enabled but these two software can't recognize it.

1659412706415.png


1659413896126.png



1659412467991.png


I need AMD-V in order to enable and use a VMWare Workstation Virtual Machine that requires virtualization to be enabled for certain software.

1659411972099.png


I was hoping someone familiar with AMD-V support and VMWare workstation might have a solution.

Previously this worked with Windows 10 and VMWare on my Master SLI/ac with 3950x and 5950x before it exploded in a puff of smoke. My original setup came up from upgrades to Windows 10 v1903, while my ITX was a fresh install of a much more recent version (maybe v2004 or v21H2).
 
Maybe the relative setting to that feature in the UEFI needs to be enabled?
 
Maybe the relative setting to that feature in the UEFI needs to be enabled?
It's called SVM and it's enabled in UEFI.

After searching the better part of the day I finally found the solution. https://www.hwinfo.com/forum/thread...d-in-bios-yet-amd-v-disabled.8201/#post-35995
bcdedit /set hypervisorlaunchtype off
There must have been some kind of change to how Windows handles hypervisors between older and newer versions of Windows 10 installations.

1659415787227.png
 
Back
Top