- Joined
- May 22, 2015
- Messages
- 14,421 (3.88/day)
Processor | Intel i5-12600k |
---|---|
Motherboard | Asus H670 TUF |
Cooling | Arctic Freezer 34 |
Memory | 2x16GB DDR4 3600 G.Skill Ripjaws V |
Video Card(s) | EVGA GTX 1060 SC |
Storage | 500GB Samsung 970 EVO, 500GB Samsung 850 EVO, 1TB Crucial MX300 and 2TB Crucial MX500 |
Display(s) | Dell U3219Q + HP ZR24w |
Case | Raijintek Thetis |
Audio Device(s) | Audioquest Dragonfly Red :D |
Power Supply | Seasonic 620W M12 |
Mouse | Logitech G502 Proteus Core |
Keyboard | G.Skill KM780R |
Software | Arch Linux + Win10 |
That would make more sense than the driver alone screwing things up like that.Regarding the core parking Bug you can use CPMinCores from Microsoft to prevent that problem until there is an official fix.
![]()
CPMinCores
CPMinCores specifies the minimum percentage of logical processors (in terms of all logical processors that are enabled on the system within each NUMA node) that can be placed in the un-parked state at any given time.learn.microsoft.com
Toms Hardware used that Tool as well because they had trouble even after a fresh install. My bet is a Board/agesa based bug in combination with the driver.