Overclock.net banner
3,301 - 3,320 of 13,697 Posts
While waiting for something better, perhaps a few users could help me test a BIOS with an updated ACPI WMI interface that should fix the previous shortcomings. I only have a version for C7H Wi-Fi: http://www.mediafire.com/file/bj1e7tvzvypa9v8/ROG-CROSSHAIR-VII-HERO-WIFI-ASUS-0012.zip/file

Approved software versions:

- HWInfo v5.88 or later
- HWMonitor Beta: http://download.cpuid.com/betas/hwm_b17.zip
- SIV 5.32 or later

I will update with CPU-Z/AIDA64 versions that support this.

If you currently have any of the issues listed below, your feedback would be very valuable.

- Bad SIO temperature readings, things like CPU temperature reading crazy values or not updating anymore
- Fans permanently stopping or getting stuck at some percentage

I will give it a go.

Edit:
So far so good and HWiNFO now displays all the temp labels again. Instead of simply numbering the sensors.
 
While waiting for something better, perhaps a few users could help me test a BIOS with an updated ACPI WMI interface that should fix the previous shortcomings. I only have a version for C7H Wi-Fi: http://www.mediafire.com/file/bj1e7tvzvypa9v8/ROG-CROSSHAIR-VII-HERO-WIFI-ASUS-0012.zip/file

Approved software versions:

- HWInfo v5.88 or later
- HWMonitor Beta: http://download.cpuid.com/betas/hwm_b17.zip
- SIV 5.32 or later

I will update with CPU-Z/AIDA64 versions that support this.

If you currently have any of the issues listed below, your feedback would be very valuable.

- Bad SIO temperature readings, things like CPU temperature reading crazy values or not updating anymore
- Fans permanently stopping or getting stuck at some percentage
Currently testing BIOS 0012. Had none of those issues with BIOS 0804, and the trend continues with 0012. Had no issues with HWiNFO labels before and still working now.

No immediate issues in evidence. Same RAM tune works with same voltages. Preliminary short-duration stability checks passed -- will need a few days for the longer ones.
 
I reduced the max running temp of the memory modules by 2c by changing the monitoring point from CPU to VRM for the case fans and the memory fan.

It has irritated me, that when I run a memory test, I never get the desired fan response to keep my memory cool. This down to the fact I had all my fans running with regards to the temp of the CPU. This is fine if I run an IBT test and the CPU hits its max running temp, but a HCImemtest does not stress the CPU so the fans don't ramp up. The three feasible sensors are CPU, VRM and the PCH points. PCH barely moves even on an IBT run. But VRM hits 50c on full CPU load and 45c on full memory load. This is how my system monitors.

resting
CPU = 34
VRM = 37
Memory = 31

IBT load
CPU = 75
Vrm = 50
Memory = 34

Memory testing
CPU = 53
VRM = 45
Memory = 40

So moving the case and memory fans reaction point away from the CPU to the VRM made more sense to me. I set the case to full load at 50c on the VRM and memory to full load at 45c on the VRM. The result pulled the memory down to 38c. It isn't a huge deal, but just a tweak to get that extra mile.
Thanks for the response.
Literally, even with 1.45V, my RAM sticks are sitting at 42-45C.
Also with 1.45-1.46V, I can run up to 3600 with not bad timings.

Have either of you guys done testing to see how temps affect memory stability?

If so what did you find? what temps do you start to see instability?
 
Have either of you guys done testing to see how temps affect memory stability?

If so what did you find? what temps do you start to see instability?
For me it seems temps in the low 40*C will start to cause stability when I am at the tight end of timings or on the edge of a stable speed. If I have some wiggle room on the timings or the speed I can be in the 40*C range and not lose stability.
 
Greetings,

I just received this board today with my 2700X I just have a question I went back a couple of pages and couldn't find the info. I'm trying to locate PBO setting's on this board. Could someone point me towards it? Also how is this board working for you guys in terms of PBO, RAM stability and all just a general question since I have never owned an Asus board before everyone was telling me to try one and well now that I'm upgrading I decided to try it. Thanks.
 
Greetings,

