System Specs:
o Q9300 Stepping C1/M1
o OCZ Vendetta2 CPU Cooler + ArcticSilver 5 Paste
o P5K Premium Mobo + 0602 Bios
o Corsair Dominator PC2-8500 2x2048 Dual Channel
o 8800GT PCI-E Video
o Vista Ultimate 32bit + SP1
o Current Max Overclock: 3.45Ghz -> Idle temp: 42c/Max Load: 88c...
I tired this on 2 different case types.. One being a Thermaltake Armour (the one with the massive 250m side fan) and a Antec Sonata3 case. Both the connection from the front eSata case cable and the optional expansion bracket that fits on the back which then also connects to the eSata on the...
Surely I cannot be the only one with this problem? This eSata issue has appeared on 3 different Asus mobos. Is this an industry trend with internal eSata connectors on the board?
I've been running an FTP server for some years but its time to simplify it down to a single small NAS-driven HDD enclosed system. I've been looking at this replacement:
Buffalo LinkStation Pro Shared Network Storage LS-320GL - NAS - 320 GB
- Serial ATA-150 - HD 320 GB x 1 - Gigabit Ethernet...
Both my current P5W DH and the P5K (system I am building for a friend) has this problem. Both Mobos work perfectly with the eSata on the back panel (once the JController is enabled in Bios for obvious reasons). But.. plug them either into the regular sata ports on the mobo or to the esata port...
I have used a few Asus boards recently (ie.Asus P5W DH, P5K) all flashed to the latest bios but the problem I am having is this:
Why when I plug the external esata connection installed onto the case's esata port to the motherboard's regular sata port OR e-sata port that the speeds on the...
Update: Think I have a winner..
o CPU Used: Conroe E6700 Retail B2
o Motherboard: Asus P5W DH (1301 Bios)
o Ram: OCZ DDR2 PC2-8000 Platinum Extreme Edition Dual Channel 1000MHz DDR2
Recommended: CL 4-5-4-15 2.2 Volts (use a VDIMM of 2.25V ± 5%)
o Power Supply: OCZ GamerXtreme 700W
o...
Okie.. finalizing things..
CPU Used: Conroe E6700 Retail B2
Motherboard: Asus P5W DH (1301 Bios)
My Current Settings:
AI Overclocking: Manual
CPU Frequency: 366
DRAM Frequency: DDR2-915Mhz
Preformance Mode: Auto
PCI Express Frequency: 100
PCI Clock Synchonization Mode: 33.33Mhz...
Okie.. ongoing with my tests I have some questions to consider:
1) For Ram - should I have tighter timings (ie. 4-5-4-12) and keep Vdimm @ 2.20V or run by SPD and then increase DRAM Frequency much higher than where I am to 800+ then increase Vdimm higher than 2.20V
2) For this kind of ram...
I'll try manually setting ram to those loose settings. That also makes sense that setting it to AUTO might cause wonky settings in the background.
As for reducing the XP paging size down to 100mb or even off. I've heard that years and years ago. Makes sense since physical memory is now...
Yeaa I figured as much: I'm getting to the point that Orthos-Beta is a "anally-retentive" torturer. ;) I tried some intensive computation apps I had a friend write for me a month back and it works flawlessly (almost 5x faster than on my old P4 3.0Ghz). Hell.. thinking of putting my DRAM...
I'll increase Ram to 2.30V
However, don't I want to keep Ram @ SPD so I can first troubleshoot the CPU first? No sense in doing both at the same time, no?
Not sure how I could be "at the cpu wall" when the CPU temps at load are far below what others are getting with serious OC'ing by air...