nvlddmkm.sys errors and crashes with Vista32/64bit

[KG26_Alpha]

Hehe yes nvlddmkm.com

I'm very familiar with this site and many others, a quick googling will show many, and TDR shows up a lot.

No my post wasn't done as the " ultimate fix" but as "its fixed the problem for me", if you read it again, but as a point in the right direction as recommend by Microsoft.

The links provided give enough information to the reader for them to decide if it's a viable solution for them, be it they don't know how to edit the registry or simply want a "hotfix" to apply, most will have the problem but wont address it as they simply reboot their system if it occurs and live with it.

I'm not going into depth regarding hardware conflicts and power management, here, purely because the fix I posted has fixed not just my PC under Vista & Win 7, but many others I've had come through my door here, after they have done hardware changes beyond the edge of reasoning, and their wallets !!!

Re the fire alarm analogy, if your fire alarm system is reporting false alarms you turn it off till its fixed.
Alarm rings !! you smell no smoke and look for a fire !! there is none .... there's no problem except with the software telling you there is.

You have to go back to fundamentals or you will spend too much time & money chasing a problem that's not really there.


Re ATI this regedit fixes that too obviously.


Its better to have a thread regarding the issue than none at all and bury your head in the sand.

Hopefully some discussion will appear here with fixes and tips, not just bashing others for trying to help.

[Feuerfalke]

Just because I'm Feuerfalke doesn't mean I bash you.

As I pointed out, the problem, the cause and the effects are numerous, so I got to admit I still have difficulties with just one "fix" that disables the alarm.

So I just wish you'd also posted the cons, too, and maybe alternatives that may help as well, without telling some people to edit the registry, who rather shouldn't


And then, as you criticize me for bashing somebody who's just helping with a selfless thread and keeps bashed by bad Feuerfalke:
Maybe it would have had a different touch if you 'd simply participated in one of the 10 already existing threads on this topic, discussing pros and cons, exchanging experiences and hardware-configs for almost a year now?

[KG26_Alpha]

Originally Posted by Feuerfalke

Just because I'm Feuerfalke doesn't mean I bash you.

As I pointed out, the problem, the cause and the effects are numerous, so I got to admit I still have difficulties with just one "fix" that disables the alarm.

So I just wish you'd also posted the cons, too, and maybe alternatives that may help as well, without telling some people to edit the registry, who rather shouldn't


And then, as you criticize me for bashing somebody who's just helping with a selfless thread and keeps bashed by bad Feuerfalke:
Maybe it would have had a different touch if you 'd simply participated in one of the 10 already existing threads on this topic, discussing pros and cons, exchanging experiences and hardware-configs for almost a year now?

Im sure you have the best intentions here but people are quite able to read the links I posted I hope you did too.

You need to read my original post instead of going off on one

Im not telling anyone to edit their registry, Microsoft are.


Bold text ref:

Not 10 but 2 re: nvlddmkm thats worth mentioning.

These are pure nvlddmkm issues the rest are nothing to do with it ..


http://forum.1cpublishing.eu/showthr...vlddmkm&page=2


http://forum.1cpublishing.eu/showthr...light=nvlddmkm

[Feuerfalke]

5 threads on the IL2-forum, 5 threads under Technical Problems and Solutions.

Makes 10 to my limited calculation abilities.


http://forum.1cpublishing.eu/search.php?searchid=497820


PS: Oh, there's 11 threads - one more in technical issues.

[KG26_Alpha]

Originally Posted by Feuerfalke

5 threads on the IL2-forum, 5 threads under Technical Problems and Solutions.

Makes 10 to my limited calculation abilities.


http://forum.1cpublishing.eu/search.php?searchid=497820


PS: Oh, there's 11 threads - one more in technical issues.

Again a lesson in reading is needed.

You didn't even read those threads did you ?

Only two contain information regarding nvlddmkm and I have replied to them already some time ago.

Edit:

