Re: Vista Update August 27 Nvidia nvlddmkm.sys BSOD

Driver updates are optional

"Smilerfive" <Smilerfive@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D38C2683-0FF2-459C-983D-5143C649C3D2@xxxxxxxxxxxxxxxx
I can confirm this is not a specific problem with Nvidia cards. I went out
and bought a new ATI graphics card because I could not afford to wait any
longer.

I immediately installed this card and my system immediately sprang into
life. And in the two hours it was working I managed to backup or otherwise
retrieve all my data.

The next I saw was a 'display driver stopped working' error in Vista, also
know as a TDR error, where timing between Vista and graphics card is lost
somehow. Basically this error appeared maybe 4 times then my system
crashed
again with the same error BSOD 116 but with the ATI driver file instaed of
the nvidia driver.

THIS IS A VISTA UPDATE problem where my system has been corrupted by a
wayward Vista Update. SOmehow this is killing graphics systems...

I hope they fix it soon.... Vista is becoming unusable



"realcestmoi" wrote:

Hi there,

If your hardware works fine: leave it be working fine and never take
driver
updates from windows update unless they are driver(s) for a microsoft
device, if not go to the manufacturers website that is IF an update is
NEEDED because the hardware is not working well.

Best regards,
Michel Denie

"Smilerfive" <Smilerfive@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D9983C7D-0FD5-450E-AC71-EBE074F1E994@xxxxxxxxxxxxxxxx
System: Windows Vista Ultimate fully updated, Intel E6600, Nvidia
7600GT,
4Gb Ram, one LCD VGA and one lcd via DVI etc, nothing is over clocked

Problem: I built this system 6 months ago and it has been running
perfectly
since. On August 27th my system tried to automatically update the
existing
Nvidia driver from Windows Update (groan, I know, I've changed it and
will
never let this happen again). My previous driver had been working
perfectly.
I was at work and came home, my system was unstable, I was getting
TDR's,
artefacts on screen and before I could really work out what was going
on
my
system crashed with BSOD on nvlddmkm.sys error 116.

Now it is in a loop. No matter what I do or what display drivers I try
Vista
always crashes on reboot with the same BSOD nvlddmkm.sys error 116.

With an Nvidia driver loaded I get a BSOD nvlddmkm.sys at boot with
error
116. Regardless of driver - 97.46, 100.64, 162.22, 162.44 etc

If I let my system update itself, ie with a Microsoft minimal driver,
it
boots but all I get displayed is a blank black screen with a mouse
cursor.
Microsoft Nvidia WDDM driver 25/01/2007 So it shows a mouse cursor that
actaully moves about but the desktop is not present, blank, black etc.

If I uninstall whatever driver is currently installed from safe mode,
removing all driver files, removing those in system32 and renaming
nvlddmkm.sys in system32/drivers, and then reboot, my system boots up
with
no
driver file loaded for the adaptor at all. This actually allows me to
boot
into Vista and gives me a desktop but clearly this means I have no
display
driver running and have no more than basic display functionality.

I really need help. My own view is Windows update partially installed a
driver or partially updated the driver that was on my system prior to
August
27th. Somehow it never completed that operation and my system has
residual
registry entries that point to incorrect driver files.

I have tried sweeping registry and I did find residual NVidia files but
they
were minimal and when I installed driver again I had the same
nvlddmkm.sts
BSOD error.

I have two monitors one a Sony 17" LCD VGA and an LG 22" DVI. They were
both
working fine prior but now they don't, obviously. I have seen messages
about
dual displays and the drivers/registry becoming confused. So I tried
various
configurations of monitor - VGA only, DVI only, connected to different
ports
etc. Each time same error BSOD nvlddmkm.sys 116.

It's now three weeks since this happened and my system is still
farquhared.
I need some serious help, I am way behind on some lucrative projects
and I
might pay for help to get this resolved. Help!!!








.

Relevant Pages

  • [Full-disclosure] Microsoft Windows Vista Slideshow Unspecified Blue Screen Of Death Vulnerabili
    ... It seems that Vista has some problems with ATI drivers. ... folder you get BSoD. ... this BSoD in atikmdag.sys (ATI Kernel Driver). ...
    (Full-Disclosure)
  • Re: Stops Working
    ... I have found Vista to be very sensitive to video driver problems. ... Sony Acid 4 is a very old version, so I thought I might have trouble with it. ... Word, IE, Windows Explorer and Sony music mixing software never quit while running under the XP operating system. ...
    (microsoft.public.windows.vista.performance_maintenance)
  • [VulnWatch] Microsoft Windows Vista Slideshow Unspecified Blue Screen Of Death Vulnerability
    ... It seems that Vista has some problems with ATI drivers. ... It was already reported that file atikmdag.sys can cause BSoD after leaving ... able to determine that there are more problems with this driver and Vista. ...
    (VulnWatch)
  • Re: Word 2007 has stopped working on Vista Home Premium
    ... Did MS get you to test in safe mode? ... I called HP and asked when they were going to have an HP driver out since I was missing features of the driver that worked with Xp. ... I don't remember if any of the Adobe products have had patched since they were installed, but there was a Vista patch for World Perfect X3. ... I probably earlier said it was worse when I tried to open a file first than using the shortcut icon on the desktop, but should have clarified that I normally use start/computer rather than than windows/e to open these files. ...
    (microsoft.public.word.application.errors)
  • Re: Vista X64 cant print to shared Vista X86
    ... Your name keeps popping up for solutions to Vista printing problems of the ... The 32 bit driver is most easily available from Vista 32 bit when using ... the client normally will install the inbox driver if the server ...
    (microsoft.public.windows.vista.print_fax_scan)