Absolutely appaling Gigabyte technical support.

[smakme7757]

Ok a few weeks ago i found a bug in the Dynamic Energy Saving software which overvolts your chip. Since then i have been trying to convince Gigabyte tech support that it exists.

Unfortunatly they keep telling me CPU-Z and AIDA 64 are reporting the wrong Vcore and that i needed to use the current beta (which i am using)! So i uploaded a video using the latest version of both products which report the correct Vcore, but they insist that i am still using an outdated version of CPU-Z!

Here is the video i made: http://jack-brennan.com/Downloads/des2voltage.avi

Now look at my video and the version numbers and cross check them with Gigabytes reply.

Gigabytes reply:
You did not use the latest CPU-Z BETA. I have attached the latest CPU-Z 1.56.3 BETA. This is reading the correct Vcore.

I enclose two screenshots of my test. As you can see:
-AIDA is showing absolutely wrong Vcore.
-On this issue, you should contact AIDA support.

EasyTune6 shows correct Vcore, CPU-Z shows correct Vcore. It does not matter if DES is on or off.

If ET6 and the attached CPU-Z still show such abnormal Vcore you should check the core temps in AIDA ( Motherboard > Sensors). If Vcore goes to such abnormal value the core temps should increase dramaticly up to shutdown of the CPU.

/End Gigabytes reply

As you can see i am clearly using the same version of CPU-Z as them and they are using an older version of Aida 64. The guy has tried 3 times to convince me that i am using an old version of CPU-Z when it's blatantly there in my video proving i am using the correct version.

Are they blind??

My results are even further backed up by DES 2 power draw meter which shows it going from 60w to nearly 100w. I just don't understand why they are being so un cooperative when i send them a video proving the phenomenon with all the latest software updates showing my Vcore i set in BIOS?

 

[IGemini]

Tried downloading the newest DES2? I noticed that their most recent one is dated for 3 days ago, maybe it fixes the problem.

 

[smakme7757]

Tried downloading the newest DES2? I noticed that their most recent one is dated for 3 days ago, maybe it fixes the problem.

Ah thank you, i had downloaded a fresh copy a few days ago, but i guess i only just missed this latest update and i havn't been back to check since. I hope this fixes the problem, i've been on their back for nearly a month.

Unfortunatly getting any sort of useful response from someone who refuses to look at the material provided is extremely annoying. Even more so when i'm being told to dosomething i alraedy have and additionally documented it in a video. The least he could have done is said "Yes we are aware of this issue, an update is on the way" instead of trying to run me around in circles.

Edit: Yep the update has fixed the problem. So maybe i wasn't such an annoying customer after all .

 

[smakme7757]

Nope new version just causes BSODs and system freezes. I give up the software is awful.

 

[MagnusTheBrewer]

Your first mistake was thinking that one of the functions of Gigabyte technical support is to respond to customers with technical issues.

 

[Diogenes2]

As with any technical support team, their job is to deny that any problem you have has anything to do with their product, even when confronted with overwhelming evidence to the contrary ..

http://www.youtube.com/watch?v=4vuW6tQ0218&feature=related

 

[slag]

Newest version as of yesterday of cpuz is 1.56.4, not 1.5.6.3. 1.56.3 reported incorrect readings for me, but 1.56.4 is correct.

 

[RussianSensation]

So hold on, you have 1.188V with Dynamic Vcore Enabled, which means that the Gigabyte software is lowering your CPU vcore vs. 1.200V without the Energy Saver enabled. This means the software is working correctly. Most importantly, from the video you linked, you don't even have EIST, C1, C3-C6 states enabled. Are you also running your chip at 1.584V per CPU-Z to achieve your 4.5ghz overclock? That's way too high for a 32nm chip.

So forget DES2 / AIDA issue for a second. You should be running your cpu < 2.0ghz at idle with proper power management features enabled (i.e., consider using Dynamic Vcore or DVID in the BIOS to arrive at 0.96-0.98V at idle).

Not sure why you have concluded that the DES software is overvolting your chip? The AIDA voltage is obviously incorrect since at 2.988V your chip would be instantly killed. Besides the point, if you are seeking to lower your idle power consumption, you need to enable all power saving features. You shouldn't even be touching DES2 before you have EIST, C1, C3-C6 and DVID sorted out imo.

 

