Quote:
Originally Posted by c42
for me, changing to cas1.5 netted me about 2-3 more mHz on my DDr oC.
C
Printable View
Quote:
Originally Posted by c42
for me, changing to cas1.5 netted me about 2-3 more mHz on my DDr oC.
C
Yea I was hoping for that, but unfortunately nope! Although I didn't try higher than 3.7 with 1.5 cas, we'll see if a burn in helps ;).
All I know is that my dfi gets along well with it, it didn't play nice with my pc4800. So I'm loving it =). 15mhz o/c doesn't hurt either heh.
I will say one thing that most know though, the mosfet gets burning HOT! Most people know this, but just restating. As most everyone knows to run at 3+ vdimm you are gonna require some kind of active cooling, 1 80mm over the ram, and 1 80mm over the mosfet is plenty for me.
read this....
Active Cooling Required *----Due to the extreme speed of these modules along with the added voltages used, Mushkin requires end users to Actively cool their memory modules. Modules that are not properly cooled will/may not meet rated timings and speeds, and may become suceptable to premature failure. We generally recommend 15-25cfm of direct airflow over the ram modules which can be easily accomplished with one 60mm or 80mm low rpm fan. This will insure increased stability and lifespan of your Redline modules
Recommended Platforms--- Mushkin tests all Redline memory modules on Athlon64 platforms. Furthermore, when running two modules, only Socket 939 platforms are validated to run at rated specifications/timings. We currently recommend and validate the Redline memory series on the DFI LanParty UT NForce4 Ultra-D, DFI LanParty UT NForce4 SLI-DR, and DFI LanParty NForce4 SLI-DR boards as they provide the best combination of voltage options and compatibility for the Redline Series. Other motherboards may work, but may require modification for adequate voltages, and may not produce optimal results. Single Channel Athlon64 systems may have a hard time running 2x512mb dimms at rated speeds due to memory load on the single channel memory controller. Pentium4 and AthlonXP systems generally will not obtain rated specifications secondary to motherboard/memory controller limitations. These modules are compatible with most motherboards for Pentium4/AthlonXP CPUs, however end users are advised that lower frequencies achieved are a very real possibility.
Try it and see if it helps to cool it.
Duonger
For some reason, my Redline won't OC at all. My OCZ and G. Skill UTT modules OC'ed okay, it's just this set. I guess I'll have to call tech support again tomorrow. It's very strange, it'll pass Memtest no problem at my OC'ed settings but it's just not stable in Windows at all. I always get BSOD's if I'm OC'ed. I haven't lost faith in Mushkin though, I just think I got a bad set.
SOunds like more of a settings/compatibility issue... because it passes memtest.Quote:
Originally Posted by B5I8
good luck!!
C
That's what I thought to, but I've exhausted all timing configurations and what not. I used the 316 BIOS and the 414-3 BIOS. Like I said, my G. Skill and OCZ UTT modules worked perfectly fine with either BIOS and the same settings. Maybe when I call tech support tomorrow, they'll have some magic setting that I somehow overlooked.Quote:
Originally Posted by charlie
I have it activley cooled, 1 80mm over the ram, 1 80mm over the mosfet ;). No way in hell would they run at 3.6 without it heh.Quote:
Originally Posted by Duonger
B518 I had a similiar problem with a previous set of ram, that it would pass memtest, p95, superpi, sandra, etc. Any test/benchmark i could throw at it, it would pass np, but if I went to play WoW or CS:S, I'd get memory errors. Couldn't explain it, b/c the memory was good, but just wasn't co-operating. Threw in the xp4000, processor is o/ced and it wasn't with the other memory, can play both games np, pass all tests etc.
hey hey - just wanted to note that these Mushkin sticks seem to run relatively cool. I'm still burning in (looping memtest) at 2-2-2-5 200mhz 3.2v and they're cool to the touch...my VX was scorching at these volts...i also have a 92mm fan blowing about 50cfm over them, but it was the same for the VX and they still got hot...dunno - but i like it :) I'm hoping to be able to push it to 250mhz tonight at 3.2v - my VX would do it after 24 hours of burn in...so we'll see..i'll be back with some results :)
Gonna have a 80mm pointed directly at the ram, 80mm fan on the mosfet and the 120mm panaflo high speed from the XP-120 cooling my ram...
JUST GOTTA WAIT FOR IT TO SHIP! :stick:
What kind of burning in is this ? :woot:Quote:
Originally Posted by AlterBridge86
can u list your timings for u?Quote:
Originally Posted by B5I8
maybe it's one of your bios settings, timings, drive strength etc...
I know that drive strength of 7 and data drive strength of 1 on bios 414-3 was helpful for me(thanks trans am ;))
Tedy - its the same burning in that Andy-OCZ had recommended we do to VX (which would naturally apply to all other CH-based products). Its basically setting tight tight timings at 200mhz with an average amout of volts - i personally choose 3.2v, some people range from 3.0v - 3.4v...either way, looping this for about 24hrs "breaks in" the RAM which gives it a bit more give...kind of like breaking in a baseball glove so that its not so stiff and makes it easier to catch a ball..same goes with ram...this should ultimately give you higher overclock using less voltage than you would need without the burn...i foud it helped out on my VX quite a bit, so i figured i'd try it out on this too...anyways, results after work ;)Quote:
Originally Posted by TEDY
No, but I did reset all settings. Unfortunately I was so disgusted I lost patinece and gave up. If I hadn't had tccd's perfectly stable at 300htt, I might have tried harder. To tell the truth, I'm not convinced that running 3.4+v 24/7 is such a good thing anyway.Quote:
Originally Posted by charlie
That sound familiar. Like Charlie said, there may be a setting or something to force more windows compatability, but I just didn't have the time to figure it out. I like tweaking, but these days my philosophy is it either works right from the start or it's outta here. Lifes too short.Quote:
Originally Posted by B5I8
Has anybody had any cold boot issues with the redline ram? I'm sick of dealing with it on my twinmoss and am thinking about trying these.
These are normally my settings:Quote:
Originally Posted by JNav89GT
200
enable
2
2
5
2
7
15
00
02
01
02
3072
1
enable
Increase
0
8
auto
7
5
16
enable
16x
7x
disabled 8 burst
I have also tried Mushkin's recommended settings of:
200
enable
2
2
6
2
8
auto
02
02
auto
auto
auto
auto
enable
auto
0
7
auto
7
auto
256
disable
8x
4x
disabled 8 burst
I've also tried upping the voltage to 3.4V. I'm going to give tech support a call right now.
Quote:
Originally Posted by B5I8
I was having similar problems when I raised my LDT and Chipset voltages. I would leave those at default settings.
(thanks JNav89GT ;)
Quote:
Originally Posted by 4X4N
my TMII's will not post in dual channel for some strange reason. But the Redline does. Each individual stick will work, so it's not the ram. I have tried bio 414-2 and 4-14-3. Has anyone else had this problem on the NF4 DFI?
Just got off the phone with tech support and it looks like these modules are going back.
What did tech say?Quote:
Originally Posted by B5I8
Duonger
200
enable
2
2
5
2
7
15
auto
auto
auto
auto
auto
auto
enable
auto
7
1
7
5
16
enable
16x
7x
disabled 8 burst
I think those are the settings I start with and tweak from there.
yeah, me too except for DRAM DRIVE STRENGTH, I use 6 or 8.Quote:
Originally Posted by JNav89GT
C
Quote:
Originally Posted by 4X4N
i had cold boot issue before... but not no more... i've been running 3.5v for over 2 months now... i found dat removing and switching ur ram from dimm slot to dimm slot will cause ur ram to latch up... i just kept my ram the way dey are now everything is working fine...
how about trfc = 12 instead of 15?Quote:
Originally Posted by charlie
12 yelds bh5
Mine won't even POST at 12 or 13 trfcQuote:
Originally Posted by esdee
C