Norton Systemworks caused big problems...

Hi all

I'm new here, so please go easy on me!

A couple of days ago I needed to renew my subscription to Norton AntiVirus 2005 live update service. Whilst I was doing so I noticed there was a good deal to upgrade to Norton Internet Security + free Systemworks, so decided to do that.

I then installed it, ran a couple of the Systemworks tools (Tidy up & disk doctor).

Ever since, it is SO slow! It's a relatively new VAIO laptop, with a dual core processor and 1Gb of RAM, so used to be really quick - from turn on to Windows sign-in screen was probably 15 seconds max, and is now about 3 minutes; from sign-in to Windows launch was about another 10 seconds, and is now only just under an additional 3 minutes!

Having used Norton anti-virus products for years with zero problems I just presumed all would be well, and didn't do the usual web trawling for problems that I usually do before installing something new. However, now this has happened there seems to be lots on Systemworks screwing up XP, in many cases wiping out HDDs completely, and everyone says it takes ages to uninstall, doesn't completely disappear, and causes further problems. So now I'm panicking!

I tried doing a Windows System Restore - but it seems to have wiped out all the system restore points from before Systemworks was installed!!

Unfortunatley in all the stuff I can find about the problem online, there is no solution anywhere as for what I should do. I know computers pretty well, but not enough to understand much about registries and so on. I desperately need help!! I'm panicking as I'm currently at my boyfriends and as such don't have access to an external HDD to backup my files, and I'm scared I'm about to lose my HDD. All the accounts online of similar problems say Norton don't have a solution.

Can anyone please help me?!! Thankyou so much in advance for any advice, I will really, really appreciate it...

 

Hi, Steelercaz13. Welcome to Windows BBS!

I'm sorry I don't have enoough experience with Symantec/Norton to feel confident about offering suggestions regarding uninstalling. I have heard that Symantec products tend to be resource hogs. Perhaps you can configure your Norton Internet Security (NIS) and/or Norton SystemWorks (NSW) to use only the features you want so your system resources used by NIS and NSW are minimized.

You can start investigating your issue with Event Viewer to see if that may shed some light on your problem.

• Click Start.
• Right-click "My Computer ".
• Click "Manage ".
• Select "Event Viewer ".
• Double-click your "Application" log and "System" log for events with red circles with an "X" in them. The events are listed in reverse-chronological order (top event is most recent).
• Double-click on one of those error events (or right-click and select "Properties ") for a Properties window that will display details about the event error.
• Click the button below the up/down arrow buttons in the Properties window to copy the contents of the error details to your clipboard.
  (You can use the up/down arrow buttons in the Properties window to move your focus to different events in the list.)
• Paste your clipboard contents into a message for each different error event (preferably in chronological order - lowest in the list to highest) that has occurred since you installed NIS and NSW.

Those error event details (if you have any) might give people viewing your thread some ideas of how to proceed.

 

Ok, gone through the System & Applications log, and copied all the errors into a Word doc... and it's 11 pages long since Norton was installed!! Have also added the 'Warning' entries as well as the 'Error' messages, since before Norton I barely seemed to have had any ever.

All details copied below, in the order you recommended, with the Applications Log first, then the System Log:

APPLICATION LOG

