Question Persistent blue screen errors (AuthenticAMD.sys) ?

Toggle sidebar Toggle sidebar
C

cheekykid

Distinguished
Jul 12, 2006
54
0
18,530
I've been having AuthenticAMD.sys errors for a long time now and am determined to get to the bottom of it as I am sick of them.

My latest minidump files : https://file.io/FN8KhhcX2uc3

I also have a kernel memory dump file but it is too large to upload but it shows:

Bugcheck code: 0x124(0x0, 0xFFFF930CDAE02028, 0xBC800800, 0x60C0859)
Bugcheck name:WHEA_UNCORRECTABLE_ERROR

I have tested my RAM with memtest and have found no errors. My Seasonic PSU was over 10 years old and recently replaced it thinking it could be it but no. My temps are fine. The crashes happen when I am on Windows 11 without doing anything intensive. Drivers are up to date across the board.

The only thing I can think of is that my Ryzen 5900X has started failing. I have tried to reseat it and put new thermal paste etc. but nothing. Same for the RAM sticks and the GPU.

I am not sure if I can RMA my CPU as I don't have the original purchase receipt and also I am not 100% sure its the CPU anyway. I would have to buy a new one which I am open to as they aren't that expensive but I just want first make sure am not missing something else. Last thing left to try is re-install Windows 11 and see if this does something.

Any thoughts please?
 
Hey,


Windows 11 Pro N 64-bit

AMD Ryzen 9 5900X 55 °C

Corsair CMH32GX4M2Z3600C18 16GBx4 = 64.0GB Dual-Channel DDR4 @ 1314MHz (18-18-18-43) ( I run them intentionally at a lower speeds just in case)

MSI MAG X570 TOMAHAWK WIFI (MS-7C84) (AM4) 36 °C

NVIDIA GeForce RTX 2080 (ASUStek Computer Inc) 36 °C

1863GB Samsung SSD 860 QVO 2TB (SATA (SSD)) 25 °C
931GB Samsung SSD 980 PRO 1TB
1863GB Western Digital WD Blue SN580 2TB

All l chipset drivers and system drivers are up to date. I am using the latest non beta Bios version from MSI.
 
down load and run this:
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

you have various problems with the build but the root cause of your bugcheck is due to the 3 copies of overclocking software.
you will want to start autoruns64 and delete the entry that looks like this:
NTIOLib_X64_fffff80328740000 NTIOLib_X64.sys Fri Dec 22 00:42:29 2023

it is colliding with this driver that is in another directory
NTIOLib_X64.sys Mon Jan 22 02:01:33 2024

the setup program does not remove the old driver before installing the new one in a different directory. Problem is the drivers are kind of stupid and each one increases the cpu frequency by some percent. the second copy causes the cpu to become unstable and results in the bugcheck.
(I would delete both copies of ntiolib_x64.sys) (first fix attempt)

your third overclock driver is
AMDRyzenMasterDriver.sys Tue Aug 1 00:37:54 2023
(this driver does not match the bios date of 7/2024 you might want to install a update to match the bios)
(second fix attempt would be to update this driver and chipset drivers to match the bios version)

note:
i would also remove:
DellInstrumentation.sys Tue Mar 19 06:56:38 2024
and
trufos.sys Thu Jul 20 04:40:54 2023

note: cpu reported the internal error and called the bugcheck
cpu is most likely ok after you get the drivers corrected
 
Last edited:
  • Like
Reactions: Roland Of Gilead
johnbl said:
down load and run this:
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

you have various problems with the build but the root cause of your bugcheck is due to the 3 copies of overclocking software.
you will want to start autoruns64 and delete the entry that looks like this:
NTIOLib_X64_fffff80328740000 NTIOLib_X64.sys Fri Dec 22 00:42:29 2023

it is colliding with this driver that is in another directory
NTIOLib_X64.sys Mon Jan 22 02:01:33 2024

the setup program does not remove the old driver before installing the new one in a different directory. Problem is the drivers are kind of stupid and each one increases the cpu frequency by some percent. the second copy causes the cpu to become unstable and results in the bugcheck.
(I would delete both copies of ntiolib_x64.sys) (first fix attempt)

your third overclock driver is
AMDRyzenMasterDriver.sys Tue Aug 1 00:37:54 2023
(this driver does not match the bios date of 7/2024 you might want to install a update to match the bios)
(second fix attempt would be to update this driver and chipset drivers to match the bios version)

note:
i would also remove:
DellInstrumentation.sys Tue Mar 19 06:56:38 2024
and
trufos.sys Thu Jul 20 04:40:54 2023

note: cpu reported the internal error and called the bugcheck
cpu is most likely ok after you get the drivers corrected
Click to expand...

