Компьютер был перезагружен после критической ошибки код ошибки 0x0000013a

Kernel Mode heap corruption is a BSOD-type error with bug check value 0x0000013A. This blue screen error usually occurs due to corrupted device drivers, obsolete graphics cards, memory issues, or malfunctioning hardware. A few users recently encounter this bug after performing an in-place upgrade on their devices.

Well, in this guide, we present detailed information on how the Stop Error 0x13A occurs in the first place. Besides, we also discussed eight solutions that help in getting rid of the KERNEL_MODE_HEAP_CORRUPTION bug. Let’s explore the workarounds in detail –

How to Fix BSOD Error 0x13A in Windows 10

To solve the KERNEL_MODE_HEAP_CORRUPTION Error 0x0000013A, try the following suggestions –

Boot Windows 10 into Safe Mode

Since you are getting the Blue Screen, you won’t be able to log into Windows normally. So, you need to first boot into Safe Mode and then perform the below workarounds. Only a handful of Windows 10 programs and services run on this mode preventing any kind of conflicts from third-party apps. 

Here are the essential steps to enter Safe Mode –

• Press the Power button for 5 seconds and wait till it shuts down successfully. 
• Repeat this process 2-3 times until the Preparing Automatic Repair screen comes into view.
• Let the system diagnoses this error for a few seconds thereafter click Advanced options.
• On the Windows Recovery Environment (WinRE), go to – Troubleshoot > Advanced options.
• Hit Startup Settings on the next screen followed by the Restart button.

When Windows reboots, press F5 to boot into Safe Mode with Networking.

Note: Selecting “Safe Mode with Networking” is essential to fix black or blue screen issues. If not, this won’t connect to the Internet causing problems in troubleshooting the actual problem.

Check Event Viewer

Knowing the reasons that might have led to the bug at hand provides an opportunity to solve the BSOD error correctly. Interestingly, the system contains a log of all bugs and errors that ever occur on Windows 10. One can access the Windows log at Event Viewer containing information like Source and Event ID. 

Now that you are already inside the Safe boot, use the below guideline to get the Windows log file –

• Use Win + S shortcut to start the Search UI.
• Type “event viewer” in the text field, and click the top result.
• Select Windows Logs > System from the left column.
• In the mid-section, scroll down and locate the log titled “Kernel Mode Heap corruption“.
• Once you find this file, double-click the same to read the description.

The log enlists the exact cause that might have caused this BSOD Error 0x13A. Usually, this error arises because of these three reasons – 

1. Corrupted Graphics Driver
2. Software/Hardware Error
3. Memory Issues

1] Check Graphics Drivers for issues

If you encounter the BSOD error 0x13A just after starting a heavy game, this problem might lie inside the graphics driver. A corrupted or obsolete graphics driver often causes the KERNEL_MODE_HEAP-CORRUPTION error on Windows 10. To fix this, you must try updating the existing graphics card driver. 

Note: In case the update process fails, you may use the rollback feature. If this method fails as well, uninstall the graphics driver, restart the device, then reinstall the graphics card back.

• Right-click on the Windows icon and select Device Manager.
• Click “>” next to the display adapters and right-click again on the available graphics card.
• Now, select the correct option depending on what are you trying to do with this. 

For Example: 

1. Update: Hit update driver option then choose “Search automatically for updated driver software“.
2. Roll Back: Click Properties, switch to the Driver tab, and hit Roll back driver.
3. Reinstall a New Driver: Click uninstall device then visit the manufacturer’s Site to download the latest version of the uninstalled graphics card. When the download completes, double-click the setup file to start the installation.

2] Run Driver Verifier Manager

Driver Verifier Manager is a great tool to discover the problematic drivers on Windows 10. So, if you are still getting the Kernel Mode Heap Corruption 0x0000013A error, you should run this tool to check the obsolete device drivers. Here’s how to perform this task –

• Launch Windows PowerShell (Admin).
• On the elevated console, type “verifier“, and hit Enter.

