Please report all spam threads, posts and suspicious members. We receive spam notifications and will take immediate action!
Results 1 to 4 of 4

Thread: WHEA Event ID 19 CPU-corrected hw error




  1. #1
    Join Date
    Oct 2014
    Location
    Europe/Hungary
    Posts
    8

    Default WHEA Event ID 19 CPU-corrected hw error

    Dear Members,

    I found the error below in Event Viewer.
    Should I change something in UEFI? (memory profile, speedstep, filter PLL?)

    No BSODs, only 9 warnings after 8 days.
    When last time occured only downloaded a cd, maybe did sha1 calc, no gaming or other intensive task.

    MciStat 0x90000040000f0005

    Found something:
    Vol. 3B 16-3
    INTERPRETING MACHINE-CHECK ERROR CODES
    Table 16-4.
    Incremental Bus Error Codes of Machine Check for Processors
    Based on Intel Core Microarchitecture

    Bus queue request type error
    bits 19-24
    000001 for BQ_PREF_READ_TYPE error

    But what does this mean? google "BQ_PREF_READ_TYPE" -> nothing
    Is it important? Helps to determine the source of the problem?
    (reg pending @ communities.intel)

    source:
    http://www.intel.com/content/dam/www...t-2-manual.pdf

    CPU tested with: Intel Processor Diagnostic Tool -> all passed

    In Event Viewer:

    A corrected hardware error has occurred.
    Reported by component: Processor Core
    Error
    Source: Corrected Machine Check Error
    Type: internal parity error

    ErrorSource 1
    ApicId 4
    MCABank 0
    MciStat 0x90000040000f0005
    MciAddr 0x0
    MciMisc 0x0
    ErrorType 12
    TransactionType 256
    Participation 256
    RequestType 256
    MemorIO 256
    MemHierarchyLvl 256
    Timeout 256
    OperationType 256
    Channel 256

    UEFI settings here: (white lines: AUTO, Speedstep: enabled)
    http://www.kephost.com/images/2014/1...0141022668.jpg
    http://www.kephost.com/images/2014/1...0141022669.jpg
    http://www.kephost.com/images/2014/1...0141022670.jpg
    http://www.kephost.com/images/2014/1...0141022671.jpg
    http://www.kephost.com/images/2014/1...0141022672.jpg
    http://www.kephost.com/images/2014/1...0141022673.jpg
    http://www.kephost.com/images/2014/1...0141022674.jpg

    System:
    MB: Asrock Z87 Extreme4 / BIOS: P3.00 - latest
    CPU: Intel Core i5 4690 3.5GHz 1150 ( Non-K !)
    PSU: EVGA SuperNOVA G2 750W - Gold - 220-G2-0750-XR
    MEM: CRUCIAL 8GB Ballistix Sport DDR3 1600MHz CL9 - KIT - BLS2C4G3D1609ES2LX0C
    CASE: CoolerMaster NSE-600-KKN1
    VGA: in cpu
    HDD: 2 WD SATA
    + 1 DVD RW with IDE->SATA converter

    OP SYS: Win 7 SP1 x86 + WSUS updates up to 2014.10.14

    Regards
    Last edited by asrockuser483; 10-23-2014 at 05:27 AM.

  2. #2
    parsec's Avatar
    parsec is offline Senior Member
    Join Date
    Jun 2012
    Location
    Third stone from the sun
    Posts
    4,824

    Default Re: WHEA Event ID 19 CPU-corrected hw error

    Quote Originally Posted by asrockuser483 View Post
    Dear Members,

    I found the error below in Event Viewer.
    Should I change something in UEFI? (memory profile, speedstep, filter PLL?)

    No BSODs, only 9 warnings after 8 days.
    When last time occured only downloaded a cd, maybe did sha1 calc, no gaming or other intensive task.

    MciStat 0x90000040000f0005

    Found something:
    Vol. 3B 16-3
    INTERPRETING MACHINE-CHECK ERROR CODES
    Table 16-4.
    Incremental Bus Error Codes of Machine Check for Processors
    Based on Intel Core Microarchitecture

    Bus queue request type error
    bits 19-24
    000001 for BQ_PREF_READ_TYPE error

    But what does this mean? google "BQ_PREF_READ_TYPE" -> nothing
    Is it important? Helps to determine the source of the problem?
    (reg pending @ communities.intel)

    source:
    http://www.intel.com/content/dam/www...t-2-manual.pdf

    CPU tested with: Intel Processor Diagnostic Tool -> all passed

    In Event Viewer:

    A corrected hardware error has occurred.
    Reported by component: Processor Core
    Error
    Source: Corrected Machine Check Error
    Type: internal parity error

    ErrorSource 1
    ApicId 4
    MCABank 0
    MciStat 0x90000040000f0005
    MciAddr 0x0
    MciMisc 0x0
    ErrorType 12
    TransactionType 256
    Participation 256
    RequestType 256
    MemorIO 256
    MemHierarchyLvl 256
    Timeout 256
    OperationType 256
    Channel 256

    UEFI settings here: (white lines: AUTO, Speedstep: enabled)
    http://www.kephost.com/images/2014/1...0141022668.jpg
    http://www.kephost.com/images/2014/1...0141022669.jpg
    http://www.kephost.com/images/2014/1...0141022670.jpg
    http://www.kephost.com/images/2014/1...0141022671.jpg
    http://www.kephost.com/images/2014/1...0141022672.jpg
    http://www.kephost.com/images/2014/1...0141022673.jpg
    http://www.kephost.com/images/2014/1...0141022674.jpg

    System:
    MB: Asrock Z87 Extreme4 / BIOS: P3.00 - latest
    CPU: Intel Core i5 4690 3.5GHz 1150 ( Non-K !)
    PSU: EVGA SuperNOVA G2 750W - Gold - 220-G2-0750-XR
    MEM: CRUCIAL 8GB Ballistix Sport DDR3 1600MHz CL9 - KIT - BLS2C4G3D1609ES2LX0C
    CASE: CoolerMaster NSE-600-KKN1
    VGA: in cpu
    HDD: 2 WD SATA
    + 1 DVD RW with IDE->SATA converter

    OP SYS: Win 7 SP1 x86 + WSUS updates up to 2014.10.14

    Regards
    You said no BSOD. Then you are calling this an error, but it is a warning in the Windows Event Log?

    You included this:

    A corrected hardware error has occurred.
    Reported by component: Processor Core
    Error
    Source: Corrected Machine Check Error
    Type: internal parity error

    I'm not completely sure about what happened, but a parity error means the method used to check that data is valid failed. That could refer to one byte of data or more.

    It also seems to have been corrected, "A corrected hardware error has occurred". That is poor English grammar, it seems to mean, an error occurred, but was corrected.

    Not all Machine Check errors are really hardware errors. You are afraid your processor itself is causing the error, but this could just be a data error.

    If this "error" was truly a CPU problem, I doubt Windows would call that a Warning.

    More information on Machine Check errors:

    Machine-check exception - Wikipedia, the free encyclopedia


    Bug Check 0x9C: MACHINE_CHECK_EXCEPTION (Windows Debuggers)

  3. #3
    Join Date
    Oct 2014
    Location
    Europe/Hungary
    Posts
    8

    Default Re: WHEA Event ID 19 CPU-corrected hw error

    Dear parsec,

    This is the exact word usage in Win:
    (not my img)
    http://cdn.overclock.net/c/c3/c301c1...arityError.PNG

    Not all Machine Check errors are really hardware errors.
    I know:

    "I have now tried different motherboards, CPUs, memory, and power supplies and
    this error is still showing up now and then.
    This points strongly to either FreeBSD bogus reporting, or these errors being
    benign. It's hard to believe that the exact same error might occur with
    completely different hardware ... unless it's being caused by the case. "
    freebsd-stable - Need Help With MCA Code

    :D

    Others says:
    " it still is causing trouble and indicates instability"
    Asus mobos - Ivy Bridge and WHEA-logger (Event 19) issues

    "a processor's machine check exception typically reports processor errors, cache and memory errors, and system bus errors."
    Hardware Errors and Error Sources (Windows Drivers)

    My question still stands: are those settings good for this cpu?

    Sadly mysterious bug :x

    Regards

  4. #4
    Join Date
    Oct 2014
    Location
    Europe/Hungary
    Posts
    8

    Default Re: WHEA Event ID 19 CPU-corrected hw error

    Hello,

    I found the solution/explanation, read my last comment here:
    https://communities.intel.com/thread/56283

    Regards

Thread Information

Users Browsing this Thread

There are currently 2 users browsing this thread. (0 members and 2 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •