Cold boot failures x58A-ud3r Rev2 bios FB

[Dark Mantis]

They all look pretty much the norm to me.

Is there anyway of replicating a cold boot?

Short of spraying it with CO₂ or similar I think you will just have to wait. It's just the joys of testing

I was just so close to doing the "wellie in the fridge" bit

[theboyfold]

I'll try using it to do a few things and boot it up again tomorrow morning.

Thanks for your help with this, very grateful!

[Dark Mantis]

You are very welcome.

[theboyfold]

Guess what. Blue screen!

Fingers crossed the retailer will also find fault with this board.

[Dark Mantis]

Yes I think that is your next step. Good luck.

[fatbobuk]

Had to go back to FB BIOS still have problems but a lot less BOOT problems than FC1 FC2 or FC3

[Dark Mantis]

hi Bob
You have my sympathy. It is a real pain when these problems go on and on and there seems no resolution but I am still sure it is the BIOS that is the trouble. Hopefully they will sort it out soon.

[d3fiant]

My earlier post was incorrect, it wasnt FB16 that bypassed the cold boot BSOD for me, it was FB11.  This bios doesnt completely solve the issues, just stops the BSOD.  The trade off is that just after verify DMA step I get a message saying recovering lost dram and then it reboots fine the second time every time as opposed to the several BSOD.

I did RMA my mobo and retailer returned no fault found and charged me for it   Basically they did the tests in IDE mode whereas I use AHCI because I have an SSD.  Very odd and very frsutrating

[Dark Mantis]

Yes very frustrating and happens very often. As a general rule you must make sure that the retailer or whoever is testing the board knows the fault and how it is setup. Best to attach a note to the board with any special particulars.

[theboyfold]

So I've RMA'd my board, will let you know what they say.

In other news, I've just heard back from Gigabyte Tech Support, saying they are sorry they have taken so long to get back to me, do I still want them to answer my question!!

[Dark Mantis]

Sounds about right. They probably know that you've been on the forum.

[theboyfold]

HAHA! Maybe

I do hope the RMA finds something, otherwise I'll be stumped as to what's actually wrong...

[FunkyErn]

Hi guys - I am back and so is my RMA old motherboard with new replacement Corsair TR3X6G1600C9 memory  Turns out it was a thermal problem with the memory on cold boot - once it warms up it was OK. The tech support guys confirmed this in their tests and it worked fine with their test RAM. I got them to test it out with the replacement RAM before sending it back. I have a new set of Corsair TR3X6G1600C9 - same model with different serial numbers (I had noted them done before sending back).

So far so good - it booted fine last night after reconnecting everything. There were some POST errors warning the hardware settings were different to the BIOS screens - I cleared the CMOS and loaded the optimised settings - this now seems fine. I have just cold booted this morning straight into Windows and then Memtest86+ without any issues!!

It feels too good to be true... I will wait a few more days before celebrating - it has been over 6 weeks now to get this far. Basically a dodgy chip on one of the DIMMs caused such a nightmare and hassle.

I will keep everyone posted. If anyone has similar issues I suggest RMAing the board and RAM back to the supplier along with a detailed note of how to replicated the prolem and your setup (as recommended by Dark Mantins previously).

[Dark Mantis]

Well I am really happy for you FunkyErn. You deserved some luck after all those problems. Fingers crossed mate.

[FunkyErn]

Well I spoke too soon - I appear to have a new problem. While MemTest86+ runs fine from cold boots, when I start up Windows and login I get BSOD BCCode 101!!!! This has happened several times now. I am using the optimised defaults with RAM settings of 8-8-8-20 (CmdRate 1T). I have since changed to the actual RAM settings of 8-8-8-22 (CmdRate 2T) - has been working fine since but cannot be sure it is resolved yet. Will need to check again when I get home tonight.

What exactly does "A clock interupt was not revieved on a secondary processor within the allocated time interval." mean? What should I be looking for? Any ideas?

I did verify there weren't any bent pins before re-inserting the processor. I am currently on bios FB - is there any point flashing to FC3?