Official GIGABYTE Forum

Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: Anat on July 29, 2015, 06:57:53 pm

Title: Have to disable core for Windows 10
Post by: Anat on July 29, 2015, 06:57:53 pm: Using h81m-ds2v and g3258 - Windows 10 will not boot with 2 cores enabled. I along with others first noticed this with build 10162. Updating drivers for motherboard had no effect. Other BIOS settings have no effect. Clean install has no effect. Turn off a core, everything is fine. Enable both cores, boot loop. Many people with different motherboards are having the same problem, links below. ASUS posted they are updating their BIOS due to a microcode update. Is this coming from Gigabyte?

http://forum.asrock.com/forum_posts.asp?TID=441&title=kb3064209-breaks-the-g3258

http://answers.microsoft.com/en-us/windows/forum/windows_10-win_upgrade/windows-10-build-1016810240-incompatible-with/01c23c9a-e9a3-4214-b936-270050e25362?auth=1

http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/cant-install-windows-10-build-10162-on-gigabyte/5be9d4ec-fdc4-47bd-9eb6-5b26806cba59

OS Name   Microsoft Windows 10 Home
Version   10.0.10240 Build 10240
Other OS Description    Not Available
OS Manufacturer   Microsoft Corporation
System Name
System Manufacturer   Gigabyte Technology Co., Ltd.
System Model   H81M-DS2V
System Type   x64-based PC
System SKU   To be filled by O.E.M.
Processor   Intel(R) Pentium(R) CPU G3258 @ 3.20GHz, 3200 Mhz, 1 Core(s), 1 Logical Processor(s)
BIOS Version/Date   American Megatrends Inc. F5, 6/19/2014
SMBIOS Version   2.7
Embedded Controller Version   255.255
BIOS Mode   UEFI
BaseBoard Manufacturer   Gigabyte Technology Co., Ltd.
BaseBoard Model   Not Available
BaseBoard Name   Base Board
Platform Role   Desktop
Secure Boot State   Off
PCR7 Configuration   Binding Not Possible
Windows Directory   C:\Windows
System Directory   C:\Windows\system32
Boot Device   \Device\HarddiskVolume2
Locale   United States
Hardware Abstraction Layer   Version = "10.0.10240.16392"
User Name
Time Zone   Eastern Daylight Time
Installed Physical Memory (RAM)   8.00 GB
Total Physical Memory   7.89 GB
Available Physical Memory   6.04 GB
Total Virtual Memory   9.76 GB
Available Virtual Memory   7.47 GB
Page File Space   1.88 GB
Page File   C:\pagefile.sys
Hyper-V - VM Monitor Mode Extensions   Yes
Hyper-V - Second Level Address Translation Extensions   Yes
Hyper-V - Virtualization Enabled in Firmware   Yes
Hyper-V - Data Execution Protection   Yes
Graphics   ATI Radeon HD 4800 Series
No Peripherals
Title: Re: Have to disable core for Windows 10
Post by: iotasnk on July 29, 2015, 11:54:14 pm: Seconding what this guy said. If ASRock can do it, so can Gigabyte.
Title: Re: Have to disable core for Windows 10
Post by: krelm on July 30, 2015, 12:11:07 am: I have the same problem on a H81M-S2PV Motherboard with a G3258 processor. Cannot install Windows 10 unless i disable 1 core.

I have always been a supporter of Gigabyte products for many years and i hope they will release a bios update to fix this - ASROCK have already fixed this issue for at least 1 of their motherboards via a bios update.

Please help us Gigabyte!

Thank you
Title: Re: Have to disable core for Windows 10
Post by: iotasnk on July 30, 2015, 12:52:05 am: Quote from: krelm on July 30, 2015, 12:11:07 am
I have the same problem on a H81M-S2PV Motherboard with a G3258 processor. Cannot install Windows 10 unless i disable 1 core.

I have always been a supporter of Gigabyte products for many years and i hope they will release a bios update to fix this - ASROCK have already fixed this issue for at least 1 of their motherboards via a bios update.

