ASRock.com Homepage
Forum Home Forum Home > OverClocking(OC) Zone > OC Technical Discussion
  New Posts New Posts RSS Feed - memory integrity
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

memory integrity

 Post Reply Post Reply Page  <1 678
Author
Message
katPHish View Drop Down
Newbie
Newbie
Avatar

Joined: 16 Jul 2020
Location: USA
Status: Offline
Points: 15
Post Options Post Options   Thanks (0) Thanks(0)   Quote katPHish Quote  Post ReplyReply Direct Link To This Post Posted: 23 Aug 2024 at 5:54am
ASRock B560M-C (bios 1.80)
ASRock Polychrome RGB 2.0.182 <- works!
ASRock Motherboard Utility(v3.0.503) <- works!
Back to Top
dominicc View Drop Down
Newbie
Newbie


Joined: 16 Oct 2020
Status: Offline
Points: 141
Post Options Post Options   Thanks (0) Thanks(0)   Quote dominicc Quote  Post ReplyReply Direct Link To This Post Posted: 23 Aug 2024 at 6:28pm
Still doesn't work for me.

A workaround is to disable 'SVM mode' in the BIOS, but obviously this will result in a less secure system. This disables windows' ability to use core isolation and will allow the bad driver to run again.
Back to Top
Sandman192 View Drop Down
Newbie
Newbie
Avatar

Joined: 29 Jul 2023
Location: Oklahoma
Status: Offline
Points: 90
Post Options Post Options   Thanks (0) Thanks(0)   Quote Sandman192 Quote  Post ReplyReply Direct Link To This Post Posted: 28 Aug 2024 at 6:26am
I just want Microsoft or ASROCK to find a way to install drivers normally with out going through the hoops of installing.

Why should we be the tech support of are computers of a company that broke it in the first place? Give us bad software that broke something that was working fine to begin with. Microsoft...
Back to Top
robeat View Drop Down
Newbie
Newbie
Avatar

Joined: 29 Aug 2024
Status: Offline
Points: 15
Post Options Post Options   Thanks (0) Thanks(0)   Quote robeat Quote  Post ReplyReply Direct Link To This Post Posted: 29 Aug 2024 at 2:29am
I had the same issue AsrDrv106 cannot load on my X670E Taichi Carrara, since sometime in August 2024.

In my case, all that was needed was to head to the support page of my motherboard and download the latest Beta for "ASRock Motherboard Utility", which it turns out is the A-Tuning Utility. I didn't uninstall the old version before installation, and it seems to correctly have detected my previous install, updated it, and even preserved my custom fan curves. After installation, it prompted me to restart, and on that boot, I no longer got any AsrDrv106 errors.

I'm happy with this solution, but be aware this is a Beta. You could also try uninstalling A-Tuning, but the Beta seems to work fine in my case and allows me to retain fan tuning.

This is the full description of the download that fixed it for me:

[Beta] ASRock Motherboard Utility ver:4.1.7 Windows® 11 64bit 63.4MB 2024/7/30 Global Download
Back to Top
LordStardust View Drop Down
Newbie
Newbie
Avatar

Joined: 12 Sep 2024
Status: Offline
Points: 15
Post Options Post Options   Thanks (0) Thanks(0)   Quote LordStardust Quote  Post ReplyReply Direct Link To This Post Posted: 12 Sep 2024 at 11:23pm
Originally posted by katPHish katPHish wrote:

ASRock B560M-C (bios 1.80)
ASRock Polychrome RGB 2.0.182 <- works!
ASRock Motherboard Utility(v3.0.503) <- works!


I have a ASROCK X670E TAICHI motherboard and confirm that the above solution works for me too.

P.S. I only registered for this forum in an effort to 'give back' to this community in hopes that this post helps others.
Back to Top
spartaner99 View Drop Down
Newbie
Newbie
Avatar

Joined: 25 Nov 2024
Location: Landshut
Status: Offline
Points: 30
Post Options Post Options   Thanks (0) Thanks(0)   Quote spartaner99 Quote  Post ReplyReply Direct Link To This Post Posted: 25 Nov 2024 at 4:06am
Die Datei AsrDrv202.sys befindet sich in dem Verzeichnis. Die Datei ist auf dem neuesten Stand und ist von ASRock Orginal. Beim Start der Software ASRock A-Tuning erscheint bluescreen mit der Meldung System_service_exeption AsrDrv202.sys. Ein crash.dmp wird seltsamerweise nicht geschrieben. "WhoCrashed" findet nichts. Die Datei wurde wie empfohlen im abgesicherten Modus umbenannt. Wird aber vom betriebssystem automatsich sofoert wieder erstellt. Wie sol lweiter vorgegangen werdfen um das Problem einzugrenzen und zu lösen ?
Vermutlich ist es das neue Windows x86 Sicherheitsupdate vomn 22.11.24
Soll man es Microsoft oder ASRock melden ?
Weiss
Back to Top
spartaner99 View Drop Down
Newbie
Newbie
Avatar

Joined: 25 Nov 2024
Location: Landshut
Status: Offline
Points: 30
Post Options Post Options   Thanks (0) Thanks(0)   Quote spartaner99 Quote  Post ReplyReply Direct Link To This Post Posted: 25 Nov 2024 at 4:08am
Die neue Datei AsrDrv202.sys befindet sich in dem Verzeichnis. Die Datei ist auf dem neuesten Stand und ist von ASRock Orginal. Beim Start der Software ASRock A-Tuning erscheint bluescreen mit der Meldung System_service_exeption AsrDrv202.sys. Ein crash.dmp wird seltsamerweise nicht geschrieben. "WhoCrashed" findet nichts. Die Datei wurde wie empfohlen im abgesicherten Modus umbenannt. Wird aber vom betriebssystem automatsich sofoert wieder erstellt. Wie sol lweiter vorgegangen werdfen um das Problem einzugrenzen und zu lösen ?
Vermutlich ist es das neue Windows Sicherheitsupdate vom 22.11.24
Weiss
Back to Top
 Post Reply Post Reply Page  <1 678
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.052 seconds.