Reboot, reboot and reboot.

That CPU core voltage may be low as well.

Let's please take a look in the Computer > Summary section of EVEREST.

Right-click in a blank area of the Summary window and select "Copy All ". This will copy the displayed information to your Clipboard.

Then paste the contents of your Clipboard into your next message.

 

Here is the report from Computer > Summary:

Field Value
Computer
Operating System Microsoft Windows XP Home Edition
OS Service Pack Service Pack 2
DirectX 4.09.00.0904 (DirectX 9.0c)
Computer Name SK
User Name KA

Motherboard
CPU Type DualCore Intel Pentium D 820, 2800 MHz (14 x 200)
Motherboard Name Unknown
Motherboard Chipset ATI Radeon Xpress 200
System Memory 2048 MB (DDR2-667 DDR SDRAM)
BIOS Type Intel (01/30/07)
Communication Port ECP 印表機連接埠 (LPT1)

Multimedia
Audio Adapter ATI SB450 - High Definition Audio Controller
Audio Adapter C-Media CMI8738/C3DX Audio Device

Storage
IDE Controller 標準雙通道 PCI IDE 控制器
IDE Controller 標準雙通道 PCI IDE 控制器
IDE Controller 標準雙通道 PCI IDE 控制器
Disk Drive ST3160811AS (149 GB, IDE)
Disk Drive Generic USB SD Reader USB Device
Disk Drive Generic USB MS Reader USB Device
Disk Drive Generic USB SM Reader USB Device
Disk Drive Generic USB CF Reader USB Device
Disk Drive WDC WD2500YS-01SHB1 (233 GB, IDE)
Optical Drive LITE-ON DVDRW LH-16W1P
SMART Hard Disks Status OK

Partitions
C: (NTFS) 152617 MB (149092 MB free)
D: (NTFS) 239359 MB (228432 MB free)
Total Size 382.8 GB (368.7 GB free)

Input
Keyboard 標準 101/102 鍵或 Microsoft Natural PS/2 鍵盤
Mouse PS/2 相容滑鼠

Network
Network Adapter Realtek RTL8139 Family PCI Fast Ethernet NIC (169.254.9.100)
Network Adapter WAN (PPP/SLIP) Interface (203.218.168.132)

Peripherals
USB1 Controller ATI SB450 - USB Controller
USB1 Controller ATI SB450 - USB Controller
USB2 Controller ATI SB450 - USB 2.0 Controller
USB Device USB Mass Storage Device

 

Hi, thiefng. Thanks for posting that additional information.

According to this Intel document, it appears the recommended core voltage range for your processor is 1.25V-1.4V. Therefore, I am inclined to think your reported CPU core voltage (0.88V) is too low and that might be causing your crashes.

I am curious about what CPU core voltage might be reported in your BIOS. (EVEREST numbers are not always accurate.) Are you familiar with accessing/using the BIOS?

Since you stated your system is new, if it is still in warranty and the BIOS also reports the core voltage is out of range, then I would suggest you take your computer box to the retailer that sold it to you and have them make adjustments AND have them replace your CPU fan. (Show them copies of your EVEREST reports and a copy of the Intel document I linked in this message.)

If the computer is out of warranty and/or you feel confident/adventurous enough to try adjusting the CPU core voltage, then I expect you can easily adjust the CPU core voltage in your BIOS to be within the specified range.

CAUTION: Keep in mind, changing BIOS settings can potentially have serious consequences. Let's wait to see what surferdude (or another HW expert) says. He's much more familiar with hardware issues than I am and I do not want to feel in any way responsible for causing you to fry your system or make it unbootable if such an unfortunate occurrence occurs.



EDIT: I removed statements about EVEREST not being able to identify the motherboard. (See my post below.)

 

Since you stated:

If the dealer that sold you this box did all that for you, by all means take it back to him for another look.

If instead you performed the work with him providing the parts, then I would be concerned about the following:

All of your info so far still points 90% to a hardware problem - processor or memory most likely with power supply and overheat still in the mix. Of the remaining cases, viral and software are equally split.

Have you tried testing in Safe Mode to see if the problem occurs there as well? If it doesn't, try a minimal software load boot by trimming the startups to the absolute minimum. You can do that with msconfig quite easily. Then check in Task Manager to see how much processor activity is going in when you sit idle for extended periods. If it still crashes, you're back to hardware problems as being the root cause.

