Windows 7 - Windows 7 RC + nvlddmkm.sys BSOD

To Whom It May Concern:

I have an issue with my EVGA GTX 280 SC, regardless of the driver installed I get a BSOD with nvlddmkm.sys error and a memory dump. It works just fine with the 6600GT I used as an alternative. I just wanted to know if anyone else is getting this error.

Regards,

Eagle Eye

So it crashes with the default Windows RC driver with no updates?

Correct my friend.

It was common problem with vista users in the early days. Typically bad or unstable drivers were the culprit and there was also some talk that the factory overclocked cards would caused the driver to crash. I'll see what EVGA has say, but I would suspect they will direct me to nVidia since they would assume this is not a hardware issue.

I forgot to add that I also experienced this with the previous Windows 7 Build, even after a clean install the problems persisted. That does make me think, my first GTX280 *stock clocks* had no issues with previous build. I'll bring this up with EVGA and see if they can't provide me with a stock bios and see if it might fix the problem.

Thanks for the reply,

Eagle Eye

Have you run eVGA's Precision utility to underclock and see what happens?

I have a pair of 260s, one being a stock and one being a 'stock' that I got from them via the Step-up program - but which is factory clocked to matching specifications of the SSC - and I have not had any issues with any Win 7 build except the 7057 which just did not like my system at all....

I should of mentioned this first. I don't get anywhere near a desktop to underclock anything, the error happens when Windows 7 initializes the display driver just after the splash screen. I get a black screen then a BSOD about a 60secs later with a memory dumb.

***It does work in SAFE MODE***

Just for kicks, pull your stock clocked GTX260 and just install the SSC ver. see if doesn't kick back the same error I am getting. If it does, well you'll completely understand my delima. If it doesn't I will be pretty convinced that the my overclock on my SC GTX280 is not stable enough along with the current nVidia drivers to work in Windows 7. Also, EVGA will be getting its card back.

Thanks for the reply,

Eagle Eye

It doesn't. I have tried it already b/c someone else mentioned this exact same error.

Of course, my mobo is an eVGA also, an I have never had any issue installing with dual 2 GB sticks of ram either, and neither have I had issues with installing *with* all my OCs and such enabled in the BIOS _ not in *nix, not XP, not Windows Vista and Not Window s7.

It's like I have a reversed jinxed machine....

oh, and I use eVGA's Precision to OC *both cards to a matching 636/1397/1107 settings, above *both* card's normal settings. No issues with the drivers at all.

I've done installs stocked clocked and overclocked on the CPU, however the GPU I can't do much about, thats a bios I can't change.

I am not suprised that your GPU doesn't have the same problem as mine, SSC ver. meets a much higher standard so to speak when it comes to overclocking than any SC will. That being said SC overclocks are always pretty modest and it says alot to just how well the card was binned upon selection. I guess when you really look at Beta OS, Beta VGA drivers, and a moderately unstable OC on a GPU you're almost guaranteed to run into problems.

Thanks very much for all the replies, I'll update the post just as soon I get a reponse from EVGA. Hopefully there will be a solution

Regards,

Eagle Eye

Kewl - but in reality you *can* do something about the SSC as well - you'll have to be careful, but NiBiToR is made just for this purpose....

Although you'll probably want to play around with it in XP as that i much more GPU BIOS friendly than Vista / 7 have proven to be thus far....

The long awaited update...

Troubleshoot troubleshoot is all EVGA had to say. I will likely try the Vista64bit drivers given the opportunity and time in the near future. I'll update this post in a day or so just as soon as the girlfriends downloads finish.

Regards,

Eagle Eye

What you are experience is called TDR, is a tool that check the response off your gpu to the system and if this response takes more than 2 secs your display driver is rebooted until a specific number of times and end up in a bsod. Ive that here too.
This post solved my problem, just have to increase the time on TdrDelay in registry or you can disable tweaking TdrLevel to 0.
Its a tweak but can free you from this issue until we wait for proper drivers for Windows 7.
Best regards.