Hi,
I have recently thrown together a new pc with the EX58 Extreme and intermitantly I have the exact same issue as the guy in this thread
( http://forums.tweaktown.com/f69/ga-e...failure-29087/ )......with a few exceptions.
First my system:
i7 920 D0
ULTRA-120 EX-1366RTF
EX58 Extreme - E9d
12GB Corsair 1600MHZ DDR3 (HX3X12G1600C9)
Gigabyte Odin 1200 Pro
Gigabyte 4890 1GB
- yes I know for the ram, supported is only 1333Mhz and below for 6 x 2GB in this board but I've been running it @ lower then 1333Mhz and have experienced the same issue with only 3 x 2GB sticks in the system )
Issue first occurred after initial hardware build (so pre-software), any change in bios settings resulted in the 'lockup' as per the linked thread above. When i say any I mean from changing IDE / SATA settings to resetting it to failsafe defaults.
Updated the BIOS to E7 after this and yielded the same results.
Updated to E9d and am now able to OC / play with all settings 85%-90% of the time -sometimes after a simple restart the pc will still lockup and I just have to wait it out.
At times I have been able to speed up the 'cool down' of this lockup by removing ram sticks (so going from 6 x 2GB -> 3 x 2GB) and having them in the correct white 1/3/5 dimms.
Which initially lead me to think it was the ram, so I tried removing all of the ram to see if it would power on and no cigar :(
I've also tried this PSU on another board ( yee old Intel PII board ) and that powers up without an issue.
I have also had the system running outside of the case on a table and experienced the same issue.
Inside my case the board is on 9 x risers that came with my case and on top of each I have placed an insulating washer, all screws are screwed in tight (but not too tight) also with insulating washers.
May sound over kill but I wanted to make sure it wasn't shorting anywhere.
Apart from the above there is another issue which may or may not be related...
With the 12GB of ram installed it will sometimes register as only ~8GB (BIOS/WIN).
Removing 3/6 sticks (so down to 6GB) can also suffer the same issue and the system will only see ~4GB (BIOS/WIN)
- I am running XP x64 and can normally see all 12GB.
What happens is I'll restart the system or turn it on for the first time and its almost as if the system ignores a stick or two but after a few restarts and swapping sticks around it works fine again (this is when all slots are populated, when I am using only 3 x 2GB I leave them in their correct 1/3/5 dimms)
Just to round up this wall of text, I am still able to use my system as per normal and have had no issue installing the OS, these issues are just happening off and on but most commonly after a change in the bios (last time it happened I had changed the voltage to the ram 1.5000V -> 1.540V ~my ram is rated @ 1.65v @ 1600Mhz and I was running it at 1440mhz) or a simple restart.
If I overclock my system to stupid extremes it doesn't do this kind of lockup, it just restarts like normal has a winge after a few restarts and fixes itself. So I'm fairly confident its nothing like that.
Thanks in advance and sorry for the wall of text :P
I have recently thrown together a new pc with the EX58 Extreme and intermitantly I have the exact same issue as the guy in this thread
( http://forums.tweaktown.com/f69/ga-e...failure-29087/ )......with a few exceptions.
First my system:
i7 920 D0
ULTRA-120 EX-1366RTF
EX58 Extreme - E9d
12GB Corsair 1600MHZ DDR3 (HX3X12G1600C9)
Gigabyte Odin 1200 Pro
Gigabyte 4890 1GB
- yes I know for the ram, supported is only 1333Mhz and below for 6 x 2GB in this board but I've been running it @ lower then 1333Mhz and have experienced the same issue with only 3 x 2GB sticks in the system )
Issue first occurred after initial hardware build (so pre-software), any change in bios settings resulted in the 'lockup' as per the linked thread above. When i say any I mean from changing IDE / SATA settings to resetting it to failsafe defaults.
Updated the BIOS to E7 after this and yielded the same results.
Updated to E9d and am now able to OC / play with all settings 85%-90% of the time -sometimes after a simple restart the pc will still lockup and I just have to wait it out.
At times I have been able to speed up the 'cool down' of this lockup by removing ram sticks (so going from 6 x 2GB -> 3 x 2GB) and having them in the correct white 1/3/5 dimms.
Which initially lead me to think it was the ram, so I tried removing all of the ram to see if it would power on and no cigar :(
I've also tried this PSU on another board ( yee old Intel PII board ) and that powers up without an issue.
I have also had the system running outside of the case on a table and experienced the same issue.
Inside my case the board is on 9 x risers that came with my case and on top of each I have placed an insulating washer, all screws are screwed in tight (but not too tight) also with insulating washers.
May sound over kill but I wanted to make sure it wasn't shorting anywhere.
Apart from the above there is another issue which may or may not be related...
With the 12GB of ram installed it will sometimes register as only ~8GB (BIOS/WIN).
Removing 3/6 sticks (so down to 6GB) can also suffer the same issue and the system will only see ~4GB (BIOS/WIN)
- I am running XP x64 and can normally see all 12GB.
What happens is I'll restart the system or turn it on for the first time and its almost as if the system ignores a stick or two but after a few restarts and swapping sticks around it works fine again (this is when all slots are populated, when I am using only 3 x 2GB I leave them in their correct 1/3/5 dimms)
Just to round up this wall of text, I am still able to use my system as per normal and have had no issue installing the OS, these issues are just happening off and on but most commonly after a change in the bios (last time it happened I had changed the voltage to the ram 1.5000V -> 1.540V ~my ram is rated @ 1.65v @ 1600Mhz and I was running it at 1440mhz) or a simple restart.
If I overclock my system to stupid extremes it doesn't do this kind of lockup, it just restarts like normal has a winge after a few restarts and fixes itself. So I'm fairly confident its nothing like that.
Thanks in advance and sorry for the wall of text :P
Comment