Windows 10: Constantly BSOD _MEMORY MANAGEMENT and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

Discus and support Constantly BSOD _MEMORY MANAGEMENT and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M in Windows 10 Drivers and Hardware to solve the problem; I constantly have BSOD on my hp laptop and its getting worse 1 BSOD every day. I did not make any changes in the hardware and the problem persists.... Discussion in 'Windows 10 Drivers and Hardware' started by VasilisPatelis, Mar 18, 2021.

  1. Constantly BSOD _MEMORY MANAGEMENT and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M


    I constantly have BSOD on my hp laptop and its getting worse 1 BSOD every day. I did not make any changes in the hardware and the problem persists. Here is the analysis from whoCrashed:


    System Information local



    [COLOR=rgba17, 17, 17, 1]Computer name: LAPTOP-OK443G7O
    Windows version: Windows 10, 10.0, version 2004, build: 19041
    Windows dir: C:\WINDOWS
    Hardware: HP Pavilion Laptop 15-cs2xxx, HP, 84C1
    CPU: GenuineIntel IntelR CoreTM i7-8565U CPU @ 1.80GHz 8664, level: 6
    8 logical processors, active mask: 255
    RAM: 17061695488 bytes 15,9GB[/COLOR]



    Crash Dump Analysis



    [COLOR=rgba17, 17, 17, 1]Crash dumps are enabled on your computer. [/COLOR]

    [COLOR=rgba17, 17, 17, 1]Crash dump directories: [/COLOR]
    [COLOR=rgba17, 17, 17, 1]C:\WINDOWS[/COLOR]
    [COLOR=rgba17, 17, 17, 1]C:\WINDOWS\Minidump[/COLOR]

    [COLOR=rgba17, 17, 17, 1]On Thu 18/03/2021 13:27:46 your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\031821-11250-01.dmp
    This was probably caused by the following module: [COLOR=rgba17, 17, 17, 1]hardware.sys[/COLOR] hardware
    Bugcheck code: 0x1A 0x41792, 0xFFFFF580E7A54930, 0x10000, 0x0
    Error: [COLOR=rgba17, 17, 17, 1]MEMORY_MANAGEMENT[/COLOR]
    Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
    This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating thermal issue or because of a buggy driver. This problem might also be caused because of overheating thermal issue.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
    Google query: [COLOR=rgba17, 17, 17, 1]hardware.sys MEMORY_MANAGEMENT[/COLOR]


    [/COLOR]

    [COLOR=rgba17, 17, 17, 1]On Wed 17/03/2021 09:52:59 your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\031721-13625-01.dmp
    This was probably caused by the following module: [COLOR=rgba17, 17, 17, 1]ntoskrnl.exe[/COLOR] nt+0x3F5C50
    Bugcheck code: 0x1000007E 0xFFFFFFFFC0000005, 0xFFFFF8051CA60057, 0xFFFFB802C26E7118, 0xFFFFB802C26E6950
    Error: [COLOR=rgba17, 17, 17, 1]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/COLOR]
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: [COLOR=rgba17, 17, 17, 1]Microsoft® Windows® Operating System[/COLOR]
    company: [COLOR=rgba17, 17, 17, 1]Microsoft Corporation[/COLOR]
    description: NT Kernel & System
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    [/COLOR]


    Conclusion



    [COLOR=rgba17, 17, 17, 1]2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

    [COLOR=rgba17, 17, 17, 1]hardware.sys [/COLOR]

    If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems[/COLOR]


    Here are the links for the .dpm files:

    https://1drv.ms/u/s!AhZJT-rs6nAwrUPrM3OFq6e-tpzL?e=yJw7PR


    https://1drv.ms/u/s!AhZJT-rs6nAwrUKyR4SGv6G7JGc4?e=EsB4Wm



    Thank you for your help.

    :)
     
    VasilisPatelis, Mar 18, 2021
    #1
  2. epso-sage Win User

    BSOD Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

    I have been having several BSOD recently and have reinstalled windows a few times but have been getting the Error:
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

    I have a crash report of:

    On Mon 8/7/2017 4:31:47 PM your computer crashed

    crash dump file: C:\Windows\Minidump\080717-7781-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0xCB5D8)

    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800A9B5B5D8, 0xFFFFBC8125F8AA28, 0xFFFFBC8125F8A270)

    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

    file path: C:\Windows\system32\ntoskrnl.exe

    product: Microsoft® Windows® Operating System

    company: Microsoft Corporation

    description: NT Kernel & System

    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.

    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Mon 8/7/2017 4:31:47 PM your computer crashed

    crash dump file: C:\Windows\memory.dmp

    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)

    Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800A9B5B5D8, 0xFFFFBC8125F8AA28, 0xFFFFBC8125F8A270)

    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

    Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.

    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Mon 8/7/2017 1:23:30 PM your computer crashed

    crash dump file: C:\Windows\Minidump\080717-7906-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0xCB5D8)

    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8018394B5D8, 0xFFFFA500C6488A28, 0xFFFFA500C6488270)

    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

    file path: C:\Windows\system32\ntoskrnl.exe

    product: Microsoft® Windows® Operating System

    company: Microsoft Corporation

    description: NT Kernel & System

    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.

    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Thu 8/3/2017 3:33:48 PM your computer crashed

    crash dump file: C:\Windows\Minidump\080317-9781-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0xCB5D8)

    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8012635B5D8, 0xFFFFCB0149BF5A28, 0xFFFFCB0149BF5270)

    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

    file path: C:\Windows\system32\ntoskrnl.exe

    product: Microsoft® Windows® Operating System

    company: Microsoft Corporation

    description: NT Kernel & System

    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.

    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    Can anyone help me figure this out?

    Thank you
     
    epso-sage, Mar 18, 2021
    #2
  3. IRQ memory BSODS, device manager, memory range?

    The only time I've seen that type of BSOD for myself is when I fried the PCI-e slots on my Striker 2 board... There wasn't anything that I could do, try and rma and go on.. I would suggest the steps that MilkyWay has said.. But, if you really don't know much about Bios's... I wouldn't play with Irq's... That can mess up everything on your board. USB, ethernet, ram, chip... But, that's just me on playing with irq's... To much of a hassle IMHO..
     
    Cold Storm, Mar 18, 2021
    #3
  4. alexsubri Win User

    Constantly BSOD _MEMORY MANAGEMENT and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

    BSOD- atikmpag.sys

    This is most likely due to an installation/upgrade error with ATI driver's. I suggest doing DriveSweeper and the following:
    • Drivesweeper all drivers & in Safe Mode
    • Unistall all drivers that aren't used in DriveSweeper (CCC Profiler Updates, MSI AfterBurner, anything related to ATI that use's it's drivers.)
    • After you do this, the first thing you need to do is go into Device Manager and Unistall your ATI Drivers
    Constantly BSOD _MEMORY MANAGEMENT and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M [​IMG]


    Once your done, restart the PC and then try installing the latest drivers.


    I had several issues with this in the past, but I overcame it with logical reasoning and whenever I have a driver issue, I just use these steps and I always overcome the problem.

    Best of luck! *Toast :toast:
     
    alexsubri, Mar 18, 2021
    #4
