Диспетчер питания ядра инициировал завершение работы windows 7

Suppose you’re working on your computer and suddenly a message shows up saying the kernel power manager has initiated a shutdown transition. It mostly happens due to an error with the operating software, a faulty driver, or battery issues.

But don’t worry about your PC health as long as we are here to help you. In this complete guide, we will provide some important information on why this kernel error occurs and how you can fix it. So, without further ado, let’s solve the issue.

Картинка с сайта: wingeek.org

Why The Kernel Power Manager Has Initiated a Shutdown Transition or the Event ID 109 Appears

There could be many reasons why the kernel power manager event id 109 happens. Here are the most possible reasons –

Reason 1: For General Troubleshooting

The kernel takes care of the operating system software and can initiate certain processes without asking for permission. ‘Event ID 109’ as well as ‘Task Category 103’ appear whenever the PC becomes shut down because of Kernel API (Application Programming Interface). In most cases, the Event ID issue may appear for general troubleshooting while doing nothing for a long time on the running PC. 

Reason 2: Due to Low Battery

The most essential reason behind the kernel initiating a shutdown is low power or battery. The system runs on low power if the battery is low. Your computer may automatically shut down while the battery percentage is under 5% or below. It happens to make sure the battery never reaches the lowest level.

Reason 3: Faulty Driver

Another reason behind the error is faulty drivers. Sometimes the drivers may show error signs which is a clear indication that the drivers are faulty. Again, the kernel power manager error occurs if the drivers are outdated.

Reason 4: Faulty Windows Update

A buggy or faulty Windows update can also be the reason behind the kernel-initiated shutdown. If you’re facing the error after a recent update, then you can assume it is because of the Windows update and go for fixing this to avoid the error.

So, what can you do if you confront the issue? Let’s follow the methods below to fix the issue.

Solution 1: Charge the Battery

If the battery percentage of your device is lower than 5%, then the kernel-initiate shutdown may occur. So, try not to keep the battery percentage below 20% and whenever the battery is low, quickly connect your device to the charger.

But if you are facing the error on your desktop computer, then follow the next solution below. 

Solution 2: Update Drivers

If your drivers are outdated or faulty, updating the drivers can fix the kernel-initiate shutdown error. Here are the steps to follow –

Step 1: Right-click on the Windows icon from the bottom-left corner and click ‘Device Manager’.

Step 2: On the device manager, check all drivers and right-click to update them. If you found an error sign, then update them first.

Картинка с сайта: wingeek.org

Step 3: After clicking ‘Update Driver’, select ‘Automatically update drivers’ and follow the on-screen prompts to update the drivers.

Картинка с сайта: wingeek.org

Note: Make sure you’re connected to the internet on your device while updating the drivers. 

You can also check for the missing drives by navigating to Settings > Update & Security > Windows Update > View all optional updates > Driver Updates. Select the missing drivers from the list and click ‘Download and Install’ to install them on your device.

After this restart, your computer and the kernel-initiate shutdown error will be resolved.

Solution 3: Uninstall Windows Update

If you are facing the kernel-initiate shutdown error due to a faulty Windows update then follow the steps below to uninstall the update and fix the issue.

Step 1: Click on the Windows icon in the bottom-left corner and click the Gear icon to access Settings.

Картинка с сайта: wingeek.org

Step 2: Select Update & Security and while on the Windows Update tab, select ‘View Update History’.

Картинка с сайта: wingeek.org

Step 3: Click ‘Uninstall’ update and it will take you to the list of Windows updates.

Картинка с сайта: wingeek.org

Step 4: Select the latest update from the list and click ‘Uninstall’ to uninstall the update.

Картинка с сайта: wingeek.org

After this, restart your computer and you won’t face the issue again.

Bonus Tip: How to Return Back Previous Session After a Sudden Shutdown

One thing you can apply is to return back the previous session where the PC was kept before the shutdown occurred. To do so, you need to follow the below steps. 

Step 1: Tap the Windows and ‘R’ keys together. Consequently, the ‘Run’ window will appear. 

Step 2: Here you have to type ‘cmd’ into the ‘Open’ box. Then click on ‘Ok’.

Step 3: After that, the ‘Command Prompt’ will appear on the screen. You have to type ‘powercfg -lastwake’. 

Step 4: At the end, tap the ‘enter’ button and you’ll be returned to the previous session.

Frequently Asked Questions and Answers

What Is the Kernel Power Manager?

The Windows Kernel-Power manager is a system tool that manages the changes in power status orderly for all the devices and components of a computer that are sensitive to power state changes. It also troubleshoots if any error occurs with the power or battery.

What Causes Event 109 Shutdown?

Event 109 shutdown occurs if the user request for a turn-off or restart on the computer. It can also occur if the power button is pressed while the computer is running. Again, if the computer shuts down due to high temperature, faulty power supply, or faulty system software, it will show the Event 109 error. 

What Is Event 41 Kernel-Power Shutdown?

Event 41 Kernel-Power means there is a wrong device driver installed on your computer, especially an old or corrupted sound card driver. Updating all the available drivers on the computer can fix this error.

How to Disable Kernel Mode?

To disable Kernel Mode, navigate to Control Panel > Administrative tools > Service. Then right-click the service that you want to configure and select Properties. Finally, click Disabled in the Startup type box in the General tab to disable it.

Final Words

Therefore, the issue- ‘the kernel power manager has initiated a shutdown transition’ is not a PC thread or a damage indication. However, you may follow the described solutions to fix the issue. If you have solved the error with the help of our solutions, don’t forget to mention it in our comment section. Thanks for reading.

Добрый день.

Это продолжение моей проблемы, на которую так никто и не ответил, приведу текст ниже;

Добрый день. Сразу скажу, что логи и действия из статьи я выполнить чисто физически не могу, так как банально не могу войти в систему. Причины приведу ниже.

Мой ноутбук, купленный с маркетплейса у каких то китайских производителей со сразу скачанной виндой потерпел «крушение » — я скачал вирус. На следующий день после скачивания программы я включаю ноутбук, жду пока загрузится система, и тут — он просто не загружается. Вечно загружает и все. Не стал унывать, зашел в среду восстановления и откатил через точку восстановления — благо она там была. Ждал около 4 часов, на что компьютер выдал ошибку — восстановление завершено безуспешно. После перезагрузки пк меня таки запустило в систему, на рабочем столе была ошибка того, что восстановления прошло с ошибкой. После минуты пребывания в ней вылез BSOD с ошибкой CRITICAL PROCESS DIED. Теперь так с каждой перезагрузкой. Пытался зайти в безопасный режим через горячую клавишу f8 и другие различные вариации — запускает обычную систему. Через среду восстановления — также. В командую строку также не могу зайти. Кроме сноса винды и восстановления через USB способов решения не вижу, но пока такой возможности нет, поэтому пишу это сообщение. Надеюсь, что вы сможете решить данную проблему»

Не дождавшись ответа, я просто решил поставить новую систему.

Скачал iso-файл, поставил. Начал процесс переустановки. На моменте выбора диска необходимо отформатировать диск, что у меня не получилось. Пытался удалить разделы, они просто не удаляются.

Пробовал через diskpart, говорит, что отказано в доступе, хотя графа «только для чтения» выключена. Попробовал уже все, что есть на просторах интернета, уже начинаю сдаваться. Думаю, что проблема в битых секторах диска. Все это делал на установочной среде флешки.

UPD: В биосе я также выключил Secure Boot