GTX 285 - Every driver BSOD's with COD4 :(

Hey guys,

I recently got a GTX 285 OC2 from BFG Tech clocked at 694Mhz. I love the card and have had absolutely 0 problems with some games but BSOD's in others. I have tried every driver since the card came out up until the 182.06's which I have now. In COD4 and a few other games I get BOSD's with the blame thrown on the nvdkllm.sys file. It is random but seems to happen on the grassy maps like Creek, Overgrown or Downpour.

Games that have issues are:
COD4 (Only tried Multiplayer)
FEAR2 (Singleplayer Only)

Games that I can play for hours with no issues are:
COD5 (Only tried Multiplayer)
FEAR2 Multiplayer
Unreal Tournament 3
Team Fortress 2
Left 4 Dead

I have a very stable overclock but I get exact same results without the overclock on and default bios settings on my mobo. I have tried re-installing COD4 and I use DriverCleaner the proper way to un/re-install drivers. Here's my basic specs:

-Core2Quad Q6600 (OC'd to 333x9 for an effective 3.0Ghz)
-eVGA 790i Ultra SLI Mobo (recent bios update)
-BFG Tech GTX285 OC2 (OC'd from the factory to 694Mhz)
-4 Gigs Kingston Hyper Memory DDR3 Linked at 1333Mhz (7-7-7-18) to match my CPU (capable of 1800Mhz at 8-8-8-24).
-Windows Vista Ultimate x64

My CPU temps are fine in the mid 50's and my GPU temps are just under 80 when at load. Regardless, I have tried without any overclocks and I get the same results.

Anyone have issues with the GTX285 and COD4 or just me?

TIA,
Sam

 

Oh, and the crashes are just kinda random. I'll be playing and my monitor will freeze for a brief second, turn off as if it has no signal and then turn back on when the driver restores back at the blue screen of death. Thanks again....any help appreciated.

 

I had problems with drivers until 182.06 too, with random BSOD's in my SLI system, it resolved totally with 182.08 and 185.20 drivers

 

Here's the Analysis of my MiniDump

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini022209-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0xfffff800`01e00000 PsLoadedModuleList = 0xfffff800`01fc5db0
Debug session time: Sun Feb 22 23:12:02.471 2009 (GMT-5)
System Uptime: 0 days 6:07:56.593
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8005b744e0, fffffa600381a1a0, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+191a0 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8005b744e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffffa600381a1a0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP:
nvlddmkm+191a0
fffffa60`0381a1a0 ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 2

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffffa60`03541a08 fffffa60`01308398 : 00000000`00000116 fffffa80`05b744e0 fffffa60`0381a1a0 00000000`00000000 : nt!KeBugCheckEx
fffffa60`03541a10 fffffa60`013081cb : fffffa60`0381a1a0 fffffa80`05b744e0 fffffa80`08a50540 fffffa80`05b744e0 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffffa60`03541a50 fffffa60`012c2d8a : 00000000`003003dc 00000000`00000000 fffffa80`08a50540 00000000`00159728 : dxgkrnl!TdrIsRecoveryRequired+0x16f
fffffa60`03541a90 fffffa60`013832a3 : 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000002 : dxgkrnl!VidSchiReportHwHang+0x312
fffffa60`03541b40 fffffa60`01381ea5 : fffffa80`08a50540 fffffa80`00000000 00000000`00159728 fffffa80`08a50540 : dxgkrnl!VidSchiCheckHwProgress+0x7b
fffffa60`03541b70 fffffa60`012c70f8 : ffffffff`ff676980 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!VidSchiWaitForSchedulerEvents+0x199
fffffa60`03541bf0 fffffa60`01381cc5 : 00000000`00000000 fffffa80`08cb5da0 00000000`00000080 fffffa80`08a50540 : dxgkrnl!VidSchiScheduleCommandToRun+0x398
fffffa60`03541d10 fffff800`02077ff3 : fffffa80`08c9ebb0 fffff800`01e4f637 fffffa60`021ae850 00000000`00000001 : dxgkrnl!VidSchiWorkerThread+0x95
fffffa60`03541d50 fffff800`01e8f546 : fffff800`01f74680 fffffa80`08c9ebb0 fffff800`01f79b80 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`03541d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+191a0
fffffa60`0381a1a0 ?? ???

SYMBOL_NAME: nvlddmkm+191a0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4990b203

FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------

 

Why not put everything on stock, i mean everything back to normal settings and just try out the WHQL drivers and see how it goes. IMO, OC is lame, and i only do it with my video card sometimes, and sometimes i don't. I get a BSOD in some games myself with my BFG 8400GS. But i notice those games always gave me a BSOD with BFG geforce cards, so i am glad i have my 2400HD for spare.

 

Exactly what he said. The first thing you should always due in this situation is reset your OC's. You said you already tried that too so I would try out some other games to see if you need to RMA the card. I play COD4 religiously and have never had a BSOD or a crash of any kind caused by a driver issue. In fact I've never had the game crash at all.

Also the GTX 285 isn't really a card that you're going to be able to OC very much. Most people have had a hard time getting the card to go very high. Personally I don't see the point of OCing this card but whatever floats your boat. You also bought a card that was already OC'd so that will also limit your ability to OC it. I don't see EVGA making the GPU Voltage Tuner compatible for this card anytime soon sine they also make 3 OC'd models and then they would be screwing themselves. I imagine sometime in the future we will get a Voltage Tuner for the 285 but for now I would just be happy the card kicks ass.

 

Yes , it worked for me. My overclock was stable ... but i got BSOD's in games and I think I have some memory issues now. But after I put everithing on stock, ... NO BSOD ... none ! I have 2 weeks now with zero blue screens. So i keep it like this and get a PII later. !!!! Try to leave everyting to stock speeds.

 

downclock a bit might help

 

I would start looking toward the RAM and try downclocking and/or memtest86.

 

As faust1200 said, my bet is on the RAM.

I don't want to throw stones, but 790i Ultra is quite whimsical chipset. Personally I have Asus Striker II Extreme and all I can say, that I had a lot of trouble with my RAM settings, even BEFORE overclocking. I nearly RMA'ed everything before finally hitting the right combination of settings (and I can say they were slightly different from what I was expecting)

So, use of memtest86, I think, is a mandatory in your case. But, of course, try it first on not overclocked system.

 

same i had a problem with gtr-evolution and the 182.06 drivers, kept getting the blue screen memory dump thingy. all fixed now with the new drivers, now all i have to fix is the downshifter at full lock on my wheel lol.

 

I have tried MemTest86 and all was fine. Also, I have mentioned that I get the same results without the OC. I actually do have it all stock as of yesterday(default BIOS settings) until I figure this out.

Thanks for the help anyway guys. I thought this might have been the place someone would know how to read a minidump analysis.

 

for cod4 mp; try make copy of config_mp file, then delete original, play mp for few secs, and replace with original

this stopped random bsods for me

 

Have you tested 182.08 drivers? We are helping you and you don't reply to us.

 

I read the release notes on 182.08 and didn't see any fixes for COD so I skipped it originally. After you mentioned it earlier, I figured it was worth a try. I installed it last night and played a few rounds with no crashes sofar.

If that still doesn't work, I will try "bokah's" suggestion with the config file.

Thanks guys, I'll report back with anything that seems to be a sure fix.

 

needed it after changing from ati to nvidia

 

In the release notes not appear all changes, to me 182.06 and earlier drivers since 181.20 gave me bsod's in all games, and after install 182.08 drivers i haven't got a crash, it repairs all problems with SLI systems.

 

I heard about that now that you mention it.

Although, I've always been on the green team.

 

I am hoping you are right.

I am hoping you are right. <Crossing my fingers> I'll be playing a lot between now and Sunday so I should be able to find out if it works.

 

I had a problem with both COD4 and COD WAW and both times it was an onboard sound issue that needs an easy adjustment.