• Subsequently, mark the “Create Standard Settings” checkbox followed by Next.

• Now, mark “Automatically select all drivers installed on this computer” and hit Finish.

• The system prompts to “Restart PC” so as to start scanning for any corrupted or damaged drivers.
• After the reboot, Windows will display a list of drivers that are found to have some errors. 

You may now re-follow method #2 to update, rollback, or uninstall-reinstall the above-displayed device drivers.

3] Run Blue Screen Troubleshooter

This is another interesting tool designed to help users fix BSOD-type errors on Windows 10. Isn’t it great that one can address the blue screen issue possibly by running a simple troubleshooter? Indeed, this is an easy way to resolve different Stop Error codes on Windows 10 PC. Here’s how to use this tool –

• First of all, navigate to the below path –

Win + I > Update & Security > Troubleshoot

• Click to reveal the Blue Screen box and hit Run the troubleshooter.

4] Perform Disk Cleanup

The presence of unnecessarily stored cache, log files, Windows Prior Installation files, and other irrelevant data may also cause the 0x0000013A error. To solve this, perform a disk Cleanup on Windows 10.

5] Run CHKDSK Utility

If the BSOD error 0x0000013A still persists, this must be due to hardware-related issues. To check whether this indeed is the case or not, run the CHKDSK command line on the Windows Console. All you need is to follow these easy steps –

• Get access to the Command Prompt with administrative privileges.
• Near the blinking cursor, type the command – chkdsk C: /f /r /x
• Hit the Enter key on your keyboard to initiate a disk check.
• This probably won’t run and prompts doing this when the system reboots. 
• Type “Y” and press Enter again. 

• Now, restart Windows 10 to finally initiate the disk check.

When this completes scanning, Windows 10 OS loads containing a list of bugs and errors that it encountered.

6] Repair Missing or Damaged System Files

The presence of corrupted data inside Windows 10 may also lead to different bugs and errors. Kernel Mode Heap Corruption Error 0x0000013A is one such bug. System File Checker is an in-built tool by Microsoft that can replace corrupted, lost, or missing DLL files. One can use this utility program even when you are not able to boot into Windows normally. Here’s how to proceed –

Case 1: When you can’t enter Windows or Safe Mode

• Enter WinRE then follow Troubleshoot > Advanced Options > Command Prompt.

Case 2: When you can enter Windows or Safe Mode

• Use Win + R  to start Run, type cmd, and jointly press Ctrl + Shift + Enter keys.
• Now that you have entered Windows Console, type “sfc/scannow” and hit Enter.

• Wait for the SFC to find and repair corrupted DLL files. Usually, this takes 10-15 minutes.
• Once over, Restart PC to incorporate the above changes.

Sign back into Windows and check whether you still encounter the BSOD Error 0x0000013A or if it has already been fixed. 

7] Look for Memory Issues

Having a bad RAM slot is another faulty reason that may erupt the KERNEL_MODE_HEAP_CORRUPTION error. This situation may arise due to sudden power surges, excessive heating, or simply motherboard issues. So, you must consider the “Memory issues” as a possibility and try fixing them (if possible). Here’s how to check for bad memory issues on Windows 10 –

• Hit the Start Menu and start typing “memory” in the search box.
• Click the well-matching result to enter Windows Memory Diagnostic.
• Choose to Restart now and check for problems. 

Note: Make sure to save any ongoing process on the computer.

• The system reboots and checks for any memory issues on the computer.
• After scanning for memory problems successfully, the device restarts with a list of all “detected issues”.

8] Use System Restore Points 

If none of the above solutions work to resolve the 0x0000013A error, use restore points to revert back your system to an earlier state when everything was working fine. In case, you don’t have a restore point or haven’t created any system backup, perform a clean installation of Windows 10. 

That’s it, if you have any queries or suggestions related to this article, ping us in the comment section.