I got rid off MSI Command Center which should have sorted the first points you raised, right? I cannot find any NTIOLib files manually.

I used Amd chipset update utility and it updated everything supposedly as far as the chipset/cpu. Have also updated what I can update from MSI. I can't see how to update AMDRyzenMasterDriver.sys specifically. As far as I can tell I do not have the AMDRyzenMasterDriver.sys installed. There next to nothing in the AMD directory.

To remove trufos.sys I would need remove Bitdefender. Is this essential?
 
Last edited:
Apologies in that case. It's not wise to use a cloud service that deletes files after such a short time.

Instead, please download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here - one that doesn't delete files! The SysnativeBSODCollectionApp collects all the available troubleshooting data and will make diagnosing your problem much easier. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.
 
cheekykid said:
I got rid off MSI Command Center which should have sorted the first points you raised, right? I cannot find any NTIOLib files manually.

I used Amd chipset update utility and it updated everything supposedly as far as the chipset/cpu. Have also updated what I can update from MSI. I can't see how to update AMDRyzenMasterDriver.sys specifically. As far as I can tell I do not have the AMDRyzenMasterDriver.sys installed. There next to nothing in the AMD directory.

To remove trufos.sys I would need remove Bitdefender. Is this essential?
Click to expand...
sorry keep the bit defender file. I was thinking of a different driver
autoruns64 should show the list of third party drivers.
 
Many thanks for the upload.

There are no dumps in there but you have been having BSODs, I can see them in the DxDiag.txt output (at the bottom if you want to look). They are all 0x124 WHEA_UNCORRECTABLE_ERROR indicating, as you might imagine, a fatal hardware error. There have also been several live kernel 0x124 event, these are corrected hardware errors.

It would seem that you probably have a hardware failure of some sort on there. 10 hours is not that long when you're testing 64GB of RAM, it might be quicker for you to remove two sticks and test each pair of sticks on their own. I suggest that Passmark's Memtest86 is a better choice of tester.

It would be wise to ensure that your system is properly configured for writing dumps. All of the following must be true...
  • The page file must be on the same drive as your operating system
  • Set page file size to "system managed"
  • Set system crash/recovery options to "Automatic memory dump"
  • The "Overwrite any existing file" box must be checked
  • The "Write an event to the system log" must be checked
  • The dump file location must be %SystemRoot%\MEMORY.DMP
  • Windows Error Reporting (WER) system service should be set to MANUAL
  • User account control must be running
In addition, the following can also prevent you seeing dumps...
  • SSD drives with older firmware may not create dumps (update the drive firmware)
  • Cleaner applications like Ccleaner delete dump files, so don't run them until you are fixed
  • Bad RAM may prevent the data from being saved and written to a file on reboot, so if all else fails test your RAM

It may also be worth stress testing your CPU with Prime95....
  1. Download Prime95 and a CPU temperature monitor (CoreTemp will do).
  2. Keep the temperature monitor running all the time you run Prime95. Your CPU will get hot!
  3. Run each of the three Prime95 tests (smallFFTs, largeFFTs, and Blend) one after the other for a minimum of 1 hour per test, 2 hours per test would be better.
  4. If Prime95 generates error messages, if the system crashes/freezes/BSODs, or if your CPU temp reaches 95°C (Tmax for your CPU), then stop Prime95 and let us know what happened.
Note that a properly cooled and stable CPU should be able to run all Prime95 tests pretty much indefinitely.

FYI: The small FFT test stresses the CPU more than RAM. The large FFT test stresses RAM more than the CPU. The Blend test is a mixture of the two.
 
ubuysa said:
Many thanks for the upload.

There are no dumps in there but you have been having BSODs, I can see them in the DxDiag.txt output (at the bottom if you want to look). They are all 0x124 WHEA_UNCORRECTABLE_ERROR indicating, as you might imagine, a fatal hardware error. There have also been several live kernel 0x124 event, these are corrected hardware errors.

It would seem that you probably have a hardware failure of some sort on there. 10 hours is not that long when you're testing 64GB of RAM, it might be quicker for you to remove two sticks and test each pair of sticks on their own. I suggest that Passmark's Memtest86 is a better choice of tester.

It would be wise to ensure that your system is properly configured for writing dumps. All of the following must be true...
  • The page file must be on the same drive as your operating system
  • Set page file size to "system managed"
  • Set system crash/recovery options to "Automatic memory dump"
  • The "Overwrite any existing file" box must be checked
  • The "Write an event to the system log" must be checked
  • The dump file location must be %SystemRoot%\MEMORY.DMP
  • Windows Error Reporting (WER) system service should be set to MANUAL
  • User account control must be running
