Windows 7 BSOD crashes! Help! RRS feed

  • Question

  • I have been experiencing multiple BSOD in the last couple weeks. I don't know what the issue is so I'm posting my dump file. If someone could help me figure out what the problem is that would be great!


    • Edited by mlaykj99 Monday, July 28, 2014 5:32 AM
    Monday, July 28, 2014 4:37 AM

All replies

  • Hi,

    In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.

    If you don't know where .DMP files are located, here's how to get to them:

    1. Navigate to the %systemroot%\Minidump folder.

    2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.

    3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.

    4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.

    If you are going to use Onedrive but don't know how to upload to it, please visit the following:

    Upload photos and files to Onedrive.

    After doing that, to learn how to share the link to the file if you are unaware, please visit the following link - Share files and folders and change permissions and view 'Get a link'.

    Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, you will need to allow the system to crash once again to generate a crash dump.

    If your computer is not generating .DMP files, please do the following:

    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

    4. Double check that the WERS is ENABLED:

    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

    If you cannot get into normal mode to do any of this, please do this via Safe Mode.



    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Monday, July 28, 2014 5:02 AM
  • Hi,

    The stop error 0x124 indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

    Please update your motherboard driver from manufacturer's website to see what's going on.

    Debugging Details:
    BUGCHECK_STR:  0x124_GenuineIntel
    PROCESS_NAME:  thermald.exe
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    fffff880`02feeb58 fffff800`03405a3b : 00000000`00000124 00000000`00000000 fffffa80`0d543028 00000000`bf800000 : nt!KeBugCheckEx
    fffff880`02feeb60 fffff800`02f9a463 : 00000000`00000001 fffffa80`0cfaf8a0 00000000`00000000 fffffa80`0cfaf8f0 : hal!HalBugCheckSystem+0x1e3
    fffff880`02feeba0 fffff800`03405700 : 00000000`00000728 fffffa80`0cfaf8a0 fffff880`02feef30 fffff880`02feef00 : nt!WheaReportHwError+0x263
    fffff880`02feec00 fffff800`03405052 : fffffa80`0cfaf8a0 fffff880`02feef30 fffffa80`0cfaf8a0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`02feed50 fffff800`03404f0d : 00000000`00000008 00000000`00000001 fffff880`02feefb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`02feed90 fffff800`033f8e88 : 00000000`00000000 00000000`00000010 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff880`02feedc0 fffff800`02e824ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff880`02feedf0 fffff800`02e82313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`02feef30 fffff800`02e7a7b8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`06c12638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!memcpy+0x208
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: GenuineIntel
    IMAGE_NAME:  GenuineIntel
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_mae
    FAILURE_ID_HASH:  {addebe90-d04a-b9c9-a39c-2531fe75dd4e}
    Followup: MachineOwner

    Kate Li
    TechNet Community Support

    Tuesday, July 29, 2014 7:50 AM
  • I updated all my motherboard drivers directly from the site and it hasn't helped.

    Thursday, July 31, 2014 10:54 PM
  • Sorry, I missed the fact that you added a dump link to your OP.


    A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).

    If we run an !errrec on the 2nd parameter of the bug check (address of the WER structure) we get the following:

    BugCheck 124, {0, fffffa800d542028, bf800000, 200401}

    Section 2     : x86/x64 MCA
    Descriptor    @ fffffa800d542138
    Section       @ fffffa800d5422c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    Error         : Internal unclassified (Proc 4 Bank 1)
      Status      : 0xbf80000000200401
      Address     : 0x00000000fee00040
      Misc.       : 0x0000000000000086

    It's an internal unclassified error, which implies it's simply not a publicly documented micro-architectural error. We cannot say what's causing it for sure given this is the specific error.

    Here's what I'd do:

    1. AppleCharger.sys is listed and loaded which is the GIGABYTE On/Off Charge driver. See here for details - http://www.gigabyte.us/MicroSite/185/on-off-charge.htm

    Very troublesome software, so please uninstall ASAP!

    2. Uninstall Zemana AntiLogger and Norton ASAP as they're likely causing conflicts

    Norton removal - https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;jsessionid=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&pvid=f-home

    MSE -  http://windows.microsoft.com/en-us/windows/security-essentials-download

    3. Uninstall any/all Gigabyte bloatware such as Easy Tune, East Saver, etc. Horrible software with extremely old drivers. OS > BIOS utilities like that are known to cause 0x124's.

    4. Navigate to services.msc and disable the nVidia Streaming service, and then restart the computer.


    If the above fails, there is only so much you can do with a bug check like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

    1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - http://www.piriform.com/speccy

    2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

    3. Ensure your BIOS is up to date.

    4. If all of the above fail, the only left to do is replace your processor as it is faulty.



    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Thursday, July 31, 2014 11:27 PM
  • I have done steps 1-3 minus uninstalling Norton so far.

    I'm going to see how that works.


    Friday, August 1, 2014 2:54 AM
  • My pleasure, please keep me updated.



    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Friday, August 1, 2014 3:37 AM