Hey,

I had always heard that the Blue Screen of Death was a relic of Win 98, and that XP did not have such a problem. However, recently I have been getting the Blue Screen quite often.

In any normal session suddenly a blue screen pops-up and my computer restarts. The contents of the screen are short lived, and the only thing I have been able to make out is the phrase, "Beginning Dump of Physical Memory"

Recently I did install and uninstall a few software. However, the restore points for these changes are lost.

I have a five year old Sony Vaio running Win XP. The computer came with XP SP1 and I added SP2 later. I do not wish to format my computer because,

a) I do not have SP2 (it is a huge download!), and
b) there are some software that I will loose which I do not wish to.

Is there a fix to this problem or will I have to format my computer. Also, is it possible to repair windows registry using old restore cds (which came with my comp and did not have sp2)?

Any and all assistance will be deeply appreciated.

Ari

I had always heard that the Blue Screen of Death was a relic of Win 98, and that XP did not have such a problem.

Hmmm, not sure where you might have heard that, because the BSOD has been a valuable (sometimes) troubleshooting tool for XP since day one.

First, we need to stop it from rebooting so you can see what the BSOD error message and code is. To change the recovery settings to disable Automatic restart:

1. Right-click My Computer and go to Properties > Advanced

2. Under Startup and Recovery, click Settings to open the Startup and Recovery settings menu

3. Under System Failure, uncheck the Automatically restart check box, then click OK as needed to exit out

4. Restart the computer and see what happens

At this point, when/if a fatal error occurs, it should not automatically reboot, but give you the BSOD. This does not fix the problem causing the fatal errors, but it does stop the endless reboot cycle and hopefully allow further troubleshooting.

It is too bad you did not order the free SP2 CD when MS was offering it. Now, you have to pay shipping, or download the file. I assume you have dial up and that is why you do not want to download it. Any friends with broadband? There are no copyright issues with making copies of SP2 or SP3 install files.

I always recommend installing SP2 (and now SP3) from an install program on your computer and not through Windows Update.

Windows XP Service Pack 2 (SP2) - Download and CD

Windows XP SP2 Network Installation Package - download and save to CD
or
Windows XP SP2 on CD, plus shipping and handling (about $3.50 in the US)

Windows XP Service Pack 3 (SP3) - Downloads and CDs

Windows XP Service Pack 3 Network Installation Package for IT Professionals and Developers

Windows XP Service Pack 3 Network - ISO-9660 CD Image File

Windows XP Service Pack 3 on CD - Asia

Windows XP Service Pack 3 on CD - Europe and Africa

Windows XP Service Pack 3 on CD - North America - cost about $10 with shipping.

Windows XP Service Pack 3 on CD - South America

That said, BSODs typically indicate a hardware problem and a 5 year old computer could likely have them.

Is the computer clean of heat trapping dust?

Do all fans spin properly?

Do you know your temperatures?

Inspect the motherboard for bulging or leaking electrolytic capacitors. These failed or failing capacitors are a common cause of sudden, but seemingly random system lock ups and reboots. The capacitors look like tall soda cans, many of which surround the CPU socket. All older motherboards, and many of today's less expensive motherboards use electrolytic capacitors containing a liquid electrolyte. Failing (including flawed and/or abused/over-heated) capacitors literally bulge at the seams due to excessive internal pressures. Extreme (and very rare) cases result in a firecracker type explosion that can really stink up a room. Typically, electrolyte just oozes from the pressure relief points stamped in the tops of the capacitor casings (seen as a symbol or letter). The electrolyte can be caustic to motherboards and flesh. Look for white to dark-brown, dried liquid or foam on the tops or bottoms of the capacitors. Bulging capacitors are a sign leakage is about to occur.

A motherboard with bulging or leaky capacitors can be repaired, but often it is more cost effective in the long run to replace the motherboard.

Just to add: get your dumps and post the logs as seen here:



BSOD
--------------------------------------------------
Read the post HERE for a few diagnostic ideas and post back any relevant data.

Dear Digerati & Jephree,

Thanks for the assistance.

I have ensured that the next time a BSOD occurs my computer will not restart. As soon as the problem occurs again I will note down the details and post them here.

Also, I have installed the debugging tools as asked for by Jephree. As a crash has not happened since the time of my last post, I cannot post a debugwiz log for a Kernal Memory Dump.

