BSOD nvlddmkm.sys error T510 Windows Server 2008 R2

hello Experts,

I am getting BSOD on lenovo T510 ( i7 M 620 Processor, 8 gb Ram).
the mesaage says nvlddmkm.sys error on BSOD.
The Laptop works fine .
I am trying to enable Hyper v on the Operating system.
In order to use it i have to enable virtualization and memory protection in Bios.

If i enable both virtualization and memory protection i get Bsod.
If i enable only one of them it works fine but do not solve the purpose
as i need to enable both in order for Hyper v to work.
I have attached the required files in attachment.
Please help!
I
Is Windows 2008 server R2 . . . - x86 (32-bit) or x64 ? 64 Bit - the original installed OS on the system? NO - an OEM or full retail version? Full Retail - What is the age of system (hardware)?
1.5 Year
- What is the age of OS installation (have you re-installed the OS?)
1.5 Year

Not the video driver but DirectX and I suspect that is being caused by your Symantec.

Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST


http://us.norton.com/support/kb/web_...080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows




Diagnosing basic problems with DirectX

I uninstalled symantec and installed the latest version of Direct X .
Still i see the BSOD..
Please Advice..

hello1211 said:

I uninstalled symantec and installed the latest version of Direct X .
Still i see the BSOD..
Please Advice..

We need the current DMP files. Please upload them.

hello1211 said:

I have attached the latest crash dump files ( Full test again)

Still the same BCC116 caused by DirectX. Do you have another video card you can try? Does it crash in safe mode?


http://windows.microsoft.com/en-US/w...s-with-DirectX

It does not crashes in safe mode.
It's a laptop .. can't try another card.
It has directX installed and it does not detect problem with dxdaig.
Please advice..

> Have you followed all of the instructions in the LINK in Post 6?

> Use a Laptop Cooling Pad and / or compressed air to follow the directions below in red.

> Please read this carefully...

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps Let us know if you need help

STOP 0x116: VIDEO_TDR_ERROR troubleshooting

I have now updated the Nvidia driver to 285.62 ( latest version) .
Now when i boot i get blank screen , it does not give me BSOD but the screen remain blank.

Yes, I have followed all the instructions in post 6 except "Move the Hardware Acceleration slider to Full."
I am not able to click change settings button ( as it is disabled ) .
When i boot in safe mode i can change it .. but it's already at Full ( in safe mode).
Also my laptop runs very cool . it does not heat at all.

After the driver update it just give blank screen. Please advice..

Suggest you boot into Safe Mode.

Start your computer in safe mode

Please check Event Viewer

1-Event viewer.

Type eventvwr in search and go to the windows log>application tab & system tabs.
Look for errors. Errors have red in the left hand column.

Look for errors that say app hang, or app crash, or anything related to the problem.
When you find them either take a screenshot of them and upload them to us, or note the event ID and source codes and look them up in google. If you cant find them in google tell us what they are.