Frequent POST failure with Q-Code "B1"

[E-AlRomaithi]

Dear All,

PCPartPicker part list: http://pcpartpicker.com/p/CfWLxr

CPU: Intel Core i7-5820K 3.3GHz 6-Core Processor
CPU Cooler: Corsair H100i 77.0 CFM Liquid CPU Cooler
Motherboard: Asus RAMPAGE V EXTREME EATX LGA2011-3 Motherboard
Memory: Crucial Ballistix Sport 16GB (4 x 4GB) DDR4-2400 Memory
Storage: Samsung 840 EVO 500GB 2.5" Solid State Drive
Storage: Seagate Barracuda 3TB 3.5" 7200RPM Internal Hard Drive
Video Card: Gigabyte GeForce GTX 970 4GB WINDFORCE Video Card (2-Way SLI)
Video Card: Gigabyte GeForce GTX 970 4GB WINDFORCE Video Card (2-Way SLI)
Case: NZXT Phantom 820 (Black) ATX Full Tower Case
Power Supply: EVGA SuperNOVA 1000G2 1000W 80+ Gold Certified Fully-Modular ATX Power Supply
Optical Drive: Asus BW-12B1ST/BLK/G/AS Blu-Ray/DVD/CD Writer
Monitor: Asus ROG SWIFT PG278Q 144Hz 27.0" Monitor

So I have this problem when I restart my PC, it fails to post and the fans keep spinning hardly. The only solution is to press the "Clear CMOS" button on my mobo, then the system will boot normally.
I am kind of a person who never shutdown his PC and keeps it running for months, and upon restarting the PC for installing new software or updates, it hangs and fail to post with Q-Code "B1" and the DRAM led switched ON. (Solid RED)
This made me believe that the problem is from the RAMs, so I reinstalled them and updated the BIOS to its latest version (ver. 3202). yet the problem still exists.
However, if i restart my PC frequently (after clearing CMOS on the first post failure), the PC boot up normally. But if i left my PC running for more than +-2 days, upon restarting it fails to post and I have to clear CMOS again.
My PC is running on stock speeds, although i did some CPU overclocking in the past.

With or without XMP the problem still exist. Everything else is set to auto.

Edit #1: Removing and installing all the RAM sticks is an alternate (temp) workaround to get my PC to post. (However, clearing the CMOS is much easier and yet the problem still exist). My assumption now is "If all modules work alone then the logic conclusion is that motherboard make a problem when communicating with the memory when in quad channel or some of the DIMM slots are not good. "

what do you guys think ?

I hope that I made it clear and sorry for many grammatical mistakes.

Regards,

[Chezpuf]

I had a similar problem when I built my system (5820k, ASUS Sabertooth), sometimes it booted, sometimes it didn't, sometimes clearing cmos worked, sometimes moving RAM sticks worked. Turns out the CPU was defective. I figured it out by replacing every other component to no avail, and finally going out and buying another CPU to test the system with.

[E-AlRomaithi]

On 7/2/2016 at 2:59 PM, Chezpuf said:

I had a similar problem when I built my system (5820k, ASUS Sabertooth), sometimes it booted, sometimes it didn't, sometimes clearing cmos worked, sometimes moving RAM sticks worked. Turns out the CPU was defective. I figured it out by replacing every other component to no avail, and finally going out and buying another CPU to test the system with.

Thanks for sharing your experience!

 

Well the problem was fixed by changing the way that CPU fans were blowing air, previously it was blowing the air inside the case and after switching the sides no more post failures! I don't know why i did this and why it worked !

 

however a new problem occurred were my PC unexpectedly shutdown (like a power loss) and restart. This happens randomly, when idle, gaming or under load at least once a day.

Windows event viewer shows Event ID (41) Task Category (63) which is not helping much.

 

I did some test to figure out what causing this problem.

Here what i did:

1. Tried to update the BIOS is already updated to the latest version.
2. Ran Firestrike with these results: http://www.3dmark.com/3dm/13163608

3. Furmark stress test for more than 20 mins with max gpu temps of 65 C. (Normal)

4. Intel Processor Diagnostic Tool passed.

5. Ran Mem86 test for 4 hrs, passed with 0 errors.

 

What to do you think is wrong now ?