Please help us Gigabyte!

Thank you

Yes, please! I also forgot to mention that I am running a GA-H81M-DS2V with a G3258 processor.
Title: Re: Have to disable core for Windows 10
Post by: krelm on July 30, 2015, 11:03:08 am: Well after having a gander through these forums it seems highly unlikely this thread will even get read by someone from Gigabyte, nevermind an actual BIOS fix!

Shame, i always liked Gigabyte but perhaps it's time to go with someone who listens (like ASRock)
Title: Re: Have to disable core for Windows 10
Post by: Anat on August 04, 2015, 04:46:53 pm: I got a response on my ticket:

"We have forwarded the information over to our team to help check, once we get updates from our team we will update this ticket."

Pretty vanilla response but if we are charitable we can assume they are looking into it?
Title: Re: Have to disable core for Windows 10
Post by: Anat on August 04, 2015, 05:32:52 pm: Support sent me a BIOS to try, it wouldn't flash. "BIOS ID check error" Sad news but looks like it's actively being worked on.
Title: Re: Have to disable core for Windows 10
Post by: Anat on August 06, 2015, 06:53:19 pm: The BIOS ID problem was my fault, I picked the wrong MB from the huge drop down list (off by a letter). They sent me the updated BIOS and it appears to fix the issue. Looks like you need to open a ticket until these get posted, don't know why but w/e.
Title: Re: Have to disable core for Windows 10
Post by: dmdilks on August 07, 2015, 03:20:51 am: You know windows 10 could be the problem. Let see windows 7 works, windows 8 works. We are going to have problems with windows 10 for some time. I understand people you are having a problem but give them time to fix.

I have run windows 10 on a lot of computers and some had problems. That I didn't have with other OS. By what I'm reading from the links the OP put up. Microsoft didn't have a problem with 10074. But they did with 10130 & 10162.

So Microsoft has left the MB companies holding the bag on this one. The one link shows that you were having a problem a month before the release date. So 10074 didn't have the problem but 10130 did. The 10130 was release MAY 29, 2015.

So 2 months before the release they had a problem. All I'm saying is Microsoft screw up and now the MB companies have to jump through hoops to fix Microsoft screw up.
Title: Re: Have to disable core for Windows 10
Post by: Anat on August 08, 2015, 06:01:59 pm: I'm really not sure who to blame, that's probably an insider question.

However, I was having an issue with windows 7 (fresh install) so I wouldn't say everything was fine. There was a Windows 7 update that refused to install, and caused a lot of issues. I also got frequent blue screens. I wasn't alone on those problems. Overall, the Windows 7 problems I had using this board (whoever's fault it was) have been annoying, but I'm glad Gigabyte got an update to me that seems OK at the moment for Windows 10.

On my main system (AS Rock) I've had no issues at all Windows 7-10 betas and final releases. Just a consumer observation.

I'm happy as long as a product is supported through these changes.
Title: Re: Have to disable core for Windows 10
Post by: tenuser on August 24, 2015, 05:50:57 am: My board has a BIOS update for this issue:

"Update CPU microcode for win10 support with Pentium AE"

http://www.gigabyte.com/products/product-page.aspx?pid=5174#bios

Is this the same as Asrock's "fix" that disables overclocking?
Title: Re: Have to disable core for Windows 10
Post by: tenuser on August 29, 2015, 10:02:48 pm: Quote from: tenuser on August 24, 2015, 05:50:57 am
My board has a BIOS update for this issue:

"Update CPU microcode for win10 support with Pentium AE"

http://www.gigabyte.com/products/product-page.aspx?pid=5174#bios

Is this the same as Asrock's "fix" that disables overclocking?

Answering my own question, the new BIOS does NOT disable overclocking. It does allow you to boot with both cores at stock speed, but if you try to overclock, you'll still get the boot crash unless you remove/rename the offending dll. (mcupdate_GenuineIntel.dll in System32)