[Noxxville7]

I just did a full 3DMark test run. My PC scored right where it should be (there is an official reference PC nearly identical to mine and they had nearly identical scores). I didn’t see any artifacting or anything unusual.

I am at a loss for anything else to look into, I think it is reasonable for me to deem that there is no problems currently and just be happy with my card, unless there is something I may have missed.

[Noxxville7]

Hello again.
I was unable to flash to UEFI, the Q-Flash utility Gigabyte wants you to use refused to accept the file saying BIOS checksum error or something along those lines. However, I was originally on F9 and updated to F12 (the most recent non-UEFI version) and did not see improvement. Since you’re on F10, I think we can rule out a compatibility issue.

I did however get the screen to go away, but it is more of a Microsoft approach. Under Advanced in the BIOS settings you can disable Fullscreen LOGO. It’ll give you the text based POST instead and there is no graphical glitch.

Sadly, I am highly doubtful that would help with your other issues. Sorry this was of no use, if I manage to get to UEFI I will let you know what the outcome is. I believe it is possible with a DOS bootable USB drive, but I’ve not personally tried yet.

[Noxxville7]

I’ve been unable to flash to the UEFI using the files provided on the gigabyte support site. Q-Flash always says Bios checksum error. I did however update my BIOS to F12 (the most recent non-UEFI) and did not help the issue at all.

I did however find the Microsoft approach to the issue – I turned of “Show fullscreen logo” in the BIOS settings to remove the image and stick with a text based format. There is no longer any strange graphical glitches on boot. This doesn’t necessarily solve the problem, but I’m not convinced it is actually a problem since I’m not having other issues.

I did see a video where someone flashed the UEFI version using a DOS bootable USB, but as far as the Gigabyte support site reads they want you to explicitly use Q-Flash. I don’t want to cause further issues so I opted to go with the most recent Q-Flashable version instead. Is this something I should try anyway? I would assume it could be ruled out to be a BIOS compatibility issue now as I was on F9, the user with the same issue as me was on F10 and I’m now on F12 and still saw the issue.

[Noxxville7]

Yeah it does seem to be GPU related but I’m wondering if you actually have two issues – GPU issues with artifacting and everything as one, but also a compatibility issue between the mobo BIOS and the card. Since I don’t have the other issues you’re having and I believe we’re on the same BIOS version, it seems reasonable that the jumbled load screen might be fixable with a BIOS update and if so, that could be one less thing for you to troubleshoot :-D.

I’ll do my BIOS flash in a couple hours and let you know of it solves that issue.

[Noxxville7]

Ahh, I meant your motherboard BIOS version. The jumbled screen you see at the start is actually the first stage of the POST operation – during the jumble is when you’d press delete to enter the BIOS, F12 to enter boot menu, etc.

When I used my original card the screen displayed properly, but the 290 royalace is causing the identical jumble as yours. I’ll be updating my BIOS later tonight to UEFI which also has a new splash screen and I’m hoping it will solve the issue.

I’ll likely be doing this within the next few hours and I’ll let you know what I end up with. I feel like I’ll have a slightly different looking jumble to take a picture of :P.

[Noxxville7]

Chachamara, can I ask what BIOS version you’re using? I am in the other thread with the exact same screen as you, although I haven’t had any artifacting yet and no issues with the drivers crashing.

I am planning on giving the UEFI version a go tonight but if you are already on that and have the same screen I don’t see a point in trying. If you aren’t, I will let you know tonight what the result is from that test.

[Noxxville7]

I am actually not using the UEFI version currently and am still on an older BIOS version since the UEFI was marked as beta. I can give the UEFI a try tonight after work to see if it helps.

I also do not currently have any of those utilities installed (never found them to be particularly useful).

I will try the UEFI tonight and get a screenshot of what it looks like then.

[Noxxville7]

I can confirm that it is not memory related as swapping them around did not solve the issue. As well, swapping back to my old card did not have the problem so I tried re-seating the 290 again and am still getting the same screen. The Gigabyte TouchBIOS screen is what is supposed to be displayed, looks similar to this:

[img]https://encrypted-tbn2.gstatic.com/images?q=tbn:ANd9GcTTDNNV-q32QxipRJGngBaNRSwSz0TYWBcvfdn942PrOrue_fzE[/img]

This screenshot is not of my setup, found it on google images since I have the 290 in again and can’t see the display. This is where I’d press delete to enter the BIOS configuration. Once this screen is done, the text screen that displays my drives shows up fine before loading me into windows.

[Noxxville7]

Thanks for the quick response.

This didn’t start happening until immediately after putting the new card in. I was previously using a 6850 and had no issues. I can perform this test later tonight when I get home if it must be done, but the rest of the PC aside from the video card is not new and have shown no issues up until installing the 290 last night.

[Author]

Posts