none
WHEA-Logger Event 19 - Windows 7

    Question

  • I have a brand new dell insparon 570 (AMD Athlon II X2 245 2GB), and I have had 11 thousand of these error in the two months of owning the machine.

    I have the latest bios and drivers installed.

    I download the Dell memory checking diagnostics program and rebooted and check with that and the CPU/cache seemed fine.

    Dell support ran their window base testers and 'surprise' it was happy also, thus the hardware support person was convinced it was a software problem. My concern is reading about this event implies it may be a CPU issue, thus if it's "dodgy" I'd rather it replaced now, but am unsure how to prove this is the case. Or if its completly harmless, why are there so many event entries?

    The event can happen multiple times per minute, or have 15 minutes between them. The PC is running as a media center server and doing nothing most of the day, but the warnings come thick and fast.

    Here is a recent event:

    Log Name:      System
    Source:        Microsoft-Windows-WHEA-Logger
    Date:          4/27/2011 10:51:51 PM
    Event ID:      19
    Task Category: None
    Level:         Warning
    Keywords:     
    User:          LOCAL SERVICE
    Computer:      sagetv
    Description:
    A corrected hardware error has occurred.

    Reported by component: Processor Core
    Error Source: Corrected Machine Check
    Error Type: Cache Hierarchy Error
    Processor ID: 0

    The details view of this entry contains further information.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{C26C4F3C-3F66-4E99-8F8A-39405CFED220}" />
        <EventID>19</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2011-04-28T03:51:51.494705400Z" />
        <EventRecordID>28949</EventRecordID>
        <Correlation ActivityID="{887DADAF-72D7-4B1D-A279-4653AD7CC1E8}" />
        <Execution ProcessID="1432" ThreadID="3476" />
        <Channel>System</Channel>
        <Computer>sagetv</Computer>
        <Security UserID="S-1-5-19" />
      </System>
      <EventData>
        <Data Name="ErrorSource">1</Data>
        <Data Name="ApicId">0</Data>
        <Data Name="MCABank">2</Data>
        <Data Name="MciStat">0x940041000000010a</Data>
        <Data Name="MciAddr">0x1f200780</Data>
        <Data Name="MciMisc">0x0</Data>
        <Data Name="ErrorType">9</Data>
        <Data Name="TransactionType">2</Data>
        <Data Name="Participation">256</Data>
        <Data Name="RequestType">0</Data>
        <Data Name="MemorIO">256</Data>
        <Data Name="MemHierarchyLvl">2</Data>
        <Data Name="Timeout">256</Data>
        <Data Name="OperationType">256</Data>
        <Data Name="Channel">256</Data>
        <Data Name="Length">928</Data>
        <Data Name="RawData">435045521002FFFFFFFF03000200000002000000A0030000313303001C040B140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B18BCE2DD7BD0E45B9AD9CF4EBD4F89016141D1B5405CC0100000000000000000000000000000000000000000000000058010000C00000000102000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000800000000102000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000098020000080100000102000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000200000000000000000000000000000000000000000000007F010000000000000002010000020000630F10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000000000000000000630F10000008020009208000FFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F008200000000008007201F000000000000000000000000000000000000000000000000000000000100000002000000743C889A5705CC010000000000000000000000000000000000000000020000000A010000004100948007201F0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
      </EventData>
    </Event>

     

    Thursday, April 28, 2011 4:15 AM