Some Windows 11 are dealing with a weird issue where every attempt at putting their PC to sleep ends with a crash. Upon investigating the crash caused using Event Viewer, the error code displayed is 0x0000013A (KERNEL_MODE_HEAP_CORRUPTION).

We’ve investigated this particular issue thoroughly and we’ve discovered that this type of error always indicates a kernel-related issue where the heap manager has detected an underlying corrupted issue in a heap.

Now, when it comes to this issue, there are several underlying possible scenarios that might lead to the apparition of this issue. Here’s a list of possible culprits that you should watch out for:

Uninstall the Dell Support Center (If applicable)

In case you’re using Dell hardware, you should know about this weird incompatibility between Windows 11 and the Dell Supporting Center utility.

This might change in the future, but as of now, a lot of Dell desktop, ultrabook, and laptop users are reporting that their Windows 11 installation crashes every time they put it in Sleep mode or after they leave it idle for a long period of time.

Important: If you’re not using any Dell hardware or the Dell Supporting Center tool is not installed, skip this method entirely and move directly to the next method below.

As it turns out, this happens due to a program called Dell Supporting Center that apparently conflicts with a kernel process and causes the OS to crash.

As of now, the only way to resolve this major inconvenience with Windows 11 Dell computers is to simply uninstall the Dell Support Center.

Note: If a new version of the program is released, you can also try installing the latest version and see if the conflict has been patched by Dell’s engineers.

If you’re looking for step by step instructions on fixing this inconvenience, follow the instructions below:

1. Press Windows key + R to open up a Run dialog box. Next, type ‘appwiz.cpl’ inside the text box and press Enter to open up the Programs and Features menu.
2. Once you see the User Account Control windows, click Yes to grant admin access.
3. Inside the Programs and Features menu, scroll down through the list of installed programs and locate the Dell Supporting Center.
4. When you locate the correct program, right-click on it and choose Uninstall from the context menu that just appeared.
5. Inside the uninstallation screen, follow the on-screen instructions to complete the uninstallation of Dell Supporting Center, then reboot your PC and see if the issue has been fixed by putting your PC into hibernation mode once again.

Note: If you’re fond of this tool, you can also go to the official download page of Dell and download the latest rebranded version of this tool – Dell Support Assist. Additionally, here are a few other troubleshooting steps that you can try for Dell computers.

If the same 0x0000013A (KERNEL_MODE_HEAP_CORRUPTION) error is still occurring despite the fact that you uninstalled the Dell Supporting Center tool.

Run Intel Driver Assistant to install every compatible driver

If the first method above was not applicable in your case, the next thing you should worry about is a potentially conflicting generic driver that is forcing the system to crash while in low-power mode.

This is commonly reported to occur with generic drivers that have been migrated to Windows 11 from an older Windows version.

Several other users that have dealt with this particular scenario have confirmed that the crashes with the 0x0000013A error have stopped once they used the Intel Driver Assistant to replace the generic equivalents of the CPU, Bluetooth, and Wi-Fi Card drivers with equivalents from Intel.

If you want to pursue this fix too, follow the instructions below:

1. On your Windows 11 computer, open up your default browser and navigate to the official page of Intel Driver & Support assistant.
   Note: If it’s the first time you’re using this tool, you will be asked to install a small utility that will scan your system locally for outdated driver and firmware. If asked to do so, install the local tool as instructed.
2. Once the tool is installed locally, wait until it scans your system of possible outdated drivers. If any occurrences are found, click on the Download All button and wait for the utility to download every pending driver.
3. Next, click on Install all to replace every current generic driver with Intel’s dedicated equivalents.
4. When asked to restart your PC, do so and see if the issue is fixed once the next startup is complete.

In case you’re still seeing the same 0x0000013A error after your Windows 11 OS crashes when you put it into sleep, move down to the next method below.

Uninstall Paragon Software & remove BioNTDrv_WINK.SYS (if applicable)

One driver that is commonly mentioned as a potential cause for this type of KERNEL_MODE_HEAP_CORRUPTION crash is BioNTDrv_WINK.SYS. This is a driver that typically gets installed with Paragon software.

