>"use Ryzen its better for what you want to do"

It means your ass is filled with jewish cum so you should stick to using intel cpu as per usual.

Okay?

>>61744337
Gigabyte mother board are trash.

T. Gigabyte motherboard owner

/g/ is NOT your personal tech support team or personal consumer review site.

>>61744384
in my anecdotal experience of owning exactly one gigabyte mainboard in my life which promptly broke i can second this

>>61744384
>>61744403
Gigabyte and MSI are shit.

Only good board I've used were Asrock (unironically) and Asus, although you can find a lemon literally anywhere. All it takes is one overworked chink at foxconn to fuck up the entire board.

>>61744417
>>61744403
>>61744384

Funny, my old i5-2500k build is using a Gigabyte z68(?)ud3 motherboard and has been running fine since 2011.

>>61744337
probably the gigabyte motherboard
read about some faulty ones so I would avoid that
R7 1700 here with a MSI B350 Tomahawk Arctic
Only issue I had was not being able to OC from the bios, would end up with 1.5GHz on all cores after crossing a certain CPU voltage.
A bios update fixed that for me though and now its working like a charm

>>61744384
gigabytes ryzen boards are actually second best behind ASUS. Granted all the low end ryzen boards are pretty hit and miss - they're under $70 so you get what you'd expect.

>>61744337
>AMD
>Gigabyte motherboard
>guilt by association

Yeah ok whatever.

>>61744337
take it to geek squat or return it, faggot

>>61744448
Thats because they made decent motherboards back then

>>61744337
well error 41 is a generic error for when you power down unexpectedly.
I'd guess that the issue is with faulty/poorly configured ram. If you're running at 3000MHz then I hope you're running the most recent AGESA update.

>>61744477
lol no, the k5 is an absolute joke of a mobo. £170 performs worse than my £80 b350 asus prime

>>61744337
Had similar corruption problems(frequent file corruption and BSOD) with 2 Athlon 64 x2s(90nm) on Gigabyte motherboards(I know they are very old for Windows 10) , no problems with my Ryzen setups though(1x5 and 1x7) with Asus motherboards. My Intel Ivy-E w/Asus mobo setup had no problems either. My previous Intel MSI setup was also fine until the VRM fried and killed the i7 (and subsequently another i3 due to testing) in it a few days before the warranty ended(distributer cannot ship in time).

Hence, based on my experience, I would sau some Gigabyte motherboards might be the issue.

>>61744417
Agree that MSI is bad, my Z77 MPower literally failed its VRMs with a buzzing 'BIG BANG' a few days before the warranty ended, killing 2 CPUs(I was not told the PC failed violently, so I went ahead to put an i3 in). Well, at least the motherboard lived up to its brand name...

File: 3dc5dd05c3f60cee6d04497f65c3813a.jpg (32KB, 480x754px) Image search: [Google]

32KB, 480x754px

>msi carbon x380
>16gb 3200mhz ddr4
>ryzen 1600
>all from microcenter for that sweet 50 bucks combo deal
>all running fine with the latest bios
works on my machine my dude

Take it into the store and have them help you test it. You bought all the stuff there, so they should throw parts at it until it works.

>>61744683

I'm not going to let fucking geek squad troubleshoot for me.

>>61744680
x370

>install Windows 10
>it breaks your computer

And here I am with Windows 7 and an R7 1700, and it's been running flawlessly.

>>61744417
>Assrock
Please tell me you're joking, I worked in a PC Retailer and 80% of returns we get for MB are Assrock.

>>61744712

how the fuck

I tried installing windows 7 but my mouse and keyboard wouldn't let me get through the installation. it's like they werent even detected.

Run RAM at stock 2133 and see what happens

>>61744521
This don't buy the k5, every day is a struggle to see if the shit will boot at 3000mhz xmp. They should have spent some cash for a reset cmos button. Some times it takes 2 or 3 times to boot, bios interface is shit too.

>>61744717
I must have gotten lucky then, I have used a couple of their boards and they all worked fine. Like I said in the latter part of my post literally any part can be a lemon. A good chance those returns were people wanting to swap it for a board that lights up or has better OC'ing features, not necessarily a legitimately busted board.

>>61744726
ASRock made a patcher that slipstreams the USB drivers into your Windows 7 image and then dumps the whole thing into a bootable USB stick.

>>61744384
>>61744417
>>61744513
Got any evidence to support this? I have 2 PCs that run a Core2Quad with Gigabyte MBs and still work fine to this day. No idea about recent Gigabyte MBs, since I've been using MSI recently.