I just received this board today with my 2700X I just have a question I went back a couple of pages and couldn't find the info. I'm trying to locate PBO setting's on this board. Could someone point me towards it? Also how is this board working for you guys in terms of PBO, RAM stability and all just a general question since I have never owned an Asus board before everyone was telling me to try one and well now that I'm upgrading I decided to try it. Thanks.
I would point you towards using Performance Enhancer Level 3 before I would recommend using PBO. But PBO is under Advanced and AMD CBS > NBIO I believe. Let me reboot and check again.
 
Specify the -NOWMI-LOCK SIV qualifier

For some reason i no longer have issues with either one of the listed programs. Can you specify exactly what we can do to replicate the issue?
With the 0702 BIOS I did not see no lockup issues, but with 0804 there were so we changed our code to interlock our ASUS WMI access with the Global\Access_EC + Global\Access_ISABUS.HTP.Method mutexes to both circumvent these and also interlock with old programs that fail to use ASUS WMI.

To see the issue with the 0804 BIOS run SIV (ideally 5.33 Beta-15 or later) with the -NOWMI-LOCK SIV qualifier (see [About]) and then one of the other utilities that report using ASUS WMI. After a while the sensors will stop being updated and the system will fail to cleanly shutdown.

Doing the same with the 0012 BIOS all was OK after over 7 hours of testing with SIV + HWiNFO + HWM + ASUSHW active. ASUSHW is an ASUS test program that does not use Global\Access_EC + Global\Access_ISABUS.HTP.Method, but I don't know if it's generally available, elmor should know.
 

Attachments

With the 0702 BIOS I did not see no lockup issues, but with 0804 there were so we changed our code to interlock our ASUS WMI access with the Global\Access_EC + Global\Access_ISABUS.HTP.Method mutexes to both circumvent these and also interlock with old programs that fail to use ASUS WMI.

To see the issue with the 0804 BIOS run SIV (ideally 5.33 Beta-15 or later) with the -NOWMI-LOCK SIV qualifier (see [About]) and then one of the other utilities that report using ASUS WMI. After a while the sensors will stop being updated and the system will fail to cleanly shutdown.

Doing the same with the 0012 BIOS all was OK after over 7 hours of testing with SIV + HWiNFO + HWM + ASUSHW active. ASUSHW is an ASUS test program that does not use Global\Access_EC + Global\Access_ISABUS.HTP.Method, but I don't know if it's generally available, elmor should know.
Thank you, that was very helpful!

There is a lot more with this 0804 BIOS than sensor and lockup problems. Overclock's are less stable, boot issues etc. but that's another story.


I will try later when i get home from the gym.

I also get this warning in event viewer: : "The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS."

They claim that its not related but it totally is.. When this error occurs the problem is there and when i no longer see this warning no fan or other stability issues.. Its right there that the BIOS is screwing the pwm signals up which is causing the fans to go haywire and Windows detect it.