BioNTDrv_WINK.SYS is a backup or cloud service software driver that’s known to conflict with certain kernel processes on Windows 11.

If you find yourself in this scenario and you have the Paragon Software package installed, the first thing you should do is go over on the developer’s website and install the latest available version.

In case that’s not an option for you (as you already have the latest driver version installed), the only option for you is to simply uninstall the conflicting software.

Follow the guide below for step by step instructions on how to do this:

1. Press Windows key + R to open up a Run dialog box. Next, type ‘appwiz.cpl’ inside the text box, then press Enter to open up the Programs and Features menu.
2. Once you see the User Account Control, click Yes to grant admin access.
3. Inside the Programs and Features menu, scroll down through the list of currently installed programs and locate the entry associated with Paragon software.
4. When you see it, right-click on it and choose Uninstall from the context menu.
5. Inside the uninstallation screen, follow the on-screen instructions to complete the uninstallation prompts until you manage to get rid of the software.
6. Reboot your PC and see if you still get the same kind of crash when you attempt to put your Windows 11 PC to sleep.

If this method was not applicable to you or you already uninstalled the Paragon software and the 0x0000013A (KERNEL_MODE_HEAP_CORRUPTION) error is still occurring, move down to the final potential fix below.

Update BIOS version to the latest

If none of the methods above have been effective in your case, the final culprit that you should investigate is an outdated BIOS driver that is not really compatible with the Windows 11 pre-release that you currently have installed.

Note: Keep in mind that Windows 11 just launched officially, so motherboard manufacturers are only now beginning to roll out BIOS firmware updates to accommodate this new operating system.

As of now, most of the major manufacturers have released BIOS updates to improve kernel stability on Windows 11. Chances are by installing the BIOS update compatible with your motherboard, you will be able to fix the 0x0000013A error appearing when you switch your PC to low power mode.

Of course, BIOS interfaces will vary a lot among different motherboard manufacturers, so we won’t be able to provide you with a dedicated guide that will walk you through the entire process of updating your BIOS version to the latest.

But a good start is to take the time and read the official documentation provided by your motherboard manufacturer in regards to updating your BIOS. Here are a few useful links:

• Dell  
• ASUS  
• Acer  
• Lenovo  

Note: If your motherboard is not among the list above, do a Google search on ‘BIOS Update + motherboard model’ and take the time to read the documentation thoroughly to get a grasp of the entire process.

If your motherboard manufacturer recommends that you update via a flash drive, follow the instructions below for a general guideline that will show you how to set up a flash drive and use it to update your current BIOS version:

1. First things first, start by ensuring that you have a blank USB flash drive at your disposal. If you have important data on your drive, take the time to store it away before advancing to the next step.
2. Next, open File Explorer, right-click on the flash drive and choose Format from the context menu.
3. Inside the Format screen, choose FAT32 from the file system options, then click on Quick Format and hit the Start button to commence the process.
4. Once the operation is complete, visit the website of your motherboard manufacturer website and download the BIOS update after you take the time to read the entire documentation about updating.
5. After you download the latest version of the BIOS driver, paste it on your flash drive (by following the instructions).
   Important: You might need to place the BIOS update in a specific folder, so take the time to read the documentation properly.
6. Once you manage to copy the BIOS update on your flash drive, reboot your PC and press the SETUP key at the initial screen to access the BIOS Settings.

   Note: In case you don’t manage to spot the Setup screen on screen, press the Esc key, the Dell key or one of the following F keys – F2, F4, F6, F8, and F12. Additionally, you can search online for specific instructions on accessing your BIOS settings according to the motherboard model that you’re using.

7. Once you’re finally inside the BIOS settings menu, look for the Advanced (Expert) settings and see if you can spot an option similar to Update System BIOS (or similar).
8. Follow the remaining instructions to complete the BIOS update, then reboot your PC normally and see if the 0x0000013A error is now fixed.