BSOD while loading Dota 2: Machine Check Exception


  1. Posts : 2
    Windos 10 Home
       #1

    BSOD while loading Dota 2: Machine Check Exception


    Hey Guys,

    As the title says, I keep running into a BSOD when trying to launch/ play Dota2. The computer freezes up and the audio keeps making a repeating noise. I have reset my laptop last night (deleted all the other files) and only downloaded the latest Nvidia driver and steam+ dota2. I spoke with a Microsoft agent, and they used remote access to check things out, and informed me that it is my memory. I ran the memory diagnostic tool, and it showed up issues. I also went out and bought new memory, and it is still doing the same thing.

    Thanks in advance!

    Attachment 146877
      My Computer


  2. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #2

    There are no mini-dumps in the zip file so not a lot we can do to help debug your problem.

    One possibility is that the memory itself is not defective but rather one or more of the memory slots on the system board is.

    You can try running memtest86+ for 8 passes and see what it shows. This will take 12 to 18 hours to complete.

    ===================================================
    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses


    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.


    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note   Note
    MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.


    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

    Take a picture when done and post in the forum please.

    Also, please make sure your PC is configured for small dump files:

    How to Configure Windows 10 to Create Dump Files on BSOD
      My Computers


  3. Posts : 2
    Windos 10 Home
    Thread Starter
       #3

    Hey thanks. I will run mem86 for 8 passes.

    Attached is another post. Hopefully that has some more information.


    Attachment 146892

    For some reason, I cannot seem to boot with the mem86+ on USB.
    Attachment 146895

    I've attached another file if that helps at all.
    Last edited by marcbreyt; 02 Aug 2017 at 22:12. Reason: Adding another crash file.
      My Computer


  4. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #4

    One dump in the latest zip file.
    Code:
    BugCheck 9C, {0, ffffd201a1a93920, 0, 0}
    Probably caused by : intelppm.sys ( intelppm!MWaitIdle+18 )
    intelppm.sys is the Intel Processor driver.

    Code:
    MACHINE_CHECK_EXCEPTION (9c)
    A fatal Machine Check Exception has occurred.
    KeBugCheckEx parameters;
        x86 Processors
            If the processor has ONLY MCE feature available (For example Intel
            Pentium), the parameters are:
            1 - Low  32 bits of P5_MC_TYPE MSR
            2 - Address of MCA_EXCEPTION structure
            3 - High 32 bits of P5_MC_ADDR MSR
            4 - Low  32 bits of P5_MC_ADDR MSR
            If the processor also has MCA feature available (For example Intel
            Pentium Pro), the parameters are:
            1 - Bank number
            2 - Address of MCA_EXCEPTION structure
            3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
            4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
        IA64 Processors
            1 - Bugcheck Type
                1 - MCA_ASSERT
                2 - MCA_GET_STATEINFO
                    SAL returned an error for SAL_GET_STATEINFO while processing MCA.
                3 - MCA_CLEAR_STATEINFO
                    SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
                4 - MCA_FATAL
                    FW reported a fatal MCA.
                5 - MCA_NONFATAL
                    SAL reported a recoverable MCA and we don't support currently
                    support recovery or SAL generated an MCA and then couldn't
                    produce an error record.
                0xB - INIT_ASSERT
                0xC - INIT_GET_STATEINFO
                      SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
                0xD - INIT_CLEAR_STATEINFO
                      SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
                0xE - INIT_FATAL
                      Not used.
            2 - Address of log
            3 - Size of log
            4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
        AMD64 Processors
            1 - Bank number
            2 - Address of MCA_EXCEPTION structure
            3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
            4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    Arguments:
    Arg1: 0000000000000000
    Arg2: ffffd201a1a93920
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    I don't know how to proceed any further in determining what this debug info means. It sounds like a problem with the Intel I7 CPU but it could be caused by a device driver as well or even defective memory, so lets wait and see if you can get memtest86+ to run. If not I would suggest removing half the ram and running that way for awhile and see what happens. If the problem reoccurs then swap the removed and installed ram and test again. If the problem does not occur in either case then one or more of the removed memory DIMMs is defective.

    You can also try running Driver Verifier and see if that shows us anything but let's wait until the ram testing is done first.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:01.
Find Us




Windows 10 Forums