Hardware problems are often challenging to diagnose without substitute gear for testing.

You are getting in a bit deep if this box is in warranty so keep that in mind. I also am concerned about your posted experience level versus how much advice to give lest I lead you to disaster.

 

mailman asked me to take a look at this and although I don't know Intel products like I should, there are few oddities that have already been pointed out.

Perhaps in summation, the processor and the heatsink parted company but no thermal paste was applied when they got reunited. This is problematic and not only creates the potential for fast frying, it can do a lot of other damage thats often not easy to trace. The fact that you are running at 0.88V as a core voltage is either grossly inaccurate or indicative of a PSU, Motherboard or Processor problem. It would be nice to get a reading from your BIOS as has been requested. One concern would be that your CPU is trying to cool down by regulating its own voltage but again, I don't know enough about Intel to know if they even work this way.

Now, if you can get some other kind of reading on that CPU voltage and if you would yank the heatsink and spread some thermal compound on it and reseat it, we might be able to try a few other things. And, as SD2 has suggested, you might get some relief from the shop that has helped you previously (assuming you had some help).

Aside from that (and I know I haven't added anything new) I'm not sure just what to tell you.

Good Luck

 

thiefng, I took a closer look at your EVEREST Sensor report output and figured out what motherboard you have.

And, from your EVEREST Summary report:

*According to this Intel "BIOS Update Release Notes" PDF document, you apparently already have the latest BIOS version currently available for your motherboard.

I am including the following link so it is handy in case anyone following this thread needs/wants to refer to it.

• Intel® Desktop Board D102GGC2 Overview
  (includes links to technical docs, support, tools & software, etc.)

 

Thx again for all of your valuable inputs.

As mailman and surferdude2 said that the running voltage of the CPU may be lower than normal, I search the intel website and found the following documents:

http://www.intel.com/support/processors/pentiumd/sb/cs-021754.htm &
http://support.microsoft.com/default.aspx?scid=kb;en-us;896256http://support.microsoft.com/default.aspx?scid=kb;en-us;896256

Could it be feasible to try to download the fix and run on my PC?

 

It's disappointed that the above fix cannot fix the problem...

After I installed the fix and reboot, the system hang and reboot itself again, the log is attached for reference:

Opened log file 'c:\debuglog.txt'

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


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.061030-0016
Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055d700
Debug session time: Sat Jun 23 11:34:55.390 2007 (GMT+8)
System Uptime: 0 days 0:02:16.093
Loading Kernel Symbols
..............................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {a718, 2, 1, 804e9851}

*** ERROR: Module load completed but symbols could not be loaded for avg7rsxp.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for avg7rsw.sys -
Probably caused by : avg7rsxp.sys ( avg7rsxp+1915 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000a718, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804e9851, address which referenced memory

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


WRITE_ADDRESS: 0000a718

CURRENT_IRQL: 2

FAULTING_IP:
nt!CcGetVirtualAddress+9d
804e9851 890a mov dword ptr [edx],ecx

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 8056a1a5 to 804e9851

STACK_TEXT:
bacdb850 8056a1a5 009a25c0 0033c000 00000000 nt!CcGetVirtualAddress+0x9d
bacdb8b8 ba6827cb 89a05f28 bacdb8e8 00000400 nt!CcMapData+0x8b
bacdb8d8 ba6829e7 8969b440 899a4008 0033c000 Ntfs!NtfsMapStream+0x46
bacdb94c ba6828f4 8969b440 899a5100 e1480280 Ntfs!NtfsReadMftRecord+0x86
bacdb984 ba68284a 8969b440 899a5100 e1480280 Ntfs!NtfsReadFileRecord+0x7a
bacdb9bc ba686f05 8969b440 e1480278 e1480280 Ntfs!NtfsLookupInFileRecord+0x37
bacdba94 ba686dd6 8969b440 e1480340 bacdbb58 Ntfs!NtfsWriteFileSizes+0x76
bacdbb7c ba686e2f 8969b440 8987a648 896ea008 Ntfs!NtfsSetEndOfFileInfo+0xaa
bacdbbec ba65fad8 8969b440 896ea008 896ea008 Ntfs!NtfsCommonSetInformation+0x477
bacdbc54 804f0095 899a5020 896ea008 896ea198 Ntfs!NtfsFsdSetInformation+0xa3
bacdbc64 ba70df45 898d43d0 899b9ed8 8987a648 nt!IopfCallDriver+0x31
bacdbc78 804f0095 899a6a08 896ea008 896ea008 sr!SrSetInformation+0x179
bacdbc88 bac19915 badc29f0 896ea008 898d43d0 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
bacdbc9c badc2436 8987a648 896ea008 8987a648 avg7rsxp+0x1915
bacdbcf8 804e59aa 8987a648 bacdbd20 80559690 avg7rsw!AvgWrapAllocatePoolWithTag+0x48
bacdbd34 804e8081 89a81030 80564720 89a2fb30 nt!CcWriteBehind+0x258
bacdbd7c 805389e1 89a81030 00000000 89a2fb30 nt!CcWorkerThread+0x12f
bacdbdac 805cf84c 89a81030 00000000 00000000 nt!ExpWorkerThread+0xef
bacdbddc 8054635e 805388f2 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
avg7rsxp+1915
bac19915 5f pop edi

SYMBOL_STACK_INDEX: d

SYMBOL_NAME: avg7rsxp+1915

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: avg7rsxp

IMAGE_NAME: avg7rsxp.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45bf5f7a

FAILURE_BUCKET_ID: 0xA_W_avg7rsxp+1915

BUCKET_ID: 0xA_W_avg7rsxp+1915

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

eax=89a1a5c8 ebx=899a25c0 ecx=89a1b768 edx=0000a718 esi=899a2690 edi=89a1a5b8
eip=804e9851 esp=bacdb840 ebp=bacdb850 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!CcGetVirtualAddress+0x9d:
804e9851 890a mov dword ptr [edx],ecx ds:0023:0000a718=????????
ChildEBP RetAddr Args to Child
bacdb850 8056a1a5 009a25c0 0033c000 00000000 nt!CcGetVirtualAddress+0x9d (FPO: [Non-Fpo])
bacdb8b8 ba6827cb 89a05f28 bacdb8e8 00000400 nt!CcMapData+0x8b (FPO: [Non-Fpo])
bacdb8d8 ba6829e7 8969b440 899a4008 0033c000 Ntfs!NtfsMapStream+0x46 (FPO: [Non-Fpo])
bacdb94c ba6828f4 8969b440 899a5100 e1480280 Ntfs!NtfsReadMftRecord+0x86 (FPO: [Non-Fpo])
bacdb984 ba68284a 8969b440 899a5100 e1480280 Ntfs!NtfsReadFileRecord+0x7a (FPO: [Non-Fpo])
bacdb9bc ba686f05 8969b440 e1480278 e1480280 Ntfs!NtfsLookupInFileRecord+0x37 (FPO: [Non-Fpo])
bacdba94 ba686dd6 8969b440 e1480340 bacdbb58 Ntfs!NtfsWriteFileSizes+0x76 (FPO: [Non-Fpo])
bacdbb7c ba686e2f 8969b440 8987a648 896ea008 Ntfs!NtfsSetEndOfFileInfo+0xaa (FPO: [Non-Fpo])
bacdbbec ba65fad8 8969b440 896ea008 896ea008 Ntfs!NtfsCommonSetInformation+0x477 (FPO: [Non-Fpo])
bacdbc54 804f0095 899a5020 896ea008 896ea198 Ntfs!NtfsFsdSetInformation+0xa3 (FPO: [Non-Fpo])
bacdbc64 ba70df45 898d43d0 899b9ed8 8987a648 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
bacdbc78 804f0095 899a6a08 896ea008 896ea008 sr!SrSetInformation+0x179 (FPO: [Non-Fpo])
bacdbc88 bac19915 badc29f0 896ea008 898d43d0 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
WARNING: Stack unwind information not available. Following frames may be wrong.
bacdbc9c badc2436 8987a648 896ea008 8987a648 avg7rsxp+0x1915
bacdbcf8 804e59aa 8987a648 bacdbd20 80559690 avg7rsw!AvgWrapAllocatePoolWithTag+0x48
bacdbd34 804e8081 89a81030 80564720 89a2fb30 nt!CcWriteBehind+0x258 (FPO: [Non-Fpo])
bacdbd7c 805389e1 89a81030 00000000 89a2fb30 nt!CcWorkerThread+0x12f (FPO: [Non-Fpo])
bacdbdac 805cf84c 89a81030 00000000 00000000 nt!ExpWorkerThread+0xef (FPO: [Non-Fpo])
bacdbddc 8054635e 805388f2 00000000 00000000 nt!PspSystemThreadStartup+0x34 (FPO: [Non-Fpo])
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
start end module name
804d8000 806e3000 nt ntkrpamp.exe Mon Oct 30 17:50:10 2006 (4545CAD2)
806e3000 80703d00 hal halmacpi.dll Mon Oct 30 17:50:16 2006 (4545CAD8)
b9141000 b9181380 HTTP HTTP.sys Wed Aug 04 14:00:09 2004 (41107B69)
b929a000 b92ec180 srv srv.sys Wed Aug 04 14:14:44 2004 (41107ED4)
b94cd000 b94f9400 mrxdav mrxdav.sys Wed Aug 04 14:00:49 2004 (41107B91)
b9876000 b9879280 ndisuio ndisuio.sys Wed Aug 04 14:03:10 2004 (41107C1E)
ba182000 ba199480 dump_atapi dump_atapi.sys Wed Aug 04 13:59:41 2004 (41107B4D)
ba19a000 ba257f00 avg7core avg7core.sys Mon Apr 23 23:31:26 2007 (462CD14E)
ba2f8000 ba366380 mrxsmb mrxsmb.sys Wed Aug 04 14:15:14 2004 (41107EF2)
ba367000 ba392180 rdbss rdbss.sys Wed Aug 04 14:20:05 2004 (41108015)
ba3bb000 ba3dcd00 afd afd.sys Wed Aug 04 14:14:13 2004 (41107EB5)
ba3dd000 ba3fdf00 ipnat ipnat.sys Wed Aug 04 14:04:48 2004 (41107C80)
ba3fe000 ba425c00 netbt netbt.sys Wed Aug 04 14:14:36 2004 (41107ECC)
ba426000 ba47da80 tcpip tcpip.sys Wed Aug 04 14:14:39 2004 (41107ECF)
ba47e000 ba490400 ipsec ipsec.sys Wed Aug 04 14:14:27 2004 (41107EC3)
ba4b1000 ba4c4780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 14:07:04 2004 (41107D08)
ba4ed000 ba520200 update update.sys Wed Aug 04 13:58:32 2004 (41107B08)
ba521000 ba531e00 psched psched.sys Wed Aug 04 14:04:16 2004 (41107C60)
ba54a000 ba560680 ndiswan ndiswan.sys Wed Aug 04 14:14:30 2004 (41107EC6)
ba561000 ba574580 parport parport.sys Wed Aug 04 13:59:04 2004 (41107B28)
ba575000 ba597680 ks ks.sys Wed Aug 04 14:15:20 2004 (41107EF8)
ba598000 ba5bae80 USBPORT USBPORT.SYS Wed Aug 04 14:08:34 2004 (41107D62)
ba614000 ba62e580 Mup Mup.sys Wed Aug 04 14:15:20 2004 (41107EF8)
ba62f000 ba65ba80 NDIS NDIS.sys Wed Aug 04 14:14:27 2004 (41107EC3)
ba65c000 ba6e8480 Ntfs Ntfs.sys Wed Aug 04 14:15:06 2004 (41107EEA)
ba6e9000 ba6ff780 KSecDD KSecDD.sys Wed Aug 04 13:59:45 2004 (41107B51)
ba700000 ba711e00 sr sr.sys Wed Aug 04 14:06:22 2004 (41107CDE)
ba712000 ba730780 fltMgr fltMgr.sys Wed Aug 04 14:01:17 2004 (41107BAD)
ba731000 ba748480 atapi atapi.sys Wed Aug 04 13:59:41 2004 (41107B4D)
ba749000 ba767880 ftdisk ftdisk.sys Sat Aug 18 04:52:41 2001 (3B7D8419)
ba768000 ba778600 pci pci.sys Wed Aug 04 14:07:45 2004 (41107D31)
ba779000 ba7a6580 ACPI ACPI.sys Wed Aug 04 14:07:35 2004 (41107D27)
ba8a8000 ba8b0c00 isapnp isapnp.sys Sat Aug 18 04:58:01 2001 (3B7D8559)
ba8b8000 ba8c2500 MountMgr MountMgr.sys Wed Aug 04 13:58:29 2004 (41107B05)
ba8c8000 ba8d4000 VolSnap VolSnap.sys Wed Aug 04 14:00:14 2004 (41107B6E)
ba8d8000 ba8e0e00 disk disk.sys Wed Aug 04 13:59:53 2004 (41107B59)
ba8e8000 ba8f4200 CLASSPNP CLASSPNP.SYS Wed Aug 04 14:14:26 2004 (41107EC2)
ba948000 ba951800 intelppm intelppm.sys Wed Aug 04 13:59:19 2004 (41107B37)
ba958000 ba962380 imapi imapi.sys Wed Aug 04 14:00:12 2004 (41107B6C)
ba968000 ba974180 cdrom cdrom.sys Wed Aug 04 13:59:52 2004 (41107B58)
ba978000 ba985680 redbook redbook.sys Wed Aug 04 13:59:34 2004 (41107B46)
ba988000 ba993a80 i8042prt i8042prt.sys Wed Aug 04 14:14:36 2004 (41107ECC)
ba998000 ba9a4880 rasl2tp rasl2tp.sys Wed Aug 04 14:14:21 2004 (41107EBD)
ba9a8000 ba9b2200 raspppoe raspppoe.sys Wed Aug 04 14:05:06 2004 (41107C92)
ba9b8000 ba9c3d00 raspptp raspptp.sys Wed Aug 04 14:14:26 2004 (41107EC2)
ba9c8000 ba9d0900 msgpc msgpc.sys Wed Aug 04 14:04:11 2004 (41107C5B)
ba9e8000 ba9f1f00 termdd termdd.sys Wed Aug 04 13:58:52 2004 (41107B1C)
ba9f8000 baa01480 NDProxy NDProxy.SYS Sat Aug 18 04:55:30 2001 (3B7D84C2)
baa08000 baa16100 usbhub usbhub.sys Wed Aug 04 14:08:40 2004 (41107D68)
baa28000 baa30700 wanarp wanarp.sys Wed Aug 04 14:04:57 2004 (41107C89)
baa38000 baa40700 netbios netbios.sys Wed Aug 04 14:03:19 2004 (41107C27)
baa48000 baa50880 Fips Fips.SYS Sat Aug 18 09:31:49 2001 (3B7DC585)
baa58000 baa67900 Cdfs Cdfs.SYS Wed Aug 04 14:14:09 2004 (41107EB1)
bab28000 bab2e200 PCIIDEX PCIIDEX.SYS Wed Aug 04 13:59:40 2004 (41107B4C)
bab30000 bab34900 PartMgr PartMgr.sys Sat Aug 18 09:32:23 2001 (3B7DC5A7)
bab90000 bab94280 usbohci usbohci.sys Wed Aug 04 14:08:34 2004 (41107D62)
bab98000 bab9e800 usbehci usbehci.sys Wed Aug 04 14:08:34 2004 (41107D62)
baba0000 baba5b80 kbdclass kbdclass.sys Wed Aug 04 13:58:32 2004 (41107B08)
baba8000 babad580 mouclass mouclass.sys Wed Aug 04 13:58:32 2004 (41107B08)
babb0000 babb5200 RTL8139 RTL8139.SYS Fri Jun 13 13:29:46 2003 (3EE9614A)
babb8000 babbc880 TDI TDI.SYS Wed Aug 04 14:07:47 2004 (41107D33)
babc0000 babc4580 ptilink ptilink.sys Sat Aug 18 04:49:53 2001 (3B7D8371)
babc8000 babcc080 raspti raspti.sys Sat Aug 18 04:55:32 2001 (3B7D84C4)
babf0000 babf5200 vga vga.sys Wed Aug 04 14:07:06 2004 (41107D0A)
babf8000 babfca80 Msfs Msfs.SYS Wed Aug 04 14:00:37 2004 (41107B85)
bac00000 bac07880 Npfs Npfs.SYS Wed Aug 04 14:00:38 2004 (41107B86)
bac10000 bac16780 USBSTOR USBSTOR.SYS Wed Aug 04 14:08:44 2004 (41107D6C)
bac18000 bac1ec80 avg7rsxp avg7rsxp.sys Tue Jan 30 23:08:42 2007 (45BF5F7A)
bac28000 bac2c500 watchdog watchdog.sys Wed Aug 04 14:07:32 2004 (41107D24)
bacb8000 bacbb000 BOOTVID BOOTVID.dll Sat Aug 18 04:49:09 2001 (3B7D8345)
bad44000 bad46f80 fsvga fsvga.sys Sat Aug 18 04:57:21 2001 (3B7D8531)
bad48000 bad4a580 ndistapi ndistapi.sys Sat Aug 18 04:55:29 2001 (3B7D84C1)
bad54000 bad56900 Dxapi Dxapi.sys Sat Aug 18 04:53:19 2001 (3B7D843F)
bad58000 bad5bc80 mssmbios mssmbios.sys Wed Aug 04 14:07:47 2004 (41107D33)
bad8c000 bad8e280 rasacd rasacd.sys Sat Aug 18 04:55:39 2001 (3B7D84CB)
bada8000 bada9b80 kdcom kdcom.dll Sat Aug 18 04:49:10 2001 (3B7D8346)
badaa000 badab100 WMILIB WMILIB.SYS Sat Aug 18 05:07:23 2001 (3B7D878B)
badb2000 badb3100 swenum swenum.sys Wed Aug 04 13:58:41 2004 (41107B11)
badb6000 badb7280 USBD USBD.SYS Sat Aug 18 05:02:58 2001 (3B7D8682)
badba000 badbbf00 Fs_Rec Fs_Rec.SYS Sat Aug 18 04:49:37 2001 (3B7D8361)
badbc000 badbd080 Beep Beep.SYS Sat Aug 18 04:47:33 2001 (3B7D82E5)
badbe000 badbf080 mnmdd mnmdd.SYS Sat Aug 18 04:57:28 2001 (3B7D8538)
badc0000 badc1080 RDPCDD RDPCDD.sys Sat Aug 18 04:46:56 2001 (3B7D82C0)
badc2000 badc3080 avg7rsw avg7rsw.sys Tue Jul 26 20:10:51 2005 (42E6284B)
badc8000 badc9100 dump_WMILIB dump_WMILIB.SYS Sat Aug 18 05:07:23 2001 (3B7D878B)
bae3c000 bae3da80 ParVdm ParVdm.SYS Sat Aug 18 04:49:49 2001 (3B7D836D)
bae46000 bae47360 avgtdi avgtdi.sys Thu Aug 25 17:59:58 2005 (430D969E)
bae70000 bae70d00 pciide pciide.sys Sat Aug 18 04:51:49 2001 (3B7D83E5)
bae9d000 bae9dc00 audstub audstub.sys Sat Aug 18 04:59:40 2001 (3B7D85BC)
baf08000 baf08d00 dxgthk dxgthk.sys Sat Aug 18 04:53:12 2001 (3B7D8438)
baf77000 baf77b80 Null Null.SYS Sat Aug 18 04:47:39 2001 (3B7D82EB)
baf78000 baf78f80 avgclean avgclean.sys Tue Aug 22 06:55:15 2006 (44EA39D3)
bf800000 bf9c0200 win32k win32k.sys Wed Aug 04 14:17:30 2004 (41107F7A)
bf9c1000 bf9d2580 dxg dxg.sys Wed Aug 04 14:00:51 2004 (41107B93)
bff70000 bff72480 framebuf framebuf.dll Thu Aug 12 09:16:03 2004 (411AC4D3)

Unloaded modules:
b95da000 b95e9000 Serial.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
babe8000 babed000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
bad88000 bad8b000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
babe0000 babe5000 Flpydisk.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
babd8000 babdf000 Fdc.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

And then I run the Everest, here is the report:

Field Value
Sensor Properties
Sensor Type SMSC DME1737 (SMBus 2Eh)

Temperatures
Motherboard 45 蚓 (113 蚌)
CPU 46 蚓 (115 蚌)
Aux 55 蚓 (131 蚌)
Seagate ST3160811AS 49 蚓 (120 蚌)
WDC WD2500YS-01SHB1 47 蚓 (117 蚌)

Cooling Fans
CPU 1852 RPM

Voltage Values
CPU Core 0.90 V
+3.3 V 3.32 V
+5 V 5.08 V
+12 V 11.94 V
VTR 3.35 V
Debug Info F 63 0B FF FF FF FF FF FF
Debug Info T 2E 2D 37 81
Debug Info V 00 73 C1 C3 BF

 

And then I also check the bios for the temp info, here are the findings:

Processor Fan Speed: 2220
Front Fan Speed: 0
Rear Fan Speed: 0

Processor Temp: 65c
Internal Temp: 46c
Remote Temp: 47c

V12.0 11.781V
V5.0 5.096V
V3.3 3.315V
Vccp 1.344V

Hope it can give you some more idea...

 

Hi, thiefng.

You did some great research! I skimmed the information you linked and, since it comes from reputable sources, the fix you applied seems reasonable. However, the BSOD you got immediately after installing the fix from Microsoft has me wondering.

That CPU temperature seems quite high.* It seems likely your computer tries to shut down when the temperature gets too high.

While I do not claim to be an expert, the first thing I would do is configure Windows to not automatically restart on fatal STOP errors (a.k.a. BSODs). If you want help with that, I'm sure someone will provide it. If your computer repeatedly crashes (one immediately after another), then I suspect the high CPU temperature might be the cause because it is not given enough time to cool down between boots before the CPU has to start processing another Windows start-up.

The cooling fan speed seems slow too.**

Off the cuff, I would suggest you carefully replace the cooling fan as soon as possible...being careful to not separate the heat sink from the CPU...and be sure all the dust is cleared from between the fins of the CPU's heat sink before attaching the new fan. Excessive heat on a CPU can be damaging to the CPU. Be sure you get a cooling fan that is compatible with your heat sink.

If the CPU fan replacement does not significantly lower your processor temperature, then I would also have someone (who is experienced in such matters) carefully apply a good thermal paste solution between your heat sink and CPU. It is very important to use a good quality (Arctic Silver?) thermal paste and not apply too much paste. It's probably also important to effectively clean off any existing thermal paste before applying the new thermal paste.

I'll leave further recommendations in this regard to Rockster and surferdude. They are much more familiar with hardware issues than I am. I expect they can make recommendations about what type of thermal paste to get and where to obtain it. They also probably know tips & tricks about methods to follow.


*I will do some digging to see if I can find a CPU temperature specification for your CPU to substantiate my hunch about your CPU temperature being too high.

**I will also see if I can find a CFU fan speed specification for the stock fan that shipped with the CPU and heat sink (assuming you have a stock fan and heat sink from Intel).

 

The following quote (I added bold emphasis.) is clipped from

• Thermal Management for the Boxed Intel® Pentium® Processor Extreme Edition and Intel® Pentium® D Processor in the 775-land Package:
  http://www.intel.com/cd/channel/reseller/asmo-na/eng/216412.htm
  

thiefng, I think you should also seriously consider adding chassis fans to your box to cool down the temperature inside the box (in addition to replacing the CPU cooling fan with a new one designed for the Pentium D CPU/heat sink). If you can put your computer into a cooler environment, I think that would also help reduce your CPU temperature.


EDIT: Here is another resource link provided for convenience to the people following this thread.

• Intel® Pentium® D Processor Product Information
  http://www.intel.com/products/processor/pentium_D/index.htm

EDIT #2 after Rockster posted his message below:

thiefng, here are quick links to specifications sheets for your processor. I do not know which "Core Stepping" revision (A0 or B0) you have.

thiefng's CPU Specifications:

• Intel® Pentium® D processor 820 - SL88T: (Core Stepping: A0)
  http://processorfinder.intel.com/details.aspx?sSpec=SL88T <--This code should be displayed on your CPU if this is your CPU revision.
• Intel® Pentium® D processor 820 - SL8CP: (Core Stepping: B0)
  http://processorfinder.intel.com/details.aspx?sSpec=SL8CP <--This code should be displayed on your CPU if this is your CPU revision.

thiefng, according to those specification sheets, your CPU temperature reported via your BIOS (65°C) is above the threshold (64.1°C).

I suggest (especially if this computer is still in warranty),

• print this entire thread and read it carefully while you
• use a highlighter to highlight every suggestion given that has not been carried out yet.
• Then take the printed thread along with your computer to the dealer that sold you the computer
• and let him/her fix it.

EDIT#3 after Rockster posted his message below:

Regardless of who fixes your computer, I also suggest you study/print the following pages at Intel:

• What Troubleshooting Steps Should I Take If My System Won't Boot or Shuts Down?
  http://www.intel.com/support/processors/sb/CS-023102.htm
• How to Recognize a Thermally Advantaged Chassis
  http://www.intel.com/support/processors/pentium4/sb/CS-008537.htm
• Thermal Management for the Boxed Intel® Pentium® Processor Extreme Edition and Intel® Pentium® D Processor in the 775-land Package
  http://www.intel.com/cd/channel/reseller/asmo-na/eng/216412.htm
• Thermal Interface Material Application for Desktop Processors
  http://www.intel.com/support/processors/sb/CS-023107.htm
• BIOS Does Not Identify or Recognize the Processor
  http://www.intel.com/support/processors/sb/CS-001488.htm
  
• Tested Motherboards List for Boxed Intel® Pentium® D Processors
  http://www.intel.com/cd/channel/reseller/asmo-na/eng/216415.htm
• Integration of the Boxed Intel® Pentium® Processor Extreme Edition and Intel® Pentium® D Processor (ATX)
  http://www.intel.com/cd/channel/reseller/asmo-na/eng/216411.htm
  There is A LOT of information in the link above about putting things together (with pictures).

All of these links were found here: http://www.intel.com/support/processors/pentiumd/
I might have missed a link or two that may be helpful to you so you might want to review the list to see if I missed anything.

If you decide to perform the suggestions in this thread yourself, I strongly recommend you also study and print all of the information available via the link below (including the embedded links to "Instructions for Recovery BIOS Update ", "Beep Codes ", etc.) in case you have troubles booting after you put everything back together.

• Troubleshooting System Boot Issues
  http://www.intel.com/support/motherboards/desktop/sb/CS-010254.htm

Here is a link to the latest BIOS and drivers for your motherboard.

• BIOS and Drivers for the Intel® Desktop Board D102GGC2
  http://downloadcenter.intel.com/filter_results.aspx?strTypes=all&ProductID=2367&OSFullName=Windows*+XP+Professional&lang=eng&strOSs=44&submit=Go%21

There are "Audio: Intel® HD Audio Controller - Realtek Codec" drivers there, published 4 days ago (6/19/2007), that might apply to you.

 

OK .......... lets go back and say it again.

Fact: The processor was replaced.
Fact: No thermal paste was used on the HSF.
Fact: [SIZE= "2"] "Certain Intel® Processors have an advanced power management feature, Enhanced Intel SpeedStep® Technology (EIST). Enhanced Intel SpeedStep® technology allows the system to dynamically adjust processor voltage and core frequency, which can result in decreased average power consumption and decreased average heat production. This feature may also be referred to as Demand Based Switching (DBS).

Systems equipped with such processors and running on Microsoft Windows* XP Professional Edition or Microsoft Windows* XP Home Edition require Microsoft Windows* XP Service Pack 2 (SP2). This requirement includes any computers that support the following features:


Multiple physical processor sockets
Multiple processor core designs
Multiple logical threads, such as Intel® Hyperthreading technology.
Additional updates to the Windows* XP operating systems are available from Microsoft. Without these additional updates, systems running Intel® processors with EIST may experience a decrease in performance or unpredictable behaviour. "[/SIZE]

Actually, one should apply thermal compound only to the processor and can apply compound to the HSF and then buff it out before reseating. Artic Silver is about the best thermal compound available and their website has an instructional video. You will also need to clean the HSF and the CPU die before applying new paste. This must be done every time a heatsink is removed from the processor. Until this is done, you are wasting everybody's time along with your own. You also need to make sure you have done the updates referenced above.

 

Thanks again, Rockster!

thiefng, here's a link.

• Arctic Silver Incorporated - Home
  [SIZE= "3"]http://www.arcticsilver.com/[/SIZE]

After you apply the above suggestions, please let us know whether you have solved your computer crash issue or not. We will be looking forward to hearing from you.

Good luck!