Event Type: Error
Event Source: Norton Disk Doctor
Event Category: None
Event ID: 1000
Date: 01/09/2006
Time: 00:15:01
User: N/A
Computer: VAIOLAPTOP
Description:
The description for Event ID ( 1000 ) in Source ( Norton Disk Doctor ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Norton Disk Doctor - Testing Drive C:
Norton Disk Doctor found problems with the file system.
Run Norton Disk Doctor and check the Fix Errors option.
.
-----

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 01/09/2006
Time: 00:34:16
User: N/A
Computer: VAIOLAPTOP
Description:
Faulting application epmwor~1.exe, version 1.2.0.1093, faulting module ntdll.dll, version 5.1.2600.2180, fault address 0x00011e58.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 65 70 6d ure epm
0018: 77 6f 72 7e 31 2e 65 78 wor~1.ex
0020: 65 20 31 2e 32 2e 30 2e e 1.2.0.
0028: 31 30 39 33 20 69 6e 20 1093 in
0030: 6e 74 64 6c 6c 2e 64 6c ntdll.dl
0038: 6c 20 35 2e 31 2e 32 36 l 5.1.26
0040: 30 30 2e 32 31 38 30 20 00.2180
0048: 61 74 20 6f 66 66 73 65 at offse
0050: 74 20 30 30 30 31 31 65 t 00011e
0058: 35 38 0d 0a 58..

-----

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 01/09/2006
Time: 00:44:46
User: N/A
Computer: VAIOLAPTOP
Description:
Faulting application epmwor~1.exe, version 1.2.0.1093, faulting module epmwor~1.exe, version 1.2.0.1093, fault address 0x000086d5.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 65 70 6d ure epm
0018: 77 6f 72 7e 31 2e 65 78 wor~1.ex
0020: 65 20 31 2e 32 2e 30 2e e 1.2.0.
0028: 31 30 39 33 20 69 6e 20 1093 in
0030: 65 70 6d 77 6f 72 7e 31 epmwor~1
0038: 2e 65 78 65 20 31 2e 32 .exe 1.2
0040: 2e 30 2e 31 30 39 33 20 .0.1093
0048: 61 74 20 6f 66 66 73 65 at offse
0050: 74 20 30 30 30 30 38 36 t 000086
0058: 64 35 0d 0a d5..

-----

Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1524
Date: 01/09/2006
Time: 02:42:20
User: VAIOLAPTOP\Angel
Computer: VAIOLAPTOP
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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-----

Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: 01/09/2006
Time: 02:42:22
User: NT AUTHORITY\SYSTEM
Computer: VAIOLAPTOP
Description:
Windows saved user VAIOLAPTOP\Angel 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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-----

Event Type: Warning
Event Source: MSSQL$VAIO_VEDB
Event Category: (8)
Event ID: 19011
Date: 01/09/2006
Time: 11:58:17
User: N/A
Computer: VAIOLAPTOP
Description:
The description for Event ID ( 19011 ) in Source ( MSSQL$VAIO_VEDB ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: (SpnRegister) : Error 1355.

-----

Event Type: Warning
Event Source: MSSQL$VAIO_VEDB
Event Category: (8)
Event ID: 19011
Date: 02/09/2006
Time: 20:41:49
User: N/A
Computer: VAIOLAPTOP
Description:
The description for Event ID ( 19011 ) in Source ( MSSQL$VAIO_VEDB ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: (SpnRegister) : Error 1355.


SYSTEMS LOG

Event Type: Error
Event Source: sr
Event Category: None
Event ID: 1
Date: 31/08/2006
Time: 23:29:21
User: N/A
Computer: VAIOLAPTOP
Description:
The System Restore filter encountered the unexpected error '0xC0000034' while processing the file 'Education .. Record.LNK' on the volume 'HarddiskVolume2'. It has stopped monitoring the volume.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 06 00 00 00 04 00 4e 00 ......N.
0008: 00 00 00 00 01 00 00 c0 .......À
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

-----

Event Type: Error
Event Source: MRxSmb
Event Category: None
Event ID: 8003
Date: 31/08/2006
Time: 23:44:23
User: N/A
Computer: VAIOLAPTOP
Description:
The master browser has received a server announcement from the computer JLF-HOMEPC that believes that it is the master browser for the domain on transport NetBT_Tcpip_{43C4EB3C-97A1-40D. The master browser is stopping or an election is being forced.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 03 00 4e 00 ......N.
0008: 00 00 00 00 43 1f 00 c0 ....C..À
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

-----

Event Type: Warning
Event Source: PlugPlayManager
Event Category: None
Event ID: 256
Date: 01/09/2006
Time: 00:34:09
User: N/A
Computer: VAIOLAPTOP
Description:
Timed out sending notification of device interface change to window of "ModemDeviceChange "

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-----

Event Type: Warning
Event Source: PlugPlayManager
Event Category: None
Event ID: 256
Date: 01/09/2006
Time: 00:34:10
User: N/A
Computer: VAIOLAPTOP
Description:
Timed out sending notification of device interface change to window of "ModemDeviceChange "

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-----

Event Type: Warning
Event Source: PlugPlayManager
Event Category: None
Event ID: 256
Date: 01/09/2006
Time: 00:34:27
User: N/A
Computer: VAIOLAPTOP
Description:
Timed out sending notification of device interface change to window of "ModemDeviceChange "

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-----

Event Type: Error
Event Source: MRxSmb
Event Category: None
Event ID: 8003
Date: 01/09/2006
Time: 12:13:54
User: N/A
Computer: VAIOLAPTOP
Description:
The master browser has received a server announcement from the computer JLF-HOMEPC that believes that it is the master browser for the domain on transport NetBT_Tcpip_{43C4EB3C-97A1-40D. The master browser is stopping or an election is being forced.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 03 00 4e 00 ......N.
0008: 00 00 00 00 43 1f 00 c0 ....C..À
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

-----

Event Type: Error
Event Source: Dhcp
Event Category: None
Event ID: 1002
Date: 01/09/2006
Time: 22:46:23
User: N/A
Computer: VAIOLAPTOP
Description:
The IP address lease 192.168.2.2 for the Network Card with network address 0013021DC2C5 has been denied by the DHCP server 192.168.1.1 (The DHCP Server sent a DHCPNACK message).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-----

Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 17
Date: 01/09/2006
Time: 22:46:48
User: N/A
Computer: VAIOLAPTOP
Description:
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time.windows.com,0x1'. NtpClient will try the DNS lookup again in 15 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-----

Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 01/09/2006
Time: 22:46:48
User: N/A
Computer: VAIOLAPTOP
Description:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 14 minutes. NtpClient has no source of accurate time.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-----

Event Type: Warning
Event Source: Dhcp
Event Category: None
Event ID: 1003
Date: 02/09/2006
Time: 18:27:53
User: N/A
Computer: VAIOLAPTOP
Description:
Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 0013021DC2C5. The following error occurred:
An operation was attempted on something that is not a socket. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 36 27 00 00 6'..

-----

Event Type: Error
Event Source: Dhcp
Event Category: None
Event ID: 1002
Date: 02/09/2006
Time: 18:28:12
User: N/A
Computer: VAIOLAPTOP
Description:
The IP address lease 192.168.1.65 for the Network Card with network address 0013021DC2C5 has been denied by the DHCP server 192.168.2.1 (The DHCP Server sent a DHCPNACK message).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-----

Event Type: Error
Event Source: ACPIEC
Event Category: None
Event ID: 1
Date: 02/09/2006
Time: 18:28:39
User: N/A
Computer: VAIOLAPTOP
Description:
\Device\ACPIEC: The embedded controller (EC) hardware didn't respond within the timeout period. This may indicate an error in the EC hardware or firmware, or possibly a poorly designed BIOS which accesses the EC in an unsafe manner. The EC driver will retry the failed transaction if possible.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 68 00 01 00 be 00 ..h...¾.
0008: 00 00 00 00 01 00 05 c0 .......À
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 99 9e 36 00 13 19 ff ff â„¢ž6...ÿÿ
0030: 73 00 09 00 13 0a 1b 00 s.......
0038: 83 00 c9 01 a3 09 a3 06 Æ’.É.£.£.
0040: 13 0a 2f 00 33 82 09 00 ../.3‚..
0048: 15 08 18 00 10 08 66 00 ......f.
0050: 60 00 0a 00 90 01 29 c1 `....)Ã
0058: 70 00 14 00 10 1a 1d 00 p.......
0060: 80 00 13 00 30 83 0d 00 €...0Æ’..
0068: 15 10 13 00 21 80 13 00 ....!€..
0070: 11 11 e6 00 a1 02 df 00 ..æ.¡.ß.
0078: 11 10 23 05 a1 13 6b 26 ..#.¡.k&
0080: 11 12 30 00 41 01 09 00 ..0.A...
0088: 16 18 b0 03 a6 0f 03 16 ..°.¦...

-----

Event Type: Error
Event Source: MRxSmb
Event Category: None
Event ID: 8003
Date: 02/09/2006
Time: 18:37:21
User: N/A
Computer: VAIOLAPTOP
Description:
The master browser has received a server announcement from the computer JLF-HOMEPC that believes that it is the master browser for the domain on transport NetBT_Tcpip_{43C4EB3C-97A1-40D. The master browser is stopping or an election is being forced.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 03 00 4e 00 ......N.
0008: 00 00 00 00 43 1f 00 c0 ....C..À
0010: 00 00 00 00 00 00 00 00 ........
0018: 01 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

-----

Event Type: Error
Event Source: MRxSmb
Event Category: None
Event ID: 8003
Date: 02/09/2006
Time: 19:37:22
User: N/A
Computer: VAIOLAPTOP
Description:
The master browser has received a server announcement from the computer JLF-HOMEPC that believes that it is the master browser for the domain on transport NetBT_Tcpip_{43C4EB3C-97A1-40D. The master browser is stopping or an election is being forced.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 03 00 4e 00 ......N.
0008: 00 00 00 00 43 1f 00 c0 ....C..À
0010: 00 00 00 00 00 00 00 00 ........
0018: 02 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

-----

Event Type: Error
Event Source: MRxSmb
Event Category: None
Event ID: 8003
Date: 02/09/2006
Time: 20:49:16
User: N/A
Computer: VAIOLAPTOP
Description:
The master browser has received a server announcement from the computer JLF-HOMEPC that believes that it is the master browser for the domain on transport NetBT_Tcpip_{43C4EB3C-97A1-40D. The master browser is stopping or an election is being forced.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 03 00 4e 00 ......N.
0008: 00 00 00 00 43 1f 00 c0 ....C..À
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

-----

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 02/09/2006
Time: 21:51:26
User: N/A
Computer: VAIOLAPTOP
Description:
Error code 1000008e, parameter1 c0000047, parameter2 804fcd08, parameter3 b65f6344, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 34 37 2c 20 000047,
0038: 38 30 34 66 63 64 30 38 804fcd08
0040: 2c 20 62 36 35 66 36 33 , b65f63
0048: 34 34 2c 20 30 30 30 30 44, 0000
0050: 30 30 30 30 0000

-----

Event Type: Error
Event Source: MRxSmb
Event Category: None
Event ID: 8003
Date: 02/09/2006
Time: 22:25:15
User: N/A
Computer: VAIOLAPTOP
Description:
The master browser has received a server announcement from the computer JLF-HOMEPC that believes that it is the master browser for the domain on transport NetBT_Tcpip_{43C4EB3C-97A1-40D. The master browser is stopping or an election is being forced.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 03 00 4e 00 ......N.
0008: 00 00 00 00 43 1f 00 c0 ....C..À
0010: 00 00 00 00 00 00 00 00 ........
0018: 01 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

-----

Event Type: Error
Event Source: MRxSmb
Event Category: None
Event ID: 8003
Date: 02/09/2006
Time: 23:37:12
User: N/A
Computer: VAIOLAPTOP
Description:
The master browser has received a server announcement from the computer JLF-HOMEPC that believes that it is the master browser for the domain on transport NetBT_Tcpip_{43C4EB3C-97A1-40D. The master browser is stopping or an election is being forced.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 03 00 4e 00 ......N.
0008: 00 00 00 00 43 1f 00 c0 ....C..À
0010: 00 00 00 00 00 00 00 00 ........
0018: 02 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........


THAT'S THE LOT!

 

EDIT: I just saw your errors AFTER posting this message. You may want to wait for comments from others before considering my suggestions below.

DISCLAIMER: The following suggestions are what I would do. However, your results may differ from mine.
Proceed at your own risk.

FWIW, I currently use NSW 2006 (but not NIS) and my system runs pretty smoothly. It might just be a matter of tweaking your NIS/NSW installation so your system performs better.

I think NSW does put a lot of entries into your registry. Maybe during your first boot after you installed, your system spent a lot of time reading the newly modified (enlarged) registry, updating its records, and making extra copies of it's newly modified registry. Perhaps after another reboot or two things will settle down and your system will speed up.

If you decide to keep NIS and NSW installed for awhile, you might want to try running NSW's LiveUpdate to be sure your NIS/NSW has all available updates. I sometimes have had to run Live Update more than once (even if it says it is updated after the first run) to get even more updates. (I have no clue why though.)

After you have made certain you have updated your MSW/NIS installation completely, then you might want to reboot. After rebooting you might want to run NSW's "Norton WinDoctor" to have it look for "problems ". I have used NSW's Norton WinDoctor on numerous occasions with no problems. Sometimes WinDoctor has fount a LOT of things to fix on my machine.

NSW's Norton WinDoctor can be accessed as follows:
Start > All Programs > Norton SystemWorks > Norton Utilities > Norton WinDoctor

Norton WinDoctor keeps a history of things it "fixed" so you can undo them later if you want. When you are at Norton WinDoctor's main menu (i.e., after having it fix problems), you can set how long you want WinDoctor to keep records of the changes it makes. (I have mine set to "Forever ".) Access that setting in WinDoctor via View > Options > Repair History tab.

 

Steelercaz13,

Good work on pasting those error descriptions! Notice each error has an "Event ID ". These Event IDs are also displayed in the Event Viewer lists.

I suggest looking back further in your Event Viewer logs to identify which of those particular Event IDs also occurred BEFORE you installed NIS and NSW.
Perhaps you can help narrow down the source of the NIS/NSW-related problem(s) by identifying which "new" Event IDs occurred after installing NIS/NSW and giving us a list of those "new" Event IDs. (To save space in this thread, list just the NEW "after NIS/NSW installation" Event IDs rather than the complete descriptions above.)

After posting, the "new" event IDs. There are some additional things you can do.

While you're waiting for suggestions from others who may be familiar with some of your Event Viewer "Event ID" errors (which does not include me ), you may want to go back to the Properties window for each of those events and click on the http://go.microsoft.com/fwlink/events.asp link provided in the Properties window for more details from Microsoft about the particular Event ID. Those Microsoft details might offer some insight on how to fix those problems.

These things may or may not be helpful but at least they're things you can do instead of feeling "helpless" as I suspect you might feel.

Hang in there!

 

Right, checked down the whole thing, and:

APPLICATIONS LOG
I've had both the 1000 error code before, but for a different program:
This is the error msg for one with 'Norton System Doctor' beside the error number -
Event Type: Error
Event Source: Norton Disk Doctor
Event Category: None
Event ID: 1000
Date: 01/09/2006
Time: 00:15:01
User: N/A
Computer: VAIOLAPTOP
Description:
The description for Event ID ( 1000 ) in Source ( Norton Disk Doctor ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Norton Disk Doctor - Testing Drive C:
Norton Disk Doctor found problems with the file system.
Run Norton Disk Doctor and check the Fix Errors option..

Yet here is one from a couple of months ago, with the same code (1000), but a differnet program, though it doesn't specify which one -
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 19/06/2006
Time: 23:32:51
User: N/A
Computer: VAIOLAPTOP
Description:
Faulting application CF_Client_Installer.exe, version 0.0.0.0, faulting module CF_Client_Installer.exe, version 0.0.0.0, fault address 0x0003fb80.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 43 46 5f ure CF_
0018: 43 6c 69 65 6e 74 5f 49 Client_I
0020: 6e 73 74 61 6c 6c 65 72 nstaller
0028: 2e 65 78 65 20 30 2e 30 .exe 0.0
0030: 2e 30 2e 30 20 69 6e 20 .0.0 in
0038: 43 46 5f 43 6c 69 65 6e CF_Clien
0040: 74 5f 49 6e 73 74 61 6c t_Instal
0048: 6c 65 72 2e 65 78 65 20 ler.exe
0050: 30 2e 30 2e 30 2e 30 20 0.0.0.0
0058: 61 74 20 6f 66 66 73 65 at offse
0060: 74 20 30 30 30 33 66 62 t 0003fb
0068: 38 30 80

Confused! But anyway... Yes, the answer is I've had the error code before, but seemingly in a differnet context.

On the warnings front, the codes were 1524, 1517 & 19011 - I have each of these several times going right back to when I got my laptop a few months ago.

SYSTEMS LOG:

The error codes listed here were 1, 17, 29, 1002, 1003 & 8003. Looking back, I have experienced 8003 lots of times, and all the others once or twice. However, again, they are often the same event ID but with a different message, for example code '1' has a kind of message since Norton, but 2 different paragraphs of text with previous error events.

Sorry if that's redundant information or I'm pointing out the obvious!!

On the warnings side, there was 256 & 1003. Both appear to have occurred pre-Norton, going right back a couple of months to the start.


Should there be this many errors? And why are there no unique onces since the Norton install & subsequent problems?!! And I'm SO cross it's wiped out all my System Restore points... I always thought that was your safeguard against stuff like this!

Really appreciating the help, thankyou!

 

PS - forgot to mention previously, other problems since installing it:

1) Won't turn itself off when been idle for the determined period. Used to go to screensaver, then hibernate. Now it goes screensaver, then a blue screen with lots of error messages on it, then back to the Windows sign-in page, then screensaver again, and so on, and

2) It had some issue with my IE Explorer home pages (I have the new one with tabbed browsing), unfortunately I didn't make a note of the window that came up to explain - I clicked 'fix', and when I now open IE there's my 4 usual homepages plus a blank page as the active tab. Odd!

 

Steelercaz13,

As I suspected, many of the Event Viewer errors were occurring before you installed NIS and NSW so I wouldn't be too quick to blame Norton. It looks to me like there are other system issues you may need to take care of before tackling the "after NIS/NSW install slowdown" issue.

One of those events appears to be a system crash when your system abruptly shut down and presented you with a "Blue Screen of Death" (BSOD) or it automatically rebooted (depending on how your system is configured). That event was:

Down the road (even now, if you want), you might want to follow the directions in this link regarding that crash. Your DebugWiz-generated crash dump analysis might be helpful in pinpointing the cause of that crash.

I am fairly confident that creating a DebugWiz-generated crash dump analysis for your Date: 02/09/2006 Time: 21:51:26 crash can be done without risk to your system.

EDIT: While I don't claim to be an expert regarding BSOD dump analysis, this 4-page article, Network World: "How to solve Windows system crashes in minutes" (specifically the last paragraph of page 3 and all of page 4) might be very helpful to you.

The first 3 pages of that Network World article are basically taken care of by following the directions I linked above.

========

Back to your "after NIS/NSW install" issues...

Does your system STILL take such a long time to boot?

========

Is your system fairly responsive AFTER your system has finished booting?

If so, I would be inclined to run Norton Disk Doctor (located in the "Norton Utilities" section of NSW) as your first error event description indicates:

Again, my disclaimer: Proceed at your own risk.

With that disclaimer in mind...I have not had trouble with recent versions of NSW. In all fairness to Norton/Symantec, the only time I had trouble with NSW was in the old days with Windows 98 (and earlier Windows versions) and I tinkered with things I had no business tinkering with. Since I installed Windows XP and newer versions of NSW since then, I have had good luck with NSW.

I am guessing Norton was checking your drive C: for errors when you booted and that is why it took so long to boot.

If you decide to forge ahead and run Norton Disk Doctor, you might want to reboot and then run Norton WinDoctor and then reboot again.

Perhaps that will decrease the time it takes your system to boot.


Since this is a holiday weekend in the USA, you might not get any advice from experts for a few days. PeteC is in the UK though so he might be around to offer suggestions in several hours (after he wakes up, I assume). Pete often shows up around 3AM-4AM Eastern Time. He knows a LOT more about troubleshooting Windows XP than me and he's a good guy.

Please let us know how you (want to) proceed (or not) and what you observe if you do proceed with any of my suggestions (at your own risk).

========

Thanks for posting that info. It might be helpful for people viewing this thread. I'm sorry I have no idea right now about #1. In regards to #2, I think you mean you have IE version 7. If so, there is a Windows Update (or Microsoft Update if you use it) patch for IE7 that's supposed to address an issue with IE7. I don't know if that patch would fix your IE7 issue. Click on the "Custom" button at the Windows Update (or Microsoft Update) page and then select the "Software, Optional" link in the menu. The one that relates to IE7 is "Update for Windows XP (KB904942) ":

I don't use IE7 so I'm sorry I don't have any other suggestions about that either...except...

I suggest starting a thread in the Internet Explorer / Outlook Express forum regarding your particular issue with IE. Someone there that is familiar with your particular version of IE might have some helpful suggestions.

 

I understand your frustration. I also have had System Restore fail on me before (in one way or another) and had to bail myself out via a different route. While System Restore seems to work well in many situations, we cannot rely on it to rescue us from all problems that occur (as you have discovered).

I did some Googling on your 8003 events: "The master browser has received a server announcement from the computer" "that believes that it is the master browser for the domain on transport " and dug up http://www.windowsitpro.com/Windows/Articles/ArticleID/3870/pg/4/4.html (dated October 1998, regarding Windows NT) where "Dr. Bob" states,

He goes on to suggest how to fix it but he also says,

Therefore, I wouldn't be too concerned about your 8003 errors, at least for now anyway. I suspect the other errors regarding DHCP and W32Time can also be ignored for now as well.

Here's a link that might be helpful for this event:
http://www.eventid.net/display.asp?eventid=1&eventno=3767&source=ACPIEC&phase=1

I suspect this error may be what trashed your System Restore Points. I would also venture to guess that NSW's Norton WinDoctor will flag a problem with 'Education .. Record.LNK' and propose to fix it.

Here's a Microsoft Knowledgebase article link that might be helpful:

• How to troubleshoot the System Restore tool in Windows XP

I'll stop posting so you and others can try to digest this information without me possibly adding to confusion and chaos.

Good luck!

 

Hello Steelercaz13 and welcome to the Board

NIS contains a firewall - what firewall were you running before and is that uninstalled?

I'm not familiar with these two tools, do they backup what they change? Look around in the their Help and in the options.

Check to see if GoBack was part of the package - that would shut SR down.

Regards - Charles

 

Hi, Charles. Thanks for jumping in.

THERE is a thought that slipped my mind. Norton GoBack might also be a reason Steelercaz's boot-up took so long too. I have had GoBack's automatic startup disabled for a long time and I have System Restore enabled. (I don't recall my reason for certain though.) I think there is an option in Norton GoBack to disable it from automatically running at startup.

Even after disabling GoBack's automatic startup, as I recall, I still had to deactivate the persistent GBTray.exe system tray icon by using Mike Lin's Startup Control Panel.

 

First off, thankyou Mailman for all your wonderful help and suggestions so far!

Um, not sure... I had Norton AntiVirus 2005 installed before, and just installed the Norton Internet Security 2006 + Systemworks over the top - the installation instructions said that was no need to uninstall previous versions. Could this be what has caused my problems?

Hmm, taken a peek, and here's what I know:

-By 'Tidy Up', I meant "Norton Cleanup ", of which I think I did the 'Express' version. In the 'bumf' it says it quickly finds & deletes unwanted cookies, history, cache & temporary files that your PC picks up during web browsing & other activities. It seems to be permanent...

- "Disk Doctor" says it diagnoses & fixes problems with disks. In it's help file it says:
"Norton WinDoctor diagnoses and repairs the most common types of Windows problems. You can tailor the repair process to your own needs by selecting which tests to run and which problems to fix.
Norton WinDoctor does the following:
- Inspects everything that's required for Windows to run properly, and keeps Windows running at peak efficiency.
- Checks for components that are needed by the programs that you run in Windows.
- Displays an easy-to-read report that lists the problems that it found, the problems that it fixed, and the severity of each problem.
- Lets you tailor the repair process. You can specify which problems to fix and how to fix them. You can also choose to fix all of the found problems automatically and let Norton WinDoctor take care of everything.
- Run Norton WinDoctor when you receive a Windows problem alert, or run it regularly to keep your Windows operating system free of accumulated errors. "

It seems it may be reversible - "Norton WinDoctor always asks you to confirm before it makes a repair. Even with this extra safeguard, you may sometimes want to undo a repair. With Norton WinDoctor, not only can you undo a repair you just made, but you can also undo a repair you made yesterday or even last week.

The Repair History tracks the changes that Norton WinDoctor makes to your system. You can configure how long to keep repairs, or how many Repair History items to retain, in the WinDoctor Options dialog box.
To undo repairs made by Norton WinDoctor:
- Click View Repair History, and then undo changes.
- Click Finish.
- Click a previously completed repair to select it.
- On the toolbar, click Undo. "

Unfortunately I cannot find anywhere that says "View Repair History "!! There is certainly nothing in the utility itself, and I can't see it anywhere else.

Yes, GoBack is part of the package. Should I therefore disable System Restore? (Whatever happened wiped my previous restore points, which I think is terrible, but they've been working since)


I'm so confused as to what to do!!

Thanks for everyone's help, I very much need it...

 

Just wondering how often counts as too often? Since installed Norton (sometime late on 1st September) I seem to have had the 8003 error 16 times. Earlier today (3rd September) I have had 10, my laptop has been on most of the day.


Ooh, also, RE previous comments, my boot-up is not getting any faster. I have resorted to just forcing hibernations by closing the lid... Even waking up from these is taking at least 4 minutes, compared to the previous seconds

 

You're very welcome. Assisting you is my pleasure.

[EDIT: Someone moved this thread to the "Other Software" forum since your primary issue seems to be NIS/NSW-related.)

I proposed a possible solution to your lengthy boot-up issue at the end of my NEXT message (message #15).]

When you run WinDoctor, you will immediately be presented with a "Norton WinDoctor Wizard" window on top of the main WinDoctor window. Click on the attached thumbnail at the end of this message and you will see a screenshot where I outlined the "Norton WinDoctor Wizard" and main WinDoctor window items in blue that are referenced in the instructions quoted above.

If you elect to have WinDoctor "Perform all Norton WinDoctor tests (recommended)." Then, after you make all repairs, you can click on the "History" button at the top of the main WinDoctor window which will display a list of all repairs made. (I outlined these items in red in my attached screenshot.)

If you want to make repairs one at a time after WinDoctor has finished its tests, highlight a "problem category" item in the main WinDoctor window by clicking on it. Then click the "Details" button at the top-right corner of the WinDoctor window. The details about all problems in that "problem category" will be displayed in a section in the bottom half of your WinDoctor window. (You might need to scroll.) You can right-click on each of those individual problem items and select "Repair Selected Problem ". Then you can specify how you want WinDoctor to repair the problem. The first repair option listed is the one WinDoctor would perform if you had allowed WinDoctor to automatically repair the item. You can scroll down the list for other repair options (if there are any).

Often my "problems" are "invalid shortcuts" because I have deleted a file from my hard drive or moved a file to another location. Sometimes, Norton WinDoctor will want to link an "invalid shortcut" to a different unrelated or older version file that has the same filename. Sometimes WinDoctor will want to retrieve an item from the Recycle Bin. In those cases, I usually elect to have WinDoctor delete the "invalid shortcut" or entry.

I always elect to repair problems one at a time for two reasons:

1. I control what gets repaired and how the repair is done.
2. I read the details so I learn more about the "problems" WinDoctor finds.

If you ever want to go straight to the main Norton WinDoctor window when you run Norton WinDoctor, click the "Cancel" button at the bottom of the "Norton WinDoctor Wizard" window.


Any time you are at the main (empty) WinDoctor window, you can undo any changes made in the past (back to the beginning of your history - instructions for setting the history length below). Simply click on the "History" button and select any repair you want to undo. Then click the "Undo" button to reverse that repair.


[SIZE= "3"]Instructions for Setting WinDoctor's Repair History Length:[/SIZE]

I posted earlier about setting the amount of time (or number of repairs) you want WinDoctor to keep a record of its repairs. (I have mine set to "Forever" and I occasionally manually delete old records from the repair history.) I have rarely had to use the history to undo changes but each time I did, the repair was undone as I requested. Here's a quick review of how to set the length of time you want to WinDoctor to keep keep a history:

While at the main WinDoctor window, click View > Options > Repair History tab. Then make your selection and click the OK button. (I outlined the "View" menu item in purple in my attached screenshot.)

 

That's your call. For now, I'd say just ignore them until you have your boot-up time issue resolved (since I assume this is your first priority).

If you are using a wireless network and the computer named "JLF-HOMEPC" is not your boyfriend's computer, then I would suspect someone else nearby (neighbor?) was using your wireless network. If this is the case, we can investigate ways to secure your wireless network from unauthorized use. We have a "Networking" forum here at Windows BBS where you can post one of your 8003 errors and ask for information and suggestions.

If "JLF-HOMEPC" is your boyfriend's computer (whether on a wireless or wired network) then I would be inclined to say the 8003 errors can be ignored.

Please click on my attached screenshot thumbnail below and let us know if that improves your boot-up time. I'm sorry I did not think of these specific adjustments sooner.

 

Hello again

1) JLFHOMEPC is my boyfriend's pc, so happy on that one now - he never turns it off, just lets the screen shut off, so guess that explains that one

2) I appear to have a different version of Disk Doctor that you - I don't have a Wizard open when I open the utility, and the window, etc, looks nothing like the one on your screenshot - it's just a small window that opens on top of everything else. There is no View menu, etc. Link to screen dump: http://images.kodakgallery.eu.com/servlet/Images/photos194/1/2/39/26/16/3/316263902133_0_BG.jpg?a=0

3) All the tickboxes in the tip you reccommended to speed up boot-up are already unticked. Doh!

 

Oh, also - I just ran Disk Doctor again, and it reported no issues this time.

When I ran it the other day, just after installation, there were lots of problems - including like you said invalid shortcuts, but also a couple of hundred registry-related issues. Unfortunately I just clicked 'fix all', or whatever it said - though in my defence I figured it knew better than I did what it was doing so I shouldn't fiddle! Guess I know better now...

 

I'm glad we're making some progress anyway.

My screenshot is for WinDoctor (not Disk Doctor).

Norton has too many doctors!

Doh! I thought I had it nailed!

I'm guessing you're referring to WinDoctor here since I don't think Disk Doctor fixes the problems you identified. In that case, you can open WinDoctor's "History" per my instructions I posted last night to view all those "repairs" (and undo any of them you wish).

BTW, for now, I suggest setting WinDoctor to keep records of its repairs "forever" at least until you have your issues cleared up. (I also posted instructions on this last night.)

If I think of anything else to try, I will follow-up.

 

Oops! Got the right one now...

Had a look in the history, says it only changed one thing - in invalid Registry entry related to Turbo Lister - said it fixed an invalid command entry.

Have set it to forever, it was currently set at 7 days so definitely covered the whole period since I installed it.

Well, at least we're eliminating stuff - that's progress right?!

 

Right! That's the right attitude!

Please see my attached screenshot. I think you might find your other "repairs" there.