Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

XP Pro, wireless optical mouse stuck...

Status
Not open for further replies.

naveedus6

MIS
Jul 16, 2006
25
US
Using XP Pro SP2 and logitech wireless keyboard and mouse, some time mouse cursor stuck, and i cant even use keyboard too, untill i restart computer, drivers are updates,

since 2-3 days i noticed when computer is in sleeping mode and i just touch key or mouse to wake computer up, the mouse is suddenly stuk. how can i fix this problem...?
 
Does your mouse or keyboard need batteries?

XP Pro asleep???
thread779-878041

Bizarre problem waking from sleep mode
thread779-945634

Is your bios up to date?

It wont hurt to check your Event Viewer to see if anything is mentioned there.

Some general things to try.

Run the System File Checker program from the Run Box by typing.....Sfc /Scannow in it and have your XP CD handy.

HOW TO: Verify Unsigned Device Drivers in Windows XP
 
Battreis are new in both.

Yes, Bios is up to date.

Event viewer... how can i get and save these info so i can post here..

i did Sfc /Scannow, after complete this, nothing showed up.

In Power Management tab i disable all power management, but problem is still teher.

Now i noticed that some time when i turn on computer it also stuck at blue screen with XP logo...

 
It is only Errors that are marked with a red X that are of concern. How many of these type of errors are you seeing, is there a common one being repeated?

Any errors logged in the Event Viewer can be expanded by double clicking on the error line.

Take any event error I.D. number and search for it on these sites.




Windows XP Stops Responding at the Welcome Screen

Have you checked your machine for malware?

Removing adware & spyware
faq608-4650

Try the free version of "Ewido"

Windows Defender


Maybe you could check the RAM too?

 
here are the even error

Type = Error
Date = 7/27/2006
Time = 9:13:56 AM
Source = DCOM
Categ = None
Event = 10016
User = Local Service

This error is 7 times continously and then randomly on different times

An other error is

Source = Service controle Manager
Event = 7000
User = Sysytem

One more Error

Source = DCOM
Event = 10010
User = Mike

But i noticed the first error event ID 10016 is so many times in event log
 
i checked RAM, and all test are okm bt the way i have 3 GB installed in tis PC
 
This is about 10016 and a quote from -
"PaulD (Last update 10/14/2004):
1. Open the registry and go to “HKEY_CLASSES_ROOT\CLSID\{<CLSID in the event message>} to find out friendly name of this component. In my case, this is "Machine Debug Manager” (CLSID: 0C0A3666-30C9-11D0-8F20-00805F2CD064).
2. Go to Component Services via Start -> Control Panel -> Administrative Tools -> Components Services. Expand the Component Services branch then expand “Computers”, “My Computer”, and “DCOM Config”. Right-click on "Machine Debug Manager" (or whatever your CLSID represents) and choose Properties. Click on the Security tab and under “Launch and Activation Permissions” select “Use Default”. Click OK, close the Component Services window. The error should disappear now."

There are other suggestions there.



Service Control Manager (7000).


Event ID: 10010
 
Thanks Linney.

i am at the point "DCOM Config" but i dont know what next as your "Machine Debug Manager", following the detail error, if u can find what i do next...


The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {BC866CF2-5486-41F7-B46B-9AA49CF3EBB1}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19). This security permission can be modified using the Component Services administrative tool.

For more information, see Help and Support Center at
 
PaulD above is using an example CLlSID that applied to his error. You should use the actual CLSID mentioned in your error, check it via the Registry to see what it applies to, then follow the example.


"Using Component ServicesWith Component Services, administrators can deploy and administer Component Services applications through a graphical user interface or automate administrative tasks by using a scripting or programming language. Software developers can use Component Services to visually configure routine component and application behavior, such as security and participation in transactions, and to integrate components into Component Services applications.

To open Component Services, click Start, point to Settings, and then click Control Panel. Double-click Administrative Tools, and then double-click Component Services.
For information about using Component Services, click Help in Component Services."



For what it is worth I am not sure all this has anything to do with your original posting but it might fix some of your Event Viewer errors.
 
I think you are WAY overcomplicating things. Try plugging into the USB port closest to your ethernet port. I have the same mouse/keyboard. I was having to press the "connect" button on both, until I realized my what-I-thought-were-new-batteries needed to be replaced.
 
here is new update...

after lot of tries the problem was still there so i decided to format and reinstall XP Pro again, then i did not install any programme and it was working fine till yesterday, i installed SP2 and all updates, as soon as i installed updates, and reboot the pc it again start giving me same problem, it stuck at very start (before welcome screen) when blue screen with xp logo and scrolling bar appears.

i am sure there is problem with some update, i dont know which one and how to fix this.
 


The last link includes removal instructions for SP2, but as you also have multiple updates that have been added you may be able to make use of System Restore and all the restore points each update created to step back in time, perhaps going back 10 updates at a time then checking for problems. If you go back too far and want to come forward you will have "undo" facilities for each restore point you returned to.

Otherwise it may be something like this that has to be done.

uninstall SP2 and all the updates and recheck for the problem.

Re-install SP2 and check for the problem.

Re-install each update one at a time, check for the problem after each update.

What a chore, but it may be the only way?




Perhaps there's something in this thread?

Anyone know which order drivers are loaded in?
thread779-1180345

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top