Fatal error

Within the last week or so, I'm getting the "Repairing Data Archive" screen more and more frequent. I've defragmented the hard drive and tried the Contig prorgram before and after defragmenting but now I am getting a fatal error (usually about 10 mins or so after starting). The dreaded blue screen of death includes the following note:

STOP: 0x0000008E (0xC000001D, 0x804FDC5E, 0xA800C8C4, 0x00000000)

And it reads "Beginning dump of physical memory" and that it has completed that function. I have included the DxDiag.txt of the system specs below.

Is this a RAM error or something else? Thanks in advance.

------------------
System Information (from DxDiag.txt)
------------------
Time of this report: 1/24/2008, 01:30:41
Machine name:
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_qfe.070227-2300)
Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
System Model: Latitude D820
BIOS: Phoenix ROM BIOS PLUS Version 1.10 A04
Processor: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz (2 CPUs)
Memory: 2038MB RAM
Page File: 361MB used, 3569MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode

Ugh me too...blue screens happened 3 times within 2 days.

I formatted recently (the above mentioned were post-format)

And i get repairing data archive a lot also..bugs the shit outa me. I can't remember what error i got..i searched it in google and it said something about my SiS drivers? or ACIS or something >_>

If you find a solution please pm it me!

My pc has the habbit to restart itself randomly. Usually when i have say mozilla open then i try and load GW, or some other big program, the error i get says i have driver conflicts, but it doesnt say which ones, so i dont know where to look :-S

It doesnt do this all the time, just sometimes :-(

No one knows why -_-

I'm really surprised becuase I don't run he newest machine but frankly I have yet to suffer a single error on GW and machines which are far better quality such as the one referred to in the original post suffer errors like this. Mainly my point is that errors and bugs don't discriminate and I was also wondering what precautions I might take to avoid such errors and bugs. Thank you

absolutely nothing....its part of life with computers