You know, the 2nd cards clocks randomly changing, causing sensors to freeze the PC etc
You noticed it yourself...![]()
ahh..... the 2D down-clock issue
yes its solved most ppl's problem in this regard....... its the primary card or core down-clocking that's the issue, the slave card or core is fine at whatever clock as it never gets used in the 2D environment..
its when the primary card or core attempts to match the 2D clocks of its partner thats when the trouble starts...
for dual monitors the primary core clock must remain @ 400mhz while idle...
for single monitors im sure ATI power-play should set the primary core to 300mhz (on 5 series cards anyway)
but yes...... these new drivers do have the clocking issues resolved, but if you try to OC it'll revert both cores back down to 157mhz again
My Computer
At a glance
SEVEN x64Q9450 @ 3.6GHZ 1.34v8GB 1066 buffalo firestix @ 1152mhz CL5Sapphire HD 5970 + GTX260 (physX)
- Computer Manufacturer/Model Number
- myself
- OS
- SEVEN x64
- CPU
- Q9450 @ 3.6GHZ 1.34v
- Motherboard
- ASUS P5K PREMIUM P35
- Memory
- 8GB 1066 buffalo firestix @ 1152mhz CL5
- Graphics Card(s)
- Sapphire HD 5970 + GTX260 (physX)
- Sound Card
- Creative X-FI Xtreme Gamer
- Monitor(s) Displays
- SAMSUNG 20'' & SAMSUNG 23'' (dual screens)
- Screen Resolution
- 2048x1152 & 1680x1050
- Hard Drives
- 1x seagate 160gb IDE & 1x seagate 160gb SATA
- PSU
- XCILIO 850w (78A)
- Case
- CM590 1x 120x38mm & 2x92x38mm / 4x 120x25mm
- Cooling
- AC7 PRO @ 92x38mm blower, Lamptron military bus bay controll
- Keyboard
- LOGITECH E110
- Mouse
- logitech NX5
- Internet Speed
- 2MB
- Other Info
- its a continual ''work in progress''....