Windows XPPost your Windows XP related questions here.
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
On 7/21/2007, I changed the batteries and the channel on my wireless mouse. Since then, my computer periodically restarts by itself. I can only restart using Last Known Good Configuration. On restart, a Windows popup says that I have recovered from a serious error. The error report says I have a device driver problem but all my devices say that they are working properly. With IBM tech support (like pulling teeth even though I have 2 more years on my extended warranty), I installed the wireless mouse driver. My restart problem persists. My system will not let me use system restore. I ran a CheckIt diagnostics today which stated that all hardware passed. Thanks for replying.
Respun
Didn't find the information you thought to find? Check out these Similar Threads
Your system probably crashes, but is set to automatically reboot on crash, and that crash happens on a shutdown w/o you noticing.
Try unchecking the box in startup and recovery on your systems' property sheet in the control panel that states "Automatically restart" on System failure. Also while you are in there, change the write debugging information to full memory dump.
Both of these options should allow you to catch the error.
Also the event log may also report some information on your system error.
Here's what I found in my Event logs since my syndrome began last Saturday. Apologies if most (all) is irrelevant. I don't know how to sort the meaningful from the drivel:
I have several instances of the following events under Application:
Source Evnt Agnt:
1) ID 1015: “TraceLevel parameter not located in registry; Default trace level used is 32.”
2) ID 1003: “TraceFileName parameter not located in registry; Default trace file used is .” This latter is not a typo – that is actually how the description stops.
Source Userenv:
1) ID: 1524: “Windows cannot unload your classes registry file - it is still in use by other applications or services. The file will be unloaded when it is no longer in use.”
2) ID 1517: “Windows saved user [my name] registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.”
I have several instances of the following events under System:
Warning ID 2511: “The server service was unable to recreate the share Kazaa Media because the directory C:\Documents and Settings\[my name]\Start Menu\Programs\Kazaa Media Desktop no longer exists. Please run "net share Kazaa Media /delete" to delete the share, or recreate the directory C:\Documents and Settings\[my name]\Start Menu\Programs\Kazaa Media Desktop.” I “uninstalled Kazaa years ago; I don’t know how to implement this instruction.
Error, Source DCOM, ID 10005: “DCOM got error "The service did not respond to the start or control request in a timely fashion."attempting to start the service iPod Service with arguments "" in order to run the server:{063D34A4-BF84-4B8D-B699-E8CA06504DDE}.”
Error, Source: Service Control Manager, ID 7009: “Timeout (30000 milliseconds) waiting for the Application Layer Gateway Service service to connect.”
Error, Source: Service Control Manager, ID 7000: “The Application Layer Gateway Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.”
Error, Source: PlugPlayManager, ID 11: “The device Root\LEGACY_SSFS0509\0000 disappeared from the system without first being prepared for removal.
I just now retarted my system following removing old Java applications in Add/Remove programs. Again, I could only reboot using Last Known Good Configuration (I have not as yet unchecked "auto restart" on crash as I am waiting for further instructions on this option from Eric). Here is everything that showed up in the Event Viewer logs:
Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1524
Date: 7/28/2007
Time: 7:49:51 AM
Description: Windows cannot unload your classes registry file - it is still in use by other applications or services. The file will be unloaded when it is no longer in use.
Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: 7/28/2007
Time: 7:49:55 AM
Description: Windows saved user [my name] registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.
Event Type: Warning
Event Source: EvntAgnt
Event Category: None
Event ID: 1003
Date: 7/28/2007
Time: 7:52:28 AM
Description: TraceFileName parameter not located in registry; Default trace file used is .
Event Type: Warning
Event Source: EvntAgnt
Event Category: None
Event ID: 1015
Date: 7/28/2007
Time: 7:52:28 AM
Description: TraceLevel parameter not located in registry; Default trace level used is 32.
Event Type: Warning
Event Source: Server
Event Category: None
Event ID: 2511
Date: 7/28/2007
Time: 7:52:10 AM
Description: The server service was unable to recreate the share Kazaa Media because the directory C:\Documents and Settings\[my name]\Start Menu\Programs\Kazaa Media Desktop no longer exists. Please run "net share Kazaa Media /delete" to delete the share, or recreate the directory C:\Documents and Settings\[my name]\Start Menu\Programs\Kazaa Media Desktop.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 7/28/2007
Time: 7:52:25 AM
Description: The Webroot Spy Sweeper Engine service failed to start due to the following error: The system cannot find the file specified.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7009
Date: 7/28/2007
Time: 7:52:57 AM
Description: Timeout (30000 milliseconds) waiting for the IMAPI CD-Burning COM Service service to connect.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 7/28/2007
Time: 7:52:57 AM
Description: The IMAPI CD-Burning COM Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Since Kazaa was removed, click Start>Run, type cmd then hit enter to open a command window. Copy the following command, including quotations, and paste it to the command window, then hit enter.
"net share Kazaa Media /delete"
When Kazaa was installed, it set up a network share. When it was removed, the share entry was left behind while the actual share is gone (the directory) and Windows is still trying to connect to it, hence the error. The above will remove the entry.
By disabling autorestart, rather than rebooting on a crash, you should get a blue screen that contains information about the cause. Write down that information and post it back here. You will then have to hold the power button in until the computer shuts down.
Hmm. I tried to delete the Kazaa entry (copied and pasted the instruction into the command window, quotes and all). I got back that the system could not find the file path specified...
I will uncheck the auto restart box and see what happens!
Click Start>Run, type compmgmt.msc and hit enter. It should open the Computer Managment Console. In the left pane, under System Tools, expand Shared Folders, then click on Shares. See if Kazaa Media Desktop is in the list. If so, right click the entry and select 'Stop Sharing'.
I have fully entered the Twilight Zone. I unchecked auto restart on failure and then restarted. No crash. No Last Known Good Config. I don't expect this good news to last. I have received an auto AOL update this morning. Could that have been the fix? Doubtful.
As for Kazaa, I looked in Shares and it was not to be found. ???
The reason for Last Known Good coming up is the crashes themselves, which are caused by some event while within Windows. The crash prevents the regsitry hive from being properly unloaded and thus likely corrupted. That event in itself is noted and when you restart after a crash, Windows automatically wants to use the Last Known Good configuration, which is (hopefully and has been so far) a registry hive that is not corrupted. Disabling autorestart, as mentioned before, will cause a blue screen when the computer once again crashes. By initiating a reboot a short while ago rather than the machine crashing, you by-passed all of the behavior that you've been experiencing.
I'll have to do some looking around to further guide you towards resolution of Windows looking for the Kazaa share.
Thanks for the tutoring. And for looking for a Kazaa solution. I can add a couple of thoughts: 1) I have been reading similar problems for other AOL users -- these forums blame AOL software glitches and suggest calling AOL (now there's a nightmare); 2) three of my self-initiated reboots over the past few days have caused a normal restart -- all others have led to the dreaded Last Known Good Configuration scenario.
Hoping you and my internet connection will still be here when the next crash occurs!! Many thanks again.
Hey thanks again! I downloaded the KazaaBeGone. It found and removed 10 files. Any way that I can run a check to see whether there are still Kazaa remnants left?
Of course I'm still living in the AOL death world, but maybe my Kazaa days are fully cleaned from my system!
