Jump to content

LanceDiamond

Members
  • Content Count

    91
  • Joined

  • Last visited

Everything posted by LanceDiamond

  1. I just got the OCZ EL Platinum PC3200 and while I couldn't be happier, they are not super-OC memory. Various posts from OCZ people about this on their forums: http://www.bleedinedge.com/forum/showthread.php?t=14442 Basically they used chips that will run with very tight timings but I saw one post from an OCZ guy that said the max he got out of them was around 230mhz and had to go high on voltage (and heat as a result) to do it. I had Ballistix PC4000 - boxed up and going for a refund now - so I went from fast OC'able memory that ran hot as hell stable for 3 weeks and then failed to running at PC3200 speed and (I hope) stable for a good long time. The OCZ runs nice and cool/warm and seems perfectly happy with 2.7v - I may drop to 2.6v and see if it stays happy, which I suspect it will. The OCZ modules are much heavier than the Ballistix too - I think maybe the heat spreader is better on them and that is the extra weight. I haven't noticed much difference in benches either - Sandra memory is 6204/6174 running 237 x 11 (2607) with 9/10 divider (memory at 200mhz) on the OCZ. On the PC4000 Ballistix at 260 x 10 with no divider it was 6651/6591.
  2. I built a new system - my first AMD X2 - about 3.5 weeks ago. I went with fairly new memory in Crucial Ballistix 2gb PC4000 modules. Of everything I did, that was the only mistake. Go with KNOWN trusted memory. I've now replaced the Ballistix with OCZ Platinum PC3200 EL and everything is working great. The Ballistix are going back for a refund. Keep this in mind when thinking about trying new memory - maybe it'll be great - my Ballistix rocked for 3 weeks - but maybe it won't. If you run into problems, will you catch it within 30 days so you can get a refund or will it be 5 weeks and you'll be stuck doing RMAs til the cows come home? I'd eliminate the newer stuff - pick one of the well known ones - and the OCZ is working great for me (for 2 days now lol - so I guess I could hit some problem with them in 3 weeks like I did the Ballistix.)
  3. Not to be a pain in the butt, but two questions: 1) Did Jim from Crucial mention what he thought you'd find here that might affect your need for an RMA? From much reading here and on HardOCP forums, all I have seen can be summed up thus: Something is wrong with some of this memory and Crucial isn't real sure what it is. 2) In ref to the above "try this" why would you want to try PC4000 memory at PC3200 speed - what is that supposed to tell you? I ran mine at stock - 250mhz 3-4-4-8 - had to use 2.7v for any stability and still found errors 3 weeks after it was working just fine. These 1gb x 2 Ballistix run HOT - I suspect this memory is cooking itself. I don't understand why memory run at stock speed and voltage in adequate airflow with low ambient temps should be anywhere near as hot as this stuff gets. It can't possibly be a good thing it's so hot.
  4. It seems clear something funny is going on with this memory. From what I've read and now experienced, somewhere between 3 weeks and 3 months, you may see problems. There is now a post about this on HardOCP forums, one of the guys there collecting the batch numbers of the memory and trying to understand what is going on. I had run over 30 hours of continuous tests - 21 hours of dual prime95, and at least 4 hours of memtest in BIOS and at least 7 hours of the HCI design memtest with zero problems showing up. Then out of the blue I start bluescreening with no consistency as to when/where it happens. My Crucial Ballistix is out and boxed up to go back to Newegg for a refund - I'm just so glad I hit this problem at 3 weeks rather than 3 months when I couldn't get a refund! One thing I am noticing with the OCZ PC3200 Platinum that seems sort of odd - no real hard facts to back this up yet as I've only had the OCZ installed for a few hours now... My PWMIC temps with the Crucial were a hell of a lot hotter at idle and load than with the OCZ. I think my PWMIC idle temp was high 40s to 50 at idle and as high as 65+ at load with the Crucial. Now I notice with the OCZ Platinum in, my PWMIC temp idles at 38c or 39c. Also, I'm running the OCZ at 2.8v and ran 40 passes of BIOS memtest, then 100% coverage on two instances of HCI memtest and the memory is nowhere near as hot as the Crucial got (measuring this with my finger so kinda subjective.) With the Crucial it got so hot even at 2.7v while running memtests that it became very uncomfortable to touch after just a few seconds. The OCZ never gets particularly hot even at 2.8v. I will check the temp of the OCZ after an overnight run of memtests. The OCZ is running way slower than the Crucial of course since it's PC3200 versus PC4000 - but if both were running stock, I'd think the Crucial shouldn't cook itself running stock. I noticed that the weight of the OCZ modules is much greater than the weight of the Crucial modules. I don't think it's the chips but rather the heat spreader or something - the OCZ is MUCH heavier, wonder if that could be why the OCZ runs cooler...
  5. After 10 hours of HCI memtest at these settings: 250mhz (3-4-4-8 - see below) 1.7v cpc Auto tcl 3 trcd 4 trac 8 trp 4 trc Auto trfc Auto trrd Auto twr 3 twtr 2 trwt Auto tref 2592 (from the Crucial guy earlier in this thread) twcl Auto interleave Enabled I had errors on the memtest. Called Newegg and luckily for me they'll do a refund within 30 days - she gave me an RMA # and address to send them back to for refund. I am going to see what Black Friday sales are on for 2gb memory, may get some locally or order some OCZ from Newegg. I really wanted to like this memory but when it works great, passes all tests and then starts getting progressively worse to the point where it won't even run stock speeds that isn't what I expect from $300 memory...that isn't what I'd expect from $150 memory lol. Edit: On the exchange question - I asked about that and she said they couldn't do that - all they could do was refund and then I can reorder something else if I like. So if you've had them over whatever the cutoff is - 30 days maybe? - and want to exchange them, push for a refund... I prefer this way anyway since now I can research what I want rather than having to come up with what I wanted right then on the phone.
  6. After more testing, I'm now running at 3-4-4-8, 250mhz - that's bone stock on the memory. Fails to boot or random reboots at 3-4-4-8/250 @ 2.6v - have to use 2.7v. At 2.7v with stock settings, modules get damn near hot enough to burn you touching them while memtest is running. They get even hotter at 2.8 or 2.9 of course... Airflow was and still is great through this case - the modules almost have active cooling - the 120mm fan on top of the XP120 blows air right onto them and my ambient room temp is 29c or so - not at all hot in here and actually much cooler than when I started building this rig 3 weeks ago and it was 85f outside. At some point while messing around with memtest tonight I got another BSOD, stop 0x4e this time. Looking at the two dumps in WinDBG, they both strongly indicate jacked up memory - bits getting flipped. Suddenly not real happy with this memory.
  7. Now seems stable at these settings: fsb 260 cpc Auto tcl 3 trcd 4 trac 8 trp 4 trc Auto trfc Auto trrd Auto twr 3 twtr 2 trwt Auto tref 2592 twcl Auto Not real sure what is going on - I am going to run over night HCI memtest at least one night this week and overnight BIOS memtest with these settings. If it works and shows no further sign of problems, I'm happy with it. I expected to be doing some tweaking in the first month or so. If the tests this week pass and then I start having problems again in a few weeks, I'll be wondering if I shoulda gone with this memory. I am going to call and talk to Newegg tomorrow and see what they say since I am still within 30 days on these - I'd really rather not swap these modules if they work at stock speed/timings and the Crucial web site says the timing on these is 3-4-4-8 at 250 - I'm now running 3-4-4-8 at 260 which is pretty darn close to stock.
  8. DRAM Voltage: 2.70v CPU VID Control: 1.500v 260mhz 3-3-3-8 (CPU running 260 x 10 - so yes, it is OC'd - I spent a week finding max CPU, max memory, running tests - CPU is good up to near 2700 but with more voltage/heat than I am happy with.) CPC: Auto TCL: 3.0 Trcd: 03 Trac: 08 Trp: 03 Trc: 07 Trfc: Auto Trrd: 03 Twr: 03 Twtr: 02 Trwt: 03 Tref: Auto Twcl: Auto Interleave: Enabled This had passed 21+ hours of dual prime95, 7 or 8 hours of the HCI Design memtest, BIOS memtest, SuperPi, OCCT and maybe a few other tests I found. After the BSOD, I fired up HCI Design memtest and it quickly found errors - running 2 instances of it with affinity set via Task Manager checking 803mb of memory in each instance (the max it says it can check.) Dropped to 250 x 10 and ran memtest no problem. Changed back to 260 x 10 but changed settings thus: Trc: Auto Trfc: Auto Trrd: Auto Twr: Auto Twtr: Auto Trwt: Auto (pretty sure that's it - I changed a bunch of stuff to "Auto" but left 3-3-3-8 settings) and now it just ran 200% on HCI memtest dual instances. I am going to go back to my original non-auto settings and see if it fails. What bothers me about this is that tests which initially passed have now failed - the HCI Design memtest ran for hours 2 weeks ago, then it failed and now it runs again with a bunch of "Auto" settings. FWIW - I had just mounted a DVD-video ISO and played a few minutes of it, then closed the player when I got the BSOD. I also got a BSOD yesterday or day before after playing BF2 for a little bit and then leaving the game open - it had minmized and when I clicked the game on the task bar to go back into the game, it blue screened - I kind of figured it was some odd ball video driver thing and unfortunately had auto-reboot and didn't get a good memory dump on that one so I can't say if it was the same BSOD as the one today. But 2 BSOD in 2 days when I'm really not doing a hell of a lot other than playing games and watching a few minutes of a DVD is WAY unacceptable.
  9. Nooooooooooooo!!!!!! :sad: :sad: Just got a BSOD: Stop 0x0000008E params 0xC0000005, 0x805B0EC6, 0XB2D29AB0, 0X00000000 I got a full memory dump which I'll look at but initial research indicates stop 0x8e tends to be....MEMORY PROBLEMS! :sad: This is 3 week old Crucial Ballistix PC4000 2gb (2 x 1gb) kit from Newegg. I am going to run some memtests and call Newegg and see what my options are. One BSOD is one too many for me. I'm not one of those people that thinks Windows just crashes and it's normal - it's not.
  10. That stop is most likely either bad drivers or memory problems as he said. If you have a fairly fresh install of the OS and no oddball drivers - just the basic stuff, graphics driver and NVidia drivers and whatnot, then it's very likely memory problems. Could be some other hardware issue besides memory, but memory is easy enough to test. Another good memtest to try out is http://www.hcidesign.com/memtest/ - this one found memory problems for me in one pass that the BIOS memtest failed to find. I ran two instances - one per core - testing just less than half the memory per instance and manually set processor affinity.
  11. Mine is still chugging along - see my previous post in this thread for my settings - although based on this thread, I'm beating the . out of this memory over the weekend of 11/26 - 27 days from when I bought it. If it shows any sign of problems, I'll call Newegg on the 28th and see about swapping it for OCZ or something. I'm quite happy if it'll run at 260mhz - but on 11/26 it's getting tortured at 260mhz hehe...
  12. I have the model 395 multi-speed - think I got it at Home Depot. It came with a case and a bunch of bits. Get the one with the case for sure - keeping track of all those bits is way easier if they're all in one case with the Dremel. Get some extra cutting discs when you buy the tool - you'll chew through those cutting up cases if that is what you're going to do - and they're fairly cheap. The cheap cutting discs, for me anyway, work far better on case cutting than the diamond wheel thingy. Kinda sorry I got the silly diamond wheel but I guess if I need to Dremel a piece of steel rebar in half I might be able to do it with the diamond wheel lol... I had a Black & Decker rotary tool a few years ago - couldn't find parts for it, lost a part of the chuck or something and it became useless. Also it was FAR less powerful than the Dremel to start with. Get a real Dremel so you can get all the accessories and parts - it's kinda like the IPod of tools - tons of accessories for it specifically. Check out the tool section at Home Depot or Lowes - the stores by me have a whole aisle of Dremel stuff.
  13. Where did you hear this? I just went and read through the thread on Creative and didn't see any indication of it. If Creative tech support told you this, I might go see if I can find a new one - not the one I returned lol - at Best Buy.
  14. I've had this memory (and the entire system) two weeks and it's still looking good with these settings: DRAM Voltage: 2.70v CPU VID Control: 1.500v 260mhz 3-3-3-8 (CPU running 260 x 10) CPC: Auto TCL: 3.0 Trcd: 03 Trac: 08 Trp: 03 Trc: 07 Trfc: Auto Trrd: 03 Twr: 03 Twtr: 02 Trwt: 03 Tref: Auto Twcl: Auto Interleave: Enabled With these settings I've run 21+ hours of dual instances of Prime95, 7 hours of memtest, all the other stability tests I could find. No problems, no reboots, no errors of any kind. I did initially think 282 x 9.5 was stable but the HCI memtest found memory problems at 282mhz at 2.9v. I dropped to 260mhz and 2.7v and passed every test I've run since. I did notice at 2.9v, the memory got VERY hot. It gets kinda hot even at 2.7v but not as hot as 2.9v. I have great airflow through the case.
  15. I read up on removing the IHS and no way I'm doing it on mine - if I had access to liquid nitrogen cooling and was trying to set world records I'd do it, but the risk is too great for only a few % possible increase for me. With regard to your heat, what voltage you on now? I ask because your temps sound much like mine at 1.6v or more - I found that while I needed 1.6v for close to 2700mhz, 1.5v was fine for close to 2600mhz and it ran about 10c cooler. My temps are now 33c idle/45c load - ambient is about 23c. Is your ambient higher? Could be you can run stable at 2610 but it's the heat from the voltage causing problems now - just an idea. Good luck!
  16. I took mine back to Best Buy for now - make no mistake, I do *want* an X-Fi, just as soon as I read someplace they fixed the problem. From what I've read, the problem in NF4 mobos ranges from "no problem at all, works great" to "sometimes bluescreens" to "won't boot." I am sure I could have installed my X-Fi and *maybe* had good luck. For that matter had it started bluescreening, I know how to capture the dumps and do some analysis on them - though without source code to the NF4 drivers and Creative's drivers, I wouldn't have got too far. Maybe I could help Creative figure out what their problem is - and I *do* think it's their problem - their comments about a temp firmware "workaround" for the X-Fi cards doesn't make a lot of sense. And the NF4 chipset has been out for a hell of a lot longer than the X-Fi. I'll bet they're saying it's a mobo problem at least in part because they're not exactly sure what is wrong - but they know something they can do in firmware or a mobo vendor can do in BIOS fixes it. When you're not sure what is wrong, blame someone else - that is one of the basic tennents of support! Regardless, I couldn't be happier with how my brand new rig is working - and I'm just not gonna stick a sound card in that might bluescreen - even a little (a little bit of a bluescreen problem is like being a little bit pregnant).
  17. I've got 3 Hitachi T7K250 in RAID0 attached to SATA1-3 working just fine. I used the floppy that came with my mobo for installation and selected both required drivers. Did you select both during your install? When XP reboots, does it bluescreen or anything - how far into the boot of XP does it get? Do you see the desktop or just the blue progress bar prior to that or what? What media are you using to install XP? XP SP2? From where? Nothing slipstreamed into it right?
  18. "supported by" doesn't necessarily mean "no warranty if not used in" though. I'd assume it has some kind of warranty whether used in a Dell system or not. Just if you call Dell and want to talk to them about setting up a 4 drive RAID0 in your DFI/AMD system, they might not talk to you much about it. I'd have to ask them every 30 seconds why they don't sell AMD processors anyway and so I doubt we'd get anywhere.
  19. I'd guess hardware - maybe a memory issue. Just found this article on troubleshooting stop messages - good stuff. If it's memory, you might be able to find it with HCI's memtest. It found problems memtest in BIOS didn't for me... http://www.hcidesign.com/memtest/
  20. When did you purchase your Ballistix from Newegg and did it by chance ship from New Jersy? Just curious... I got mine 10/26/2005 - and my order shipped from CA except the memory - it came out of NJ. I've never ordered anything from Newegg and had it come from NJ, guess they got a warehouse up there too. I do hope mine doesn't drop dead! :confused:
  21. Great find!! If someone gets one of these, do tell us about the results! The one thing I'm not terribly happy with is my chipset temps and vid card sitting on top of the cooler.
  22. Hehe still at it huh? I did about the same as you, for over a week - I had mine setup on the kitchen table with laptop next to it to look stuff up. I didn't even place it into my office until I had decided what speed I was happy with... I had somewhat similar issues - I could run everything except the HCI memtest for hours upon hours, but that HCI memtest would fail running CPU @ 1.6v at around 2700mhz, 2.9v on the memory. I suspect there may be some stable point up around 2700mhz for me, but I decided to back off to 2600mhz and lower voltages (1.5v/2.7v) and sure enough, all tests including the HCI memtest passed. In your case, it sounds like prime95 is to you what the HCI memtest was to me. The guy raining on the parade. I'm sure you can find a stable solution close to where you are, but it may take lots more time. If it's going to drive you crazy or make you mad at your nice new system, maybe just back off 75-100mhz and see how it looks there? I mean I thought about the diff between 2500 and 2600 and realized, "hey, thats like 4% - what the hell do I care about 4% for if it's going to cost me another week!" I guess I'm just trying to offer encouragement here, no actual help... Good luck!
  23. How are you telling which CPU is holding you back - prime fails on one and not the other or ? In regard to the original topic, I read some info on "tunneling" someplace in the past week or so - maybe on here. Something about higher voltages causing electron tunneling, regardless of temps, and that being what can kill CPUs or memory. Google "electron tunneling overclock" for some interesting reading if you can't sleep. The way I look at it, almost anything should work at +/- 10% voltage - I may be wrong, but that's my simple minded thinking.
  24. You need to poke the OS into recognizing it needs a new HAL - you might try installing the AMD ACPI driver thingy as I know that that will make the OS go from single proc to multi proc - maybe it works the other way too, dunno... http://www.amd.com/us-en/assets/content_ty...ties/amdcpu.exe There should be a way to do what you need without having to reinstall - hopefully the amdcpu thing does the trick... Try as I might, I can't find the Microsoft info I swear exists on how to do this. Edit: Should mention, if the AMDCPU thing does the trick, you can remove it afterward - it just triggers a HAL refresh. From what I've read, I'm as sure as I can be without having done it myself that it will go from single->multi proc, so it stands to reason it should also go from multi->single.
  25. Changed stripe size from last post... 3 x 250gb Hitach SATA2 RAID0 16k stripe size - previous post was 64k (default) stripe size 4k cluster size SATA2 & spread spectrum enabled via Feature Tools XP SP2 + updates & drivers I booted and ran each benchmark 3 times per suggestion of someone in this thread. I've posted the 3rd run of each - the results were different on each run. In HDTach, burst rate ranged from 332mb/sec to 355mb/sec and average ranged from 145.4mb/sec to 150.3mb/sec. In ATTO the first and third runs were pretty similar and all the numbers in the middle run were lower (write only once went above 87k in the 2nd ATTO run - no clue why.) I notice with 16k stripe, the graph in HDTach is much more spikey - but the average comes out the about the same - around 145mb/sec - as 64k stripe size. Edit: I also would love to see the SCSI results from goob for comparison!
×
×
  • Create New...