X58 failing motherboard help

They're only stuck on with some double sided tape.
Get it done :D
Will do next time I pull the case panel off but its not as easy due to how much hardware is in the PC :eek:

AIO GPU Kit (Kraken G10 + H55 with dual 120mm fans)
6 case fans
7 SATA drives
Noctua HSF + 140MM fan is blocking pulling 2 of the Gigabyte Blue covers off unless I pull the mobo & remove the HSF to gain access.

Lots of cables only way to pull the blue covers is for me to almost remove the motherboard due to how tightly its all packed in!
 
This is very interesting, I bought a new X99 system because I was having exactly the same problem with my X58 system which uses this exact board. I still haven't sold it, which I was planning to do. Might try replacing the TIM as you did.

NB temps were always fine but may be the Mosfets or Southbridge causing the problem. Although sometimes the problem would occur in quick succession, other times it would be weeks between it occurring so will keep an eye on this thread to see whether it re-occurs for you.
Probably Southbridge mine had melted sticky Thermal Pads residue all over it one I cleaned it up & put some proper TIM on its been fine eversince!

Mosfets are a different matter I just left mine as is with the thermal pads they looked fine. Its very hard to replace & use TIM way too small/fiddly & dangerous you get the wrong TIM material in there bye bye the mobo it will probably short or blow due to all the trace wires on the mobo in that area!
 
Currently having the same dilemma myself, running an Asus Rampage 3 Black Edition board with a i7 980 hex and 24gb ram.

The voltages as reported in the bios or windows apps for the 3.3v, 5v and 12v rails are all under the exact figure they should be, and specifically the 3.3v will drop over time to around 2.8v at which point I loose display and have to shut off manually, disconnect the power cable and remove the 24 pin connector from the board for a few minutes for it to reset. Will depend on time from a month to a couple of times a day and never got to the bottom of it, but more recently it's got worse, daily rather than monthly.

Very annoying tho as it's such a cost to change board cpu and ram all at once to upgrade.
 
Just another update. It just crashed again after almost 4 weeks. Same error 41. No warning just restarting.

It could well be software but as it did the same thing on a brand new Win 10 install (I have 4 OS on a multiboot partition 1xSSD for each OS).

Oh well I will see what happens I guess :(
 
Just another update. It just crashed again after almost 4 weeks. Same error 41. No warning just restarting.

It could well be software but as it did the same thing on a brand new Win 10 install (I have 4 OS on a multiboot partition 1xSSD for each OS).

Oh well I will see what happens I guess :(

Well that's a pity that it happened again. As I said, sometimes the issue would take weeks to manifest itself, other times it would happen several times a day. I doubt it's a software issue unless it's a bug with the F13 BIOS. My problems started a month after updating, which I assumed was a coincidence. Was this happening when you were using F12 as well? I assume this was the BIOS you upgraded from.
 
Last edited:
Well that's a pity that it happened again. As I said, sometimes the issue would take weeks to manifest itself, other times it would happen several times a day. I doubt it's a software issue unless it's a bug with the F13 BIOS. My problems started a month after updating, which I assumed was a coincidence. Was this happening when you were using F12 as well? I assume this was the BIOS you upgraded from.
Yep with F13 bios. F12 makes no difference.
Google this eventviewer GUID code: {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

Lots of people have this issue on Win 7 some of us think its an old bug related to dates/time & or MS stealth software. This is on a lot of different machines of varying ages!
 
Last edited:
Mobo is 99% retirement home for long serving mobos :( it now does this most of the time so its too risky to use anymore :eek:

Looks like a dodgy cap or some other component failing rapidly now. At least I got another few months out of it!

I have another Gigabyte X58 mobo I am using now just need to buy a cheap working X58 replacement for the other PC!!
 
Last edited:
1 other thing I want to add is that the dual bios on these boards are soldered on so you cannot easily replace (I think mine is corrupt beyond repair).

You can however short pins 1-2 on Bios chip #1 (with some wire) then it will force the motherboard to use Bios chip #2! Be very careful though its hard to work in such a small area!!

You can also force it via being very fast & holding the clear CMOS button down as you power the PC off but this is hit or miss the timing is hard to achieve.
 
Last update.

I replaced this for a similar Gigabyte motherboard I bought from an auction site real cheap as non working or spares only (I gambled it would work and it did) & everything works 100% so it was definitely the motherboard got fried somewhere.
 
Just want to update this to say as a last resort I bought a £10 Xeon skt 1366 CPU 10 months ago & the failing X58 motherboard has worked perfectly eversince with it in!

Which leads me to believe the unreplaceable dual bios (soldered directly to the mobo) was corrupt after all & putting a different CPU in somehow allowed it to become stable :eek:

So if you have a dodgy X58 with similar symptoms buy a cheap Xeon see if it fixes this type of issue.
 
I'm not sure if your mobo, like my gigabyte x58, has blue metal panels over the board mounted heatsinks with GIGABYTE slapped on them.

If it does... rip those things off and chuck em in the bin and see the temps drop 5C


I have a x58 UD3R mobo and I was getting the same symptoms as the OP a while back. I checked the temps and I think it was the ICH chipset temp was hitting 95 degrees so I removed the blue plate on the heatsink and attached a tiny fan on top and after this temps never went over 65 degrees and I have had zero random reboots
 
Back
Top Bottom