However, I did find a lot of minidumps on my machine and I am posting the debugwiz log for the latest minidump created.

Please assist me with the same.

As far as temperature stats are concerned, I have to admit I am unaware of the operating temperature of my machine. However, I have always ensured that my fans are working properly and that my machine is dust free. From time to time I do get my computer serviced from an authorized dealer. Is it time to take it to the cleaners again?

Do you guys believe that this could possibly be a hardware problem? I ask this because a physical clean up by an authorized dealer does not include a software check. I have to ensure the robustness of my software myself. This is essentially because software maintenance generally translates into format and restore as opposed to diagnosing and debugging, and I do not wish to pay for something that I can do on my own !!

I reiterate my gratitude for all the assistance offered.

Thanks,

Ari

Here is my debugwiz log for a latest minidump
------------------------------------------------------------

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini072708-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32 \drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Sun Jul 27 14:44:48.046 2008 (GMT+5)
System Uptime: 0 days 0:12:56.619
Loading Kernel Symbols
.................................................. .................................................. ....................................
Loading User Symbols
Loading unloaded module list
..............
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, 8054d570, a2000000, 84010400}

*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : intelppm.sys ( intelppm+20a0 )

Followup: MachineOwner
---------

kd> !analyze -v;r;kv;lmtn;.logclose;q
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000000
Arg2: 8054d570
Arg3: a2000000
Arg4: 84010400

Debugging Details:
------------------

NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.

This error is documented in the following publication:

- IA-32 Intel(r) Architecture Software Developer's Manual
Volume 3: System Programming Guide

Bit Mask:

MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
32109876543210987654321098765432109876543210987654 32109876543210
----------------------------------------------------------------
10100001111111111111111111111111100001000000000100 00010000000000


VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.

UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.

INTTIMERERR - INTERNAL TIMER ERROR



Concatenated Error Code:
--------------------------
_VAL_UC_INTTIMERERR

This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.

BUGCHECK_STR: 0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 806effaf to 8053354e

SYMBOL_ON_RAW_STACK: 1

STACK_ADDR_RAW_STACK_SYMBOL: ffffffff8054d5fc

STACK_COMMAND: dds 8054D5FC-0x20 ; kb

STACK_TEXT:
8054d5dc 00000000
8054d5e0 805503d0 nt!KiDoubleFaultStack+0x2d50
8054d5e4 00000000
8054d5e8 805503b0 nt!KiDoubleFaultStack+0x2d30
8054d5ec 00000000
8054d5f0 00000002
8054d5f4 00000000
8054d5f8 f774f0a0 intelppm+0x20a0
8054d5fc 00000000
8054d600 00000000
8054d604 00000000
8054d608 002202a1
8054d60c 00000000
8054d610 00000000
8054d614 00000000
8054d618 00000000
8054d61c 00000000
8054d620 00000000
8054d624 00000000
8054d628 00000000
8054d62c 00000000
8054d630 00000000
8054d634 00000000
8054d638 00000000
8054d63c 00000000
8054d640 00000000
8054d644 00000000
8054d648 00000000
8054d64c 00000000
8054d650 00000000
8054d654 00000000
8054d658 00000000


FOLLOWUP_IP:
intelppm+20a0
f774f0a0 6a00 push 0

SYMBOL_NAME: intelppm+20a0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME: intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107b37

FAILURE_BUCKET_ID: 0x9C_GenuineIntel_intelppm+20a0

BUCKET_ID: 0x9C_GenuineIntel_intelppm+20a0

Followup: MachineOwner
---------

