Jump to content

mongoose470

Members
  • Content Count

    89
  • Joined

  • Last visited

About mongoose470

  • Rank
    Member
  1. Mushkin Redline XP4000 2GB here. 280FSB and rock solid, that is until my DFI bit the dust.
  2. For those experiencing the 3-5 second freezes, you're likely suffering from GPU throttling if the card is overclocked. Use Rivatuner Hardware monitor to determine if you're throttling. Check nvnews forums for a huge thread on the subject. I have terrific temps on my card even at 400/1100 (watercooling.) But it still throttled. Upping my GPU voltage in the card's BIOS to 1.4V solved the issue somewhat, enough to achieve Ultra speeds without those pauses (throttling.) Disabling fastwrites can eliminate the throttling for some but at the cost of performance (1000 3DMarks on my system.) It was once thought to be a NForce 3, 6800 series bug. Now it seems more like a Forceware issue. If I use any driver post 66.93, throttling returns on even the slightest overclock even with the Volt mod. A bug has been identified by NVidia with the 7800GTX. This so called "cold bug" throttles the GPU to stock at temperatures seemingly below 35C. This happens with NForce 4 motherboards so it doesn't appear to be a chipset or chipset driver issue. I don't think it's a temp issue nor is it isolated to 7800GTX cards or any chipset. My theory is a Forceware issue with cards using aftermarket cooling but not the default fan connection. The driver detects no fan turning, interprets it as a fan failure and throttles the card back. I tried to put my theory to the test by connecting the stock fans while leaving my watercooled solution installed and see if it throttles. Unfortunately since my temps are so cool, the fans shut off completely when Windows is finished booting (adding further credence to a Forceware issue.) So I cannot tell if having a fan connected to the default connector solves the throttling issue. 6800s vary the fan speed according to temperature demands so the driver or card's BIOS could be shutting them down, then the driver believes there is a fan failure. I believe it is a Forceware issue introduced after the 66.93 driver. I'd like to test this further so I'm open to suggestions.
  3. For those experiencing the 3-5 second freezes, you're likely suffering from GPU throttling if your card is overclocked. The "bug" seems to only occur in D3D apps. Use Rivatuner Hardware monitor to determine if you're throttling. Check nvnews forums for a huge thread on the subject. I have terrific temps on my card even at 400/1100 (watercooling.) But it still throttled. Upping my GPU voltage in the card's BIOS to 1.4V solved the issue somewhat, enough to achieve Ultra speeds without those pauses (throttling.) Disabling fastwrites can eliminate the throttling but at the cost of performance (1000 3DMarks on my system.) It was once thought to be a NForce 3, 6800 series bug. Now it seems more like a Forceware issue. If I use any driver post 66.93, throttling returns on even the slightest overclock even with the Volt mod. A bug has been identified by NVidia with Forceware and the 7800GTX. The so called "cold bug" throttles the GPU to stock at temperatures seemingly below 35C. The issue also occurs on NF4 motherboard so it doesn't look like a chipset issue. I don't think it's a temp issue nor is it isolated to 7800GTX cards or any chipset. My theory is a Froceware issue detecting a fan failure on cards that have aftermarket cooling but don't use the default connector. I tried to put my theory to the test by connecting the stock fans while leaving my watercooled solution installed and see if it throttles. Unfortunately since my temps are so cool, the fans shut off completely when Windows is finished booting (adding further credence to a Forceware issue.) So I cannot tell if having a fan connected to the default connector solves the throttling issue. 6800s vary the fan speed according to temperature demands so the driver or card's BIOS could be shutting them down (especially on watercooled cards,) then the driver believes there is a fan failure and throttles back to low power 3D move (stock clocks.) I believe it is a Forceware issue introduced after the 66.93 driver. I'd like to test this further so I'm open to suggestions.
  4. Agreed. I never got 9x working however I had to use slots 1 & 3 to get 11x working properly, otherwise I receive a few hundred errors in memtest. Have you tried switching slots when using 11x? With 9X I'd go straight to DFI if I were you. Angry and rgone can accomplish only so much and it IS a real issue that needs addressing.
  5. Because when we examine the original thread in question, he claimed the cold boot issue was resolved with the 5/04 BIOS then went onto the clearly unresolved issue of receiving memory errors in memtest only when using certain multipliers. Unfortunately I have no tip for filtering out every single post that is irrelevant to the issue sought during a search. Regarding the 9x multiplier issue or any other issues, I fear the DFI NF3 motherboards will soon likely be joining the ranks of "unsupported motherboard." Here's another tip for searches... http://www.dfi-street.com/forum/showthread...90662#post90662
  6. I found it in a minute. I also found a few more threads with the keywords "multiplier AND memory AND issue" Less than a minute, Only three pages, hardly "10,000 posts." Game, set, match. Use the search function. It's your friend
  7. Go read ANY support forum for any motherboard. By design, those forums are for people with problems so it stands to reason you're going to see a plethora of complaints. Regarding DFI, we wanted... 1) A motherboard that pushes RAM and CPU much further than it was designed to... 2) that motherboard to have every feature available on the market... 3) that motherboard to be dirt cheap relative to the features and performance. Something has to give between 1-2 and 3. You want a motherboard that lets you overclock any hardware, run ANY hardware combination without a single glitch, bug, crash???? Be prepared to spend a over a grand. Be prepared for those companies to go belly up quicker than a rabbit gets (you fill in the blank) DFI does not build motherboards for web surfers and online gamblers. They make enthusiast boards for crazed hot rod enthusiasts and attempt to make them affordable to those with less than six digit income. Like any real hot rod, you'll spend a lot of time under the hood and some issues will never be resolved. That's the REALITY of the "affordable" enthusiast market. Such is the reality of the entire affordable PC market. The tradeoff is bugs and service. You want to design a system around absolute rock solid stability and nothing more, buy something else or don't overclock... and good luck. You'll need it because I haven't seen such a system yet. Yes, it sucks. But I can afford it.
  8. That's just it, I haven't heard of a reason why 9x multiplier doesn't work on CPUS other than a 9x default. I suspect an issue with the NForce chipset, ANY NFORCE chipset I've ever had. I'd be curious if the 9x issue is limited to DFI or is present with all NForce 3 motherboards. I recall that 9x or 9.5x was a huge problem for many on the NForce 2. I can't remember which since it's been ages since I used my Abit. I doubt we'll ever see a fix. With the NForce 4 and SLI motherboards released, that's likely overwhelming the techs as is.
  9. SEARCH FUNCTION DFI-Street has generously provided us????????? http://www.dfi-street.com/forum/showthread...highlight=9x%2A Obviously well documented enough for rgone to take a poll about the "issue" and provide links to threads on other forums. To Capt Proton: I confirmed there is a known and documented issue with the 9x multiplier. I already acknowledged his claim about 11x and telling him mine works is an explaination of why I can't offer any info on whether it really is a bug or how I solved it. I simply don't know about 11x or the odd multipliers. BTW: If we follow your rules and forbid any responses of "hey, mine works" how in hell could techs ever seperate a real issue with the board or bios from a common plague known as USER ERROR????
  10. The 9x multiplier issue is well known and documented on the DFI Lanparty UT 250GB and has been since shortly after its release. The moderators are likely not responding because of that reason: The issue has already been reported. In short, you'll get tons of memory errors using the 9x multiplier on any A64 that isn't a default 9x CPU. I get hundreds of thousands on test 5 of Memtest. I know of no odd numbered multiplier issue because 11x works fine on mine.
  11. Well I could have another RMA coming so I don't have much option there. Either I get another RMA or I'm stuck with a paperweight. Wasn't the 3200VX BH5 based? Mine was pretty solid. How about the Mushkin Redline PC4000?
  12. Only be embarassed if you DIDN'T ask the question. Just hit the DELETE key.
  13. I'm thinking about requesting a cross ship since I've already been waiting over a month just to get my system back up to full potential. Never again! Never again will I do a kind favor for a nephew and give him a nice working pair of RAM as a present (actually I built him a system.) "Suffer...BIATCH!" No good deed goes unpunished.
  14. That's the likely probability. I'm conversing with Steve over at bleedinedge. Edit for Thunda: I've already received an RMA. This will be my second RMA.
  15. the RAM will boot... one stick won't pull it's advertised speeds. OCZ VX is advertised to run @ 250 FSB with 3.3 VDIMM and 2-2-2-8 timings. This is the second kit where one stick couldn't do it. At this point, I really wish I stuck with Mushkin.
×
×
  • Create New...