7 Replies Latest reply on Feb 28, 2018 12:58 AM by wiebo67

    WHEA-Logger ID 19 and BSOD's


      Hi there,

      Last year I've assemble a game PC for my son. It was a present for his 18th birthday.


      These are the components I used inside of a NZXT S340 Special Edition Razer Case:

      Motherboard: ASUS Maximus VIII Ranger

      Processor: Intel Core i7-6700K Unlocked 4GHz, 8MB Cash LGA1151

      Power supply: Corsair RM650x

      Memory: Ballistix BLS8G4D240FE 8GB (2 modules 16GB in total)

      Graphics Card: MSI Nvidia Geforce GTX 1070

      SSD: Samsung EVO 850 500GB

      HDD: Seagate 2TB SATA disk

      OS: Windows 10 Pro


      The installation went well and the system worked smoothly for several months.

      Beginning of this year, the problems started.

      First the browsers (Internet explorer, Edge, Chrome, Firefox) began to fail (stuck or even closed).


      I also get in the Event Viewer frequently WHEA-Logger ID19 warnings:

      A corrected hardware error has occurred.

      Reported by component: Processor Core

      Error Source: Corrected Machine Check

      Error Type: Internal parity error

      Processor APIC ID: 2


      I started to update, BIOS and all recently drivers from the ASUS website, also updated the graphics MSI Nvidia GTX1070 driver.

      Did the same with the Intel processor (Chipset, Graphics driver, etc.) using Intel(R) & Support Assistant Tray.

      Still the same problems. Browser crashes and BSOD.


      The Intel Processor Diagnostic Tool didn’t show any problems

      Also the ASUS PC Diagnostics and the Samsung Magicain software didn’t find any problem.


      Then I began to remove installed components: such as the video card, one of Memory modules (switch them one by one), replaced the SSD with another one. Without success.


      Reinstalled the system with a minimum of additional components.

      The BSOD’s came even during a new Windows 10 installation (several times).


      I’ve even replaced the MoBo by another one (exact the same board).

      This was also not succesfull.


      Is there anyone who can help me with this.

      I’m starting to fear, there is something wrong with the processor.

      I only don’t know how to find out what it is.


      Any suggestions would be helpful.

        • 1. Re: WHEA-Logger ID 19 and BSOD's
          Intel Corporation
          This message was posted on behalf of Intel Corporation

          Hello, wiebo67.

          Thank you very much for taking the time to reach the Intel® Communities Team.

          I understand you are facing some issues with your system since you are getting BSOD's while the normal use of your computer. I will be more than glad to assist you with this problem you are facing.

          I would like to know if you have used this new Motherboard with another known working processor and the same components? In addition, was this processor overclocked? if so, please try using it with the default settings.

          Antony S.

          • 2. Re: WHEA-Logger ID 19 and BSOD's

            Hi Antony,


            Thanks for your replay.


            First of all I can work with the system sometimes for several minutes/hours without a BSOD.

            The browser Edge doesn't give problems (more or less stable) if I don't get a BSOD of course. Chrome and Inter Explorer are not workable.

            I get constantly WHEA-logger warnings. Sometimes every minute.


            I did not replace the current processor with a working other one, because I don't have a replacement or spare (too expensive).

            We did not use overclocking. Always default motherboard settings (=no overclocking).


            I've you need additional information, please let me know.


            Kind regards,


            Guido Meel.

            • 3. Re: WHEA-Logger ID 19 and BSOD's
              Intel Corporation
              This message was posted on behalf of Intel Corporation

              Hello, wiebo67.

              Thank you very much for your reply and the information provided.

              If you do not mind, can you attach a screenshot of the error you are getting? That will be very helpful for me to perform a deeper research regarding this issue.

              Antony S.

              • 4. Re: WHEA-Logger ID 19 and BSOD's

                Hi Antony.


                I first want to give you an update on what I've recently done for testing.


                I replaced my memory whit a total other type and brand of memory (I'm sure this memory worked in other devices).

                I also replaced my SSD into another working type.


                I start-over a clean install.


                It get stuck during the Windows 10 installation and I had to start the installation again (two times).


                After that I succeed with the installation, but it doesn't mean the system run's well.

                Browsers are still crashing and the BSOD's are also still there. Before, during and after I update all the drivers.


                I send you some screenshots of BlueScreenView's, Windows EventViewer and Internet Explorer and Chorme crashes.

                As I said before, Edge is not crashing but sometimes it get stuck. Youtube viewing has stops while the time-bar is still running.

                All tests with the browser are mostly done playing a YouTube file, because that's the fastest way to crash the browser.


                I hope this information helps.


                Kind regards,

                Guido Meel.

                2018-02-27 23_11_52-Internet Explorer.jpg2018-02-27BlueScreenView  -  C__Windows_Minidump.jpg2018-02-27 22_48_00-Event Viewer.jpg2018-02-27 23_09_21-Event Viewer.jpg2018-02-27 23_02_14-MONSTER HUNTER WORLD (Honest Game Trailers) - YouTube_Chrome.jpg

                • 5. Re: WHEA-Logger ID 19 and BSOD's
                  Intel Corporation
                  This message was posted on behalf of Intel Corporation

                  Hello, weibo67.

                  Thank you very much for your prompt reply.

                  I sent you a private message, please verify your inbox.

                  Antony S.

                  • 6. Re: WHEA-Logger ID 19 and BSOD's

                    Hi Antony,


                    Your private e-mail address is not shown.

                    I can't send messages to "webadmin".

                    The private message you've send me is also via "webadmin".

                    Can you give it another try?


                    Thanks in advanced.

                    Kind regards,

                    Guido Meel.

                    • 7. Re: WHEA-Logger ID 19 and BSOD's

                      Sorry Antony,


                      I thought I had to replay on a e-mail you've send me too.

                      Meanwhile I've found the private message and send you an answer.


                      Kind regards,

                      Guido Meel.