eax=ffdff13c ebx=8054d570 ecx=00000000 edx=00000000 esi=84010400 edi=a2000000
eip=8053354e esp=8054d530 ebp=8054d548 iopl=0 nv up di ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000086
nt!KeBugCheckEx+0x1b:
8053354e 5d pop ebp
ChildEBP RetAddr Args to Child
8054d548 806effaf 0000009c 00000000 8054d570 nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo])
8054d674 806eccae 80042000 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd (FPO: [Non-Fpo])
8054d674 00000000 80042000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x46 (FPO: TSS f10f10:0)
start end module name
804d7000 806eb500 nt ntoskrnl.exe Wed Feb 28 14:40:41 2007 (45E54711)
806ec000 806ffd80 hal halacpi.dll Wed Aug 04 11:29:04 2004 (41107B28)
bf800000 bf9c2180 win32k win32k.sys Thu Mar 08 19:17:34 2007 (45F013F6)
bf9c3000 bf9d4580 dxg dxg.sys Wed Aug 04 11:30:51 2004 (41107B93)
bf9d5000 bfa10000 ati2dvag ati2dvag.dll Thu Jan 20 08:55:56 2005 (41EF24C4)
bfa10000 bfa4d000 ati2cqag ati2cqag.dll Thu Jan 20 08:25:56 2005 (41EF1DBC)
bfa4d000 bfa7f000 atikvmag atikvmag.dll Wed Mar 23 07:59:47 2005 (4240D49B)
bfa7f000 bfcaf440 ati3duag ati3duag.dll Wed Mar 23 08:17:12 2005 (4240D8B0)
bfcb0000 bfd44ba0 ativvaxx ativvaxx.dll Wed Mar 23 08:11:05 2005 (4240D741)
bffa0000 bffe5c00 ATMFD ATMFD.DLL Wed Aug 04 13:26:56 2004 (411096C8)
efc77000 efca1180 kmixer kmixer.sys Wed Jun 14 14:17:45 2006 (448FCD31)
eff4a000 eff8a280 HTTP HTTP.sys Fri Mar 17 06:03:09 2006 (441A03C5)
f020b000 f025c480 srv srv.sys Mon Aug 14 16:04:39 2006 (44E051BF)
f055b000 f056f400 wdmaud wdmaud.sys Wed Jun 14 14:30:44 2006 (448FD03C)
f0598000 f05c3d80 mrxdav mrxdav.sys Tue Dec 18 1533 2007 (47679825)
f05f4000 f05fe000 secdrv secdrv.sys Wed Sep 13 18:48:32 2006 (45080528)
f0688000 f068a6c0 mdmxsdk mdmxsdk.sys Wed Dec 11 23:52:03 2002 (3DF7824B)
f072c000 f073ad80 sysaudio sysaudio.sys Wed Aug 04 11:45:54 2004 (41107F1A)
f08fc000 f08ff280 ndisuio ndisuio.sys Wed Aug 04 11:33:10 2004 (41107C1E)
f29fc000 f2a13480 dump_atapi dump_atapi.sys Wed Aug 04 11:29:41 2004 (41107B4D)
f2a3c000 f2b04a60 avg7core avg7core.sys Wed Oct 10 21:53:39 2007 (470CFC8B)
f2ba5000 f2bc5f00 ipnat ipnat.sys Thu Sep 30 03:58:36 2004 (415B3714)
f2bc6000 f2c34a00 mrxsmb mrxsmb.sys Fri May 05 15:11:42 2006 (445B1DD6)
f2c35000 f2c5fa00 rdbss rdbss.sys Fri May 05 15:17:55 2006 (445B1F4B)
f2c60000 f2c81d00 afd afd.sys Wed Aug 04 11:44:13 2004 (41107EB5)
f2c82000 f2ca9c00 netbt netbt.sys Wed Aug 04 11:44:36 2004 (41107ECC)
f2caa000 f2d01e80 tcpip tcpip.sys Tue Oct 30 22:50:52 2007 (472767F4)
f2d02000 f2d14400 ipsec ipsec.sys Wed Aug 04 11:44:27 2004 (41107EC3)
f6daa000 f6dac900 Dxapi Dxapi.sys Sat Aug 18 02:23:19 2001 (3B7D843F)
f6dc6000 f6e1ee80 update update.sys Mon Apr 23 16:02:54 2007 (462C8B56)
f6e1f000 f6e2fe00 psched psched.sys Wed Aug 04 11:34:16 2004 (41107C60)
f6ed0000 f6ee6680 ndiswan ndiswan.sys Wed Aug 04 11:44:30 2004 (41107EC6)
f6ee7000 f6f09e80 USBPORT USBPORT.SYS Wed Aug 04 11:38:34 2004 (41107D62)
f6f0a000 f6f1d900 parport parport.sys Wed Aug 04 11:29:04 2004 (41107B28)
f6f1e000 f6f342e0 Apfiltr Apfiltr.sys Tue Jun 10 18:05:58 2003 (3EE5D0AE)
f6f35000 f6f57680 ks ks.sys Wed Aug 04 11:45:20 2004 (41107EF8)
f6f58000 f6f7b980 portcls portcls.sys Wed Aug 04 11:45:47 2004 (41107F13)
f6f7c000 f7009300 smwdm smwdm.sys Wed May 28 02:35:41 2003 (3ED3D325)
f700a000 f70a2000 HSF_CNXT HSF_CNXT.sys Tue Mar 18 18:16:47 2003 (3E771537)
f70a2000 f71b0480 HSF_DP HSF_DP.sys Tue Mar 18 18:15:30 2003 (3E7714EA)
f71b1000 f71d8500 HSFHWALI HSFHWALI.sys Tue Mar 18 18:18:02 2003 (3E771582)
f71d9000 f71ec780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 11:37:04 2004 (41107D08)
f71ed000 f72e1000 ati2mtag ati2mtag.sys Thu Jan 20 08:55:36 2005 (41EF24B0)
f72e9000 f72eb280 rasacd rasacd.sys Sat Aug 18 02:25:39 2001 (3B7D84CB)
f733a000 f7354580 Mup Mup.sys Wed Aug 04 11:45:20 2004 (41107EF8)
f7355000 f7381a80 NDIS NDIS.sys Wed Aug 04 11:44:27 2004 (41107EC3)
f7382000 f740e400 Ntfs Ntfs.sys Fri Feb 09 16:40:31 2007 (45CC56A7)
f740f000 f7425780 KSecDD KSecDD.sys Wed Aug 04 11:29:45 2004 (41107B51)
f7426000 f7437f00 sr sr.sys Wed Aug 04 11:36:22 2004 (41107CDE)
f7438000 f7439000 fltmgr fltmgr.sys unavailable (00000000)
f7458000 f746f480 atapi atapi.sys Wed Aug 04 11:29:41 2004 (41107B4D)
f7470000 f748e880 ftdisk ftdisk.sys Sat Aug 18 02:22:41 2001 (3B7D8419)
f748f000 f74ac480 pcmcia pcmcia.sys Wed Aug 04 11:37:45 2004 (41107D31)
f74ad000 f74bda80 pci pci.sys Wed Aug 04 11:37:45 2004 (41107D31)
f74be000 f74ebd80 ACPI ACPI.sys Wed Aug 04 11:37:35 2004 (41107D27)
f750d000 f7515c00 isapnp isapnp.sys Sat Aug 18 02:28:01 2001 (3B7D8559)
f751d000 f752be80 ohci1394 ohci1394.sys Wed Aug 04 11:40:05 2004 (41107DBD)
f752d000 f753a000 1394BUS 1394BUS.SYS Wed Aug 04 11:40:03 2004 (41107DBB)
f753d000 f7547500 MountMgr MountMgr.sys Wed Aug 04 11:28:29 2004 (41107B05)
f754d000 f7559c80 VolSnap VolSnap.sys Wed Aug 04 11:30:14 2004 (41107B6E)
f755d000 f7565e00 disk disk.sys Wed Aug 04 11:29:53 2004 (41107B59)
f756d000 f7579200 CLASSPNP CLASSPNP.SYS Wed Aug 04 11:44:26 2004 (41107EC2)
f757d000 f7585b80 PxHelp20 PxHelp20.sys Sat Feb 03 02:53:57 2007 (45C3ABED)
f759d000 f75ac180 nic1394 nic1394.sys Wed Aug 04 11:28:28 2004 (41107B04)
f75ad000 f75b7380 imapi imapi.sys Wed Aug 04 11:30:12 2004 (41107B6C)
f75bd000 f75c9180 cdrom cdrom.sys Wed Aug 04 11:29:52 2004 (41107B58)
f75cd000 f75db080 redbook redbook.sys Wed Aug 04 11:29:34 2004 (41107B46)
f75dd000 f75e8780 R8139n51 R8139n51.SYS Fri Oct 04 07:34:08 2002 (3D9CF718)
f75ed000 f75f9880 rasl2tp rasl2tp.sys Wed Aug 04 11:44:21 2004 (41107EBD)
f75fd000 f7607200 raspppoe raspppoe.sys Wed Aug 04 11:35:06 2004 (41107C92)
f760d000 f7618d00 raspptp raspptp.sys Wed Aug 04 11:44:26 2004 (41107EC2)
f761d000 f7625900 msgpc msgpc.sys Wed Aug 04 11:34:11 2004 (41107C5B)
f762d000 f7636f00 termdd termdd.sys Wed Aug 04 11:28:52 2004 (41107B1C)
f763d000 f7646480 NDProxy NDProxy.SYS Sat Aug 18 02:25:30 2001 (3B7D84C2)
f768d000 f769b100 usbhub usbhub.sys Wed Aug 04 11:38:40 2004 (41107D68)
f769d000 f76a5700 netbios netbios.sys Wed Aug 04 11:33:19 2004 (41107C27)
f76bd000 f76c5880 Fips Fips.SYS Sat Aug 18 07:01:49 2001 (3B7DC585)
f76cd000 f76d5700 wanarp wanarp.sys Wed Aug 04 11:34:57 2004 (41107C89)
f76dd000 f76ebd80 arp1394 arp1394.sys Wed Aug 04 11:28:28 2004 (41107B04)
f76ed000 f76f5d80 HIDCLASS HIDCLASS.SYS Wed Aug 04 11:38:18 2004 (41107D52)
f76fd000 f770c900 Cdfs Cdfs.SYS Wed Aug 04 11:44:09 2004 (41107EB1)
f774d000 f7755d00 intelppm intelppm.sys Wed Aug 04 11:29:19 2004 (41107B37)
f775d000 f776bb80 drmk drmk.sys Wed Aug 04 11:37:54 2004 (41107D3A)
f776d000 f7779e00 i8042prt i8042prt.sys Wed Aug 04 11:44:36 2004 (41107ECC)
f777d000 f7785040 SonyWBMS SonyWBMS.SYS Mon Nov 18 11:42:02 2002 (3DD884B2)
f778d000 f7793200 PCIIDEX PCIIDEX.SYS Wed Aug 04 11:29:40 2004 (41107B4C)
f7795000 f7799900 PartMgr PartMgr.sys Sat Aug 18 07:02:23 2001 (3B7DC5A7)
f779d000 f77a2bc0 atisgkaf atisgkaf.sys Fri Aug 30 02:27:14 2002 (3D6E8AAA)
f77bd000 f77c1500 watchdog watchdog.sys Wed Aug 04 11:37:32 2004 (41107D24)
f77fd000 f7802780 strmdisp strmdisp.sys Tue Mar 18 18:20:01 2003 (3E7715F9)
f783d000 f7843780 USBSTOR USBSTOR.SYS Wed Aug 04 11:38:44 2004 (41107D6C)
f7865000 f786c580 Modem Modem.SYS Wed Aug 04 11:38:04 2004 (41107D44)
f786d000 f7872a00 mouclass mouclass.sys Wed Aug 04 11:28:32 2004 (41107B08)
f7875000 f787b000 kbdclass kbdclass.sys Wed Aug 04 11:28:32 2004 (41107B08)
f787d000 f7882020 SonyNC SonyNC.sys Thu Nov 09 15:45:07 2000 (3A0A792B)
f7885000 f788a000 usbuhci usbuhci.sys Wed Aug 04 11:38:34 2004 (41107D62)
f788d000 f7893800 usbehci usbehci.sys Wed Aug 04 11:38:34 2004 (41107D62)
f7895000 f789c000 GEARAspiWDM GEARAspiWDM.sys Mon Aug 07 22:41:27 2006 (44D7743F)
f789d000 f78a1880 TDI TDI.SYS Wed Aug 04 11:37:47 2004 (41107D33)
f78a5000 f78a9580 ptilink ptilink.sys Sat Aug 18 02:19:53 2001 (3B7D8371)
f78ad000 f78b1080 raspti raspti.sys Sat Aug 18 02:25:32 2001 (3B7D84C4)
f78b5000 f78b9c40 RadProbe RadProbe.sys Wed Apr 27 09:16:55 2005 (426F0B2F)
f78dd000 f78e3180 HIDPARSE HIDPARSE.SYS Wed Aug 04 11:38:15 2004 (41107D4F)
f78e5000 f78ea200 vga vga.sys Wed Aug 04 11:37:06 2004 (41107D0A)
f78ed000 f78ee000 Msfs Msfs.SYS unavailable (00000000)
f78f5000 f78fc880 Npfs Npfs.SYS Wed Aug 04 11:30:38 2004 (41107B86)
f7905000 f790bc80 avg7rsxp avg7rsxp.sys Tue Jan 30 20:38:42 2007 (45BF5F7A)
f791d000 f7920000 BOOTVID BOOTVID.dll Sat Aug 18 02:19:09 2001 (3B7D8345)
f7921000 f7923480 compbatt compbatt.sys Sat Aug 18 02:27:58 2001 (3B7D8556)
f7925000 f7928700 BATTC BATTC.SYS Sat Aug 18 02:27:52 2001 (3B7D8550)
f7929000 f792bd80 ACPIEC ACPIEC.sys Sat Aug 18 02:27:55 2001 (3B7D8553)
f79b9000 f79bb580 hidusb hidusb.sys Sat Aug 18 02:32:16 2001 (3B7D8658)
f79bd000 f79bff80 mouhid mouhid.sys Sat Aug 18 02:17:57 2001 (3B7D82FD)
f79e5000 f79e8700 CmBatt CmBatt.sys Wed Aug 04 11:37:39 2004 (41107D2B)
f79e9000 f79eb580 ndistapi ndistapi.sys Sat Aug 18 02:25:29 2001 (3B7D84C1)
f79f9000 f79fcc80 mssmbios mssmbios.sys Wed Aug 04 11:37:47 2004 (41107D33)
f7a0d000 f7a0eb80 kdcom kdcom.dll Sat Aug 18 02:19:10 2001 (3B7D8346)
f7a0f000 f7a10100 WMILIB WMILIB.SYS Sat Aug 18 02:37:23 2001 (3B7D878B)
f7a11000 f7a12480 aliide aliide.sys Sat Aug 18 0254 2001 (3B7D83EA)
f7a41000 f7a42120 aeaudio aeaudio.sys Mon Apr 01 20:09:14 2002 (3CA87112)
f7a43000 f7a44100 swenum swenum.sys Wed Aug 04 11:28:41 2004 (41107B11)
f7a47000 f7a48280 USBD USBD.SYS Sat Aug 18 02:32:58 2001 (3B7D8682)
f7a49000 f7a4a000 Fs_Rec Fs_Rec.SYS unavailable (00000000)
f7a4b000 f7a4c080 Beep Beep.SYS Sat Aug 18 02:17:33 2001 (3B7D82E5)
f7a4d000 f7a4e080 mnmdd mnmdd.SYS Sat Aug 18 02:27:28 2001 (3B7D8538)
f7a4f000 f7a50080 RDPCDD RDPCDD.sys Sat Aug 18 02:16:56 2001 (3B7D82C0)
f7a51000 f7a52080 avg7rsw avg7rsw.sys Tue Jul 26 17:40:51 2005 (42E6284B)
f7a61000 f7a62100 dump_WMILIB dump_WMILIB.SYS Sat Aug 18 02:37:23 2001 (3B7D878B)
f7ab5000 f7ab6a80 ParVdm ParVdm.SYS Sat Aug 18 02:19:49 2001 (3B7D836D)
f7ad5000 f7ad5d80 OPRGHDLR OPRGHDLR.SYS Sat Aug 18 02:27:55 2001 (3B7D8553)
f7afe000 f7afed00 dxgthk dxgthk.sys Sat Aug 18 02:23:12 2001 (3B7D8438)
f7b66000 f7b66c00 audstub audstub.sys Sat Aug 18 02:29:40 2001 (3B7D85BC)
f7be7000 f7be7980 Cdr4_xp Cdr4_xp.SYS Wed Aug 10 23:58:07 2005 (42FA4737)
f7be9000 f7be9a00 Cdralw2k Cdralw2k.SYS Wed Aug 10 23:58:04 2005 (42FA4734)
f7bea000 f7beb000 Null Null.SYS unavailable (00000000)
f7bec000 f7bed000 avgclean avgclean.sys Mon Dec 03 17:39:01 2007 (4753F1DD)
f7bff000 f7bffde0 DMICall DMICall.sys Tue Dec 05 12:44:23 2000 (3A2C95CF)

