Serius Annoyng Windows XP crash error

Hi ctrindade,
Please post the log from this:

  HijackThis -->http://www.spychecker.com/program/hijackthis.html

~sirbounty

Hi sirbounty,

Thanks a lot for helping me!

Here goes the requested information.

Logfile of HijackThis v1.97.5
Scan saved at 21:42:13, on 09/03/2004
Platform: Windows XP SP1 (WinNT 5.01.2600)
MSIE: Internet Explorer v6.00 SP1 (6.00.2800.1106)

Running processes:
C:\WINDOWS\System32\smss.exe
C:\WINDOWS\system32\winlogon.exe
C:\WINDOWS\system32\services.exe
C:\WINDOWS\system32\lsass.exe
C:\WINDOWS\System32\Ati2evxx.exe
C:\WINDOWS\system32\svchost.exe
C:\WINDOWS\System32\svchost.exe
C:\WINDOWS\system32\spoolsv.exe
C:\WINDOWS\System32\inetsrv\inetinfo.exe
c:\PROGRA~1\mcafee.com\vso\mcvsrte.exe
C:\Program Files\Analog Devices\SoundMAX\SMAgent.exe
C:\Program Files\Commander Pro\UPServ.exe
C:\WINDOWS\System32\MsPMSPSv.exe
C:\Program Files\Commander Pro\UPS.EXE
C:\WINDOWS\system32\Ati2evxx.exe
C:\WINDOWS\Explorer.EXE
c:\PROGRA~1\mcafee.com\vso\mcshield.exe
C:\Program Files\Analog Devices\SoundMAX\SMax4PNP.exe
C:\Program Files\Analog Devices\SoundMAX\smax4.exe
C:\Program Files\Roxio\Easy CD Creator 6\DragToDisc\DrgToDsc.exe
C:\Program Files\Roxio\Easy CD Creator 6\AudioCentral\RxMon.exe
C:\PROGRA~1\mcafee.com\vso\mcvsshld.exe
C:\PROGRA~1\mcafee.com\agent\mcagent.exe
c:\progra~1\mcafee.com\vso\mcvsescn.exe
C:\PROGRA~1\KEYB_M~1\Keyboard\Ikeymain.exe
C:\PROGRA~1\KEYB_M~1\Mouse\Amoumain.exe
C:\WINDOWS\System32\taskswitch.exe
C:\Program Files\ATI Technologies\ATI Control Panel\atiptaxx.exe
C:\WINDOWS\System32\rundll32.exe
C:\WINDOWS\System32\ctfmon.exe
C:\Program Files\MailCheck\mailck.exe
C:\Program Files\Roxio\Easy CD Creator 6\AudioCentral\Playlist.exe
C:\Program Files\Douwantit\duwi.exe
C:\Program Files\InterVideo\Common\Bin\WinCinemaMgr.exe
C:\Program Files\LightSurf\Common\IconMgr.exe
C:\Program Files\3com\Connection Assistant\bin\mad.exe
C:\Program Files\SMASHER\Smasher.exe
C:\Program Files\LightSurf\Color Indicator\TICIcon.exe
C:\Program Files\SMASHER\Smasher.exe
C:\Program Files\3com\Connection Assistant\bin\mpbtn.exe
C:\PROGRA~1\3com\CONNEC~1\Common\MOTIVE~1.EXE
C:\Program Files\Messenger\msmsgs.exe
c:\progra~1\mcafee.com\vso\mcvsftsn.exe
C:\WINDOWS\System32\dllhost.exe
C:\WINDOWS\System32\inetsrv\DavCData.exe
C:\Program Files\Outlook Express\msimn.exe
C:\Program Files\Internet Explorer\iexplore.exe
C:\Documents and Settings\Carlos Trindade\Local Settings\Temp\HijackThis.exe

