Latest C7H BIOS

[xeizo]

I don't understand how you do to get BSODs, I have never had a BSOD with Crosshair VII regardless of settings, running 2700X, 3700X and now 3900X. It must be some setting you have set very wrong.

I'm running the gupsterg with SMU 46.49 at the moment, 0002M-FIE, while it boosts like 50MHz less all over than 0002+ it is stable for me.

[igralec84]

I don't understand how you do to get BSODs, I have never had a BSOD with Crosshair VII regardless of settings, running 2700X, 3700X and now 3900X. It must be some setting you have set very wrong.

I'm running the gupsterg with SMU 46.49 at the moment, 0002M-FIE, while it boosts like 50MHz less all over than 0002+ it is stable for me.

I don't know, had no problems on 2700X, but since switching to 3600 and 3600X, i get BSODs every day. Had a 5 day period without them, but when i started experimenting with RAM profiles, i kept getting them again.

I only set the timings according to the calculator, DRAM and Vboot voltage, VDDP, VDDG, SOC voltage, FCLK and memory clock and custom fan curves. No fancy stuff.

After the next BSOD, i'll just run optimized defaults + custom fan curves and see once and for all if it's the RAM or something else, maybe WIn 10 corrupt from all these crashes (although DISM + sfc don't find anything, but i always have some drivers not compatible in driver verifier) or some strange drivers conflicts that weren't there with the previous X470 board + 2700X or this one + 2700X.

[Max1mus91]

People who have the new SMU user beta bios with 3900x. Do you still get lower clock speeds when ram is over 3400?

[xeizo]

People who have the new SMU user beta bios with 3900x. Do you still get lower clock speeds when ram is over 3400?

Well, the new SMU 46.49 boosts worse than the old 46.34 everywhere(50MHz lower overall), but it doesn't seem to have anything to do with RAM-speed. I run 3800MHz RAM and have this boost in idle on 12 cores:

4550
4575
4575
4425
4425
4500
4325
4325
4300
4375
4300
4325

CB15 is 12x4100MHz
CB20 is 12x4075MHz

The hard limit for higher boosts in bench is power limit, as these newer bioses can't consume more than 145W or 98A no matter what settings in bios or Ryzen Master. Only way to improve slightly is to lower temps.

[sean.s.adkins]

I don't know, had no problems on 2700X, but since switching to 3600 and 3600X, i get BSODs every day. Had a 5 day period without them, but when i started experimenting with RAM profiles, i kept getting them again.

I only set the timings according to the calculator, DRAM and Vboot voltage, VDDP, VDDG, SOC voltage, FCLK and memory clock and custom fan curves. No fancy stuff.

After the next BSOD, i'll just run optimized defaults + custom fan curves and see once and for all if it's the RAM or something else, maybe WIn 10 corrupt from all these crashes (although DISM + sfc don't find anything, but i always have some drivers not compatible in driver verifier) or some strange drivers conflicts that weren't there with the previous X470 board + 2700X or this one + 2700X.

I have to manually up the timings on mine ever since a bios update several version ago..ya think it would run docp timings no problem if your getting crashes then raise them up a tad. (or let it keep crashing lol)

[igralec84]

I have to manually up the timings on mine ever since a bios update several version ago..ya think it would run docp timings no problem if your getting crashes then raise them up a tad. (or let it keep crashing lol)

I also get crashing running 2133, so it's not all memory it seems. I have 3200 CL14 running at 3600 CL16 1.35v and it's fine according to memtests, for benchmarks i have 3600 CL14 that gets errors immediately but gives a little points boost in 3Dmark haha. I noticed i needed to update the DRAM calculator to the latest version, as there were some differences and i couldn't get 3600 CL16 safe setting to run, not on V1, V2 or even manual after 2703 BIOS.

Maybe i had driver verifier running every time i started windows as i think the 5 day crash free period was when i deleted the verifier settings that stops stress testing them or the ones that are not verified (some bizzare ones keep popping up, beep.sys, cdrom.sys, etc). Will see if i'll now stop getting BSODs, although if stress testing drivers made some of them crash eventually, there's still something not right. But bad or unstable memory overclocks (starting with DOCP 3200 CL14) probably have a lot to do with it.

[Max1mus91]

Well, the new SMU 46.49 boosts worse than the old 46.34 everywhere(50MHz lower overall), but it doesn't seem to have anything to do with RAM-speed. I run 3800MHz RAM and have this boost in idle on 12 cores:

4550
4575
4575
4425
4425
4500
4325
4325
4300
4375
4300
4325

CB15 is 12x4100MHz
CB20 is 12x4075MHz

The hard limit for higher boosts in bench is power limit, as these newer bioses can't consume more than 145W or 98A no matter what settings in bios or Ryzen Master. Only way to improve slightly is to lower temps.

When I go above 3400 ram speed, xmp is 3600, 3900x doesn't boost above 4250.

If I go to 3400 boost is at 4525\4400 depending on the core.

This idle and gaming.

[sean.s.adkins]

I also get crashing running 2133, so it's not all memory it seems. I have 3200 CL14 running at 3600 CL16 1.35v and it's fine according to memtests, for benchmarks i have 3600 CL14 that gets errors immediately but gives a little points boost in 3Dmark haha. I noticed i needed to update the DRAM calculator to the latest version, as there were some differences and i couldn't get 3600 CL16 safe setting to run, not on V1, V2 or even manual after 2703 BIOS.

Maybe i had driver verifier running every time i started windows as i think the 5 day crash free period was when i deleted the verifier settings that stops stress testing them or the ones that are not verified (some bizzare ones keep popping up, beep.sys, cdrom.sys, etc). Will see if i'll now stop getting BSODs, although if stress testing drivers made some of them crash eventually, there's still something not right. But bad or unstable memory overclocks (starting with DOCP 3200 CL14) probably have a lot to do with it.

Gods honest truth.....every bsod i have ever had was memory related. I get zero crashes for months on end so i use what works for me. Memory test doesnt tell you if the memory is stable in my experience. Im positive i can fire up mine with 3500 memory speed and pass any memory tests but it would still give bsod crashes when i least expect it lol

[andyliu]

well, BSOD can happen with the windows update easily lately.
for one, this is what I am currently experiencing, some get reboot without warning, some get bsod
https://www.reddit.com/r/HyperX/comm...thout_warning/

one thing you can check is to go thru event viewer and see what kinda critical message it gives under the windows log/system
that's how i figure out the issue has to do with the usb dongle of my headset

[igralec84]

well, BSOD can happen with the windows update easily lately.
for one, this is what I am currently experiencing, some get reboot without warning, some get bsod
https://www.reddit.com/r/HyperX/comm...thout_warning/

one thing you can check is to go thru event viewer and see what kinda critical message it gives under the windows log/system
that's how i figure out the issue has to do with the usb dongle of my headset

Some of my BSODs were usb related, so i suspect there's either something wrong with the boards USB hub, or the ports on the case, or for some reason with the Razer keyboard or the Asus ROG mouse, which would be a shame tbh.
Not sure why a cdrom driver can cause a crash, i haven't had a CD/DVD drive in 3 years lol.
But yeah, if i get another BSOD i'll check event viewer if there's more info there, the mini dump viewer doesn't give away much, but there are aroud 5 bug codes that are repeated, the drivers causing it are always ntoskrnl.exe and hal.dll. It's interesting that the 2700X worked fine on this board, but the 3000 series doesn't. But i did also change from 3200 CL16 Trident Z RGB to 3200 CL14 Ripjaws V in the same time.
What's also funny is i can play games for hours, never had a BSOD there, but it 90% of the time crashes while idle, if i take a shower or have lunch, come back and it's at login screen.