Jump to content
Corsair Community

AX series: Moving the connector to power on


Rockzz

Recommended Posts

Hi, within customers having an issue with their power supply, many encounter the exact same issue.

 

Issue:

After a period of flawless functioning, the PC doesn't power on anymore the normal way (short press on the PC case power button). The motherboard and power supply LEDs are on by the way. A workaround method achieves powering on the PC: moving the power cable connector into its slot, creating some kind of short-circuit.

 

Affected users (more to find within the related threads):

 

RMA expectations:

  • Beeing notified by the Corsair support team when the issue is understood, and when a replacement part is proven not to fall into it again
  • Granting a full RMA to users for which the Corsair support team will have validated this specific issue: full RMA means Corsair will take care of replacing the product out and back from and to the customer home, or grant them both the shipping and returning costs to be refunded

 

Experiments of affected users in order to find causes:

  • Replacing the faulty power supply with another one and checking the PC powers on and boots up fine: Done - OK
  • Disconnecting the wall outlet, purging electricity out of the PSU by keeping the PC power button pressed, switching off the PSU power button, waiting 10 minutes, wiring up again, waiting 15 minutes to ensure electricity to be available into the PSU, pressing the PC power button and checking it powers on: Done - Not OK
  • Using the faulty power supply in another PC and checking the other PC does not power on too: To do

 

Side-notes:

 

Post any related info, I'll update the main post :biggrin: Also, please provide your motherboard, processor and memory specifications, as much precise as possible, using this template:

- PSU: Corsair AX650 Modular (bought in France)

- Motherboard: Gigabyte GA-EP45-DS3P - BIOS Award Modular EP45-DS3P-F9c 2009-09-03

- Processor: Intel® Core2 Duo CPU E8400 @ 3.00GHz - CPUID revision: 0001067Ah - Microcode Update Revision: A07 - stepping E0

- Memory: DDR2 SDRAM - G Skill F2-6400CL5-2GBNT (2 x 2GB), Transcend JM800QLU-1G (2 x 1 GB) - Dual channel

 

What Granny Jam thinks of it: "YARRR! Help me you faithful Corsairs, this shark is gonna crush my board in no time!"

Granny Jam tips to the team: "You assemble PSUs when you're on sea!?! *YARRRLCOPTER* This is dangerous. Now equip your boots please."

Link to comment
Share on other sites

Rockzz - Hardware specifications:

- PSU: Corsair AX650 Modular (bought in France)

- Motherboard: Gigabyte GA-EP45-DS3P - BIOS Award Modular EP45-DS3P-F9c 2009-09-03

- Processor: Intel® Core2 Duo CPU E8400 @ 3.00GHz - CPUID revision: 0001067Ah - Microcode Update Revision: A07 - stepping E0

- Memory: DDR2 SDRAM - G Skill F2-6400CL5-2GBNT (2 x 2GB), Transcend JM800QLU-1G (2 x 1 GB) - Dual channel

 

PSU voltages:

- BIOS: +3.3V: 3.312V

- BIOS: +5V: 4.972V

- BIOS: +12V: 12.048-12.112V (changing from one value to the other constantly, every 2 seconds approx.)

- Windows - idling: +3.3V: 3.312V

- Windows - idling: +5V: 4.973V

- Windows - idling: +12V: 12.176V

I've somehow mitigated the issue, and there's indeed some incompatibility between the PSU and the motherboard involved (who's the culprit? I don't know):

 

- On a Gigabyte motherboard:

 

> - Probable cause: A bad mix over time between the BIOS, its DMI data and its CMOS data, or a bug in some AHCI Bioses causing this bad mix, when you switch the "SATA mode" BIOS option from its defaults "IDE" to "AHCI"

 

> - Steps to follow:

> > - You don't have to clear the CMOS with the motherboard button if any

> > - 1/ In the BIOS, backup your CMOS settings/profiles if precious, on HDD, by setting the BIOS "SATA mode" to "IDE" first (needed to see your disk and partitions in QFlash, you need a FAT32 partition on the target disk, only those are visible through QFlash). Note that the following step will wipe all your CMOS profiles, so load each CMOS profile you want to backup, and save it to your disk

> > - 2/ Through the BIOS QFlash utility, overwrite your current BIOS with the original BIOS file for the version you're currently using (example: f9c). In the process, set the QFlash option "Keep DMI data" to "Disabled", and set the QFlash option "Reset to default CMOS" to "Enabled". Overwrite the BIOS with QFlash, reboot, access BIOS to set back "AHCI" if you were going this way previously, and let your operating system booting, by ensuring to see the BIOS "Update successful" and "DMI database initialized" messages (this is the important and relevant part)

> > - 4/ Power off your PC through the operating system functionality, wait for fans and stuff to stop, a few seconds let's say

> > - 5/ Press your case power button: magic, it powers on your machine again, without having to move the power cable connector! Try it multiple times to ensure fix is solid, it seems so

 

If you're affected with the issue, please say here if it works or not for you ;)

 

Observations on the motherboard when the issue occurs:

- Machine is powered off, the PSU power cable is wired and a press on the case button triggers no power on: The MB S5-S0 system power states LEDs are off, only one is on, and it's red still (S5?)

- When pressing the power button short or long and releasing it, no power on, and the same LED is still red still

- When moving the power cable inside the PSU, having some quick PSU power on, with blue LED flashes appearing, but not going on cause you didn't insert the power cable fully at this moment, the same motherboard LED goes orange still (S4-S1?). After those quickPSU power-ons-with-blue-LED, the motherboard LED is still orange still, as if it has acknowledged a signal

- When moving the power cabled again, and managing to solidly plug it "in time", that's when the power goes on and the PSU blue LED flashes, you get a persistent power on, machine starts it's normal boot sequence, and the motherboard LED goes green still. The PSU blue LED is blue still

 

On the Corsaire team side, I think there's something to investigate ;)

-----

 

 

Edit - 2014-04-24:

-----

Fix is still solid after 10 days.

-----

 

 

Edit - 2014-05-26:

-----

Still working after a month. Closing main thread, feel free to comment if you're concerned with the issue ;)

-----

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...