Printable View
ive finally given up trying to get this striker II extreme board working stable with ocz ram, ive tried 2x2gb OCZ1600EB sticks and 2x1gb OCZ1333 both do exactly the same and crash in windows in around 2 hours of prime95, more if i just leave it idling. in any case ive ordered 2x1gb supertalent projectX 2000 to test if the board really doesnt like ocz memory and should be here friday.
Lets burn every single SIIE in the world!!!!
Seriously, with economy this bad and companies giving us such a bad products for $450 when they are not worth the money you pay I think Im just gonna wait and let this go for a while. no nvidia chipset for me for a good time, im going to spend my money on the rest of the components I need and hopefully by then we will see if anything good happens.
i saw this http://www.urbaczewski.com/humor/softdevcycle.htm while i was taking a quiz and i thought of this thread :rofl:
SPI 32M stable
http://img244.imageshack.us/img244/8...i32mcv2.th.jpg
I installed Vista x64 and the screen refresh problem went away. But, when the screen saver kicked in, I had a blank screen :mad: . So , I guess we would have to OC PCI-E lanes, for 450FSB and above. I am gonna prime now.
"in-it", Manchester, United Kingdom speak for "this is so right". This would be so funny if it wasn't true of $450 motherboards that fail where $98 motherboards succeed. Private message me if you want the facts.Quote:
Originally Posted by andymg350
I feel your pain. see my post #355 in this thread & read my signiture, Cheers from the UK.Quote:
Originally Posted by slim142
I still haven't got my Corsair 2x2GB 7-7-7-20 1600 memory so untill tomorrow I only test my QX9650 by raising the multiplier (because touching anything with the FSB or Memory will result in an error or freze. It seems I am 2 h OCCT v 2.0.0a CPU test stable at a multi of 11.5 (3.83 GHz) with loadline calibration enable and a v-core of 1.3625 (set in BIOS 0511). My max temps measured by Real Temp v. 2.41 are: 59, 61, 66, 64 degree Celcius (OCCT temps are 10 more on all cores). In CPU-Z v. 1.44.2 the v-core is read as 1.328 and in Asus PC Probe II it is read 1.41. My question is: Are these temps reasonable for the watercooling I use or are they too high? (se sig, I have plenty of airflow in my case, bottom and front 120 mm fans suck in and all four 120 mm on the radiators blow out, 200 mm side fan suck in, Chasisfan duty cycle set to 70 % and all optional fans set to 80 % in BIOS). The other question is how high temps do people let their 9650's run 24/7 at (I know Google/search XS but on this MB)?
#tekjunkie which v-core did you set for your 4050 MHz 32M screenshot and which temps do you get at these settings when running OCCT CPU test (if it is stable there)?
Sure I can complete SuperPi 32M at 4 GHz with v-core 1.4 but to be at leas OCCT CPU stable I need more than 1.4 V on the core which results in higher temps than I dare run. I will not set more than 1.4 on the CPU until I am sure my watercooling works as it is supposed to, that's why I ask everybody what can be expected from my cooling (it is my first watercooling build)?
Under watercooling none of my cores exceed 60 degrees, even at 1.465 VCore. I am struggling to keep 4GHz even with 1.465 VCore (loadline calibration disabled), one core always fails Prime95. I have ordered a QX9770 to see if I get any more luck with that.Quote:
Originally Posted by Holmer
#Tyke thanks for responding. This means my watercooling sucks/you have ultra high-end watercooling or my MX-1 TIM still have not settled since I have only really tested my CPU today due to all the trouble with my memory overclock. I think my delta-t is way too high for watercooling vith this relatively modest v-core. Maybe I should reseat my CPU block?Quote:
Originally Posted by Tyke
If I don't enable loadline calibration I loose stability.
Just got this from Asus about Bios 0603
ASUStech-Chris> 0603 was designed to overcome problems accessing and sending data from the RAM when 1600Mhz or faster modules were installed.
He also Said in 2 weeks the expect another bios
just thought I share the info I have
Quote:
Originally Posted by Holmer
Quote:
Originally Posted by Tyke
When testing my QX9650 under a PRIME95 or SuperPI 32 W/Prime & Real Temp 2.41 along with this Thermal Profile chart for the QX9650 I watch to see if the TEMPS are in range of the Power (W) vs the Maximum (TC) Temps on there cores. If they are not in range I assume system will not be stable and I assume it could hurt the CPU. I will attach a picture soon of my QX9650 in action.. So far I almost got my QX9650 to pass at 4GHz, but because of my CPU/BATCH I got requires 1.5 vcore to get me there with LOAD LINE disabled. One of my CPU cores Power(W) is at 42 but the TC (C) is at 52c when it should be at 49.5 it will start to fail. So I am thinking I need more power to that core..Quote:
Originally Posted by Holmer
http://i274.photobucket.com/albums/j...ileTEMPS-1.jpg
Awesome!!! So I can spend another 3-4 hours fiddling with a buggy bios before I reflash back to 0511 which in itself is crippled...Quote:
Originally Posted by X2beach
Why do I keep buying their products, (specially Nvidia based boards)???
I think the Same thing, but I like a Challenge
Asus Also informed me They are having More issues with OCZ 1600 then any other. He Said if we keep the Ram Under 1600 OCZ Ram works Great..
you have 4gb?because don't play 4gb my striker check my last pot
yes 4gigs
Well, did you get that from customer support? Because they are full of bs sometimes.Quote:
Originally Posted by X2beach
Hopefully BIOS 0605 or 0701 or w/e the name is gonna be will fix 1) memory problems 2)high fsb problems 3) data corruptions (which if this asus guy is right, all this might be related to RAM)
Something has to be the weakest link ;)Quote:
Originally Posted by Tyke
One of my cores fails in prime95 above 4450 mhz, the other 3 keep priming for hours.
That's life.
I have a D-Tek fusion on a Thermochill triple rad running on the CPU alone.Quote:
Originally Posted by Holmer
See post 361 above keep close the Power (W) and the Maximum TC (C) Temps and you should be fine.. Maybe yours is getting to much or not enough vcore to one of the cores?Quote:
Originally Posted by Justifire
Core #4?Quote:
Originally Posted by Justifire
My vcore was@1.4125 in BIOS with LLC enabled. That gave me 1.392 in windows per cpuz. I wasnt prime stable(it failed instantly) @ these settings. But, I kept playing with the GTL and guess what I am priming now @1.3975 set in BIOS and 1.36 in CPUZ in windows. Its been like half an hour now I am still going with no freezes or no errors in prime. I will post a screen shot soon as soon I hit the 1 hour mark with the real temp in the screen shot. I also have a feeling that it might be stable @ these speeds with 1.375 set in BIOS, which gives me 1.344 windows(CPUZ).Quote:
Originally Posted by Holmer
Good luck tekjunkie, those values did not work for me :(
Now waiting on my QX9770!!
Here is an update of what is happening. My settings first
QDR/RAM=1800
PCIE1 and PCIE2=100
SPP<->MCP =200
VCORE =1.39(CPUZ reports 1.36 in windows)
LLC =Enabled
VTT=1.32
VDIMM=1.92(7-7-7-18 2T rest of timings @ auto)
VSPP=1.5
VMCP=1.55
GTLREF0 = -51
GTLREF1 =-48
The rest @ auto with IDE,Jmicron,spread spectrums,C1E and EIST, all disabled.
Prime 95 failed after 56 minutes on core #1.
I changed the GTLREF0 a notch below -51(-44 or -42, can't remember), rest the same and prime failed after 40 minutes on core #2.Then, I changed GTLREF0 to -36, prime failed in 9 minutes on core#2. Next try was GTLREF0 to -58 and GTLREF1 to -51 and a scary thing happened. Vista froze while primming, I reboot and the POST was hanging on IDE INIT or IDE DET or something like that with no activity on my Raptors. I was like "There goes my raptors", but was hoping for the best and cleared CMOS and thankfully booted into vista. Then I went back into BIOS, dialled in all the previous settings with GTLREF0 @ -58 and now priming again. Let's see how far I go.
Update:
I got a BSOD in vista after about an hour of priming. I don't know whether its due to wrong GTL or low vcore.I am guessing that it's due to low vcore. Wrong VTT/GTL usually leads to a system freeze and low vcore usually leads to BSOD. This is comming from my very limited experience OCing. Anway, I am @ 1.4 vcore which gives me 1.376 in windows. I am priming now.
More update:
I was greeted with a vista log on screen when I woke up this morning, so I guess it BSODed again. This was with 1.372 in windows with LLC.Since I am on air, I didn't want to pump any more volts into my QX9650, hence I dropped back to 445FSB and 1.375 vcore in bios(1.344 windows). I could prime all day long with the settings that I have now, but the problem was one core craps out while priming. So, I decided to concentrate on getting all cores prime stable for atleast 6 hours with out errors, by playing with GTL.
Keep us updated, tekjunkie. I will be reading your experiences closely to relate with mine.
Me too, fingers crossed!:up:Quote:
Originally Posted by Big Myke