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.

Windows Error 9c

Discussion in 'Windows XP' started by yamaha200, 2006/08/14.

  1. 2006/08/14
    yamaha200

    yamaha200 Inactive Thread Starter

    Joined:
    2006/08/14
    Messages:
    2
    Likes Received:
    0
    Hello, this is my 1st time posting in i really need help.

    I recently built my computer with all new part and i installed Windows XP home sp 2 on it. I get a 0x0000009C: MACHINE_CHECK_EXCEPTION error randomly (but i can get it to come up all the time if i try to install my HP 1410v software).

    Windows support website says it could be my RAM, CPU, Power supply, or Motherboard. I've changed the Ram, Power supply, and motherboard so far, tomrrow i'll get a temporay CPU.

    my main drivers are all up to date, i have a few like my dlink PCI card needs to be updated.

    What should i do:confused: Thanks for your help
     
  2. 2006/08/14
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    Hi, yamaha200. Welcome to Windows BBS. :)

    Since you just built the system, I suspect you may have a driver issue somewhere.

    If you go into Device Manager, do you have any "issues" (such as exclamation point icons or question mark icons) reported there? If so, what are they? (DISCLAIMER: These issues would be the things I would tackle first anyway. Other people here may advise you to proceed otherwise.)

    Device Manager can be accessed as follows:
    • While holding down your Windows Key, press your Pause Key to bring up your "System Properties" window.
    • Click on the Hardware tab.
    • Click on the Device Manager button.

    I'm guessing you may be experiencing "Blue Screen of Death" (BSOD) errors that produce the famous blue screen or cause an automatic reboot (depending on how your system is configured). If so, consider following the instructions in this link to provide more information about the particular BSOD crash errors you experience.

    EDIT: Other people here, please feel free to chime in. Do not be concerned about "stepping on my toes." :)
    I'm just trying to get yamaha200 started in the right direction as I see it.
     
    Last edited: 2006/08/14

  3. to hide this advert.

  4. 2006/08/15
    yamaha200

    yamaha200 Inactive Thread Starter

    Joined:
    2006/08/14
    Messages:
    2
    Likes Received:
    0
    Ok first off, thanks mailman for replying,

    Now, i was able to make a debuglog from the program you told me to download. From what i gathered is my processor is the problem. I am running a intel Pentium D 3.00GHz 2x2 L2 cache with a ECS P4m800pro-M V1.0a motherboard.



    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\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is 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.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
    Debug session time: Tue Aug 15 11:15:59.828 2006 (GMT-7)
    System Uptime: 0 days 0:04:54.390
    WARNING: Process directory table base 00039000 doesn't match CR3 06C40000
    WARNING: Process directory table base 00039000 doesn't match CR3 06C40000
    Loading Kernel Symbols
    .............................................................................................................
    Loading User Symbols

    Loading unloaded module list
    ...
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

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

    Probably caused by : intelppm.sys ( intelppm!AcpiC1Idle+12 )

    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: f7ac2050
    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

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    PROCESS_NAME: Idle

    LAST_CONTROL_TRANSFER: from 80702bff to 805371aa

    STACK_TEXT:
    f7ac2028 80702bff 0000009c 00000000 f7ac2050 nt!KeBugCheckEx+0x1b
    f7ac2154 806fdc52 f7abed70 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd
    f7ac2154 f79a0062 f7abed70 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x4a
    f7c55d50 804dcbef 00000000 0000000e ffffff7f intelppm!AcpiC1Idle+0x12
    f7c55d54 00000000 0000000e ffffff7f ffeffffb nt!KiIdleLoop+0x10


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    intelppm!AcpiC1Idle+12
    f79a0062 6a00 push 0

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: intelppm!AcpiC1Idle+12

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: intelppm

    IMAGE_NAME: intelppm.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 41107b37

    FAILURE_BUCKET_ID: 0x9C_IA32_GenuineIntel_intelppm!AcpiC1Idle+12

    BUCKET_ID: 0x9C_IA32_GenuineIntel_intelppm!AcpiC1Idle+12

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

    eax=f7abe13c ebx=f7ac2050 ecx=00000000 edx=00000000 esi=1040080f edi=b2000000
    eip=805371aa esp=f7ac2010 ebp=f7ac2028 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:
    805371aa 5d pop ebp
    ChildEBP RetAddr Args to Child
    f7ac2028 80702bff 0000009c 00000000 f7ac2050 nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo])
    f7ac2154 806fdc52 f7abed70 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd (FPO: [Non-Fpo])
    f7ac2154 f79a0062 f7abed70 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x4a (FPO: TSS 28:0)
    f7c55d50 804dcbef 00000000 0000000e ffffff7f intelppm!AcpiC1Idle+0x12 (FPO: [0,2,0])
    f7c55d54 00000000 0000000e ffffff7f ffeffffb nt!KiIdleLoop+0x10 (FPO: [0,0,0])
    start end module name
    804d7000 806fd000 nt ntkrnlmp.exe Tue Mar 01 16:57:27 2005 (42250F77)
    806fd000 8071dd00 hal halmacpi.dll Tue Aug 03 22:59:09 2004 (41107B2D)
    b9490000 b94a7480 dump_atapi dump_atapi.sys Tue Aug 03 22:59:41 2004 (41107B4D)
    b94f8000 b9538280 HTTP HTTP.sys Thu Mar 16 16:33:09 2006 (441A03C5)
    b9599000 b95a3800 fetnd5bv fetnd5bv.sys Mon Jun 12 03:05:11 2006 (448D3C57)
    b98e9000 b98f8900 Cdfs Cdfs.SYS Tue Aug 03 23:14:09 2004 (41107EB1)
    b9a61000 b9ab2400 srv srv.sys Thu Apr 20 23:12:25 2006 (444877C9)
    b9cbb000 b9ce7400 mrxdav mrxdav.sys Tue Aug 03 23:00:49 2004 (41107B91)
    ba5f4000 ba5f7280 ndisuio ndisuio.sys Tue Aug 03 23:03:10 2004 (41107C1E)
    bf000000 bf011580 dxg dxg.sys Tue Aug 03 23:00:51 2004 (41107B93)
    bf012000 bf463d00 nv4_disp nv4_disp.dll Thu Jun 01 18:06:00 2006 (447F8EF8)
    bf800000 bf9c1180 win32k win32k.sys Wed Oct 05 17:05:44 2005 (43446A58)
    f49ec000 f49f2de0 ANIO ANIO.SYS Mon May 05 03:18:54 2003 (3EB63A8E)
    f4fc2000 f4fe5000 Fastfat Fastfat.SYS Tue Aug 03 23:14:15 2004 (41107EB7)
    f5392000 f5394900 Dxapi Dxapi.sys Fri Aug 17 13:53:19 2001 (3B7D843F)
    f53cd000 f53d1500 watchdog watchdog.sys Tue Aug 03 23:07:32 2004 (41107D24)
    f54e8000 f55a5d00 avg7core avg7core.sys Mon Jul 03 16:41:42 2006 (44A9AB36)
    f55a6000 f5614a00 mrxsmb mrxsmb.sys Fri May 05 02:41:42 2006 (445B1DD6)
    f563d000 f5667a00 rdbss rdbss.sys Fri May 05 02:47:55 2006 (445B1F4B)
    f5708000 f5729d00 afd afd.sys Tue Aug 03 23:14:13 2004 (41107EB5)
    f572a000 f574af00 ipnat ipnat.sys Wed Sep 29 15:28:36 2004 (415B3714)
    f574b000 f5772c00 netbt netbt.sys Tue Aug 03 23:14:36 2004 (41107ECC)
    f5773000 f57cad80 tcpip tcpip.sys Thu Apr 20 04:51:47 2006 (444775D3)
    f57cb000 f57dd400 ipsec ipsec.sys Tue Aug 03 23:14:27 2004 (41107EC3)
    f5ab9000 f5abcf60 HPZipr12 HPZipr12.sys Tue Sep 28 23:41:44 2004 (415A5928)
    f5d45000 f5d48b00 usbscan usbscan.sys Tue Aug 03 22:58:44 2004 (41107B14)
    f709b000 f70ce200 update update.sys Tue Aug 03 22:58:32 2004 (41107B08)
    f70cf000 f70dfe00 psched psched.sys Tue Aug 03 23:04:16 2004 (41107C60)
    f7110000 f711c6a0 HPZid412 HPZid412.sys Tue Sep 28 23:41:41 2004 (415A5925)
    f7150000 f7158880 Fips Fips.SYS Fri Aug 17 18:31:49 2001 (3B7DC585)
    f7160000 f7168700 netbios netbios.sys Tue Aug 03 23:03:19 2004 (41107C27)
    f7170000 f7178700 wanarp wanarp.sys Tue Aug 03 23:04:57 2004 (41107C89)
    f7180000 f7196680 ndiswan ndiswan.sys Tue Aug 03 23:14:30 2004 (41107EC6)
    f7197000 f71aa900 parport parport.sys Tue Aug 03 22:59:04 2004 (41107B28)
    f71ab000 f71cde80 USBPORT USBPORT.SYS Tue Aug 03 23:08:34 2004 (41107D62)
    f71ce000 f71f0680 ks ks.sys Tue Aug 03 23:15:20 2004 (41107EF8)
    f71f1000 f725ef60 A3AB A3AB.sys Tue Mar 22 19:17:32 2005 (4240DFCC)
    f725f000 f7272780 VIDEOPRT VIDEOPRT.SYS Tue Aug 03 23:07:04 2004 (41107D08)
    f7273000 f76317a0 nv4_mini nv4_mini.sys Thu Jun 01 18:11:09 2006 (447F902D)
    f767a000 f7694580 Mup Mup.sys Tue Aug 03 23:15:20 2004 (41107EF8)
    f7695000 f76c1a80 NDIS NDIS.sys Tue Aug 03 23:14:27 2004 (41107EC3)
    f76c2000 f774e480 Ntfs Ntfs.sys Tue Aug 03 23:15:06 2004 (41107EEA)
    f774f000 f7765780 KSecDD KSecDD.sys Tue Aug 03 22:59:45 2004 (41107B51)
    f7766000 f7777f00 sr sr.sys Tue Aug 03 23:06:22 2004 (41107CDE)
    f7778000 f7796780 fltMgr fltMgr.sys Tue Aug 03 23:01:17 2004 (41107BAD)
    f7797000 f77ae480 atapi atapi.sys Tue Aug 03 22:59:41 2004 (41107B4D)
    f77af000 f77cd880 ftdisk ftdisk.sys Fri Aug 17 13:52:41 2001 (3B7D8419)
    f77ce000 f77dea80 pci pci.sys Tue Aug 03 23:07:45 2004 (41107D31)
    f77df000 f780cd80 ACPI ACPI.sys Tue Aug 03 23:07:35 2004 (41107D27)
    f782e000 f7836c00 isapnp isapnp.sys Fri Aug 17 13:58:01 2001 (3B7D8559)
    f783e000 f7848500 MountMgr MountMgr.sys Tue Aug 03 22:58:29 2004 (41107B05)
    f784e000 f785ac80 VolSnap VolSnap.sys Tue Aug 03 23:00:14 2004 (41107B6E)
    f785e000 f7866e00 disk disk.sys Tue Aug 03 22:59:53 2004 (41107B59)
    f786e000 f787a200 CLASSPNP CLASSPNP.SYS Tue Aug 03 23:14:26 2004 (41107EC2)
    f787e000 f7888e80 uagp35 uagp35.sys Tue Aug 03 23:07:43 2004 (41107D2F)
    f790e000 f791c100 usbhub usbhub.sys Tue Aug 03 23:08:40 2004 (41107D68)
    f799e000 f79a6d00 intelppm intelppm.sys Tue Aug 03 22:59:19 2004 (41107B37)
    f79ae000 f79b8380 imapi imapi.sys Tue Aug 03 23:00:12 2004 (41107B6C)
    f79be000 f79ca180 cdrom cdrom.sys Tue Aug 03 22:59:52 2004 (41107B58)
    f79ce000 f79dc080 redbook redbook.sys Tue Aug 03 22:59:34 2004 (41107B46)
    f79de000 f79eae00 i8042prt i8042prt.sys Tue Aug 03 23:14:36 2004 (41107ECC)
    f79ee000 f79fdd80 serial serial.sys Tue Aug 03 23:15:51 2004 (41107F17)
    f79fe000 f7a0a880 rasl2tp rasl2tp.sys Tue Aug 03 23:14:21 2004 (41107EBD)
    f7a0e000 f7a18200 raspppoe raspppoe.sys Tue Aug 03 23:05:06 2004 (41107C92)
    f7a1e000 f7a29d00 raspptp raspptp.sys Tue Aug 03 23:14:26 2004 (41107EC2)
    f7a2e000 f7a36900 msgpc msgpc.sys Tue Aug 03 23:04:11 2004 (41107C5B)
    f7a3e000 f7a47f00 termdd termdd.sys Tue Aug 03 22:58:52 2004 (41107B1C)
    f7a8e000 f7a97480 NDProxy NDProxy.SYS Fri Aug 17 13:55:30 2001 (3B7D84C2)
    f7aae000 f7ab4200 PCIIDEX PCIIDEX.SYS Tue Aug 03 22:59:40 2004 (41107B4C)
    f7ab6000 f7aba900 PartMgr PartMgr.sys Fri Aug 17 18:32:23 2001 (3B7DC5A7)
    f7b56000 f7b5b000 usbuhci usbuhci.sys Tue Aug 03 23:08:34 2004 (41107D62)
    f7b5e000 f7b64800 usbehci usbehci.sys Tue Aug 03 23:08:34 2004 (41107D62)
    f7b66000 f7b6c000 kbdclass kbdclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
    f7b6e000 f7b73a00 mouclass mouclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
    f7b76000 f7b7d000 fdc fdc.sys unavailable (FFFFFFFE)
    f7b7e000 f7b82880 TDI TDI.SYS Tue Aug 03 23:07:47 2004 (41107D33)
    f7b86000 f7b8a580 ptilink ptilink.sys Fri Aug 17 13:49:53 2001 (3B7D8371)
    f7b8e000 f7b92080 raspti raspti.sys Fri Aug 17 13:55:32 2001 (3B7D84C4)
    f7bce000 f7bd3000 flpydisk flpydisk.sys Tue Aug 03 22:59:24 2004 (41107B3C)
    f7bde000 f7be3200 vga vga.sys Tue Aug 03 23:07:06 2004 (41107D0A)
    f7be6000 f7beaa80 Msfs Msfs.SYS Tue Aug 03 23:00:37 2004 (41107B85)
    f7bee000 f7bf5880 Npfs Npfs.SYS Tue Aug 03 23:00:38 2004 (41107B86)
    f7c06000 f7c0db80 usbccgp usbccgp.sys Tue Aug 03 23:08:45 2004 (41107D6D)
    f7c0e000 f7c14d00 avg7rsxp avg7rsxp.sys Sun Jun 25 16:45:43 2006 (449F2027)
    f7c1e000 f7c24500 usbprint usbprint.sys Tue Aug 03 23:01:23 2004 (41107BB3)
    f7c2e000 f7c333e0 HPZius12 HPZius12.sys Tue Sep 28 23:40:14 2004 (415A58CE)
    f7c3e000 f7c41000 BOOTVID BOOTVID.dll Fri Aug 17 13:49:09 2001 (3B7D8345)
    f7cc6000 f7cc8280 rasacd rasacd.sys Fri Aug 17 13:55:39 2001 (3B7D84CB)
    f7ce6000 f7ce9c80 serenum serenum.sys Tue Aug 03 22:59:06 2004 (41107B2A)
    f7cea000 f7cec580 ndistapi ndistapi.sys Fri Aug 17 13:55:29 2001 (3B7D84C1)
    f7cfa000 f7cfdc80 mssmbios mssmbios.sys Tue Aug 03 23:07:47 2004 (41107D33)
    f7d16000 f7d18c00 vulfntr vulfntr.sys Mon Jun 06 02:51:37 2005 (42A41CA9)
    f7d2e000 f7d2fb80 kdcom kdcom.dll Fri Aug 17 13:49:10 2001 (3B7D8346)
    f7d30000 f7d31100 WMILIB WMILIB.SYS Fri Aug 17 14:07:23 2001 (3B7D878B)
    f7d32000 f7d33500 viaide viaide.sys Tue Aug 03 22:59:42 2004 (41107B4E)
    f7d34000 f7d35a80 ParVdm ParVdm.SYS Fri Aug 17 13:49:49 2001 (3B7D836D)
    f7d3a000 f7d3b380 avgtdi avgtdi.sys Sat Sep 03 17:38:58 2005 (431A4222)
    f7d60000 f7d61b00 vulfnth vulfnth.sys Wed Jan 05 02:02:08 2005 (41DBBB20)
    f7d62000 f7d63100 swenum swenum.sys Tue Aug 03 22:58:41 2004 (41107B11)
    f7d6e000 f7d6f280 USBD USBD.SYS Fri Aug 17 14:02:58 2001 (3B7D8682)
    f7d88000 f7d89f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 13:49:37 2001 (3B7D8361)
    f7d8a000 f7d8b080 Beep Beep.SYS Fri Aug 17 13:47:33 2001 (3B7D82E5)
    f7d8c000 f7d8d080 mnmdd mnmdd.SYS Fri Aug 17 13:57:28 2001 (3B7D8538)
    f7d8e000 f7d8f080 RDPCDD RDPCDD.sys Fri Aug 17 13:46:56 2001 (3B7D82C0)
    f7d92000 f7d930c0 avg7rsw avg7rsw.sys Sun Sep 18 17:09:31 2005 (432E01BB)
    f7dca000 f7dcb100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 14:07:23 2001 (3B7D878B)
    f7df6000 f7df6d00 pciide pciide.sys Fri Aug 17 13:51:49 2001 (3B7D83E5)
    f7eea000 f7eeac00 audstub audstub.sys Fri Aug 17 13:59:40 2001 (3B7D85BC)
    f7f66000 f7f66b80 Null Null.SYS Fri Aug 17 13:47:39 2001 (3B7D82EB)
    f7f67000 f7f67d00 dxgthk dxgthk.sys Fri Aug 17 13:53:12 2001 (3B7D8438)

    Unloaded modules:
    f498c000 f49a4000 dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7bd6000 f7bdb000 Cdaudio.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7cc2000 f7cc5000 Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:\debuglog.txt


    Is there anything else in here that i should know about?
     
  5. 2006/08/15
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    Hi, yamaha200. Good work with DebugWiz! :)

    I quoted snippets of your BSOD dump analysis with boldface/color emphasis added for the parts I think may be relevant.

    While I don't claim to be an expert :( regarding BSOD dump analysis, according to this 4-page article, Network World: "How to solve Windows system crashes in minutes" (specifically the last paragraph of page 3), it appears your BSOD problem might be caused by your intelppm.sys driver.

    If you Google intelppm.sys, you might find some information that will help you resolve this problem.

    You might find some helpful information about intelppm.sys on Intel's web site.

    If your search efforts are not successful, I suggest you contact Intel support with your dump analysis log and Pentium D 3.00GHz 2x2 L2 cache with a ECS P4m800pro-M V1.0a motherboard information.

    Perhaps someone else reading this thread will have some ideas.
     
    Last edited: 2006/08/15

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.