I am in despair! Persistent authenticamd.sys BSOD's

No luck here. At the time I thought things have settled down but no. I even replaced the Ram with new dimms but still the same problem. I also reinstalled windows 11 to rule out any driver issues.
My latest minidump is this: Easyupload.io - Upload Files and Share Them Easily. At this point it seems to me the culprit is my cpu. I cannot think what else could it be? My temps are fine.
 
Hi!

- Make sure you have the two ram sticks seated in the second and fourth slots (starting from the CPU).
- Update the BIOS to 7C84v1I.1 (Beta version) 2024-09-05.
- Load optimized defaults (F6).
- Set the RAM frequency/speed to 3200 MHz (MT/s).
- Uninstall MSI center and run Clean Center Master to completely remove MSI Center
- Post fresh logs.
 
xilolee said:
Hi!

- Make sure you have the two ram sticks seated in the second and fourth slots (starting from the CPU).
- Update the BIOS to 7C84v1I.1 (Beta version) 2024-09-05.
- Load optimized defaults (F6).
- Set the RAM frequency/speed to 3200 MHz (MT/s).
- Uninstall MSI center and run Clean Center Master to completely remove MSI Center
- Post fresh logs.
Click to expand...

Thanks for your post. I have set the ram to various speeds to no effect.

With my new installation of Win11 I never installed MSI center or any of their crapware other than the drivers needed for the chipset/cpu. Dimms are on 2nd and 4rh slot. Would it be essential to update to the very latest Beta version? I tend to stay away from beta releases. I have already tried F6.
 
New logs with--> Blue Screen of Death (BSOD) Posting Instructions - Windows 11, 10, 8(.1), 7 and Vista


You had two whea-logger event ids:
Read More:

The VPN seems the culprit (in the first one).
You also got two driver verifier violations about mullvad-split-tunnel.sys.

If you uninstall it, could you always re-install it?
Could you live without it for some days?
How often do bsods occur?
 
xilolee said:
New logs with--> Blue Screen of Death (BSOD) Posting Instructions - Windows 11, 10, 8(.1), 7 and Vista


You had two whea-logger event ids:
Read More:

The VPN seems the culprit (in the first one).
You also got two driver verifier violations about mullvad-split-tunnel.sys.

If you uninstall it, could you always re-install it?
Could you live without it for some days?
How often do bsods occur?
Click to expand...
Yes I can uninstall mullvad though I mostly use it inside vmware. It does not run by default and I do not often turn it on while on my main windows. Bsods occur daily or every other day or few days. About once each day, never had many in the same day. Logs: Easyupload.io - Upload Files and Share Them Easily
 
It's almost like the others.
In the first one, mullvad-split-tunnel.sys (Thu Sep 22 11:41:33 2022) is not present, dxgkrnl.sys (DirectX Graphics Kernel) is present.
In the last one, vmware was probably in use.
In all dumps, hal.dll (Hardware Abstraction Layer DLL) and pshed.dll (Platform Specific Hardware Error Driver) are present.

  1. 0x124 {0, ffff9e894b602028, fc800800, 60c0859}
    PROCESS_NAME: chrome.exe
    !blackboxpnp deviceid: SW\{96E080C7-143C-11D1-B40F-00A0C9223196}\{3C0D501A-140B-11D1-B40F-00A0C9223196}
    (Microsoft Streaming Service Proxy)

  2. 0x124 {0, ffffd483a2a43028, bc800800, 60c0859}
    PROCESS_NAME: chrome.exe
    !blackboxpnp deviceid: SW\{96E080C7-143C-11D1-B40F-00A0C9223196}\{3C0D501A-140B-11D1-B40F-00A0C9223196}
    (Microsoft Streaming Service Proxy)

  3. 0x124 {0, ffffd481b8c23028, fc800800, 60c0859}
    PROCESS_NAME: chrome.exe
    !blackboxpnp deviceid: SW\{96E080C7-143C-11D1-B40F-00A0C9223196}\{3C0D501A-140B-11D1-B40F-00A0C9223196}
    (Microsoft Streaming Service Proxy)

  4. 0x124 {0, ffffd70beb823028, bc800800, 60c0859}
    PROCESS_NAME: dwm.exe
    !blackboxpnp deviceid: SW\{96E080C7-143C-11D1-B40F-00A0C9223196}\{3C0D501A-140B-11D1-B40F-00A0C9223196}
    (Microsoft Streaming Service Proxy)

  5. 0x124 {0, ffffa38f8cf94028, bc800800, 60c0859}
    PROCESS_NAME: chrome.exe
    !blackboxpnp deviceid: USB\Vid_0E0F&Pid_0001\9&3c9c7f0&0&2
    (VMware Device)
Read More:
 
Last edited:
All these BSODs are WHEA_UNCORRECTABLE_ERROR bugchecks - WHEA is the Windows Hardware Error Architecture. These are usually hardware related as I mentioned back in post #2. You've tested RAM thoroughly be removing each stick and in post #16 I suggested you run Prime95 to stress test the CPU. It's seems then that you were questioning the ability of your CPU cooler in order to run Prime95? I don't know whether you ever did run Prime95?

