Jump to content


  • Content Count

  • Joined

  • Last visited

About anthonys123

  • Rank
    New Member
  1. Thanks everyone for all the feedback! The crackling happens in all games, and after further checking, when EAX or hardware mixing is enabled, as Charlie22911 mentioned. What's annoying me to no end is that my bloody Asus A7N8X-Deluxe never had any problems like these - damned Asus boards. Though that board had nowhere near the Vdimm settings I need for my BH-5... :nod: Windows XP is configured as "ACPI Uniprocessor PC" - I'm worried about disabling ACPI because I'm hesitant to have to reinstall this system. At these mild overclocks, would ACPI be the problem? NEOAethyr - thanks for the mention of the fact that PCI slot 5 should be the one to use since that's not on the IDE controller's bus - I'll definitely try moving the card to that slot. In terms of South-bridge cooling, I have a 120-mm fan mounted on one of the backplane tabs, pointed at the 6800GT, so there should be a bit of air hitting the SB. This is in a Silverstone TJ-05 case with 5 fans, so airflow is pretty decent. Wow - good question about the type of mobo NEOAethyr - I just took a close look at it. I bought it new six months ago from Axiontech and it appears to definitely be a Rev. B board (it's labelled as such on the box and on the board). It also has a heat-sink on the SB, which I believe was a feature of Rev. B. BUT, as you mentioned, "Made in Taiwan" is whited-out!!! What does this mean?!?! :sad: - Anthony
  2. Hello All, One can run all the stability apps in the world (MemTest, S&M, Prime95) and think you have a stable system, but it doesn't mean diddly-squat until you get into an intense UT2004 frag session... I'm at my wit's end on this one - I thought my rig was entirely stable, I was only mildly overclocking the FSB to 216 MHz and my Mobile 2500 to 2496 MHz. Auto setting for AGP bus speed and North-bridge (i.e., 1.6 V). I have an Audigy 2 ZS and noticed that there are random crackling noises when I play UT2004 or Far Cry at virtually any FSB above 200 MHz. I've tried almost everything: - Down-clocked the CPU and played with various voltage settings. - I'm running OCZ BH-5 and have tried voltage settings at 3.0V and 3.1V, all settings with CPC disabled. - Tried North-bridge voltage settings of 1.7 and 1.8V - no effect. - Fixed the AGP bus speed @ 66 MHz, instead of the "Auto" setting in the BIOS. There are no glitches whatsoever @ 200 MHz FSB, but the glitches show up as early as 205 MHz. Does a LanParty NFII Rev B lock the PCI bus @ 33 MHz during overclocks? Should I try moving the sound card to a different slot? Is there the possibility that the Audigy is running at a higher speed than 33 MHz? I've relegated myself at this point to simply running @ 200 MHz FSB with the CPU @ 2.4 GHz. Any insight/help would be appreciated! - Anthony
  3. - What is "Disable Safe Mode" in CPU Test and Memory Settings? It's un-checked by default. Does checking these options make the tests more stressful? Does it disable temperature monitoring? - What is the "Variable pattern" setting in the Memory Setting? Does checking it make the memory test more stressful?
  4. Thanks NEOAethyr - yeah, if you could upload the 1.7.3 version, that would be great! Where is the location it will be stored at? I'm new to the forum, so I'm still learning my way around.
  5. medianOCer - I tried running the Windows version of S&M on one of my Win 2K Server rigs and the test never starts. The application starts, I can run the Wizard to set options appropriately or set them manually, but when I click on the "Start" button, the test never starts (0% CPU). S&M works fine on my Windows XP Pro rig - is there an incompatibility you're aware of with Windows 2000? - Anthony
  6. Thanks for the info regarding the Windows version of S&M - I had no idea how to run it in Windows and didn't realize that the executable could run either in a DOS or Windows environment. I will definitely try that tonight. I haven't run the "Fast" or "Quick" tests on the systems - I figured that "Normal" and the slower tests would stress the systems more? The Normal test needs something like 7-8 minutes to run and has proven useful for doing quick spot-checks of stability. The Slow and Long tests have been useful too and thank goodness all of my rigs pass these three tests. I agree - the UI leaves a bit to the imagination in terms of understanding. It appears to auto-sense the stick in slot 1 but will not auto-sense any other sticks. I've simply booted from the floppy, exited the "Volkov Commander" by hitting F10, and running S&M manually from the DOS prompt. When the app starts, I tab over to the right-hand menu and select which test type I want and hit Enter to start the test. I think in this mode I'm only testing the first stick, though I haven't figured out how to make it test both sticks in the same test. As an update, I disabled all overclocking/over-volting on one of my rigs this morning (Sempron 2500+, 166MHz memory bus, 1.6V core, 2.6V DIMM) and ran "Night" mode. Low and behold I get home tonight and there are even MORE errors than when it was overclocked! - Anthony
  7. Hi Everyone, S&M is turning into a blessing and curse for me. When I run the S&M "Night" test (DOS floppy version) on all of my rigs that I thought were stable, it inevitably results in literally millions of errors by test's end. S&M "Normal", "Long", and "Slow" tests do not reveal any errors, but I haven't tested with the "Fast" and "Short" tests - my thoughts are that the Normal and longer-term tests are the most stressful ones. My rigs test out successfully with the other apps I've thrown at them: - OCT Stability and 12-14 hour Torture test - OCT running concurrently with Norton AntiVirus scan and Microsoft AntiSpyware scans - Prime95 small, medium, large FFT -> all run for at least 17 hours - Prime95 running concurrently with Norton AntiVirus scan and Microsoft AntiSpyware scans - OCT and Prime95 running concurrently -> 12-15 hours - MemTest86 Test #5 -> 17 hours - MemTest86 Test #8 -> 17 hours - MemTest86 All Tests -> 17 hours And yet, the S&M Night test reveals errors - what are your experiences with this particular test? I've resigned myself to stopping all overclocking/over-volting on one of the systems and running the test just to make sure no errors surface, but could there be a problem (dare I say bug?) with S&M itself? I'm also going to try the test on several plain-jane Dell and HP systems to see if they show any stability. - Anthony
  8. Thanks everyone for the replies - much appreciated! Clay - good points about the BH-5 sticks. I think I've been lucky, especially after my nightmarish experience with them and my old Asus A7N8X Deluxe. I'm pumping 3.12V into them with 2-2-2-11 timings with a 120mm fan blowing directly on them and the NB. I've heard that test #5 of MemTest86 is a particularly stressful one. My system did something like 700 iterations over 19 hours (at 230 FSB) with no errors - so I was pretty psyched about that. I'll be running the basic and extended tests later this week for 24-hour periods each - I'm hoping success at these tests shows a decent memory subsystem. Are there other MemTest86 tests I should focus on and run for extended periods? I'll also make sure I aim a fan at the SB too. NEOAethyr - many thanks for your input. You mentioned "s&m" - what utility is that? Is it Windows-based? I'm using MemTest86 and Prime95 for my system qualification - I didn't think of using SuperPi - I'll add that also to the test collection. Excellent point too about hammering the FPU - will Prime95 and SuperPi be good for that? I assume that you mean just running these day-in and day-out for a week or so? How long should the "break-in" be? I'll keep everyone posted!
  9. Hi Everyone, I'm testing my system with LanParty NFII Rev. B and am currently running it at 230 MHz FSB. I've noticed that if I run Prime95 and do some surfing (surprisingly the system is quite usable even with Prime95 running ), sometimes I lose the onboard NVidia network connection (requiring a reboot to get everything working again), though the RealTek Gigabit connection works fine. I'm chalking this up to the 230 FSB and maybe running a bit too fast for the network hardware? Does the NVidia network hardware reside on the NorthBridge or SouthBridge? Should I just switch to the RealTek port and keep clocking the be-jeezus out of the FSB? A more general question - when clocking this high, does increasing the NorthBridge voltage help at all? I've read that increasing the voltage actually decreases reliability in some cases. As an FYI, I'm running a MicroCool active cooling heatsink/fan on the NB with Arctic Ceramique. - Anthony
  10. Thanks King of Nothing and Clay for the quick replies! King Of Nothing - good point about the use of a multi-meter - I should try that. I did check the BIOS readings for lower voltage settings and they're pretty accurate, so there is something weird going on with the "3.2V" and "3.3V" settings in terms of the sensor readings. Clay - I've seen your other threads pertaining to the utt-bh5 (thanks for the model name clarification) sticks. I too had a lot of issues using these sticks with my original Asus A7N8X-Deluxe MB and eventually gave up with that board. I found my LanParty new and on sale several months ago and decided to give it a whirl before I resign and relegate these sticks for my future A64 system. I've been receiving errors with the Prime95 "Blend" torture test (the other tests run fine) after 8-9 hours of running. I may have found a sweet-spot, though, at 227MHz FSB, 2-2-2-11, x11 for the CPU (2497MHz for the CPU). I saw a posting in another thread showing someone successful with these particular OCZ sticks at 230MHz with 3.1V (I'm pushing ~ 3.12V now), and that any higher FSB requires 3.2V and beyond. - Anthony
  11. Hello Everyone, I recently installed a LanParty NFII Rev. B and am using two OCZ PC-3200 Winbond BH-5 512MB sticks (OCZ4001024ELDCGE-K) that I purchased Summer 2005. I've found that the board is not setting Vdimm higher than 3.12V regardless if the value set in the BIOS is "3.2V" or "3.3V". In fact, what's really weird is that the actual value falls to 3.0V on the "3.2V" setting and rises back to 3.1 for the "3.3V" setting (same actual value as the BIOS "3.1V" setting). Agghh. I'm using a Fortron 550-W server-grade PSU, and have also tried a 400-W PSU with the same results. I don't think the PSU is the culprit, and I definitely connected the 4-pin ATX 12V power plug. My understanding is that the Vdimm is sourced off the 5V line? I'm seeing between 4.96-4.98V there in the BIOS monitor. Could the BH-5 sticks themselves be somehow restricting the Vdimm that can be set? Thanks in advance! - Anthony
  • Create New...