-
First thing I did when I got home was update to the latest BIOS. I like the small tweaks they've made.
Went straight to 295x12 3550Mhz and it crashed PrimeStable almost immediately.
I increased vcore and NBvolt a little and changed to 3510Mhz and it was Prime stable 6.5 hours.
Funny thing when I got up this morning to check it I turned my LCD on, moved the mouse to turn off screen saver and when the LCD displayed it showed a BSOD that only occured moments earlier. It seems coming out of screensaver caused the BSOD. Moments before I turned on my LCD I checked my CPU useage with my G15 Keyboard and noticed all cores running 100%. CoreTemp logs confirmed it had been running for 6.5 hours.
Funny that. I'll be sure to turn off my screensaver tonight.
Anyhow to me this confirms it was not my PSU that caused the shutdown. With increased voltage to CPU and NB, the Galaxy had no problem running Prime for 6.5 hours overnight. From memory vcore was 1.4625 and NB was 1.4375 (close to anyway).
NB temps are screaming at over 70degrees now, so I'll be rotating the NB HSF 180 and will put less TIM on it soon.
I'm still happy with progress. GTL tweaks will need to be made soon.
Considering I haven't lapped my CPU and I have a fair bit of headroom in my vcore to play with, I still have a bit to go :)
NB: I really enjoy the new option with the latest BIOS to modify the CPU temp delta. Now, on load Guardian is the same as Coretemp for me :) gg DFI
On another note, looking through the hwbot rankings, my 1024M and 32M wPrime times are the fastest for my CPU frequency. Infact my times are faster than others that run their QX6700 at a higher frequency. This is with a multiplier of 12, and 'basic' RAM timings of 4-4-4-1T, using Vista :D
I don't know what motherboards or OS the others are using, but this MB damn fast :D
-
Quote:
Originally Posted by
C-N
Raja I will get some Ceramique & give that a go on the weekend along with ensuring the heatsink is flat.
The rig is running Orthos small fft's at the moment (2 1/2 hours so far) at 462.5 x 8 3.7GHz with a 70mm fan on the PWM heatsink & a 120mm blowing down between the CPU & NB toward the long chips in front of the PWM heatsink. The heatsink temp is mid 20's & the long chips are low 30's.
One thing I now notice is Smartguardian is running very close to Coretemp (high 60's low 70's) maybe its the fans maybe its the later 521 BIOS I will investigate later & post my findings.
Regards
Craig.
I haven't hooked up my lp 680i lt yet just got it this week but I do believe the bios enables such an action. I will see if i can find the info I speak of. Unfortunately I think I saw this at DFI-Street is now DIY and not all was archived after the debacle. Beside that, I speak of the NF4/AMD platform. I'm yet to be baptized in Intel/DDR2 O'cing so this may be off base.
-
anyone have experience removing the PWM heatsink?? i think i recall someone mentioned it here and found some very tough stuff underneath... was hard to remove.
-
I won't ever remove my PWM heatsink, not after the dramas I had with the Abit QuadGT.
-
Quote:
Originally Posted by
Borgod
On another note, looking through the hwbot rankings, my 1024M and 32M wPrime times are the fastest for my CPU frequency. Infact my times are faster than others that run their QX6700 at a higher frequency. This is with a multiplier of 12, and 'basic' RAM timings of 4-4-4-1T, using Vista :D
I don't know what motherboards or OS the others are using, but this MB damn fast :D
Borgod, where are the wPrime times you are referring to? I'd like to check them out. What are your times?
-
BTW, there are some $10 off coupons for this board from Motherboardpro.com in the deals forum.
-
Still eager to know what the new bios brought? Probably flash my bios tonight especially if it keeps the saved cmos.
-
major changes I have found,
Unlocked upward multi for XE edition cpu's
Temp threshold adjustment/rearrangement of naming to reflect NB and sb temps..
This is what I myself have found..
regards
Raja
-
virtualrain: goto www.hwbot.org or more information in the XS Forums <here>
Join i4memory.com team ;)
Vincey: BIOS changes I found:
-Unlocked Multiplier beyond 10 for Extreme CPU's
-Once you have selected your multiplier, you can now lock it
-Added CPU Temp delta settings, so you can match it to CoreTemp etc. Note the scaling is still different, so idle temps in Guardian/BIOS will be different to idle temps in CoreTemp if they're both the same on load
Also, yes the BIOS's are saved, but something is screwy with the FSB if you load your old BIOS settings. eg I loaded an old BIOS setting and although it was set to 10x320, for some reason it calculated this to be a MUCH bigger FSB, so my final frequency was set to something like 28000Mhz (yes really)
Make sure you check this, as you dont want to boot your PC set at this frequency of course.
This occured with all 3 old saved BIOS settings.
Another bug, all saved BIOS's will save vdimm at 2.88v
Make sure you change vdimm to correct voltage before saving and rebooting.
NB and SB temps are now displayed properly
-
I have not had the vdimm over voltage save since the older bios's, I find it stays where I save it to. However it would be wise to check before reboot just to make sure.
Also do not use previously saved cmos bank settings after a bios flash, make sure you over write these with new ones..
regards
Raja
-
Quote:
Originally Posted by
raju
I have not had the vdimm over voltage save since the older bios's, I find it stays where I save it to. However it would be wise to check before reboot just to make sure.
Also do not use previously saved cmos bank settings after a bios flash, make sure you over write these with new ones..
Yes it stays when I tell it to, but if I load a BIOS Usersave from the OLD bios, the vdimm voltage is overwritten with 2.8vdimm.
Indeed overight with new ones.
Aways double check before loading a BIOS - especially OC'd.
-
ya i just wrote over all my old saved BIOS after i flashed... then again i didn't really have any i wanted to save LOL
also came across possibly the easiest _quad_ overclock i've ever done ... just bumping the multi from 10 to 11 gives a 10% boost and required absolutely no voltage changes to pass OCCT ...
the temps stay low too cause everything is drooping from the stock BIOS voltage settings...
-
Quote:
Originally Posted by
raju
I have not had the vdimm over voltage save since the older bios's, I find it stays where I save it to. However it would be wise to check before reboot just to make sure.
Also do not use previously saved cmos bank settings after a bios flash, make sure you over write these with new ones..
regards
Raja
I agree, the whole mapping of settings to values could change with each bios release making it risky to load old settings into a new flash.
I finally have time to flash mine now. Will report later. :)
Borgod... thanks I'll look into that when I get a minute.
-
Quote:
Originally Posted by
Borgod
Yes it stays when I tell it to, but if I load a BIOS Usersave from the OLD bios, the vdimm voltage is overwritten with 2.8vdimm.
Indeed overight with new ones.
Aways double check before loading a BIOS - especially OC'd.
By old bios you mean settings from an older bios version? If that is the case you should never use older cmos saves on newer bios's, that will create issues such as these.
Each new bios means yo0u must overwrite your user cmos saves and start again, do not use old saves on new bios' flashes !
Using the same bios version with fresh cmos saves I have none of the over voltage issues you mention.
regards
Raja
-
Initial findings on latest BIOS (as most others have previously reported):
I'm using the 2C BIOS on my X3220 as it says it's for Q6600! :confused:
PC Health and Status:
- Temperature shutdown defaults to disabled
- NB Temp correctly labeled
- New option for CPU temp offset
FSB:
- Multi option is now available (and works! :yepp: ) - testing 450x8 now with all other settings the same as before.
Outstanding Issues:
- Voltage set vs. get hasn't changed (still major discrepancies between what you set and what you get)
- GTL entries are still mis-labeled
Hopefully it's not a whole new challenge to find working GTL values at this FSB.
-
Quote:
Originally Posted by
raju
... snip...
I know mate I agree with you, just giving 'fresh' evidence to support both our recomendations :)
-
well.. 11 and 12 multi's both proved stable at all the stock settings.
13 multi required me to increase the VID to what the processor is spec'd for around 1.35v but no other changes. this brings me to my highest cpu clock i've achieved on the board of 3467 mhz and it passes OCCT on air which seems incredible.
although i realize the memory throughput is restricted by the lower FSB. i'm not sure how to calculate what FSB is required to fully support 3.4ghz... but regardless this clocking gives me my fastest super PI ever!
-
SuperPi and wprime times are largely ineffected by FSB speeds I've found... its the raw CPU frequency and RAM timings that make the difference... in my experience.
-
hum updated to beta bios but i cant change the multiplier? You do it in the FSB menu correct?
-
Well, I spent all evening trying to get a good overclock on my x8 multi. I was shooting for 450x8 to equal my previous 400x9. Board/CPU/NB just couldn't do it even with voltages maxed, I couldn't load Vista after 430FSB... tried every GTL setting under the sun and the moon!
So, it would appear something on my system is FSB limited as I can boot Vista at 430x9 but not 440x8.
So, back to x9 multi. I'm going to see if I can increase my previous overclock at all.
BTW, Jobeo, nice OC on air! :shocked:
What are your voltages (CPU, NB, SB, VTT)?
-
My rig ran Orthos small fft's for 5 hours last night at 1850fsb/462.5 x 8 = 3.7GHz then I stopped it.
I then selected blend & it shutdown after 45minutes.
I had plenty of air blowing on the PWM & I am fairly convinced the PWM overheating is not the cause of the shutdowns.
The Coretemp/Smartguardian temps ran very close for the 5 hours which is much better than the 15oC difference there used to be with the last BIOS.
Now the temps run closer to each other & coupled with the Coretemp & Orthos logs I am sure its not a CPU temp shutdown problem either.
I was also running 2.3vdimm @ DDR925 CL5 on these sticks which is well within what I have previously tested these sticks to (DDR1000 @ 2.15v) so I am also sure the shutdowns aren't RAM related.
I will try messing around with voltages tonight & see if I can increase the 45min shutdown time.
Regards
Craig.
-
Silly question maybe, but is your RAM running in sync?
-
Quote:
Originally Posted by
Borgod
Silly question maybe, but is your RAM running in sync?
Yes although I have tried unlinked @ DDR900 where I know this RAM has run Orthos 8 hours + on this board with exactly the same 45min shutdown.
Craig.
-
Quote:
Originally Posted by
virtualrain
BTW, Jobeo, nice OC on air! :shocked:
What are your voltages (CPU, NB, SB, VTT)?
tx! nb, sb, and vtt are all stock settings you'd get without any tweaking. the CPU VID is the only thing i had to change its around 1.38v and drooping at idle to 1.34
don't get me wrong i dont think i'm going to win any overclocker of the year awards (unless its the noob oc'er of the year lol).... but, as you related in your GTL experience from last night, i find dealing with the NB, VTT, GTL's a major headache and very frustrating. the board is "extreme" as in extremely finicky when it comes to balancing those things.
like i said with the lower FSB the cores will bottleneck at the MCH if they all start accessing the ram at once. but for now i'm satisfied. i'd like to get my memory clocked up a bit and we'll see how that goes. when i get my stamina up a bit i'll probably start fidgeting with the FSB again but i'm tired of banging my head against the wall.
-
Quote:
Originally Posted by
Jobeo
tx! nb, sb, and vtt are all stock settings you'd get without any tweaking. the CPU VID is the only thing i had to change its around 1.38v and drooping at idle to 1.34
Ahh... the benefits of an unlocked multi... Luxury! You have no idea of the frustration level you would be under if you were trying to get that clock stable on a quad at x9 multi! :p:
-
old news? IDK, just thought I'd share this. Just used winflash184 to update from beta504 to beta521 bios without error.
Quote:
posted by virtualrain on his blog
At this time, Winflash does not work. It throws an error saying "Onboard BIOS not Award BIOS".
-
Quote:
Originally Posted by
xTr33m sammich!
old news? IDK, just thought I'd share this. Just used winflash184 to update from beta504 to beta521 bios without error.
Yeah, it should have been qualified to say it doesn't work on Vista x64.
-
Right after a full days worth of messing about I have found out what was causing the shutdowns it was the SB voltage.
I initially upped the NB & SB voltage almost together with the CPU drive set on strong as its the only way the board would boot. I have now found by switching the CPU drive to weak I can significantly reduce the SB voltage needed yet it will still allow me to up the NB voltage.
I have run 12 attempts at 462.5fsb x 8 = 3.7GHz today all ending between 20 minutes & an hour & a half with an Orthos fatal error rather than a shutdown.
From this I come to the conclusion that 3.7GHz isnt going to happen with this E6400 on air despite it being 5 hours+ Orthos stable on small fft's.
I reduced the fsb to 1825 456.25 x 8 = 3650MHz & it ran Orthos for 8 1/2 hours on blend until I stopped it.
Regards
Craig.
-
thats really odd..
I had the same problem with the same settings and orthos going BSOD on my arse at 462.5x8 3.7ghz....
what are your bios settings, got mine stable for 8hrs with a significant Vcore increase.. it will still bsod at that speed if i leave it going for 10-20hrs.. I havent played with the gtl ettings at all, maybe I should.
-
-
Quote:
Originally Posted by
xTr33m sammich!
thats really odd..
I had the same problem with the same settings and orthos going BSOD on my arse at 462.5x8 3.7ghz....
what are your bios settings, got mine stable for 8hrs with a significant Vcore increase.. it will still bsod at that speed if i leave it going for 10-20hrs.. I havent played with the gtl ettings at all, maybe I should.
My settings are nothing special at all but here they are for 3650MHz & I think I could get 3.7GHz Orthos stable with even more vcore but as you can see I am already piling it on.
I have had a little play with vtt & gtl but didn't find anything that helped me but I haven't finished playing with it yet.
One more thing even with the ldt vtt & sb dual voltage all on default minimum the board will still run PCI-E 130mhz & SPP 300MHz quite happily.
Regards
Craig.
Code:
Genie BIOS Settings:
Voltage Control:
CPU VID Control................ - 1.60000V
CPU VID Special Add............ - 101.55%
CPU Drive Strength............. - Weak
DRAM Drive Strength............ - Weak
DRAM Voltage Control........... - 2.18V
NB Voltage Control............. - 1.57V
SB Voltage Control............. - 1.62V
SB Dual Voltage................ - 1.52V
LDT Voltage Control............ - 1.22V
CPU VTT 1.2V Voltage........... - 1.21V
GTL REF Voltage Control........ - Disable
FSB & Frequency Seting:
FSB-Memory Clock Mode.......... - Linked
FSB-Memory Ratio............... - Sync Mode
FSB (QDR), MHz................. - 1825
=====
PCI Bus, Slot 1 MHz............ - 100
PCI Bus, Slot 2 MHz............ - 100
SPP <-> MCP Ref Clock, MHz..... - 200
LDT Frequency.................. - 5x
CPU BSelect.................... - BSel_7
CPU Clock Ratio Unlock......... - Enabled
CPU Clock Ratio................ - 8x
CPU Feature:
PPM Mode....................... - Native Mode
Limit CPUID MaxVal............. - Disabled
C1E Function................... - Disabled
Execute Disable Bit............ - Enabled
Virtualization Technology...... - Enabled
Core Multi-Processing.......... - Enabled
Memory Timing Setting:
Memory Timing Setting.......... - Expert
CAS Latency Control (TCL)...... - 5
RAS# to CAS# Delay (TRCD)...... - 5
Row Precharge Time (TRP)....... - 5
Min RAS# Active Time (TRAS).... - 15
Command Per Clock (CMD)........ - 2T
=====
Bank To Bank CMD (TRRD)........ - 4
Row Cycle Time (TRC)........... - 28
Write Recovery (TWR)........... - 6
Write -Read Commad............. - 10
DRAM Refresh Rate.............. - 7.8uS
-
Ive finally gave up with the throttling issue on this board with Quads. No matter how much I cool the PWM, anything over 1.3875 vcore will start going back and forth between 6 and 9 multi on my Q6600 after around 5 minutes of Quad Prime Small FFT.
Core temps dont exceed 65c fully loaded at 1.425. It happens much quicker if I remove my PWM fan.
I know this quad has more in it. But I am just sick of not having my main rig up, (First Crappy IN9-32X, Blown BX2, Blown Gskill Memory, etc..) I'm sitting at almost 4 months on this rebuild cycle.
I put my E6600 back in, got it to 3650 very easily. Much easier and at lower voltages than my IN9.
I think I am just going to dump the Quad for now, and rebuy one sometime later this year when the P35 chipsets mature a bit.
-
Ya the PWM heatsink is just a really crappy painted aluminum heatsink, its a shame DFI went really cheap quality on it. Mine are starting to make a hissing sound during quadprime 95 and shutting off.. I've got 2 fans trying to blow over them :shrug:
On the cpu throttling download rightmark cpu clock utility and you can disable the throttling there.
-
Quote:
Originally Posted by
Spazilton
anything over 1.3875 vcore will start going back and forth between 6 and 9 multi on my Q6600 after around 5 minutes of Quad Prime Small FFT.
i feel your pain ... i have a quad (qx6700) and the experience can, at times, feel very un-rewarding with this board.
question for ya though what speeds are you trying to reach going above the 1.3875 vid? like, what are you stable at 1.3875 which is forcing you to up the volts...
-
Quote:
Originally Posted by
vincey2kr1
Ya the PWM heatsink is just a really crappy painted aluminum heatsink, its a shame DFI went really cheap quality on it.
i have a theory... remember how the PWM temp was mis-labeled in all the BIOS's except the most recent? i think when they were designing the board they were relying on those reported temps and thinking the PWM was fine...
otherwise i don't see how they would have released the board with such a bad solution. the HS does look quite cheap and they've sandwiched it in-between a bunch of components... there's no way it could be getting decent airflow the way its designed which is why people have to rig fans on it...
-
Quote:
Originally Posted by
C-N
Right after a full days worth of messing about I have found out what was causing the shutdowns it was the SB voltage.
I initially upped the NB & SB voltage almost together with the CPU drive set on strong as its the only way the board would boot. I have now found by switching the CPU drive to weak I can significantly reduce the SB voltage needed yet it will still allow me to up the NB voltage.
Craig, So are you saying the SB voltage being too high was causing the shutdown? At what point does the SB voltage cause this?
Also, I'm not sure I understand your SB voltage comments... on one hand, you are saying you can significantly reduce the SB voltage, but in your settings in your next post it's at 1.62V. a) that's not significantly reduced (although I'm not sure where you had it before) and b) 1.62V for the SB is what Tony's overclocking guide recommended.
Another thing, you say running weak CPU drive, allows you to up the NB voltage, but according to your setting, you are running 1.57 which after the droop is about 1.45 actual... not that very much for 450+ FSB.
Finally, Tony had this to say about CPU drive strength...
Quote:
If the CPU needs Strong Drive you will have a low to middle NB voltage setting.
If the CPU needs Weak Drive you will have a middle to higher NB voltage setting
It sounds like you agree with this, although I still maintain your NB voltage is not very high at all for the FSB you are running.
Some additional clarification on what you have found would be helpful... Thanks!
-
BTW, have you guys seen this (DFI X38 board)? Does it appeal to any of you?
-
I'm sure it will appeal to many...
-
Quote:
Originally Posted by
virtualrain
Craig, So are you saying the SB voltage being too high was causing the shutdown? At what point does the SB voltage cause this?
On my rig 1.74 - 1.76v
Quote:
Also, I'm not sure I understand your SB voltage comments... on one hand, you are saying you can significantly reduce the SB voltage, but in your settings in your next post it's at 1.62V. a) that's not significantly reduced (although I'm not sure where you had it before) and b) 1.62V for the SB is what Tony's overclocking guide recommended.
I have been up to 1.76v in the attempt to find stability so reducing to 1.62v imo is significant. Also 1.62v is one maybe 2 clicks over what I need to run stable.
I found Tonys guide interesting to read but that was it. None of his findings or settings have benefited me & my rig this time.
Quote:
Another thing, you say running weak CPU drive, allows you to up the NB voltage, but according to your setting, you are running 1.57 which after the droop is about 1.45 actual... not that very much for 450+ FSB.
My rig would not boot over 1.51v NB with strong CPU drive strength unless I had the SB voltage over 1.7v
My 1.57v atm is one or 2 slicks over what I need for 450fsb too.
Quote:
It sounds like you agree with this (Tony's guide re cpu drive strength/nb voltage) although I still maintain your NB voltage is not very high at all for the FSB you are running.
I do agree with Tony with an E6400 but wonder how this may differ with a quad core. I notice you are running high v NB with your quad @ 400fsb my E6400 rig will run 490fsb (thats as far as I have taken it) with lower NB voltage than you are using.
Regards
Craig.
P.S Sorry to post a slow reply but I don't get email notifications from this forum although I have it enabled it just don't work for me.
-
Quote:
Originally Posted by
virtualrain
BTW, have you guys seen this (
DFI X38 board)? Does it appeal to any of you?
I will take one put my name on the list :D
Proper Caps on this board wonder if they will still be there at retail launch ?
Craig.
-
Quote:
Originally Posted by
virtualrain
BTW, have you guys seen this (
DFI X38 board)? Does it appeal to any of you?
that makes me have buyers regret for getting the 680i from dfi, why would you be so cold hearted to post that in here :(
-
DFI Roadmap Mobo release dates
-
Quote:
Originally Posted by
C-N
I do agree with Tony with an E6400 but wonder how this may differ with a quad core. I notice you are running high v NB with your quad @ 400fsb my E6400 rig will run 490fsb (thats as far as I have taken it) with lower NB voltage than you are using.
Thanks for your added insights... I'll add the stuff about the SB voltage causing shutdowns to my FAQ blog post. How long does the board take to shutdown with high SB voltage and what stress testing seems to replicate it reliably?
As for my NB voltage, I have to admit, I'm still not sure what to do with it. I've found I need it relatively high to run my memory at 1T but I haven't spent enough time trying to lower it and retest to know where the limit is.
-
Quote:
Originally Posted by
Wiggy McShades
that makes me have buyers regret for getting the 680i from dfi, why would you be so cold hearted to post that in here :(
Sorry! It shouldn't give you buyers remorse... you have a good board!
Keep in mind that we first saw the DFI 680i board back in Dec! Who knows when this board will actually be available. Hopefully sometime before the next generation! :p:
-
Quote:
Originally Posted by
virtualrain
Thanks for your added insights... I'll add the stuff about the SB voltage causing shutdowns to my FAQ blog post. How long does the board take to shutdown with high SB voltage and what stress testing seems to replicate it reliably?
It took between 20 & 45minutes & Orthos blend on priority 8+
Quote:
As for my NB voltage, I have to admit, I'm still not sure what to do with it. I've found I need it relatively high to run my memory at 1T but I haven't spent enough time trying to lower it and retest to know where the limit is.
It may be the 4GB or even the quad that is demanding the NB voltage but considering the extra load your NB has compared to mine your voltage isn't crazy its just surprising its that high at 400fsb which would suggest to me you couldn't get much more out of your RIG even if the CPU could do it.
I have just had a little play & my board will boot 1970fsb on 1.51v NB although you do need 1.6 + to run 3dmark & keep the bandwidth up in Everest. All other voltages are at minimum.
I haven't found a massive drop in bandwidth from 1t to 2t why don't you drop to 2t & see how low you can drop the NB voltage just out of curiosity.
Craig.
-
Quote:
Originally Posted by
C-N
It took between 20 & 45minutes & Orthos blend on priority 8+
It may be the 4GB or even the quad that is demanding the NB voltage but considering the extra load your NB has compared to mine your voltage isn't crazy its just surprising its that high at 400fsb which would suggest to me you couldn't get much more out of your RIG even if the CPU could do it.
I have just had a little play & my board will boot 1970fsb on 1.51v NB although you do need 1.6 + to run 3dmark & keep the bandwidth up in Everest. All other voltages are at minimum.
I haven't found a massive drop in bandwidth from 1t to 2t why don't you drop to 2t & see how low you can drop the NB voltage just out of curiosity.
Craig.
I am definitely FSB limited on my rig... as you say it could be the 4G or the quad. I can boot at 430x9 but not 440x8 so 430 is the most I can get out of it even though the memory can run 1T to 900MHz and the quad is clearly stable at 3.6GHz. You would think 450x8 would be feasible but it's not. It's very stable at 400x9 and I'm happy with that.
It's just a matter of tweaking voltages to run it as cool as possible...
Since I'm going to be cooling the NB with water when I go 24/7 with it, I'm not too concerned about the voltage, but when I get around to it, I'll play with it somre more. I know it can go much lower on 2T with relaxed timings.
I'll definitely report anything new that I find.
-
Quote:
Originally Posted by
virtualrain
Sorry! It shouldn't give you buyers remorse... you have a good board!
Keep in mind that we first saw the DFI 680i board back in Dec! Who knows when this board will actually be available. Hopefully sometime before the next generation! :p:
Yes, but we have to keep also in mind that this is a ddr2 board. If DFI wants to stay in the game, they should go out really fast with this board just to be in time with ddr3 also.
-
I lapped my QX6700 today. Temps have come down a few degrees which is great, but temps between all 4 cores is very even now under load.
I also rotated my NB heatsink 180 so the pipes are over the NB chip, and put an 80mm fan blowing up aswell. It's really made no difference. On load the NB temp is still just over 80degrees :(
However I put a 70mm fan over the PWM heatsink so that would of made a good different Im sure as that was too hot to touch before.
-
Quote:
Originally Posted by
Borgod
I also rotated my NB heatsink 180 so the pipes are over the NB chip, and put an 80mm fan blowing up aswell. It's really made no difference. On load the NB temp is still just over 80degrees :(
I would have said even taking into consideration you have a quad & your in sunny Perth your NB temp is too high. I can only just hit mid 50's with loads of NB voltage & tight ddr900 1t under full load most of the time my rig runs 45-50oC.
silly question but did you remove the extra little foam triangle from the NB before you put the heatsink on & what thermal compound are you using ?
Craig.
-
C-N should that triangle be removed before attaching heatsink?
-
Quote:
Originally Posted by
AlphaHeX
C-N should that triangle be removed before attaching heatsink?
Officially I don't know & DFI dont make it very clear but the way I saw it there was no way the heatsink would sit level/flat if it were left on so I took it off & my temps are great.
Craig.
-
Ok, then I will reaply my heatsink for the 2nd time :)
-
I actually left the little triangle ON. I think it depends which orientation you use for the stock heatpipe cooler, it definitely lined-up with the edge of the triangle in the orientation I used. (Tower farthest away from CPU.)
-
Can someone tell me what idle/load temps should I expect with Tuniq Tower (Arctic Silver 5) and E6600 CPU at default speed and voltage 1.28? and with 3.2 overclock and voltage 1.4?
-
Quote:
Originally Posted by
volve
I actually left the little triangle ON. I think it depends which orientation you use for the stock heatpipe cooler, it definitely lined-up with the edge of the triangle in the orientation I used. (Tower farthest away from CPU.)
Mine must have been stuck on wrong then as my triangle bit was near the PCI-E slot & if you fitted the heatsink tower to PCI-E slot the you ended up with a triple foam pad thickness PCI-E side & double on the CPU side.
I took my triangle off & tested the board & I then realised the 680 chip is not in the centre of the 4 hook mounting but rather its off centre toward the CPU socket & logically I figured the NB heatsink heatpipe would be better over the chip than off to the side so I rotated the heatsink.
My temps are way better tower to CPU socket rather than tower to PCI-E.
Regards
Craig.
-
Quote:
Originally Posted by
Apollonas
Yes, but we have to keep also in mind that this is a ddr2 board. If DFI wants to stay in the game, they should go out really fast with this board just to be in time with ddr3 also.
DDR2 is still where the action is at performance wise, the latencies on all current ddr3 chips are still too loose to compete with good ddr2, couple that with high priced ddr3, ie $600 or so for a kit and you begin to see the reasoning. Not to mention the ddr2 true 1066 parts are on the way. I don't believe we will be seeing any truly worthy ddr 3 until the end of this year..
regards
Raja
-
Quote:
Originally Posted by
C-N
I would have said even taking into consideration you have a quad & your in sunny Perth your NB temp is too high. I can only just hit mid 50's with loads of NB voltage & tight ddr900 1t under full load most of the time my rig runs 45-50oC.
silly question but did you remove the extra little foam triangle from the NB before you put the heatsink on & what thermal compound are you using ?
Craig.
Previously I left the triangle attached, but yesterday I removed the triangle and it made no difference. It wasn't easy removing the triangle without making a mess of the foam surrounding it so I'm thinking it's not supposed to be removed.
I'd like it if someone could remove all the foam together and test temps :)
However my 70mm fan over my PWM's has made a big difference as my QX6700 was prime stable 8 hours at 3550Mhz over night :) temps were just under 70degrees aswell which is excellent for me.
Tonight I shoot for 3600Mhz.
raju I know you watercool your NB together with your SLI 8800GTX's with a PA120.3. How do you think it would effect temps if I just used a PA160 ? Im considering SLI and already have the PA160 mounted and ready to go. I need to find another DDC+ however since two have been returned under warranty already :(
-
hrmm... the extra triangle on mine peeled off very easily. like it wasn't attached to anything. i'm not sure why it was there to begin with. once it was gone the pad on the NB HS was fully intact...
when you say 70c borgod are you referring to the NB or the cpu cores? what temps do your cores get to and what kinda cooling ?
-
@C-N:
Well, I had to rotate mine as my Enzotech Ultra-X doesn't permit the tower to be CPU-side vs. PCIe-side.
I would say temperatures seem fairly reasonable, although I'll await a full stable BIOS update so they've got the labeling round the right way before I get terribly concerned.
-
CPU temps on load while priming is just under 70degrees with 20degrees ambient. This is with a lapped QX6700, Fuzion block, DDC+ with Petras top and a PA120.2 radiator and 1/2" tubing. This is at a voltage of 1.45625 + 1.02%
NB temps vary from 70-80 degrees whether idling or on load it doesnt matter.
This is with NB heatsink mounted both ways, with a 70mm or an 80mm fan attached... no difference with the side of the cass off. AS5 TIM (thin layer) used also. voltage of NB at 1.52v
The temps don't vary a great deal which tells me the Heatsink IS making contact with the NB, but just doing a poor job of cooling it. I want to remove one layer of the foam, but Im not game enough :D
-
my NB is at 38C right now watercooling with swiftech mcw30...
-
What else is in your loop Grinch?
-
I tried lowering my voltages today, one at a time and seeing if the OC was still good. I played with CPU, NB, and RAM voltages only. I left the SB, VDT, and GTL voltages alone. Here are my findings:
- To run my CPU at 400x9, requires max Vcore (set 1.6V get 1.55V or 1.50 under load).
- With RAM timings relaxed and running 2T, it was stable with lower NB voltage (i.e. 1.47V) and RAM voltage (i.e. 2.1V).
- With RAM timings relaxed and running 1T, my OC needs NB to be at 1.6V actual (set to 1.74 or max) and RAM at 2.3V actual to be stable.
- Tightening timings at 1T requires no extra voltage.
Hence, the bottom line for me is that my CPU is about as maxed out as it can get and still be PRIME stable. I appear to be FSB limited as I can't boot at 440x8 but I can boot at 430x9. I can't get stable at 430 though, it would require radical cooling and more voltage than I care to dial in.
Running 4GB of RAM at 1T is clearly challenging for this board (maybe any board). It requires me to max the NB voltage (which has terrible droop) and run my RAM at max allowable voltage (according to Mushkin).
So, no matter what tweaking I do, I don't think I'm going to improve this overclock. Fortunately, my volt modded 8800GTX should be here any day so I'll have to get onto that next.
Comments/Opinions welcomed.
-
Question: has anyone noticed any performance improvement with the 521 bios or was it just a bug fix release (and a small set of bugs at that)?
-
Cant say I've really noticed any improvement in overclocking.
Although I hit 3550Mhz Prime Stable lastnight 8hrs, whereas before it was only prime stable 1.5hours but I have played with voltage and GTL settings since then.
One odd thing I found.
12x300 = 3600Mhz doesnt boot into windows
11x327 = 3598Mhz has no problem at all and is currently priming as we speak.
You're a lucky man to have those Mushkin sticks. I wonder how 4x1GB sticks would go, considering how much this board dislikes 1T in those orange RAM slots.
-
Quote:
Originally Posted by
virtualrain
- With RAM timings relaxed and running 2T, it was stable with lower NB voltage (i.e. 1.47V) and RAM voltage (i.e. 2.1V).
- With RAM timings relaxed and running 1T, my OC needs NB to be at 1.6V actual (set to 1.74 or max) and RAM at 2.3V actual to be stable.
- Tightening timings at 1T requires no extra voltage.
Thats very interesting to know out of interest how much performance do you gain at 1t compared to 2t.
I had a little play last night & run 465 x 8 sync 4.3.3.6 2T with just 1.57v NB & 2.30v on the RAM set in BIOS (2.22v in Windows) which is more than I need but just added a bit to be on the safe side whilst playing.
I still got 11500mb/s & 46ns latency in Everest which is only a couple of hundred mb/s off what I can do with these DIMMS @ 1t.
Craig.
-
Quote:
Originally Posted by
Borgod
What else is in your loop Grinch?
I am running 2 seperate loops:
http://www.xtremesystems.org/forums/...30&postcount=1
1st loop is dtek fuzion...petras pump...pa120.3
2nd loop is petras pump...swiftech mcw30...ek full cover gpu...pa120.2
-
Got up, out of bed, somethings wrong:confused:
My box is hung on a post, Look at BIOS, settings are whacked, shut down, clear cmos, back to bios.. setting thins back up and checking, my mems are set at 3.04v!?! :shrug: why!?! quick to power down clearcmos and nuthin, "code88"
now one stick gets code 88 and the other beeps and hangs at code 31..
I surely did not set vdimm to 3.04v I run always at 2.2v
The clear cmos should have given me 1.9v as always.
But it was at 3.04v for moments and it took my ram. 2x1GB ballistix ddr1000. :down:
Now I've got an RMA with NewEgg, but I think I would preffer DFI taking care of it.
tested with different ram works again, no other damage as far as I can tell atm.
-
Quote:
Originally Posted by
xTr33m sammich!
Got up, out of bed, somethings wrong:confused:
My box is hung on a post, Look at BIOS, settings are whacked, shut down, clear cmos, back to bios.. setting thins back up and checking, my mems are set at 3.04v!?! :shrug: why!?! quick to power down clearcmos and nuthin, "code88"
now one stick gets code 88 and the other beeps and hangs at code 31..
I surely did not set vdimm to 3.04v I run always at 2.2v
The clear cmos should have given me 1.9v as always.
But it was at 3.04v for moments and it took my ram. 2x1GB ballistix ddr1000. :down:
Now I've got an RMA with NewEgg, but I think I would preffer DFI taking care of it.
tested with different ram works again, no other damage as far as I can tell atm.
Holy $hit....that's not good...so it was running fine and then...all the sudden it overvolts your ram to 3.04V...on it's own?:eek:
-
Thats about all I can figure out, 3.04v right after clearing CMOS via jumper. I've never set it past 2.4v personally, and that was some cheapo dell 2x256MB ddr533@1066.
-
wow....hope they are working on some new bios's for this...
-
has anyone gotten their board to report proper temps, i have the latest beta bios and i still have a huge issue with temp readings. my cpu temp is 50 idle and 53 loaded north bridge is 40 idle and 43 loaded... this is water cooled and ive remounted the nb and cpu block twice and both times they were making proper contact. also my on board nic's stopped working randomly but thats totally unrelated.
although this is with a balck ice stealth gt 360 and an mp-05 sp, not the water cooling in my sig. also the temps i said im getting are both at 3.8ghz and at stock speeds.
-
The 05/04 beta bios corrected this issue.
-
Quote:
Originally Posted by
Praz
The 05/04 beta bios corrected this issue.
thats the bios i have yet my temps still are no different between load and idle.
-
Quote:
Originally Posted by
Wiggy McShades
has anyone gotten their board to report proper temps
My board & Smartguardian reports temps just fine using the 521 BIOS.
Regards
Craig.
-
Quote:
Originally Posted by
C-N
My board & Smartguardian reports temps just fine using the 521 BIOS.
Regards
Craig.
Same here. Use CoreTemp or Speedfan (which reports CoreTemp but you need to add 15-deg offset) for CPU temps.
Craig, I will try high-clock 2T tonight in the yellow slots and see what it can do. Last time I played with high-clock 2T, my Read bandwidth at 1120MHz 5-5-5 2T was lower than 4-3-3 1T at 800MHz.
-
Quote:
Originally Posted by
xTr33m sammich!
Thats about all I can figure out, 3.04v right after clearing CMOS via jumper.
hrmm.... wow. thats not good. which BIOS were you using?
kinda scary to think about cause once ya boot with the overvolt like that its all over... nothing you can do to fix it real quick.
i haven't cleared the CMOS by jumper in a long time... i always use the reset/power button trick. hrmmmmmmmmmmm.
-
Happened while using Beta 4CTST521. I had been using it for several days, and had originally cleared CMOS via jumper after updating to it.
I'm a little put off by it, and lucky enough I guess to have Newegg on my side, they agreed to full refund for board and ram no restocking fee.
Now I just have to decide what I'm gonna do. Anyone know if theres an sli hack for the p35? otherwise I may have to sell a pair of 8600GT's.
-
Quote:
Originally Posted by
xTr33m sammich!
I'm a little put off by it, and lucky enough I guess to have Newegg on my side, they agreed to full refund for board and ram no restocking fee.
hrmm... if you give up on the board the DFI 680i userbase will drop by about 25% ... lol j/k
i feel your pain. i would be very upset if this board just up and decided to overvolt my ram that way. so far it hasn't happened to me.
i hope they continue to put time into developing this BIOS ... although i fear they won't. i expect about 1 or 2 more updates before they move onto other things.
-
Quote:
Originally Posted by
Jobeo
hrmm... if you give up on the board the DFI 680i userbase will drop by about 25% ... lol j/k
i feel your pain. i would be very upset if this board just up and decided to overvolt my ram that way. so far it hasn't happened to me.
i hope they continue to put time into developing this BIOS ... although i fear they won't. i expect about 1 or 2 more updates before they move onto other things.
With pics of the X38 board in circulation, I'm afraid we may get left in the dust also. Hopefully they at least get bugs like this fixed before moving on.
BTW, I also use the power/reset button to clear CMOS and it has worked flawlessly for me (many many times!).
-
Quote:
Originally Posted by
virtualrain
With pics of the X38 board in circulation, I'm afraid we may get left in the dust also.
ya but as you pointed out a few posts ago who knows when DFI will release that. i mean we saw pics of the 680i board at the start of 2007 and look when it came out.
if they do get it out a few months from now i'd consider moving over to it... if it still supports my qx6700 that is. i like the idea of better stock cooling for the PWM and NB, things they should have done for the 680i to begin with. for now i'm satisfied which is good cause i doubt DFI's x38 solution will be released this year.
-
Quote:
Originally Posted by
Jobeo
ya but as you pointed out a few posts ago who knows when DFI will release that. i mean we saw pics of the 680i board at the start of 2007 and look when it came out.
if they do get it out a few months from now i'd consider moving over to it... if it still supports my qx6700 that is. i like the idea of better stock cooling for the PWM and NB, things they should have done for the 680i to begin with. for now i'm satisfied which is good cause i doubt DFI's x38 solution will be released this year.
Jobeo, what is it going to take to get you to switch to water cooling! :yepp:
Do it man! :D
-
Quote:
Originally Posted by
Jobeo
ya but as you pointed out a few posts ago who knows when DFI will release that. i mean we saw pics of the 680i board at the start of 2007 and look when it came out.
if they do get it out a few months from now i'd consider moving over to it... if it still supports my qx6700 that is. i like the idea of better stock cooling for the PWM and NB, things they should have done for the 680i to begin with. for now i'm satisfied which is good cause i doubt DFI's x38 solution will be released this year.
http://img299.imageshack.us/img299/3...2007ch0.th.jpg
-
-
Quote:
Originally Posted by
virtualrain
Jobeo, what is it going to take to get you to switch to water cooling! :yepp:
ya i prob should ... maybe if i knew what to buy. because its so new to me i can just imagine things going very wrong like my case being flooded with coolant or something.
i'm sure once i got it going i'd be very happy... i guess i'm stuck in the past i've cooled on air for so long ... =/
-
Quote:
Originally Posted by
Jobeo
ya i prob should ... maybe if i knew what to buy. because its so new to me i can just imagine things going very wrong like my case being flooded with coolant or something.
i'm sure once i got it going i'd be very happy... i guess i'm stuck in the past i've cooled on air for so long ... =/
Ahhh... no worries. If you get inclined PM me or drop into the water cooling forum. Just be prepared to layout more $$$ :p:
-
It's been reported that you should use the yellow slots for increased memory bandwidth and the orange slots for higher clocks with 1T (Link - see post 30/31). So I tried running my Mushkin PC2-8500 2x2GB kit in both the orange and yellow slots to see if there was any truth to this... well, here are my results...
http://members.shaw.ca/virtualrain/MemoryBW.png
Comments:
- Strangely, I could not get the board to POST with the RAM running at 1T in the yellow slots. :confused:
- At 1100MHz running 2T command rate, there was no difference between the yellow and orange slots with my memory.
- Oddly, when switching RAM between slots, the board requires a CMOS clear to POST. Then after adjusting settings (loading from cmos reloaded profiles for example) and rebooting, it would hang on POST code #75 for 2 minutes before rebooting normally. I'm not sure why it does this, any thoughts? At any rate, be patient if it does this.
- As I reported earlier, for me, 1T is marginally faster at 800MHz than 2T at 1100MHz (at least according to Everest... Sisoft Sandra has 1T slightly slower).
Based on my results, I feel bad for anyone trying to get good clocks on four sticks! Yikes!
-
BTW, I've updated my Tips and Tricks Blog Article to represent the most current wisdom with this board.
It's also available via my sig.
-
Quote:
Originally Posted by
virtualrain
Based on my results, I feel bad for anyone trying to get good clocks on four sticks! Yikes!
Yep, it has me very worried for future upgrades. :(
-
Quote:
Originally Posted by
virtualrain
It's been reported that you should use the yellow slots for increased memory bandwidth and the orange slots for higher clocks with 1t (
Link - see post 30/31). So I tried running my Mushkin PC2-8500 2x2GB kit in both the orange and yellow slots to see if there was any truth to this
I read that over at TTR but I cant find any difference between the slots at all & never have with any of the BIOS's I have used.
I put my OCZ 8500 SLI RAM & 8800gts in last night & ran 456 x 8 4.4.3.8 1T sync pci-e 120mhz spp 300mhz graphics card 595 x 950 the memory bandwidth is 11950mb/s & the latency is mid 43ns & it run Orthos 8 hours + again.
My NB voltage was 1.57 & the temp never hit 50oC
I am a happy man this board is super fast & rock solid stable I love it.
Craig.
-
Bios 2007/05/21 has been moved to stable section on DFI webpage :)
Major Reasons of Change:
1.Fixed Core Multi-Processing function fail issue on Intel Core 2 Extreme QX6700 /X6800 CPUs.
2.For Intel Core 2 Quad ,Intel Core 2 Extreme & X6800 CPUs only.
3.Fixed CPU Bselect can’t set to Auto mode with E6750(FSB 1333MHz) CPU.
4.DRAM Voltage will be selected on 3.04V when doing the load last bootable setting.
5.Fixed CPU Fan speed control.
As you can see point 4 is reffering to the DRAM voltage problems.
I'm wondering why it has happend to xTr33m sammich! if he was using that version of BIOS. Maybe there is a difference between beta 05/21 and final 05/21?
-
Well guys picked up a Asus Pk5Deluxe and no more shutdowns during 8k quadprimes now at 3.6ghz 8*450 (q6600) after only an hour of playing :D and I'm not done tweaking.. No sli dammit though but at least they implemented 1t timings now .. REally think with a nice aftermarket PWM cooler the DFI should of done the same.
-
Quote:
Originally Posted by
AlphaHeX
Bios 2007/05/21 has been moved to stable section on DFI webpage :)
Major Reasons of Change:
1.Fixed Core Multi-Processing function fail issue on Intel Core 2 Extreme QX6700 /X6800 CPUs.
2.For Intel Core 2 Quad ,Intel Core 2 Extreme & X6800 CPUs only.
3.Fixed CPU Bselect can’t set to Auto mode with E6750(FSB 1333MHz) CPU.
4.DRAM Voltage will be selected on 3.04V when doing the load last bootable setting.
5.Fixed CPU Fan speed control.
As you can see point 4 is reffering to the DRAM voltage problems.
I'm wondering why it has happend to xTr33m sammich! if he was using that version of BIOS. Maybe there is a difference between beta 05/21 and final 05/21?
An interesting change is that the original 2CTST file was noted as being for Q6600. The Beta 4CTST was noted as being for Quad Core and Extremes... very ambiguous if you owned a Q6600. Since the 2C version clearly stated it was for Q6600, I used that one (and it didn't affect my OC at all).
Now with it being published to the regular BIOS page, the 4CTST is noted as being for quad core and extreme processors while there is no mention of what processors the 2C version is for. Although I suppose it's obviously for dual-cores.
I guess I will have to try the 4C version now. Maybe it will improve my FSB wall issue. We shall see.
-
Quote:
Originally Posted by
vincey2kr1
Well guys picked up a Asus Pk5Deluxe and no more shutdowns during 8k quadprimes now at 3.6ghz 8*450 (q6600) after only an hour of playing :D and I'm not done tweaking.. No sli dammit though but at least they implemented 1t timings now .. REally think with a nice aftermarket PWM cooler the DFI should of done the same.
Arg! Another blow to this board's community... leaving a lone few to soldier on! :p:
-
More chaos with this board.
Earlier this week, I tried lowering my NB and RAM voltage to see if I could maintain my OC (400x9 Sync'd). No go. I couldn't lower either my NB or my RAM voltage even one notch and stay PRIME stable for more than an hour.
Last night I tried moving my memory from orange to yellow and then back to orange slots. I don't know what possessed me to try this, but before I went to bed, I lowered the NB voltage a few notches and the RAM voltage a notch and ran PRIME. Well much to my surprise, it was still running happily after 6+hrs this morning.
I just don't understand this board sometimes.
-
Genie BIOS Settings:
Voltage Control:
CPU VID Control................ - 1.28125V
CPU VID Special Add............ - Auto
CPU Drive Strength............. - Weak
DRAM Drive Strength............ - Weak
DRAM Voltage Control........... - 2.01V
NB Voltage Control............. - 1.44V
SB Voltage Control............. - 1.56V
SB Dual Voltage................ - 1.52V
LDT Voltage Control............ - 1.22V
CPU VTT 1.2V Voltage........... - 1.21V
GTL REF Voltage Control........ - Disable
FSB & Frequency Seting:
FSB-Memory Clock Mode.......... - Linked
FSB-Memory Ratio............... - Sync Mode
FSB (QDR), MHz................. - 1600
=====
PCI Bus, Slot 1 MHz............ - 100
PCI Bus, Slot 2 MHz............ - 100
SPP <-> MCP Ref Clock, MHz..... - 200
LDT Frequency.................. - 5x
CPU BSelect.................... - Auto
CPU Clock Ratio Unlock......... - Enabled
CPU Clock Ratio................ - 8x
CPU Feature:
PPM Mode....................... - Native Mode
Limit CPUID MaxVal............. - Disabled
C1E Function................... - Disabled
Execute Disable Bit............ - Enabled
Virtualization Technology...... - Enabled
Core Multi-Processing.......... - Enabled
Memory Timing Setting:
Memory Timing Setting.......... - Expert
CAS Latency Control (TCL)...... - 4
RAS# to CAS# Delay (TRCD)...... - 4
Row Precharge Time (TRP)....... - 4
Min RAS# Active Time (TRAS).... - 12
Command Per Clock (CMD)........ - 2T
=====
Bank To Bank CMD (TRRD)........ - 3
Row Cycle Time (TRC)........... - 22
Write Recovery (TWR)........... - 5
Write -Read Commad............. - 9
DRAM Refresh Rate.............. - 7.8uS
not that this is a BIG overclock...just wanted to share where I am 100% stable right now...here are my temps:
Cpu-Z Shot:
http://www.ximages.us/thumbs/default/cpu-z.JPG
http://www.ximages.us/thumbs/default/temps_1.2875V.JPG
-
Quote:
Originally Posted by
Grinch
Genie BIOS Settings:
Hey Grinch,
Thanks for sharing all the hard work. This is exaclty what I've been looking for here. I wish someone would start a data base thread.
This will be (almost) my set up when it gets here. I already received the mobo & e6600 but the ram (xms8500C5DF) % the GPU (EVGA 640-P2-N821-AR) got stollen from my front porch. Believe it or not UPS thinks there driver stole the FedX box who came late that day. They have placed a dummy box on my front porch with a micro cam in it to maybe catch him snooping around my porch. It has 40hour tape in it.
It's a real bummer cause Fedx won't pay up until they investigate which usually take 6 weeks before they payoff and zipzoomfly won't do anything until they do. Screwed up rebates and checking the hardware in case I need to use the 30day return/exchange/defectives with the suppliers. I usually order a complete system all at once for just that reason. I timed it so well it all came the same day. I don't think I'll do that again.
O well maybe it's a blessing I will seek a refund and rethink my choices for ram & gpu.
-
Oh man that sucks :(
I get all my stuff delivered to my workplace now so I'm guaranteed to get it on delivery. Good luck with the investigation.
Also, I agree with the database thread :D
-
Quote:
Originally Posted by
owcraftsman
Hey Grinch,
Thanks for sharing all the hard work. This is exaclty what I've been looking for here. I wish someone would start a data base thread.
This will be (almost) my set up when it gets here. I already received the mobo & e6600 but the ram (xms8500C5DF) % the GPU (EVGA 640-P2-N821-AR) got stollen from my front porch. Believe it or not UPS thinks there driver stole the FedX box who came late that day. They have placed a dummy box on my front porch with a micro cam in it to maybe catch him snooping around my porch. It has 40hour tape in it.
It's a real bummer cause Fedx won't pay up until they investigate which usually take 6 weeks before they payoff and zipzoomfly won't do anything until they do. Screwed up rebates and checking the hardware in case I need to use the 30day return/exchange/defectives with the suppliers. I usually order a complete system all at once for just that reason. I timed it so well it all came the same day. I don't think I'll do that again.
O well maybe it's a blessing I will seek a refund and rethink my choices for ram & gpu.
Sorry to hear about your stuff...are you going to watercool? You know how fun it would be to catch somebody in the act of stealing your stuff? I can say this..by the time the police arrived there would be only 1 story...MINE!
Quote:
Originally Posted by
Borgod
Oh man that sucks :(
I get all my stuff delivered to my workplace now so I'm guaranteed to get it on delivery. Good luck with the investigation.
Also, I agree with the database thread :D
We should have a database thread....:clap: :up:
-
wonder if nvidia monitor will ever be updated to read our dfi boards properly?
