Send News. Want a reply? Read this. More in the FAQ.   News Forum - All Forums - Mobile - PDA - RSS Headlines  RSS Headlines   Twitter  Twitter
User Settings
LAN Parties
Upcoming one-time events:

Regularly scheduled events

Out of the Blue

Here's a question for those of you more technically apt than myself, which includes my grandma, but I forgot to bring this up at brunch yesterday.

I've been trying to run Battlefield 2 in piggish 1600x1200 on my bust-out retail super-duper 6800 Ultra-OC video card. The card itself seems perfectly capable of running at such high resolution, but I have been getting unexplainable Blue Screen of Death errors in Windows XP with an infinite loop in the NV_DISP driver. The problem does not seem to occur at lower resolutions, but at 16X12 it is intermittent, but inevitable, often preceded by flashes of texture corruption. After a go-through with tech support I cleaned out the old drivers with driver cleaner, reinstalled the latest 77.72 FORCEWARE drivers, and confirmed that if the card's absurdly high 120 degree centigrade heat alarm was not being set off, the problem was probably not thermal.

I then tried again, with the same result.

The BSoD included a message to the effect that the problem was likely with either the driver or the card, so I called back tech support, and was told that it was possible that this was a problem with the application itself. I was then told that in order to demonstrate that the card itself was defective, I was in for the nightmarish prospect of repeatedly reproducing the problem after, a) reinstalling the game, b) using a different 3D app, and c) repeating (a) and (b) on a second machine altogether. Now if that's the process I really must go through to determine the problem, then fair enough, but a Google search on NV_DISP infinite loop errors seems to indicate that this is a problem that's been mysteriously plaguing NVIDIA users for literally years now, and troubleshooting tips range from the useful, like testing your RAM (seven passes by memtest 86 says this wasn't the problem), to the worthless (almost every time someone asks this on a forum he is inundated with driver rollback suggestions, but this has happened with three different driver revisions now), to the spooky (I don't think the most desperate or reckless of users would implement all the different registry hacks I've seen suggested to address this). The one bit of video card related voodoo I still plan I trying here is backing off the AGP speed from 8X to 4X, which worked for me on a different problem once before.

So anyway, my question is simply this (I bet you had almost forgotten by now that I started off promising a question here). Before I embark on the lengthy path set out for me by Mr. Tech Support: is his assertion that the BSoD could be cause by the game code itself is accurate? I know that misbehaving apps are not supposed to be able to crash the system (which to my recollection was genuinely true for my in several years of running Win2K Professional), but I also know that just because something is not supposed to happen, doesn't mean it is impossible (I remember seeing proof-of-concept BSoD code for WinNT that was all of three lines).

So... no application-triggered BSoDs in WinXP... fact, or fiction?

Blue Links of Death! Thanks Mike Martinez, Ant, and EvilToast.
Links: How To Make Your Own Custom Body Kit.
Stories: Coke tries to can Indian poster.
14-Pound Baby Girl Born in Kentucky.
Internet provides instant Harry Potter reviews.
Science! Small Earthquake Shakes Mount St. Helens.
Oklo: Natural Nuclear Reactors. Thanks Flying Penguin.
Poaching making China elephants evolve tuskless.
Media: JCB Ballet. Thanks Lost Dragon.
Follow-up: Thousands mark first atomic blast.
Shuttles Dogged by Aging Parts.
Teh Funny: FoxTrot.

Post Comment
Enter the details of the comment you'd like to post in the boxes below and click the button at the bottom of the form.

26. Don't OverClock anything... Jul 17, 2005, 18:48 WaltC
The other suggestions I'd have made have been made--such as check your ram and PSU...but I think you should begin with this one:

If your 6800 is overclocked beyond its nVidia factory defaults for the particular 6800 gpu you own (as the marketing name of "OC" seems to indicate) then I'd use Coolbits to lower the gpu clock to the nVidia standard clocks and try again.

Ditto any cpu/fsb overclocking you are doing in your system, if any. Set all clocks to factory default and then see if the problem repeats.

Remember that nVidia doesn't warranty or support the overclocking that some nVidia OEMs (like BFG) do to try and make the cards run faster to attract more business. There's a good reason nVidia doesn't support 3rd-party overclocking directly--they don't test and validate their gpus for overclocked conditions.

At 1600x1200 you are putting maximum stress on a 3d gpu when running a 3d game at that resolution, and as such, in a game serving up the right conditions, even a relatively "minor" gpu overclock could cause the gpu to fail--so find out what the stock clock is for your gpu and set it there and you may well see the problem disappear. It's very likely as you do not apparently have these problems under lower resolutions in the game at the "OC" setting.

The only time I ever experienced the "infinite loop" graphics error under XP was way back in 2001 and when I'd first installed the OS and was running a nVidia GF4 gpu. But in that case *all* my 3d games were affected equally--in that none of them would run at all.

It turned out to be a problem between the VIA chipset I was using at the time and Windows XP--in that I was running the fsb clock for the ram bus at a higher speed than the fsb clock setting for the cpu (asynchronous operation), and although the same video card and VIA chipsets and games had no problem running this way under Win9x, XP would tolerate nothing but synchronous clocking of the ram and cpu buses. As soon as I set up synchronous timings for the cpu and ram bus under XP the problem completely vanished.

But since this is apparently a problem you only get in this game at this resolution, my bet would be that something overclocked in your system, or just your overclocked gpu if nothing else, is causing the game to fail because of being overclocked. Because the problem is resolution sensitive, my bet is that it's the "OC" clock of your gpu causing the problem in this particular game.

Avatar 16008
It is well known that I do not make mistakes--so if you should happen across a mistake in anything I have written, be assured that I did not write it!
Reply Quote Edit Delete Report
      ;)   ;)   :(   :(   :o   :o   %)   %)   :)   :)   :|   :|   ;P   ;P   X|   X|   :D   :D   More
Login Email   Password Remember Me
If you have a signature set up, it will be automatically appended to your comment.
If you don't already have a Blue's News user account, you can sign up here.
Forgotten your password? Click here.
          Email me when this topic is updated.

Special Codes

  • b[bold text]b
  • i[italic text]i
  • u[underline text]u
  • -[strikethrough text]-
  • c[code text]c
  • +[bullet point]+
  • q[quote text (indented)]q
  • [quote="Author"]quote text (indented)[/quote]
  • [url=Link]text[/url]
  • r{red text}r
  • g{green text}g
  • b{blue text}b
  • m{maroon text}m
  • s{secret text (shows in the background colour)}s

Forum Rules

  1. Disagree all you want but attacks of a personal nature will not be tolerated.
  2. Ethnic slurs and homophobic language will not be tolerated.
  3. Do not post spam, links to warez sites, or instructions on how to obtain pirated software.
  4. Abusing the forums in any manner that could be construed as 'griefing' will not be tolerated.


Blue's News logo