[SOLVED] Need help proving my CPU is causing BSOD

[effektz]

Hi everyone,

I am continuing my long journey to solve my BSOD problems when playing Unity Games (Link to previous post)

Here is my machine info:
---------------------------------------------------------------------------------------------------
CPU: AMD Ryzen 7 3700X
Motherboard: GIGABYTE X570 AORUS ELITE ATX
RAM: Crucial Ballistix Sport LT 32GB (2 x 16GB) DDR4-3200 PC4-25600 CL16
SSD: SAMSUNG 1TB 980PRO NVME M.2 SSD
GPU: ASUS AMD RADEON RX5700 8G
PSU: CORSAIR RMX750X FM 80+G ATX PSU
Chassis: Fractal Meshify Mid-Tower
OS: Windows 10, 10.0, version 2009, build: 19044 (x64)
---------------------------------------------------------------------------------------------------


Here is what I have tried so far that has not helped

• Clean install of latest GPU drivers
• Tried even downgrading GPU drivers
• Updated BIOS to latest version
• Updated AMD Chipset Drivers
• Updated Motherboard Drivers
• Cleaned out GPU and reseated it in the motherboard
• Tried running Driver Verifier on Windows with no results
• Ran MemTest86 and passed
• Reinstalled Windows 10 (3 times now)
• Ran Prime95 test for 20 hours, no issues
• Bought new RAM
• Bought a new SSD (980PRO)

---------------------------------------------------------------------------------------------------

Here is a link to my dump files : https://drive.google.com/file/d/1nvqkfheKEf-IgmQ5uHQ7PmFXtxlFLkAX/view?usp=sharing

After trying everything in my previous post, I replaced my SSD and the computer seemed to get better. However it is started BSOD 'ing again when playing Unity Games. I was able to further figure out that it seems to BSOD when there are mass movements done in the game. Example moving 500 models of a ship to a different area in the game at the same time. I got with the game developers to try to debug but they are not able to replicate the issue and have asked 20 other players to try the same thing and they dont get the crashing or BSOD. I kept searching on Google and found what seems to be issues that are identical to mine where it seems that math equations or calculations are causing access violations to the memory causing BSOD. Here are a couple links to people with similar issues

https://forum.unity.com/threads/uni...es-made-with-it-are-randomly-crashing.897173/

https://www.bleepingcomputer.com/fo...s-crash-with-unityplayerdll-access-violation/

I was hoping someone way smarter than me can look at my dump files and see if my issue is being caused by the CPU like in the links above and if so, what would be the best way to go about proving to AMD that the CPU is the issue? This thing is driving me nuts and I would like to finally resolve it!

 

[tennis2]

Why couldn't this go in your previous/original thread?

Not sure why you think it's related to a game(s) when the machine crashes in Prime95 and the like.

I see you replaced the RAM. Statistically if a stick was bad in the original kit, your chances of getting a replacement kit that also had a faulty stick should be very small....but never zero.

When you test RAM, test with 1 stick installed at a time. If it's a 2 or 4 stick kit, (similar to above) statistically you'd expect only 1 stick to be bad. Then it's a matter of swapping sticks until you find which one(s) is good or which one is bad.

I've had known a known bad stick of ram go Prime95 for 19 hours before crashing. Crashed consistently within 5-10 minutes doing F@H. Narrowed down the bad stick (and obviously RMA'd the pair/kit) and it worked fine.

 

[effektz]

Why couldn't this go in your previous/original thread?

Not sure why you think it's related to a game(s) when the machine crashes in Prime95 and the like.

I see you replaced the RAM. Statistically if a stick was bad in the original kit, your chances of getting a replacement kit that also had a faulty stick should be very small....but never zero.

When you test RAM, test with 1 stick installed at a time. If it's a 2 or 4 stick kit, (similar to above) statistically you'd expect only 1 stick to be bad. Then it's a matter of swapping sticks until you find which one(s) is good or which one is bad.

I've had known a known bad stick of ram go Prime95 for 19 hours before crashing. Crashed consistently within 5-10 minutes doing F@H. Narrowed down the bad stick (and obviously RMA'd the pair/kit) and it worked fine.