R0 - HKCU\Software\Microsoft\Internet Explorer\Main,Start Page = http://online.expresso.pt/
R1 - HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings,ProxyOverride = 127.0.0.1
O2 - BHO: (no name) - {B3269F9A-6521-4793-A951-3E9A9B2E55E7} - C:\Program Files\Douwantit\duwibco02.dll
O3 - Toolbar: &Radio - {8E718888-423F-11D2-876E-00A0C9082467} - C:\WINDOWS\System32\msdxm.ocx
O3 - Toolbar: McAfee VirusScan - {BA52B914-B692-46c4-B683-905236F6F655} - c:\progra~1\mcafee.com\vso\mcvsshl.dll
O4 - HKLM\..\Run: [SoundMAXPnP] C:\Program Files\Analog Devices\SoundMAX\SMax4PNP.exe
O4 - HKLM\..\Run: [SoundMAX] "C:\Program Files\Analog Devices\SoundMAX\smax4.exe" /tray
O4 - HKLM\..\Run: [TCASUTIEXE] TCAUDIAG.EXE -off
O4 - HKLM\..\Run: [RoxioEngineUtility] "C:\Program Files\Common Files\Roxio Shared\System\EngUtil.exe"
O4 - HKLM\..\Run: [RoxioDragToDisc] "C:\Program Files\Roxio\Easy CD Creator 6\DragToDisc\DrgToDsc.exe"
O4 - HKLM\..\Run: [RoxioAudioCentral] "C:\Program Files\Roxio\Easy CD Creator 6\AudioCentral\RxMon.exe"
O4 - HKLM\..\Run: [VSOCheckTask] "c:\PROGRA~1\mcafee.com\vso\mcmnhdlr.exe" /checktask
O4 - HKLM\..\Run: [VirusScan Online] "c:\PROGRA~1\mcafee.com\vso\mcvsshld.exe"
O4 - HKLM\..\Run: [MCAgentExe] c:\PROGRA~1\mcafee.com\agent\mcagent.exe
O4 - HKLM\..\Run: [MCUpdateExe] C:\PROGRA~1\mcafee.com\agent\McUpdate.exe
O4 - HKLM\..\Run: [iKeyWorks] c:\PROGRA~1\KEYB_M~1\Keyboard\Ikeymain.exe
O4 - HKLM\..\Run: [WheelMouse] c:\PROGRA~1\KEYB_M~1\Mouse\Amoumain.exe
O4 - HKLM\..\Run: [CoolSwitch] C:\WINDOWS\System32\taskswitch.exe
O4 - HKLM\..\Run: [ATIPTA] C:\Program Files\ATI Technologies\ATI Control Panel\atiptaxx.exe
O4 - HKLM\..\Run: [New.net Startup] rundll32 C:\PROGRA~1\NEWDOT~1\NEWDOT~1.DLL,NewDotNetStartup
O4 - HKLM\..\Run: [QuickTime Task] "C:\Program Files\QuickTime\qttask.exe" -atboottime
O4 - HKCU\..\Run: [CTFMON.EXE] C:\WINDOWS\System32\ctfmon.exe
O4 - HKCU\..\Run: [MailCheck] C:\Program Files\MailCheck\mailck.exe
O4 - Global Startup: 3Com Connection Assistant.lnk = C:\Program Files\3com\Connection Assistant\bin\matcli.exe
O4 - Global Startup: DoUWantIt.lnk = C:\Program Files\Douwantit\duwi.exe
O4 - Global Startup: InterVideo WinCinema Manager.lnk = C:\Program Files\InterVideo\Common\Bin\WinCinemaMgr.exe
O4 - Global Startup: LightSurf.lnk = C:\Program Files\LightSurf\Common\IconMgr.exe
O4 - Global Startup: Microsoft Office.lnk = C:\Program Files\Microsoft Office\Office10\OSA.EXE
O4 - Global Startup: SMASHER.lnk = C:\Program Files\SMASHER\Smasher.exe
O8 - Extra context menu item: E&xport to Microsoft Excel - res://C:\PROGRA~1\MICROS~2\Office10\EXCEL.EXE/3000
O9 - Extra button: Related (HKLM)
O9 - Extra 'Tools' menuitem: Show &Related Links (HKLM)
O10 - Hijacked Internet access by New.Net
O10 - Hijacked Internet access by New.Net
O10 - Hijacked Internet access by New.Net
O10 - Hijacked Internet access by New.Net
O10 - Hijacked Internet access by New.Net
O16 - DPF: {166B1BCA-3F9C-11CF-8075-444553540000} (Shockwave ActiveX Control) - http://download.macromedia.com/pub/shockwave/cabs/director/swdir.cab
O16 - DPF: {41F17733-B041-4099-A042-B518BB6A408C} - http://a1540.g.akamai.net/7/1540/52/20031216/qtinstall.info.apple.com/mickey/us/win/QuickTimeInstaller.exe
O16 - DPF: {4ED9DDF0-7479-4BBE-9335-5A1EDB1D8A21} (McAfee.com Operating System Class) - http://bin.mcafee.com/molbin/shared/mcinsctl/en-us/4,0,0,76/mcinsctl.cab
O16 - DPF: {9059F30F-4EB1-4BD2-9FDC-36F43A218F4A} (Microsoft RDP Client Control (redist)) - file://C:\WINDOWS\Web\TSWeb\msrdp.cab
O16 - DPF: {9F1C11AA-197B-4942-BA54-47A8489BB47F} (Update Class) - http://v4.windowsupdate.microsoft.com/CAB/x86/unicode/iuctl.CAB?37995.6232638889
O16 - DPF: {BCC0FF27-31D9-4614-A68E-C18E1ADA4389} (DwnldGroupMgr Class) - http://bin.mcafee.com/molbin/shared/mcgdmgr/en-us/1,0,0,16/mcgdmgr.cab
O16 - DPF: {D27CDB6E-AE6D-11CF-96B8-444553540000} (Shockwave Flash Object) - http://fpdownload.macromedia.com/pub/shockwave/cabs/flash/swflash.cab
O16 - DPF: {F3F193CC-8D90-4BEB-8EDA-3EA69BB624F0} (Downloader Class) - http://a2044.g.akamai.net/7/2044/7189/20031111212146/www.douwantit.com:80/web/download/dwnldr.cab
O17 - HKLM\System\CCS\Services\Tcpip\..\{2DD7EB0C-006A-4162-AF9B-F1C09266D133}: NameServer = 194.65.5.2,194.65.3.21

