XP dropping question

[tim]

I've had sb.exe running for months on an XP machine, and suddenly I get the windows message "sb.exe has encountered a problem and needs to close."

Windows gives the following info:
Error signature:
AppName: sb.exe AppVer: 0.0.0.0 ModName: sb.exe
ModVer: 0.0.0.0 Offset: 0008a3ad

The file it wants to send as debug info to Microsoft:
<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="sb.exe" FILTER="GRABMI_FILTER_PRIVACY">
<MATCHING_FILE NAME="sb.exe" SIZE="439296" CHECKSUM="0x3C2FFF03" MODULE_TYPE="WIN32" PE_CHECKSUM="0x749F7" LINKER_VERSION="0x0" LINK_DATE="09/04/2005 20:51:12" UPTO_LINK_DATE="09/04/2005 20:51:12" />
<MATCHING_FILE NAME="sobsvc.exe" SIZE="73728" CHECKSUM="0x1D861AB5" BIN_FILE_VERSION="1.6.0.1" BIN_PRODUCT_VERSION="1.6.0.1" PRODUCT_VERSION="1, 6, 0, 1" FILE_DESCRIPTION="SOB Client Service Executable" COMPANY_NAME="Seventeen or Bust" PRODUCT_NAME="SOB Client Service Executable" FILE_VERSION="1, 6, 0, 1" ORIGINAL_FILENAME="sobsvc.exe" INTERNAL_NAME="sobsvc" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.6.0.1" UPTO_BIN_PRODUCT_VERSION="1.6.0.1" LINK_DATE="01/27/2004 14:56:47" UPTO_LINK_DATE="01/27/2004 14:56:47" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="sobsvc9x.exe" SIZE="61440" CHECKSUM="0x6CE64CD5" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="01/27/2004 14:56:58" UPTO_LINK_DATE="01/27/2004 14:56:58" />
<MATCHING_FILE NAME="uninst.exe" SIZE="33512" CHECKSUM="0xB8CA60C8" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="03/19/2005 13:58:02" UPTO_LINK_DATE="03/19/2005 13:58:02" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="984576" CHECKSUM="0xF0B331F6" BIN_FILE_VERSION="5.1.2600.3119" BIN_PRODUCT_VERSION="5.1.2600.3119" PRODUCT_VERSION="5.1.2600.3119" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.3119 (xpsp_sp2_gdr.070416-1301)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xF9293" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.3119" UPTO_BIN_PRODUCT_VERSION="5.1.2600.3119" LINK_DATE="04/16/2007 15:52:53" UPTO_LINK_DATE="04/16/2007 15:52:53" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>

The error report contents it wouldn't let me cut and paste, but the first thing it showed was Exception Information:
Code: 0xc0000005
Flags: 0x00000000
Record: 0x0000000000000000
Address: 0x000000000048a3ad

It's died like that several times in the last few days. Any suggestions?

[Joe O]

snip
It's died like that several times in the last few days. Any suggestions?

Open your computer up and clean off the dust from the heatsink and fan. Make sure that none of the case vent holes are clogged.

[umccullough]

Probably a good time to run memtest86+ also...

[gopher_yarrowzoo]

I've had that, closed it down, restarted it no problem - I think it was due to the fact I was running a remote logger to see who the SoB client was doing.
Mind you said machine is now down due to the PSU being :Pokes: dead.