BSOD Kernal Mode Heap Corruption

  1.    1 Week Ago #1

    BSOD Kernal Mode Heap Corruption


    I was playing a game called second life and then tried running dead by daylight on steam then got a blue screen called BSOD kernal mode heap corruption i would like to know exactly what caused this crash as i don't want to have repeat crashing, ive always been able to run a lot of games at the same time.

    System Specs - Ryzen 7 2700, Gigabyte rtx 2070, 16gb ram at 2400, 240 SSD boot drive, 2 TB storage drive

    the DM file is attached aswell as a minidump to when the crash happened
    BSOD Kernal Mode Heap Corruption Attached Files
      My ComputerSystem Spec


  2. Posts : 22,677
    windows 10 professional version 1607 build 14393.969 64 bit
       1 Week Ago #2

    Hi thyztmusic,

    1) There are two log collectors: DM and BETA.
    At some time the BETA log collector will replace the DM log collector.
    The BETA log collector will collect more useful files and folders.

    Please run the BETA log collector and post a zip into this thread.

    2) Update the specs in the "My Computer" section:

    System Specs - Fill in at Ten Forums | Tutorials
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums

    Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)

    3) Open file explorer > this PC > C: > in the right upper corner search for: C:\windows\memory.dmp > if the file size is < 1.5 GB then zip and post a share link into the thread using one drive, drop box, or google drive
      My ComputerSystem Spec

  3.    1 Week Ago #3

    I've attached the BETA log collector aswell as the memory.dmp updated specs on my profile too

    heres the google drive to the memory.dmp

    MEMORY.DMP - Google Drive
    BSOD Kernal Mode Heap Corruption Attached Files
      My ComputerSystem Spec


  4. Posts : 22,677
    windows 10 professional version 1607 build 14393.969 64 bit
       1 Week Ago #4

    1) In the DM log collector there was only one mini dump file.
    2) In the BETA log collector there were no mini dump files.

    3) Wondering what happened to the mini dump file?
    Was the mini dump file removed from its typical location?
    Was it deleted?

    It may take a while for the memory dump to download.

    4) Windows driver verifier is a tool that will stress drivers and when there is a BSOD the dump files can be debugged.

    After each BSOD you will need to turn off or recover from using the tool and commands are ran after opening the Window recovery menu.

    5) Read this link to learn the methods to turn off and recover from using the tool.
    Enable and Disable Driver Verifier in Windows 10 | Tutorials

    6) Do not use the tool until it is communicated in the thread.

    7) Make a backup image using Macrium:
    Macrium Software | Your Image is Everything

    8) And make a brand new restore point.

    9) Open administrative command prompt and type or copy and paste:
    10) sfc /scannow
    11) dism /online /cleanup-image /restorehealth
    12) chkdsk /scan
    13) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    14) Make sure that there is no over clocking while troubleshooting.

    15) Sometimes there are problems in the bios that produce bsod.
    The BIOS: Version/Date American Megatrends Inc. F22, 3/15/2018

    16) Please check to see if this is the most up to date version.

    17) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.

    18) To ensure that there are no improper bios settings please reset the bios.

    19) Sometimes there can be failure to boot after resetting the bios.

    20) Make sure the Macrium backup image is saved to another drive or to the cloud

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    https://www.howtogeek.com/131623/how...bios-settings/
    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow



    Code:
    1/7/2019 8:43 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 13a
    P2: 12
    P3: 380
    P4: ffffd38eff2ad000
    P5: 0
    P6: 10_0_17763
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010719-11484-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-40984-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA4B.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA4C.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA4D.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA6D.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_13a_6594d8d1a269bf85ee6394e1a18dc627913161d_00000000_cab_0368ba66
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 3137baeb-41a2-4419-ad3d-08045b984183
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    Code:
    1/7/2019 8:44 PM	Windows Error Reporting	Fault bucket 0x13a_12_nt!ExFreePoolWithTag, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 89b315da-7e24-4661-8780-35b87c2deba2
    
    Problem signature:
    P1: 13a
    P2: 12
    P3: 380
    P4: ffffd38eff2ad000
    P5: 0
    P6: 10_0_17763
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010719-11484-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-40984-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA4B.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA4C.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA4D.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA6D.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_13a_6594d8d1a269bf85ee6394e1a18dc627913161d_00000000_cab_1159a207
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 3137baeb-41a2-4419-ad3d-08045b984183
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
      My ComputerSystem Spec

  5.    1 Week Ago #5

    The Minidump from the crash file is inside the 1st zip file i uploaded, i moved it there
      My ComputerSystem Spec


  6. Posts : 22,677
    windows 10 professional version 1607 build 14393.969 64 bit
       1 Week Ago #6

    1) There was one misbehaving hardware driver identified in the memory dump.

    2) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)

    3) re-install the Nvidia GPU driver from the Nvidia website

    4) make sure that you check the clean install box and if available install the physx driver.

    Display Driver Uninstaller Download version 18.0.0.4 (or newer version if available)
    Display Driver Uninstaller: How to use - Windows 7 Help Forums
    NVIDIA
    Download Display Driver Uninstaller - MajorGeeks

    4) Please continue with all of the steps in the prior post.

    5) If there are any BSOD:
    a) run the BETA log collector and post a new zip into the thread
    b) open file explorer > this PC > C: > if the file size is < 1.5 GB then zip and post a separate share link into the thread using one drive, drop box, or google drive
      My ComputerSystem Spec

  7. philc43's Avatar
    Posts : 3,824
    64bit Win 10 Pro ver 1809 Build 17763.253 and W10 Insider Build 18312
       1 Week Ago #7

    @thyztmusic you asked what specifically caused the crash.

    Bugcheck 13a was caused by your system detecting corruption in the heap. The BSOD crash then happens to prevent any further damage to your system from trying to implement corrupt code. The Heap is a section of the memory used for dynamic memory allocation.

    The question then becomes why did it occur? It could be bad RAM or a bad disk if virtual memory was being used. With only one crash dump file and to be honest it doesn't show very much, we are just guessing.

    Please post up new log files if you get any further crashes. It might have been a one-off and you may not need to worry but time will tell.

    Note: As you have seen the crash dump files do get deleted off your system if you leave it more that a day or two before running the log collector so don't wait too long before running it.
      My ComputersSystem Spec


 

Related Threads
Microsoft (R) Windows Debugger Version 10.0.17061.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File User Mini Dump File: Only registers, stack and portions of memory are available Symbol search path...
Unexpected Kernal Mode Trap on Boot-up in BSOD Crashes and Debugging
Hi I have a bit of a weird problem in that in about one out of every five reboots my PC fails to boot up first time and comes up with an UNEXPECTED KERNAL MODE TRAP (which I believe is designated code 7F). It then has another go and is generally...
BSOD - Unexpected Kernal Mode Trap + Others in BSOD Crashes and Debugging
Hello all, Have been having this BSOD just about two months now. I really only BSOD when I am gaming. I have noticed that I get multiple different error messages with the post title being the most recent, but all relate ntoskrnl.exe (thanks to...
Hi i keep getting this error i got this image from google i have the latest driver version(361.43) and i still get it just got it ~30 mins ago ...
Hi i keep getting this error https://www.tenforums.com/attachments/graphic-cards/38989d1443009740t-nvidia-driver-355-82-stopped-responding-has-recovered-capture.jpg i got this image from google i have the latest driver version(361.43) and i...

Tags for this Thread

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 20:41.
Find Us