I have faulty 8700K or ram or ?WHOA LOGGER entries

Discussion in 'Desktop Hardware' started by sew333, Jan 31, 2018.

  1. sew333

    sew333 Notebook Guru

    Reputations:
    0
    Messages:
    69
    Likes Received:
    3
    Trophy Points:
    16
    Hi. Today i checked my event viewer and found some weird errors in 21.01.2018 :

    System Warning 21/01/2018 A corrected hardware error has occurred.

    Reported by component: Processor Core Error Source: 1 Error Type: 9 Processor ID: 0

    Here are screen:

    [​IMG]

    Its only in 21.01.2018 day.After 21.01.2018 till today no that entries. I remember that system was idle in night this time.

    Ok my pc: 8700K stock, MTU on, 4700mhz auto Asus Z370 Pro Gaming

    16GB DDR 3000MHZ ( XMP )

    Corsair 750i

    SSD Crucial 525GB

    HDD TOSHIBA 500GB

    Windows 10 clean install 1709 Creator Fall Update

    Temps of cpu fine,temps of gpu fine. Never had any single BSOD. Memtest86 no errors. All benchmarks passing, no crashing in games

    . Only saw that error in event viewer which make think that is still with cpu or what?
     
  2. KY_BULLET

    KY_BULLET Notebook Evangelist

    Reputations:
    460
    Messages:
    579
    Likes Received:
    623
    Trophy Points:
    106
  3. sew333

    sew333 Notebook Guru

    Reputations:
    0
    Messages:
    69
    Likes Received:
    3
    Trophy Points:
    16
    But in my situation it was reporting about cpu hardware corrected error,not pcie.

    Going through event viewer i saw error:
    WHEA Event ID 19 CPU-corrected hw error
    on day 21.01. I remember that i finished installing system on this day and left pc in idle overnight. Today i was checking event viewer and met that error.
    Is this symptom of fault of my hardware?
    But like i said i dont have any crashing in games,benchmarks,no freezing,no bsods.
    So thats weird.
     
  4. KY_BULLET

    KY_BULLET Notebook Evangelist

    Reputations:
    460
    Messages:
    579
    Likes Received:
    623
    Trophy Points:
    106
    From the link it says you need to navigate to your device manager, and see if there are any drivers that didn't install correctly. There should be some kind of error message like "Driver didn't install correctly or driver missing".

    Windows may have tried to install "chipset driver" and messed it up? I wouldn't be surprised if this is your problem.

    Hope this helps.
     
    Vasudev likes this.
  5. sew333

    sew333 Notebook Guru

    Reputations:
    0
    Messages:
    69
    Likes Received:
    3
    Trophy Points:
    16
    Hi. Last question.

    Somebody said this to me:"WHEA errors are only produced when a hardware error occurs."

    So its only hardware fault ?


    On Win10 builds 16299.192 and 16299.214 no WHEA-Logger 19 warnings.


    Only on 16299.15 build i had this.
     
    Vasudev likes this.
  6. KY_BULLET

    KY_BULLET Notebook Evangelist

    Reputations:
    460
    Messages:
    579
    Likes Received:
    623
    Trophy Points:
    106
    I've never

    You probably need to back up and do a clean installation (Again) and when it asks you to connect to the internet, skip that part. This will keep Windows from trying to install drivers (Common Problem). After you get up and running, install the drivers manually by going to your Desktop Manufacturers website (MSI, ASUS, ete etc..).

    I know how you feel, I had some aggravating issues with Stopcode errors at every single restart. It took me forever to figure out what was causing them. Ended up being SGX (Intel Software Guard Extensions) causing BSOD with Stopcode error "Bad_System_Configuration". I did a clean install, skipped the part where windows asks you to connect to the internet, after installation finished, I left SGX out, been good ever since.

    You will find it, I hope this helps you to do so. Might have to do some digging on Google but there is a fix for it out there.

    Charlie
     
  7. BeastsForever.TheDragon

    BeastsForever.TheDragon Notebook Evangelist

    Reputations:
    172
    Messages:
    562
    Likes Received:
    381
    Trophy Points:
    76
    Maybe, one of your cores in die is going rogue!(although this is the least probable)

    Or, maybe cpu isn't fitted well in the socket, OR some pins of socket are bent! Making some cores less respinsive to board!
     
  8. sew333

    sew333 Notebook Guru

    Reputations:
    0
    Messages:
    69
    Likes Received:
    3
    Trophy Points:
    16
    If some pins of socket are bent why i dont had this errors after 21.01 till today 05.03.2018 ?
    I tested in many benchmarks pc in this days.
     
Loading...

Share This Page