1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

PC Keeps restarting ?

Discussion in 'PC Hardware' started by Mark Nordstrom, 2006/10/16.

  1. 2006/10/16
    Mark Nordstrom

    Mark Nordstrom Inactive Thread Starter

    Joined:
    2006/10/16
    Messages:
    8
    Likes Received:
    0
    It does this in and out of games. I have prob 20 debug logs from it heres one.

    Opened log file 'c:\debuglog.txt'

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


    Loading Dump File [C:\WINDOWS\Minidump\Mini101606-02.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
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Mon Oct 16 12:49:36.500 2006 (GMT-5)
    System Uptime: 0 days 0:10:54.203
    Loading Kernel Symbols
    ................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9C, {0, f7880050, b2000000, 1040080f}

    *** ERROR: Module load completed but symbols could not be loaded for AGRSM.sys
    Probably caused by : AGRSM.sys ( AGRSM+14b87 )

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

    1: 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: f7880050
    Arg3: b2000000
    Arg4: 1040080f

    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
    3210987654321098765432109876543210987654321098765432109876543210
    ----------------------------------------------------------------
    1011001000000000000000000000000000010000010000000000100000001111


    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.

    EN - Error Enabled
    Indicates that the error was enabled by the associated EEj bit of the
    IA32_MCi_CTL register.

    PCC - Processor Context Corrupt
    Indicates that the state of the processor might have been corrupted
    by the error condition detected and that reliable restarting of the
    processor may not be possible.

    BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
    These errors match the format 0000 1PPT RRRR IILL



    Concatenated Error Code:
    --------------------------
    _VAL_UC_EN_PCC_BUSCONNERR_F

    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_IA32_GenuineIntel

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    PROCESS_NAME: eqgame.exe

    LAST_CONTROL_TRANSFER: from 806e7bff to 804f9c37

    SYMBOL_ON_RAW_STACK: 1

    STACK_ADDR_RAW_STACK_SYMBOL: 17002000010004

    STACK_COMMAND: dds F78801C0-0x20 ; kb

    STACK_TEXT:
    f78801a0 0000ffff
    f78801a4 00cf9300
    f78801a8 0000ffff
    f78801ac 00cffb00
    f78801b0 0000ffff
    f78801b4 00cff300
    f78801b8 cd7020ab
    f78801bc f7008b87 AGRSM+0x14b87
    f78801c0 c0000001
    f78801c4 f7c09387
    f78801c8 e0000fff
    f78801cc 7f40f3fd
    f78801d0 0400ffff
    f78801d4 0000f200
    f78801d8 00000000
    f78801dc 00000000
    f78801e0 f0800068
    f78801e4 f7008987 AGRSM+0x14987
    f78801e8 f0f00068
    f78801ec f7008987 AGRSM+0x14987
    f78801f0 2f30ffff
    f78801f4 00009302
    f78801f8 80003fff
    f78801fc 0000920b
    f7880200 700003ff
    f7880204 ff0092ff
    f7880208 0000ffff
    f788020c 80009a40
    f7880210 0000ffff
    f7880214 80009240
    f7880218 00000000
    f788021c 00009200


    FOLLOWUP_IP:
    AGRSM+14b87
    f7008b87 0300 add eax,dword ptr [eax]

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: AGRSM

    IMAGE_NAME: AGRSM.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 43d7ec89

    SYMBOL_NAME: AGRSM+14b87

    FAILURE_BUCKET_ID: 0x9C_IA32_GenuineIntel_AGRSM+14b87

    BUCKET_ID: 0x9C_IA32_GenuineIntel_AGRSM+14b87

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

    eax=f787c13c ebx=f7880050 ecx=00000000 edx=00000000 esi=1040080f edi=b2000000
    eip=804f9c37 esp=f7880010 ebp=f7880028 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:
    804f9c37 5d pop ebp
    ChildEBP RetAddr Args to Child
    f7880028 806e7bff 0000009c 00000000 f7880050 nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo])
    f7880154 806e2c52 f787cd70 00000001 00000014 hal!HalpMcaExceptionHandler+0xdd (FPO: [Non-Fpo])
    f7880154 01158841 f787cd70 00000001 00000014 hal!HalpMcaExceptionHandlerWrapper+0x4a (FPO: TSS 28:0)
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0012d480 00000000 00000000 00000000 00000000 0x1158841
    start end module name
    804d7000 806e2000 nt ntkrpamp.exe Tue Mar 01 18:34:38 2005 (42250A1E)
    806e2000 80702d00 hal halmacpi.dll Wed Aug 04 00:59:09 2004 (41107B2D)
    a824b000 a828b280 HTTP HTTP.sys Thu Mar 16 18:33:09 2006 (441A03C5)
    a8626000 a8677480 srv srv.sys Mon Aug 14 05:34:39 2006 (44E051BF)
    a86ee000 a8702400 wdmaud wdmaud.sys Wed Jun 14 04:00:44 2006 (448FD03C)
    a872b000 a8757400 mrxdav mrxdav.sys Wed Aug 04 01:00:49 2004 (41107B91)
    a8890000 a889ed80 sysaudio sysaudio.sys Wed Aug 04 01:15:54 2004 (41107F1A)
    a8a68000 a8a6b280 ndisuio ndisuio.sys Wed Aug 04 01:03:10 2004 (41107C1E)
    aad68000 aad7f480 dump_atapi dump_atapi.sys Wed Aug 04 00:59:41 2004 (41107B4D)
    aada8000 aae16a00 mrxsmb mrxsmb.sys Fri May 05 04:41:42 2006 (445B1DD6)
    aae17000 aae41a00 rdbss rdbss.sys Fri May 05 04:47:55 2006 (445B1F4B)
    aae42000 aae63d00 afd afd.sys Wed Aug 04 01:14:13 2004 (41107EB5)
    aae64000 aae84f00 ipnat ipnat.sys Wed Sep 29 17:28:36 2004 (415B3714)
    aae85000 aaeacc00 netbt netbt.sys Wed Aug 04 01:14:36 2004 (41107ECC)
    aaead000 aaf04d80 tcpip tcpip.sys Thu Apr 20 06:51:47 2006 (444775D3)
    aaf05000 aaf17400 ipsec ipsec.sys Wed Aug 04 01:14:27 2004 (41107EC3)
    bf800000 bf9c1180 win32k win32k.sys Wed Oct 05 19:05:44 2005 (43446A58)
    bf9c2000 bf9d3580 dxg dxg.sys Wed Aug 04 01:00:51 2004 (41107B93)
    bf9d4000 bfa17000 ati2dvag ati2dvag.dll Tue Aug 22 20:53:30 2006 (44EBB51A)
    bfa17000 bfa5e000 ati2cqag ati2cqag.dll Tue Aug 22 20:14:38 2006 (44EBABFE)
    bfa5e000 bfaa4000 atikvmag atikvmag.dll Tue Aug 22 20:21:15 2006 (44EBAD8B)
    bfaa4000 bfcee6c0 ati3duag ati3duag.dll Tue Aug 22 20:38:43 2006 (44EBB1A3)
    bfcef000 bff53fa0 ativvaxx ativvaxx.dll Tue Aug 22 20:33:45 2006 (44EBB079)
    f6a2a000 f6a2c900 Dxapi Dxapi.sys Fri Aug 17 15:53:19 2001 (3B7D843F)
    f6a42000 f6a75200 update update.sys Wed Aug 04 00:58:32 2004 (41107B08)
    f6a76000 f6aa6100 rdpdr rdpdr.sys Wed Aug 04 01:01:10 2004 (41107BA6)
    f6aa7000 f6ab7e00 psched psched.sys Wed Aug 04 01:04:16 2004 (41107C60)
    f6ae0000 f6af6680 ndiswan ndiswan.sys Wed Aug 04 01:14:30 2004 (41107EC6)
    f6b97000 f6bba980 portcls portcls.sys Wed Aug 04 01:15:47 2004 (41107F13)
    f6bbb000 f6f82040 ALCXWDM ALCXWDM.SYS Fri Mar 31 00:38:44 2006 (442CCE74)
    f6f9a000 f6fad900 parport parport.sys Wed Aug 04 00:59:04 2004 (41107B28)
    f6fae000 f6fd0e80 USBPORT USBPORT.SYS Wed Aug 04 01:08:34 2004 (41107D62)
    f6fd1000 f6ff3680 ks ks.sys Wed Aug 04 01:15:20 2004 (41107EF8)
    f6ff4000 f710cbc0 AGRSM AGRSM.sys Wed Jan 25 15:24:25 2006 (43D7EC89)
    f710d000 f7120780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 01:07:04 2004 (41107D08)
    f7121000 f72d9000 ati2mtag ati2mtag.sys Tue Aug 22 20:53:13 2006 (44EBB509)
    f72dd000 f72df280 rasacd rasacd.sys Fri Aug 17 15:55:39 2001 (3B7D84CB)
    f7321000 f733b580 Mup Mup.sys Wed Aug 04 01:15:20 2004 (41107EF8)
    f733c000 f7368a80 NDIS NDIS.sys Wed Aug 04 01:14:27 2004 (41107EC3)
    f7369000 f73f5480 Ntfs Ntfs.sys Wed Aug 04 01:15:06 2004 (41107EEA)
    f73f6000 f740c780 KSecDD KSecDD.sys Wed Aug 04 00:59:45 2004 (41107B51)
    f740d000 f741ef00 sr sr.sys Wed Aug 04 01:06:22 2004 (41107CDE)
    f741f000 f743e780 fltMgr fltMgr.sys Mon Aug 21 04:14:57 2006 (44E97991)
    f743f000 f7456480 atapi atapi.sys Wed Aug 04 00:59:41 2004 (41107B4D)
    f7457000 f747c700 dmio dmio.sys Wed Aug 04 01:07:13 2004 (41107D11)
    f747d000 f749b880 ftdisk ftdisk.sys Fri Aug 17 15:52:41 2001 (3B7D8419)
    f749c000 f74aca80 pci pci.sys Wed Aug 04 01:07:45 2004 (41107D31)
    f74ad000 f74dad80 ACPI ACPI.sys Wed Aug 04 01:07:35 2004 (41107D27)
    f75dc000 f75e4c00 isapnp isapnp.sys Fri Aug 17 15:58:01 2001 (3B7D8559)
    f75ec000 f75f6500 MountMgr MountMgr.sys Wed Aug 04 00:58:29 2004 (41107B05)
    f75fc000 f7608c80 VolSnap VolSnap.sys Wed Aug 04 01:00:14 2004 (41107B6E)
    f760c000 f7614e00 disk disk.sys Wed Aug 04 00:59:53 2004 (41107B59)
    f761c000 f7628200 CLASSPNP CLASSPNP.SYS Wed Aug 04 01:14:26 2004 (41107EC2)
    f762c000 f7636e80 uagp35 uagp35.sys Wed Aug 04 01:07:43 2004 (41107D2F)
    f769c000 f76a4700 netbios netbios.sys Wed Aug 04 01:03:19 2004 (41107C27)
    f76ac000 f76b4880 Fips Fips.SYS Fri Aug 17 20:31:49 2001 (3B7DC585)
    f76cc000 f76db900 Cdfs Cdfs.SYS Wed Aug 04 01:14:09 2004 (41107EB1)
    f76dc000 f76e4d00 intelppm intelppm.sys Wed Aug 04 00:59:19 2004 (41107B37)
    f76ec000 f76f6380 imapi imapi.sys Wed Aug 04 01:00:12 2004 (41107B6C)
    f76fc000 f7708180 cdrom cdrom.sys Wed Aug 04 00:59:52 2004 (41107B58)
    f770c000 f771a080 redbook redbook.sys Wed Aug 04 00:59:34 2004 (41107B46)
    f771c000 f7728e00 i8042prt i8042prt.sys Wed Aug 04 01:14:36 2004 (41107ECC)
    f772c000 f773bd80 serial serial.sys Wed Aug 04 01:15:51 2004 (41107F17)
    f773c000 f774ab80 drmk drmk.sys Wed Aug 04 01:07:54 2004 (41107D3A)
    f774c000 f7756800 fetnd5bv fetnd5bv.sys Wed Aug 30 22:19:34 2006 (44F65546)
    f775c000 f7768880 rasl2tp rasl2tp.sys Wed Aug 04 01:14:21 2004 (41107EBD)
    f776c000 f7776200 raspppoe raspppoe.sys Wed Aug 04 01:05:06 2004 (41107C92)
    f777c000 f7787d00 raspptp raspptp.sys Wed Aug 04 01:14:26 2004 (41107EC2)
    f778c000 f7794900 msgpc msgpc.sys Wed Aug 04 01:04:11 2004 (41107C5B)
    f77ac000 f77b5f00 termdd termdd.sys Wed Aug 04 00:58:52 2004 (41107B1C)
    f77bc000 f77c5480 NDProxy NDProxy.SYS Fri Aug 17 15:55:30 2001 (3B7D84C2)
    f780c000 f781a100 usbhub usbhub.sys Wed Aug 04 01:08:40 2004 (41107D68)
    f784c000 f7854700 wanarp wanarp.sys Wed Aug 04 01:04:57 2004 (41107C89)
    f785c000 f7862200 PCIIDEX PCIIDEX.SYS Wed Aug 04 00:59:40 2004 (41107B4C)
    f7864000 f7868900 PartMgr PartMgr.sys Fri Aug 17 20:32:23 2001 (3B7DC5A7)
    f786c000 f7874000 videX32 videX32.sys Wed Feb 22 04:10:28 2006 (43FC3894)
    f7874000 f787c000 xfilt xfilt.sys Wed Feb 22 04:10:20 2006 (43FC388C)
    f78e4000 f78eb580 Modem Modem.SYS Wed Aug 04 01:08:04 2004 (41107D44)
    f78ec000 f78f1000 usbuhci usbuhci.sys Wed Aug 04 01:08:34 2004 (41107D62)
    f78f4000 f78fa800 usbehci usbehci.sys Wed Aug 04 01:08:34 2004 (41107D62)
    f78fc000 f7902000 kbdclass kbdclass.sys Wed Aug 04 00:58:32 2004 (41107B08)
    f7904000 f7909a00 mouclass mouclass.sys Wed Aug 04 00:58:32 2004 (41107B08)
    f790c000 f790d000 fdc fdc.sys unavailable (00000000)
    f7914000 f7918880 TDI TDI.SYS Wed Aug 04 01:07:47 2004 (41107D33)
    f7924000 f7928580 ptilink ptilink.sys Fri Aug 17 15:49:53 2001 (3B7D8371)
    f792c000 f7930080 raspti raspti.sys Fri Aug 17 15:55:32 2001 (3B7D84C4)
    f7934000 f7939000 flpydisk flpydisk.sys Wed Aug 04 00:59:24 2004 (41107B3C)
    f7944000 f7949200 vga vga.sys Wed Aug 04 01:07:06 2004 (41107D0A)
    f794c000 f7950a80 Msfs Msfs.SYS Wed Aug 04 01:00:37 2004 (41107B85)
    f7954000 f795b880 Npfs Npfs.SYS Wed Aug 04 01:00:38 2004 (41107B86)
    f797c000 f7980500 watchdog watchdog.sys Wed Aug 04 01:07:32 2004 (41107D24)
    f79ec000 f79ef000 BOOTVID BOOTVID.dll Fri Aug 17 15:49:09 2001 (3B7D8345)
    f7a8c000 f7a8fc80 serenum serenum.sys Wed Aug 04 00:59:06 2004 (41107B2A)
    f7a90000 f7a92580 ndistapi ndistapi.sys Fri Aug 17 15:55:29 2001 (3B7D84C1)
    f7ab0000 f7ab3c80 mssmbios mssmbios.sys Wed Aug 04 01:07:47 2004 (41107D33)
    f7adc000 f7addb80 kdcom kdcom.dll Fri Aug 17 15:49:10 2001 (3B7D8346)
    f7ade000 f7adf100 WMILIB WMILIB.SYS Fri Aug 17 16:07:23 2001 (3B7D878B)
    f7ae0000 f7ae1500 viaide viaide.sys Wed Aug 04 00:59:42 2004 (41107B4E)
    f7ae2000 f7ae3700 dmload dmload.sys Fri Aug 17 15:58:15 2001 (3B7D8567)
    f7ae8000 f7ae9280 USBD USBD.SYS Fri Aug 17 16:02:58 2001 (3B7D8682)
    f7af0000 f7af1100 swenum swenum.sys Wed Aug 04 00:58:41 2004 (41107B11)
    f7af6000 f7af7f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 15:49:37 2001 (3B7D8361)
    f7af8000 f7af9080 Beep Beep.SYS Fri Aug 17 15:47:33 2001 (3B7D82E5)
    f7afa000 f7afb080 mnmdd mnmdd.SYS Fri Aug 17 15:57:28 2001 (3B7D8538)
    f7afc000 f7afd080 RDPCDD RDPCDD.sys Fri Aug 17 15:46:56 2001 (3B7D82C0)
    f7b06000 f7b07100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 16:07:23 2001 (3B7D878B)
    f7b64000 f7b65a80 ParVdm ParVdm.SYS Fri Aug 17 15:49:49 2001 (3B7D836D)
    f7ba4000 f7ba4d00 pciide pciide.sys Fri Aug 17 15:51:49 2001 (3B7D83E5)
    f7ba5000 f7ba6000 speedfan speedfan.sys Wed Jun 15 09:55:53 2005 (42B04179)
    f7ba6000 f7ba6680 giveio giveio.sys Wed Apr 03 20:33:25 1996 (316334F5)
    f7be5000 f7be5d00 dxgthk dxgthk.sys Fri Aug 17 15:53:12 2001 (3B7D8438)
    f7cd9000 f7cd9b80 Null Null.SYS Fri Aug 17 15:47:39 2001 (3B7D82EB)
    f7d1d000 f7d1dc00 audstub audstub.sys Fri Aug 17 15:59:40 2001 (3B7D85BC)

    Unloaded modules:
    a8018000 a8043000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a86a0000 a86cb000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a86cb000 a86ee000 aec.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7c63000 f7c64000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a89a8000 a89b5000 DMusic.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a89b8000 a89c6000 swmidi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7b6c000 f7b6e000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f793c000 f7941000 Cdaudio.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f72e1000 f72e4000 Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:\debuglog.txt
     
  2. 2006/10/16
    Mark Nordstrom

    Mark Nordstrom Inactive Thread Starter

    Joined:
    2006/10/16
    Messages:
    8
    Likes Received:
    0
    It cant be normal that

    LAST_CONTROL_TRANSFER: from 806e7bff to 804f9c37

    is the same for all 20 + dump logs i got from it crashing so far can it ?
     

  3. to hide this advert.

  4. 2006/10/17
    mattman

    mattman Inactive Alumni

    Joined:
    2002/06/10
    Messages:
    8,198
    Likes Received:
    63
    Hi and welcome to the BBS,

    It seems to all relate to the Pentium processor.

    If you are overclocking, go back to standard settings.

    Set your BIOS to default settings (setup defaults) until you find the reason.

    Check for overheating. Clean out the dust. Check if all the fans are spinning freely (including the PSU fan). Check for a buildup of dust in the fins of CPU heatsink (see if the fan can be removed, but don't remove the heatsink from over the CPU).

    If there may be a problem of the BIOS setting the processor incorrectly, check for a BIOS update for your motherboard. If you have not done a BIOS update before, follow the instructions carefully. Do not do the upgrade in Windows, use the method of making a DOS boot disk. If Windows is unstable, you may lose the BIOS.

    Get a new CMOS battery in case the CMOS may be starting to "lose" setting.

    [It may be easier to find or download your motherboard manual to look up information]

    Matt
     
  5. 2006/10/17
    Mark Nordstrom

    Mark Nordstrom Inactive Thread Starter

    Joined:
    2006/10/16
    Messages:
    8
    Likes Received:
    0
    The entire PC is brand new.

    Motherboard,
    cpu
    ram
    hd
    video card everything is new.


    Ive tried everything but replacing the brand new CPU nothing helps. Could the CPU be overheating but not telling me it is ? because the temp never goes above 60c.
     
  6. 2006/10/17
    mattman

    mattman Inactive Alumni

    Joined:
    2002/06/10
    Messages:
    8,198
    Likes Received:
    63
    Mark, don't panic :) (been there, done that :D ) Your system will be covered by warranty (been there,...etc :) )

    The error reports say it is a hardware problem and point to the CPU. My guess would be that the CPU has an air pocket between the CPU and heatsink. 60*C sounds high to me, I think Intel would be looking at around 40*C or less for a brand new system (especially if you are looking in the BIOS temperature readouts).

    If you attempt to make your own repairs that are not sanctioned, you will void the warranty. Start emailing the supplier. Explain the problem as you have done here and ask them for their suggestions. Ask how to RMA the system with the least inconvenience to yourself.

    [Just to check...you are not running programs outside the the specifications of the system?]

    Matt
     
  7. 2006/10/17
    Mark Nordstrom

    Mark Nordstrom Inactive Thread Starter

    Joined:
    2006/10/16
    Messages:
    8
    Likes Received:
    0
    It only gets to around 60 when playing 3d games. Sitting idol it sits around 38. But it crashes when doing normal stuff in windows and playing games.


    It has to be hardware issue thou, i got 2 PCs the same everything. Motherboard, ram, hd, dvd burner, cpu, etc, and this one is only one restarting like this.
     
  8. 2006/10/17
    mattman

    mattman Inactive Alumni

    Joined:
    2002/06/10
    Messages:
    8,198
    Likes Received:
    63
    I have just realized, it may be a system you have built yourself from several suppliers. Did you install the CPU? No drama (I hope:) ). Read the instructions for Arcticsilver 5 here:
    www.arcticsilver.com
    Remove the CPU, check for bent pins, apply the thermal compound, I would recommend using Arcticsilver 5, and try again. It may take a few times to get your technique right. Check your temps, if they seem too high, clean off the old compound and start again. You want the thinnest, most even layer of compound.

    Matt
     
  9. 2006/10/17
    Mark Nordstrom

    Mark Nordstrom Inactive Thread Starter

    Joined:
    2006/10/16
    Messages:
    8
    Likes Received:
    0
    Thanks for help ill try it. Just dont see how its overheating problem, my old PC used to get up to 60c without overheating. Its a Intel Pentium D 945 3.4 ghz Dual Core CPU.
     
  10. 2006/10/17
    Rockster2U

    Rockster2U Geek Member

    Joined:
    2002/04/01
    Messages:
    3,181
    Likes Received:
    9
    Mark:

    If you are 38°C at idle and are hitting 60° or above under load you either have very poor air circulation inside your case or a deficient CPU heatsink/cooler or both. Your previous reference to a system running at 60° plus as "not over-heating" is a stretch - but lets just say there is considerable room for improvement and if you are taking a serious hit while taxing the system (like gaming), it doesn't take a rocket scientist to figure this one out. You might also want to look at your GPU temperatures as well as I suspect they too are perilously close to never never land.

    ;)
     
  11. 2006/10/17
    Mark Nordstrom

    Mark Nordstrom Inactive Thread Starter

    Joined:
    2006/10/16
    Messages:
    8
    Likes Received:
    0
    Well ill have to look into all of this, just dont think overheating is an issue especially when it does crash when doing non gaming stuff when the CPU is barely being used and is around 40c.
     
  12. 2006/10/17
    Rockster2U

    Rockster2U Geek Member

    Joined:
    2002/04/01
    Messages:
    3,181
    Likes Received:
    9
    I'll stand corrected - didn't realize you were having problems regardless of the load. You should eventually check into some better cooling gear, but if this is happening all the time, you are oh so right in saying its more than a heat issue. My apologies for the mis-interpretation. Can you give us any other info - I don't pretend to read dump logs and make any more than the most basic guess at what it is I can't read.

    ;)
     
  13. 2006/10/17
    Mark Nordstrom

    Mark Nordstrom Inactive Thread Starter

    Joined:
    2006/10/16
    Messages:
    8
    Likes Received:
    0
    Right now i have the PC sitting in a game for 4 hrs no restarts. BUT if i actually start to do stuff in the game it restarts. This is the same for windows i can let it sit there for days but if i start to do stuff it restarts.

    Im questioning how its a hardware issue if i can just let the PC sit there all day and it wont restart until i start to do stuff on it.
     
  14. 2006/10/17
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    The CPU is just idling - look in Task Manager. As soon as you start working it you seem to have problems. I would question the integrity of the CPU based on your dump log, but then I'm no expert. Have you checked out your memory ? Windows Memory Diagnostic Tool

    See if there are any Intel forums out there and post the log.
     
  15. 2006/10/17
    mattman

    mattman Inactive Alumni

    Joined:
    2002/06/10
    Messages:
    8,198
    Likes Received:
    63
    When there is activity the processor is required to do work (calculations). Without activity the processor sits idle.

    One or two other checks before taking off the heatsink. Is the CPU you mentioned listed as compatible at the motherboard's website? Could incorrect settings have been made in the BIOS? I mentioned overclocking, would there be any settings for Hyperthreading or the dual core that need to be adjusted.

    I could not find in info at Intel, but you could email their Support. This is the information you need to pass on:
    Matt
     
  16. 2006/10/17
    Mark Nordstrom

    Mark Nordstrom Inactive Thread Starter

    Joined:
    2006/10/16
    Messages:
    8
    Likes Received:
    0
    not overclocking it and the motherboard and cpu are the same as the other ones i got and the other PC works just fine with the same settings, windows, ram, hd, etc its all exactly the same hardware. Ive emailed intel with the dump log see what they say.
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.