PC Processors

[ardankyaosen]

Some months back, I switched from an Asus X570 motherboard to a Gigabyte B550 motherboard and the SCEP Certification Errors I'd been getting constantly went away.  Today, I updated to the latest Windows 11 version (22H2 - Build 22621.521), and they're back.  Once again, I'm getting Event 86 Errors:

Log Name: Application
Source: Microsoft-Windows-CertificateServicesClient-CertEnroll
Date: 9/21/2022 5:23:49 PM
Event ID: 86
Task Category: None
Level: Error
Keywords: Classic
User: SYSTEM
Description:
SCEP Certificate enrollment initialization for Local system via https://AMD-KeyId-578c545f796951421221a4a578acdb5f682f89c8.microsoftaik.azure.net/templates/Aik/scep failed:

GetCACaps

Method: GET(0ms)
Stage: GetCACaps
The server name or address could not be resolved 0x80072ee7 (WinHttp: 12007 ERROR_WINHTTP_NAME_NOT_RESOLVED)
Event Xml (could not include because your fine forum software won't allow it).

and

Log Name: Application
Source: Microsoft-Windows-CertificateServicesClient-CertEnroll
Date: 9/21/2022 5:23:49 PM
Event ID: 86
Task Category: None
Level: Error
Keywords: Classic
User: SYSTEM
Description:
SCEP Certificate enrollment initialization for WORKGROUP\DAVESWIN11$ via https://AMD-KeyId-578c545f796951421221a4a578acdb5f682f89c8.microsoftaik.azure.net/templates/Aik/scep failed:

GetCACaps

Method: GET(16ms)
Stage: GetCACaps
The server name or address could not be resolved 0x80072ee7 (WinHttp: 12007 ERROR_WINHTTP_NAME_NOT_RESOLVED)
Event Xml (ditto):

From what I've been able to find over the months (year?) that this has been happening without anyone from AMD or Microsoft giving a ...care, this is because the address of the AMD's certificate server is wrong in Windows.  For Pete's sake, fix this.  It's a security certificate, not a penny.

[brkeudunman]

I have updated all my drivers, includes nvidia, but still error occurs. I'm using W11, Asus FA506IV. I can not disable TPM because the bios does not have any option for TPM. Any recommendation ?

[brkeudunman]

For the logging :

• I closed the fast boot, didnt solve
• I have cleared tpm with tpm.msc, waiting/ Didnt solve either

[brkeudunman]

After a while I've noticed that, whenever the computer is plugged in, the problem occurs after every 10 or 20 min. Gotta research more.

No, even if it does not plugged in, the problem occurs

[Siding4915]

i have a FA506II had the same issue... Did you download the drivers from ASUS or AMD & Nvidia ? i recommend you backup things and then go back to Windows 10 and then upgrade all the drivers from AMD & Nvidia and so on and then see if issue stays... then you can disable TPM but not in BIOS but you can disable it with this: https://xtreh.ru/d/98582-tpm-off-uninstall-method-for-asus-laptop-users

Or from Reddit: https://www.reddit.com/r/ASUSROG/comments/zspy65/cant_disable_tpm_on_asus_rog_zephyrus_m16_g503zw/j5...

Hopefully this works for you please make a backup of your data in case this goes wrong! 

[brkeudunman]

I downloaded from Windows Update, then if they are mismatch I installed from ASUS`s drivers section. Now I`m gonna apply your instructions. Hopefully this works!

[goodplay]

MS released this to insider build some months ago,

  Might make it to RTM in the next annual update?

[brkeudunman]

I have applied to the insider program right now (Beta Channel). I will update the post after a test.

[ardankyaosen]

Yep.  I installed that back on 22 March 2023.  It didn't help.  Here's the Microsoft Feedback Hub item I reported to Microsoft (with nothing but an acknowledgement that they received it):

https://aka.ms/AAm27ha 

[Siding4915]

I'm reporting back just had 2 back to back crashes again black screen and then i check event viewer and i see SCEP errors are back on startup... I have celebrated prematurely.... sad.... So it seems like i will be buying a new PC now definitely going back with Intel & Nvidia lol.

[brkeudunman]

same

[brkeudunman]

I have closed the TPM. Waiting for the new crisis..

[EdgeHurd]

Updating after two weeks into using my new 5800X - no crashes, no SCEP failed.  I believe the issue was my RAM frequency of 2800MHz pairing with the old 1700X CPU. To get that to work, I should've been using 2666MHz, but it doesn't matter now with the 5800X. Using DOCP with 3200MHz and it's been fine.

[Vertibird]

Hello, its 01.10.2023 and problem is still there! AMD why are you not fixing this already? 

My specs: Motherboard: Msi b450 m2 pro max, Cpu: R5 5600, GPU: Rx 6800, 2x16 gb ram at 3600mhz.

I have windows 11 with latest update. I have the exact authority doesnt exist problem. I have no reboots, can play games normally. My problem is everytime I reboot, radeon is restored to default due to system failure. I updated bios, chipset, gpu drivers. I also disabled TPM from BIOS, deleted windows TPM files but problem still exists. I have to reload my radeon OC settings everytime I reboot my computer.

For my last 3 pc build, I am completely using AMD products. But AMD not trying to fix this is ridiculous. I am getting disappointed.

[chikkidog]

My computer just froze, had no option to power off by holding the power button in. Issue went away for the last two weeks now back. Getting the same - SCEP Certificate enrollment initialization events. Looks like a new computer if this is not fixed soon.

[ariely99]

Well, this is not really a solution, but I did have several crashes (around 5-6!) every day, so I had to do something about it; otherwise, my PC was completely useless.

What I did was:

1. Uninstalling AMD Software Adrenalin using the "AMD Cleanup Utility."
2. Updating Windows - which didn't fix the problem directly - but it did update my GPU (Radeon RX 6650 XT) driver to version 31.0.12027.7000 (dated 20.10.22).

It's been a day, and so far, no crashes. I know this is not ideal for long-term performance and compatibility as I'm not using the latest GPU driver, but I prefer to have a functioning PC at this point.

[notsatisfiedwithAMD]

Hello, writing here after a few months, i changed out my old ryzen 2600 to a 5800x3d and didn't have any problems since. My guess it was either the older cpu or maybe the ram frequency. Cheers

[Mailman]

Win 10 Enterprise was crashing daily, and diagnoses showed the boot device, an NVME 2TB SSD was going bad, it was only a year old, but the system board and CPU were five years old and no longer actively supported by the manufacture having been replaced newer models. I bought a replacement SSD and installed without removing the intermittently failing SSD. Restored the OS to the new device from a backup, and brought up the OS, but got a Disk Signature Collision error, even though the both devices came from different vendors. That fix was simple, simply deleted all the old partitions on the failing device, but that is when I noticed this error. Nothing I’ve tried has worked and I’ve spent 3 days on it. What I wanted to contribute to this thread is a notice I read from MS about four months ago while solving other HW problems. The notice essentially said that MS would no longer offer support for any OS when the HW platform it was running on, was not a currently supported HW platform by the manufacture, or something along those lines. More specifically it said, if the HW was not “current and fully supported” by the manufacture, then MS makes no claims regarding the reliability of any OS on that HW. It went on to give some date ranges as examples that made it quite clear that if the HW is replaced by something newer and is older than 3-5 years, your just SOL. No help from MS. The only solution they offered was, upgrade to a newer version of the OS but that doesn't really solve and aging HW problem now does it. So, if a single component goes bad, a drive for example, and the new drive works in your system, but your system is no longer actively supported by the manufacture, and there's some kind of conflict between the system and the new HW you just bought, don’t call MS cause they won’t help, instead by a new computer… Totally FU….

[ganesh23]

I was finally able to fix this messy problem of EVENT ID 86. This fix has nothing to do with MICROSOFT servers and AMD fTPM. The error pops up because your CPU is struggling and beyond a certain percentage usage it will give up. System will restart either randomly when it is in the idle state or instantly when you run some apps or games which utilize 60-70% cpu during the start. 
I was getting this problem when I was trying to play online multiplayer games on steam. Ex- Apex legends or Rainbow Six Siege. (I was able to play offline mode games initially like "shadow of the tomb raider"). My pc always froze in the menu of the games and restarted everytime I launched the game. 
I did every possible thing (software wise) to sort this out. The following I tried:-

1. I reinstalled the games

2. I reinstalled the steam

3. I disabled the fTPM module in BIOS

4. I updated the BIOS to the latest version

5. I removed the RAM, cleaned the slots , reinserted the RAM

6. I updated/ Reinstalled the chipset drivers. Even the GPU.

7. I reverted back to windows 10 ( was on windows 11 pro) with fTPM disabled. But still got the same error and same freezing/restarting

Not a single thing above helped. Because the problem lied somewhere else entirely. When on 15th may 2024, after trying everything, I tried to play "Shadow of the tomb raider". It froze just like APEX LEGEND and gave me BSOD. Thereafter it restarted itself. It was then that hit me. Either my cpu is CHOKING or my connections are lose somewhere inside. And boy oh boy, I was **bleep** right! 
Yesterday I disassembled my entire cabinet. Disconnected every cable on the motherboard. Removed the gpu, NVMEs, Rams . When I was removing the HEAT SINK over the CPU , I found my CPU to be stuck to the Heat Sink. Thermal paste was long gone. 
So now I was sure my CPU was overheating while launching CPU intensive apps. It was a matter of couple of months before it would start freezing in idle state. I used a hair dryer and gently seperated the HEAT SINK and CPU. Cleaned the old thermal paste using alcohol. Cleaned the dust on the motherboard with a new/unused artist brush. I even removed the dust from the fan of HEAT SINK. 
After all the cleaning , I applied the new thermal paste properly on the cpu and re fit all the components on the motherboard. This time I ensured all the cable connections are tight and nothing is lose. Even after completing the hardware installations, I was skeptic. I wasn't sure that it will work. I connected the power cord, Hdmi cable, keyboard and mouse. I switched it on. And I ran into an error in the boot menu screen. b1 initialize library failed 0xc0000001. 

I thought I wrecked my PC. I searched it on google and someone pointed out that it happens whenever the motherboard is reset. Solution was to remove the CMOS battery for 20-30 seconds and reinsert it. 
I was good to go. System booted up. Reached the home screen.

Quickly launched every game installed on my steam account. And My miseries were gone. Finally no more freezing and restarting. System is good as new before. On event viewer I no longer get EVENT ID - 86. I think it does happen whenever the system is restarting because of the CPU failure.

For people who made it worked by replacing the CPU entirely, I think they should have disassembled, cleaned, applied new thermal paste and reassembled the entire components first ensuring tight connections. Of course new CPU will fix the problem, because it is new. It won't fail up on heating cause the heat sink will work properly on it. But same is not the case with 6months 8months or 1 year old systems. Old systems are riddled with dust and dried thermal paste. CPU failure are bound to happen.  

If you are facing such a problem, do this before throwing your system and buying a new one. I hope it helps whoever is getting the problem of system freeze. 
SCEP certification authentication failure has nothing to do with your system freeze. Its just a report generated following your CPU failure. 

I was cursing AMD and MICROSOFT all this time when the problem was poor maintenance on my side. I live in tropical region where temperature in summers go higher and there is a lot of dust around. 
Kindly try the solution before completely giving up.

[falloutboy]

This is not a fix for an SECP error "b1 initialize library failed 0xc0000001" is related to either CMOS becoming corrupted, BIOS being updated causing a loss of all CMOS settings in some instances a M.2 NvME not being inserted properly or having a dirty connection, in rarer cases a dead NvME and in an indeterminate number of cases a bad CMOS battery.

Cleaning and re seating the NvME is appropriate. I would have checked if the issue was resolved at that point before removing the CMOS battery as a boot detect may have sorted it at this point. If it hadn't then you would remove the CMOS battery, or alternately powered down the whole system, removed the power plug and pressed the CMOS reset button on the back of the chassis IO area ( if you have one )

Your system "freeze" would have been related to this as it's a hardware issue.

I don't think this issue was related and the fact that the other errors were occurring was coincidental.

If you were also having CPU issues however this could contribute as unless you have a discrete TPM your TPM is built into your AMD CPU, if that was having problems for whatever reason it could certainly cause issues with TPM.. In this instance it's entirely possible that those issues were caused by the problems you were having with your hardware.

[Equal]

Figured out a fix on my end after doing everything you've been trying over the last 2 years. It was as simple as my RAM staying at an overclocked rate. It was set to 3200MHz when it can only handle 2400. Please anyone who's having these freezes, please check in your bios and make sure the ram is set correctly

[ariely99]

I was able to solve the problem as well. I was about to post here when I saw your message. You couldn't have explained the solution any better.

Since March, I've encountered this issue, especially when the CPU is under heavy load, and I've linked it to the "SCEP" error message. Additionally, I faced a new problem where the computer sometimes wouldn't turn on completely.

I suspected there was an issue with the contacts or loose connections. It then occurred to me that both issues might be related. I replaced my 10-year-old computer case with a new one (probably didn't need to replace the case, but I figured it was a good opportunity to do so), disassembled , cleaned and reassembled everything, and I haven't had any problems for the past two months.

[vincentm]

I found a fix that works for more than one day now. Let's hope it sticks. The solution is referred to somewhere here above in this thread. It put me on the track. I will lay out the steps.

It has to do with missing certificates. That is logic seeing the error messages involved. It is a TPM issue. Microsoft has a list of these certificates. This is weird in itself: why are these no part in the frequent system updates?

Anywayz...this is the page:

https://learn.microsoft.com/en-us/windows-server/security/guarded-fabric-shielded-vm/guarded-fabric-...

And on that page follow steps to take:

Step 1. Download the latest package from (at the moment of this writing) https://go.microsoft.com/fwlink/?linkid=2097925

And follow the rest of the explained steps in a powershell (as admin).

Step 5. Can be difficult since the current user has no authorization to run scripts. You can find the instructions here to temporarily change that: https://learn.microsoft.com/nl-nl/powershell/module/microsoft.powershell.core/about/about_execution_...

I have set 'Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope CurrentUser' and later changed that back from Bypass to Undefined.

Make sure you're working in the right directory, where you expanded the certificates. You can delete the folders you don't need. In my case, I removed all the dirs except for AMD and MS. It appeared to me that the missing certificates are in that Microsoft directory.

When step 5, the script has run, the missing certificates are installed. You even don't have to restart.

After updating BIOS, uninstalling and installing drivers, chaning everything around my Nvidia GPU, almost wrecking my machine, a state of desparation after ten days of which three fte are spent on this, computer freeze and brain freeze, becoming an uncertified Windows expert engineer, et cetera et cetera, this seems to be the solution. 

Hope it helps. Hope, it helps.

[vincentm]

And now a day later, I had the same trouble again. Looking at the Windows update history on my laptop, there has been an automatic update early this morning (KB5043076). And since I'm looking into that, the previous update was on  August 31, (KB5041587), exactly the day of the first occurances of these restarts and BSODs. The update before that, on August 15, (KB5042099), has not led to trouble.

So I have repeated the steps I described here above, assuming that the Windows update has erased the root certificates I installed earlier before.

I hope this is the case.

But if so, how weird would that be?? Microsoft presenting a list of root certificates that are not installed and even deinstalled at update time. And where can you drop this issue, I mean, at a point were they actually care... the feedback hub?

[vincentm]

It is not the solution, it seems. I found it ackward since it's intended for servers of which I doubt it is connected to Windows 11. But it had effect.

Only, after a new Windows update the errors came back.

Rolling back to the update before August 31 is not possible, that was an update that can't be reversed for some reason.

It is in the software of Microsoft and/or AMD. My hardware is checked and fine. Also, since it occurs on new machine as well (as I read) it shouldn't be the case of hardware failure. Buying a new machine is not the solution. Or maybe when it's Intel. Or Apple

The system dumps show different errors all the time. The only message involved each time when there is a restart/BSOD, is the 404 on the certificate.

What's next...? Perhaps a bigger roll back on my machine.

[ardankyaosen]

I've sent actual bug reports to both AMD and feedback on Microsoft's Feedback Hub.  Completely worthless.  Personally, I think Microsoft hates AMD and doesn't care if they sabotage them.  But, there's still no excuse for AMD's total silence on this for years.

[Siding4915]

I am guessing AMD have bigger fish to fry. My laptop still gets this event 86 thing but at least it no longer bluescreens & randomly shuts off. Personally i think this event 86 thing is a side effect of some other issue for me & another guy the fix was disabling turbo boost with windows power plan.

[Siding4915]

Hello i wanted to do an update on my situation and how i fixed it...

The error still shows up in the event viewer but hey at least the PC doesn't crash or blue screen.

Apparently in my case it had something to do with turbo boost getting enabled and then crashing me into a blue screen that's why it had happened randomly... apparently on older CPUs turbo boost becomes a problem no idea... that's what I've found so the event 86 thing is still visible but the laptop works fine i mean okay it's got lower performance but it works so before you do anything system restore point of course and backup your important files in case anything goes wrong... So before we do this what this is it will enable a hidden power option and that will disable your CPU for turbo boosting which apparently causes the blue screens (i know that's a weird fix but hey it works!) just follow the steps:

Step 1:

open Powershell (windows key + s, search for powershell and right click Powershell and select open as admin) and paste the following command:  (if you are doing this first time make sure to use the enable command - i've added the disable command because you might need it if you want to disable this hidden power option from being visible - if this works you won't need to disable it leave it be as it is).

To Enable:

Spoiler

Set-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7\ -Name attributes -Value 2

To Disable: (remember if you do this first time use the enable command only not this one)

Spoiler

Set-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7\ -Name attributes -Value 1

Step 2:

After we do this we need to navigate to edit plan settings so lets go press windows key + s and type in edit power plan and then click on the first result now it opens up a window and you will see bottom left something called "Change advanced power settings" click that and then power options window opens then we expand the following menu: "Processor power management" after that you will see at the bottom a new power option called "Processor performance boost mode" now the final step is to simply disable this from the drop down menu and voila this worked for me laptop is usable ok it has lower performance but it does not blue screen. 

I recommend restarting after this just to be sure the setting gets applied. (if you reinstall windows fully you have to redo this process again so don't forget this!)

Let me know if this will work for you it's worth a shot if you tried everything else!

ALSO if you are not happy with using powershell for this here's the manual method using Registry editor (if you already used the method with powershell you can disregard this):
Using Registry Editor, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 and select Attributes. Modify the value of "Attributes" from 1 to 2. Data should read “0x00000002 (2)”.

[vincentm]

I'll try that one when my latest solution (see below) fails.

[Siding4915]

Great. Hopefully either mine or your fix works for you.

[vincentm]

New possible solution. Multiple people with the same or comparable systems, appear to have issues with their Dolby Atmos software. I came to investigate that, since I noticed that literally every time the certificate error occurs, it is proceeded by a DAX3API action. Clicking the details of that action, it appears to have an error, but this message lies a bit hidden.

Here is how you can remove that software from your system (and fix it with a new one if you like):

https://www.reddit.com/r/pcmasterrace/comments/qcx3fa/i_have_an_issue_with_a_windows_file_named/

(Note 1: in my case the error message does not hold the filepath. Bu tyou can easily follow it and find the folder that you have to delete.

Note 2: I removed the Dolby App first.)

I have my fingers crossed once again.

[vincentm]

Now I'm rather definite about the solution, at my side at least. Again

Just connect to the router with a cable. Because my WiFi driver fails. And that is a common issue if you Google it.

In my case it's a rather old version of driver Intel(R) Wi-Fi AX200 160MHz. Version 22.80.0.9 date 19-8-2021. But I see people with newer versions also complaining. It is not easy to upgrade this one either, and I want to be sure first, so, that's why I plug in the cable.

I haven't checked the feedback hub yet. And we must blame the Intel-MS combination it seems, not AMD. It's a chain of events.

So I'll wait a few more days to be sure and then I'll drop, hopefully, a confirmation here.

[Siding4915]

I am hopeful that this will work for you its much better than my solution i guess but if not try my solution and let us know if it will work out my laptop seems to work now with my solution applied another guy tried it and it works for him too so idk i am guessing it will work on desktop PCs too no idea. Hopefully it works for someone that's why i shared it lol but it was frustrating as hell to debug this issue kind of a shame no one addresses this we are just aimlessly wondering around and trying everything to fix this by ourselves.