Added Vista Service Pack 2 today soak testing now with MY registry TDR=0 removed.

[CZS_Ondras]

Greetings,

well I am really not an OS / HW expert, but this is my simple observation. I currently have:

------------------
System Information
------------------
Time of this report: 4/16/2009, 19:50:02
Machine name: SUPERAVIATORII
Operating System: Windows Vista™ Ultimate (6.0, Build 6001) Service Pack 1 (6001.vistasp1_gdr.090302-1506)
Language: Czech (Regional Setting: Czech)
System Manufacturer: ASUSTeK Computer INC.
System Model: P5N-T DELUXE
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (4 CPUs), ~2.4GHz
Memory: 4094MB RAM
Page File: 1797MB used, 6601MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 10
DX Setup Parameters: Not found
DxDiag Version: 6.00.6001.18000 64bit Unicode
---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 295
Manufacturer: NVIDIA
Chip type: GeForce GTX 295
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_05E0&SUBSYS_82DC1043&REV_A1
Display Memory: 2671 MB
Dedicated Memory: 879 MB
Shared Memory: 1791 MB
Current Mode: 1680 x 1050 (32 bit) (60Hz)
Monitor: Obecný monitor PnP
Driver Name: nvd3dumx.dll,nvd3dum,nvwgf2umx.dll,nvwgf2um
Driver Version: 7.15.0011.8250 (English)
DDI Version: 10
Driver Attributes: Final Retail
Driver Date/Size: 3/27/2009 10:03:00, 8635904 bytes
WHQL Logo'd: Yes

and before GTX295 I had 2x8800GTS512m (but this has no importance regarding this issue)

Until nvidia driver line 179.xx there were no problems for me, even SLI split screen mode worked like charm. Then the disaster came, but suddenly with 182.50 the problem is gone for me (well, SLI is unfortunately no show with il2 any more). What ever anybody says about who/what is the generator of this, my opinion is coming-up directly from my previous sentence.

O.

[Feuerfalke]

Originally Posted by KG26_Alpha

Again a lesson in reading is needed.

You didn't even read those threads did you ?

Only two contain information regarding nvlddmkm and I have replied to them already some time ago.

Edit:

Added Vista Service Pack 2 today soak testing now with MY registry TDR=0 removed.

I tested it too with my current setup (different Graphics Card and different CPU)

Plan:
-change the entries
-reboot
-test
-put in memory that caused the problem before
-test

Result:

After changing the entry and rebooting (without changing RAM) my Vista didn't start - bluescreen during boot. Had to recover from safe mode.

[KG26_Alpha]

I have removed Vista Service Pack 2

Its causing BSOD on my system.

This system has never BSOD'd on me.

Here's the lnk for the SP2 download.

http://www.microsoft.com/downloads/d...DisplayLang=en

[Thunderbolt56]

I've got a brand new build going live in less than a week. It was (and still is to an extent) to use Vista Home Premium x64 as my base OS. I also intended to have a dual-boot with XP Pro.

This issue has plagued a friend of mine from day one, but several others haven't had a single occurrence with almost identical machines. The randomness of it is what is perplexing for most and appears it will continue to be so. I heard/read that Vista SP2 (currently in beta) has fixed the problem for most, but can't relate as I'm still not running it yet nor have I experienced it.

I have a box of shiny new parts enough to put together a sweet new i7 rig replete with GTX285 OC, Raptors, 6GB Corsair Dominator, etc,.. If this error pops up, I'll certainly be disappointed.


TB

[Feuerfalke]

To my personal experience the error surfaced much less often with SP2 RCs. When it appeared I found that it did occur again and again, even on the desktop and when loading games until I switched of my PC completely (shut down, switch off PSU for 5 seconds)

Then it worked perfect again.


As you said, Thunderbolt56, it's random in itself and dependent on different factors. I sure hope you won't run into the same problem!


Maybe you can keep us up to date, once your nice rig runs the first games?