If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
There is a beta bios for the GA-Z97X-UD5H-BK which provides TPM2 module support. It is version F9D. I received it from Gigabyte support.
I have a GA-Z97X-UD5H and the latest bios on Tweaktown is F11D and does not support TPM2. I was able to get the BK firmware working on my non-BK hardware (via efiflash) by modifying the BIOS model string in the BK bios. Only issue is that I cant use the XMP profile for my memory.
The BIOS update is possibly more for the firmware solution supplied by the Intel ME rather than a plug-in module but it wont help with W11 as you also need a 8th gen or newer CPU. I was able to enable TPM with a Z170 but my 6700K is ruled out anyway.
Thanks jwsg. Fyi the F9B linked on page 1 did not support TPM2, so F9D upgrade is in fact more than just for an intel ME upgrade. I agree win11 doesn't support my 4th gen Intel CPU, but I took it as a challenge to find a way to get TPM2 support on my Mobo.
I've a B550i AX PRO + 5600x +DDR4 3200, and after updating from F13g to F13, I've been plagued with random reboots (mainly when playing noita). The windows log only shows a 'system shutdown was not clean'
At first I thought it to be related to PBO, but it happens even with it disabled. Both cinebench and prime95 don't give any error/windows error log/issue/beep.
Has anyone experienced the same? I might revert back to F13g, hoping even if the BT was lost now and then
To be honest you will always find people with problems after a BIOS update - just the process of updating BIOS resets everything plus the fact youre getting a new AGESA. I went from F12 to F13 and noticed various internal things have changed but luckily nothing that cause instability. My advice would be to investigate the reboots - is it the PSU for example - and try to move forward with F13 rather than assuming there's some problem with it and going backwards.
Has anyone been able to flash TRX40AORUSMASTER11.FBj to the TRX40 Aorus Master Rev 1.1 successfully I continue to get failed BIOS update error when attempting to flash
Event 41 isnt really the actual error as such - its more an event logged on startup recording that some problem caused the PC to shutdown/restart unexpectedly - like a BSOD (some info should be logged) or a h/w prob like the PSU.. Happening once in weeks would worry me - but 10 times a day I would be thinking of rebuilding the PC as just changing BIOS isnt going to help unless it was an early one lacking matured DRAM timings etc.
Im currently doing testing, i have 2 issues, one being hyperX cloud 2 headset causing the pc to crash that has been resolved, other one being whea error/kernal 41
To be honest you will always find people with problems after a BIOS update - just the process of updating BIOS resets everything plus the fact youre getting a new AGESA. I went from F12 to F13 and noticed various internal things have changed but luckily nothing that cause instability. My advice would be to investigate the reboots - is it the PSU for example - and try to move forward with F13 rather than assuming there's some problem with it and going backwards.
I realize that it's unlikely to have these kind of issues with a stable BIOS version, but the PSU is less than 6mo old and the issue only appeared when I upgraded from F13g to F13, until then it's been running flawless (aside from known issues like BT). I'll try to triage it further to see if I can pinpoint it.
F13 flashed still experiencing kernal error ID 41,10 times a day
Same motherboard, same CPU, no overclocking. Absolutely solid on F13 for 10 days so far, including BT. No real difference from F13l (which lost BT once in three weeks) except I'm hoping BT is even more stable.
As jwsg said, that kind of error rate suggests something pretty fundamental is not right. I'd reset the BIOS to optimised defaults, see if the system is stable and then start adjusting things, one at a time, if you need to make changes.
My PC started to BSOD when applying a Windows Update a year or so back. The actual problem was a misbehaving driver that was no longer tolerated by something in the update and only by tracking down and removing the driver solved things - in other words the issue was highlighted by the update but not really caused by it.
stasio I’m curious if there has been any beta bios update for the z590 vision d? F5 has some serious problems in s3 sleep with non-windows OSes. I had to go back to an earlier T bios.
Comment