Unloaded modules:
f050d000 f0538000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7c5e000 f7c5f000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f06fc000 f0709000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f0538000 f055b000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f070c000 f071a000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7abd000 f7abf000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f6e30000 f6e40000 Serial.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f76ad000 f76b6000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f72ed000 f72f1000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f78d5000 f78da000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f78cd000 f78d2000 Flpydisk.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f78c5000 f78cc000 Fdc.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b65000 f7b66000 Cdralw2k.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b64000 f7b65000 Cdr4_xp.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

However, I have always ensured that my fans are working properly and that my machine is dust free. From time to time I do get my computer serviced from an authorized dealer. Is it time to take it to the cleaners again?

That's great. I generally recommend popping the side off the case and doing a "visual" inspection monthly, and clean when necessary. If the CPU fan fins are clogged, it's time to clean. And don't forget to inspect for leaky capacitors. I note one of the dangers of cleaning (especially if you have to transport it to be cleaned) is that something can be knocked or otherwise worked itself loose while being jostled about. So I always make sure all connectors are tightly fastened, including the motherboard power and data cables (touching bare metal first to discharge static).

Do you guys believe that this could possibly be a hardware problem?

As mentioned above, "BSODs typically indicate a hardware problem and a 5 year old computer could likely have them." My eyes and mindset don't take to analyzing logs but I note you had a Stop 9C error - this also suggests hardware.