I decided a new one as I am really leaning towards it being an issue with Gaming and thought it would help better for future people who search if the title more aligned to what the issue may of been.

I have tested my RAM one stick at a time and all passed so I bought replacement RAM to see if somehow it was the issue with them. I still got BSODs after replacing the RAM. Even tried individually in different slots and still no improvement. So I am down to either it being motherboard, GPU or CPU. Since I can play other games like Fortnite and CSGO for hours with No issues I feel like I can somewhat eliminate the GPU. Motherboard I feel like I would have other issues to point towards it and when researching I found people who had similar issues as me and it ended up being a CPU issue. Although with theirs it was an Intel CPU, I still think things really point to my cpu causing the issues. I just need to know how I can figure out if it is it so I can RMA it.

Also related to Prime95, I tested it and it had no issues come up.

 

[effektz]

Another interesting note, I was able to constantly get a BSOD when trying to update the AMD Chipset Driver via the Aorus App Center program.

Here is the link to those dump files: https://drive.google.com/file/d/1_8FgUULAWijV2J9WyFzKYyOsoOHXTDJa/view?usp=sharing

 

[johnbl]

I was looking at the pattern of modified core windows files in each memory dump:
here is the pattern:
51722-6765 may 17 09:16 2022 files modified (3) uptime 17:44
51722-6750 may 17 09:33 2022 files ok uptime 16 mins
51722-6578 may 17 10:10 2022 files ok uptime 36 mins
51822-6828 may 18 08:25 2022 files modified (2) uptime 0 days 22 hr 14 mins
51922-6687 may 19 09:49 2022 files modified (2) uptime 1 day 1 hr 23 min sec

seems like something modifies the files in memory, the bugcheck reboots and clean files are loaded, then files are modified again (in memory)

what is running 15 mins after a clean boot up? something in task scheduler? or when you log on?

 

[effektz]

I was looking at the pattern of modified core windows files in each memory dump:
here is the pattern:
51722-6765 may 17 09:16 2022 files modified (3) uptime 17:44
51722-6750 may 17 09:33 2022 files ok uptime 16 mins
51722-6578 may 17 10:10 2022 files ok uptime 36 mins
51822-6828 may 18 08:25 2022 files modified (2) uptime 0 days 22 hr 14 mins
51922-6687 may 19 09:49 2022 files modified (2) uptime 1 day 1 hr 23 min sec

seems like something modifies the files in memory, the bugcheck reboots and clean files are loaded, then files are modified again (in memory)

what is running 15 mins after a clean boot up? something in task scheduler? or when you log on?

I opened Task Scheduler and there seems to be 113 total scheduled tasks. All of these look like Windows processes or AMD related. Is there a way I can help identify which one is doing that?

I also went back to your earlier suggestion last month to download AutoRuns. I see in the scheduled Tasks tab that AMDRyzenMasterSDKTask is showing highlighted in Red. I am not sure what that really means so Ill await for your feedback.

Lastly I did a fresh restart and immediatly BSOD with Kernel Level Security Check. Here are the minidump and Memory Dump if it helps: https://drive.google.com/file/d/1sVuFW-KnO7eakYdFOBGpAV0WFL7a-_2c/view?usp=sharing

 

[effektz]

About 6 more BSODs tonight with Kernal Security Check, System Reference and KMODE Exception

https://drive.google.com/file/d/1jSAk6WeMRWdRXqvlyES23SwsW492sr9g/view?usp=sharing

Also adding the Crash files from the Unity Game that I can replicate the BSOD in. Maybe it will help point to something? When i try to read it, all I get from it is that it is trying to access an Invalid Address

https://drive.google.com/file/d/1JqHCOpImyr-WjpQyr4EV_kSgWFdUqm6e/view?usp=sharing

========== OUTPUTTING STACK TRACE ==================

0x00007FFBB95F048E (UnityPlayer) UnityMain
0x00007FFBB9613DBD (UnityPlayer) UnityMain
0x00007FFBB98898F3 (UnityPlayer) UnityMain
  ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFBB94CA81D)
