TheColin21

Thanks a lot! It booted right away with 1.3V SOC. Stock was 1.265V. It also boots with 1.28V. I'll stress test it a bit to see how it impacts temps and performance. Now I just have to decide whether or not to update the BIOS nonetheless....

good idea, edited it in.

Update: just read the BIOS files with easy flash. Versions >=2414 give me an explicit "You won't be able to downgrade" warning, version 2413 does not. So I think I won't be able to downgrade back to 2214. I read conflicting reports online on whether BIOS flashback would still be able to downgrade.... The question ow is: could "Improve system stability" in Version 2414s changelog indicate that this version might again be able to correctly use EXPO on this RAM?

Hi, I recently built a new PC for a friend using the Ryzen 7800X3D, an ASUS B650E-E MB and 2x16GB Kingston FURY Beast DDR5-6000, CL36-38-38 RAM (which is listed on the boards QVL). When I first built the computer I upgraded the BIOS to the then latest version 2413. I could not reliably get the computer to boot with EXPO enabled. It would fall back to safe mode with the SPD frequency of 4800 MHz. I tried reseating the CPU and RAM which did not help After downgrading the BIOS to version 2214 I can at least run the system with EXPO enabled but I cannot set UCLK to 1:1. It won't boot in that configuration. Do you have any hints which settings I could tweak (slightly rise a voltage or something similar) to get the system to boot and run stable with UCLK 1:1? That shouldn't be a problem with 6000MHz RAM... or so I thought. Also there are now two new BIOS versions, 2414 and 2613. I am thinking about trying an update to one of those but I fear that I might not be able to downgrade to 2214 again if I do that. If anyone here has a reliable answer to whether I may be able to downgrade again I would much appreciate that too. Just FYI, the changelog of the latest BIOS versions: Version 2613 12.86 MB 2024/04/17 "Update AGESA version to Combo 1.1.7.0 patch A to support next generation AMD Ryzen™ processors Before running the USB BIOS Flashback tool, please rename the BIOS file (SB650EE.CAP) using BIOSRenamer." Version 2414 11.29 MB 2024/04/17 "1. Improve system stability Before running the USB BIOS Flashback tool, please rename the BIOS file (SB650EE.CAP) using BIOSRenamer." Version 2413 11.24 MB 2024/02/07 "Disable STAPM of AM5 Ryzen™ 8000 processors to improve system performance. Before running the USB BIOS Flashback tool, please rename the BIOS file (SB650EE.CAP) using BIOSRenamer" Version 2412 11.24 MB 2024/01/30 "Update AGESA version to Combo AM5 PI 1.1.0.2b Before running the USB BIOS Flashback tool, please rename the BIOS file (SB650EE.CAP) using BIOSRenamer" Version 2214 11.23 MB 2024/01/04 "1. Update AGESA version to Combo AM5 PI 1.1.0.1 2. Improve system stability 3. This update includes the patch for the LogoFAIL vulnerabilities 4. Support graphics card with M.2 storage Before running the USB BIOS Flashback tool, please rename the BIOS file (SB650EE.CAP) using BIOSRenamer."

You were totally right. I tried with an older version. Memtest86 V4. All sticks are without errors there. Probably really an incompatibility.

That's why I switched to another CPU... False errors are an interesting idea though. I'll test it with Windows' tools.

thanks for the idea but I tried the recommended configurations for three and four DIMMs as well as others... still the same result. I think I rules out bad traces because two sticks work in pretty much any combination of the six sockets.... I really just don't get it...

Hi, I have a pretty old system lying around here. It's an i7 920 on an ASUS Rampage II Extreme with (formerly) 6*2GB of DDR3-1066 non-ecc RAM (also an old SSD and a GTX 470). Pretty old system, used to work quite well nonetheless. I was experiencing weird errors in Windows and, just for fun, tried Lubuntu. Worked perfectly for the few hours I tried. Then, just for fun as well, I ran memtest86+. Loads of errors, instantly. I tried all the modules on their own. Four worked perfectly, with two of them the system wouldn't even boot. I tried all in the same known-good slot. Then I tried two. Worked perfectly. Three --> errors. Same with all four sticks which worked perfectly on their own. I tried different slots, nothing changed. I could put two of the four sticks in any slot I wanted and everything was fine. Just no more than two. I also tried running them at higher voltages or at DDR3-800. Same result. I thought the CPU might be the issue and ordered a cheap Xeon X5660 to replace the i7 920. Same erros. As far as I know the memory controller on this generation is built into the CPU so I don't know what else could be the error. TLDR: Asus Rampage II Extreme board with X58 chipset (LGA1366) 6*2GB of DDR3-1066 RAM i7 920 and Xeon X5660 --> same result Two sticks probably dead. The other four work perfectly well on their own, no matter which slot. Two sticks work perfectly well in any slots as well. More sticks fail instantly in memtest. I'd be thankful for any ideas...

I have no problem with chipset drivers though

This has the exact same result as installing any official AMD driver manually, the system hangs, has to be rebooted, driver not installed. But thanks still.

I'll try it... If it breaks the windows installation I'll try again...

there is actually an automatic driver installer that does not suck? thanks i'll try

Hi, I just got a used Dell Inspire 17R 5737 which comes with an AMD Radeon HD 8870/R9 M270X. I put an SSD in the system (although I also tried this on an HDD before) and did a fresh install of Windows 10 20H2. I installed all the drivers but failed when I tried to install any AMD driver version. I've already tried the following: - BIOSes A10, A11, A12 - Installing just the driver from Device Manager in normal and safe mode - complete uninstall of all AMD/Intel drivers with DDU and AMD Cleanup Utility - "Normal installation" via the Setup-File downloaded form AMD.com - Driver versions 20.11.2, 21.2.3, 17.12.2 (from Guru3D), original AMD driver from Dell Support which install an old CCC based version, latest Windows 8.1 driver for my Win 8 try - Windows Versions 20H2, current dev Build, Windows 10 RTM (1507), Windows 8.1 - UEFI and Legacy Boot Modes - Ubuntu, the GPU seems to work there so I think I can rule out a hardware error - disabling driver signature enforcement I tried pretty much everything described in these threads: Solved: Laptop freezes while installing AMD driver - Page 2 - AMD Community System freezes during installation of Radeon Softw... - Page 2 - AMD Community Solved: Laptop freezes while installing AMD driver - AMD Community Solved: Inspiron 17r 5737 Graphics Driver Issues - Dell Community Solved: Re: System freezes during installation of Radeon drivers - Dell Community The symptoms are allways as follows: - when trying to install the driver in normal mode the computer freezes in the exact moment when the driver would actually be updated and has to be restarted - driver is not installed - when trying to install the driver in safe mode the installation via device manager works, installation via the update package installs the device driver but software does not get installed, after rebooting, the DELL logo with the spinning points appears but before the login screen the display turns off and the notebook has to be restarted and the driver uninstalled in safe mode. I am studying computer science and would describe myself as pretty tech savvy but I have no idea how to solve this. There are loads of threads on the internet about such errors (like the ones above) but I did not find any working solution. If any one of you has any idea I would very much appreciate it. Best regards Colin

Hey guys, I've got an old Samsung Laptop here (np350v5c-s0ade). A few years ago, I was young and stupid, I tried copy a huge game to it. It took too long via WiFi so I took out the SSD, plugged it into my PC, copied the game on it and put it back in. The SSD still works, the never turned on since. Charging the battery seems to work and the power LED is on for about 3 seconds when I try powering it on but that's it... Any ideas?

correction: it worked after the first boot (after the upgrade). After the next reboot the problem was back. That's frustrating