locked
Blue screen issue Windows 7 RRS feed

  • Question

  • Hi there, I am experiencing issues with blue screens on my Windows 7 shipped Dell i7. It is rather strange as I keep the system up-to-date. I am unfortunately on a slow Internet connection with limited download capacity and as such cannot download the debugging file. I have loaded two dmp files to this location, and I'm hoping these can be analysed in order to offer up possible causes and/or solutions. http://cid-12bb1dbfc931f79d.skydrive.live.com/redir.aspx?resid=12BB1DBFC931F79D!146 I would really appreciate any help anyone is able to offer.
    Monday, June 6, 2011 3:33 PM

Answers

  • Hi,

     

    After viewing the dump file, I found the Bug Check 0x9C: MACHINE_CHECK_EXCEPTION is caused by intelppm.sys.

     

    The intelppm.sys is Intel processor drive. I suggest updating the Intel chipset drivers, graphic drivers and network adapter drivers from Dell site.

     

    http://support.dell.com/support/index.aspx?c=us&cs=19&l=en&s=dhs

     

    Also open an elevated command and run chkdsk /f /r command to check the hard drive. Test if the issue occurs in Safe Mode.

     

    Best Regards,

    Niki


    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Niki Han Monday, June 13, 2011 2:02 AM
    Wednesday, June 8, 2011 9:46 AM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffff880030f7180, The PRCB address of the hung processor.
    Arg4: 0000000000000006, 0.
    Debugging Details:
    ------------------
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  d
    STACK_TEXT:  
    fffff800`07140c48 fffff800`02ce18f9 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`030f7180 : nt!KeBugCheckEx
    fffff800`07140c50 fffff800`02c944b7 : 00000000`00000000 fffff800`00000006 00000000`00002711 fffff800`02c1eb75 : nt! ?? ::FNODOBFM::`string'+0x4e2e
    fffff800`07140ce0 fffff800`031fd895 : fffff800`03223460 fffff800`07140e90 fffff800`03223460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
    fffff800`07140de0 fffff800`02c86233 : 2aaaaaaa`aaaaaaab 2aaaaaaa`aaaaaaab fffff800`07140e80 fffffa80`03a83800 : hal!HalpHpetClockInterrupt+0x8d
    fffff800`07140e10 fffff800`02cc03bd : fffffa80`056d8770 00000000`000007ff fffffa80`05d4a000 00000000`3231555f : nt!KiInterruptDispatchNoLock+0x163
    fffff800`07140fa0 fffff800`02c8f82c : 00000000`00000000 fffff800`07141188 00000000`00000001 00000000`000007ff : nt!KxFlushEntireTb+0xc5
    fffff800`07140fe0 fffff800`02cc451f : 00000000`00000000 00000000`00000001 fffff800`07141180 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x28c
    fffff800`071410b0 fffff800`02c7e2ec : 00000000`00000000 fffff6fb`00000000 00000000`00000005 00000000`00004c00 : nt!MiReturnSystemVa+0x2af
    fffff800`07141150 fffff800`02db2514 : fffffa80`0009b010 fffffa80`03a84980 00000000`00000002 fffffa80`08400000 : nt!MiReturnNonPagedPoolVa+0x34c
    fffff800`07141270 fffff800`02db6557 : fffffa80`08400000 00000000`00000000 fffff6fb`7ea00210 00000000`00000001 : nt!MiFreePoolPages+0x214
    fffff800`07141380 fffff880`014aa195 : 00000000`00000000 fffff880`058a0e60 fffffa80`3331555f fffff880`00000000 : nt!ExFreePoolWithTag+0x7c7
    fffff800`07141430 fffff880`056e9e42 : fffffa80`05219c10 fffffa80`06c90820 fffffa80`056c6c10 fffff880`056e7805 : ndis!NdisFreeMemory+0x15
    fffff800`07141460 fffffa80`05219c10 : fffffa80`06c90820 fffffa80`056c6c10 fffff880`056e7805 00000000`00000000 : 0xfffff880`056e9e42
    fffff800`07141468 fffffa80`06c90820 : fffffa80`056c6c10 fffff880`056e7805 00000000`00000000 fffff880`056e8d70 : 0xfffffa80`05219c10
    fffff800`07141470 fffffa80`056c6c10 : fffff880`056e7805 00000000`00000000 fffff880`056e8d70 fffffa80`056a06a0 : 0xfffffa80`06c90820
    fffff800`07141478 fffff880`056e7805 : 00000000`00000000 fffff880`056e8d70 fffffa80`056a06a0 fffff880`056e6cdc : 0xfffffa80`056c6c10
    fffff800`07141480 00000000`00000000 : fffff880`056e8d70 fffffa80`056a06a0 fffff880`056e6cdc fffffa80`0579fad0 : 0xfffff880`056e7805
    STACK_COMMAND:  kb
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: Unknown_Module
    IMAGE_NAME:  Unknown_Image
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    Followup: MachineOwner
    ---------
    ___________________________________________________________
    I suspect that there is a problem with your processor. Start updating your processor driver and if the problem persist, I recommand contacting your manufacturer Technical Support.
    I see multiple drivers that have not been updated since 2009 so please update them also.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

    • Marked as answer by Niki Han Monday, June 13, 2011 2:02 AM
    Wednesday, June 8, 2011 10:06 AM

All replies

  • The 0x9c error = hardware.

    The 0x101 is also probably hardware, study this post to gain some understanding of the specific error.

    Contact Dell.

    Monday, June 6, 2011 4:05 PM
  • Hi,

     

    After viewing the dump file, I found the Bug Check 0x9C: MACHINE_CHECK_EXCEPTION is caused by intelppm.sys.

     

    The intelppm.sys is Intel processor drive. I suggest updating the Intel chipset drivers, graphic drivers and network adapter drivers from Dell site.

     

    http://support.dell.com/support/index.aspx?c=us&cs=19&l=en&s=dhs

     

    Also open an elevated command and run chkdsk /f /r command to check the hard drive. Test if the issue occurs in Safe Mode.

     

    Best Regards,

    Niki


    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Niki Han Monday, June 13, 2011 2:02 AM
    Wednesday, June 8, 2011 9:46 AM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffff880030f7180, The PRCB address of the hung processor.
    Arg4: 0000000000000006, 0.
    Debugging Details:
    ------------------
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  d
    STACK_TEXT:  
    fffff800`07140c48 fffff800`02ce18f9 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`030f7180 : nt!KeBugCheckEx
    fffff800`07140c50 fffff800`02c944b7 : 00000000`00000000 fffff800`00000006 00000000`00002711 fffff800`02c1eb75 : nt! ?? ::FNODOBFM::`string'+0x4e2e
    fffff800`07140ce0 fffff800`031fd895 : fffff800`03223460 fffff800`07140e90 fffff800`03223460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
    fffff800`07140de0 fffff800`02c86233 : 2aaaaaaa`aaaaaaab 2aaaaaaa`aaaaaaab fffff800`07140e80 fffffa80`03a83800 : hal!HalpHpetClockInterrupt+0x8d
    fffff800`07140e10 fffff800`02cc03bd : fffffa80`056d8770 00000000`000007ff fffffa80`05d4a000 00000000`3231555f : nt!KiInterruptDispatchNoLock+0x163
    fffff800`07140fa0 fffff800`02c8f82c : 00000000`00000000 fffff800`07141188 00000000`00000001 00000000`000007ff : nt!KxFlushEntireTb+0xc5
    fffff800`07140fe0 fffff800`02cc451f : 00000000`00000000 00000000`00000001 fffff800`07141180 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x28c
    fffff800`071410b0 fffff800`02c7e2ec : 00000000`00000000 fffff6fb`00000000 00000000`00000005 00000000`00004c00 : nt!MiReturnSystemVa+0x2af
    fffff800`07141150 fffff800`02db2514 : fffffa80`0009b010 fffffa80`03a84980 00000000`00000002 fffffa80`08400000 : nt!MiReturnNonPagedPoolVa+0x34c
    fffff800`07141270 fffff800`02db6557 : fffffa80`08400000 00000000`00000000 fffff6fb`7ea00210 00000000`00000001 : nt!MiFreePoolPages+0x214
    fffff800`07141380 fffff880`014aa195 : 00000000`00000000 fffff880`058a0e60 fffffa80`3331555f fffff880`00000000 : nt!ExFreePoolWithTag+0x7c7
    fffff800`07141430 fffff880`056e9e42 : fffffa80`05219c10 fffffa80`06c90820 fffffa80`056c6c10 fffff880`056e7805 : ndis!NdisFreeMemory+0x15
    fffff800`07141460 fffffa80`05219c10 : fffffa80`06c90820 fffffa80`056c6c10 fffff880`056e7805 00000000`00000000 : 0xfffff880`056e9e42
    fffff800`07141468 fffffa80`06c90820 : fffffa80`056c6c10 fffff880`056e7805 00000000`00000000 fffff880`056e8d70 : 0xfffffa80`05219c10
    fffff800`07141470 fffffa80`056c6c10 : fffff880`056e7805 00000000`00000000 fffff880`056e8d70 fffffa80`056a06a0 : 0xfffffa80`06c90820
    fffff800`07141478 fffff880`056e7805 : 00000000`00000000 fffff880`056e8d70 fffffa80`056a06a0 fffff880`056e6cdc : 0xfffffa80`056c6c10
    fffff800`07141480 00000000`00000000 : fffff880`056e8d70 fffffa80`056a06a0 fffff880`056e6cdc fffffa80`0579fad0 : 0xfffff880`056e7805
    STACK_COMMAND:  kb
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: Unknown_Module
    IMAGE_NAME:  Unknown_Image
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    Followup: MachineOwner
    ---------
    ___________________________________________________________
    I suspect that there is a problem with your processor. Start updating your processor driver and if the problem persist, I recommand contacting your manufacturer Technical Support.
    I see multiple drivers that have not been updated since 2009 so please update them also.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

    • Marked as answer by Niki Han Monday, June 13, 2011 2:02 AM
    Wednesday, June 8, 2011 10:06 AM