Badaxe 2 Fault

Soldato
Joined
20 Oct 2002
Posts
12,012
Location
Derby
I dont know if anyone else has noticed this but if you disable the second S-ATA controller on the motherboard the HDD Activity light just stays on constantly... Enable the Second controller and it works... Intel have been aware of this since November but done NOTHING about it... What a suprise... :rolleyes:

Anyone know of a workaround or a modded bios?
 
Yeah i found something on another forum that says it was supposed to be out on the 8th of this month... It is just the light but a bit of a pain to send a customer a machine that either a) has the secondary controller enabled that gives error messages and causes the machine to boot up slower or b) not have any hard disk activity led.
 
YEY... It sorts the HDD Activity out... But then causes a BSOD when installing Microsoft Windows XP Pro x64. The error is PFN_LIST_CORRUPT... I have contacted Intel on this matter. It also does it with bios version 2431 and the HDD LED Activity is not fixed in that. I can back off the bios to 2330 and it works fine.
 
I have done a little more investigating and it appears to be some sort of 64Bit Fault.

If i use BIOS 2330 i can install XP Professional 32Bit, XP Professional x64 and Vista Business 64Bit But the HDD Activity LED does not work (Stays on constantly) if the Marvell controller is disabled.

If i use BIOS 2431 i can install XP Professional 32Bit with no problems but if i try either XP Professional x64 and Vista Business 64Bit I get a BSOD on both occasions either right after i install the RAID/AHCI drivers or windows installs the IDE driver it halts. The HDD Activity LED Still Does not work.

If i use BIOS 2507 It exhibits the same problems as 2431 but the HDD LED Activity actually works...

UPDATE.. And on even further investigation... It apears as if its a problem with the QX6700's. If i disable Core multiplexing in the BIOS everything works ok...

UPDATE2.. If you disable Core Multiplexing in the BIOS then it actually works.

:(
 
Last edited:
We are waiting to here back from Intel. Another customer of our distributer has has exactlly the same fault but as no-one else had reported it till i did they just dismissed it... :rolleyes:
 
Back
Top Bottom