Printable View
Ok running orthos right now while typing this with C1E on and EIST off, cpuz is reporting the voltage staying at 1.15v under full 100% cpu load, cpu temp rose from 22C to 37C which indicates the cpu really is under load since my system is not crashing do I need to worry about the voltage not increasing under load?
I had a similar problem the first time I started using the JMicron controller, where I was getting transfers around 1 MB/s. :shocked: But it turns out I just needed to install the drivers for the controller. they weren't installed automatically with the rest of the drivers from the Asus CD like I thought they were.Quote:
Originally Posted by Crow-
My pc has the following parts:
Asus P5W DH Deluxe
E6600
2 * 1GB Kingstone @ 800
MSI 8800GTS 640MB
With the latest bios every tme i had for my cpu temps around 28-35 c and for my mobo 40 - 45 c. Everything on stock cooling...
I mounted for fun a forgotten Zalman Fan ( http://www.zalman.co.kr/eng/product/...dx=15&code=016 ) under my GTS... Suprised i saw on next boot my Mobo has temps lower than my Cpu! Around 26 - 28 !!!!
So cause the mounted fan is hitting the ICH7R Chip and cooling it i have so much lower temps? It is true that the warm heatsink of my GTS is almost totally covering the above chip i mentioned... So what happened? The mobo temps for the P5W DH Deluxe are measured by ICH7R?
ps: Just to mention that my pc case doesn't have any side fans... i mounted this fan in my case... so "no fresh" air is coming throught this fan...
I am on 2403 and just discovered that disabling speedstep does not actually cancel clock speed changes on my system :shrug:. May be I need to move to 2406. Anyway, I think that when we talk about an idle system you are right - C1E is the feature that delivers most of the power savings. The speedstep comes into play on the system under a light load and is thus recommended for 24/7 setups.Quote:
Originally Posted by Chrysalis
i have a little pb with the pionner 112 detection master and the dection of sata externeQuote:
Originally Posted by genish
but my pb is since the 2406 my ram is unstable. corsair 6400 c4 2*1go
is the bios 2406 how crash something on my motherboard ?
is the print of the 2406 on 2004?
is my motherboard naturally crash ?
or is my ram crash ?
i test that:confused:
"pb?" What is "PB"?
Can you please at least TRY to write in standard written English, and not rediculous abbreviations?
This isn't an AOL chatroom or instant messenger...
I would guess it means problem. :D
Just went to turn my computer on and got stuck at the post screen so i restarted an now all i get is the fans spinning away nothing output to screen. Two green lights on mobo,
tried resetting them cmos no joy,
took the battery out and left it out for 20mins no change,
took 1 stick of ram out no change
swapped it with other stick of ram no change.
Tried unplugging all RAM so board would beep at me but no beeps
tried uplugging all hdd so it would beep once again no beeps what else can i do or is my board ready for the scrap heap in the sky?
You might want to put a 40mm fan on the north bridge heat sinkQuote:
Originally Posted by Lee13168
Just upped to 2406 and the few sec. delay entering the HW Monitoring submenu in the BIOS is gone, it's now instantaneous. Nice! :)
anything on that...? :shrug:Quote:
Originally Posted by P5WDHdeluxe
Yeah, the temp probe is close to the ICH7R chip, so any air blowing over that is going to lower the temps displayed by BIOS/software.Quote:
Originally Posted by P5WDHdeluxe
Hey guys, anyone got any ideas how I can fix my problem here: http://www.xtremesystems.org/forums/...25#post2665625
Cheers :)
Hi people!
So, I've had my P5W/C2D setup for about a year now.
Originally I had a E6600, wich ran nicely on 3,6GHz, (400x9, no idea on what BIOS I used) but unfortunately the E6600 died after a while :(
Later I got an E6850, but I didn't bother with any oc at first. Updated BIOS to the modded 2004 found here.
Anyways; about two weeks ago my system became unstable, and finally all I got was a black screen (no post). After a bit of trial and error, I discovered that by removing one of the RAM modules (Crucial Anniversary) everything seemed OK. (I tried switching back and forth between the modules, so it was pretty clear that one of them was dead)
Got my self a pair of Corsair dominator 8500 (2x1GB), but I was still experiencing some unstability. Updated BIOS to 2406 and got the latest chipset drivers, but it only made things worse. (screen freezes. Example; the intro video in H-L2 Episode Two freezes after a couple of seconds. The computer can also freeze by just using an internet browser)
(evrything running at stock settings)
Then again, I tried with only one RAM module, and everything works fine(works with both the Corsair modules one at the time, so they are both healthy). I i have tried both using the orange and the black slots, but no difference there.
Secondly; With the E6600 I had no problems running at 400 FSB, but now I can only get it to boot at about 360. Just the BIOS? (I've read most of this thread and tried all tips I could find)
Any clues? Faulty MB? Bad BIOS?
Seems I spoke too soon.Quote:
Originally Posted by romfi
Further observations.
the low voltage is permenant not only when idle, if I stress the system it remains at 1.168volts however is stable, but if I disabled C1E the voltage is still 1.168 even under full load.
seems the only way to get what should be the normal voltage is to manually specify it in the bios or to enable speedstep, selecting auto voltage with speedstep disabled regardless of thermal/c1e settings the voltage is always in power saving mode.
Although it seems stable and can run orthos no problems I have notice occasional clock speed fluctuations in cpuz from 2667mhz to 2000mhz and I am curious if this is because of undervolting.
Last night I left my pc up for a couple of hours on the fixed 1.35v setting in bios and when I went back to it was frozen, did some googling and I may have accidently slightly over volted the cpu although as I understand many people here up their voltage this is the only time my pc has ever hung so I am putting the explanation down to me manually setting the voltage.
I dont know if this voltage behaviour is specific to 2406 and would happen on 2004 as on 2004 I always used speedstep apart from ages ago when I cannot remember the behaviour.
cpu is 6420 overclocked to 6600 speed 2.6ghz which has ran fine in this config for months and months and temps are very low mid 40s under load low 20s idle.
For now I have reenabled speedstep.
--edit--
just checked speedfan and its reporting both my fans at 0rpm clearly wrong, I am seeing some weird behaviours so I may roll back to 2004.
The link seems to be broken ... At least it doesn't work for meQuote:
Originally Posted by lawrywild
yeah link broken here also.
ok now I am back on 2004 bios however the afudos flags in post #1 do not work, latest afudos says bios incompatible so have to use older afudos which doesnt support wipe cmos.
2004 behaviour a bit different.
speedstep disabled, windows runs as if speedstep is enabled.
I then enabled lock cpu ratio to 8x so forcing it but windows ignores it and runs as if speedstep is on again.
I noticed now in bios the vcore is staying at 1.325v so I am thinking now the speedstep behaviour is driver/software related? been turned on by windows itself?
I got my fan readings back I power cycled the computer.
2046 and 2004 do behave differently however 2406 with speedstep disabled does appear to mainly lock the cpu speed at full speed but has small fluctuations down and cpu voltage is locked at low power mode, 2004 as said above acts just as if speedstep is on all the time.
further observation
rightmark cpu utility which shows both cores monitoring (unlike cpuz only first core) shows the 2nd core at full speed occasionally dropping down to speedstep speed but instantly going back up again also at full voltage but the first core is acting as if speedstep is on. Very strange.
Ok confusion ended.
I disabled C1E on 2004 and is as it should be full voltage and normal clock speed so my conclusion is 2046 is buggy either due to the bios buggy or me not able to wipe cmos data on flash and 2004 is working as it should.Quote:
C1E is only invoked if the CPU recieves the HLT signal. This is issued by the OS when there are no instructions to do (think of the idle process in the task manager issuing HLT). Once a Core 2 CPU recieves the HLT, it's clocking down multiplier 6x and a certain minimum VID (desktop 1.163 V, mobile 0.95 V). Once it recieves a non-HLT signal, multiplier and VID go up to standard levels.
EIST is controlled by a OS driver which instructs the CPU. The driver measures the CPU load, then it selects from several steps (up to 6 on my mobile cpu) which one to choose. The lowest EIST multiplier/VID matches exactly the ones of C1E. The other steps are choosen at medium load. EIST keeps the multiplier/VID as low as they are needed.
In addition if anyone is interested intel released 7.8 version of matrix drivers and finally fixed the long standing write cache bug, now on single drives write cache is enabled finally and it no longer forces disabled write cache on drives attached to the jmicron controller.
I checked it out, but he was able to resolve it.Quote:
Originally Posted by romfi
Oh yeah, links broken because I deleted the thread. Managed to fix the problem. Cheers for making the effort to look though :)
hey lawrywild how did you configure your motherboard for your Q6600. I have the Q6600 and this motherboard too and i want to see how you overclock it thanks
Hi,
I come not over 440FSB by max Vcore , what is the max FSB with this board ?
That is about as high as this board gets.Quote:
Originally Posted by XSS
Bios 2406, Auto vcore, 333Fsb, Pci 33.3, Pci-e 100, EIST enabled, DDR2 833Mhz, Vdimm 2.1v, 4-4-4-4-4, auto vmch, auto vich, intel RAID 0,Quote:
Originally Posted by JimmyDDD
That about covers the important bits..
since i have 400 MHZ ram, is it better if i went to higher fsb so it will take fuller advantage? I emulated your configuration since I have faster ram. I had the same thing with my E6600 before but before I got 5.9 on my Computer in Vista x64, but now even with the new CPU that is OC, i get the same 5.9. is that 5.9 wrong? or did i not oc mine enough?
You will most likely get better performance if you were to run your memory at 1:1, and a higher FSB will help you to achieve that. However, better performance is not guaranteed, and the only way to know is to try both configurations and benchmark them.
5.9 is the current maximum score in Vista.