Jump to content

dobbs

Members
  • Content count

    57
  • Joined

  • Last visited

About dobbs

  • Rank
    Member
  1. Well, it's not this particular drive. I checked another one of these WD drives on my work machines, and I get the same crappy performance. It's only bursting at 79 MB/s, a shade over ATA-66 speeds. Everything that I've read/seen on the web indicates that this drive should perform at least 133 MB/s speeds. I tried putting the jumper on to disable spread spectrum (since it comes from the factory with it on, and these drives all have them off) just to see - but that didn't do anything (nor did I expect it to, but couldn't think of anything else to try). I guess the next step is to call WD and see if these drives are somehow crippled in some way in the firmware to be made to work with the Raid King device http://www.raidking.com If anyone has a WD2500JD, I'd appreciate some benchmarks.
  2. I just ran the WD tools on the drive off of Tmod's BIOS cd and lo and behold, it fails the test and crashes out with some obscure error upon running it. The drive does appear fine in Windows and can be read/written to/from just fine though -- the performance seems to be the only issue. I have another one I can try -- we've got a bunch of them that came out of a server class ATA raid array (called a Raid King) that we're upgrading the drives in. So I will do that. From what I can gather from Rgone's post, he's saying not to sweat what the BIOS is reporting in the way of drive specifications. However, there is still the issue of the WD drive not performing in line with the Maxtor drive. There's no doubt that the Maxtor is the better drive (16 mb buffer vs 8, among other things), but I still don't think the WD should be performing at just a shade over ATA66 speeds when it's supposed to be a SATA G1 drive.
  3. I've got a Maxtor Diamondmax 10 as my primary system drive and have had it for about 2 years. It's the 300 GB 6B300S0 model. I recently received a WD 2500 JD 250G SATA drive for free from work. My system drive is plugged into SATA 1 and the new drive is plugged into SATA 3. I figured I might as well put them on different controllers. These are on the Nvidia controller on my NF4 SLI-DR, the Silicon Image controller is disabled in the BIOS. In my BIOS (510-2FIX), my Maxtor reports as ATA 133. I figured this was normal, but now I'm not sure. The weird thing is, the Western Digital new drive is reporting only as ATA 100. Inside of Windows, when I look at the Nvidia interface controllers in the control panel, both drives are listed as SATA Generation 1-1.5. My Maxtor supports NCQ; the WD does not. Using the built in speed test and using other 3rd party benchmarks, my Maxtor gets up to 133 on the burst test of a theoretical 150, but the WD drive only gets up to 71.2. I suspect there's something wrong somewhere. Should the WD drive be detected at ATA 100? Everything I've checked on about the drive has turned it up as a standard SATA generation 1 drive, capable of regular 150 operation. I even swapped the cables just to make sure it wasn't a cable thing. Should the Maxtor drive be showing as ATA 150, too? Thanks for any help in advance.
  4. This is just unbelievable. After months and months of searching for the solution to this issue, I have finally found it. Mods might wanna mark this resolved or something because its something that's so far out in left field I can scarcely believe it myself and it may help other users like me who have done all of the memory and stability testing possible and still can't figure out why their SLI rig locks up (seemingly) randomly. The cause of the random freezes after long periods of idle time is caused by MONITOR POWER SAVING. Yeah, go figure. And it only happens with SLI setups and it only happens with certain kinds of cards. This did not happen with my BFG cards. But I have two eVGA cards and it certainly happens. Here's how I verified the problem: I was browsing around on the nzone.com forums in the SLI section and came across a thread that I had forgotten that I had contributed to like a week ago or whatever and found someone else was having the same problems as me. He discovered that if he turned his monitor power saving off, the issues with hanging on game start went away. I thought, "There's no way. What does monitor power saving have to do with anything?" Then I fired up WoW and it started without any problems. I closed it. I went to my power saving functions and changed my monitor shutdown timer to 2 minutes and waited. It shut down, I waited another minute, and woke it from sleep mode. I tried to load WoW. Freeze. WHAT THE F***************************************** What in the hell could possibly cause this to be the root of the problem? Someone I know posited that when the monitor powers down, the cards do as well, and perhaps are not "woken" properly by the driver. That doesn't make much sense, but I'll buy it since I don't have any other explanation. How in the world can something as innocuous as monitor blanking cause a total system freeze when a 3D app (and apparently my PokerOffice utility uses some kind of accelerated functions as well) starts? Just unbelievable.
  5. The Intel 713s will work? Is this recommended? Wow. Had no idea there. I've used the 77.76s before as well as the 77.77s -- they dont seem to matter in the scope of things. I have not disabled DEP before. I will try that. One thing is that it doesn't seem to be a factor of time, only time spent idle. I used the PC for 5 hours solidly last night and started WOW at intermittent time intervals just fine. I let it sit for 10-20 minutes and then came back and started WOW fine as well. But when it sits idle for over an hour or so, thats when I get locks. I am trying to use FileMon (www.sysinternals.com) to try to see if there's any commonality between my apps and when they lock. I have logged captures of correct application starts and am trying to get the machine to freeze with the filemon output on the screen (since it has no logging to text file features sadly) and then I will match up the lines where the machine crashes to a corresponding line in a correct start and see if I can determine what file is being read into memory when the machine hangs. I officially hate this problem btw.
  6. I have not tried this but I could do so -- I would only have one item that is a known crash generator (PokerOffice) since I could not load any games that generate the freezes without video drivers installed. What's odd is that this particular problem did not happen before I had my broken BFG cards swapped for eVGAs and my 530w PSU changed for a 600w. (as you may recall from the other lengthy thread to my credit). The CD i've used to install Windows has been the same in both cases. The only thing different would be the patch level of the OS obviously, as more updates have been released and applied to the machine over the last 3 months.
  7. OK -- I've been diagnosing and troubleshooting this issue for a while now. It is totally bizarre but now I have some more information and perhaps learn more. Essentially everything else I've said is still true but I've narrowed the circumstances even further. I don't have to run any application or anything like that. The simple act of the computer being idle for an unspecified period of time is what will generate these freezes. Over the past couple weeks I have tried numerous different BIOSes, memory timings, memory slot configurations, light / heavy loadouts of services, with certain cards in my system, without certain cards in my system, juggled IRQs around, turned various devices on the motherboard on or off... basically everything you can think of that can go in to diagnosing and resolving intermittent freezing issues has been tried. As a test, I rebooted my computer this morning at 9 am. I did not log in or anything, just simply left it idle. I logged in around now and attempted to start World of Warcraft. The machine froze immediately. I rebooted the machine and logged in, then started WoW again. It ran fine. I don't think it's connected to gaming specifically as I can attempt to load PokerOffice which is a standard Windows GUI app and it will do the same thing. There is something going on in the operating system or in the hardware that's like a "decay" of some sort, whereby after a certain amount of time passing OR some trigger happening during that passage of time that causes the machine to freeze after "it" -- whatever "it" is -- takes place. Has ANYONE ever seen or heard of anything like this?
  8. Is the 623-3 version on this BIOS cd the release version or the beta?
  9. Well, haven't had any success at all after several rebuilds and reinstalls of WinXP. I've tried the 704-2 BIOS but that caused me some other problems so I went back to the 510-2FIX but now I'm suddenly having graphical corruption issues inside of GTA:SA that are brand new to me today (the game ran fine every other day prior) and was treated to a fine PFN_LIST_CORRUPT blue screen upon Windows start once too. These are my memory timings in the yellow slots: >> In Genie Bios: >> >> 200 >> auto >> 16 16 >> auto >> 100 >> disable >> 1.500v >> 1.500v >> above VID 0 or auto >> 1.30v >> 1.50v >> 2.8v-2.9v as needed for stability >> >> DRAM Settings: >> >> 200 >> enable >> 2.0 >> 02 >> 07 >> 02 >> 07 >> 16 or 14 >> 03 or 02 >> 03 >> 02 or 01 >> 03 or 02 >> 0648, 2560 or 3120 (Try 0648 first. If it's stable, leave it be) >> auto >> enabled >> auto >> 0 >> level 8 >> level 2 >> 7.0 >> auto >> 256 >> disable >> 16 >> 07 >> disable >> >> Where I show an option, use the higher number first. When these >> conservative >> settings prove stable, you can try the lower numbers shown if you desire. >> Change one setting at a time and check for stability before trying the >> next >> one. I'm thinking of installing the 623-3 release official bios and changing to orange slots cuz its just about the only thing that I haven't tried yet. Also, is there ANY way to make the SB Audigy 2 NOT share an IRQ with the graphics card in the BIOS? Since I have SLI, the card must go in the last slot, there are no other places to put it. I just don't love the fact that the SMBUS controller, sound card, and video card are all sharing IRQ 5. I know that Win XP is supposed to make IRQ sharing worries a thing of the past, but what with all the problems I'm having I'd just like to rule everything out.
  10. Update: After a rebuild of my machine and under Andy's settings, I haven't had this problem replicate itself in a few days now. I currently have LDT voltage at 1.3, chipset at 1.6, and voltage at 2.9 with a 5x multiplier manually set. That plus a total reinstall of windows seems to be doing me pretty well right now. I have gotten a blue screen during a Media Player session (IRQ NOT LESS etc) and had an old game (NHL2005) crash while I was playing it, but thats it over the last 72 hours or so.
  11. Here's how I have been able to reproduce the problem: Reboot system. Load a game which uses the 3d accelerator functions. That means you have to actually get in the game and start playing it. Title menus, no problem. Play game for about 5 minutes or so. Open up IE, Windows Media Player, a poker client, whatever. Close said application. Attempt to restart game or another game. Freeze. Last night I played WOW for about 5 hours and then afterwards opened Media Player and tried to watch a .MPG file. I had extreme graphical corruption inside of Windows (portions of the screen went black and dragging the Media Player UI acted like an eraser). I then tried to restart WOW. Freeze. Reading what was said about LDT voltage, I upped it from 1.3 to 1.5 and started stability testing. It ran SuperPI 32M fine but then it crashed to a blue screen within 1 hour or so under Prime blend. The blue screen was like PFN_LIST_CORRUPT. So it seems that 1.5v is too strong for the LDT bus or generates too much heat that it causes stability problems. The LDT multiplier on an Athlon FX 55 is supposed to be 5x, right? 5x x 200 HTT = stock operation yes? I manually set the CPU multiplier to 13 and the LDT to 5 and lowered the LDT voltage to 1.4 to see if I could produce another crash. When I go home for lunch, guess I'll find out...
  12. Oh yeah, Xtrematrix - we both have the same vid card setup , 2 eVGA 6800 GT SLI and the same motherboard. Different memory but I'm pretty sure it's not a memory issue now. What drivers are you using for the cards? What's your sound card? What driver rev for the sound card? What bios are you using? etc
  13. My hard drive grinds a lot too, even with a permanent swapfile. I am not sure what this is symptomatic of since I kill all unneeded process and generally run a very tight, clean rig. But you're not alone.
  14. Tried testing the newest 80.40 beta detonators to no avail. I think I have found a quick way to reproduce the problem (for me) though, so that should greatly aid in the speed of testing solutions. Stay tuned.
  15. Very similar problem to what I'm having. Check my thread and lets try to work on this together: http://www.dfi-street.com/forum/showthread.php?t=16620
×