On another note, not all people seem to be affected by it and have zero issues they claim. So it could also be that these IT sensor is not only extremely cheap (you can buy 10 of them for only 15 euro's) but also poorly made which means that with every 100 sensors you get several bad ones..?
 
Have either of you guys done testing to see how temps affect memory stability?

If so what did you find? what temps do you start to see instability?

1smus originally posted about adding fans helped stability early on the CH6. It was picked up again about 4 months ago in the forum. Adding fans can reduce temps down below 40c at full load. A few said that stability improved which allowed them to move on a memory strap to 3533. I still cant obtain 3533, but my temps were in the 40c's previously now they max at 39c on 3533 attempts.


I think some mentioned 42c at being the start of instability.
 
The devil is in the detail

I also get this warning in event viewer: : "The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS."

They claim that its not related but it totally is.. When this error occurs the problem is there and when i no longer see this warning no fan or other stability issues.. Its right there that the BIOS is screwing the pwm signals up which is causing the fans to go haywire and Windows detect it.
Provided all the reporting programs are using ASUS WMI then these should not happen and if they do then I suspect it's an issue with the ASUS WMI ACPI methods.

I can't find any of these on my C7H system, but then again all the EC access is now done via ASUS WMI. I suspect these only happened when AIDA64 + HWiNFO + SIV were doing direct EC access and when ASUS WMI is used this should no longer happen.

If you just run SIV 5.33 Beta-15 or later do you still get them? If so then we need to get ASUS to look into why. I can only sensibly comment when only SIV is active as I don't know exactly what other utilities do so you need to get their developers involved if you see them when their utilities are active.

Do you have any ASUS software active? Please post Menu->Help->Lock Usage + Menu->Help->Lock Handle so I can double check what is happening in terms of locking.
 
Provided all the reporting programs are using ASUS WMI then these should not happen and if they do then I suspect it's an issue with the ASUS WMI ACPI methods.

I can't find any of these on my C7H system, but then again all the EC access is now done via ASUS WMI. I suspect these only happened when AIDA64 + HWiNFO + SIV were doing direct EC access and when ASUS WMI is used this should no longer happen.

If you just run SIV 5.33 Beta-15 or later do you still get them? If so then we need to get ASUS to look into why. I can only sensibly comment when only SIV is active as I don't know exactly what other utilities do so you need to get their developers involved if you see them when their utilities are active.

Do you have any ASUS software active? Please post Menu->Help->Lock Usage + Menu->Help->Lock Handle so I can double check what is happening in terms of locking.

There is an issue with the WMI implementation which is why Mumak (author of hardwareinfo64) disabled it in the since the v5.87-3490 Beta release with the following comment: "Disabled ASUS WMI support on current BIOSes due to a faulty BIOS implementation."


I actually never used SIV to be perfectly honest with you but i am inclined to give it a try. I normally use hardwareinfo64 in the background and whenever i use the EC sensor, doesn't matter what program i get this warning message about the EC returning data etc. when this happens i also notice an slight decrease in performance and snappiness in Windows. When i disable or shut down software monitoring i no longer feel this and get the error in Windows event viewer. Performance also seem to be affected in benchmarks. In Cinebench R15 i seen a drop between 10-40 points if i use the EC sensor or disabled it. Firestrike means 100-300 points less in physics score.
I never seen this on any other board except Asus boards with this EC sensor.

The only Asus software i have is Aura lighting but that's about it. Even Alsuite 3 is causing big issues which result in even bigger problems than hardweareinfo64 or any other software monitoring program, it even has a tool to delete all the services because the uninstaller simply won't delete everything..
 
Provided all the reporting programs are using ASUS WMI then these should not happen and if they do then I suspect it's an issue with the ASUS WMI ACPI methods.

I can't find any of these on my C7H system, but then again all the EC access is now done via ASUS WMI. I suspect these only happened when AIDA64 + HWiNFO + SIV were doing direct EC access and when ASUS WMI is used this should no longer happen.

If you just run SIV 5.33 Beta-15 or later do you still get them? If so then we need to get ASUS to look into why. I can only sensibly comment when only SIV is active as I don't know exactly what other utilities do so you need to get their developers involved if you see them when their utilities are active.

Do you have any ASUS software active? Please post Menu->Help->Lock Usage + Menu->Help->Lock Handle so I can double check what is happening in terms of locking.
Will give it a go when I get back from the dentist.... For last month I have used almost exclusively, only, AISuiote3. Latest version, with ZERO problems. In fact, it seems to give me more accurate voltage readouts which I really don't get. I have used HWInfo a bit, with WMI disabled, and SIV when I want to fnd more detail... and no problems. I'm still on 0804 which seems a little more stable since summer ended - maybe I imagine that! ;) My machine has been more stable than ever. Zero critical errors.
@hurricane28 I also have those events`in event viewer. : The embedded controller (EC) returned data when none was requested. The BIOS might blah blah blah....
 
Get back when you have tried SIV

I actually never used SIV to be perfectly honest with you but i am inclined to give it a try.
I am told getting started with SIV is a bit of a steep learning curve and suggest you read http://rh-software.com/Using SIV to Control AIO Devices.pdf. A lot of it is about how to setup AIO control, but much of it is generally applicable.

In terms of CPU load then when I was testing after 7 hours SIV had used 3:39 and HWiNFO 9:13 so SIV should have a lesser effect on your Cinebench score.

The ASUS LightingService uses excessive CPU time and leaks handles so many SIV users keep asking me to get SIV to control the motherboard LEDs and at the moment I am looking into doing this. I have SIV32X showing signs of life and am trying to get ASUS to supply the x64 AURA_SDK64.dll that SIV64X needs to use.
 

Attachments

I also get this warning in event viewer: : "The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS."

They claim that its not related but it totally is.. When this error occurs the problem is there and when i no longer see this warning no fan or other stability issues.. Its right there that the BIOS is screwing the pwm signals up which is causing the fans to go haywire and Windows detect it.

On another note, not all people seem to be affected by it and have zero issues they claim. So it could also be that these IT sensor is not only extremely cheap (you can buy 10 of them for only 15 euro's) but also poorly made which means that with every 100 sensors you get several bad ones..?

Try disabling fast startup and turn hibernate off and see if that helps. Also, stop using AI Suite or any software that installs the Asus Com Service. You can also try uninstalling the ACPI device driver in the device manager to see if the errors and bad behavior stops.

I actually never used SIV to be perfectly honest with you but i am inclined to give it a try. I normally use hardwareinfo64 in the background and whenever i use the EC sensor, doesn't matter what program i get this warning message about the EC returning data etc. when this happens i also notice an slight decrease in performance and snappiness in Windows. When i disable or shut down software monitoring i no longer feel this and get the error in Windows event viewer. Performance also seem to be affected in benchmarks. In Cinebench R15 i seen a drop between 10-40 points if i use the EC sensor or disabled it. Firestrike means 100-300 points less in physics score.
I never seen this on any other board except Asus boards with this EC sensor.

The only Asus software i have is Aura lighting but that's about it. Even Alsuite 3 is causing big issues which result in even bigger problems than hardweareinfo64 or any other software monitoring program, it even has a tool to delete all the services because the uninstaller simply won't delete everything..
I like SIV in every way except for one, It needs to be simplified in the UI. I would honetly use it for everything that it can do if the UI were a bit more user friendly. If it were made over with a really nice simplistic UI or even an option for one then I believe more people would use it. Navigating the menus can be a challenge for first time users which could drive some away from using it if they were frustrated. I like the idea of one app controlling everything with minimal interference with the system resources. It just needs to have an option to make it simpler to navigate. Maybe even a way to take some of the readings that are most used and make a custom readout you can have on screen that is small and be able to minimize the main window to tray while being able to monitor voltages, frequencies, temps on a smaller widget type look with the values of your choice. I used to use a 2nd software to do that with HWinfo to create a windows widget with bar graphs that I customized names and colors etc and was very nice besides having to run 2 apps and install another software to adapt widgets back into windows. It got to be too bulky for benching with. Now im in the process of getting digital readouts and mounting them to a panel and soldering connecting wires to ProbeIt points and several other places on the motherboard for and got an IR temp gun so that I can monitor the system without software when it is finished.
 
RTFM (read the forgotten manual)

Maybe even a way to take some of the readings that are most used and make a custom readout you can have on screen that is small and be able to minimize the main window to tray while being able to monitor voltages, frequencies, temps on a smaller widget type look with the values of your choice.
Not only is this implemented you can also auto minimise the SIV main window on startup!
 

Attachments

Not only is this implemented you can also auto minimise the SIV main window on startup!
Hmm, I was reading the manual but to be fair it’s more like a book written for a college course ???? Don’t get me wrong, I love the complexity and the sheer amount of information and effort that is put into this. I didn’t make it as far as the custom window as I was studying just to get gpu and fans customized and I just got impatient I presume. I will take another look into it tonight and see what it takes to get it set up. Now that I’ve eaten my words on the custom window, that only leaves me wanting a simplification of the menu navigation, which does seem daunting at first but maybe there is a pattern to it that is easily learned. Ty for some clarification Ray.
 
I find the menus simple, but there are a lot of entries

Now that I’ve eaten my words on the custom window, that only leaves me wanting a simplification of the menu navigation, which does seem daunting at first but maybe there is a pattern to it that is easily learned.
I just checked and there can me almost a 1,000 entries in the menus and about 400 different panels! Given this I suspect many are overwhelmed by the sheer volume.

I find the menu trivial to navigate and pretty much all you need is in Menu->Tools->.... Did you find Menu->Help->View Menus?
 

Attachments

Hi everyone, I have a problem with my 970 Evo, or rather I think the C7H has it

I changed 2 Samsung 960 Pro and now I currently have the 970 Evo

Today I installed the demo of FH4, the game remains locked in the loading screen, while if I install the game on the Samsung 840, it starts without problems,this happens to me for example with Sleeping Dogs

Since I changed a total of 3 M2, I do not think they are the problem, remains the motherboard, someone has this problem with the M2?

is the fault of the CPU?
 
3,301 - 3,320 of 13,697 Posts