Forum Home
Press F1
Thread ID: 141726	2016-02-10 20:31:00	New PC Build problem	Nyuuji (5460)	Press F1

Post ID	Timestamp	Content	User
1415886	2016-02-10 20:31:00	Hi, I have just finished a new build for eldest son, with Win10 64bit. On a Gigabyte Z170N board, with i5-6500 and 16GB Ripjaws RAM, I have attatched a Samsung 950 Pro 256GB SSD to the rear M.2 port. There is also a WD 3TB Sata drive for all his data, games etc to go on. During install, I chose the 256GB SSD for the Windows installation. However, afterwards when I checked Disk Managment I got the below image.. 6959 Windows appears to have partitioned The 3TB drive into 3 parts, and made one system reserved (BIOS is also a bit slow to boot through). This is obviously not what I intended to happen. How do I repair this without having to do a reinstall with the 3TB disconnected to make sure it all goes on the 256GB SSD? Cheers, Nyuuji.	Nyuuji (5460)
1415887	2016-02-10 20:50:00	Did you enable secureboot and UEFI in the BIOS, before you installed Windows 10? 2.2 TB is the limit for MBR partitions Here's the same question on Reddit. The guy had to start again (www.reddit.com) And you may or will have to disconnect the 3TB before you install Windows again	Speedy Gonzales (78)
1415888	2016-02-10 21:01:00	And how did you install Win10? From a DVD or did you use something like Rufus and extract the ISO to a flash drive?	Speedy Gonzales (78)
1415889	2016-02-10 21:15:00	Hi Speedy, Thanks for the quick reply. Yes, the guy in the link you gave had a similar set up and almost identical problem. I installed by booting to USB flash disk with Win10 on it. Looks like I may have to reinstall with 3Tb disconnected. Can't remember changing any UEFI settings. In BIOS, will they be under any particular heading?	Nyuuji (5460)
1415890	2016-02-10 21:28:00	If you used Rufus to put it on the flash drive, you have to select UEFI / NOT MBR before you extract it to the flash drive (Thats if you used an ISO) What GB mobo have you got?? There's more than 1 Z170N mobo. ie: Gaming / wireless. And since this is a Skylake mobo, there is a known issue with the 6700K CPU (and maybe other Socket 1151 CPU's). It'll freeze under load. There may a BIOS update that fixes this So, once you're up and running, I would update the BIOS as well You would have to read the manual. I've never built a GB system, only ASUS. To see where the UEFI / secureboot options are	Speedy Gonzales (78)
1415891	2016-02-10 21:38:00	Windows 7 has done that to me before, I only realised when I removed the data drive and windows refused to boot. I think I eventually managed to fix it by using EasyBCD to make the C: drive bootable but it was ages ago and my memory is not the best. Hindsight and all but it's always best to install windows with only 1 drive attached, it's not a well behaved installer. Edit: Also note the MBR issue speedy mentions only effects boot drives, you can still format and use all 3TB from windows regardless as long as you don't want to use it as a MBR boot disk.	dugimodo (138)
1415892	2016-02-10 23:13:00	It's the i5 6500 3.2Ghz model, so should hopefully be fine. The board is GA-Z170N Gaming 5 (ITX), and a Gigabyte GTX 960 Mini graphics card. All inside a Phanteks Enthoo EVOLV ITX case. Disconnected the 3TB and, as predicted, would not boot. So I have disconnected the 3TB and am reinstalling Win10 now. Will update with results later. Cheers.	Nyuuji (5460)
1415893	2016-02-10 23:18:00	Looks like the CPU may still be affected since the latest BIOS F4d fixes the prob Fix Intel Skylake CPU Prime 95 issue Altho, I dont really trust BETA Bioses. They're beta for a reason. Get it later when it's out of beta	Speedy Gonzales (78)
1415894	2016-02-10 23:27:00	Yes, I saw that on the Gigabyte support page. Was going to update BIOS earlier untill I saw it was BETA (15th Jan 2016). Will wait a litlle while. Thank you.	Nyuuji (5460)
1415895	2016-02-11 00:09:00	The CPU prime 95 bug is not all hat big of an issue, intel say most people will not experince it. I know I have a 6700K and did a burn in test with prime95 when I built it with no problems, so even using the effected CPU for the exact program doesn't necessarily trigger the bug. I would definately update the BIOS to a fixed version at some point but waiting for a while for a proper release version should be perfectly fine, I did mine a couple weeks ago but am not sure the new version actually has that fix. I've had mine since early august and never experienced any problems. Mines an Asus board.	dugimodo (138)
1 2