Everest? Any app that looks at the onboard sensor foobars IDU until a reboot...Quote:
Originally Posted by slagdemon
Everest? Any app that looks at the onboard sensor foobars IDU until a reboot...Quote:
Originally Posted by slagdemon
Is 2333 still the prefered bios?
I switched to the AW9D-Max. I think I'll stay there for a while till I get some multi adjustment in a new BX2 bios. Performance is amazing too. gtj, is your board with the blue chokers from RMA too?
Well everything was stable for a while but now my RAM is acting up. G.Skill F2-8000PHU1-1GBHZ, I'm now at 2.4v hoping it will help. It's at 266/533 and I was stable all the way up to 400 MHz FSB. I've since pared it back to 375 or so, and it runs all day and after sitting idle for several hours, gets unstable. I went all the way down to 310 FSB for a while and it was still unstable so I started suspecting the RAM. PFN_LIST_CORRUPT or other bluescreens. If I orthos after a long idle period, the CPU-only test is stable but blend bluescreens immediately, it's definitely RAM. Timings are at 5-5-5-12 (was 5-5-5-8 and stable for a while) and there's lots of air blowing around. This RAM is rated 2.2-2.4 and since it is at 266/533 it's not overclocked really, so I'm surprised there's a problem. I thought I might have pushed the volts too far and dropped it to 2.0v but that was nearly fatal - got 3 beeps trying to start with the CMOS Recovery jumper set! After a cooldown period it seemed to boot long enough for me to increase the voltage.
I'm in a bit of a panic since 2.4v and 5-5-5-12 is about as far as I can go. I'm afraid the higher voltage is slowly damaging it and it's going to hit the wall if I try to push any more. What can I do to loosen the burden on the RAM???
@minsc_tdp. what ram slot you're in now? is it the 3rd (blue) one? I heard that the 3rd slot causes / killed some ram.
@Sigfever. i want to know that as well.
how do u noe when the OC has reached its max? Are erratic behaviors in XP considered as one of the signs? I tested my OC via Orthos - 8hrs, SUper Pi and OCCT and everything is ok. However, i can feel like there's a delay i.e. opening folders, etc. Is there sumthing wrong ?
Btw, after my orthos tests or OCCT has ended why does my cpu usage at > 50% ? I left everything as idle after the tests.
My current settings are as below:
ref mem timings vdimm vcore vfsb vmch/ich FSB Multi CPU speed
266 533 5-5-5-13 1.84 1.325 1.25 1.525 333 9 2997
orthos1hr 8hr super pi (32M) occt
stable stable 18m 52.907s stable
what should i experiment next if say, my fsb at 340 fails at the stock vcore of 1.325?
1. Increase the vcore or
2. Loosen the memory timings or
3. Increase vdimm or
4. Increase vfsb or
5. Increase vmch/ich
edit: OCCT failed/crashed when i set my fsb to 340X9. Super Pi was ok. OS hangs 15 while gaming. Have yet to try Orthos at 1hr and 8hrs.Tried to run to latency tests via Everest but it hang after passign thru the level 1 cache test. Do you guys reckon i should increase vdimm from 1.84 to say 2.0v?
I have two sticks so they're in the blue slots to get the dual channel.Quote:
Originally Posted by nop
Pretty much.Quote:
Originally Posted by SiGfever
Nope. Retail purchases.Quote:
Originally Posted by Zucker2k
I'm not sure you can loosen the burden any further considering that they're running below spec now. Have you run memtest yet? Tried 1 stick at a time? Swapped the sticks in their slots? Moved from the blue to the black slots?Quote:
Originally Posted by minsc_tdp
If you can pass an 8 hour orthos then problems with XP are likely not related to the overclock. Have you looked at Task manager to see what's causing the CPU to stay above 50%?Quote:
Originally Posted by hotchoc
You're memory is still underclocked so giving it more voltage isn't going to help. Increasing Vcore will probably help most but it's not clear that it's the overclock that's causing the problem with XP.
The first time i opened Core temp the whole pc just reboot. The second time, it reboots after 1-2 mins of me opening core temp. went to read the previous threads and ppl have been complaining how sandra and everest screws up the voltage thingy. what do u think gtj ?
as for my case, i kinda up my vdimm to 1.88 from 1.84. Gonna up my vcore to one level and see what can be done. would it be better for me to leave my vmich and vfsb the same for benchmarking purposes? dram ratio is still set as 1:1
In regards to the CPU usage, it only occurs after i did the Orthos tests. Went top check on hte task mgr and couldn't find wat's eating up all the resources. CPu usage will be normal ~1-2% once i reboot my comp. weird
Hmmm. That's a little wierd. The voltage reset problem only occurred when the vcore was higher than the default so I don't think that's your problem. In any case, make sure you use the latest beta of Everest from http://www.lavalys.com/forum/index.php?showforum=12 Sandra still has the issue so don't use it if youstart increasing your vcore.Quote:
Originally Posted by hotchoc
Yep, you can leave your vmch and vfsb at their defaults for now.
one more thing
opened my coretemp at it shows me this:
tjunction = 85
core 0 = 36
core 1 = 37
should i be worried with tjunction? it's 85C !!!
another thing is this. remember back while i asked sumthign bout the raid 1 thingy. every time my system restarts itself or whenever i use the rest button, intel matrix will auto repair my raid 'errors'. what errors are these btw? i found out that everytime my OC fails, the next time i boot into windows the same auto repair thingy will occur as well. seems to be taking ages as well. approx. 30 mins at times. will it be alright if i were to reboot the system ? i can't be stuffed to let the raid to repair for 30mins while i need to tweak my vcore settings.
thks
Tjunction is a reference temp, 85C for Conroes and 100C for Allendales. It's nothing to worry about.Quote:
Originally Posted by hotchoc
thks mate. meaning 85C is the max before i should shut the system down manually ?Quote:
Originally Posted by Forceman
gtj:
remember back while i asked sumthign bout the raid 1 thingy. every time my system restarts itself or whenever i use the rest button, intel matrix will auto repair my raid 'errors'. what errors are these btw? i found out that everytime my OC fails, the next time i boot into windows the same auto repair thingy will occur as well. seems to be taking ages as well. approx. 30 mins at times. will it be alright if i were to reboot the system ? i can't be stuffed to let the raid to repair for 30mins while i need to tweak my vcore settings.
I tried the black slots and one stick, and it has no effect. It's the same thing every time, I've done this several times: Bootup, orthos stable for a while, let it sit nearly idle for 8 hours or so and it'll crash nearly on the 8 hour mark on the dot. Won't post in either regular or recovery mode (recovery mode gives 3 beeps). Move to black slots, nothing. Try one stick, nothing. Put both back in blue slots and wait. Wait some more. Magically comes up in regular mode only. Change some settings (or not) and it's back to Windows for the day. It just has to be shut off for a short while to recover.Quote:
Originally Posted by gtj
I notice the lower I drop the RAM voltage, the less likely it is to boot, hence the 3 beeps in recovery mode which is trying 1.8v. The RAM got the taste of blood.
I've taken it down to 1.45v CPU, 1.3v FSB, 1.6 MCH, and stock clocks (266 FSB). Obviously I can go lower on volts at 266 FSB but I don't want to drop it too much at once. Memory is at 2.32 and 5-5-5-8 at 266/533 so if this isn't stable then something is terribly wrong with my RAM.
Once the array is clean, a normal reboot should be just fine. It's only doing this because of the abnormal shutdowns.Quote:
Originally Posted by hotchoc
every time it happens i have to let it clean by itself? or can i just reboot the system? the cleaning might take 2-3 hrs from what i can see O_o
edit: after finish typing this, the system auto reboots by itself. managed to see a BSOD though. XP is kinda slow now. It takes like 1 sec-2 sec delay before anything that i click will open.
On Conroes 85C is when the CPU will throttle automatically - not sure if anyone has verified when that happens on the Allendales. In theory, any temps less than 85C should work fine and not damage the processor.Quote:
Originally Posted by hotchoc
http://img460.imageshack.us/img460/713/hotchocuj4.jpg
I kinda tried various settings and currently sitting at the blue row now (refer to pic). Everything is ok (WinXP, gaming,SuperPi) but Orthos fails at 33 mins. What did i do wrong btw ?
I have disabled:
1. Watchdog
2. C1E
3. EIST
4. VT
Btw, can someone plz tell me why a big jump of 0.1 V is needed just to increase a small increase of 20FSB ?
Please advice. Many thks
p.s Just went thru the whole 120pg of the thread. My head is spinning now lolz
You might try upping the memory voltage - 1.88 is kind of low. Those sticks are rated at 2.0. Have you tried the 333/667 strapping yet?
yes, increase your vcore to 1.45 and your mem voltage to 2.0 at the least.
when you run orthos, which test have you been trying, small, large, or blend?
is this mobo able to go 450FSB (using water cooling on NB) on Kentsfield?
Will be trying the 2.0V. Problem is i'm under clocking my ram. why the higher voltage?Quote:
Originally Posted by Forceman
am running the blend testsQuote:
Originally Posted by shimmishim
tried this:
Ref Freq (Mhz) = 266
Mem Freq (Mhz) = 533
Timings Mem Voltage (V) = 1.92
CPU Vcore (V) =1.45
FSB (V) = 1.35
MCH/ICH (V) = 1.6
CPU Freq (Mhz) = 375
Multi = 9
CPU Speed = 3375
Orthos = error in 27s
SuperPi (32MB) = 16m 23.610s
OCCT= crashed less than 2mins
Win XP = n/a
Try switching to the 333/667 memory strapping and see if that helps at all.Quote:
Originally Posted by hotchoc
in other words changing the strap to 1333 but retaining the 1:1 ratio ? why would u want to do that btw? thought latency will increase by increasing the strapQuote:
Originally Posted by Forceman
edit: tried the 333/667. Error in orthos in 12 secs. OCCT crashed.