0x00007FFBB94CA81D (UnityPlayer) (function-name not available)
0x00007FFBB96192C0 (UnityPlayer) UnityMain
0x00007FFBB96154FF (UnityPlayer) UnityMain
0x00007FFBB9612168 (UnityPlayer) UnityMain
0x00007FFBB9601C62 (UnityPlayer) UnityMain
0x00007FFBB95CBE48 (UnityPlayer) UnityMain
0x00007FFBB95D676D (UnityPlayer) UnityMain
0x00007FFBB9769977 (UnityPlayer) UnityMain
0x00007FFBB975810A (UnityPlayer) UnityMain
0x00007FFBB97581B0 (UnityPlayer) UnityMain
0x00007FFBB975C448 (UnityPlayer) UnityMain
  ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFBB951C6BA)
0x00007FFBB951C6BA (UnityPlayer) (function-name not available)
  ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFBB951AB8B)
0x00007FFBB951AB8B (UnityPlayer) (function-name not available)
  ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFBB951FCF2)
0x00007FFBB951FCF2 (UnityPlayer) (function-name not available)
0x00007FFBB9520C7B (UnityPlayer) UnityMain
  ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FF6560711F2)
0x00007FF6560711F2 (MankindRemastered) (function-name not available)
0x00007FFBE9DB7034 (KERNEL32) BaseThreadInitThunk
0x00007FFBEA762651 (ntdll) RtlUserThreadStart

 

[Colif]

i closed your old thread since its 20 days since you last posted.
Have you updated bios this month as there is a new one as of the 12th.

I see in the scheduled Tasks tab that AMDRyzenMasterSDKTask is showing highlighted in Red. I am not sure what that really means so Ill await for your feedback.

Some elements in Autoruns are highlighted with red or yellow:

• Yellow means that the item is exist in registry, but the file is not found.
• Red means that the item’s in the registry, the file is in place, but the Publisher string is empty.

source
I probably shouldn't guess But john might want you to untick it so its not running at start up, see if it makes any difference.

 

[effektz]

I did try it but it did not help one bit. @johnbl did you get a chance to look at the dump files?

 

[johnbl]

edit 4: after you do the various updates, uninstall gigabyte app center
i would not run gigabyte cloud:

This breakthrough application is called GIGABYTE Cloud OC and it gives you real time access to overclocking and system monitoring with the help of virtually any internet connected device such as an iPad, iPhone, notebook PC, netbook, or any smart phone with a browser.

it scares me

edit 3:
overall I think this driver is causing you issues:
gdr3.drv (remove via uninstaller or microsoft autoruns)
note: the debugger could not read the dpc on processor 7 that caused the one bugcheck. to see the who made the call you need to change the memory dump type to kernel so the info is stored in the much larger memroy.dmp file.
minidump only shows the active cpu core stack and driver list.
in the dump I looked at it was a graphic stack overflow. hense; update apu driver and remove gdr3.drv
and maybe remove amdryzenmaseterdriver since it might be tweaking on the cpu APU settings.

edit 2:
https://www.gigabyte.com/Motherboard/X570-AORUS-ELITE-rev-10/support#support-dl-bios
update bios on 5/12/22
(2 versions newer)
I would also pick up the amd chipset driver and apu driver
intel lan driver is updated also.
do not install the utilites, if you have them installed you should remove them for testing.
(I would also disable the amdRyzenMasterDriver.sys for testing,
you could update the version to match your bios version after you get the system stable, your version if from june 24 2021)

edit:
download microsoft autoruns and disable this driver: gdr3.drv
reboot and see if you crash your game/bugcheck

Next, disable any secondary monitor in windows control panel device manager.
reboot and retest.

