ASRock.com Homepage
Forum Home Forum Home > Technical Support > Intel Motherboards
  New Posts New Posts RSS Feed - (Solved)PGX Z390 BIOS Bug Issue
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

(Solved)PGX Z390 BIOS Bug Issue

 Post Reply Post Reply Page  12>
Author
Message
kiberman545 View Drop Down
Newbie
Newbie


Joined: 10 Nov 2019
Location: Russia
Status: Offline
Points: 17
Post Options Post Options   Thanks (0) Thanks(0)   Quote kiberman545 Quote  Post ReplyReply Direct Link To This Post Topic: (Solved)PGX Z390 BIOS Bug Issue
    Posted: 11 Feb 2020 at 7:40pm


Chеck Auto value



Set up manual value like was in auto mode,or any other- doesnt matter



Save and restart



Check value again



Changing back to AUTO



What is this?)))).

Bios 1.20 Official - motherboard pgx z390.

I'll did two posts to Support Asrock_TSD@asrock.com.tw using support form, and NO ANSWER-JUST SILENT MORE THAN MONTH.

How can buy Asrock products in the future, if Support do not answer technical questions. It?�s better then to buy a competitor board, next time.   


Edited by ASRock_TSD - 17 Apr 2020 at 9:42am
Back to Top
RLGL View Drop Down
Senior Member
Senior Member
Avatar

Joined: 29 Jul 2018
Location: MN
Status: Offline
Points: 2025
Post Options Post Options   Thanks (0) Thanks(0)   Quote RLGL Quote  Post ReplyReply Direct Link To This Post Posted: 11 Feb 2020 at 10:03pm
so, what is the question. DMI voltage should be about 1 volt, .0967 is close enough.
Asrock Z370 Gaming K6,Intel i7 8700K,
Asrock x570 Taichi

Back to Top
kiberman545 View Drop Down
Newbie
Newbie


Joined: 10 Nov 2019
Location: Russia
Status: Offline
Points: 17
Post Options Post Options   Thanks (0) Thanks(0)   Quote kiberman545 Quote  Post ReplyReply Direct Link To This Post Posted: 11 Feb 2020 at 10:43pm
dmi was an example.

I chose this field as safe, since the overstatement there is not large.

Here's another.

Is everything "all right" here?











Back to Top
kiberman545 View Drop Down
Newbie
Newbie


Joined: 10 Nov 2019
Location: Russia
Status: Offline
Points: 17
Post Options Post Options   Thanks (0) Thanks(0)   Quote kiberman545 Quote  Post ReplyReply Direct Link To This Post Posted: 12 Feb 2020 at 4:01pm
and silence, no answer) - "wonderful".
Back to Top
Xaltar View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 16 May 2015
Location: Europe
Status: Offline
Points: 25028
Post Options Post Options   Thanks (0) Thanks(0)   Quote Xaltar Quote  Post ReplyReply Direct Link To This Post Posted: 12 Feb 2020 at 4:23pm
This is a community forum, not a branch of ASRock Tech Support. If you want support
from ASRock you will need to submit a support ticket:
https://event.asrock.com/tsd.asp

When a community member has a solution or workaround they will typically do their
best to help but technical issues like this can only really be addressed by ASRock
Tech Support directly. As a moderator I do my best to help users here where I can
but I do not speak for ASRock, I am a community moderator not Tech Support.

Please bare all this in mind when posting.
Back to Top
kiberman545 View Drop Down
Newbie
Newbie


Joined: 10 Nov 2019
Location: Russia
Status: Offline
Points: 17
Post Options Post Options   Thanks (0) Thanks(0)   Quote kiberman545 Quote  Post ReplyReply Direct Link To This Post Posted: 12 Feb 2020 at 5:24pm
Thank you i understand but - i did two post to https://event.asrock.com/tsd.asp

and no answer on this problem.

I do not think this damage of board, because work smooth and very well more than 3 month now- with high load. Great stability.

I will wait for a response from the users of the same board.

Back to Top
Xaltar View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 16 May 2015
Location: Europe
Status: Offline
Points: 25028
Post Options Post Options   Thanks (0) Thanks(0)   Quote Xaltar Quote  Post ReplyReply Direct Link To This Post Posted: 12 Feb 2020 at 5:30pm
Tech support can take a while to respond, so long as you received a confirmation
email that your ticket has been received there is usually no need to send more
than one ticket.

The best thing to do with a voltage related bug is to check the voltage in OS using
a 3rd party monitoring app, more often than not the reported (high or low) voltage
reported in the BIOS is incorrect and the actual voltage is within spec when you
check in OS.
Back to Top
kiberman545 View Drop Down
Newbie
Newbie


Joined: 10 Nov 2019
Location: Russia
Status: Offline
Points: 17
Post Options Post Options   Thanks (0) Thanks(0)   Quote kiberman545 Quote  Post ReplyReply Direct Link To This Post Posted: 12 Feb 2020 at 8:43pm
"Tech support can take a while to respond"

1.5 Month enough time to response i think - )))))



This is a real overestimation - this is not about distorted or incorrect monitoring, because on the selected components, the PC rises in temperature by 10-15 degrees IN THIS CASE

- if there is a strong overestimation of voltage. There is no way to explain it.

If i choose PCH FIELD in bios do overvoltage BUG such method- 1.3-1.5V- see 70C - IN NORMAL MODE 1.05V--- 45-55C IN HIGH LOAD/

Do you really think that if it were just the testimony is not correct, I would write here)))))
Back to Top
kiberman545 View Drop Down
Newbie
Newbie


Joined: 10 Nov 2019
Location: Russia
Status: Offline
Points: 17
Post Options Post Options   Thanks (0) Thanks(0)   Quote kiberman545 Quote  Post ReplyReply Direct Link To This Post Posted: 12 Feb 2020 at 8:45pm
Add more - ALL GREAT IN FULL AUTO MODE OR FULLY MANUAL
Back to Top
Xaltar View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 16 May 2015
Location: Europe
Status: Offline
Points: 25028
Post Options Post Options   Thanks (0) Thanks(0)   Quote Xaltar Quote  Post ReplyReply Direct Link To This Post Posted: 12 Feb 2020 at 10:28pm
So probably an issue with the calibration algorithm. Thanks for the extra info.
Back to Top
 Post Reply Post Reply Page  12>
  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 4.203 seconds.