In addition, the following can also prevent you seeing dumps...
  • SSD drives with older firmware may not create dumps (update the drive firmware)
  • Cleaner applications like Ccleaner delete dump files, so don't run them until you are fixed
  • Bad RAM may prevent the data from being saved and written to a file on reboot, so if all else fails test your RAM

It may also be worth stress testing your CPU with Prime95....
  1. Download Prime95 and a CPU temperature monitor (CoreTemp will do).
  2. Keep the temperature monitor running all the time you run Prime95. Your CPU will get hot!
  3. Run each of the three Prime95 tests (smallFFTs, largeFFTs, and Blend) one after the other for a minimum of 1 hour per test, 2 hours per test would be better.
  4. If Prime95 generates error messages, if the system crashes/freezes/BSODs, or if your CPU temp reaches 95°C (Tmax for your CPU), then stop Prime95 and let us know what happened.
Note that a properly cooled and stable CPU should be able to run all Prime95 tests pretty much indefinitely.

FYI: The small FFT test stresses the CPU more than RAM. The large FFT test stresses RAM more than the CPU. The Blend test is a mixture of the two.
Click to expand...

Yes I accidentally deleted the dumps myself. Let me run these tests and get back to you.
 
I run Prime 95 for 2 hours each time for Smallest FFTS, Small FFTS and Large FFTS. No blue screens or issues whatsoever. Temps were fine too but sometimes did creep up to 90C for a short while and then fell. I had my Noctua running at full speed 1500RPM.

Can we deduce from this that my CPU is in the clear and can therefore concentrate on the RAM? In the past BSODS always happened when my CPU temps were low and not under stress.
 
Last edited:
I would like to update this thread and say that I have now removed the 2 DIMMS that I had for a few years now (blue screens were happening with them in place) and left behind the 2 newer ones that I bought this year and which presumably are ok. This is to rule out one of them older DIMMS being faulty and causing the problems. Next step would be new installation of Windows.
 
Last edited:
cheekykid said:
I would like to update this thread and say that I have now removed the 2 DIMMS that I had for a few years now (blue screens were happening with them in place) and left behind the 2 newer ones that I bought this year and which presumably are ok. This is to rule out one of them older DIMMS being faulty and causing the problems. Next step would be new installation of Windows.
Click to expand...
Ahhhh. Why would you continue to use RAM that you knew caused BSODs? Also, I can see that the four RAM sticks all have the same part number, which is good, but if they weren't bought as a pack of matched sticks then that's a worry.

It is perfectly true that RAM with the same part number should be fully compatible with one another, but buying RAM in a pack of matched sticks guarantees they will be compatible. In addition, that RAM that you have (Corsair CMH32GX4M2Z3600C18) is not on the QVL for your CPU and motherboard. That doesn't mean that it won't work of course, but when you're getting BSODs that may be RAM related that does become a concern.

See how it is on just the two newer sticks.
 
ubuysa said:
Ahhhh. Why would you continue to use RAM that you knew caused BSODs? Also, I can see that the four RAM sticks all have the same part number, which is good, but if they weren't bought as a pack of matched sticks then that's a worry.

It is perfectly true that RAM with the same part number should be fully compatible with one another, but buying RAM in a pack of matched sticks guarantees they will be compatible. In addition, that RAM that you have (Corsair CMH32GX4M2Z3600C18) is not on the QVL for your CPU and motherboard. That doesn't mean that it won't work of course, but when you're getting BSODs that may be RAM related that does become a concern.

See how it is on just the two newer sticks.
Click to expand...

Because I wasn't, and still am not , certain the sticks is the problem but its now time to isolate them.

Also have been using my first two dimms for years without any issues whatsoever so perhaps one of them went bad in 2024? They weren't bought as a pack of matched sticks.

I'll stick with the newer ones for a bit and see how things go. Next step would be a new installation of Windows 11 to rule out any drivers issues unless you have another recommendation.
 
With my newer DIMMS on I just got a new BSOD "Hypervisor_error". Event viewer gives this message:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00020001 (0x0000000000000026, 0x0000000000000000, 0x00007ff988a054a6, 0x0000006d3aaff0b0). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 07dcacf5-b546-40d1-a742-f6481a192132.

Any clues? WhoCrashed is showing this: https://ibb.co/hWtFcwp minidump: https://file.io/XmjPZj398Eva

In addition more of the same machine check exceptions errors and subsequent blue screens so it cannot be my RAM at this stage as its been replaced. Could it be a failing CPU regardless of it passing Prime95?

I think its time to do a clean installation of Win11
 
Last edited:
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom