[bambidbl]

Hello,still getting some crashes,i ll send the dump file,the mtb log and speccy url.

Have a nice day

 

http://speccy.pirifo...ZDJMJziqdXETPCN

 

 

Attached Files

•  MTB.txt   5.96KB   64 downloads
•  052924-46421-01.zip   301.46KB   77 downloads

[Advertisements]

Thread moved to the more appropriate OS forums.

 

Couple of things there, one is new and the other looks to be something that got overlooked while pursuing your previous suspected hardware issues.

 

The first one is the Trusted Platform Module causing issues, make sure that it is enabled " how to " here

 

The second is more of an issue and looks to be something that we can do nothing about

 

BIOS

Brand: American Megatrends Inc.

Version: P8.01

Date: 01/30/2023

 

 

I`m afraid that you have a version of BIOS that was not meant to be used with the Pinnacle Ridge CPU that you have, this may explain why the issue is so random.

 

 

L8.01 2023/2/14 10.63MB Instant Flash Update AMD AM4 AGESA Combo V2 PI 1.2.0.8

*This BIOS doesn't support Bristol Ridge CPU, do NOT update this BIOS if Bristol Ridge CPU is being used.
**It requires to update BIOS to 7.00 before updating this version.
***ASRock do NOT recommend updating this BIOS if you are going to use Pinnacle, Raven or Summit Ridge CPU on your system.
**** User will not able to flash previous BIOS once upgrading to this BIOS version.

 

 

 

Check here and you will see that version 2.30 was the last safe version of BIOS to use with your particular range of CPU, see notes for version 3.30.

 

[phillpower2]

Thread moved to the more appropriate OS forums.

 

Couple of things there, one is new and the other looks to be something that got overlooked while pursuing your previous suspected hardware issues.

 

The first one is the Trusted Platform Module causing issues, make sure that it is enabled " how to " here

 

The second is more of an issue and looks to be something that we can do nothing about

 

BIOS

Brand: American Megatrends Inc.

Version: P8.01

Date: 01/30/2023

 

 

I`m afraid that you have a version of BIOS that was not meant to be used with the Pinnacle Ridge CPU that you have, this may explain why the issue is so random.

 

 

L8.01 2023/2/14 10.63MB Instant Flash Update AMD AM4 AGESA Combo V2 PI 1.2.0.8

*This BIOS doesn't support Bristol Ridge CPU, do NOT update this BIOS if Bristol Ridge CPU is being used.
**It requires to update BIOS to 7.00 before updating this version.
***ASRock do NOT recommend updating this BIOS if you are going to use Pinnacle, Raven or Summit Ridge CPU on your system.
**** User will not able to flash previous BIOS once upgrading to this BIOS version.

 

 

 

Check here and you will see that version 2.30 was the last safe version of BIOS to use with your particular range of CPU, see notes for version 3.30.

 

[bambidbl]

Hello,thanks for your fast reply,i had to update bios because of malware on it a few months earlier.
The version was recommended by a member of the malware removal forum so i just did it without looking.

Is there really not any way to get back to a previous version?
I wasnt planning on buying a new motherboard,and have no idea how to install a new one.

Have a nice day

Edited by bambidbl, 30 May 2024 - 10:36 AM.

[phillpower2]

As you have found since you first replied the BIOS update is irreversible.

 

As you were already having issues at the time it is quite possible that updating to the present version of BIOS is unrelated to these latest issues + as was advised in your last thread after you went 7 or more days with zero problems after carrying out our remedial work the problem/s look to be being caused by something that you are installing or something that you are running from another source such as an external storage device, this does not mean that you are doing something bad but instead having problems caused by an update or third party program that you use neither of which you can be blamed for doing.

 

Have you addressed the TPM as was suggested in my reply #2.

 

You are welcome btw 

[bambidbl]

Hello,yes,sorry i forgot to mention.I checked Trusted Platform Module and everything is the way it should be in the bios.

 

If it is related to an app or some hardware can i diagnose it in any way or not?

[phillpower2]

The TPM is the culprit, see info here for suggestions

[bambidbl]

ok i will get back to you in a bit.

Have a nice day

[phillpower2]

No rush on my behalf as I`m calling it a day now, been online since before 8am and it is gone 20.00hrs here in the UK.

 

Just to add, the below are your TPM issues,

 

 

Error: (05/24/2024 07:57:47 AM) (Source: CertEnroll) (EventID: 86) (User: AUTORITE NT)

Description: Event-ID 86

 

 

System errors:

=============

Error: (05/29/2024 03:43:52 PM) (Source: DCOM) (EventID: 10010) (User: DESKTOP-2UDSIP1)

Description: Event-ID 10010

 

Error: (05/29/2024 03:42:44 PM) (Source: BugCheck) (EventID: 1001) (User: )

Description: Event-ID 1001

 

Error: (05/29/2024 03:41:28 PM) (Source: Microsoft-Windows-TPM-WMI) (EventID: 1796) (User: AUTORITE NT)

Description: La mise à jour du démarrage sécurisé n’a pas pu mettre à jour une variable de démarrage sécurisé avec l'erreur -2147020471. Pour plus d'informations, veuillez consulter https://go.microsoft...?linkid=2169931

 

Error: (05/29/2024 03:40:26 PM) (Source: EventLog) (EventID: 6008) (User: )

Description: L’arrêt système précédant à 15:28:53 le ‎29/‎05/‎2024 n’était pas prévu.

 

Error: (05/29/2024 03:37:13 PM) (Source: DCOM) (EventID: 10010) (User: DESKTOP-2UDSIP1)

Description: Event-ID 10010

 

Error: (05/29/2024 03:29:28 PM) (Source: Microsoft-Windows-TPM-WMI) (EventID: 1796) (User: AUTORITE NT)

Description: La mise à jour du démarrage sécurisé n’a pas pu mettre à jour une variable de démarrage sécurisé avec l'erreur -2147020471. Pour plus d'informations, veuillez consulter https://go.microsoft...?linkid=2169931

 

Error: (05/29/2024 03:28:10 PM) (Source: volmgr) (EventID: 161) (User: )

Description: Échec de la création du fichier de l’image mémoire en raison d’une erreur lors de la création de cette image.

 

Error: (05/29/2024 03:28:53 PM) (Source: EventLog) (EventID: 6008) (User: )

Description: L’arrêt système précédant à 20:51:11 le ‎28/‎05/‎2024 n’était pas prévu.

 

Error: (05/29/2024 03:25:57 PM) (Source: Microsoft-Windows-TPM-WMI) (EventID: 1796) (User: AUTORITE NT)

Description: La mise à jour du démarrage sécurisé n’a pas pu mettre à jour une variable de démarrage sécurisé avec l'erreur -2147020471. Pour plus d'informations, veuillez consulter https://go.microsoft...?linkid=2169931

 

Error: (05/29/2024 03:25:00 PM) (Source: DCOM) (EventID: 10010) (User: DESKTOP-2UDSIP1)

Description: Event-ID 10010

 

[bambidbl]

Ok np I wasnt planning on asking for more today
have a nice night

[phillpower2]

Great, will check back tomorrow, good luck meanwhile 

[bambidbl]

Hello again,i did what the website was suggesting and i tried booting the computer a few times today.I believe the error is still here but i m sending a new MTB log for you because i dont really trust myself on that.

Have a nice day

Attached Files

•  MTB.txt   7.64KB   58 downloads

[bambidbl]

Got another crash just now,sending the dump and mtb

Attached Files

•  053124-51437-01.zip   436.17KB   81 downloads
•  MTB1.txt   7.35KB   59 downloads

[phillpower2]

Couple of things going on there, both that we have seen before in previous threads.

 

Are you running MTB in English.

 

When you did the recent reset of Windows did you reinstall the system drivers in the exact same order as in you first thead.

 

The driver responsible for the latest crash was storahci.sys have you recently installed or updated this driver, this would be after the seven days that you paused Windows updates.

[bambidbl]

Hello,mtb isnt running in English and I have no idea why.
I did reinstall the drivers the same way as the first time If I remember correctly.

I dont remember updating storahci.sys in any way.
I have already heard that this driver had problems on this computer,but I dont think anyone asked to update.

 

I also have some issues on windows update and other things but I put them in a new topic,ik it is deleted but if you need it I can provide information.

[phillpower2]

First thing we need to do is see if we can sort out Windows updates and then address the others one at a time, this may also resolve any bad or missing driver updates that are only available via Windows updates, the storahci.sys driver being one of them.

 

Please run the Windows update trouble shooter

 

 

Tip

If using a computer and not a mobile phone, please avoid adding multiple posts while waiting for us to reply to your last, edit your latest post to include anything that you wish to add, this will ensure nothing gets overlooked which can sometimes happen if a thread has more than one page, it also avoids filling up folks inbox.