Solution
- Joined
- Oct 16, 2009
- Messages
- 15,152
Does it happen even if it is not being used?
You might try watching Task Manager to see if it shows some process taking CPU time when the chime occurs.
You might check the Event Viewer to see if any errors are showing up consistently.
Check and make sure all your connections are secure to any external devices? Any devices need a battery replaced?
You might try watching Task Manager to see if it shows some process taking CPU time when the chime occurs.
You might check the Event Viewer to see if any errors are showing up consistently.
Check and make sure all your connections are secure to any external devices? Any devices need a battery replaced?
- Joined
- Oct 16, 2009
- Messages
- 15,152
The Event Viewer may or may not help. Many times problems are accompanied by repeating errors that may describe the situation in a way that might help someone track it down. So in the Event Viewer, you go to the errors and see if anything is showing multiple instances of a problem and even check when they are occurring. If you double click the error, another page shows up that will give a two or three line description of what caused the error. The message may contain devices, or utilities or error codes that can be used.
If there are no errors that seem relevant, you might also check the warnings to see if anything there is showing up that could be related.
There have actually been a couple of times when I sent the info to Microsoft, they actually had a fix. I almost fell out of my chair!
Glad you found the problem.
If there are no errors that seem relevant, you might also check the warnings to see if anything there is showing up that could be related.
There have actually been a couple of times when I sent the info to Microsoft, they actually had a fix. I almost fell out of my chair!
Glad you found the problem.
paradive
Senior Member
- Joined
- Aug 23, 2010
- Messages
- 100
- Thread Author
- #5
The Event Viewer may or may not help. Many times problems are accompanied by repeating errors that may describe the situation in a way that might help someone track it down. So in the Event Viewer, you go to the errors and see if anything is showing multiple instances of a problem and even check when they are occurring. If you double click the error, another page shows up that will give a two or three line description of what caused the error. The message may contain devices, or utilities or error codes that can be used.
If there are no errors that seem relevant, you might also check the warnings to see if anything there is showing up that could be related.
There have actually been a couple of times when I sent the info to Microsoft, they actually had a fix. I almost fell out of my chair!
Glad you found the problem.
that's the problem. there is no "errors".