Warp2Search Forums: RUNDLL error in nvqtwk missing entry: nvcpldaemon - Warp2Search Forums

Jump to content

Sign In »
New user? Register Now! Help
  • Search section:
Advanced
  • Warp2Search
  • Forums
  • Members
  • Warp2Search Forums
  • > Graphics Cards & Drivers
  • > General Graphics Card Talk
  • View New Content
  • RSS Feed
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

RUNDLL error in nvqtwk missing entry: nvcpldaemon

#1 Guest_con_*

  • Group: Unregistered / Not Logged In

Posted 18 April 2002 - 08:12 PM

Every time I start my computer up it says RUNDLL error in nvqtwk missing entry: nvcpldaemon. It doesn't seem to affect anything but it gets real annoying. My specs are an Asus TUA266 motherboard, sound blaster live platinum, pentium3 866 133mhz bus, 256mb pc133 kingston ram, linksys 10/100 LAN card, visiontek geforce3 ti 200, windows ME. I'm wondering if its the video card driver because my old video card works problem free. I tried installing new drivers but still didn't help.
0
  • Back to top of the page up there ^

#2 Guest_mike_*

  • Group: Unregistered / Not Logged In

Posted 18 April 2002 - 11:33 PM

just go to msconfig and disable it in your start up menu. happens to me too with some of the drivers. no biggie. has no effect at all on your performance.
0
  • Back to top of the page up there ^

  • ← Previous Topic
  • General Graphics Card Talk
  • Next Topic →

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users

Delete Post

Remove From View

The post may still be visible to moderators in this topic

Reason:

Delete From Topic

The post will be removed from this topic completely


Skin and Language

Execution Stats

  • Time Now: May 24 2013 04:06 PM
  • Back to top
  • Forum Home
  • Delete My Cookies
  • Mark Board As Read

Community Forum Software by IP.Board

© 2007-2013 Esselbach Internet Solutions
All products mentioned are registered trademarks or trademarks of their respective owners.
Read our disclaimer over here and our Privacy Policy over here