Puget Systems print logo

https://www.pugetsystems.com

Read this article at https://www.pugetsystems.com/guides/1042
Article Thumbnail

WHEA_UNCORRECTABLE_ERROR on Gigabyte x299 and Skylake-X [SOLVED]

Written on September 21, 2017 by Chad Warmenhoven
Share:

Current Status

Many users are currently experiencing a WHEA_UNCORRECTABLE_ERROR (BSOD) when using Adobe products on the Gigabyte x299 motherboard and Skylake-X processors. 

Common configurations:

Gigabyte x299 Aurus - BIOS v. F7m

Skylake-X Intel Core i7 7820X


Update 9/22/17

Our current solution is below along with clarification as to why this works. 

Please follow these steps and let us know if you have any trouble/questions along the way, we are here to help. 
1. Please restart the computer and enter the BIOS using the F2 key on the keyboard - start repeatedly pressing/releasing F2 after you hear the POST beep
2. Using the keyboard arrow keys, under the "M.I.T." tab navigate to "Advanced Voltage Settings" and hit enter
3. Navigate to "CPU Core Voltage Control" and hit enter
4. Highlight "Internal CPU Vcore" then use the +/- keys to adjust settings
- Internal CPU Vcore: 1.200V
- Adaptive Mode: Enable
5. Navigate to the "Save & Exit" tab
6. Highlight "Save & Exit Setup" and hit enter - confirm any prompts

It appears that a recent Adobe update calls for more power from the CPU, almost as though it desires an overclock in order to function correctly with these hardware configurations. Customers whose system is already overclocked likely won't encounter the WHEA error for that reason but those that do not opt for an overclock will need to apply the voltage change in order to rectify the BSOD. 

When you change the CPU voltage please follow our suggestions as CPU damage can result from an incorrect voltage adjustment. Additionally, a few of our users along w/ many people on the forums have reported that adjusting AVX offset but we would advise against this. Changing the AVX settings makes numerous (on-demand) changes to CPU clock, multiplier, voltage and core clock which only introduces more failure points when the voltage is the only adjustment needed. If the AVX setting is adjusted your system which has been carefully configured may become unstable and may even produce more heat which would increase fan speeds to compensate; your fans would get much louder and overall temperatures could effect system performance. The AVX change is also not a complete fix as it only applies when applications actively running AVX instruction sets.

As always, if you have any questions or concerns please do not hesitate to reach out to the Puget Systems support staff. 

Email: Support@pugetsystems.com

Phone: (425)458.0273

Posted 9/21/17

The error is reproducible when under heavy load and we are currently researching a solution. We will update this article as new information becomes available. The error is causing critical failures and BSODs. We are currently consulting with Intel and Adobe as well as our internal labs department in an effort to find a solution as quickly as possible. 

We encountered this error during our internal testing of the Gigabyte x299 boards and Gigabyte released a hotfix addressing it, unfortunately we don't think it was enough and therefor did not fully resolve. We are most heavily focusing on BIOS voltage changes and will include a full tutorial if that fix is successful. 

The error typically presents when using Adobe products under heavy load with varying circumstances and is reproducible for many of our customers. We are currently unable to reproduce with our current testing/bench-marking but have numerous reports from customers when using the following software: Adobe Premiere, Photoshop, After Effects and Lightroom. 

If you are currently experiencing any BSODs related to this issues and are running the aforementioned software/hardware please check back frequently for an update. 

 

We will continue to update this article as new information presents. 

Tags: Software, Hardware, Premiere Pro, After Effects, Photoshop, Lightroom, Skylake-X, Motherboards
barcik

does it concern just Gigabyte boards? Have you tested this issue on other boards from Asus or MSI?

Posted on 2017-09-22 12:44:23
Samyntha Hubbard

Hi Barcik,

So far, all reported instances are only on Gigabyte X299 boards and we believe it to be isolated. However, if we hear of it affecting other boards as well, we will certainly broaden our testing. If you are experiencing this issue or are in need of additional assistance, please feel free to reach out to our Support team by emailing Support@pugetsystems.com or calling (425) 458-0273 Ext. 2. We are always happy to assist!

Posted on 2017-09-22 16:58:17
Davey Kropf

I got the exact same issue on the MSI X299 SLI Plus with BIOS version 1.50.

Posted on 2017-10-25 18:44:45
pillybilly

This is a problem caused by bad factory clock settings, producers try to rise the charts during the reviews overclocking by default their motherboards. Every board with high power consumption can have these problems, the ourus 7 56.4 watt and the msi sli plus 57.6 when the the gygabyte x299 ud4 consumes in idle 46.8 watt. If you need a motherboard to work with it don't choose a "gaming" board...

Posted on 2017-11-21 11:56:59

Other boards are affected. I have Alienware area 51 R4 unidentified motherboard. And I had that problem too. Many people are complaining on Adobe, intel dell forums and I think they have other boards than Gigabyte.

Posted on 2017-11-26 15:47:12
gamer 8439

can this be remedied by adding adobe product to the gpu 3d management profiles then adjusting settings under the profile?
if exe running not listed in this list then generic profile used
also ensure that under windows color profiles you have compatible .ics files as default(adobergb.ics when adobe product used)

