Problems after upgrade

Hi all, I'll try and keep this as concise as possible: About a month ago, our computer crashed. We had an upgrade done. Our system info is:
Microsoft Windows Xp, Home Edition 2002, Service Pack 3
Computer: Pentium(R) Dual Core CPU E5400 @ 2.70Ghz, 1.96 GB RAM.

Since the ugrade, randomly the computer shuts down, and restarts, where we see an error message "The System has recovered from a serious error". The log comes up with different error codes each time. Here are some of them I've made a note of:

C:\DOCUME~\OurName\Locals~1Temp\WERe698.dir00\Mini03410.03.dmp
C:\DOCUME~\OurName\Locals~1Temp\WERe698.dir))\sysdata.xtml
Sorry I didn't record the bugcheck Codes for the above.

And this:
BCcode:c2 BCP1:00000007 BCP2:00000CD4 BCP3:10000000 BCP4:E18BOBCO
OSver:5_1_2600 SP:3_0 Product 7681

C:\DOCUME~1\OURNAME\LOCALS~1\Temp\WER9a41.dir00\Mini030510.01.dmp
C:\DOCUME~1\OURNAME|LOCALS~1\Temp\WER9a41.dir00\sysdata.xml

And this:
C:\OURNAME\LOCALS~1\Temp\WERab76.dir00Mini030410.01.dmp
C:\OURNAME|LOCALS~1TempWERab76.dir00\sysdata.xml

BCcode:1000008c BCP1:C0000005 PCP2:B9F18685 BCP3:A6B90904 BCP4:0000000 OSVer:5_1_2600 S):3_0 Product 768_1

And here is another Bugcheck Code (without full error log (sick of writing them down, as they are different every single time:banghead)):
BCcode:24 BCP1:001902FE BCP2:B14E3AE4 BCP3:BA4E37EO BCP4:B9EAB413 PSVer:5_1_2600 SP3_0 Product 768_1

I've updated some drivers using Window Driver Whiz. Not all were successful. After some research, I have seen others try and delete their minidumps which only seems to stop the error message coming up. (I gather from some of the error codes above minidump files are involved.) This isn't going to stop the errrors. I've Googled the codes, and none match mine. From one forum I looked at some who had minidump problems related it back to video cards. I have been assuming it's a hardware/driver problem.

Please note the errors and shut down are not the blue screen of death, but each time we send the report we are directed to Microsofts not overly helpful blue screen error help page. If anyone can help, I will be really appreciative,
Cheers, Lisa

 

Okay, good news I think. I looked again at the hardware in device manager and found one which I had earlier been unable to update drivers for. Well it had a yellow exclamation. I unistalled it, but I don't think it actually unistalled. So I disabled it as it wasn't working properly anyway. I turned off and rebooted the computer and no error messages. Yay. So far the computer hasn't shut down anymore either, and everything seems to be working fine. I don't know how I missed it before, but here's hoping the problem is permanently resolved. If it isn't, I'll be back. Guess this should have been posted in the hardware section. Oops!

 

Normally an upgrade is not a fix for a crash.
What OS were you running? Explain with a bit more detail about the crash.
I'm thinking that the hardware problem that caused the initial crash still hasn't been identified and fixed.
First we need to stop the restarts and get some BSOD so we can see what the computer is trying to tell you.
Do this: right-click My Computer, left-click properties then advanced => startup & recovery settings and uncheck Automatically Restart.
You should now not reboot but instead get a blue screen with white printing when the computer crashes. Copy the first alphanumeic string starting with 0x0 and and words with the BSOD.

 

RE the computer crashing, we thought and hoped it was just the power supply, and had it looked at locally, and was told it was the motherboard etc etc. (The computer would not start up at all). The guy said it was likely too outdated to do much with, and that the parts were probably obsolete, so I figured we'd be buying a new tower etc. Anyway he said he could upgrade it. So that's what we did. Just before that happened, we had signed up for an upgraded internet account on ADSL2 which required a new modem. The new modem came while the pc was in being fixed, so the daythe computer came home my husband did the new broadband installation. I think the hardware which was causing trouble was to do with the old modem. The problems began almost straight away. Things like the printer etc we only added later. So, hopefully now we've disabled the old hardware things should stay stable. I'll have a go a what you recommend to make sure there isn't anything else going on. Thanks.

 

If the computer crashes again, I'll post what feedback I get. Here's hoping it wont. Thanks so much for replying. If there are no more problems over the next few days, I'll report back with an all clear. Watch this space...........
BTW we were previously running Windows XP home 2002 service pack 2.

 

Okay, I've had a few more hassles this afternoon, and looked at the event log. I'm going to see what happens tomorrow. It's all been fine for the last couple of hours. I just looked over 7 days of errors, and for the sake of simplicity will use a log from tomorrow. I'm sure there will be some drama occuring.

 

Okay, here is an event log of the errors today:
Event Type: Warning
Event Type: Error
Event Source: Ntfs
Event Category: Disk
Event ID: 55
Date: 6/03/2010
Time: 11:54:22 AM
User: N/A
Computer:
Description:
The description for Event ID ( 55 ) in Source ( Ntfs ) 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: , C:.
Data:
0000: 00 00 00 00 02 00 4e 00 ......N.
0008: 02 00 00 00 37 00 04 c0 ....7..À
0010: 00 00 00 00 32 00 00 c0 ....2..À
0018: 18 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: 6/03/2010
Time: 11:43:47 AM
User: N/A
Computer:
Description:
Error code 1000008e, parameter1 c0000005, parameter2 b9e7eeed, parameter3 a795a81c, 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 30 35 2c 20 000005,
0038: 62 39 65 37 65 65 65 64 b9e7eeed
0040: 2c 20 61 37 39 35 61 38 , a795a8
0048: 31 63 2c 20 30 30 30 30 1c, 0000
0050: 30 30 30 30 0000
Event Type: Warning
Event Source: RemoteAccess
Event Category: None
Event ID: 20192
Date: 6/03/2010
Time: 11:43:12 AM
User: N/A
Computer:
Description:
A certificate could not be found. Connections that use the L2TP protocol over IPSec require the installation of a machine certificate, also known as a computer certificate. No L2TP calls will be accepted.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 6/03/2010
Time: 11:42:47 AM
User: N/A
Computer:
Description:
The Bluetooth Support 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.

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


Last night, I kept getting a message saying our virus protection was turned off, and it wouldn't allow me to turn it on. (Avira free version). I uninstalled and reinstalled it, did updates, but the problem persists.

Can anyone help?

 

Sorry, I don't ever bother looking at my event logs because I can't figure out what they try to tell me. The computer keeps going and when I look in I see all these red Xs so I figure, what sort of error allows the computer to run without any hiccups.

Maybe someone will come along and be able to interpret them.

 

Thanks for reading. I have googled and not being a real tech head kind of gal, I normally manage to fix things by chance, but I'm so over it. The only good thing is the PC isn't crashing while I'm actually using it. I don't really want to muck around in the system too much in case I make things worse.