Dolphin, the GameCube and Wii emulator - Forums

Hrmm...it seems to be mostly g3258 users that are experiencing a SAFE_OS error while trying to upgrade to windows 10. So here's the gist of what I read so far:

- g3258 processors are receiving "SAFE_OS" error while attempting to upgrade or fresh install of windows 10 if overclocked and using an H, B, or Q series board. Z board users do not appear to be affected by this.
- To fresh install or upgrade to windows 10, users must set to stock speed and, in some situations, use only single core.
- Users who have installed windows 10 on an H, B, or Q series board will experience the "Bootloop death" if they attempt an overclock afterwards.
- This problem seems to be associated with update "KB3064209" after build 10130.
- Build 10130 introduced an Intel microcode "mcupdate_GenuineIntel.dll" that appears to be interfering with overclocking
- Some windows 10 users are only able to overclock just 1 core after this build.
- Some windows 10 users have been able to restore full overclockability after deleting or renaming the Intel microcode.
- Some windows 7, 8, and 8.1 users have also had this same overclocking issue after the microcode was updated on their system.
- Microsoft claims it is not on their end but rather it's a problem with the aforementioned Intel Microcode.
- Intel claims to be working on correcting the faulty microcode.

So for anyone who is considering overclocking on a post 10130 windows 10 build...you may have issues if you're running a non-Z board. I will attempt the fix listed in the link below and update.

Here's a summary of this issue and possible solutions on the MS forums:
http://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/windows-10-upgrade-fails-with-0xc1900101-0x20017/db224756-027e-4a5c-83a8-0c8edd156e55

It worked! I'm able to reach 4.2MHz on 1.3 vcore. My vcore is a bit too high I think, so I'll tweak it lower. Did a 10x Intel Burn test on Very High stress and temps did not exceed 74 C.

The fix in the previous post did the trick. Renaming the "mcupdate_GenuineIntel.dll" seem to have prevented the microcode from borking with win10 bootup.

About Win10 issues with OC, I still believe it have no relation with the board or the CPU, I have an HTPC-ish build with a Z97 board and an overclocked G3258 with it, if I use a Technical Preview or Insider Preview build of Windows 10 it won't boot into windows, no matter what, but using RTM build works perfectly fine (even after installing all updates available)...

Well, I guess it's hard to say what exactly is the issue is then. All I can say is what I've done to fix it and what I've read seems to suggest it's an issue with certain board series and a faulty microcode from Intel (although I did read that some Z boards users, especially from ASRock, are experiencing this issue as well). In any case, it's good news for me...just a few more bucks I don't have to spend for a Z board.

So I finally got the G3258 at a stable 4.0 GHz...wow, I'm impressed at its performance in Dolphin. I haven't ran any Dolphin-related benches, but right away I can tell it's performing better than the FX8530 for Skyward Sword. It's dead solid smooth at 2x native (720p) openGL. The FX is not bad either, but I immediately notice less stuttering and a consistent 30fps with the g3258. I'm definitely recommending this chip to anyone looking for an inexpensive Dolphin build.

That's expected. Most (if not all) AMD CPUs are garbage for Dolphin...