Oh... is that what the check for updates option is on the installer? I assumed that only applied during installation, so it would get the latest fixes from the AMD servers while installing.
D'oh!
I think it's a poor design choice, deliberately deceptive, and they ought to just put a toggle in...
I tried that. There's nothing that I can toggle there.
The "Check for Updates" button just tells me that a new version is available.
The "Preferences" and "Notifications" screens don't have anything to turn it off either. From "Notifications" I can only view and dismiss notifications.
Curious if anyone else is experiencing this and what (if anything) you did about it.
I'm running Windows 10 x64 and previously had the Crimson 16.3.2 WHQL driver package. Then about a week or so ago I started getting upgrade notifications from Radeon Settings that a new version was available...
I have an Audigy X-Fi card laying around and was also concerned about finding stable Win10 drivers when I decided not to use it. As it turns out the on-board audio on my motherboard is nice and has noise shielding, too.
Ultimately, I realized that the weakest link in my setup is my speakers...
I don't know if you have access to any good computer stores nearby, but in my experience shopping at the local MicroCenter is invaluable when building a new PC. They have a no-fuss return policy and I can usually exchange parts to try out with no risk (and most importantly, no RMAs or shipping...
At the risk of jinxing myself or speaking too soon, I think I might be stable.
It's been about a week now since I updated the driver for the LPC controller in Device Manager, and I haven't seen any blue screens. I never unplugged my USB gear so everything is as it was (including the GPU)...
Just keep in mind that ignoring the problem or working around it (with a USB DAC) means you won't know the source, and leaving it this way could cause other kinds of failures to creep up down the line.
That doesn't mean anything, necessarily. An issue could have been introduced when you were working inside the case.
Anyway, hope you get it worked out.
How many GPU's are you running? You might try removing one if you're doing SLI or swapping them; see if the problem follows the GPU or a specific PCI-E slot.
Might also try removing all the GPUs and testing with just the Intel iGPU.
I can tell you that the audio setup on that board is pretty good because I have the same setup on my GA-Z170X-UD5. I don't have this issue.
My first guess, assuming you don't have a bad board, is something is causing interference in your case.
It's a Rosewill. Actually I've got two hubs. I forgot the one built into my Dell monitor.
I think those memory addresses would be the same. The theory right now is that one of my USB devices (or hubs) is acting up, or there's a bad interaction with the driver.
Everything's still plugged in...
I might have a clue about where my problem area is. Here's my thought process...
Last night I turned the driver verifier off, and this morning I got another BSOD at startup. As before, it's the IRQL_NOT_LESS_OR_EQUAL message; the one I'm hunting. Great!
Comparing it with the earlier...
This is the kit: http://www.newegg.com/Product/Product.aspx?Item=N82E16820233752
CORSAIR Vengeance LPX 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 2400 (PC4 19200) Memory Kit Model CMK16GX4M2A2400C14
It's running in the one and only XMP profile it has, XMP-2400. Timings & SPD info below:
It...
Alright, Intel RST is gone. Back to default AHCI driver.
Turned driver verifier back on. Let's see :) If the crashes go away then I'll add the GPU back in.
By the way the performance difference between the two AHCI drivers seems pretty small. I might just keep the MS default.
Intel on...
I'm turning off the driver verifier because it's catching far too much and I'm not sure what's related to my issue and what's not.
When I booted up today I got this:
Memory corruption? Bad RAM?
Or just some driver writing where it shouldn't?
:\
I spent the last few hours messing around with the windows driver verifier tool and systematically disabling any that caused verification errors. Well- it's messy, but I learned some things.
First of all, I highly recommend these tools:
- "sfc /scannow" in Administrator console (to fix...
I didn't have much luck on the Gigabyte forums when I was asking about how to get the F5 BIOS loaded. One of the regulars there, who I felt was trying to be genuinely helpful, could only offer that I should submit a bug to Gigabyte. (which I tried and failed because the site wouldn't let me...
Another thing I noticed is that most of the crashes seem to happen on bootup, after the computer had been shut down the night before. I use Power->Shut down instead of Power->Sleep because I noticed that my computer never stays asleep for very long. The few times I've tried I always come back...
I get one about every few days, or once a week. What's annoying is that it's not always the same code. I don't remember having as many issues with my Asus P6T Deluxe, but at this point I'm not able to point at any one thing. Hard to say.
I just downloaded a tool called WhoCrashed and ran it...
@UsandThem Thanks. I'm familiar with the reliability monitor but I need to spend more time digging into the core dumps.
@vailr Thanks, I've already got the latest f/w (MU02)
I don't remember exactly but I've had it at least a couple years. Before I upgraded to Windows 10 recently I was running the Crucial Storage Executive app, and the drive was in good health. It's at 98% wear.
I'm running the Intel RST app now and it's also not showing any errors...
I'm not having good luck with stability. Fired up the desktop tonight and got a crash with error code 0xa (IRQL_NOT_LESS_OR_EQUAL). I've seen this one before.
After restart the system did an automatic disk check on my C: partition.
Starting to wonder if my SSD is not liked by this...
Alright, about 9 hours to run Memtest86 and it's a Pass. No errors detected. That's with XMP Profile1 and no other modifications.
Good news: I've got F5 installed! Thanks, Edrick. I'm going to run this for a few weeks with the XMP Profile and see how it goes.
UsandThem, there's a new...
Running Memtest86 now... let's see what happens. If it passes then I'll bump the timings down and give it a couple weeks to see if the BSOD's go away.
Kinda hoping it fails the test so I know what to replace :-/
Yeah, I did the clean install from USB and set up my partitions from scratch. Also using build 1511 with the latest (March 8th) updates.
Since we're using the same F4 BIOS (I really need to get into the habit of saying UEFI) and the board is still at revision 1.0, then I guess it's got to be...
Hey, as an aside, are you seeing any crashes in Windows with this board?
I just got a blue screen today with bugcheck ID 0x0000001a (MEMORY_MANAGEMENT). The last BSOD I got was on 3/13 (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED).
It's relatively stable but I do get the occasional BSOD and I'm not...
Understood; that's a sane argument.
Any kind of logic bug is just unsettling to me, however statistically unlikely I am to encounter it. It reminds me of the old Pentium FDIV bug: https://en.wikipedia.org/wiki/Pentium_FDIV_bug
Sorry, the only USB3.x device that I own so far is a 3.0 thumb drive. I've used it a little bit on the front ports (mostly to install Win10) and it seemed to work fine.
Were you able to submit a ticket? I tried to register on Gigabyte's website to tell them about the F5 issue, but it won't...
Same result with this one. It started to flash and half way through it failed.
Either it's a bad BIOS or there's something messed up on my end. If anyone else has had success with F5 please chime in.
It's supposed to have additional fixes, such as the Skylake bug found in Prime95. I'm not sure why they didn't list that on their official website, but they did previously (in one of the F5 betas). I think maybe they omitted it in the notes or the website is wrong since they updated it recently.
Is that a beta?
I don't trust the F5 binary at this point enough to take a risk with it. I'll be looking around a bit for some other peoples' experiences.
Hopefully in the meantime Gigabyte will fix their website. F5 is supposed to have a number of fixes, including the Prime 95 Skylake bug...
Thanks for the suggestion. It didn't work, but I learned something doing it... it seems the F5 BIOS they posted is invalid or broken!
The @BIOS tool could not even find an F5 version from the Gigabyte servers. When I told it to grab the latest, it said F4 was the latest and that I already...
I am lucky enough to have a MicroCenter nearby, and they usually either match competitor prices or they run periodic sales or combo deals which are much better than NewEgg or Amazon.
So I bought my last couple of motherboards and CPUs from them and as luck would have it, I got a bad Gigabyte...
Hopefully someone's been through this already and knows what to do.
I'm trying to update the BIOS on a Gigabyte GA-Z170X-UD5 from F4 to the newly released F5. I had previously tried to upgrade to the beta BIOS (F5j) before this one was released and had the same results. The BIOS seems...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.