>>61744726
Oh the beauty of PS/2...

File: 45020-IMG_4958.jpg (52KB, 800x600px) Image search: [Google]

52KB, 800x600px

I fukken told you

>>61744764
Read the second part of my post you fuck head, I said any board can be a lemon. Those are just my personal experiences with motherboards.

>>61744764
Try running Windows 10 on them. My Athlon 64s with Gigabyte Motherboards runs XP, Vista and 7 fine. When I install 10 on them the installations are almost guaranteed to corrupt. I have to take 2-3 time to even install them because they simply corrupt halfway during installation. Media is fine since I use it to install on other machines which had zero problems.

>>61744712
>and it's been running flawlessly.
Except that you can't even run updates without hacks anymore.
>b-but i don't need updates
Can't wait for wojak/frog posts once you get your shit encrypted.

>>61744758
Can confirm this, used this method and it worked fine. I gave it up and """upgraded""" to botnet 10 anyway. I don't have the strength to fight microshaft anymore.

>>61744830
Fucking Windows 10 is worse than Linux.

>>61744337
This definetly happened.

>>61744774
does anyone actually use these?

>>61744781
rude

>>61744873
Sorry about that mate, I just don't have the patience for retards with zero reading comprehension.

File: Untitled.png (73KB, 1100x882px) Image search: [Google]

73KB, 1100x882px

>>61744337
>DDR4 16GB 3000Hz
Not a supported speed.

>>61744898
still rude

>>61744967
I'm running it at 2933. BIOS will not let it hit 3000.

I will try reinstalling Windows 10. If it hangs, I'll return the ram and exchange it for a different one. Thanks for pointing that out.

>>61744986
Stupid question but did you clean install Windows? Also the launch version is known to have issues.

>>61744986
Gigabyte boards is bound to have issues when overclocking, happened to me in 2 of my builds.
Take >>61744967's advice and try loading a lower latency, I'm sure it'll work by then.

>>61744986
I would still say that your motherboard is a suspect.

>>61745013

clean boot. definitely not the latest iso. probably very early.

tested it on my old i5 2500k build, just to fool around with Win10 to get used to it before upgrading, it ran flawlessly.

>>61745082
well, I don't overclock. Ram is 3000, runs at 2933 max. I'll try to lower it first.

File: chicks for free.png (3MB, 1920x1080px) Image search: [Google]

3MB, 1920x1080px

>>61744337
The watchdog clock thingy is usually OC instability.
Check the BIOS and try to disable anything that looks like the motherboard forcing some OC/performance tweak on the CPU and/or RAM. Start by resetting CMOS before that, and I guess for starters, reduce the RAM clock to some low level to make sure it is not unstable RAM.

>>61745165
You probably want a clean install of Windows 10 ISO updated for after the Ryzen launch to be honest.

>>61745082

Sounds like user error. I'm have a 1600 and AB350M gaming 3 motherboard and I haven't had a single problem running at 3.9GHz for over two months now.

>>61745181
>>61745175

everything is stock. I'll double check.

I never overclock. Never had a reason to.

>>61745165
get the microsoft media creation tool and download the win 10 pro iso straight from microsoft. load it to your usb drive and install it. there are a lot of updates since the version you're using, just disable the bullshit like most of us do. get dws_lite and spybot anti-beacon and all that good stuff.

>>61744717
Huh, I must have been lucky the past 6 times I bought an assrock mobo

>>61744337
Stop using shitty OS

>>61744462
Seconding tomahawk/mortar series. MSI got its shit together. Just werks.

>>61744859
Only because it was free

>>61744417
MSI is pretty bad, but lumping gigabyte with them is nuts. The longest lasting boards/gpus I've ever owned are gigabytes.

>>61744764
Recent gigabyte board owner here. It works.l, and has a comfy dac/amp. No issues.

>>61744859
>does anyone actually use these?
I've had them. Never bought, or used them though.

>>61744337
>Microcenter will let me return anything even if i cum on it
But will they let you return it if they see you used your cum as a thermal paste?

>>61744337
>using the smiley with a carat nose

>>61744337
make sure you're on the Windows 10 Creator's Update cause it has the drivers from Ryzen

my just newly built Ryzen 7 1700X system was crashing in Windows until it finally updated to creator's Update

>>61744337
Well at least you didn't buy an intel cpu.

>>61744717
ASrock is my most common board vendor next to Gigabyte and I've never had a board fail. I still have 1 working right now that is 12 years old.