1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Eliminating setpoint32.exe error

Discussion in 'Windows 7' started by Davbla, 2014/07/21.

  1. 2014/07/21
    Davbla

    Davbla Well-Known Member Thread Starter

    Joined:
    2008/01/13
    Messages:
    12
    Likes Received:
    0
    I am getting frequent setpoint32 errors (cannot locate the specified device or file) which freeze the PC completely (everything appears to be fine but no software will open). This can generally be eliminated by rebooting 3 or 4 times. I have tried completely cleaning my registry, running a deep anti-virus (I use Vipre) and antimalwarebytes several times. but it is still happening. I know I could reinstall but I just do not have the time at the moment. No major event could have caused this and no new software. Something must be corrupted.

    Any ideas?
     
  2. 2014/07/21
    lj50 Lifetime Subscription

    lj50 SuperGeek WindowsBBS Team Member

    Joined:
    2003/07/04
    Messages:
    2,801
    Likes Received:
    137
    When was the last time you updated the drivers? Have you check the manufacturers website for the latest software version? Logitech makes a lot of products. Is this a mouse, a keyboard, etc.?
     
    Last edited: 2014/07/21
    lj50,
    #2

  3. to hide this advert.

  4. 2014/07/21
    Davbla

    Davbla Well-Known Member Thread Starter

    Joined:
    2008/01/13
    Messages:
    12
    Likes Received:
    0
    I have not tried updating the Logitech driver, but will. From what I have seen it is not related to the logitech drive but a system problem.
     
  5. 2014/07/21
    Davbla

    Davbla Well-Known Member Thread Starter

    Joined:
    2008/01/13
    Messages:
    12
    Likes Received:
    0
    Driver is up to date.
     
  6. 2014/07/21
    lj50 Lifetime Subscription

    lj50 SuperGeek WindowsBBS Team Member

    Joined:
    2003/07/04
    Messages:
    2,801
    Likes Received:
    137
    Open up Command Prompt and run as administrator. Once in command prompt type sfc /scannow then hit enter.
     
    lj50,
    #5
  7. 2014/07/21
    Davbla

    Davbla Well-Known Member Thread Starter

    Joined:
    2008/01/13
    Messages:
    12
    Likes Received:
    0
    Thanks for the trip. sfc did not report any repairs but reboot worked this time without the setpoint32 error. Fingers crossed!
     
  8. 2014/07/21
    lj50 Lifetime Subscription

    lj50 SuperGeek WindowsBBS Team Member

    Joined:
    2003/07/04
    Messages:
    2,801
    Likes Received:
    137
    Mine are crossed to. After a few days let us know if all is well.
     
    lj50,
    #7
  9. 2014/07/22
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,889
    Likes Received:
    386
    If so please mark your thread as Resolved ....

    Marking a thread as 'Resolved'

     
  10. 2014/07/22
    lj50 Lifetime Subscription

    lj50 SuperGeek WindowsBBS Team Member

    Joined:
    2003/07/04
    Messages:
    2,801
    Likes Received:
    137
    Thanks PeteC. I wasn't to sure if I was allowed to tell the original poster to mark a thread resolved. So I've always left that to the Windows BBS team, and/or Staff.
     
    lj50,
    #9
  11. 2014/07/22
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,889
    Likes Received:
    386
    If you have posted in a thread which has been resolved I see no problem in you suggesting to the OP that he/she marks the thread as Resolved.
     
  12. 2014/07/22
    lj50 Lifetime Subscription

    lj50 SuperGeek WindowsBBS Team Member

    Joined:
    2003/07/04
    Messages:
    2,801
    Likes Received:
    137
    Thanks.
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.