most of the debugging would just show what the problem is not caused by.īoth systems were running games, one with a nvidia gpu and the other with an AMD GPU.Īnother reason I suspected the CPU was both system were running the cpu at the same odd clock rate. Really not sure how to debug this issue so I am making a best guess. It could also be that microsoft pushed out a microcode patch to mcupdate_AuthenticAMD.dll but it also requires a BIOS update that microsoft can not apply and you would have to install. (i could not tell if the microsoft patch was applied since the debugger returned a error when I went to check the cpu microcode patch level)īoth systems looked like they were one bios patch behind.Īnyway, go to your motherboard vendors website and load the most current bios and download the chipset drivers from the motherboard vendors website reboot and see if you still get the same bugcheck. This the microsoft file:\SystemRoot\system32\mcupdate_AuthenticAMD.dll * Invalid bugs in the CPU are worked around by machine a patch that is put into the BIOS and microsoft will also put a patch into a cpu specfic file they load when the system boots. You could both be hitting a bug in the cpu. The key difference is that the payload of the hotfix is primarily one of two files: mcupdateGenuineIntel.dll Intel. both dumps show AMD CPUs with the same stepping (version of the cpu) I am going to see if I can find the other memory dumpĬlick to expand.i found the other memory dump. At the same time, none of my undervolt settings carry through to the window on the right in FIVR Control, which displays all 0s. 8.74, it keeps saying 'FIVR Control - Locked'. ProcessorNameString = REG_SZ AMD Ryzen 5 3500X 6-Core Processor Im trying to undervolt my Surface Laptop 3 (Released Oct 2019, which was before the Plundervolt patch announcement in Dec 2019) with a 10th-gen i5. Identifier = REG_SZ AMD64 Family 23 Model 113 Stepping 0 ![]() SystemManufacturer = Gigabyte Technology Co., Ltd.īaseBoardManufacturer = Gigabyte Technology Co., Ltd.Ĭomponent Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0Ĭonfiguration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0 I think you had a different motherboard running a different game and a different set of suspect drivers. Right click - services - make symbolic link. ![]() On your external hard drive, create a folder called backup. Read the read me and youll see that it needs to live in the services folder. It is interesting since I looked at another dump today that looked like the same problem. Download SymbolicLinker and dont be like me and willy-nilly open the. And used that copy to replace the updated version. Then booted WinPE with Active Boot Disk from a USB drive with a copy of the older version of mcupdateGenuineIntel.dll. Then copied mcupdateGenuineIntel.dll from an earlier backup/clone of Windows 10 version 1803. System bugchecked trying to do a Direct Memory Access request. First I made sure Spectre protection was disabled.
0 Comments
Leave a Reply. |