Several concerns have emerged following the Intel 13th generation upgrade.
Several concerns have emerged following the Intel 13th generation upgrade.
I recently moved to an Intel 13th generation processor and encountered some issues. Upgrades include an i7-13700K with 32GB RAM. Previous specs were AMD Ryzen 5 5600X. Problems: CPU runs at base speed (3.4GHz) and takes time to respond sometimes. Difficulty reading the new BIOS file; it worked once before. I attempted to update the BIOS to version F4C and manually set static core speeds and voltages, disabling E cores and hyperthreading. Other settings were adjusted. PSU is an EVGA 1000 T2 with both 8-pin CPU power connectors in. GPU is an MSI RX 4090 Gaming with a trio cooler from Noctua NH-D15S. OS is Windows 10 Home (I don’t plan to upgrade to 11). I couldn’t locate any drivers online for my chipset, possibly the cause. The BIOS reports correct frequencies, but Windows (via hwinfo) shows 3400MHz even during stress tests.
The extended article is based on DDR5 technology, that’s the current setup. It’s tough to explain, but 13th generation Intel needs Windows 11 to function correctly. That’s why I switched to AM5 since I prefer Windows 10.
Usually chipset drivers aren't crucial; focus on the Intel Management Engine. Windows updates should handle it automatically, though sometimes you'll need a manual install. If you're migrating from an AMD system, verify the first step. Memory training can be tricky—DDR5 takes a long time to boot. It seems like Gigabyte might be having issues with flash drives or similar devices, possibly causing occasional problems. The 13th generation runs smoothly in Windows 10 when E Cores are disabled; leaving them on still works but may lead to odd performance behavior during certain tasks.
The Windows driver search feature is currently turned off. I’m considering re-enabling it and will update this post if it helps. I’ve used two old 16GB flash drives, but they’re slow and not very reliable. They still function, though. The only solution that worked was saving the file to a SATA SSD, which allowed it to read the data, even after several attempts. Edit: It didn’t work—should I just reinstall Windows? It’s really frustrating, but I think that’s my only option. According to the latest updates, Intel drivers were already installed, so I’m unsure what’s causing this issue.
Consider a fresh installation, but it might be better to apply an Intel ME update first. The most convenient source is Gigabyte's site, though you should also check Intel's offerings. https://download.gigabyte.com/FileList/D...fa30b4a1b8