Jump to content

Wildstaroct

Members
  • Content Count

    38
  • Joined

  • Last visited

Posts posted by Wildstaroct


  1. Good thread, was looking for an excuse to try the NV drivers.

     

    Based on a couple of tests (boot time, HD Tach), here's my results (switching from MSFT drivers to NV):

     

    * Boot time decreased 7.5% to 80 seconds (from 86)

    * CPU utilization increased 57% to 3.66% (from 2.33)

    * All other HD Tach stats showed no difference

     

    I tested both boot time and HD Tach 3 times and averaged them. So not a big sample by any stretch.

     

    Despite the CPU utilization increase (which I find suspect with such a small sample), I'll probably stick with the NV drivers unless a problem starts cropping up.

     

    My reasoning:

     

    * System feels a bit snappier (totally subjective, I know)

    * I like faster boots (even if it is only 6 seconds)

    * I can turn command queuing off on my Raptor 150. I've seen some results suggesting that turning it off in a non-server environment (me) results in increased performance and less potential problems with the NV drivers. The MSFT drivers don't give an option to turn NCQ off.

     

    That's it, cheers.


  2. I'm getting some strange readings w/ the new version of Speedfan, v4.29.

     

    In this release, there is a new sensor called AMD K8. The Speedfan change log reads "added full support for AMD K8 (Sempron, Opteron, Athlon 64) internal temperature sensor."

     

    This new sensor is reporting load CPU temps 12C higher than the mobo sensor. I've already got the DFI Expert temp offset to +10, so if this new sensor is accurate, it would mean the mobo sensor is off by a whopping 22C. And that I've really been cooking my CPU :(

     

    Any idea which sensor(s) I should believe?


  3. No noticeable change in Obvilion, I tried it in a couple of CPU-constrained areas. No bad side effects tho, tried also in HL2. BTW, I also installed on top of MS hotfix.

     

    Edit: Correction: HL2 now seems to fly, much better w/ the fix.


  4. haha, what is "it" though? I dont know what it looks like.... :(

     

    If you have an extra fan lying around, mount it to blow on PWN like so. If you've got an extra 3-pin fan header that is controllable by BIOS, even better since you can regulate fan speed. Mine goes about 1000 rpm which isn't even audible. And it reduced PWM temps by 10C+.


  5. Speedfan works fine for me, though I believe w/ the switch you lose some functionality...still has voltage and temp monitoring which is goodness, all I really need. Change your shortcut to this to get it working on the Expert:

     

    "C:Program FilesSpeedFanspeedfan.exe" /NOSMBSCAN


  6. Since moving from my Abit IC7 / P4 3.0 Northy to my new DFI Expert / Opty 170, I wasn’t really surprised about how inaccurate s/w temp readings are for CPUs. There have been a couple of threads on this board re: how the Expert underestimates temp, whereas it is common knowledge that the IC7 overestimates temp (reference http://www.bleedinedge.com/reviews/abit_as...s_temps_02.html).

     

    While I wasn’t as diligent as the Bleeding Edge folks in testing (e.g., embedding thermal probes in heatsinks), I believe I have an accurate estimate on how much the Expert underestimates CPU temp.

     

    And by temp, I mean load temp. Load temps apply to everything below.

     

    The answer? Roughly 12C.

     

    The ironic thing is that the IC7 overestimates roughly equal to how much the Expert underestimates: 12C.

     

    How did I calculate this? By keeping variables constant between systems:

     

    • Ambient temp (19C)

    • Software monitoring tool (Speedfan)

    • Case temp (28C)

    • Koolance w/c, same block, same thermal probe location under the block…this is what kicked me off on this effort, the major constant.

     

    Both systems registered 29C at load in the Koolance display, but Speedfan registered IC7 at 50C and Expert at 28C. All other factors constant, if we know that IC7 overestimates by an average of 12C, then we can reasonably conclude that Expert underestimates by 12C.

     

    BTW, Expert bios used for testing is 2005/12/07.

     

    Conclusion: Until more rigorous testing is conducted, or a bios fix is provided (or even possible), Expert users w/ an Opty (170) should add 12C to their load temp to gain a more accurate view of real CPU temp.

     

    WildstarOCT


  7. Hi.

     

    I've just got my hands on a 36GB Raptor to be used for Windows/Apps/CSS. I remember seeing lots of people who had CSS running off of their Raptor saying that they were always first on the server and that the Windows bootup is quicker and those kinds of statements.

     

    Since installing it I've seen no difference at all. I ran the File System Benchmark test in SiSoftSandra and also HD Tach and I've included links below to the screen shots.

     

    http://ap0ll0uk.pwp.blueyonder.co.uk/images/hd.jpg

     

    http://ap0ll0uk.pwp.blueyonder.co.uk/images/hdtach.jpg

     

    My drive is listed first (labelled as Current Drive) and the exact same drive is listed underneath which is a lot faster than mine and I have no idea why this is.

     

    I have all the settings in the Bios which refer to the drive set to Auto and the drive itself is connected to Sata 3.

     

    Does anyone have any suggestions?

     

    Your Hdtach results are same as mine, I'm about 105.5. Are you using the Nvidia IDE drivers or Microsoft's?


  8. When installing v6.70, there are 4 options:

     

    Network

    SMBus

    Storage

    Audio

     

    Since I have an Expert w/ Marvell lan and Realtek audio, I only selected SMBus and Storage, then got the latest audio and lan drivers from the source. I didn't install the Nvidia IDE driver because I've heard some people have had issues with it.

     

    Is this right? Is there any benefit to installing Nvidia network and audio?


  9. then I realized the 3 LED's on the back of the OCZ PS were yellow. I adjusted the 3 dials above the PS led's until they were all green & the PC booted great.

     

    Lenny, you should check out your PSU. Yellow isn't good. Green is of course, but there's leeway even with green. Either get a multimeter and test directly or ensure in BIOS that your rails are close to spec. I've done both...my BIOS reads 3.36, 5.12, and 12.35. Multimeter readings are closer to spec. If you don't have a multimeter, boot into BIOS and sloooowwwllly adjust your rails until they read a tad above spec (3.3, 5.0, 12.0).

     

    BTW, can you pls make your sig smaller? It makes me feel all tripped out.


  10. I have read about this problem before and experienced it with Speedfan. I assume like Speedfan, MBM likes to poll the SMBus. This has been known to immediately crash systems built on Expert, not sure why. I fixed my Speedfan by entering the /NOSMBSCAN switch on the app command line. Check to see if there is a similar switch for MBM. You may lose some functionality (I did w/ Speedfan), but I still get voltages and temps. Hope this helps.

     

    Edit: Found it right here! http://www.dfi-street.com/forum/showthread.php?t=34110


  11. Completed my first AMD system build this week and I'm impressed to say the least, even at stock speeds. Happy about my investment.

     

    However I'm having issues -- and there are a few posts on the web that ask the question but don't have the answers yet -- w/ 3D performance and my Redline PC4000 2x1GB.

     

    I'm running the latest beta BIOS 12/7/05 on my Expert and have loosened timings, increased volts to 2.9, etc. I'm several hours primex2 stable at 265, but I crash immediately in 3D (tested w/ nature 3dm01, rthdribl). Have to dial back to 255 to get 3d stable.

     

    So I'm looking for the magic bullet...I've tested different settings/voltages for 2 days and can't get 3D stable at 265, which appears to be the sweet spot for my CPU. Thanks in advance for help.

×
×
  • Create New...