CTrindade

Also this

Dumprep - Explained (Microsoft)

It has various mode of functionality. ER Utility Application - This will be referred to as dumprep.exe from here forward.

This application houses a few simple functions to be used when a separate application is needed to perform certain tasks (such as snapping a minidump of a process, etc).

Queued reporting:

This goal of this mode is similar to that of regular manifest exception reporting: prevent non-privileged users from accessing data they should not be accessing. In regular manifest mode, we have the possibility that a non-privileged user could see a minidump from a service process if he was logged onto the local console when the service faulted.

Even if he does not look at the minidump, he is potentially given the option of reporting the fault to Microsoft- which may not be what a machine admin would want to do.

To work around this, we introduce the concept of queue. Queue works very similarly to kernel fault reporting.

1. We enter queue at the point which we left manifest exception reporting above. Note that we never return to manifest exception reporting mode. When we finish, we go directly back to the point where we left 'user mode exception' reporting.

2. The ERSvc invokes faultrep.dll to do the actual reporting. Faultrep.dll is loaded into the ERSvc process.

3. A user fault signature is extracted from the minidump.

4. The fault is stored in the user fault queue directory. If the directory is located on an NTFS drive, we attempt to use NTFS
compression to compress the file.

5. The fault signature as well as some other metadata about the fault is packaged into a structure and stored in the registry along with the pointer to the file in the queue directory. We also dumprep.exe to the HKLM 'Run' key, which causes dumprep.exe to get executed every time a user logs in (until it is removed from the 'Run' key).

6. We check and see if the fault reporting queue is above the maximum number of entries (10 by default) and delete the oldest entry from the queue.

7. Wait for an administrator to log in interactively (either at the local console or via terminal server / remote desktop). Note that we really return back to the faulting app here and do not actually cause the faulting app to 'wait'. However, the fault reporting process for this fault effectively waits.

8. When an administrator logs in, dumprep.exe runs and checks the list of user faults. If it is empty, dumprep.exe (and ER) terminates.

9. We attempt to acquire a global mutex that only administrators have access to (this is how we enforce administrator access to reporting). If we fail, dumprep.exe (and ER) terminates.

10. We read an entry from the registry list. That the following steps occur once for each entry in the list.

11. Faultrep.dll is loaded and called with the path to the minidump to report & the user fault metadata we stored away in the registry.

12. Faultrep.dll is loaded and the registry based configuration is checked.

a. If both reporting and notification are disabled, ER terminates.

b. If reporting is enabled and notification is not, we report in silent mode

c. If notification is enabled and reporting is not, we display a pop up notifying the user of the fault, but there is no 'Send / Don't Send' button set. There is just an 'Ok' button.

d. If both are enabled, we report normally.

13. We collect application compatibility data if possible and store it in a file in the temp directory.

