authenticamd.sys bsod

M

michaelv

Member
Joined
Oct 4, 2022
Posts
13
Hi,

Is anyone able to help me identify the cause of regular bsods caused by authenticamd.sys?

I've run a 20 pass Memtest86+ test with no RAM failures.

Dump files here:

Public
 
The dumps you have so far are inconclusive, so I'm going to ask you to enable Driver Verifier for third-party drivers. This is a tool that subjects drivers to additional checks in an attempt to isolate flaky drivers. Be warned though, that Driver Verifier is designed to make your system BSOD if it finds a suspect driver, so you may see more BSODs whilst we troubleshoot your system.

To enable Driver Verifier please see the instructions here. Please be sure that System Restore is enabled and cut a restore point before you turn Driver Verifier on, this will allow you to recover your system in the (unlikely) event that Driver Verifier BSODs a driver during the boot process.

If your system BSODs with Driver Verifier enabled then restart as normal. We want as many dumps (ie. BSODs) as possible, but I would suggest you disable Driver Verifier after 48 hours. You can do this from a command prompt by entering the command verifier /reset and then rebooting. Please then run the Sysnative file collection app again and upload the zip file.

I did notice that you use Driver Easy and have a scheduled Driver Easy scan running each day. Do you use Driver Easy to download and install your drivers? If so, when was the last time you used it to install a driver update?
 
The Sysnative log collector was unable to collect multiple files.



The BSOD bugchecks seen in the log files were:

3B
BE
7F
A
7E
F7
1E



Memtest86+ results were reported in the opening post.
A share link for the result images was not posted.
The software version used for the testing was not reported.



The logs displayed a fresh installation on 9/12/22.

The computer has had at least 7 types of bugchecks within the past 22 days.




1) Please uninstall Kaspersky AV using the applicable uninstall tool and post a new log collector share link.

Removal tool for Kaspersky applications (kavremover)
How to remove a Kaspersky application


2) Make sure that Microsoft defender is on.


When installing drivers on Lenovo hardware it's best to use the Lenovo automatic driver update.
This will install the best tested drivers.

laptops and netbooks :: yoga series :: yoga slim 7 14are05contentdetail - Lenovo Support US



3) Post a new Sysnative log collector share link after uninstalling all third party antivirus software.


4) Lenovo has a full hardware diagnostic sweet.
If can run overnight and images or share links could be posted into this thread.
laptops and netbooks :: yoga series :: yoga slim 7 14are05 - Lenovo Support US
 
Hi,

I ran the Lenovo diagnostics and all tests passed (attached).

I've uninstalled Kaspersky.

I ran driver verifier over the weekend and the PC crashed many times, but only 1 crash seems to have been written to the dump.

I have rerun Sysnative log collector and the results are attached. It stops at "Gathering network statistics".

Thanks for any assistance you can provide in identifying the cause of the BSODs.
 

Attachments

Have you modified any of the BIOS settings? If so, which ones and why?

Could you be more descriptive about how these BSODs happen? Is there a pattern for example; do they happen with specific applications, do they happen when gaming, do they happen after a long time of running, etc.
 
I updated the BIOS firmware but none of the settings (and not over-clocking).

No apparent pattern, sometimes after a couple of days, sometimes a few hours, almost always while the computer is idle.
 
When did you do the BIOS update?

Was the system OK (ie. not having BSODs) for some time afterwards?

From where did you obtain the BIOS update?
 
The opening post reported the use of Memtest86+.


The computer is using LPDDR4 RAM at 4266 MHz.


In the forums this software Memtest86+ has rarely been used for this type of RAM.


There may be false negatives.





Please test the RAM with Memtest86 free version.


MemTest86 - Official Site of the x86 Memory Testing Tool


Run two tests of four passes each (total of eight passes).


Take pictures and post images or share links into this thread.
 
I think we need to try and eliminate third-party drivers and services as much as we can on reboot. These are the most likely cause of BSODs, so eliminating them should prevent your BSODs - unless this is a hardware issue of course.

The easiest way to eliminate third party drivers is to boot into safe mode. This will not provide a system where you'll be able to do much real work however, so it may be something you want to do before you go to bed and leave the system running at idle (in safe mode) overnight. There are instructions from Microsoft on how to start in safe mode here.

If it's still running in safe mode in the morning then you've not had a BSOD and that will be important troubleshooting information. If it BSODs overnight and restarts it will restart into normal mode (and you wont see the SAFE MODE warning messages).
 
After a bit of research I can tell you that sleep is not active in Safe Mode, so the shutdowns do look like they may be hardware related.

Could yopu please run the Sysnative BSOD Collection app again please and upload the zip file. There should be some data about the shutdowns in the logs which may point us in the right direction.
 

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

Back
Top