Another incompatibility between Enermax power supplies and motherboards

Unfortunately I must point out yet another incompatibility between Enermax power supply with a motherboard. :frusty: The power supply in question is an INFINITI 650W and a motherboard Gigabyte P45 DS4 (edit: think with all the Gigabyte P45). The problem occurs with difficulty initiating fake boot blocks and the inability to change any entry in the BIOS menu MIT as at the next reboot the card fails to apply the changes. With other power supplies everything works perfectly. Now I would like to know if there is same technical problem in Enermax even with the new MODU82+ ?

Excuse me if involved but I am interested in the debate because I have a modu82 + in rma arrived fault but because the store I work indicates, however, I have a Asus m3a32-MVP, I wanted to ask how can you be sure that no Enermax is defective? You could try it with another motherboard? I have not been able to because the modu82 + has fixed the connector ATX 24-pin, and I too have thus based on the fact that other PC power supply works perfectly.

What I also tried on a Gigabyte P35 (same config with only the Mobo different) and an Asus matx sk 939 and works well.

First I apologize for the delay in this genuine debate. Though proceeded to submit his application, citing data that we sent the head, which we reported that after the tests have not found inconsistencies in the start-up phase. Nevertheless, we want to deepen the test to verify exactly that assumption is no wonder truncated. Kindly give me more information about configuring this. In particular need of the serial ballast version of the motherboard, so that they can readily communicate, and help to solve the problem.

Q6600 cpu
Motherboard Gigabyte EP45-DS4
Ram 2x2gb Corsair Dominator 8500
Samsung 320GB HD
Nvidia 8800GT
INFINITI 650W Enermax PN801019920000 SN 71102605XX
if also the last two digits of the serial te mando in PVT

I took note of the issue, stated specifically in his last post. As I understand the problem occurs only when you try to change a value inside the BIOS itself, leaving all "factory" settings the machine starts up normally. Specifically it could be something in hardware that "freezes" the computer screen in the BIOS, but I think it is unlikely that depends on it.