Windows 7 RC + nvlddmkm.sys BSOD

Eagle Eye · May 9, 2009

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

johngalt · May 9, 2009

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

Eagle Eye · May 9, 2009

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

johngalt · May 9, 2009

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....

Eagle Eye · May 9, 2009

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

johngalt · May 9, 2009

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.

Eagle Eye · May 9, 2009

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

johngalt · May 9, 2009

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....

Eagle Eye · May 18, 2009

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

jutajata · May 18, 2009

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 w7.
Best regards.

nuluis · May 19, 2009

I have had a similar problem with my 2 XFX 9800GTx+ in SLI and by themselves. Except it only happens under a heavy load in a game. Would this also be a tdrdelay problem?

It doesnt memory dump, but it causes constant hangs which only ctrlaltdelete fixes temporarily in game, then continues to do it over and over again until eventually i get the nvlddmkm problem.

GatoSoft · May 25, 2009

Hi! ^_^

I've just upgraded my PC from Beta 7048 to build 7127 and get this problem too. Using nVIDIA drivers v185.85 give me that same error. Mainly when I play videos on Media Player Classic using EVR Custom Presenter, that uses graphics card for video processing, screen flashes for 1 or 2 secs. and then shows the BSOD with nvlddmkm.ddl.
Going to try that tweak that Jutajata shows to us and I'll come back to tell you what's up.

Eagle Eye · May 25, 2009

Looking forward to your results.

Sounds a lot like it nuluis it could very well be. We can only hope that nVidia works to fix these issues. We must remember that even in Vista upon its release these problems were all to common.

EE

GatoSoft · May 25, 2009

Well... after trying too much combinations I just gather the possibility to delay a little the video driver restart process before it shows the BSOD. I mean, I can't fix the error yet.

I want to get my games working again before one of my head's veins explode!

jutajata · May 26, 2009

GatoSoft said:
Well... after trying too much combinations I just gather the possibility to delay a little the video driver restart process before it shows the BSOD. I mean, I can't fix the error yet.
I want to get my games working again before one of my head's veins explode!

Ive noticed that a lot of people are getting problems with the 185 nvidia drivers and get this solved by downgrading to 181, try to disable the tdr using the command TdrLevel 0 in registry, im an old ati (1900Xt) user and this fixed the issue for me until good drivers are make.

Cheers

GatoSoft · May 26, 2009

I had seen that fix using TdrLevel=0, but I didn't tryed with it because I tought that it would generate even worst results. But now, let's give it a try.

Mew · May 29, 2009

GatoSoft said:
I had seen that fix using TdrLevel=0, but I didn't tryed with it because I tought that it would generate even worst results. But now, let's give it a try.

So did it work?
I'm getting the exact same error. And I'm only getting it when I'm using EVR custom present in MPC HC.

I'm forced to switch to Renderless WMR9 to stop my windowns from crashing. I really hope the next nvidia drivers fix this...

Jverse · May 31, 2009

Nvidia Drivers strike again....

I am having the same issue installing windows 7 after splash screen BSOD. And now there is nothing I can do about it...You can't get any futher into the install because it never completes. No safe mode no nothing....this is so frustrating....Can Nvidia ever release good drivers...I mean what do they do there....I've been a gamer for 10 years now and I haven't seen them release flawless drivers for any platform....ever....

Sorry, just ranting, but I was enjoying my systems just fine until they released this crappy driver....Now I'm back to square one with none of my systems working correctly except my laptops.... Any fix would be greatly appreciated. I would love to try the registry fix but since I can't even get into windows, I am a sitting duck....

GatoSoft · Jun 1, 2009

Hi again! I've good news minna! ^o^

I've reinstalled Windows 7 in an attempt to get MPC HC with EVR Custom Presenter working. This time I have installed build 7137 and get the same error, with & without the 185.85 nVIDIA drivers. But I've solved the problem easily. Seems to be something wrong with the H.264 decoder built in Windows 7 (try to play something in WMP12 and you'll get the same error).
So, to fix the problem, just go to Programs -> K-Lite Codec Pack -> Configuration -> ffdshow video decoder. Once there, in the left-side options click "Decoders" and change the "H.264/AVC" codec from "disabled" to "libavcodec". This will allow you to use the EVR Custom Presenter again without problems.

Hope it helps you all and leave comments to know if everything went well!

falcon · Jun 1, 2009

Eagle Eye said:
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.

or try build 7137 it is working fine with me..
Thanks for the reply,

Eagle Eye

have u installed any driver after installing rc??
are u using build 7100??

if u are using 7100 run windows update. there u will find a hotfix that will probably solve ur issue.....

and due to some reason u cant do that then open the windows in safe mode then open run, type msconfig. now in msconfig open services and select "hide all microsoft service" then switch off all the services that are present....
and disable all startup programs....
ur windows should boot in normal mode...

Windows 7 RC + nvlddmkm.sys BSOD

New member

My Computer

Antidisestablishmenta

My Computers

New member

My Computer

Antidisestablishmenta

My Computers

New member

My Computer

Antidisestablishmenta

My Computers

New member

My Computer

Antidisestablishmenta

My Computers

New member

My Computer

New member

My Computer

New member

My Computer

Windows 7

My Computer

New member

My Computer

Windows 7

My Computer

New member

My Computer

Windows 7

My Computer

New member

My Computer

New member

My Computer

Windows 7

My Computer

Banned

My Computer