Posted on 2017-10-03 21:25:40
TheRealLagmaster

I also use my PC for gaming and have this CPU and MB combo and was really confused at why Count strike Global offensive was crashing and coming up with this error but this seems to have fixed it all that was happening when launching CS:GO it would crash right away before even loading the intro video but now im able to play again TY.

Posted on 2017-10-04 14:52:18
Scandal

Same Problem here but in CSGO ( WHEA Blue screen ) after 1-2min sometimes crash already in the intro vid.

I tested this and it Works ( thanks btw )

But i prefer an BIOS update, any hope?

my system:

Motherboard: GIGABYTE X299 UD4
BIOS: F4
CPU: i7 7820X
System: Win 10 64-bit

Posted on 2017-10-05 20:04:33
Kurt Boswood

Hi Chad,
Just wanted to say a quick "thank you"!

The latest firmware update was causing constant BSOD's, and the previous fix of adjusting the LLC (CPU LoadLine Calibration) didn't work.

Thanks again!
Kurt.

Posted on 2017-10-12 08:46:57
Mark81

the truth here is that motherboard vendors are standard overclocking
these cpu's. (dont know if they all do it, but MSI does) For the 7820x
it should standard overclock all cores to 4GHZ.
The problem is dat
fair amount of 7820x cpu's cant run stable on these clockspeeds because
most mainboards set the auto vcore setting too low. So not enough juice
to feed the cpu resulting in BSOD such as WHEA uncorrectable.

So like puget already offered for a workaround set the Vcore at 1.2V and look if it runs stable. If it does you can
lower the vcore with small steps until it become unstable. Also set it
to adaptive mode so it does not run 1.2v trough the CPU all the time.

Posted on 2017-11-02 16:33:37
Pavel Smirnov

Thank you! Got the same problem on 7820x and msi x299 raider. Helps wite Core voltage 1.2

Posted on 2017-11-09 07:06:52
Dorian Apanel

Same issue on x299 Aorus Gaming 7 (Gigabyte) with 7820X. It crashes after about 10-15 seconds of compressing videos (using free XMediaRecode).

Posted on 2017-11-09 20:55:52
David Kutz

THANK YOU VERY MUCH !!;
I work with very large Photoshop files - some exceeding 40GB. PS ran normal for small files, but I could not load a big one without getting a WHEA...BSOD. I followed your instructions for changing the Internal CPU Vcore to 1.200V. I'm still testing, but it looks like it is working!!! THANKS!!! My new system is:
Win10 x 64
Intel Core i9-7940X Skylake
GIGABYTE AORUS X299 AORUS Gaming 3 (rev. 1.0)
BIOS: F5

Posted on 2017-11-14 16:12:04

Got the same problem whit an alienware area 51 R4 (x299) and i9-7980XE cpu. But not only in after effect but when rendering with 3dsmax/V-Ray too. I will try increasing cpu vcore and setting adaptive mode on if I can do it in my bios.

Posted on 2017-11-24 17:54:51

Hey I just wanted to thank you for publishing this solution on your website, it works for me and I can see many people on Intel forum, Adobe forum, etc all having the same problem so I sent them the link to your website! I think you will save many people a lot of time!

One thing: after that I wanted to overclock my cpu a bit more but the bsod were back so I then used the avx offset too and the bsod are gone again! But would it be better to increase even more my voltage instead of using avx offset if I want to overclock?

Posted on 2017-11-26 15:44:50
Andrew Bougie

Thanks so much for posting this in the Adobe forum! I wasted so much time with other troubleshooting steps before finding this solution. This fixed my crash on launch issue for both Premiere Pro and InDesign CC 2018. I have the Gigabyte X299 Aorus motherboard and the i7-7820X.

Posted on 2017-11-30 22:00:57

Just to follow up, my blue screens are back. I just got 4 in a row trying to start a 3d rendering. So it was stable for a few days with some overclok settings but now it stopped. I received a replacement computer with a new bios and that one has got any blue screen since I receive it it a week ago and I have been rendering on it almost full time. So maybe my first cpu was damaged by the bad settings or the old bios is just flawed.

Posted on 2017-12-09 13:48:35
Matthew Pietkevich

Hello Jocelyn,
Glad to hear you are finding some success with your Alienware build. I'm a designer and purchased the same Alienware build as you. What Bios version did the new replacement computer have? My Bios has version 1.0.3.
Thanks and appreciate the help,
Matt

Posted on 2017-12-12 22:18:17

The new one has 1.0.7

Posted on 2017-12-13 02:10:29
David Fliss

I have the same set up as you do and I have tried both BIOS versions 1.0.3 and 1.1.2. I'm still getting BSOD with both. Can you confirm that 1.0.7 is stable as far as you know?

Posted on 2018-01-05 01:53:42
Jake Dean

my asus x299 "rampage vi" board also has vcore regulation issues. I was able to fix it changing vCore to 1.12V (fixed, not adaptive, for now). It doesn't seem adobe-specific, but things that need high cpu frequency on a single-threaded load.

Posted on 2017-12-15 15:06:55
Matt Taylor

