BSOD error (Desperate)

[JayRod]

I've come to realize this problem doesnt exactly have to do with ETW anymore but this is where it started. Ever since I installed empire I've gotten random BSOD errors. At first I thought this was only on ETW and would be fixed with a patch but now I BSOD on every game I have about every 60 minutes or so.

The error is 0X00000116 and has something to do with display drivers. I've tried a google search and even managed to find a specific program to fix it but it only works with vista 32x and I have 64x. Some people have said it could be a corrupted file and the error itself tells me to remove any recently installed software or hardware. I'm finally uninstalling empire and not sure if this will actually fix it yet.

If anyone has had the error 0X00000116 before and knows a 64x solution please let me know. I have updated and downgrades drivers multiple times as well and its gotten me nowhere. Its getting very anoying to crash all the time. I'll appreciate any help I can get.

[SunofVich]

Please do not take this the wrong way, please don't think I am calling you stupid with this question.

Did you remove the old drivers before installing the new ones?

[yankeepyrate]

Have you turned off the automatic reboot windows does with BSODs, so you can read the screen? Or maybe Vista works different in regards to that than XP does, I don't know.
I was getting BSODs with ETW and it was involving dxg.sys, which is DirectX related. I'm still working to resolve the problem. I also pulled up the Event Viewer log and with the latest ETW crash, it was faulting Direct X as well.

[JayRod]

Yes I made sure to uninstall the old drivers before I installed the new ones. The error screen stays there until I turn off the computer and turn it back on.

The specific file thats causing the problem is nvlddmkm.sys

I have also tried manualy replacing this file in system32>drivers with the one in the driver folder and changing the extention so it works.

While researching this on google someone did say something about replacing it manually like that but when I do it doesnt recognize it so Im not sure.

[Bungus Holius]

check RAM stability. i had that issue with MTW2. swap RAM sticks or remove them gradually until the performance stabilizes. There are some RAM memory free ware programs that you can use to check RAM.

[Pent uP Rage]

A BSOD is a physical hardware failure. 0X00000116 is the memory address where the failure occurred.
As with all graphics based failures, you should uninstall and reinstall a fresh copy of an older driver that you KNOW works...in safe mode.

My research shows that your error may be caused by a driver error in Virtual Memory. If you have plenty o RAM (which since you're running Vista 64, you probably have plenty.) you can totally disable virtual memory.

BUT...if after trying all the software fixes and you STILL have the problem, it could be indicative of a physical hardware failure.

How good are ya w/ a multimeter?

[JayRod]

Thank you, I cant beleive I didnt think of that, trying old drivers in safe mode. Ill also try removing ram sticks to see if it works. I only have two, two GB sticks though so I dont think Ill want to leave it out since that would cut my ram in half.

If all else fails Ill just take it in to a computer store and I guess Ill have to trust them to fix it or replace the card.

Oh one more question, if I unistall drivers just simply by using the uninstal button when I go into device manager is that fine? Or should be downloading a program to uninstall drivers?

Edit: Oh yeah I also dont know what a multimeter is and I know how to change it but Im also not entirely sure what virtual memory does.