Thema:

Constantly BSOD _MEMORY MANAGEMENT and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

Loading...
  1. Constantly BSOD _MEMORY MANAGEMENT and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M - Similar Threads - Constantly BSOD _MEMORY

  2. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M BSOD

    in Windows 10 Gaming
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M BSOD: Here is my dump file. I could not pinpoint any cause of failure. Help is appreciated.https://drive.google.com/file/d/1XJUth_utSVbbfaSUb1XMf60ZEVjPM-f3/view?usp=sharing...
  3. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M BSOD

    in Windows 10 Software and Apps
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M BSOD: Here is my dump file. I could not pinpoint any cause of failure. Help is appreciated.https://drive.google.com/file/d/1XJUth_utSVbbfaSUb1XMf60ZEVjPM-f3/view?usp=sharing...
  4. Constant SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 1000007e

    in Windows 10 BSOD Crashes and Debugging
    Constant SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 1000007e: My PC has been randomly black screening and causing a buzzing sound before restarting. I have fully uninstalled My Nvidia Drivers and reinstalled them, I have done the memory diagnostic test and I have tried lowering the speed of my card but still it crashes randomly. Here is...
  5. Constant SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 1000007e

    in Windows 10 Gaming
    Constant SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 1000007e: My PC has been randomly black screening and causing a buzzing sound before restarting. I have fully uninstalled My Nvidia Drivers and reinstalled them, I have done the memory diagnostic test and I have tried lowering the speed of my card but still it crashes randomly. Here is...
  6. Constant SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 1000007e

    in Windows 10 Software and Apps
    Constant SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 1000007e: My PC has been randomly black screening and causing a buzzing sound before restarting. I have fully uninstalled My Nvidia Drivers and reinstalled them, I have done the memory diagnostic test and I have tried lowering the speed of my card but still it crashes randomly. Here is...
  7. BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

    in Windows 10 Software and Apps
    BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M: There are only two things I recently changed.Shrink D: to expand C:. C: cannot expand. Expand D: to original size.Add extra 2 two sticks of 8GB ram, mismatch frequency but BIOS set DRAM speed to the lowest speed. 8Gb 3600Mhz+ 8Gb 3200Mhz. Is there any additional steps when...
  8. BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

    in Windows 10 Gaming
    BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M: There are only two things I recently changed.Shrink D: to expand C:. C: cannot expand. Expand D: to original size.Add extra 2 two sticks of 8GB ram, mismatch frequency but BIOS set DRAM speed to the lowest speed. 8Gb 3600Mhz+ 8Gb 3200Mhz. Is there any additional steps when...
  9. BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

    in Windows 10 BSOD Crashes and Debugging
    BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M: There are only two things I recently changed.Shrink D: to expand C:. C: cannot expand. Expand D: to original size.Add extra 2 two sticks of 8GB ram, mismatch frequency but BIOS set DRAM speed to the lowest speed. 8Gb 3600Mhz+ 8Gb 3200Mhz. Is there any additional steps when...
  10. BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 1000007e

    in Windows 10 BSOD Crashes and Debugging
    BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 1000007e: Microsoft R Windows Debugger Version 10.0.21306.1007 AMD64 Copyright c Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\041421-18953-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv*...