Jump to content

Erekosse

Members
  • Content Count

    66
  • Joined

  • Last visited

About Erekosse

  • Rank
    Member
  1. I'm running XP Pro-64. I don't seem to have any problems with 3DMark05. I do get errors when trying to run Aquamark. I also found that OCCT indicates driver errors when loading. It appears to run okay after that, but an error message at the outset always leave that unsettled feeling in your mind... David
  2. I'm about the same. I'm trying to loosen my RAM timings to 2.5-2-3-5 from 2-2-2-5 to see if I can even stabilize at 235x11. (Dual primes running on the system below as I type from my kids' machine.) 235x11 was about max for the CPU with stable dual primes with RAM values set very loose. When I tightened from the CPU testing Bios setting in the OC Guide Sticky, I lost the dual prime stability at that setting. With the 2-2-2-5 settings, the second core errors at about 5-6 hours into prime. The first core seems to be rock solid stable - single prime for 8 hours at 240x11, but I had to drop to 235x11 before I got both cores at least 8 hours stable. I do have a baseline working OC at 233x11 with RAM at 1:1 at 2-2-2-5 that I'm using while not trying to tweak further. David
  3. I'll add my .02 for going straight to the bios update. That was the advice I got from RGone when I posed the question of compatibility of my mobo and the X2 processor. My first boot of the system was with a floppy containing the latest official bios. I'm pretty sure that all I had connected at that point was the power, the RAM, the video card and a floppy drive - no hard drives, no optical drives, no sound card. I next connected the optical drives and used Memtest overnight on the RAM. It was a few days later that I found the time to put the rest of it together and install the hard drives and the OS... David
  4. Onboard sound on the SLI-DR actually got a pretty decent review from Anandtech, but I'd still go with the sound card. Unless you've got a hardware audio chip (some of MSI's boards have a Creative audio chip on the MOBO), the onboard sound will use more MOBO resources to generally achieve lower quality... David
  5. Don't know if anyone has posted this yet, but looks like these sticks have gone on special again at newegg. http://www.newegg.com/Product/Product.asp?Item=20-227-211 ($123.95 after $15 rebate) I also saw the OCZ Titanium 2GB (2 x 1GB) 184-Pin DDR SDRAM Dual Channel Kit System Memory on special http://www.newegg.com/Product/Product.asp?Item=20-227-056 ($274.93 after $35.00 Mail-In Rebate) Any thoughts on the performance of the Titanium sticks? David
  6. I'm pretty sure I've seen that procedure on a forum suggesting it for burning-in BH-5 based memory... I'd be careful of the suggested voltage. I'm guessing that the level indicated in that procedure would void most memory warranties... I know the warranty on the OCZ Gold PC3200 I have is good to 3.0V (+/- a small percent variance). Of course, I think I've seen a variety of comments from AG about this particular RAM, and that he typically runs it at 3.2V; although I probably would double check that before I did it... David
  7. I flashed the bios at first boot to the latest official with the X2 seated without a problem. I've been fine so far on that bios. Other folks seem to be using the 7.04 bta from the BIOS factory board in the Overclocking section. It's up to you and your comfort level. I also read the disclaimers associated with the beta and/or unofficial bioses before flashing with them. I am quite happy that it was unlike the MSI P4N I built for someone with an 830 Smithfield. I had to strip a 775 socket P4 chip from another machine to flash the bios on that board before I could do anything. I was luck I had a machine from which I could borrow an older socket 775 CPU... David
  8. I used the approach suggested a few posts up. Have 2 SuperPI directories and execute from both. Before starting calculation, use task manager to bind one to CPU0 and the other to CPU1. An update on OCCT and XP64 - I ran OCCT at stock (got the driver error), and stability test ran for full time period. So, I'm guessing that it may work but no guarantees. I'm also off to dual prime95 testing. I tweaked Vcore to 1.325 + 123% (1.56-7 actual in MBM5) and was able to get OCCT to run to completion at 242x11 with good temperatures. I ran it again at 243x11 to see if the Vcore tweak will allow me to go a little higher but hit CPU instability about 25 minutes into the test :sad: . David
  9. I tried this and got a stable dual SuperPI at 243x11 and 1.3+123% special. I'm guessing that the instances competed for resources since both instances took just under an hour each. Of course, I had all the RAM values scaled back while CPU testing. Haven't had time to try this yet, but I'll try to do so tonight after the kids have been put to bed and report back. Anyone know if OCCT is accurate for stability testing in XP64 (despite the driver error at load)? David
  10. I am using an Antec TP II 550 in the configuration in the signature below. It's been rock solid since I built the system in July... David
  11. Thanks for the thoughts on the dual SuperPI. I'll give that a shot. I also think that I'll reset to stock and run OCCT to see if I get a pass on the 30-min stability test. If not, I have to assume that OCCT is not a good test program in the XP64 environment. Of course, it could also be an XP64 problem...LOL I've also been trying different combinations of CPU VID and VID Special without much success to stabilize in the low 240's. I've kept the calculated Vcore total below 1.6v (and in practice from MBM5 Vcore varied from 1.52-1.57). My temperatures for OCCT have been under 50C. Any thoughts on the safety zone on Vcore for these chips under air cooling? David
  12. I'll be interested to hear this as well. I'm reading it as actual value determined through monitoring, approximately base times percentage multiplier. I am trying to zero in on my max OC for my 4400 at the moment (on the slow train averaging about 1-2 tests a night). Memory timings at the moment are at 2.5-3-3-7 @ 2.7V not at the ones indicated below; I wanted to loosen things up during CPU testing. Other setting are as specified in the Overclocking Guide sticky. I was using SuperPI with stock voltage until I started hitting errors at around 250MHz x 11. I then bumped voltage up to 1.3 and +123% which still led to errors. I also tried 1.4 and +113% which also had errors. Both cases, the CPU hit 51C at its highest temp. I then scaled back to 244Mhz x 11 with no errors at 1.4 and +113%. I'm wondering if I should be running two simultaneous instances of SuperPI, and if doing so will cause execution of one instance on each core. I'm guessing that SuperPI is not programmed to use both cores simultaneously so likely is only executing on a single core. I hope it was running on the core with the lower OC potential; otherwise, I may have to spend quite a bit of time with dual instances of prime95 to get to a dual core stable OC. In any case, I ran OCCT at the 244Mhz x 11. OCCT hit a driver issue running under XP Pro 64-bit, which makes me wonder (only a little ) about its accuracy on testing stability under this OS. Does anyone know if there is a 64-bit version of this software available? Anyway, OCCT indicated instability at about 10 minutes into the 30 minute stress test. I'm wondering if I should bump the voltage base or multiplier at this point to see if I can take it higher or reach stability at the current settings. What are your views on the max Vcore for these 4400's? David
  13. I just experienced this same issue. My three temperature reading went to -128 in both the bios and with MBM. This occurred after I ran MBM and SpeedFan simultaneously, so I'm guessing that soundx98 knew whereof he spoke a few posts up. The scary part of the situation was that with the readings at -128 the CPU fan turned off and the CPU temperature reading from the probe I have wedged into the heatsink near to the base shot up from low thirties to around 50C. I shut down rather quickly. The shutdown, however, was not entirely successful. The system hung after the Windows has shutdown with a black screen but activity light on my DVD-ROM drive and power to the system - temperature sensor was still displaying and blue front panel LED on the P160 were still on. I tried the power button on the front panel with no success. I also tried the MOBO power button with no success either. I ultimately powered down by switching off the power supply. I thankfully found this thread after jumping onto another machine. I've rebooted the machine and the problem seems to have cleared itself. I have to say though that seeing those temperature readings was not a fun experience, particularly when I saw that it meant the CPU fan was a dead stop with the temperature actually rising... Hope this helps someone else that bumps into this issue. David
  14. I'll second that. It's been running nicely on my digital video encoding, but I have not tried much in the way of games. I've got a few older devices that are still used by other systems in the house that I do not have (and likely will never have) 64-bit drivers... David
  15. Recommend that you run a search in all forums on post by Fernando with nLite in the content to integrate the RAID drivers into an XP Pro (64-bit) install CD. I spent several unproductive hours trying different F6 floppies during the boot process with no luck. Once I got the the drivers integrated, no more problem. This was a month or so ago, so maybe the floppies have been "fixed". Hope this helps... David
×
×
  • Create New...