All replies

  • Hi,

     

    For WHEA error 19, please refer this KB:

    http://support.microsoft.com/kb/961080

     

    That should apply to Windows 7 too.

     

    Also this link about error 19 may be helpful to you:

    http://www.eventid.net/display.asp?eventid=19&eventno=9845&source=Microsoft-Windows-WHEA-Logger&phase=1

    Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

     

    Hope that helps.

     

     

    Regards,

    Leo   Huang

     

     


    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.
    Monday, May 2, 2011 2:30 AM
    Moderator
  • Thanks for the response, I'd seen both those before, and the EventId.Net site didn't have any work a rounds, other than it may be hardware. I assumed the KB fix noted for Vista and Intel chips wouldn't apply due to I'm using Win7 and an AMD chip.

    I couldn't find the AMD Machine Check Exception Analysis Tool referred to in the event id site.

    I did run the Dell check program for a few hours and it came up happy, also the Dell Hardware support people ran an even simpler version of the test, and it was happy, thus they declared it a software issue.

    Short of buying my own new CPU and RAM to swap them to test if it's those, I'm not sure how to progress this.

    Monday, May 2, 2011 4:22 PM
  • Hi,

     

    In order to determine the problem related with operation system or hardware, you can logon with Safe Mode to see if the same issue occurs.

     

    Regards,

    Leo   Huang

     

     


    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.
    Wednesday, May 4, 2011 1:14 AM
    Moderator
  • I ran the PC in Safe Mode for 1 hour and did not have any warnings, I was also running Prime95 and Windows Security Essentials (WSE) scan to exercise the machine like under normal system operations.

    I then ran the Dell Boot Daig memory check again, 30 minutes later it all passed.

    I went back to normal Win7 and got the warning without needing to run Prime or WSE. I turned off the capture card driver, remove the Wifi USB stick, and turned of my media center service (SageTV), rebooted and had the warnings.

    I removed the capture hard from the system, and in normal Win7 had the warnings.

    I turned the device driver off for the flash card reader, DVD drive (TSS corp), On-board Ethernet (Broadcom), Mac Bridge Miniport, HD Audio (MS), Realtek HD Audio. Then rebooted, and had 1 warning then ran Prime95 & WSE and got more.

    I uninstalled WinPcap/Wireshark and TightVNC and rebooted, still getting warnings.

    I have now rebooted to "safe mode with networking" but have no network plugging in, and am running Prime95 & WSE scan to see if I get any warnings. 15 minutes in so far and there has been no warnings.

     

    So it would appear safe mode is happy, normal mode is not happy.


    Thursday, May 5, 2011 4:32 AM
  • Since the issue not occur in Safe Mode, the problem should related with hardware drivers or third party tools.

     

    Please update the hardware drivers, also please check if the hardware  are compatible with Windows 7. You can check it on Windows 7 Compatibility Center. Update the BIOS to the latest version as well.

     

    Furthermore, remove some third party tools, or boot with Clean Boot for test. Maybe some services are corrupted at boot up.

     

    Regards,

    Leo   Huang

     

     


    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.
    Thursday, May 5, 2011 8:31 AM
    Moderator
  • I left it in Safe Mode over night, and after 9 hours in safe mode there were no warnings, but when I rebooted into normal mode, I got 200 warnings in the first two seconds, so I am thinking that the issue was happening, but safe mode may not be able to detect/report CPU errors, thus the CPU stored them for later reporting. This is based on the fact that the CPU temperature tool would not work in safe mode, so it would seem possible that the WHEA-Logger may also not be able to query the CPU for issues, and that I have never seen more than 2 warnings per-second.

    I have the first 70 warnings saved if these are of any help to anyone.

    I have the latest drivers from Dell, and the single extra device I have is on the compatibility list (that the capture card that the issue keep occurring while the device driver was turned off, and the device was removed) and that has it latest driver. I downloaded the latest AMD driver pack, and the issue occured before and after installing that.

    I just tried the clean boot options, and with all non-MS services turned off, the issue still occurs.


    Thursday, May 5, 2011 1:09 PM
  • First off, thank you for providing so much help,
    Please update the hardware drivers,

    I have done this already.

    also please check if the hardware  are compatible with Windows 7. You can check it on Windows 7 Compatibility Center.
    The one only extra pice of hardware above the Dell shipped system, is on the list as compatible.
    Update the BIOS to the latest version as well.
    I am already running Dell's latest BIOS for this system.

    Furthermore, remove some third party tools, or boot with Clean Boot for test. Maybe some services are corrupted at boot up.

     

    I have done this, as noted above, and the issue persists.

    Anymore idea's on how to test, or how would you tackle the issue is you though it was a hardware issue?

    Friday, May 6, 2011 3:02 PM
  • Hi,

     

    We cannot handle with hardware problem much more, some generally troubleshooting is using device clean boot:

    Device Clean Boot

    =================

    1. Click Start, type "devmgmt.msc" (without quotation marks) in the Search bar and press Enter.

     

    2. Expand "Sound, video and game controllers".

     

    3. Right click on your sound card and then click "Properties.

     

    4. In the dropdown menu of Device Usage, please choose "Do not use this device (disable)" and click OK.

     

    5. Please use the same method to disable other dubious hardware such as: internal modem, network card and CD-R drive. Please note some devices such as video adapter are not available to be disabled.

     

    In addition, we suggest contact hardware manufacturer for further help.

     

    Thank you for your understanding.

     

    Regards,

    Leo   Huang

     

     


    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.
    Monday, May 9, 2011 1:20 AM
    Moderator
  • Thank you for your suggestion, I have actually done the above steps of turning off all non-core devices, as reported 5th May 4:32am. Thus why I don't think it's a driver issue. I turned them all off.

    What I am trying to understand is how to prove to Dell hardware support that it's an hardware issue, thus I'm very keen to know if the WHEA-Logger is known to work under Safe Mode.

    Monday, May 9, 2011 2:13 PM