Thank you! Exactly what I needed!

Edit: BSOD still persists. I've now disabled turboboost in BIOS and things seem to be working. Keeping my fingers crossed...

Posted on 2017-12-19 23:31:15
Jean-François Begue

Hello, I've got the same problem, and only with photoshop. My consummer assistant send me some information to change the bios. In the first time i'll try it, but the problem still persist.. so I go looking in easy tune.. and change all value of core ( as on bios).. and Now.. all is ok...
The turbo is of, but photoshop is OK.
Advanced Frequency Settings:
CPU BCLK Frequency : 100 MHz
PCIe/DMI/PEG Frequency : 100 MHz

all the rest on auto

Advanced CPU Cores Settings

CPU Flex Ratio Override : Disabled
Intel Turbo Boost Technology : Auto
Turbo Ratio : Auto
Intel Turbo Boost Max Technology : Auto
Turbo Per Core Limit Control : 43 for all ( and don't forget put the same in easy tune).

Posted on 2018-01-07 17:43:32
JoshPabst

This did fix my BSOD probelm, but performace is still terrible in many softwares, until I disabled TurboBoost in BIOS. For example, even with 1.2v I could not play a video clip smoothly in Vegas - at less than 1 fps... once I disabled TB in BIOS, all software run stable. Also, when TURBOBOOST was enabled and I had voltage at 1.2v, Adobe software was slow and would hang a lot, this was fixed by disabling TurboBoost

Posted on 2018-01-08 17:10:55
timaoul

I try this, just limit cpu turbo per core.. and it's ok.. it woerk at 4300 mhz maxi

Advanced Frequency Settings:
CPU BCLK Frequency : 100 MHz
PCIe/DMI/PEG Frequency : 100 MHz

all the rest on auto

Advanced CPU Cores Settings

CPU Flex Ratio Override : Disabled
Intel Turbo Boost Technology : Auto
Turbo Ratio : Auto
Intel Turbo Boost Max Technology : Auto
Turbo Per Core Limit Control : 43 for all ( and don't forget put the same in easy tune) if you have install it.

Posted on 2018-01-08 17:54:17
Edward R Przyzycki

Thanks for this page, Puget Systems. This is why people should have you do their builds! I have a Gigabyte X299 Gaming 9 (with a i9-7920x), which had bios version F5 (6/26/17). CPU Vcore was set to auto. Made the change to 1.200V and adaptive mode: enable, exactly as you said, and my Premiere errors are gone! Note that I am not overclocking. I also then realized bios F6 is available (9/20/17). I then upgraded the bios. Note that the new default was Vcore auto at 1.133V, and adaptive mode: auto. Premiere is still working. Wanted to let people know that switching to F6 doesn't hurt anything, either. Thanks again for the lifesaver post!

Posted on 2018-01-12 13:06:19
Stu Siegal

Thanks so much for posting this, saved me some serious time and stress! Question - does this fix rule out overclocking? I am running the gigabyte x299 aorus gaming 7 w/ i7 7820x and 32gb ram and still seeing yellow render bars, but don't want to go back to seeing BSOD's.

Posted on 2018-01-22 02:25:45
Richard Servello

Msi x299 raider here and I've been having this same problem. Trying this change now. Fingers crossed.

Posted on 2018-03-09 19:45:47
lsbrasil

Could anyone point me where I can find these options on Asrock X299 TAICHI ? I'm not beeing able to find and my system is crashing using any Adobe software. Thank you very much for your time and patience!

Posted on 2018-04-16 12:02:18
André Venancio

Finally, in its latest BIOS update (Aorus Gaming 3 - BIOS version F8d) Gigabyte corrected the compatibility issue between Adobe software and the X299 platform. Until the previous version, I had many problems. Photoshop and After Effects only worked with changes in VCore and overclocking. Even so, it was not 100% yet. I had to restart the computer a few times, kick the machine, throw it against the wall, cry, despair, it was horrible.
After I upgraded to this latest BIOS version the issues are gone. Everything running fine.
I think other manufacturers have also upgraded their systems. Update everything, software, firmware, hardware and all the wares you have. :)

Posted on 2018-08-06 19:44:51
Russell Kaye

Just wanted to say thanks! I was having this same problem on an Asus Prime x299 Deluxe with the i7-7820x, and making this change seems to have solved the issue.

Posted on 2018-09-11 21:23:09
Raul Martinez

Any progress?? I’m currently using an x299 Gaming 7 with an i9 7960x and when trying to overclock it shutdown while using Pix4D Mapper Pro. The only thing that prevent this to happens it’s putting the settings to “eco mode” on the “easy tune” program. I think that a CPU an MOBO like this should be able to run programs like this while overclocking with out problems. Don’t you think?

Posted on 2018-12-25 21:41:31

ironically the same isuue is still there after more than a year, CPU I9 7920x mainboard ASUS PRime x299 deluxe II. what helped in my case: Increas only the """"CPU Input Voltage""" from Auto to 2.10V attanton CPU Input Voltage is not VCore!!!! I guess problem is more from the VRM to the CPU...

Posted on 2019-03-11 00:58:01