NVCPL.DLL error.

I have recently applied about 2mths of maint to the Windows, switched from dial-up to DSL internet access, installed this years verson of TurboTax and updated CCleaner -- just to mention a few things that have happened lately.

Now I am incurring the following problem periodically when I bootup:

RUNDLL NVCPL.DLL The process cannot access the file because it is being used by another process.

I know this has something to do with nvidia - which is the extent of my knowledge. This problem does not seem to have any impact on the bootup or on anything I am doing. I do not consider it to be more than a nuisance but can anyone help me eliminate this problem?

Thanks, Wayne

 

Hi have you tryed this :

Nvcpl.dll Repair
Top Rated Nvcpl.dll Repair Tool. Free Download. 100% Guaranteed.
Fix-PC-Errors.com

Fix nvcpl.dll
Download nvcpl.dll Repair Tool. Free Download
www.Dll-Error-Repair.com

I seen it in the MajorGeeks Support Forums Advertisement Banner under your post.

 

Skippy, have you fixed the same type of error with one of these products and which one do you suggest?

 

HI, no sorry i have not had that problem on any of my computer before that i can remember but i thought i might post it as the MajorGeeks Support Forums Advertisement Banner under your post changers everytime you view the page so i thought i might suggest it incase you never got to see the add.

Hope them programs help, best of luck.

 

It is associated with the nVidia based graphics cards. You can disable it from starting "if you do not overclock".

Using CCleaner, go to Tools > Startup and disable it from starting when you start the computer.

Steve

 

Thanks for the input everyone. Last night I contacted Dell -- I let them remotely analyze my PC. I watched them do a start/run/msconfig/startup and uncheck NvCpl which right now seems to have eliminated the problem -- at least no problem thru 4 additional bootups.

The odd thing that I have found is found that the NvCpl item again has a check in the box when I revisted start/run/msconfig/startup this morning. I don't know if that will become a problem in the future -- I'll repost here again if the problem reappears.

They also had me run 'sfc /scannow' in Safe Mode with Networking -- I didn't see that that did anything.