Short story: Bought gigabyte H170M-DS3H, i3 6100, 8GB RAM. Both Windows and Linux would freeze on boot. Borrowed ASUS motherboard; Linux worked fine on that. Returned faulty gigabyte H170 motherboard, and bought a gigabyte B150M-D3H and it has the exact same problem as the first gigabyte motherboard.
Now I don't know whether I have lucked-out with two dud gigabyte motherboards, or have a CPU that, for some reason, doesn't like gigabyte motherboards.
Things I'm pretty sure aren't the problem:
- RAM: I can boot memtest86 on the gigabyte H170. Left it running for an hour or so. No problems.
- PS: Tried with a no-name 450w and a corsair 850w.
- BIOS: Upgraded the H170 from F4 to F20. The B150 came with F20.
- OS: I get a screen with a random pattern of green and black pixels a few seconds into booting, with both windows (from SSD) and Linux (Ubuntu 16.10 from USB). Multiple boots of Linux in text-only mode show a freeze at different points, at around the 4-5 second mark, and once I got a kernel panic.
Which leaves:
CPU: I booted Ubuntu 16.10 on USB on a borrowed ASUS motherboard (same CPU and RAM) and ran a couple of infinite loop programs to tax the CPU. It was working fine a few hours later. So I know the CPU works with a non-gigabyte motherboard.
Motherboard: Perhaps I just got two broken gigabyte motherboards in a row?
Something else: Any other suggestions as to what might be wrong?
[edit]
I returned the gigabyte B150M motherboard and got an identical replacement, and it had exactly the same symptoms. So CPU bad right? However, I then returned the gigabyte motherboard and got a ASUS B150 motherboard. And the i3 6100 has been running flawlessly with the ASUS motherboard for over a week. So somehow I've ended up with a CPU that doesn't like gigabyte motherboards. Which seems pretty unlikely, but every other explanation is even less likely.