cancel
Showing results for 
Search instead for 
Did you mean: 

QCode: 00 + 3rd PCIEx16_SW Lane switch blining + 4th no light at all

montekristo75
Level 7
Hello.

I am trying to make the following setup (without any overclocking) to boot stable and without issues Windows 10 64 bit Pro:

Motherboard: Asus ROG Rampage V Edition 10
CPU: Intel i7 6850k
GPU(s): 2 x Asus Strix 1080ti
EVGA Pro SLI Bridge 80 mm HB (2-Way).
The two GPUs are placed in the suggested PCI 16 slots and the appropriate jumper in motherboard has been set for 2 way SLO.
RAM: 4 x 16GB G.Skill Ripjaws V DDR4
M.2 SSD: Samsung 960 Pro 512GB
SATA SSD: Samsung 850 Pro 1TB
Cooling: No CPU Fan. 2 x 360 radiators. Fans connected to the NZXT Grid + fan controller hub
PSU: Corsair HX 1200 Watt 80 Plus Platinum

The latest UEFI/BIOS version and drivers are installed.

After individually testing the 4 memory sticks one by one I find out that one of them was causing boot issues.
I removed it and re-assembled my custom water loop.

So after a while I booted on Windows 10 and continued to prepare the working environment while still inspecting for leaks...

After some hours I felt safe in terms of leaking and I shutted down through Windows 10.
First time that I did something like that... (it was always restarts and hardware based resets).

I close also the PSU for 4-5 minutes in order to move the PC to its final position and when I fired up everything I am stuck with Q-Code: 00 and the 3rd from the top PCIEX16_SW Lane switch blinking and the 4th having no light at all.

Any suggestion s will be greatly appreciated.
2,759 Views
6 REPLIES 6

xkm121
Level 7
qocde 00 usually means either motherboard or cpu is dead.*

Nate152
Moderator
Hi montekristo75

Try clearing the cmos, if no help try reflashing the bios or try bios 2.

If you get it going and there's nothing connected to the cpu fan header, in the bios on the monitoring tab set the cpu fan speed to ignore.

Nate152 wrote:
Hi montekristo75

Try clearing the cmos, if no help try reflashing the bios or try bios 2.

If you get it going and there's nothing connected to the cpu fan header, in the bios on the monitoring tab set the cpu fan speed to ignore.



I will do what you said but currently I am mostly worried about the CPU... I hope it's not fried.

For the motherboard I couldn't care less since I came to the conclusion that is a crappy peace of junk and I will not be using it anyway even if what you suggest works.

Chino
Level 15
Make sure the screws for the monoblock aren't overtightened. Too much pressure can warp the motherboard and prevent the CPU from making complete contact with all the pins in the socket.

Chino wrote:
Make sure the screws for the monoblock aren't overtightened. Too much pressure can warp the motherboard and prevent the CPU from making complete contact with all the pins in the socket.


Your suggestions does not make much of a sense..
If it does then it means that I will not be able to trust this motherboard anyway.

Thank you anyway for the suggestion and your time though.

Chino wrote:
Make sure the screws for the monoblock aren't overtightened. Too much pressure can warp the motherboard and prevent the CPU from making complete contact with all the pins in the socket.



Just to give the last update...
Without any change in the hardware setup besides the lack of M.2 and the SSD and connection to the internet the motherboard posted normally outside of my case in my workbench.
Thankfully nothing is fried. This just empowers my perception of complete unreliability of this board.

I do not know if I can close this thread but you can close it or/and delete it if necessary.

Thanks anyone who tried or even thought to help.

best regards
montekristo75