[smakme7757]

So hold on, you have 1.188V with Dynamic Vcore Enabled, which means that the Gigabyte software is lowering your CPU vcore vs. 1.200V without the Energy Saver enabled. This means the software is working correctly. Most importantly, from the video you linked, you don't even have EIST, C1, C3-C6 states enabled. Are you also running your chip at 1.584V per CPU-Z to achieve your 4.5ghz overclock? That's way too high for a 32nm chip.

So forget DES2 / AIDA issue for a second. You should be running your cpu < 2.0ghz at idle with proper power management features enabled (i.e., consider using Dynamic Vcore or DVID in the BIOS to arrive at 0.96-0.98V at idle).

Not sure why you have concluded that the DES software is overvolting your chip? The AIDA voltage is obviously incorrect since at 2.988V your chip would be instantly killed. Besides the point, if you are seeking to lower your idle power consumption, you need to enable all power saving features. You shouldn't even be touching DES2 before you have EIST, C1, C3-C6 and DVID sorted out imo.

Russian you have to read my post again.

I sent the video to Gigabyte - this is to prove that DES 2 overvolts my chip! Now look at my video from start to finish. At the start my Vcore is 1.289 which is what i set in BIOS. Once i turn DES 2 off it skyrockets to 1.589 Vcore - That's the bug i'm trying to imform Gigabyte about!

The pictures above are what Gigabyte sent to me in a reply to my video (if you look carefully you can see they are using a 2600, not a 2600K that i have). They are using an old version of AIDA which is reporting 2.988, not me. my problem is that Gigabyte keep telling me to use CPUZ version 1.56.3, but i am and it 100&#37; visible in my screenshot.

In my video you can clearly see DES 2 overvolting the CPU as it starts at 1.289(what i set in BIOS) and ends up at 1.589! I proved it and they refuse to believe it. The fact that the CPU is overclocked is irrelevant as software shouldn't be pushing the CPU to nearly 1.60v!!!!!!!!!!!

 

[smakme7757]

Newest version as of yesterday of cpuz is 1.56.4, not 1.5.6.3. 1.56.3 reported incorrect readings for me, but 1.56.4 is correct.

They both report the same for me, i have no issues.

 

[RussianSensation]

In my video you can clearly see DES 2 overvolting the CPU as it starts at 1.289(what i set in BIOS) and ends up at 1.589! I proved it and they refuse to believe it. The fact that the CPU is overclocked is irrelevant as software shouldn't be pushing the CPU to nearly 1.60v!!!!!!!!!!!

Ok now I understand it. You made it a lot clearer.

But besides the point, why are you even using DES2 hehe. I had played with P35, P45, P55, P67 Gigabyte boards and never used this gimmicky software! Just enable EIST, C1, C3-C6 and call it a day. Even if DES2 does work, I doubt it makes much difference if at all. I see why you are frustrated now though. Well maybe you have to clarify to them over the phone the issue in detail.

 

[smakme7757]

I have all the power saving features enabled in BIOS, i was just testing all the features of the board as it's new and came across this problem. I suppose i'm beating a dead horse as Gigabyte will most likely get back to me and say to use CPUZ 1.56.4 (As slag pointed out it's just been released).

But yes it's very frustrating to be told to use a particular version of the software, when i have a video of my using the software . My guess is they didn't watch my video.

I really didn't do this for my benifit, but rather for anyone who wants to use this software. I was just trying to make Gigabyte aware of the issue.

They have since released a new version, but it just freezes my system so i've given up . I just hope some people don't kill their processors by using the software.

 

[Tsavo]

Nope new version just causes BSODs and system freezes. I give up the software is awful.

I see nothing has changed.

ET6 will hard lock my system in a nanosecond even going up only 200 MHz.

 

[smakme7757]

I see nothing has changed.

ET6 will hard lock my system in a nanosecond even going up only 200 MHz.

Well i guess i'm not the only one then .

I've given up, i just got a reply for the support rep, and he said that AIDA 64 is broken, dispite the fact AIDA 64 shows the same Vcore as CPUZ.

I can't be bothered talking to him anymore, he just seem to be trying to take the conversation off topic and always winding his way around the fact DES 2 is unstable and broken.