That most recent 0x124 dump is also referencing memory in the same way as earlier...
Code: 
FAILURE_BUCKET_ID:  0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys
It is thus important that we check the CPU...
 
ubuysa said:
All these BSODs are WHEA_UNCORRECTABLE_ERROR bugchecks - WHEA is the Windows Hardware Error Architecture. These are usually hardware related as I mentioned back in post #2. You've tested RAM thoroughly be removing each stick and in post #16 I suggested you run Prime95 to stress test the CPU. It's seems then that you were questioning the ability of your CPU cooler in order to run Prime95? I don't know whether you ever did run Prime95?

That most recent 0x124 dump is also referencing memory in the same way as earlier...
Code: 
FAILURE_BUCKET_ID:  0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys
It is thus important that we check the CPU...
Click to expand...

I have run Prime95 for 2 hours for each instance and all completed without any errors. Is this test enough of a benchmark to completely rule out the CPU? Can we rule out that its not the motherboard/gpu/sound card?
 
CheekyKid said:
I have run Prime95 for 2 hours for each instance and all completed without any errors. Is this test enough of a benchmark to completely rule out the CPU? Can we rule out that its not the motherboard/gpu/sound card?
Click to expand...
That's good, so we know your RAM is good and your CPU is good. It is possible, on rare occasions, for a 0x124 BSOD to be caused by a rogue driver, so we need to check for those now by enabling Driver Verifier. This will subject every selected driver (which will be all third-party drivers) to extra checks as they are loaded, if any of those checks fail Driver Verifier will BSOD. The resulting dump will tell us which driver was at fault (so you MUST keep all dumps).

Full details on enabling Driver Verifier with the appropriate settings can be found here: Driver Verifier Instructions - BSOD - Windows 11, 10, 8(.1), 7 and Vista. Have a read through all that before you make any changes, it's not as difficult as it first appears. It's VERY important that you create a restore point, or take a full image of your system drive (via Macrium, Acronis, or similar), before you enable Driver Verifier. Don't skip that step.

The BSOD stop codes we are particularly interested in are these...
  • 0xC1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
  • 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION
  • 0xC6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
  • 0xC9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
  • 0xD6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
  • 0xE6: DRIVER_VERIFIER_DMA_VIOLATION
If you see one or more BSODs with any of those stop codes make absolutely certain that you keep the dumps. Other BSODs may also happen but these we are less interested in at the moment.

Keep Driver Verifier enabled for 48 hours and in that time use every app, every feature, every device that you have. Driver Verifier can only check drivers when they are loaded, so it's important that we get every third-party driver that you have installed loaded at some point in that 48 hours.

Note that, because Driver Verifier is doing extra work each timer a driver is loaded, you may notice some slight performance degradation, this is normal and cannot be helped.
 
ubuysa said:
That's good, so we know your RAM is good and your CPU is good. It is possible, on rare occasions, for a 0x124 BSOD to be caused by a rogue driver, so we need to check for those now by enabling Driver Verifier. This will subject every selected driver (which will be all third-party drivers) to extra checks as they are loaded, if any of those checks fail Driver Verifier will BSOD. The resulting dump will tell us which driver was at fault (so you MUST keep all dumps).

Full details on enabling Driver Verifier with the appropriate settings can be found here: Driver Verifier Instructions - BSOD - Windows 11, 10, 8(.1), 7 and Vista. Have a read through all that before you make any changes, it's not as difficult as it first appears. It's VERY important that you create a restore point, or take a full image of your system drive (via Macrium, Acronis, or similar), before you enable Driver Verifier. Don't skip that step.

The BSOD stop codes we are particularly interested in are these...
  • 0xC1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
  • 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION
  • 0xC6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
  • 0xC9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
  • 0xD6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
  • 0xE6: DRIVER_VERIFIER_DMA_VIOLATION
If you see one or more BSODs with any of those stop codes make absolutely certain that you keep the dumps. Other BSODs may also happen but these we are less interested in at the moment.

Keep Driver Verifier enabled for 48 hours and in that time use every app, every feature, every device that you have. Driver Verifier can only check drivers when they are loaded, so it's important that we get every third-party driver that you have installed loaded at some point in that 48 hours.

Note that, because Driver Verifier is doing extra work each timer a driver is loaded, you may notice some slight performance degradation, this is normal and cannot be helped.
Click to expand...

What if after 48 hours I have no BSODS? they come and go randomly and they may not occur within 48hours

ET_Explorer said:
Do you see any led light on your mother indicating a cpu problem.
Click to expand...

No, nothing.
 
CheekyKid said:
What if after 48 hours I have no BSODS? they come and go randomly and they may not occur within 48hours
Click to expand...
During that 48 hours I've asked you to use every device, every app, every feature, so that every third-party driver is loaded at some point. If after 48 hours, having ensured that every third-party driver has been loaded, there are no Driver Verifier BSODs then we can safely conclude that the 0x124 BSODs are not being caused by a driver.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top