software maintenance generally translates into format and restore

No, it doesn't. Formatting is ALWAYS a last resort option and should be avoided if at all possible. Not withstanding the loss of data, security is set back months or even years and is often left exposed in that state until ant-malware and intrusion defenses are established and the system is patched and updated. There are always other things to check and try before resorting to a format.

I do not wish to pay for something that I can do on my own !!

I don't blame you. But then, if you have a technician you can trust taking too, it is always nice to be able to hold someone else liable for any collateral damage!

Have you recently made any hardware changes?

I would test the RAM using one of the following programs. Both require you to create and boot to a bootable floppy disk or CD to run the diagnostics. Using the floppy method is generally easier and yet another reason I still include floppy drives in my new PC builds. However, the CD method is just as effective at detecting RAM problems. Allow the diagnostics to run for several passes or even overnight. You should have no reported errors.

Windows Memory Diagnostic - see the easy to follow instructions under Quick Start Information.
or
MemTest86+ (for more advanced users) - an excellent how-to guide is available here.

Just to add:

That dump was on the CPU. INTERNAL TIMER ERROR

NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.

0x0000009C: MACHINE_CHECK_EXCEPTION
(Click to consult the online MSDN article.)
This is a hardware issue: an unrecoverable hardware error has occurred. The parameters have different meanings depending on what type of CPU you have but, while diagnostic, rarely lead to a clear solution. Most commonly it results from overheating, from failed hardware (RAM, CPU, hardware bus, power supply, etc.), or from pushing hardware beyond its capabilities (e.g., overclocking a CPU).

