Jump to content
AIDA64 Discussion Forum
jjxaker

MSI Z270 Gaming M7 (MS-7A57) problems

Recommended Posts

Hello!

Bug reading vcore, It displays an incorrect value.

I wanted to create a aida64 full report, but in reading SMBus dump(full) my system herself shuts down. but this is clearly a problem of the aida64...

isasensordump.txt

Share this post


Link to post
Share on other sites

We follow MSI's recommendations on how to handle the sensor registers on MSI Z270 motherboards.  What exactly is the issue about the Vcore?  Does MSI's own monitoring software measure a different value or the same value?

Share this post


Link to post
Share on other sites

any other software reads correctly... in the BIOS manually voltage 1.360

vcore.jpg

PS. lacks +3 V

the same problem with the ASUS PRIME Z270-K

cpu vid read exactly what is needed!:blink: cpu core voltage 1.144 It shows the nonsense.

vid.jpg

Share this post


Link to post
Share on other sites

Please use MSI's own software as a reference on MSI motherboards, and Asus' own software as a reference on Asus motherboards.  We'll add CPU VID voltage below the CPU Vcore reading to the Sensor page as well, so you can see both values listed.

Share this post


Link to post
Share on other sites
3 hours ago, Fiery said:

Please use MSI's own software as a reference on MSI motherboards

Software and utility from manufacturers always been crap, how to use them! it is for housewives))) but monitoring is working properly.

Bezymiannyi.jpg

Share this post


Link to post
Share on other sites

We've contacted MSI to find out what causes the discrepancies between the information they've provided us, and the way their own monitoring software works.

Meanwhile, we've added the missing +3.3V reading in the latest beta version of AIDA64 Extreme available at:

https://www.aida64.com/downloads/latesta64xebeta

After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
 

Share this post


Link to post
Share on other sites

Thank you, I hope you and MSI will find the truth with.

Temporarily, and so will come down, true looks CPU VID of reading more than vCore:ph34r:

Bezymiannyi.jpg

 

Share this post


Link to post
Share on other sites

It seems on your particular motherboard model the Vcore reading has to be multiplied by 1.2.  We'll implement that in the next AIDA64 beta update ;)

Share this post


Link to post
Share on other sites

Since they both will be displayed on the Sensor page, I don't think we need to replace anything :) Whichever you don't like, just ignore it ;)

Share this post


Link to post
Share on other sites

Thank you! new beta 5.80.4084 solved the problem of monitoring the voltage.

I have a question about Cache & Memory Benchmark, incorrectly displays the frequency North Bridge Clock. but this problem has long.

cachemem.png

Bezymiannyi.jpg

 

 

Share this post


Link to post
Share on other sites

In case the north bridge clock fluctuates, it's normal that sometimes AIDA64 cannot capture the highest value in the power states.  Or is it consistently lower on the Cache & Memory Benchmark panel than the value displayed on the Overclock page?

Share this post


Link to post
Share on other sites

I'm afraid we have no idea what could work incorrectly about the NB clock measurement. How do you know it's an issue limited to MSI motherboards?

As for the SPD issue, for some reason your memory modules cannot perform SPD bank switching. Bank switching is necessary to read the full 512-byte SPD block of DDR4 memory modules.  Can you please check if CPU-Z is also affected?

Share this post


Link to post
Share on other sites
4 hours ago, Fiery said:

How do you know it's an issue limited to MSI motherboards?

There are no problems NB clock with Asus Z170/Z270,  in contrast to MSI Z170/Z270 Series...

I tried the boards MSI Z170 Gaming M3/M5/M7/M9 and Z270 Gaming M5/M7 with all of them the frequency of the north bridge is read incorrectly.

4 hours ago, Fiery said:

As for the SPD issue, for some reason your memory modules cannot perform SPD bank switching. Bank switching is necessary to read the full 512-byte SPD block of DDR4 memory modules. 

This may be the problem due to bios? I pulled out the video card(EVGA GTX 1070 FTW) and the problem disappeared.  At least I can not reproduce the situation with the problem...

Bezymiannyi.jpg

ps. But is it right that it is indicated that there is not present thermal sensor? Because it is available, Giantec GT34TS04

CPU-Z when there was a problem not always read the data SPD...  Now for now everything is fine <_<

Share this post


Link to post
Share on other sites

The difference between how NB clock is measured on the Overclock page vs. on the Cache & Memory Benchmark panel, is that the latter will disable the power management facilities (namely EIST a.k.a. SpeedStep and C1E a.k.a. Enhanced Halt State) of the CPU before measuring the clock speeds.  Maybe MSI motherboards alter the behavior of the NB, ie. adjust its operating frequency in a proprietary way when those power management features are disabled?

As for the SPD bank switching issue, it looks a lot like a BIOS issue.

Share this post


Link to post
Share on other sites
24 minutes ago, Fiery said:

Maybe MSI motherboards alter the behavior of the NB, ie. adjust its operating frequency in a proprietary way when those power management features are disabled?

EIST disabling It helps. But this is a bad way out of the situation)))

eist_off.png

Miracles are what by the way vid and vcore equaled after turning EIST off :huh:

Bezymiannyi.jpg

Share this post


Link to post
Share on other sites

Unfortunately they communicate with them is difficult...

I can not even Make the SMBus dump(Full), the system itself turns off :(

Share this post


Link to post
Share on other sites
23 minutes ago, jjxaker said:

Unfortunately they communicate with them is difficult...

I can not even Make the SMBus dump(Full), the system itself turns off :(

If you could check what's the device that's scanned when the system turns off, we can filter that device out.  Previous MSI boards with Z170 and X99 chipset are sensitive for scanning at device 21h, 22h and 23h, so we skip those devices there.  We haven't received any guidelines from MSI about Z270 boards, so we somehow have to discover if there are sensitive devices there too ;)

Share this post


Link to post
Share on other sites

I've sent you an email about the SMBus issue.

As for the benchmark reference results setting, that's exactly how it should work.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...