MAP_Finder

I suppose I'll need to look into it some more find out for sure then. Worse case is I go with a 980x which clocks slightly lower and costs a bit more but overall won't effect much.

Nice! For some reason they are a lot cheaper then the 990x and if I remember correctly they also clock slightly higher.

So I'm looking at some X58 motherboards, and managed to find a decent deal on the Foxconn X58 Flaming Blade GTI. Now I know that X58 is a dead platform and that the CPUs are very power hungry and don't get a lot of work done in 2021 and that I should just go with a Ryzen system or whatever but I think it would be a fun project. So now the question: as far as I know, it was up to the board vendor to determine rather they wanted to support LGA 1366 Xeon processors like the X5690, but because Foxconn no longer makes motherboards I can't just go to the QVL and see if it's compatible. Does anyone know if the X5690 is compatible? And if it is, I'm 90% sure it's overclockable, but just to make sure, does anyone havea 100% on that? And side question, would the X5690 and 12GB of 1600MHz DDR3 bottleneck a Vega 64 too badly?

The yellow is only on a few contacts underneath the GPU cores

So I bricked my Pro Duo. The HBM clock on these cards is locked so the only way to change the clock is through the BIOS, I was stable at 575MHz with 1.275V on the memory and raised the clock speed to 585 a few days ago and the card wouldn't boot anymore. That's fine I have a dual BIOS right? Well, apparently that isnt working for some reason. I tried the refreshing the stock BIOS on with no luck, tried shorting BIOS rom pins, and tried the SPI Flash tool were you directly connect to the ROM all with no luck. Now my only option seems to be a ROM replacement but I noticed these contacts covered in some kind of yellow strip. Does anyone know what these contacts are for or if they might help in some way with what I'm trying to do?

Oh, yeah I for some reason figured I would need the graphics card installed for that but that wouldn't be the case unless the driver somehow physically changed the firmware, thanks for that time saving tip Lol

Looks like I need to install Ubuntu and install drivers then, won't boot in Crossfire with my R9 Fury X into Windows and the driver support for Linux Mint is non existent.

This is the bluescreen the 390xs cause

Something like Something like APPLICATION_NOT_HANDLED but I'll check for what it says exactly in a minute

So I picked up a pair of completely untested R9 390xs for really cheap and they came in so of course the first thing I did was try them as they where. It showed a display, it booted normally into Windows, then bam! Bluescreen as soon as I go to put in my password, I've fixed a number of broken graphics cards but I've never seen this before and the other 390x did the same. I swapped over to the graphics card I was using before and it booted and did things no problem. Put one of the 390xs in, booted to Linux, and it runs completely fine in Linux, threw the other one in to Crossfire test them and it's again, completely fine in Linux. Well, I had a spare hard drive so I decided to make a new Windows install on it and midway through the install it gets stuck on a bluescreen loop, bluescreens, restarts PC, bluescreens, restarts PC and so on. Does anyone know what might be wrong with this? I would take the cards apart to look for any physical damage but if they where damaged in any way I don't know why they would work perfectly fine in Linux, also I don't think it was my Windows install because it would bluescreen while installing Windows on a blank hard drive.

Well I built my computer only last year but when I did I found a $80 R9 Fury X to put in it and I don't plan to upgrade for a while, as long as I get 720p 60fps I'm happy

I would imagine a quad core i5 to bottleneck the RTX 3070 at least slightly, if you keep the same platform but upgrade to a 4th gen i7 the extra threads should help with that and you can find thoes chips used for under $100.

I do have the card udervolted and overclocked actually, 1,100MHz core with 545MHz HBM at 1.194V V-core over the stock 1.240V I might be able to drop the clocks down to 1,000MHz and do closer to 1.1V though

The pump is on the bottom with the RAD/RES mounted on the rear or the case like an exaulst fan. Apologies for the poor photo quality, I used flash instead of taking the side panel off.

So I might be one of the only ones left at this point but I'm running a R9 Fury X with the reference watercooler and have used MSI Afterburner to set a custom fan/pump curve to make the pump stop at idle. I know that it is inevitable that eventually the AIO will run low on fluid and create all kinds of thermal and acoustic issues and I'm starting to see (and hear) signs on that already so my solution was to set that custom fan/pump curve to make the pump do the least amount of work it has to, that means even under full load the pump normally doesn't exceed 1,000RPM. Now I could just turn the system off instead of letting all the remaining fluid in the AIO flow through the graphics card and eventually go to evaporation and condensation but the issue with that is my only boot drive is an old and very slow HDD that takes a long time to boot then sees disk utilization pinned at 100% in task manager for five minutes after. Anyway with all of that said long story short should I deal with the excessive noise from my AIO running out of fluid, deal with the long wait and constant 100% disk utilization after boot, or deal with an idle temperature of about 45°C due to not running the pump under idle? PS load temperature generally stays under 70°C without much trouble from the struggling pump Any feedback is appreciated, thank you!