Stop error message in Windows XP that you may receive: "0x0000009C (0x00000004, 0x00000000, 0xb2000000, 0x00020151)"


Monitoring your temperature on the CPU would help.

SpeedFan - Access temperature sensor in your computer


As mentioned running MemTest is also a good idea.

If your dumps continue to be the same and point out your CPU as the above does you might want to remove the heatsink and clean the old thermal material and add a new application.

http://www.d-a-l.com/help/general-ha...-material.html

These logs are most telling in comparison so if you get more please post them.

STACK_COMMAND: dds 8054D5FC-0x20 ; kb

STACK_TEXT:
8054d5dc 00000000
8054d5e0 805503d0 nt!KiDoubleFaultStack+0x2d50
8054d5e4 00000000
8054d5e8 805503b0 nt!KiDoubleFaultStack+0x2d30
8054d5ec 00000000
8054d5f0 00000002
8054d5f4 00000000
8054d5f8 f774f0a0 intelppm+0x20a0
8054d5fc 00000000
8054d600 00000000
8054d604 00000000
8054d608 002202a1
8054d60c 00000000
8054d610 00000000
8054d614 00000000
8054d618 00000000
8054d61c 00000000
8054d620 00000000
8054d624 00000000
8054d628 00000000
8054d62c 00000000
8054d630 00000000
8054d634 00000000
8054d638 00000000
8054d63c 00000000
8054d640 00000000
8054d644 00000000
8054d648 00000000
8054d64c 00000000
8054d650 00000000
8054d654 00000000
8054d658 00000000

As pointed out that was an "Idle" failure i.e. the CPU stopped responding to commands.



...