next if you only have one monitor, make sure it does not have any special scaling
(settings->system->display-> scale and layout. advanced make the system monitor look like a plain dumb monitor.
reboot and retest.

make sure you have all of the windows updates. .net framework, various patches, and Microsoft amd cpu microcode patches.
just in case your motherboard vendor has not picked up the microcode fixes for your cpu.
https://www.amd.com/en/corporate/product-security

I would also look at windows updates and see if they have put in a new amd cpu microcode patch. These can break cpu functions (or appear to break cpu functions) sometimes removing microsoft cpu patch can "fix" thing by not fixing the security. (just a guess)
the microsoft amd cpu microcode patcher is called: mcupdate_authenticAMD.dll
(debugger has issues trying to read amd microcode patch versions)

your bios version is
f36
1/4/2022
x570 aorus elite
amd ryzen 3700x stepping 0




==============
here is a link that sounds reasonable for fixing unity related issues:

URGENT!!! - Unity keeps crashing - Unity Answers

Unity is the ultimate game development platform. Use Unity to build high-quality 3D and 2D games, deploy them across mobile, desktop, VR/AR, consoles or the Web, and connect with loyal and enthusiastic players and customers.

answers.unity.com

.

app log file location:
\Users\<username>\AppData\LocalLow\<CompanyName>\<ProductName>\Player.log
-------------
I am the wrong person to look at app crashes.
it looks like a 32 bit app tried to set up some process, set a timer and waited for a signal.
it then tried to pass control to some memory address and the module was not loaded.
that cause the app to run its fault handler, and I think the fault handler crashed the subsystem.

I would be looking for a .dll that did not get registered and could not load.
or some dll that the function was removed or moved to another file.
as an admin you can use
regsvr32 .exe <dllname>
to register a dll

you might be able to look up the used the function address and look at the build log rebase log file to find out what should have been at that address to find the file name
that could not be loaded. if it is a app dll you could unregister and reregister the dll.
if it is a system file then I guess I would do a system update or a repair of the subsystem
(or a clean install, since I am not sure if dism.exe or sfc will repair the subsystems, windows update for the case where microsoft moves or removes functions, update the unity framework maybe if it is a bug in the game engine)

Note: found the symbol server for unity
info here: Unity - Manual: Windows Debugging (unity3d.com)
in window debugger run the command:
.sympath+ SRVc:\symbols-cache

Index of /

!reload

and you see what unity was trying to do at the time of the crash.
stack was messed up you have to look at the raw stack
via
dqs command

here is part of the raw stack: (read from the bottom up)
0:000> kn
# Child-SP RetAddr Call Site
00 000000c28e0ebc48 00007ff90574cbc0 ntdll!NtWaitForMultipleObjects+0x14
01 000000c28e0ebc50 00007ff90574cabe KERNELBASE!WaitForMultipleObjectsEx+0xf0
02 000000c28e0ebf40 00007ff8a769017d KERNELBASE!WaitForMultipleObjects+0xe
03 000000c28e0ebf80 00007ff8a7690222 UnityPlayer!winutils::ExternalCrashHandler::HandleCrash+0x26d [C:\buildslave\unity\build\PlatformDependent\Win\ExternalCrashHandler.cpp @ 349]
04 000000c28e0ec030 00007ff8a76a1d88 UnityPlayer!winutils::ExternalCrashHandler::HandleCrash+0x22 [C:\buildslave\unity\build\PlatformDependent\Win\ExternalCrashHandler.cpp @ 419]
05 (Inline Function) ---------------- UnityPlayer!winutils::CrashHandler::HandleCrash+0x30 [C:\buildslave\unity\build\PlatformDependent\Win\CrashHandler.cpp @ 281] 06 000000c28e0ec080 00007ff90580ff27 UnityPlayer!winutils::ProcessInternalCrash+0x118 [C:\buildslave\unity\build\PlatformDependent\Win\WinUtils.cpp @ 596] 07 000000c28e0ec0b0 00007ff907c751b0 KERNELBASE!UnhandledExceptionFilter+0x1e7 08 000000c28e0ec1d0 00007ff907c5c766 ntdll!RtlUserThreadStart$filt$0+0xa2 09 000000c28e0ec210 00007ff907c7209f ntdll!_C_specific_handler+0x96 0a 000000c28e0ec280 00007ff907c21454 ntdll!RtlpExecuteHandlerForException+0xf 0b 000000c28e0ec2b0 00007ff907c70bce ntdll!RtlDispatchException+0x244 0c 000000c28e0ec9c0 00007ff8a79cd9b8 ntdll!KiUserExceptionDispatch+0x2e 0d 000000c28e0ed0e0 00007ff8a78d611e UnityPlayer!AtomicStack::Pop+0x68 [C:\buildslave\unity\build\Runtime\Threads\AtomicQueue.cpp @ 316] 0e 000000c28e0ed120 00007ff8a78d7567 UnityPlayer!JobQueue::CreateGroup+0xfe [C:\buildslave\unity\build\Runtime\Jobs\Internal\JobQueue.cpp @ 1099] 0f (Inline Function) ---------------- UnityPlayer!JobQueue::CreateJobsForEach+0x2f [C:\buildslave\unity\build\Runtime\Jobs\Internal\JobQueue.cpp @ 1440]
10 000000c28e0ed180 00007ff8a78d5534 UnityPlayer!JobQueue::ScheduleJobsForEach+0x47 [C:\buildslave\unity\build\Runtime\Jobs\Internal\JobQueue.cpp @ 1434]
11 000000c28e0ed1e0 00007ff8a77993fa UnityPlayer!ScheduleJobForEachDependsInternal+0xa4 [C:\buildslave\unity\build\Runtime\Jobs\Jobs.cpp @ 181]
12 (Inline Function) ---------------- UnityPlayer!ScheduleJobForEachDepends+0x34 [C:\buildslave\unity\build\Runtime\Jobs\Jobs.h @ 332] 13 000000c28e0ed250 00007ff8a7797362 UnityPlayer!PrepareSceneNodes+0x3ca [C:\buildslave\unity\build\Runtime\Camera\Culler.cpp @ 593] 14 000000c28e0eded0 00007ff8a777b976 UnityPlayer!CullScene+0x132 [C:\buildslave\unity\build\Runtime\Camera\Culler.cpp @ 623] 15 000000c28e0edf50 00007ff8a778670f UnityPlayer!Camera::CustomCull+0x356 [C:\buildslave\unity\build\Runtime\Camera\Camera.cpp @ 1608] 16 (Inline Function) ---------------- UnityPlayer!Camera::Cull+0x41 [C:\buildslave\unity\build\Runtime\Camera\Camera.cpp @ 1315]
17 (Inline Function) ---------------- UnityPlayer!DoRenderScreenCamera+0xc8 [C:\buildslave\unity\build\Runtime\Camera\RenderManager.cpp @ 129] 18 000000c28e0ee650 00007ff8a7919977 UnityPlayer!RenderManager::RenderCameras+0x4cf [C:\buildslave\unity\build\Runtime\Camera\RenderManager.cpp @ 351] 19 000000c28e0ef090 00007ff8a790810a UnityPlayer!PlayerRender+0x2c7 [C:\buildslave\unity\build\Runtime\Misc\Player.cpp @ 1000] 1a 000000c28e0ef1a0 00007ff8a79081b0 UnityPlayer!ExecutePlayerLoop+0x5a [C:\buildslave\unity\build\Runtime\Misc\PlayerLoop.cpp @ 384] 1b 000000c28e0ef340 00007ff8a790c448 UnityPlayer!ExecutePlayerLoop+0x100 [C:\buildslave\unity\build\Runtime\Misc\PlayerLoop.cpp @ 408] 1c 000000c28e0ef4e0 00007ff8a76cc6ba UnityPlayer!PlayerLoop+0xb8 [C:\buildslave\unity\build\Runtime\Misc\PlayerLoop.cpp @ 514] 1d 000000c28e0ef560 00007ff8a76cab8b UnityPlayer!PerformMainLoop+0x35a [C:\buildslave\unity\build\PlatformDependent\WinPlayer\WinMain.cpp @ 324] 1e 000000c28e0ef590 00007ff8a76cfcf2 UnityPlayer!MainMessageLoop+0x10b [C:\buildslave\unity\build\PlatformDependent\WinPlayer\WinMain.cpp @ 1202] 1f 000000c28e0ef600 00007ff8a76d0c7b UnityPlayer!UnityMainImpl+0x1542 [C:\buildslave\unity\build\PlatformDependent\WinPlayer\WinMain.cpp @ 1718] 20 000000c28e0ff8a0 00007ff6779711f2 UnityPlayer!UnityMain+0xb [C:\buildslave\unity\build\PlatformDependent\WinPlayer\WinMain.cpp @ 1758] 21 (Inline Function) ---------------- MankindRemastered!invoke_main+0x21 [d:\agent\_work\4\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl @ 118]
22 000000c28e0ff8d0 0000000000000000 MankindRemastered!__scrt_common_main_seh+0x106 [d:\agent\_work\4\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl @ 288]

if the 32bit subsystem is messed up you could try the
dism.exe commands
sfc.exe commands
or do a repair install of windows
(same version of windows but a repair install to fix the subsystem)
then reinstall your game and see if it works as expected.

I don't like seeing any modules loaded that start with ati
since ati was sold to amd so many years ago. but I don't know much about the 33 bit subsystems to know if these ati modules are legit.

 

[effektz]

@johnbl

So I based on your feedback I have done the following:

1. Run sfcscannow, no issues detected
2. Run DISM commands, no issues detected
3. Removed Gigabyte APP Center
4. Checked scaling in Display and everything is set to recommended settings
5. Engaged Game Developers who are making a special build to see if there is an AMD Thread issue
6. Changed MEMORY dump to Kernel
7. Downloaded Autoruns
8. There is no driver gdr3.drv listed in the drivers tab, so I am not sure where this is located
9. I have disabled and deleted amdRyzenMaster driver but it keeps coming back even after restart (and I ran AutoRuns as Administrator)
10. I downloaded the drivers for LAN, APU and Chipset
11. Installed LAN Driver
12. Tried to Install Chipset Driver but continuously BSOD with SYSTEM_REFERENCE_EXCEPTION

Here is the link to the logs from the last 3 BSOD and the MEMORY dump file which should be Kernel now. I appreciate your help with this, I feel like we are on to something. Since I cannot install chipset drivers I am wondering if that would point to my CPU failing?

https://drive.google.com/file/d/1VWPod-pN509X3_9nuAkCE6cWAp4Jwa70/view?usp=sharing

 

[johnbl]

run this tool to see if it fixes install/uninstall problems with your chipset drivers:
https://support.microsoft.com/en-us...-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d
(uninstall any amd driver you see then try to install the chipset again)

looks like 4 installs going on at the same time.
i would try and do the amd chipset install, reboot before attempting the RadeonSoftware install.
when you install these, just install the basic drivers needed without adding any extra utilities until later if you need them.
I assume all of these programs are for an amd graphics card

avoid the amd utilites also until you get your system stable:
things like amdfendrsr.exe amd crash defender service
------------
basic assumption is malware/rootkit issue
you might try to do a complete memory dump and zip it and provide that so I can see what is hiding and where.

will look at some of the logs and the minidumps to see if i see something useful.

-------------------
-windows kernel has been modified.
-null.sys driver has been replaced. looks like it is also paged out to disk so it could not be looked at. checksum removed.
-
\SystemRoot\system32\drivers\AtihdWT6.sys
(ati audio driver ?, suspect due to its name)

\AMDRyzenMasterDriver.sys Thu Jun 24 22:21:58 2021
installed. you need to find out how this keeps coming back.

Instup.exe running to update Avast Free Antivirus at time of bugcheck.
I can not see that avast is even installed. were you doing a antivirus install at the time of the bugcheck.
------------
Desc: ITE Device(8595)
is connected to a usb hub that is suspended.
device is
IT8297 RGB LED Controller

Genesys Logic, Inc.
hub is also on a suspended hub
-------
BIOS Version F36
BIOS Starting Address Segment f000
BIOS Release Date 01/04/2022
Manufacturer Gigabyte Technology Co., Ltd.
Product Name X570 AORUS ELITE
AMD Ryzen 7 3700X 8-Core Processor

 

[effektz]

@johnbl

I am unable to delete the AMDRyzenMasterDriverV19. Everytime I do, it just says Failed to delete and its not listed when trying to use that uninstaller fixer you linked. When I got the bug check i was just trying to install the AMD Chip Set drivers from Gigabytes website.

I changed the Memory dump as you had said and got a BSOD. Here is the dump file and the memory file

https://drive.google.com/file/d/1bmkUQWuXcxj7sMtBRqG5iJ_Kleill7GH/view?usp=sharing

 

[effektz]

@johnbl So I deleted all the AMD Drivers using that Tool you sent. Verified in Autoruns that AMDRyzenMaster was gone and then tried to install the AMD Chipsets Driver and got another BSOD. Here is that one with the full dump

https://drive.google.com/file/d/1bYftLikbPpNHSe3ibHl2XFJBQUU7_LbZ/view?usp=sharing

 

[johnbl]

@johnbl

I am unable to delete the AMDRyzenMasterDriverV19. Everytime I do, it just says Failed to delete and its not listed when trying to use that uninstaller fixer you linked. When I got the bug check i was just trying to install the AMD Chip Set drivers from Gigabytes website.

I changed the Memory dump as you had said and got a BSOD. Here is the dump file and the memory file

https://drive.google.com/file/d/1bmkUQWuXcxj7sMtBRqG5iJ_Kleill7GH/view?usp=sharing
note: these updates might need to match your bios version. amd will have the current versions but your motherboard vendor might be 6 months in providing the matching bios version.
so check the motherboard vendor website

main issue I see so far is that your drive from samsung went into a unknown state right before the crash. Also all of your usb devices were waiting to wake up. maybe change the system settings to high performance mode so the nothing sleeps.
since both storage drivers state changed to unknown it could be one of the amd link drivers having a issue. I think sleep functions would have been logged.

I would focus on: removing all amd chip drivers/ ryzen drivers and getting a reinstall of them.
-----------

the new memory dump works very well.
it looks like your custom version of unity crashed the system but i think it was due to your drive going into a unknown state.
you have several files that the debugger shows as modified, since this is from a subsystem I don't know if that is a problem. the debugger complained that its memory allocations did not add up correctly.
(not sure if this is common with a subsystem since i normally do not debug subsystems.) let me look for instructions on how to do that. How to Install AMD Ryzen™ Chipset Drivers on a Windows® Based System | AMD
(bottom of txt has info on uninstall)

notes:
12 errors : dbghelp (7ff8efa2b018-7ff8efa2d678)
10 errors : KERNELBASE (7ff8f63f40e4-7ff8f63f4420)
10 errors : KERNEL32 (7ff8f863b0e4-7ff8f863b408)
8 errors : ntdll (7ff8f8954124-7ff8f8954424)
6 errors : nt (fffff80548531620-fffff8054853162a)
C:\Users\jlewa\OneDrive\Desktop\MK Special Build\v3.0.7.10xth\UnityPlayer.dll Sat May 1 02:08:19 2021

C:\Program Files\AMD\Performance Profile Client\AMDRyzenMasterDriver.sys Thu Jun 24 22:21:58 2021


Sum of individual system commit + Process commit exceeds overall commit by 13016 Kb ? **

InstancePath is "PCI\VEN_144D&DEV_A808&SUBSYS_A801144D&REV_00\6&fa55729&0&0008000A"
ServiceName is "stornvme"
device was working then went to
StateHistory[19] = Unknown State (0x0)
same as:
InstancePath is "PCI\VEN_1022&DEV_7901&SUBSYS_79011022&REV_51\6&2b648123&0&0050000A"
ServiceName is "storahci"


bunch of your usb devices are waiting for a wake signal

 

[johnbl]

second bugcheck was also from wow64 subsystem
ie running 32 bit apps via emulation.
app running at the time was instupd.exe
debugger shows 229 modifications to the file clr.dll
this module contains machine code to start .net
kernelbase.dll 4 modifications
user32.dll 16 modifications
wow64.dll 124 modifications
extra copy of ntdll.dll loaded at an offset
debugger is still scanning (taking a long time for some reason)
will check on some of the changes to see what kind of change
will check when debugger stops scanning

not sure what is going on with your dotnet files, maybe some dot net update?
the files have a internal string:
file version 4.8.4510.0 built by net48rel1last_b
private build ddbld365b
file date march 31 2022

 

[effektz]

Ok I will watch for your updates! I did uninstall and then reinstall the AMD Chipsets using the copy downloaded from AMD and not gigabyte. I changed the power plan from Ryzen Balanced Power to High Performance. As for USB Devices, I just have a mouse, keyboard, and a gaming headset plugged into the USBs.

 

[effektz]

@johnbl I am working on uploading a new dump for you. I got a KERNAL SECURITY CHECK FAILURE after I had put the PC to High Performance and installed the Ryzen Chip Sets. May take a bit to upload the file to Google (as my internet sucks) but I will share the link once it is done

 

[johnbl]

@johnbl I am working on uploading a new dump for you. I got a KERNAL SECURITY CHECK FAILURE after I had put the PC to High Performance and installed the Ryzen Chip Sets. May take a bit to upload the file to Google (as my internet sucks) but I will share the link once it is done

ok, I will be out for a few hours. will look at it when I get back.
FYI: the error with the drive was when it woke up
WakeFromD3 it was supposed to have no flags set but returned
0x00400000 and that was not a defined flag so windows reported a error from the subsystem. something wrong with sleep functions.

 

[effektz]

ok, I will be out for a few hours. will look at it when I get back.
FYI: the error with the drive was when it woke up
WakeFromD3 it was supposed to have no flags set but returned
0x00400000 and that was not a defined flag so windows reported a error from the subsystem. something wrong with sleep functions.

Here is the link: https://drive.google.com/file/d/1AtFEpFygO_I9rqj8e2mY2gfM-7gePGdq/view?usp=sharing

I am hoping to really figure this out as its driving me insane. I have updated the firmware on the main NVMe SSD through Samsung Magic Software

 

[johnbl]

Here is the link: https://drive.google.com/file/d/1AtFEpFygO_I9rqj8e2mY2gfM-7gePGdq/view?usp=sharing

I am hoping to really figure this out as its driving me insane. I have updated the firmware on the main NVMe SSD through Samsung Magic Software

stack corrupted, raw stack shows game calling a nt function then nt function crashes but the nt file has been modified

the usb shows various usb devices waiting for a wake up signal but the usbhub3 driver has been modified

pci.sys bus driver also has been modified
ntdll driver has been modified
also indicates dbhelp has been modified

storage drive indicates it is waiting for a wake signal.

 

[johnbl]

stack corrupted, raw stack shows game calling a nt function then nt function crashes but the nt file has been modified

the usb shows various usb devices waiting for a wake up signal but the usbhub3 driver has been modified

pci.sys bus driver also has been modified
ntdll driver has been modified
also indicates dbhelp has been modified

storage drive indicates it is waiting for a wake signal.

I would think something is wrong with the amd power management.

 

[effektz]

I would think something is wrong with the amd power management.

Would that mean something related to the CPU? My brother has the exact same PC build as me and he does not have the issues I am experiencing. I guess where should I go from here? Should I continue to log the BSODs and upload them?

 

[effektz]

@johnbl Here is another dump for you. I upgraded the Motherboard BIOS from F36 to F37c. I got BAD OBJECT HEADER in this one

https://drive.google.com/file/d/1_GbRaobcvTMfD0g2UrituK8iauW3-fiY/view?usp=sharing

 

[johnbl]

@johnbl Here is another dump for you. I upgraded the Motherboard BIOS from F36 to F37c. I got BAD OBJECT HEADER in this one

https://drive.google.com/file/d/1_GbRaobcvTMfD0g2UrituK8iauW3-fiY/view?usp=sharing

windows wow64 subsystem looks like some chrome extension attempting to get access to something and it tried to pass control to a bad memory address (address zero) function called was
chrome!GetHandleVerifier

not sure what chrome_elf.dll is for