Sudden rebooting becoming a real pain!

Question

Hi
I've been using this board quite happily for a couple of months or so and I like it but just recently, I've been getting sudden reboots for no apparent reason which, once back on the desktop, I'm informed that Windows has recovered from a serious error.  I must admit that this is becoming a real pain now and I don't know what's causing it.
A few minutes ago, I just pressed Ctrl+Alt+Del to bring up Task Manager and the computer just restarted for no reason.  Every so often, it seems like I just have to hit one key and it reboots  
I have read threads in this forum about users who had had similar problems and as far as I am aware, my PSU is up to the job - see system spec and my CPU temp, using stock heatsink with thermal pad is around 44Cat idle.  I also have two fans inside the Enermax PSU and another 'exhuast' fan at the back of the case.  The DDR voltage is set to 2.70v and the AGP voltage is set to 1.65v.  The content of the log file that was created is as follows:
Microsoft Windows
The system has recovered from a serious error
A log file has been created
For more information about this error, click here
The following files will be included in this error report:
C:\WINDOWS\Minidump\Mini112303-01.dmp
C:\~1\David\LOCALS~1\Temp\WER1.tmp.dir00\sysdata.xml
Server=watson.microsoft.com
UI LCID=1033
Flags=123154
Brand=WINDOWS
TitleName=Microsoft Windows
DigPidRegPath=HKLM\Software\Microsoft\Windows NT\CurrentVersion\DigitalProductId
RegSubPath=Microsoft\PCHealth\ErrorReporting\DW
ErrorText=A log of this error has been created.
HeaderText=The system has recovered from a serious error.
Stage2URL=
Stage2URL=/dw/bluetwo.asp?BCCode=a&BCP1=FFB92000&BCP2=00000002&BCP3=00000000&BCP4=8052A4EC&OSVer=5_1_2600&SP=1_0&Product=768_1
DataFiles=C:\WINDOWS\Minidump\Mini112303-01.dmp|C:\DOCUME~1\David\LOCALS~1\Temp\WER1.tmp.dir00\sysdata.xml
ErrorSubPath=blue
There is another file inside the "WER1.tmp/dir00" called "sysdata" which is an XML doc but I can't make any sense of it.
HELP!
Regards

Answer 1

Hi and thanks to all who responded to my post.
Ok, to Danny, I downloaded "Memtest86" and after extraction, I now have an ISO file.  When I burn the ISO to CD,  does it create a 'bootable' CD with which I boot the computer with it or do I need to actualy create a bootable CD first?  Also, what tests need to be run?  See last few paragraphs.
MarkA:  I looked at the link you provided and I am already running XP Home with SP1 and ALL updates that are available at this time.  I have saved the link so i can look at it later regarding the "pagefile".  See last few paragraphs.
Gio1:  My DDR Ram is in slots 1 & 3 and I may try moving the sticks to 2 & 4.  See last few paragraphs.
SoCalMX:  My AGP voltage has been at 1.65v since I build the system and I have never had any problems with rebooting until recently (but see my last few paragrahs below), but I will give it a try at 1.60v.   BTW, I don't play games on the computer.
To all of you:  I forgot to mention that I have been using the board for a couple of months or so and I was very happy with it but around a week ago, I enabled the Promise controller and moved my ATA133 drives from IDE1 to IDE3 and then updated the WinXP Promise S-ATA(378(tm) drivers from v1.00.16 to v1.00.29 and that's when I got my very first error message since I've been using the board, and the message was something like "IRQ less than or not equal to etc, etc, etc".
BTW, the drivers have been rolled back to v1.00.16.
I posted my problems in this forum and after trying a few suggestions from user's, I moved my drivers back to IDE1.  I now don't get the IRQ message - at least not since I moved them back but I am getting the error as shown in my first post in this thread.
So, just to clarify, I had absolutely no problems with this board until I moved my ATA133 drives to IDE3 and updated the drivers and that's when the problems started.  I have updated my PSU to the one shown in my system 'specs' below.
BTW, the drivers have been rolled back to v1.00.16 but I'm just wondering if the previously updated drivers are still causing problems and I'm thinking of formatting and re-installing XP to see if that will solve the issue?
Regards