locked
System locks and restarts WHEA-Logger Event ID 18 RRS feed

  • Question

  • I have an HP e9150t pc with Intel i7 CPU 2.67GHz 8gig 64bit Win7 Ultimate that Blue Screens. I updated the BIOS. The on board diags say everything is fine.

    Log Name:      System
    Source:        Microsoft-Windows-WHEA-Logger
    Date:          7/12/2010 4:30:00 PM
    Event ID:      18
    Task Category: None
    Level:         Error
    Keywords:     
    User:          LOCAL SERVICE
    Computer:      JohnW7
    Description:
    A fatal hardware error has occurred.

    Reported by component: Processor Core
    Error Source: Machine Check Exception
    Error Type: Internal Timer Error
    Processor ID: 4

    The system log also shows this error on Processor ID:2

    Does not seem to be associated with an application. It just did it with IE and Outlook open.

    Suggestions?

    Thanks,
    John

    Monday, July 12, 2010 9:13 PM

Answers

  • Since Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a third-party device drivers, backup software or anti-virus services (buggy services).

    The system goes to a BSOD because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are).

    To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call.

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

    Microsoft - Help and Support
    http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

    If you are outside the US please see Microsoft Worldwide Home for regional support phone numbers.
    http://www.microsoft.com/worldwide/

    Meantime, you can refer the following KB for troubleshoot.

    Windows Kernel event ID 41 error in Windows 7 or in Windows Server 2008 R2: “The system has rebooted without cleanly shutting down first”
    http://support.microsoft.com/kb/2028504/en-us

    Regards,


    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 Magon Liu Friday, July 23, 2010 7:19 AM
    Thursday, July 15, 2010 10:17 AM

All replies

  • Please upload the dmp files from the folder C:\Windows\Minidump to your Skydrive [1] (copy the dmp files first to your desktop, otherwise you can't upload them) and post a link here, so that we can look at the dumps.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Monday, July 12, 2010 10:10 PM
  • Tuesday, July 13, 2010 6:34 PM
  • Hi John,

    you have an internal Timer issue:

    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 7/12/2010 20:29:10
    Flags         : 0x00000002 PreviousError

    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800a4cb428
    Section       @ fffffa800a4cb500
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal

    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Micro-Architectural Error
    Flags         : 0x00
    CPU Version   : 0x00000000000106a5
    Processor ID  : 0x0000000000000002

    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800a4cb470
    Section       @ fffffa800a4cb5c0
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal

    Local APIC Id : 0x0000000000000002
    CPU Id        : a5 06 01 00 00 08 10 02 - bd e3 98 00 ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

    Proc. Info 0  @ fffffa800a4cb5c0

    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800a4cb4b8
    Section       @ fffffa800a4cb640
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal

    Error         : Internal timer (Proc 2 Bank 5)
      Status      : 0xbe00000000800400
      Address     : 0x0000388005aa4f8b
      Misc.       : 0x0000000000007fff

    Disable the turbo feature, update to the latest BIOS, revert any OC. If nothing works, take advantage of your warranty and try to get a new CPU.


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Proposed as answer by Andre.Ziegler Tuesday, July 13, 2010 10:34 PM
    Tuesday, July 13, 2010 10:34 PM
  • Thanks for looking at this. Please explain "revert any OC ".

    John

    Wednesday, July 14, 2010 12:34 AM
  • Please explain "revert any OC ".

    Hi John.

    OC = Overclocking. This means running the CPU with a higher speed as it runs by default. If you do this, revert it back to the default CPU speed settings.

    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Wednesday, July 14, 2010 12:40 PM
  • André, Thanks for explaining. I don't over clock.

    I will check the "turbo mode".

    John

    Wednesday, July 14, 2010 3:33 PM
  • Since Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a third-party device drivers, backup software or anti-virus services (buggy services).

    The system goes to a BSOD because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are).

    To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call.

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

    Microsoft - Help and Support
    http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

    If you are outside the US please see Microsoft Worldwide Home for regional support phone numbers.
    http://www.microsoft.com/worldwide/

    Meantime, you can refer the following KB for troubleshoot.

    Windows Kernel event ID 41 error in Windows 7 or in Windows Server 2008 R2: “The system has rebooted without cleanly shutting down first”
    http://support.microsoft.com/kb/2028504/en-us

    Regards,


    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 Magon Liu Friday, July 23, 2010 7:19 AM
    Thursday, July 15, 2010 10:17 AM