Well thanks to all of you for prompt and helpful responses.
Digerati, Okay I goofed in my punctuation, and the space bar is so large.

As for the other issues it sounds like it is off to the shop for this one. I once restored a motorcycle and constructed the wiring harness myself. 12 volt no worries, even if you get on the high voltage side of the coil it will only give you a "thrill." Which is not pleasant, but not life thretening either.
Anything that plugs into the wall is the territory of professionals.
Question:
Would said professional also be able to run tests that would, for lack of a better word, "push" the new RAM cards and see if they have any faults? Checking that the PSU could cope with extra RAM is not an issue that occurred to me, I was confused enough making sure that the RAM was compatible with the motherboard, so it seems possible that may be an issue.
Townsbg:
The RAM came from a reliable source, and I had no issues for a couple of weeks, so as I said I am reasonably confident they are okay.
When installed, due to poor short term memory I installed the RAM, restarted the computer and checked system properties which showed I now had 2gb of RAM. I then did some other stuff on the computer. It was later that day that I remembered the 1394 card, so technically I did only change one thing at a time.
As for updates I have received Windows updates including updates for IE 8, in the period of time since the changes to RAM. I also had an update to Silverlight, which surprised me as I thought I had declined the original offer of Silverlight. It doesn't do anything that I am likely to need, but there it was in Add/Remove so I downloaded the update.
The other main change that occured around the same time was replacing Symantec Corporate AV with Avast as the former had become unstable. I think that gets a mention in the log below.
Broni, here is a VEW log:
Vino's Event Viewer v01c run on Windows XP in English
Report run at 29/08/2009 9:44:58 AM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 28/08/2009 2:57:44 PM
Type: error Category: 1
Event: 2 Source: ACW_DE
Abnormal termination by the user.
Log: 'Application' Date/Time: 21/08/2009 3:32:52 PM
Type: error Category: 0
Event: 2004 Source: PerfNet
Unable to open the Server service. Server performance data will not be returned. Error code returned is in data DWORD 0.
Log: 'Application' Date/Time: 21/08/2009 3:32:52 PM
Type: error Category: 0
Event: 2004 Source: PerfNet
Unable to open the Server service. Server performance data will not be returned. Error code returned is in data DWORD 0.
Log: 'Application' Date/Time: 18/08/2009 10:30:40 PM
Type: error Category: 0
Event: 2004 Source: PerfNet
Unable to open the Server service. Server performance data will not be returned. Error code returned is in data DWORD 0.
Log: 'Application' Date/Time: 18/08/2009 10:30:40 PM
Type: error Category: 0
Event: 2004 Source: PerfNet
Unable to open the Server service. Server performance data will not be returned. Error code returned is in data DWORD 0.
Log: 'Application' Date/Time: 18/08/2009 10:08:30 PM
Type: error Category: 0
Event: 2004 Source: PerfNet
Unable to open the Server service. Server performance data will not be returned. Error code returned is in data DWORD 0.
Log: 'Application' Date/Time: 18/08/2009 10:08:30 PM
Type: error Category: 0
Event: 2004 Source: PerfNet
Unable to open the Server service. Server performance data will not be returned. Error code returned is in data DWORD 0.
Log: 'Application' Date/Time: 18/08/2009 9:49:33 PM
Type: error Category: 0
Event: 2004 Source: PerfNet
Unable to open the Server service. Server performance data will not be returned. Error code returned is in data DWORD 0.
Log: 'Application' Date/Time: 18/08/2009 9:49:33 PM
Type: error Category: 0
Event: 2004 Source: PerfNet
Unable to open the Server service. Server performance data will not be returned. Error code returned is in data DWORD 0.
Log: 'Application' Date/Time: 16/08/2009 5:37:37 PM
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application SDFiles.exe, version 1.6.1.7, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Log: 'Application' Date/Time: 16/08/2009 5:36:48 PM
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application SDFiles.exe, version 1.6.1.7, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Log: 'Application' Date/Time: 08/08/2009 11:54:47 PM
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application firefox.exe, version 1.9.1.3497, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Log: 'Application' Date/Time: 08/08/2009 11:54:23 PM
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application firefox.exe, version 1.9.1.3497, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Log: 'Application' Date/Time: 08/08/2009 11:54:05 PM
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application firefox.exe, version 1.9.1.3497, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Log: 'Application' Date/Time: 30/07/2009 11:49:30 PM
Type: error Category: 0
Event: 51 Source: Symantec AntiVirus
The event description cannot be found.
Log: 'Application' Date/Time: 30/07/2009 11:49:30 PM
Type: error Category: 0
Event: 5 Source: Symantec AntiVirus
The event description cannot be found.
Log: 'Application' Date/Time: 30/07/2009 11:49:29 PM
Type: error Category: 0
Event: 46 Source: Symantec AntiVirus
The event description cannot be found.
Log: 'Application' Date/Time: 30/07/2009 11:48:19 PM
Type: error Category: 0
Event: 51 Source: Symantec AntiVirus
The event description cannot be found.
Log: 'Application' Date/Time: 30/07/2009 11:48:17 PM
Type: error Category: 0
Event: 5 Source: Symantec AntiVirus
The event description cannot be found.
Log: 'Application' Date/Time: 30/07/2009 11:48:16 PM
Type: error Category: 0
Event: 46 Source: Symantec AntiVirus
The event description cannot be found.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 21/08/2009 3:32:29 PM
Type: error Category: 0
Event: 1002 Source: Dhcp
The IP address lease 169.254.249.111 for the Network Card with network address 0016E66F4A68 has been denied by the DHCP server 192.168.1.254 (The DHCP Server sent a DHCPNACK message).
Log: 'System' Date/Time: 21/08/2009 3:16:53 PM
Type: error Category: 0
Event: 4307 Source: NetBT
Initialization failed because the transport refused to open initial Addresses.
Log: 'System' Date/Time: 21/08/2009 3:16:47 PM
Type: error Category: 0
Event: 4307 Source: NetBT
Initialization failed because the transport refused to open initial Addresses.
Log: 'System' Date/Time: 18/08/2009 12:59:25 PM
Type: error Category: 0
Event: 7022 Source: Service Control Manager
The Windows Time service hung on starting.
Log: 'System' Date/Time: 16/08/2009 5:46:49 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The bcftdi service failed to start due to the following error: Insufficient system resources exist to complete the requested service.
Log: 'System' Date/Time: 16/08/2009 5:46:49 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The bc_filter service failed to start due to the following error: Insufficient system resources exist to complete the requested service.
I will await Broni's interpretation of the log before I do anything to the box, though I do agree going back to the old RAM will isolate that as a source of the problem. One fly in that ointment is that even if I leave the new RAM in, which I will for the time being, it could be days before there is a repeat of the problem. (If it turns out that the new RAM is the problem, or part of it, I will be more than a little cheesed off. I have never run short of RAM, well I have never had any mesages from the sytem saying it is low on virtual memory. The extra gb was really future proofing.) When it comes to electrics/electronics the worst faults are intermittent ones.
After looking at the log a couple of other events come to mind, which may be relevant or helpful. My password is stored inside the modem. I followed the instructions on the ISP website to change password, but then had to phone them and go through the process again as the new password was not accepted. And there was another occasion where I was unable to get on to the net. With the assistance of my ISP I made some changes to the settings of my modem which sorted that one out.
I await.