Jump to content

naddie

Members
  • Content count

    174
  • Joined

  • Last visited

Posts posted by naddie


  1. I feel my current build (in my sig) still feels quick. It is used mostly playing BF2142 and lots of video transcoding from divx/xvid and wmv to wmv - wmv to wmv transcoding because of resizing video for my mobile media center.

     

    I am wondering how much faster is moving from my current setup to an Opty 165? The minimum OCs I am seeing the 165s are getting are around 2.7-2.8GHz. If I were to buy one from NewEgg now, will I get one that can do 3GHz+?

     

    Will the performance be noticable from a 2.5GHz dual core (512kb cache) to a 2.8GHz (at minimum) with 1MB cache? And by how much?

     

    I haven't seen any direct comparisons of a 2.5GHz x2 compared to a 2.8-3.0GHz DC Opty.

     

    And lastly, how does a 3.0GHz DC Opty compare to Intel's latest C2Ds? Specifically those also at around 3.0GHz (in other words, clock for clock). I know they can go as high as 3.6GHz (most report 3.2-3.4GHz OCs), but I'm interested in 3.0GHz clock-for-clock comparo between AMD and Intel.

     

    Thanks in advance. And yes, I know I've been away for a long time... need to get back up to speed with the "new stuff". :)


  2. My 9 month old Evercool EC-VE-RC is now making noises. Sounds like it's about to fail. It is clean, and I made sure of it, but it still makes noise like it's loose or unbalanced.

     

    Not sure if I should replace it with another Evercool EC-VE-RC or go with the Vantec Iceberg CEBERQ CCB-A1C. The only thing about that is that it is only a 2-wire fan, so no RPM sensor. I can replace it with the stock DFI I still have, but I heard that will fail after a couple months.

     

    This isn't just a simple replacement - I will have to remove the motherboard from my case, which invovles removing almost EVERYTHING just to replace this garsh darn HSF. I replaced the DFI HSF when I first bought the mobo because of good info here. Unfortunately, my Evercool failed me.

     

    Anyone have such a failure? If not, how long have you had it? If it's just me, then I will buy the Evercool again - maybe I just got a bad one.


  3. I tried with stock timings and settings first before messing with anything. Also if what you say is true, then I should still be able to use the yellow slot (the one furthest away from the CPU) on its own, but that caused stability issues without changing anything else onthe BIOS. It is okay on the orange slot (again, the one furthest aay from the CPU).

     

    And you are wrong about the "overclocked" 7900s because stock-clocked 7900GTXs were also affected. Ask me how I know. ;)

     

    MODS: Can you please move this back to a non-cooling issue troubleshooting thread-area? And change the title to "Memory slot sensitive?" Thanks!

     

     

    EDIT: I'll elaborate on the 7900 fiasco, as I was smack in the middle of it. It was frustrating to read on the "mainstream tech sites" the nVidia media spin that it was just OCed 7900 series, as tech support forums for the stock-clocked 7900s were also being poured in with issues. Exact same issues, in fact - artifacting. None of us really locked up. Just artifacts and a very slow lock-up when getting back to the desktop (desktop will filcker in and out, eventually your inputs will be ignored, but if you are fast enough, you might be able to shutdown your PC properly using your power button if it is set up in your BIOS/WinXP to shut down with it).

     

    I personally went through 4 EVGA 7900GTX EGS (stock ref cards). All of the product numbers ended in AX. The new product number ended in AR, and are now called the "reloaded" cards. They are redesignd with Infineon memory chips instead of Samsung. We found out that manufacturers were pushing the Samsungs a little too hard with voltages (they weren't rated at 2.0v I believe was what they were using). The Infineon were rated that high, and were used instead.

     

    Now, EVGA did all the troubleshooting themselves (love that company). Not sure if nVidia or any other companies have recognized this fix.

     

    Sure enough, months later, I am still very hapilly playing my games without any artifacts. My troubleshooting proved that it was memory-slot related, and not the card.

     

    Yes - Deepfreeze worked over 24 hrs. :) No artifacts, no lockups, no perf issues.


  4. It's not an issue with anything actually. Single channel memory goes in the orange slot furthest from the CPU, and dual channel goes in both orange. It's not a problem, just how it is. ;)

     

    Ah, last piece of the puzzle...

     

    Single slot memory (either stick) works great! gamed for hours and hours without an issue.

     

    It is NOT the memory. Troubleshooted down to either the motherboard (memory slot) or the CPU (memory controller?).

     

    Which is more likely?


  5. Okay, I think it may be the memory slots.

     

    Both memory boots up the PC and tests just fine each on their own.

     

    The slots near the CPU (a yellow and orange) doesn't work on their own (if you only have a single memory stick). Only the Yellow and Orange furthest away fromt he CPU runs single channel memory (1 stick only). Is that suppose to be?

     

    Memory in the Yellow slot (furthest away from the CPU) boots the PC up, but keeps restarting.

     

    Memory in the Orange slot (furthest away from the CPU) boots up just fine into windows (have yet to start WoW).

     

    This is begining to sound like a memory slot issue (and in turn, an issue with the board).

     

    Can any one chime in with more info on this?


  6. First of all, I can't Step-Up my card because it was already stepped up from a 7800GT. Besides, not everyone have an EVGA card. :) The 7900 series is pretty good, actually - especially since they started using Infinion memory chips (Samsung memory was the culprit in the original fiasco).

     

    Anyways, the updated/cleaned drivers didn't help. Reinstalled WIndowsXP and used the latest and greatest drivers - still no go. Instead of hard locking though, WinXP restarts uruptly.

     

    It's really getting under my skin!

     

    Currently running memtest86 AGAIN to make sure memory hasn't gone bad. Though it locked up even before I upgraded to an XFI, I will see if moving my XFI to a different slot would help (logically it shouldn't, but you'll never know).

     

    If that doesn't work, I will try moving my memory from the recommended orange slots to the yellow ones.

     

    Next step after that would be using just one memory stick in single memory chan and see which one is "bad" if any.

     

    Lastly, I would consider the mobo. Then my last resort would be the CPU.

     

    PS: AMD Athlon x2 drivers was installed - so that wasn't the culprit.


  7. Well, no update yet. I just finished uninstalling all nVidia-realted drivers and re-installing them. i found that the nVidia updated their video drivers (91.31 was my old one, now they are up to 91.47).

     

    I uninstalled all of nvid's chipset drivers, and resintalled it all except for the sound driver (since I have an XFI).

     

    Also updated X-Fi drivers. They seem to require the old driver installed before it can be updated.

     

    I fired up WoW again, so we'll see.


  8. This has always been my GFX card. The "new" thing that changed was WoW being installed and played (I'm new to WoW, but old enough to now have a lvl 32 char). I never had any stability probs. in fact, as I said, it only hard locks on WoW that I know of.

     

    It only hard locked on me once while playing either FEAR or Q4 (dont reember which one), but as I don't spend the amount of time playing FPSs (cuz they do get boring after a short while) compared to WoW, that may be the reason why they don't lock as often or ever.

     

    WoW, on the other hand, is where I am experiencing the most issue. Being an MMO, it is very frustrating to have it lock on you.

     

    So that should answer the questions that OldGuy had.

     

    I just tried a fan today blowing on the mobo, and still had locks. So you guys are right about it not being the chipset's temp.

     

    I will try a reinstal of WnXP and see if that helps. I'll report back.


  9. dont forget wow is... wow when it comes to bugs :)

    also, maybe its on a different hdd or something? bad hdd (just a really small guess :|)

     

    WoW works well on my laptop, though a bit slow.

     

    I'll reinstall Windows again. :/ Any suggestions regarding which versions of drivers to use, or just use the latest? I am espcially concerned with the SATA drivers, since the F6 floppy drivers must be old by now.


  10. All stock speeds, stock voltages. Crashes under WoW though, but not while normal computing. Doesnt seem to crash at FPS games, but then again, I don't play FPS very long, lol.

     

    dual-Prime95, memtest86, and 3DMark06,05, and 03 stable. Overnight and then some (into the day), so around 16 hours of burnin for each test. I also Primed and 3DMarked at the same time to see if that would recreate the issue, but no.

     

    I will try to reinstall WinXP, but it's a fresh install to begin with. Maybe with different drivers.


  11. Well, the combo of the two seems to conflict:

     

    EVGA+nbridge.jpg (hope the img is small enough).

     

    As you can see, the HSF of the GTX is blocking more than half of the northbridge HSF!

     

    The stock one was replaced with the VCF copper HSF as suggested by a member (or two) here in DFI. It certainly cooled better, but now that I have GTX (and a new revised card that fixed all the other issues that pertained to the 7900 series fiasco), I am getting hard locks instead of artifacts (all stock speeds) - especially when playing World of Warcraft.

     

    Any suggestions on how to remedy the situation? Not sure if there is an aftermarket HSF for the GTX.

     

    EDIT: Found out that it was very senstive to where I put my memory on the slot (but I can only use one slot, making for single chan use only). Still looking for a solution (RMA?). Read below for more details. Thanks for reading, btw. :)


  12. So the math is...

     

    WITH THE STOCK 266FSB THE RAM SPEEDS ARE AS FOLLOWS FOR DIVIDERS:

    1:1 - DDR533 = 1(266 * 2)/1

    16:15 - DDR566 = 16(266 * 2) /15

    9:8 - DDR600 = 9(266 * 2) /8

    6:5 - DDR633 = 6(266 * 2) /5

    5:4 - DDR666 = 5(266 * 2) /4

    4:3 - DDR700 = 4(266 * 2) /3

    3:2 - DDR800 = 3(266 * 2) /2

     

    SO With the FSB of 445 you'd get the following RAM speeds at these dividers:

     

    3:2 - DDR1335 = 3(445 * 2) /2

    4:3 - DDR1187 = 4(445 * 2) /3

    5:4 - DDR1113 = 5(445 * 2) /4

    6:5 - DDR1068 = 6(445 * 2) /5

    9:8 - DDR1001 = 9(445 * 2) /8

    16:15 - DDR949 = 16(445 * 2) /15

    1:1 - DDR 890 = (445 * 2) /1

     

    Excellent. Also, I was afraid that there weren't that many dividers. This is very uplifting news.

     

    Also, is a FSB of 445 MHz even possible with the current i975 chipset? I've read easy OCs of 400 MHz. But what about 445 MHz? Or even more? Anyone figured out the ceiling with a low-multi Conroe? (E6600 and below? 9x and below?)


  13. What do these ratio refer to?

     

    The FSB of Conroe platforms are now at 266, not the 200 of P4s, right?

     

    Currently P4s are using DDR2-800, which is a ratio of 1:2, which is (FSB*2)*2 ?

     

    So with Conroes, is it the same formula?

     

    I took a look at how I would OC a E6600. If it is true that 4GHz is possible, it looks like my FSB would be 445 Mhz (445*9 = 4005 MHz). If that is true, how would I work out the memory?


  14. As with any new platform, there is a new learning curve to get over. It took me some time to learn AMD's Athlon 64 no-FSB/HTT/bus nuiences.

     

    Now that Core 2 Duo is on the scene as the best enthusiest CPU "eva", is there any tutorials or write-ups on how to OC this bad boy? I tried my best to understand the memory dividers and how DDR2 memory works in terms of how the memory speed is related to Intel's FSB (and how this "quad" multiplier applies to the whole schema).

     

    Can someone either break it down or point to a place where they do just that?

     

    Also do memory dividers affect performance on the Intel platform? Or is it a non-issue as with the AMD platform? If dividers doesn't matter, does that mean overall CPU/FSB/memory speed is the determining factor for "teh win"? How does tight latencies at DDR2-800 compare to loose latencies at DDR2-1067 and beyond?

     

    Sorry so many Qs. Just that going over to the Intel side just isn't confusing enough, I now have to contend with DDR2 memory (higher latencies, but faster memory speeds).


  15. In all seriousness, have anyone ever experienced this, too? Ever since I had my first AMD rig (Athlon XP 2500+ OCed to 2.2 GHz), any and all Intel machines (even the P4 3.0c I replaced my AMD with) just seems to be less "snappy" in winxp. This is even more noticable during disk activities, including burning CDs/DVDs.

     

    I had a P3-1 GHz home server and just couldn't stand it anymore. I could barely navigate to do any chores on it (DL patches, move or copy files) while it is up and running (and there are only a few computers that uses it - mostly my Media Center).

     

    When I finally retired my Athlon XP machine so I can use it as a server, it was a world of difference.

     

    Now, don't tell me that it was because it was a 1 GHZ vs 2 GHz difference because it also happens with my P4 3.0c.

     

    For that reason alone, I have shyed away from Intel for a long time.

     

    I will, of course, test out the Conroe 2 Duo before jumping in.

     

    I am not a fanboy of either company. My first gaming rig was a P2-450 during the VooDoo2 era (and that CPU was the fastest in its day - it cost me $900 for just the CPU!). I still liked that platform, as with the same mobo (Asus P2B - gotta love the 440BX chipset!), I was able to upgrade it to a Celeron 900 (OCed to 1 GHz and beyond).

     

    But it was here I started to noticed the disk access sluggishness after another upgrade to an Athlon XP 2500+.

     

    It has to be a chipset issue, since I once had a Comapq laptop that uses the ATI chipset for a AMD Athlon XP mobile that exhibited the problem even worse.

     

    Bah, Im ranting cuz its late and I lost all sense of putting words together, lol.


  16. how do you check whether it is CHS or LBA when its selected as auto?

     

    Also, my bios has the option of selecting CHS and LBA, so shoudl I just select LBA for my IDE harddrive instead of auto? Okay to just change it, won't mess up any data on harddrive? running 6/23 bios btw.

     

    Compare the settings from AUTO with CHS and LBA. If it the settings matches CHS, then it is in CHS mode. If it matches LBA, it's in LBA mode.

     

    As for switching it, it's not that simple - if you switch from CHS to LBA or vice versa, you will need to reformat and reinstall your OS.

×