XP Random Restarts (minidump included)

By chris_uk_lad
Mar 12, 2008
Topic Status:
Not open for further replies.
  1. Hi all,

    My PC has been a nightmare lately with random restarts, these vary between 10mins and 10 hours. Because of this i did a full reformat last week, yet still showed error after reinstalling everything, tried this again on a different hard disk but same problem. I have also tried several different pieces of ram so know those to not be the problem. System tmep is usually around 40'C so shouldnt be a problem either.

    Minidump displayed below, have attatched several dump files incas ei caused an error in debugger (also removed h from http in order ot be allowed ot post)

    Opened log file 'c:\debuglog.txt'
    kd> .sympath srv*c:\symbols*ttp://msdl.microsoft.com/downloads/symbols
    Symbol search path is: srv*c:\symbols*ttp://msdl.microsoft.com/downloads/symbols
    kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
    Invalid relocation block size 0x0
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ......................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    * *
    * 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: 8054da70
    Arg3: a2000000
    Arg4: 84010400

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

    ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
    ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,214600,41108004
  2. kimsland

    kimsland Ex-TechSpotter Posts: 18,353

    It's good that you can view your own MiniDumps

    But if you allow more time in the processing of your MiniDump, it will eventually (after seemingly a long pause) show you what file is causing this.

    By the way, most of these errors point to drivers that require updating (and mem - already confirmed)
    Have all the drivers been fully updated?
  3. chris_uk_lad

    chris_uk_lad Newcomer, in training Topic Starter

    everything but windows updates and the bios, i figured it had finished analysing the dump, ill do again if my comp stays on long enough, its so random :(
  4. kimsland

    kimsland Ex-TechSpotter Posts: 18,353

    Bios is not usually important (ie even the first revision actually worked once)

    But Windows updates can have a bearing (ie Service Pack 2)

    But I don't think it's that either

    My guess is CPU

    Waiting for Minidump...
  5. chris_uk_lad

    chris_uk_lad Newcomer, in training Topic Starter

    i had suspicions of SP2 as my computer worked fine a while back without any SP (security issues aside lol). Just surprised how random it is

    latest minidump:

    Opened log file 'c:\debuglog.txt'
    kd> .sympath srv*c:\symbols*ttp://msdl.microsoft.com/downloads/symbols
    Symbol search path is: srv*c:\symbols*
    ttp://msdl.microsoft.com/downloads/symbols
    kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
    Invalid relocation block size 0x0
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ......................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    * *
    * 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: 8054da70
    Arg3: a2000000
    Arg4: 84010400

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

    ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
    ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,214600,41108004
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    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
    ----------------------------------------------------------------
    1010000111111111111111111111111110000100000000010000010000000000


    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
  6. chris_uk_lad

    chris_uk_lad Newcomer, in training Topic Starter

    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.
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
  7. chris_uk_lad

    chris_uk_lad Newcomer, in training Topic Starter

    MODULE_NAME: nt

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 41108004

    BUGCHECK_STR: 0x9C_GenuineIntel

    CUSTOMER_CRASH_COUNT: 4

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    LAST_CONTROL_TRANSFER: from 806effaf to 805339ae

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8054da48 806effaf 0000009c 00000000 8054da70 nt+0x5c9ae
    8054db74 806eccae 80042000 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd
    8054db74 00000000 80042000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x46


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt+5c9ae
    805339ae 5d pop ebp

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt+5c9ae

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: ntoskrnl.exe

    BUCKET_ID: WRONG_SYMBOLS

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

    eax=ffdff13c ebx=8054da70 ecx=00000000 edx=00000000 esi=84010400 edi=a2000000
    eip=805339ae esp=8054da30 ebp=8054da48 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+0x5c9ae:
    805339ae 5d pop ebp
    ChildEBP RetAddr Args to Child
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8054da48 806effaf 0000009c 00000000 8054da70 nt+0x5c9ae
    8054db74 806eccae 80042000 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd (FPO: [Non-Fpo])
    8054db74 00000000 80042000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x46 (FPO: TSS f10f10:0)
    start end module name
    804d7000 806eb600 nt ntoskrnl.exe Wed Aug 04 07:19:48 2004 (41108004)
    806ec000 806ffd80 hal halacpi.dll Wed Aug 04 06:59:04 2004 (41107B28)
    b85eb000 b8614f00 kmixer kmixer.sys Wed Aug 04 07:07:46 2004 (41107D32)
    b8615000 b862c480 dump_atapi dump_atapi.sys Wed Aug 04 06:59:41 2004 (41107B4D)
    b900f000 b904f380 HTTP HTTP.sys Wed Aug 04 07:00:09 2004 (41107B69)
    b9d24000 b9d76180 srv srv.sys Wed Aug 04 07:14:44 2004 (41107ED4)
    ba0e7000 ba113400 mrxdav mrxdav.sys Wed Aug 04 07:00:49 2004 (41107B91)
    ba27b000 ba28f400 wdmaud wdmaud.sys Wed Aug 04 07:15:03 2004 (41107EE7)
    bad94000 bad97280 ndisuio ndisuio.sys Wed Aug 04 07:03:10 2004 (41107C1E)
    bf800000 bf9c0380 win32k win32k.sys Wed Aug 04 07:17:30 2004 (41107F7A)
    bf9c1000 bf9d2580 dxg dxg.sys Wed Aug 04 07:00:51 2004 (41107B93)
    bf9d3000 bfe24580 nv4_disp nv4_disp.dll Sun Oct 22 22:02:50 2006 (453BDC7A)
    bffa0000 bffe5c00 ATMFD ATMFD.DLL Wed Aug 04 08:56:56 2004 (411096C8)
    f5f91000 f5fb4000 Fastfat Fastfat.SYS Wed Aug 04 07:14:15 2004 (41107EB7)
    f5fd6000 f609ea60 avg7core avg7core.sys Wed Oct 10 17:23:39 2007 (470CFC8B)
    f6134000 f6189d80 OVCODEK2 OVCODEK2.sys Fri Aug 17 22:05:06 2001 (3B7D8702)
    f61b2000 f61d2f00 ipnat ipnat.sys Wed Aug 04 07:04:48 2004 (41107C80)
    f61d3000 f6241380 mrxsmb mrxsmb.sys Wed Aug 04 07:15:14 2004 (41107EF2)
    f6242000 f626d180 rdbss rdbss.sys Wed Aug 04 07:20:05 2004 (41108015)
    f626e000 f628fd00 afd afd.sys Wed Aug 04 07:14:13 2004 (41107EB5)
    f6290000 f62b7c00 netbt netbt.sys Wed Aug 04 07:14:36 2004 (41107ECC)
    f62b8000 f630fa80 tcpip tcpip.sys Wed Aug 04 07:14:39 2004 (41107ECF)
    f6310000 f6322400 ipsec ipsec.sys Wed Aug 04 07:14:27 2004 (41107EC3)
    f7acd000 f7b00200 update update.sys Wed Aug 04 06:58:32 2004 (41107B08)
    f7bb5000 f7bb7900 Dxapi Dxapi.sys Fri Aug 17 21:53:19 2001 (3B7D843F)
    f7bc9000 f7bf9100 rdpdr rdpdr.sys Wed Aug 04 07:01:10 2004 (41107BA6)
    f7bfa000 f7c0ae00 psched psched.sys Wed Aug 04 07:04:16 2004 (41107C60)
    f7c0b000 f7c21680 ndiswan ndiswan.sys Wed Aug 04 07:14:30 2004 (41107EC6)
    f7c22000 f7c35900 parport parport.sys Wed Aug 04 06:59:04 2004 (41107B28)
    f7c36000 f7c59980 portcls portcls.sys Wed Aug 04 07:15:47 2004 (41107F13)
    f7c5a000 f8049b00 ALCXWDM ALCXWDM.SYS Thu Jan 24 08:35:49 2008 (47984DE5)
    f804a000 f806ce80 USBPORT USBPORT.SYS Wed Aug 04 07:08:34 2004 (41107D62)
    f806d000 f808f680 ks ks.sys Wed Aug 04 07:15:20 2004 (41107EF8)
    f8090000 f80ee680 netwg311 netwg311.sys Thu Jun 17 21:41:13 2004 (40D201E9)
    f80ef000 f8102780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 07:07:04 2004 (41107D08)
    f8103000 f84d2400 nv4_mini nv4_mini.sys Sun Oct 22 22:08:02 2006 (453BDDB2)
    f84f3000 f84f6c80 mssmbios mssmbios.sys Wed Aug 04 07:07:47 2004 (41107D33)
    f851b000 f8535580 Mup Mup.sys Wed Aug 04 07:15:20 2004 (41107EF8)
    f8536000 f8562a80 NDIS NDIS.sys Wed Aug 04 07:14:27 2004 (41107EC3)
    f8563000 f85ef480 Ntfs Ntfs.sys Wed Aug 04 07:15:06 2004 (41107EEA)
    f85f0000 f8606780 KSecDD KSecDD.sys Wed Aug 04 06:59:45 2004 (41107B51)
    f8607000 f8618f00 sr sr.sys Wed Aug 04 07:06:22 2004 (41107CDE)
    f8619000 f8637780 fltmgr fltmgr.sys Wed Aug 04 07:01:17 2004 (41107BAD)
    f8638000 f864f480 atapi atapi.sys Wed Aug 04 06:59:41 2004 (41107B4D)
    f8650000 f8675700 dmio dmio.sys Wed Aug 04 07:07:13 2004 (41107D11)
    f8676000 f8694880 ftdisk ftdisk.sys Fri Aug 17 21:52:41 2001 (3B7D8419)
    f8695000 f86a5a80 pci pci.sys Wed Aug 04 07:07:45 2004 (41107D31)
    f86a6000 f86d3d80 ACPI ACPI.sys Wed Aug 04 07:07:35 2004 (41107D27)
    f86f5000 f86fdc00 isapnp isapnp.sys Fri Aug 17 21:58:01 2001 (3B7D8559)
    f8705000 f870f500 MountMgr MountMgr.sys Wed Aug 04 06:58:29 2004 (41107B05)
    f8715000 f8721c80 VolSnap VolSnap.sys Wed Aug 04 07:00:14 2004 (41107B6E)
    f8725000 f872de00 disk disk.sys Wed Aug 04 06:59:53 2004 (41107B59)
    f8735000 f8741200 CLASSPNP CLASSPNP.SYS Wed Aug 04 07:14:26 2004 (41107EC2)
    f8745000 f874db80 PxHelp20 PxHelp20.sys Fri Feb 02 21:23:57 2007 (45C3ABED)
    f8755000 f875f500 viaagp viaagp.sys Wed Aug 04 07:07:42 2004 (41107D2E)
    f8785000 f878e480 NDProxy NDProxy.SYS Fri Aug 17 21:55:30 2001 (3B7D84C2)
    f8795000 f87a3100 usbhub usbhub.sys Wed Aug 04 07:08:40 2004 (41107D68)
    f87b5000 f87bd700 netbios netbios.sys Wed Aug 04 07:03:19 2004 (41107C27)
    f87e5000 f87ed880 Fips Fips.SYS Sat Aug 18 02:31:49 2001 (3B7DC585)
    f87f5000 f87fd700 wanarp wanarp.sys Wed Aug 04 07:04:57 2004 (41107C89)
    f8805000 f880dd80 HIDCLASS HIDCLASS.SYS Wed Aug 04 07:08:18 2004 (41107D52)
    f8815000 f8820b80 OVCAM2 OVCAM2.sys Fri Aug 17 22:05:03 2001 (3B7D86FF)
    f8825000 f8830e00 STREAM STREAM.SYS Wed Aug 04 07:07:58 2004 (41107D3E)
    f8835000 f8843d80 sysaudio sysaudio.sys Wed Aug 04 07:15:54 2004 (41107F1A)
    f88b5000 f88bdd00 intelppm intelppm.sys Wed Aug 04 06:59:19 2004 (41107B37)
    f88c5000 f88d1180 cdrom cdrom.sys Wed Aug 04 06:59:52 2004 (41107B58)
    f88d5000 f88e3080 redbook redbook.sys Wed Aug 04 06:59:34 2004 (41107B46)
    f88e5000 f88f3b80 drmk drmk.sys Wed Aug 04 07:07:54 2004 (41107D3A)
    f88f5000 f8904d80 serial serial.sys Wed Aug 04 07:15:51 2004 (41107F17)
    f8905000 f8911e00 i8042prt i8042prt.sys Wed Aug 04 07:14:36 2004 (41107ECC)
    f8915000 f8921880 rasl2tp rasl2tp.sys Wed Aug 04 07:14:21 2004 (41107EBD)
    f8925000 f892f200 raspppoe raspppoe.sys Wed Aug 04 07:05:06 2004 (41107C92)
    f8935000 f8940d00 raspptp raspptp.sys Wed Aug 04 07:14:26 2004 (41107EC2)
    f8945000 f894d900 msgpc msgpc.sys Wed Aug 04 07:04:11 2004 (41107C5B)
    f8955000 f8963a20 odysseyIM3 odysseyIM3.sys Wed Jan 07 00:42:40 2004 (3FFB5600)
    f8965000 f896ef00 termdd termdd.sys Wed Aug 04 06:58:52 2004 (41107B1C)
    f8975000 f897b200 PCIIDEX PCIIDEX.SYS Wed Aug 04 06:59:40 2004 (41107B4C)
    f897d000 f8981900 PartMgr PartMgr.sys Sat Aug 18 02:32:23 2001 (3B7DC5A7)
    f8a15000 f8a1c000 GEARAspiWDM GEARAspiWDM.sys Mon Aug 07 18:11:27 2006 (44D7743F)
    f8a1d000 f8a22000 usbuhci usbuhci.sys Wed Aug 04 07:08:34 2004 (41107D62)
    f8a25000 f8a26000 fdc fdc.sys unavailable (00000000)
    f8a2d000 f8a33000 kbdclass kbdclass.sys Wed Aug 04 06:58:32 2004 (41107B08)
    f8a35000 f8a39880 TDI TDI.SYS Wed Aug 04 07:07:47 2004 (41107D33)
    f8a3d000 f8a41580 ptilink ptilink.sys Fri Aug 17 21:49:53 2001 (3B7D8371)
    f8a45000 f8a49080 raspti raspti.sys Fri Aug 17 21:55:32 2001 (3B7D84C4)
    f8a4d000 f8a52a00 mouclass mouclass.sys Wed Aug 04 06:58:32 2004 (41107B08)
  8. chris_uk_lad

    chris_uk_lad Newcomer, in training Topic Starter

    f8a55000 f8a5a000 flpydisk flpydisk.sys Wed Aug 04 06:59:24 2004 (41107B3C)
    f8a65000 f8a6a200 vga vga.sys Wed Aug 04 07:07:06 2004 (41107D0A)
    f8a6d000 f8a71a80 Msfs Msfs.SYS Wed Aug 04 07:00:37 2004 (41107B85)
    f8a75000 f8a7c880 Npfs Npfs.SYS Wed Aug 04 07:00:38 2004 (41107B86)
    f8a7d000 f8a83180 HIDPARSE HIDPARSE.SYS Wed Aug 04 07:08:15 2004 (41107D4F)
    f8a85000 f8a8bd80 OVCD OVCD.sys Fri Aug 17 22:05:10 2001 (3B7D8706)
    f8a95000 f8a9bc80 avg7rsxp avg7rsxp.sys Tue Jan 30 15:08:42 2007 (45BF5F7A)
    f8aa5000 f8aa9500 watchdog watchdog.sys Wed Aug 04 07:07:32 2004 (41107D24)
    f8b05000 f8b08000 BOOTVID BOOTVID.dll Fri Aug 17 21:49:09 2001 (3B7D8345)
    f8b99000 f8b9b280 rasacd rasacd.sys Fri Aug 17 21:55:39 2001 (3B7D84CB)
    f8bbd000 f8bbf580 hidusb hidusb.sys Fri Aug 17 22:02:16 2001 (3B7D8658)
    f8bc1000 f8bc3f80 mouhid mouhid.sys Fri Aug 17 21:47:57 2001 (3B7D82FD)
    f8bd5000 f8bd8c80 serenum serenum.sys Wed Aug 04 06:59:06 2004 (41107B2A)
    f8bd9000 f8bdb980 gameenum gameenum.sys Wed Aug 04 07:08:20 2004 (41107D54)
    f8bdd000 f8bdf580 ndistapi ndistapi.sys Fri Aug 17 21:55:29 2001 (3B7D84C1)
    f8bf5000 f8bf6b80 kdcom kdcom.dll Fri Aug 17 21:49:10 2001 (3B7D8346)
    f8bf7000 f8bf8100 WMILIB WMILIB.SYS Fri Aug 17 22:07:23 2001 (3B7D878B)
    f8bf9000 f8bfa500 viaide viaide.sys Wed Aug 04 06:59:42 2004 (41107B4E)
    f8bfb000 f8bfc700 dmload dmload.sys Fri Aug 17 21:58:15 2001 (3B7D8567)
    f8bfd000 f8bfea80 ParVdm ParVdm.SYS Fri Aug 17 21:49:49 2001 (3B7D836D)
    f8c23000 f8c24100 swenum swenum.sys Wed Aug 04 06:58:41 2004 (41107B11)
    f8c2b000 f8c2c280 USBD USBD.SYS Fri Aug 17 22:02:58 2001 (3B7D8682)
    f8c2d000 f8c2ef00 Fs_Rec Fs_Rec.SYS Fri Aug 17 21:49:37 2001 (3B7D8361)
    f8c2f000 f8c30080 Beep Beep.SYS Fri Aug 17 21:47:33 2001 (3B7D82E5)
    f8c31000 f8c32080 mnmdd mnmdd.SYS Fri Aug 17 21:57:28 2001 (3B7D8538)
    f8c33000 f8c34080 RDPCDD RDPCDD.sys Fri Aug 17 21:46:56 2001 (3B7D82C0)
    f8c35000 f8c36080 avg7rsw avg7rsw.sys Tue Jul 26 13:10:51 2005 (42E6284B)
    f8c3d000 f8c3e100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 22:07:23 2001 (3B7D878B)
    f8c55000 f8c56360 avgtdi avgtdi.sys Thu Aug 25 10:59:58 2005 (430D969E)
    f8d00000 f8d00d00 dxgthk dxgthk.sys Fri Aug 17 21:53:12 2001 (3B7D8438)
    f8d8d000 f8d8db80 Null Null.SYS Fri Aug 17 21:47:39 2001 (3B7D82EB)
    f8d8e000 f8d8f000 avgclean avgclean.sys Mon Dec 03 12:09:01 2007 (4753F1DD)
    f8e32000 f8e32c00 audstub audstub.sys Fri Aug 17 21:59:40 2001 (3B7D85BC)

    Unloaded modules:
    f5ed9000 f5ef1000 dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba22e000 ba258000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f8d7b000 f8d7c000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    babd8000 babe5000 DMusic.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba258000 ba27b000 aec.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    babe8000 babf6000 swmidi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f8c9d000 f8c9f000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f87d5000 f87e0000 imapi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f87c5000 f87ce000 processr.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f8a5d000 f8a62000 Cdaudio.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f8b95000 f8b98000 Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:\debuglog.txt
  9. kimsland

    kimsland Ex-TechSpotter Posts: 18,353

    Gods sake!
    I'm glad you are now allowed to attach (using the paperclip in a new message)
    Because this is huge

    Here's the fault: ntoskrnl.exe

    You may want to do a search on Google just on that exe, you'll get lots of responses (You might be able to hear, that I'm leaving this to you!!)

    Also I meant, you need SP2 (not don't install it) SP2 fixes a lot of issues (SP3 coming out this year too)
  10. chris_uk_lad

    chris_uk_lad Newcomer, in training Topic Starter

    from what ive been reading i should replace the current ntoskrnl.exe via the following method:

    reovery console:
    expand d:\i386\ntoskrnl.ex_ c:\windows\system32

    gonna attempt, hopefully solve the problem :)
  11. kimsland

    kimsland Ex-TechSpotter Posts: 18,353

    • Start your computer with your XP CD
    • Press the R key to enter the recovery console.
    • Select the operating system you wish to fix
    • Type 1 to logon to the administrator account, then enter.
    • Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
    • Type Y to overwrite the existing file.
    • Type exit to reboot the computer.
  12. chris_uk_lad

    chris_uk_lad Newcomer, in training Topic Starter

    tried the above, caused issue with ntfs.sys and another file kpdlnpl.exe or something, tried allsorts in recovery console to revert but decided just to do a complete reformat, figuring that the change SP2 makes to ntoskrnl.exe cause the issue.

    Dont know now, reformatted, only installed antivirus and internet, no audio/graphic/anything drivers and has occured again.

    New minidump attatched having learned my lesson from last ;)
  13. kimsland

    kimsland Ex-TechSpotter Posts: 18,353

    Inside the new MiniDump:

    Bugcheck 7F refers to Hardware fault (ie Ram; M/b or CPU)

    But, have you also installed all the chipset drivers?

    To confirm Ram, please run Memtest for 7 Passes
     
  14. chris_uk_lad

    chris_uk_lad Newcomer, in training Topic Starter

    Ran it once today and no errors, shall run tommorow for the advised 7 times.

    Chipset drivers??? im unaware of these im afraid. Could oyu give me a hint of what im looking for?
  15. kimsland

    kimsland Ex-TechSpotter Posts: 18,353

  16. cpc2004

    cpc2004 Newcomer, in training Posts: 2,044

    Bugcheck code i9C is hardware error and Bugcheck 7F with intel interrupt code d is also related to hardware error.

    From the stack trace, I find the footprint of CopressorError. I believe the culprit is either the CPU or ram.

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8053bd98 804d8362 0000007f 0000000d 00000000 nt!KeBugCheckEx+0x19
    8053bdcc 804e9f3a 81e3d948 81cb1000 ffdff9c0 nt!KiCoprocessorError+0xe2 <--- ??
    8053be24 804ea0ab 0001000c 0000003f 8053be38 nt!KeInsertQueueDpc+0xbf
    8053beb4 80529bcf 80544640 805443e0 ffdff000 nt!KeSynchronizeExecution+0x13c
    8053bed0 804f0264 00000000 0000000e 00000000 nt!PoRegisterDeviceNotify+0x7d6
    8053bed4 00000000 0000000e 00000000 00000000 nt!KiDispatchInterrupt+0x2bb

    Refer the following problem and it crashed with bugcheck code 9C and BP4 is 84010400

    http://www.techspot.com/vb/topic36391.html
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.