14. The DW manifest is constructed.

15. DW is launched. The behavior is described in the 'DW Process' section above.

16. Once DW returns, ER terminates (or repeats if we have been called by dumprep.exe and there are additional faults to report- note, if the DW dialog remained up for more than 5 minutes without user interaction, then no further reports will be offered to the user. The next admin who logs in will be offered the opportunity to report).

I don't recognize these...
C:\Program Files\Douwantit\duwi.exe
O2 - BHO: (no name) - {B3269F9A-6521-4793-A951-3E9A9B2E55E7} - C:\Program Files\Douwantit\duwibco02.dll
O4 - Global Startup: DoUWantIt.lnk = C:\Program Files\Douwantit\duwi.exe

C:\Program Files\SMASHER\Smasher.exe <-- spyware stopper - but why 2 instances?

While not harmful, this can be removed:
O4 - HKLM\..\Run: [QuickTime Task] "C:\Program Files\QuickTime\qttask.exe" -atboottime
O4 - Global Startup: Microsoft Office.lnk = C:\Program Files\Microsoft Office\Office10\OSA.EXE

You might also try:
Start->Run->SFC /Scannow

and

Start->Run->MSCONFIG
 Remove all items from the startup tab and see if the problem persists...

There is also new dot net that needs to be removed...
O4 - HKLM\..\Run: [New.net Startup] rundll32 C:\PROGRA~1\NEWDOT~1\NEWDOT~1.DLL,NewDotNetStartup
Remove the above key in the registry... Or use MSCONFIG as stated above..

duwi.exe  -- Do U want it  
Program Name: DoUWantIt
Executable Name: duwi.exe
Required: No
Comments: DoUWantIt - online shopping assistant. Start it manually

Hello Everybody,

Thanks very much for all your precious information. You all have been very useful, especially 1stITMAN.

Now, I am working hard, trying to narrow the problem using all the information you gave me. I will inform you when I find the source of the error.

Meanwhile, I noticed that if I try to change the properties of IPX/SPX/NetBIOS Protocol, needed to communicate with a Print Server, the Local Area Connection Properties application hangs and, sometimes, I need to restart the computer to get rid of the bad situation.

I don't now if this is related with the main explained problem. If it isn’t, I will worry about that latter when I solved the main problem.

CTrindade

IPX/SPX is only needed if u are a novell network and I dont think ull need NetBios Protocol unless you state otherwise..

Well, the manual of the Print Server (Linksys) said that the user needs to install the IPX/SPX protocol when running Windows but, as a matter of fact, I already uninstall it and the Print Server is working just fine without that protocol.

Yeh well it will running on TCP/IP I Hope!!

Hello! Things are getting worse. When I tried to check the installed drivers with verifier.exe, the error with the DLL HAL.DLL began to show up - it said that HAL.DLL is missing or corrupted and I hardly can load Windows XP. I copied the file from another computer running the same OS to the C:/Windows/system32 directory but I am still getting the same result. I hope I wouldn’t have to reinstall Windows. What do you think about this? Thanks.

Have a look here
https://www.experts-exchange.com/questions/20855465/WinXP-Won't-Boot-Missing-hal-dll-file.html
https://www.experts-exchange.com/questions/20863407/Hal-dll-error-at-boot-time-Unable-to-boot.html
http://www.computerhope.com/issues/ch000490.htm

You havent changed anything in boot.ini have you?
If you get an error regarding a missing or corrupt hal.dll file, it might simply be the BOOT.INI file on the root of the C: drive that is misconfigured
Insert and boot from your WindowsXP CD.
At the first R=Repair option, press the R key
Press the number that corresponds to the correct location for the installation of Windows you want to repair.
Typically this will be #1
Type bootcfg /list to show the current entries in the BOOT.INI file
Type bootcfg /rebuild to repair it
Take out the CD ROM and type exit

No, I haven't changed anything in boot.ini. I will try to proceed as you told me above. Thanks a lot!

OK! I managed to get rid of the hal.dll faulty problem, thanks to 1stITMAN.

I also scanned the system and it seems it's working much better now. I proceed with the drivers test using verifier.exe. It happens  the test returns some blue screens either with the 0xc5 or 0xc9 errors, when I was verifying the NetBT.sys driver. On the other hand, The 3COM NIC Doctor utility reports an error while running Network Test, but give a clean result running NIC test.

