- last edited on by
ROGBot
HI,
Yesterday I updated the UEFI from 802 to 2103 and the PC booted into Windows but problems started when I tried to reload previous OC profile and things went South:
- UEFI uploaded my Mem OC profile (3200 cl14) used with 802 for the last year
- PC froze with Q-Code 50 (Memory Initialization Error)
- UEFI reset
This is my OC Profile, it has been working for the last year without a problem
- Second time, uploaded OC Profile (3200 cl14)
- increased dram the voltage from 1.35 to 1.36
- Q-Code 50
- UEFI reset
- Boot UEFI
- upload clean 2103 from USB
- Manually punched the timings
- dram voltage Auto
- Q-code 50
- UEFI reset
- Start Windows 10 Pro (1809)
- Thaiphoon (reads mem for about 5min)
- Thaiphoon result (WTF)
That was very strange!
- Boot UEFI
- Intended to downgrade UEFI to previous versions. I keep all prior versions, with original names and C7HWIFI.CAP variant.
- No valid file selected?
- Boot UEFI
- Upload again clean 2103
- touch nothing go strait into Windows 10
- Thaiphoon readings normal with properly recognized dram sticks.
- Boot UEFI
- punch new cl16 timings for 3200 speed (using DRAM calculator 1.4.1)
- Q Code 50
-UEFI reset
- load Windows
- Thaiphoon (5 min. reading wrong as hell)
Didn't have much time to play , plus since CH7 does not have Dual BIOS chip and I have a lot of work next day I decide to quit
- UEFI Flashback to 802
- loaded OC mem profile
- works as intended
J just wanted to see if somebody else has encountered similar behavior from 2103 and can share if he/she managed to resolve or find what's causing the issue
Ryzen 2700x
Crosshair Hero VII (WiFi)
G.Skill F4-3600C17-16GTZ (2x16GB)
Radeon RX 560
Mellanox ConnectX2
EVGA G2 850W
Yesterday I updated the UEFI from 802 to 2103 and the PC booted into Windows but problems started when I tried to reload previous OC profile and things went South:
- UEFI uploaded my Mem OC profile (3200 cl14) used with 802 for the last year
- PC froze with Q-Code 50 (Memory Initialization Error)
- UEFI reset
This is my OC Profile, it has been working for the last year without a problem
- Second time, uploaded OC Profile (3200 cl14)
- increased dram the voltage from 1.35 to 1.36
- Q-Code 50
- UEFI reset
- Boot UEFI
- upload clean 2103 from USB
- Manually punched the timings
- dram voltage Auto
- Q-code 50
- UEFI reset
- Start Windows 10 Pro (1809)
- Thaiphoon (reads mem for about 5min)
- Thaiphoon result (WTF)
That was very strange!
- Boot UEFI
- Intended to downgrade UEFI to previous versions. I keep all prior versions, with original names and C7HWIFI.CAP variant.
- No valid file selected?
- Boot UEFI
- Upload again clean 2103
- touch nothing go strait into Windows 10
- Thaiphoon readings normal with properly recognized dram sticks.
- Boot UEFI
- punch new cl16 timings for 3200 speed (using DRAM calculator 1.4.1)
- Q Code 50
-UEFI reset
- load Windows
- Thaiphoon (5 min. reading wrong as hell)
Didn't have much time to play , plus since CH7 does not have Dual BIOS chip and I have a lot of work next day I decide to quit
- UEFI Flashback to 802
- loaded OC mem profile
- works as intended
J just wanted to see if somebody else has encountered similar behavior from 2103 and can share if he/she managed to resolve or find what's causing the issue
Ryzen 2700x
Crosshair Hero VII (WiFi)
G.Skill F4-3600C17-16GTZ (2x16GB)
Radeon RX 560
Mellanox ConnectX2
EVGA G2 850W
