cancel
Showing results for 
Search instead for 
Did you mean: 

True performance is back after few year vulnerables patched

restsugavan
Level 14
93375

Core i9 7980XE " SYNC ALL CORE OPTION " FROM MODDED 3601 BIOS
with Intel 02006D05 Microcode DATE 2021-11-13
Testing under W11 22H2 25131.1000

93376

It was 4 years taken since 2018 after Intel disclosed Skylake X CPU SKUs vulnerable in many parts of Its micro architect .
Intel engineers team up to fixing both X299 PCH and CPU itself. Tons of patch and ME Firmware updates released.

Finally I think It was back !!!

The KING of Core X i9 7900 Series Extreme Edition true performance level.
W11 C 24H2 26236.5000 Core i9 7980XE 02007108 MCE ME 11.12.95.2499 R6E Modified BIOS 3801 SAMSUNG OG9 FW 1019.0 SSD 970 EVO PLUS 1 TB x 3 NVIDIA RTX 4090 GAME READY 555.99 64GB GSKILL DDR4 3200MHz JBL 9.1 Sound Bar DTS-X
745 Views
7 REPLIES 7

echelon
Level 7
Glad to see that, and thanks for keep supporting 7980XE & R6E :-), does this link still containing your latest R6E mod?

restsugavan
Level 14
Yes mate @echelon . 😮
W11 C 24H2 26236.5000 Core i9 7980XE 02007108 MCE ME 11.12.95.2499 R6E Modified BIOS 3801 SAMSUNG OG9 FW 1019.0 SSD 970 EVO PLUS 1 TB x 3 NVIDIA RTX 4090 GAME READY 555.99 64GB GSKILL DDR4 3200MHz JBL 9.1 Sound Bar DTS-X

@restsugavan Hi would your bios work good with the 9940x cpu ?

Thanks

restsugavan
Level 14
Skylake X Refresh 9900-9980XE series were different CPU ID microcode revision. I'm afraid it may not working correctly.

If you want to trying please use Master tistou 77 modified bios on first page of the quote better. :cool:

https://rog.asus.com/forum/showthread.php?108495-Modded-bios-Rampage-VI
W11 C 24H2 26236.5000 Core i9 7980XE 02007108 MCE ME 11.12.95.2499 R6E Modified BIOS 3801 SAMSUNG OG9 FW 1019.0 SSD 970 EVO PLUS 1 TB x 3 NVIDIA RTX 4090 GAME READY 555.99 64GB GSKILL DDR4 3200MHz JBL 9.1 Sound Bar DTS-X

echelon
Level 7
"Sync All Core" makes me reaching 3.9 - 4.12 Ghz, seems nice but since I am on the equator country, it's requires me a massive cooling setup to run it properly without overheating, "Auto" have less clock speed (2.9 - 3.13 Ghz) but works wonder for me.

I am getting BSOD from overheating mostly with "Sync All Core", from HYPERVISOR_ERROR (yes I have enabled HYPER-V) into DPC_WATCHDOG_TIMEOUT (Windows 11 22H2).

restsugavan
Level 14
I am getting BSOD from overheating mostly with "Sync All Core", from HYPERVISOR_ERROR (yes I have enabled HYPER-V) into DPC_WATCHDOG_TIMEOUT (Windows 11 22H2).


Please share your information to Windows team via Feedback. Your help will bring Windows 22H2 Hyper V issue patch soon. 😮


93410

There are some Hyper V issues on several builds since 22581. But on 25131 build It was already fix for 2 weeks ago.
It may not cause by your hardware setup.
Windows itself now preparing to switch from Nickle aka Sun Valley 2 (22H2) to Copper aka Sun Valley 3 (23H2) for Dev Channel.

By the way. I recommend you to apply AIO Cooling such as Kraken NZXT for your rigs.
It was more comfortable for you to take on heat. Long life your lover CPU and other component.

W11 C 24H2 26236.5000 Core i9 7980XE 02007108 MCE ME 11.12.95.2499 R6E Modified BIOS 3801 SAMSUNG OG9 FW 1019.0 SSD 970 EVO PLUS 1 TB x 3 NVIDIA RTX 4090 GAME READY 555.99 64GB GSKILL DDR4 3200MHz JBL 9.1 Sound Bar DTS-X

echelon
Level 7
I need stability for my works, so I only use RTM in my setup, currently using 22H2 22621.1, I know that mostly IP builds are stable enough but I don't want the chance for random instabilities.

Already using Custom water cooling loop in my system but perhaps it's not enough for my country 's base temperatures.

Will try IP/Insider Preview and reporting my issues when I have got the chances, btw did you run benchmark on Windows 11 22H2 Build 25136.1000, curious about what was your peak CPU's temperature when running it with "Sync All Core"?.

About HYPERVISOR_ERROR BSOD error, it happened at my peak performance (sync all core) after several minutes benchmarking using HANDBRAKE to convert a movie, if I was uninstalled HYPER-V then DPC_WATCHDOG_TIMEOUT happened, so that why I am really sure it's about my CPU/Memories temperatures.