Memory read/write exceptions.. problem may be motherboard.

I run broadcasting software on a dedicated machine (SAM Broadcaster - SAMBC.exe) and I also run kwakkelflap's watchdog-o-matic program to monitor SAM, restart SAM when it crashes or freezes, etc.)..

Every day or so, the watchdog program will show debug messages (first-chance exceptions, then second-chance exceptions) concerning SAM... for instance here's a snippet of the messages:
=========================================
11/12/2008 09:46:05 : SAMBC.exe (2776): first chance exception: Access Violation. The instruction at 0x0000656D referenced memory at 0x0000656D. The memory could not be read.
11/12/2008 02:06:44 : SAMBC.exe (1504): first chance exception: Access Violation. The instruction at 0x0041BF38 referenced memory at 0x00000000. The memory could not be written.
11/12/2008 02:06:42 : SAMBC.exe (1504): first chance exception: Access Violation. The instruction at 0x00401FCF referenced memory at 0x595AC033. The memory could not be read.
11/12/2008 02:06:39 : SAMBC.exe (1504): first chance exception: Access Violation. The instruction at 0x004022F4 referenced memory at 0x595AC067. The memory could not be written.
11/12/2008 02:06:35 : SAMBC.exe (1504): first chance exception: Access Violation. The instruction at 0x0040250C referenced memory at 0x1C5F923A. The memory could not be read.
11/12/2008 02:06:35 : SAMBC.exe (1504): first chance exception: Access Violation. The instruction at 0x00401D6B referenced memory at 0x90152D18. The memory could not be written.
11/12/2008 02:06:34 : SAMBC.exe (1504): first chance exception: Access Violation. The instruction at 0x00296E77 referenced memory at 0x143F2410. The memory could not be written.
11/12/2008 02:06:34 : SAMBC.exe (1504): first chance exception: Access Violation. The instruction at 0x0047DB45 referenced memory at 0xFAF0F63C. The memory could not be read.
11/11/2008 04:34:00 : SAMBC.exe (1504): first chance exception: Access Violation. The instruction at 0x0000656E referenced memory at 0x0000656E. The memory could not be read.
11/11/2008 04:34:00 : SAMBC.exe (1504): first chance exception: Access Violation. The instruction at 0x0341E8FC referenced memory at 0x7C931C41. The memory could not be written.

==========================================

In a nutshell the following addresses had read errors:
instruction (0x0000656D) ==> memory (0x0000656D)
instruction (0x00401FCF) ==> memory (0x595AC033)
instruction (0x0040250C) ==> memory (0x1C5F923A)
instruction (0x0047DB45) ==> memory (0xFAF0F63C)
instruction (0x0000656E) ==> memory (0x0000656E)


And the following addresses had write errors:
instruction (0x0041BF38) ==> memory (0x00000000)
instruction (0x004022F4) ==> memory (0x595AC067)
instruction (0x00401D6B) ==> memory (0x90152D18)
instruction (0x00296E77) ==> memory (0x143F2410)
instruction (0x0341E8FC) ==> memory (0x7C931C41)


After a few of these, a day will pass then all of a sudden there are thousands of them. Then my SAM program crashes.

First I thought it was a memory problem but I checked my brand new memory in memtest86+ and the test results came back normal. The only thing left to check was the motherboard.

I know nothing about addresses or ports so i decided to look into it. In the first chance exception messages the address 0x0000656D is referenced.

I used a motherboard diagnostic program and it looks like that address refers to the PCI Bus. See the attachment bookmark2.jpg
Drop.io SAM_SUPPORT_ELLIOTT benchmark2

You can also see the other files related to this issue at Drop.io SAM_SUPPORT_ELLIOTT

So If I'm reading this right, the addresses in the first chance exception messages correspond to the same I/O Ports in the Motherboard Diagnostic program.

READ Errors
------------------------
instruction (0x0000656D) ==> memory (0x0000656D) = Instruction(PCI BUS) & Memory (PCI BUS)
instruction (0x00401FCF) ==> memory (0x595AC033) = Instruction(???) & Memory (PCI BUS)
instruction (0x0040250C) ==> memory (0x1C5F923A) = Instruction(???) & Memory (???)
instruction (0x0047DB45) ==> memory (0xFAF0F63C) = Instruction(???) & Memory (PCI BUS)
instruction (0x0000656E) ==> memory (0x0000656E) = Instruction(PCI BUS) & Memory (PCI BUS)

WRITE Errors
------------------------
instruction (0x0041BF38) ==> memory (0x00000000) = Instruction(???) & Memory (PCI BUS)
instruction (0x004022F4) ==> memory (0x595AC067) = Instruction(???) & Memory (PCI BUS)
instruction (0x00401D6B) ==> memory (0x90152D18) = Instruction(???) & Memory (PCI BUS)
instruction (0x00296E77) ==> memory (0x143F2410) = Instruction(???) & Memory (???)
instruction (0x0341E8FC) ==> memory (0x7C931C41) = Instruction(???) & Memory (PCI BUS)


The question marks denote addresses that I was unable to match with any I/O port designation. So If I am infact reading this right and coming to these conclusions that the problems are majorily caused by the PCI BUS, What's my next step?

Do I need new cables? Do I need to have the motherboard replaced? How can I stop these problems from occuring.

BTW My system specs are:

Intel Pentium4 3.2GHz 1GB DDR RAM (corsair) Windows XP Home SP2


I appreciate any help you can give to get me pointed in the right direction!

Thanks,

Elliott
[email protected]

 

Is this watch dog program the only thing throwing up errors?

 

Watchdog isn't throwing the errors, it's showing the errors.