You have to remove your heatsink, yes. the number's ontop of the heatspreader and nowhere else.Quote:
Originally Posted by Mehran
Printable View
You have to remove your heatsink, yes. the number's ontop of the heatspreader and nowhere else.Quote:
Originally Posted by Mehran
guys is anyone using G.Skill 4400LE 2x512 TCCD sticks with Neo2 and e3 venice, im having a a hell of a time setting them up, checked g.skill threads and i just cant get them to work stable even at stock.........................weird thing about them is that even on a DFI and a Sanddy thay got truble being stable at 275mhz but they do 300mhz at same settings stable :confused: :confused: :confused: and on Neo2 and my Venice at 290 i got to 9nth loop of 1mb PI and on 275 instant crash LOL
......ah ya also either my CPU or my mobo died last night when i was playing with the ramm and settings in windows at 290 (all voltages whitin normal range) i just changed Trcd to 4 got a BSOD and no more boot....i took off everything and cleared the bios without the battery and psu unpluged overnight and nothing......the four leds on the bracket are showing all red (well one looks like orangy not red)
im starting to wonder am i that unlucky to have 2 crappy cpus (one was really really e6 crapy) or a bad mobo or im i just dumb since i cant get either 3 sets of 2x512 mb BH5, 2x256 OCZ CH5 (that do 250ish at 3.4) and a set of G.Skill TCCD to work at decent speeds.........ah ya mobo was volt modded for the BH5 but the mod taken of for the TCCD
i cannot run my BH-5 either (see may previous post). Tried yesteday 1:1 cl2225 with 240x9 - crash when posting, 230x9 - windows restarts before it boots, 220 - windows boots but crasches instantly after logon, 210 - windows freezes. 200x9 seems OK.
Mobo is Vdimm modded. So bad CPU? So bad memory? Today I check Vdimm voltage with a good multimeter,
i also had the vdimm mod and i got 2 sets of Ocz gold, and i couldnt get them 100% stable @ 240 2-2-2-5 at 3.4v prime would fail after couple hours, i also got a 2x512mb set of old KHX bh5 that can do 240@3.2v 2T on a nf2 an7 and barton, and could do 230@3.2 1T on a epox with newcastle, but on this i cant get them stable at 230 even with 3.5v.....thats with 2 venuce cpus (both crappy though) so i don't know if its the cpus or mobo........oh ya droping the multi didnt help either
I have my Venice 3000+ 2*290 stable in Prime95, SuperPI and 3DMark2001, only freezes in 3Dmark03 Ragtroll test looping (I think it's vertex shader test).
I'm using Leadtek 6600GT on stock frequencies. In BIOS NV speed disabled, Fastwrite also.
What it could be?
try LDT = 3x and vAGP = 1.6 or 1.65
With me 4x250 1:1 seems ok, but just 6x250 crashes...Quote:
Originally Posted by Millyons
Thx to u and TMM also.Quote:
Originally Posted by ridczak
I think I made a mistake.
mine is LBBLE 0519 APAW.
How is that?!
It wasn't in that list special gave me.
Du know how it can handle overclocking? :confused:
Quote:
Originally Posted by ridczak
i see your cpu is a 0535, mabey the new ones just have crappy mem controlers, i tested with a 0533 (max stable 2600) and a e6 0528 (max stable 24xx :) )
I think so, because the mobo & ocz gold rather cannot be so crappy ;) Hopefully I will get my hands on Opteron 144 in some time and we will see then. For now I'm going to stay with lower clock on mem, play with some other bioses & eventually measure this 3.3V voltage.Quote:
Originally Posted by Millyons
my vdimm with the mod and enermax 430w psu (modded also) at like 3.4v would drop to 3.3v under memtest #5 and in win would be 3.8 idle and 3.6 prime big fft. but the atx connector point that i was running the vdimm off was always 3.4v
thats a pretty good stepping afaik. Should do 2.6-2.8 on air :)Quote:
Originally Posted by Mehran
well guys, (se and whoever else replied to mee specifically)
note well im using SATA drives on SATA 3 and SATA 4 of course. now it could well be the ram being paged and sending corrupt stuff. lemme give you the weekend recap rundown if you dont mind. before i do tho, i do remember lots of talk from the pre 1.5 bios days of whether you had to set agp to 66 or 67 to lock the pci and make sure it was async.... lemme know if thats tru or not. also note that ALL of this happens at 250 htt. 250x10 is what my cpu has been running at since the beginning of the year and thru any bios or ram or watercoolin upgrade its what i strive to achive my stability with.
alrighty. got the TCCD last week to replace my bh-5 since i gave up on the combination of the bh-5 + ddr booster + neo2 + silence. fine
messed around with the tccd. lots to learn here. aint so simple to clock like the bh-5 was (up voltage and go go go).
eventually got quick memtest to pass a few times when i tried the wacky thought of 2.5-3-3-10 @ 250 with 2.6v. ran memtest over night to confirm, was workin somewhat. SUPER-PI fails immediately and locks up prompting a error report send off. thats pretty important to what happens over the weekend.
what happens next? i think, oh hmm, lemme holla at SE's tccd modded bios. previously, any bios after the 1,8mod3 nfm version didnt work that great.. but who knows, maybe it will now.
upgrade to 1.b tccd SE bios. set memtest again. looking great.
up agp to 81mhz, check my 6800 clocks... change mem by 25 mhz. get higher test scores. totally awesome. use machine as normal. get random windows explorer crashes, then when the error report thing pops up, it crashes prompting me to send error report about Drdaemon or whatever the "Dr" progrma is that does bugsolving.
decide at work on friday that windwos media center edition is awesome, i see lots of OEMs shipping it on their gaming systems... i can upgrade one of my dual boots to it. i choose to upgrade my clock testing boot. cd is bad, upgrade if fuxored.
eventually do a clean install and all that on this boot, with a good cd. other boot still messed up, chkdsk reports mad errors. boot to dos mode and chkdsk /f that mofo. in that REGULAR boot, i open the super pi folder and it runs.
but in the media center boot it doesnt want to run.
at some point during all of this, i again mess around with a few ram settings, get back to 1.8nfm bios since its the only one that works it seems on my winnie and crashes stop happening.
i eventually settle it at 2.5-4-4-10 @ 250htt with 2.6v. agp is back to 66. chkdsk and diskeeper defrags have been run on both boots.
++++++
so thats as best in chronological order i could remember. im thinkin either the mem wasnt stable, makin super pi crash (the only program to do so consistently.... other random thigns crashed whenever they wanted)..... or the hdds got corrupted becuz of bad memery or bad agp 81mhz..... and i know for sure that, yet again, the 1.8mod3 nfm bios was the only one that worked well for me.
what yall think? wanna clear up any misconceptions i got goin on here? my computer wasnt fully workin for much of this weekend and that sucks, plus i havent had this kinda crash problems since before i got this system. i been used to the stability and NOT using my regualr boot until i get ma stability. no hdd probs at all. i dunno, im just not pleased with system wide probs cuz usually i might work on one part if that. and the only new thing was the ram, which made me try new bioses (never gave a prob before either so back to the ram?) and then the agp 81
el rolio..you missed your sex life ....To answer your question we must know about this also..
a little question: how can i set the CPU VCore to 1.9v without Corecell?
Unfortunatly I can hardly now get it stable at 2635! :stick:Quote:
Originally Posted by TMM
What's wrong?
I mean I can't get it stable at 2700 even with 1.78 V!
:( What should I do?!
LOL yes we need more smut in this forum.Quote:
Originally Posted by Losphoron
Hi all! Most of you won't remember, but i had an issue with my old board a while back (the keyboard controller chip was borked). Anyway, i got a replacement today and am amazed at the clockability of this 2gb kit of ballistix. However, i am experiencing artifacts in 3d apps whenever i use a high fsb (270+). I guess that the agp/pci lock isn't working?
I'm using the 1.b bios modded for ballistix by sideeffect and am running clockgen to OC the ram/cpu. I have yet to try another bios.. i also thought that changing the agp freq to 67mhz like in the old days might fix it but but still no go.
Anyone else experienced this issue before?
aiit well there was no sex this weekend, too stressed for that, but did meet 2 new chicks, had one sleep over on sat night and have a diff one visitin i think end of october.....
now back to ma computer! :P
Quote:
Originally Posted by ZeroSanity
Im not sure but i wouldnt think that artifacts would be caused by high HTT. Ussually the graphics card alone would cause the artifacts because its overclocked to much. Lets say the locks are not taking place Nvidia cards still will take up to 100 mhz on the agp bus. The hard disk would give out before the card would. So i am lead to believe the locks are working.
Is the graphics card at stock speeds? Try setting vagp volts of 1.65 volts. Im thinking possibly that the more you overclock the cpu the less power the video card has and so is artifacting maybe ...
Bit of a lame guess but you should test things like highest cpu/HTT overclock at a low gpu clock without artifacts. then highest gpu overclock without artifacts at a lower cpu/ htt level.
On my motherboard im certain the locks are taking place. I dont know though if all boards have working pci locks or not.
Hmm, well i lowered the gpu clocks to way below stock and i get the same problem when i enable the cpu/ram OC. That voltage scenario you mentioned sounds convincing though, ill try that now ;) .
el rolio 250 2.5-4-4- isnt very good for tccd. Im thinking maybe your winchester has a bad memory controller and thats what was causing the instability and the corrupt disk drives.
Try and to tighten the timings up a bit to 2.5-3-3 if you can. Some tccd likes low voltage like 2.65 - 2.7 and wont work at high voltage some tccd likes 2.85 - 2.9 volts and is not so good at low voltage.
Try all voltage settings and use memtest in dos to work out your max mem speed.
Right, raised the agp volts to 1.65 and still the same problem, this is real strange because as soon as i lower the clocks to the cpu everything runs fine again.
One thing that i am 110% sure of... it's definately not a colling issue. ;)
Any ideas?
Just discovered that the system is fine up to 260 fsb, anything over causes these artifacts.
is this 260 HTT with 260 mhz ram speed or 260 HTT with the ram on a divider?
well back on page 120 this is what i said:
Quote:
Originally Posted by el rolio
quick note, later i remembered that the +5% wasnt my stable 24 hour setting for 2.5ghz so i changed it to +8.3%Quote:
Originally Posted by el rolio