underdog1425

Not too sure if this is even the right place for this thread...

Basically, I will be operating the system in my sig (only 2 gpus at the moment) and suddenlt it bluescreens on me.

This is something that had been giving me trouble previously and I never bothered to write down the file that the bluescreen was telling me was a problem.

"nvlddmkm.sys" Is the file. I googled it and apparently a lot of people are having problems with this guy and vista and 7, but I don't necessarily think that my problem is the same as theirs.

A few noteworthy facts:

If I use nvidia control panel to change from multiple displays (for folding) to a single one, it crashes and I get this error bluescreen when I log into windows..so I have to do a system restore. What works is using the windows display manager to change displays, then nvidia control panel to enable/disable SLI for folding.

The system is unoverclockable. If I change ANYTHING, volts or speeds, it gives me this problem again. Not necessarily the exact file and bluescreen, but it either won't load into windows, or it just reboots.

However, if I do a system restore and keep everything at "optimized default settings" in the bios, then everything is fine. I can overclock the video cards with evga's precision, and have been folding, playing games etc.. perfectly fine.

Any ideas?

for what its worth, when booting and posting, when it shows the bus devices and their IRQ, it has "NA" for the memory controllers, but has a number for everything else... O_o

__________________
Unofficial Neked Computer ClubAlabama Overclocker Member of the OCN Diablo III ClubCurrent Project Why water > air

7hm

Have you rolled back to any previous drivers that worked? Also nvlddmkm.sys can be a number of things unstable oc's, bad ram,faulty card, bs windows repost. Try uninstalling your drivers completely then going into safe move and running driver sweeper removing anything involding nvidia except your chipset of course unless you'd like to reinstall those too and check your repository folder and make sure there's no remaining nvlddmkm.sys files.

http://www.guru3d.com/category/driversweeper/

__________________

underdog1425

Update.

On my system, to swap between multiple displays and single display, nvidia control panel cannot be used. I have to use the built in windows "Personalization" method, going into the display settings that way and choosing between extending the display and showing only on display 1.

I recreated my problem by enabling SLI while I was operating on both 'displays' (I use a dummy plug) and sure enough I get the nvlddmkm.sys BSOD and hard boot after a memory dump.

I removed the 186.16 drivers that I was using and installed the 181.16 x64 drivers, swapped out a different stick of memory, and reset all of my clocks including video cards.

Using the windows default method, I was able to swap back and forth between sli mode.

Ignoring the windows display settings and using nvidia control panel and enabling SLI, I caused the nvlddmkm.sys BSOD.

Remove and driver sweep the 181.16 drivers, install 185.85 x64, rinse and repeat. Works like a charm.

I put in one of my blade sticks, recreated the problem, reinstalled the drivers, and confirmed the same windows display > nvidia cp working.

Took that one out, tried the other one, same thigns worked. Now I've got both sticks in and have again been able to swap back and forth between sli and non sli using that method without a problem.

Going to apply my overclocks and will check back.

EDIT:

Assuming the stability of my overclock, then the solution stands.

If your setup is like mine, and you ran into this problem, try enabling/disabling extra displays first with windows display manager. Once 'display only on 1' is set, go into nvidia control panel and enable sli.

To use two screens, disable SLI in nvidia CP first, then use windows display manager to activate the second display. And vice versa =]

__________________
Unofficial Neked Computer ClubAlabama Overclocker Member of the OCN Diablo III ClubCurrent Project Why water > air

jm3

i keep getting this bsod it happens if i try to overclock either of my cards using ntune i have to run stock speeds atm. it only happens if i oc, im not even ocing them by much there not in sli however so my problem differs from yours

underdog1425

Only happens when you OC? Im far from the right person to ask advice of, but that sounds like a hardware problem to me.

See if you can cause the BSOD. Once I figured out how to intentionally cause the bluescreen I was able to rule out bad hardware, seems to be a software problem with nvidia control panel.

Im not using ntune though, using EVGA Precision.

__________________
Unofficial Neked Computer ClubAlabama Overclocker Member of the OCN Diablo III ClubCurrent Project Why water > air

jrharvey

Your not alone. I havnt been able to figure it out either. I have had 3 GTX 260's and they all do the same thing so its not the cards and Ive tried new power supply, motherboards and ram. Nothing seems to work and Nvidia just blames other hardware which is useless to me. I have narrowed it down to crappy drivers and/or dual screen setups. Not sure why but it ONLY does it when i run dual monitors.

BTW: Nvidia told me that my monitor must not be compatable. I was like WTH? Is that even possible? Can a monitor be causeing a BSOD? I think not. They really just piss me off sometimes.

__________________
My Digital Portfolio
55nm GTX 260 Overclocking Thread

underdog1425

Ofcourse they blame other hardware

Personally I think it is an "nvidia + multi monitor" problem. It can't be my monitor, because the one that I use for my main works fine, and the other is a dummy plug! xD

Plus, these cards are fresh from RMA, the ram and PSU are brand new, and the CPU has yet to fail me.

Could be the mobo, but I don't think that's the case...it passes everything that Hiren's Boot CD has to offer.

__________________
Unofficial Neked Computer ClubAlabama Overclocker Member of the OCN Diablo III ClubCurrent Project Why water > air

jrharvey

It ONLY happens in vista for me. Ive never seen it happen in XP so I assume its a driver issue or something wrong with the vista kernel itself (which I doubt but possible). Since vista and windows 7 are so much alike I assume thats why you see the same issue.
---- Whatch your temps. I have noticed before BSOD, the temps skyrocket to 90,100 or even 120c
Im assuming its not really getting that hot, it would be rediculous. I think it may be the sensor. Keep in mind, I have RMA'd twice already.

__________________
My Digital Portfolio
55nm GTX 260 Overclocking Thread

jm3

i can oc the cards fine in vista and xp. win 7 just doesnt seem to like nvidia drivers its always nvldmmkm.sys and i cant get rivatuner to work in win7 something to do with unsigned drivers.

underdog1425

I had one telling me it was 100 something C at one point. RMA'd both of mine, and they work perfectly overclocked and at stock clocks, I only get this problem when I try to switch between SLI and extended display. Weird.

Same here, I used rivatuner until windows7 now I use EVGA Precision.

__________________
Unofficial Neked Computer ClubAlabama Overclocker Member of the OCN Diablo III ClubCurrent Project Why water > air