Well, I haven't had yet enough time to test all the drivers, but I begin to suspect that something is wrong with the Network Card. It's a 3 COM 3C940 Gigabit NIC, integrated in the motherboard, and I have the latest driver.

I am beginning also to accept the possibility that something may be wrong with the RAM (1GB Dual Channel) or even with the power supply (350W).

Cheers!

well you can sson test the RAM use www.simmtester.com
HAve you issued a virus scan on system lately? Try http:\\housecall.trendmicro.com
Also try an get hold of a hardware testing utiltity to check the mainboard etc..
I use PCCheck myself!!
Where are you in the world?

Fine! I hope I will have a little more time to proceed with the PC tests during the week-end.

I already tried to test my memory, but the big surprise is that the DocMemory software hangs just at the beginning of the test. It works nice in the other machines I have at home. Do you think I can conclude that this is a memory problem or perhaps has something to do with the fact the machine is working with dual channel memory? Meanwhile, I keep getting the annoying blue screens.

I am in Portugal. By the way, where are you?

Have a nice week end!

It could be ur memory then, Well I am in sunny UK!!
I would take one stick out the test again!
Then swap them round!!

Hello, here is what I done so far.

- I disabled DCOM (it keeps turning me errors everytime I boot the computer) with DCOMbobulator (http://grc.com/dcom/);
- I updated all my Intel Chipset drivers;
- I cleaned up my system with PCBugDoctor;
- I checked and repaired some hard disk errors with CHKDSK.

The memory and hard disk tests reports no errors.

The blue screens seem to have gone, but I had to format the hard drive and reinstall the OS because, at some point, the disk got uncoverable errors. The only thing I am sure until now is that, in my case, what really matters was the Chipset drivers installation. The system becomes much more stable. Although it is not perfect and sometimes reboots on its own without having even loaded the OS.

As the bios is up-to-date I think that symptom and the frequent disk errors may point to a faulty power supply. The power supply is a 350W one and perhaps hasn't enough power for two hard disks, a P4 processor and 1GB memory. I will buy a 450W or 550W power supply soon.

Ok so u r running kinda smoothley then !!

Well, here we are again!

At this time, I already changed my power supply to a 550W one, but the bad situation remains unchanged.

I managed to test my memory with several RAM utility testers, always giving me a clean report with no errors. I swap the modules around always with no positive results.

I also tested my S-ATA hard drive which reports not a single error.

I tested exhaustively the installed drivers with verifier.exe getting some inconclusive results.

I disabled several devices, rolled back some drivers and reinstalled the last versions of others.

I also try to adjust the BIOS parameters more accurately and performed some tests.

Although it's true the system stability improved a lot, I keep getting the following blue screens from time to time:

- 0x0000000a
- 0x000000c5
- 0x0000008e

Do you know if SATA hard disks need a specific driver to work properly, even if they aren't configured as raid? Mine is not configured as raid.

Thanks a lot!

Plz check the event log and post the full errors??

Here we go!

Event log cat. (102) event 1003

Error code 000000c5, parameter1 ee657645, parameter2 00000002, parameter3 00000001, parameter4 80538105.
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 30 30 30 30 30 30 63    000000c
0020: 35 20 20 50 61 72 61 6d   5  Param
0028: 65 74 65 72 73 20 65 65   eters ee
0030: 36 35 37 36 34 35 2c 20   657645,
0038: 30 30 30 30 30 30 30 32   00000002
0040: 2c 20 30 30 30 30 30 30   , 000000
0048: 30 31 2c 20 38 30 35 33   01, 8053
0050: 38 31 30 35               8105    

Error code 0000000a, parameter1 00000016, parameter2 0000001c, parameter3 00000000, parameter4 804fceb3.
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 30 30 30 30 30 30 30    0000000
0020: 61 20 20 50 61 72 61 6d   a  Param
0028: 65 74 65 72 73 20 30 30   eters 00
0030: 30 30 30 30 31 36 2c 20   000016,
0038: 30 30 30 30 30 30 31 63   0000001c
0040: 2c 20 30 30 30 30 30 30   , 000000
0048: 30 30 2c 20 38 30 34 66   00, 804f
0050: 63 65 62 33               ceb35

Error code 1000008e, parameter1 c0000005, parameter2 80538105, parameter3 b1c1e438, parameter4 00000000.
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: 38 30 35 33 38 31 30 35   80538105
0040: 2c 20 62 31 63 31 65 34   , b1c1e4
0048: 33 38 2c 20 30 30 30 30   38, 0000
0050: 30 30 30 30               0000

Thanks a lot for help me and sorry for the inconvenience.

check this out http://www.eventid.net/display.asp?eventid=1003&source=

End of the Story!

After a three month fight I manage to get rid of the Windows blue screens.

I had a defective memory. Actually I had two defective memory modules. The computer store exchanged the modules and now everything is working fine. They said their tests didn’t reveal anything wrong with the modules and they are probably incompatible with my motherboard (ASUS P4P800 Del). Meanwhile, the memory factory support service (TwinMOS) claims that these modules are compatible with my motherboard.

The truth is that I tested extensively the modules with "Windows Memory Diagnostic" and it reports 18 errors in one module and 42 in the other one.

The lesson learned about this is, if you got these several types of errors randomly or even similar ones,

0x000000C5
0x0000000a
0x00000050
0x0000008E
0x000000D1
0x0000007E

and you have everything up-to-date including the machine BIOS, probably the problem is a defective RAM or a faulty motherboard.

Just test the memory in EXTENSIVE MODE with "Windows Memory Diagnostic". My experience told me that other test utilities like MemTest86 or DocMemory wouldn't work properly with some types of memory.

Of course, you may also have some other faulty hardware. Bad drivers could give one of these errors, but usually only one.

"Windows Memory Diagnostic" could help you to define if the problem is with RAM memory or either the motherboard or something connected to it.

Thanks everybody for your precious and useful help.

I hope this can help anyone with a similar problem.

Best Regards!

i have the exact same problem and  no idea whats wrong.

Go to http://oca.microsoft.com/en/windiag.asp and download the "Windows Memory Diagnostic".

Follow the instructions to install the application in a diskette or in a CD.

You must reboot your computer from that diskette or CD.

The memory test application runs automatically as soon as your reboot from one of these supports.

Run the extended test mode rather then the standard test. Live it running for a few hours. If the test reports any errors you have a defective RAM or a defective motherboard.

To know if the problem is with RAM or with the motherboard, you should install some other memory module which proved to be OK.

If you have two memory RAM modules, try to take one out and test the other once again. Swap the modules leaving that one already tested out.

If you have another spare module which proved to be OK, install it alone and run the test again.

If the memory test stops showing errors, at least one of the modules you had initially installed is defective.

If the memory test continues to report any error, even with a proved RAM module, you probably have a defective motherboard.

Although, and considering this last case, you must not exclude the possibility of having some other faulty hardware like, for instance, the graphics card.

Good luck!

My computer crashes sporadically. My OS isn't an upgrade and I don't use Soundblaster, I use C-Media. Here's what my error report says, maybe someone can help me interpret it:

BCCode : d1     BCP1 : 00000020     BCP2 : 00000002     BCP3 : 00000000    
BCP4 : F62A4B3F     OSVer : 5_1_2600     SP : 1_0     Product : 768_1  

C:\WINDOWS\Minidump\Mini042704-02.dmp
C:\DOCUME~1\Fredric\LOCALS~1\Temp\WER9.tmp.dir00\sysdata.xml

I had this problem "Error code 0000000a = "IRQL_NOT_LESS_OR_EQUAL" - The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS. For additional details see the link to error code 0x0000000a."

If I pull the battery and pull the RAM chips then reinsert both the system would be fine for a month or two.  I think what the problem is that the system is either over heating or I have bad RAM.  Or both.
 
If I don't pull the RAM and the battery but  keep trying to reboot I ended up  corrupting driver and system files and needed to reload from a backup.  I have since bought a laptop cooler and I run a little desk fan. I should just break down and by new RAM as I suspect it's burnt.
But right now it's running fine as long as I keep it cool.
 
That's my experience anyway.

i had the exact same problem and it turned out one of my 512 sticks was defective, never had a prob since

My brand new box suffered from various unpatterned troubles all reporting Event ID 1003 System Error and giving me a real headache.  Then I found this thread and accordingly ran Windows Memory Diagnostic, resulting in the discovery of 18 errors with my only memory module.  Because I wasn't in a position to have a replacement module, I resorted to polishing the gold fingers with a rubber eraser then trying the diagnostics again.  The diagnostics succeeded without error and Event ID 1003 System Error no longer happened.