Содержание
- Kernel power 42
- SOLVED: Windows Kernel Power Event 41 Error [Updated 2022]
- Компьютер перезагружается сам. Решение на УРА.
- Kernel power 42
- Как решить проблему с пробуждением из спящего режима?
- Компьютер сам перезагружается Windows 10. «kernel power 41»
If you have updated to win 8.1 and you get the error message « the system cannot find the file specified» it is a known problem. The work around is to edit the registry. If you are not comfortable doing this DONT. If you are, backup the key before you do
Kernel power 42
I am stumped here. We have a Windows Server 2016 Datacenter Host, Hyper-V role, 8 Virtual Machines (all same OS as host). One of these Virtual Machines is a Terminal Server for a number of users inside and outside the LAN. I’ll call it TS-SERVER. TS-SERVER randomly reboots a number of times a week. It always logs Event 41, Kernel-Power, but I cannot find the underlying reason. Obviously this is a critical issue for us since 5-10 users can be logged into this VM at any given time, all of them losing any unsaved work every time it happens. I’ve browsed the event logs surrounding the times of the reboots, but I can’t seem to pinpoint any related events. No Bugcheck logged either. Any suggestions are appreciated. Thank you
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2/27/2018 11:05:20 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: TS-SERVER.domain.local
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
» />
0
0x0
0x0
0x0
0x0
0
0
0
0
false
0
0
- Edited by mattwc Tuesday, February 27, 2018 8:02 PM
Tuesday, February 27, 2018 7:48 PM
All replies
I’d try; under system properties, Advanced system settings, Advanced tab, Startup and Recovery section, Settings, clear the Automatically restart check box.
Regards, Dave Patrick .
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.
Tuesday, February 27, 2018 10:28 PM
Thanks Dave, did that just now. Now it’s a waiting game because it really is random. Sometimes it happens once a week, sometimes twice in 24 hours.
Wednesday, February 28, 2018 4:53 PM
Sounds good, see what happens.
Regards, Dave Patrick .
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.
Wednesday, February 28, 2018 4:56 PM
Looks like it happened again on Sunday, same Kernel-Power error. I didn’t notice until now since no one was affected by it on a Sunday. The last time it happened before that was 2/27, the day I posted this thread.
Tuesday, March 6, 2018 6:16 PM
Are there any Group Policy settings applied that have to do with power? Are there any power related issues on the host? Are the host and guests up to date? Philip Elder Microsoft High Availability MVP Blog: http://blog.mpecsinc.ca Twitter: @MPECSInc
Wednesday, March 7, 2018 6:01 AM
Hi , Just want to confirm the current situations.
Please feel free to let us know if you need further assistance.
Best Regards,
Candy
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Thursday, March 8, 2018 5:40 AM
Has anyone heard of a fix or more information on this. I’m having the exact same issue on two HyperV VM’s in the same situation, they host our thin client sessions so when they die the users booted out in the middle of what they were doing. This started happening 2-3 days ago and I’ve ran Windows update and rebooted when necessary both the VM hosts and the VM’s. There are about 14 VM’s between the two hosts and only these two VM’s are being affected.
Friday, March 16, 2018 4:57 PM
Sorry everyone, I stopped getting email notifications on this thread for some reason. Phillip, No GPOs related to power, no power issues on host, and all is relatively up to date. The host was last updated about a month ago, the VM is updated once a week or so. I haven’t seen a Kernel Failure in 10 days, and the only thing I changed was the NAT policy in our firewall. I was noticing a huge amount of failed login attempts every second because we were using the default RDP port number 3389 and it was open to the public. I thought this would be fine since we have 2-factor authentication using third party software, but seeing all the attempts in the event log made me uncomfortable so I changed the NAT policy only for outside sources. This is literally all I changed, and I haven’t seen a power failure since (or any questionable logon attempts). I don’t know if it’s coincidence or if somehow the brute force attempts were triggering something that caused the unexpected shutdown. If it happens again, I’ll post here right away, but for now that’s the only clue I have as to a related event or possible cause.
Monday, March 19, 2018 7:34 PM
TSGrinder. Please use RD Gateway and RD Broker with a separate RD Session Host. Never, _ever _, open a Remote Desktop Protocol listener to the Internet on any port. Philip Elder Microsoft High Availability MVP Blog: http://blog.mpecsinc.ca Twitter: @MPECSInc
- Edited by Philip Elder MVP Monday, March 19, 2018 7:38 PM
Monday, March 19, 2018 7:38 PM
The problem is back. it was down to only happening once a month or so. Now it’s had 3 kernel-power reboots in the last two days. There have been no changes that we’re aware of, and event viewer doesn’t tell me anything except «the previous system shutdown . was unexpected»
SOLVED: Windows Kernel Power Event 41 Error [Updated 2022]
Wednesday, May 16, 2018 6:41 PM
Did you ever find a solution?
Wednesday, May 16, 2018 6:42 PM
The night before the problem came back I had upped the number of virtual cores from 8 to 12. After 4 reboots in two days I put it back down to 8 and today it has been fine so far
Thursday, May 17, 2018 10:37 PM
Still having this issue. I finally found a correlation on the host. The host logs Event 18550, Hyper-V-Worker. ‘VmName’ was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault. This error might have been caused by a problem in the hypervisor. If the problem persists, contact Product Support. (Virtual machine ID ) Still can’t figure out why that’s happening, but at least I’m getting somewhere. I plan to contact Dell support but running their diagnostic would require me to bring down all the VMs.
Friday, May 25, 2018 6:31 PM
HI mttwc, I do have the same issue, did you find the a fix for the issue, would you please share your resolution steps?
Tuesday, July 31, 2018 6:39 AM
Hi mttwc, I do have the same issue, did you find the a fix for the issue, would you please share your resolution steps?
Wednesday, August 1, 2018 4:58 AM
Seeing the same issue on two 2016 Datacenter hosts. It’s happening to both of them here and there. No pattern that we’ve been able to identify, either.
Tuesday, August 21, 2018 12:38 PM
Anybody ever come up with a solution to this? I am seeing the same issue. Server 2016 DC cluster, Windows 10 1709 VMs. I have now had 3 out of 476 show this error over the last 2 weeks. Have never seen prior. Hosts and VMs all patched with all FW and updates applied. All of what has been stated above is the same with me. Errors in VM and in host match up. No changes to host or VM hardware. Definitely a goofy situation.
Wednesday, February 20, 2019 3:20 PM
. ran into the same problem: Windows Server 2019, one of the two virtual machines started crashing ~ 2 times a day. No 18550 events, but I noticed that the following events — presumably- appear in the log before the VM craches: After stopping the backup jobs that were using that VM’s drive D: no crashes have occured so far. Regards,
Michael
- Edited by MF47 Thursday, April 25, 2019 6:58 AM
Thursday, April 25, 2019 6:58 AM
. ran into the same problem: Windows Server 2019, one of the two virtual machines started crashing ~ 2 times a day. No 18550 events, but I noticed that the following events — presumably- appear in the log before the VM craches: After stopping the backup jobs that were using that VM’s drive D: no crashes have occured so far. Regards,
Michael
What backup product and what version is it please?
Philip Elder Microsoft High Availability MVP Blog: http://blog.mpecsinc.ca Twitter: @MPECSInc
Компьютер перезагружается сам. Решение на УРА.
Thursday, April 25, 2019 5:26 PM
I’m using the built-in Windows Backup (OS=WinServer 2019 Standard). Regards,
Michael Firsov
- Edited by MF47 Thursday, April 25, 2019 6:37 PM
Thursday, April 25, 2019 6:33 PM
I’m using the built-in Windows Backup (OS=WinServer 2019 Standard). Regards,
Michael Firsov
Make sure in-guest volume shadow copy snapshots are not happening within 1 hour before/after the host backup runs. Check the problematic drive’s snapshot cache it may be full.
Philip Elder Microsoft High Availability MVP Blog: http://blog.mpecsinc.ca Twitter: @MPECSInc
- Edited by Philip Elder MVP Thursday, April 25, 2019 6:49 PM
Kernel power 42
My Sony VAIO randomly goes to sleep after a couple minutes. The sleep setting—both with and without battery power—is set to ‘never’ (so it should never sleep if the system is idle, right?). Here is the event log:
Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2/21/2015 11:19:17 AM Event ID: 42 Task Category: (64) Level: Information Keywords: (4) User: N/A Computer: valika-VAIO Description: The system is entering sleep. Sleep Reason: System Idle Event Xml:" /> 42 2 4 64 0 0x8000000000000004 34416 System valika-VAIO 5 5 7 0
I could not find an answer to this problem myself. Please let me know if there’s anything I could do to fix the problem!
Thanks!
Saturday, February 21, 2015 4:54 PM
Answers
Update: I figured this out after noticing that my computer was hibernating, not sleeping, after running the powercfg -a command above. I managed to ‘fix’ it. Control panel -> Power options -> Change plan settings -> Change advanced power settings
under «Sleep» there should be a Hibernate after: setting. Mine said Hibernate after: Plugged in: 2 minutes. I just changed 2 to 60. Thanks for all help.
- Marked as answer by vali7oscar Saturday, February 21, 2015 10:31 PM
Saturday, February 21, 2015 10:31 PM
All replies
Vali Please upload the event viewer logs and run this from an elevated command prompt powercfg -a to tell us the supported sleep states.
Please provide us with your Event Viewer administrative logs by following these steps:
Click Start Menu
Type eventvwr into Search programs and files (do not hit enter)
Right click eventvwr.exe and click Run as administrator
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As.
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file to Onedrive or a file sharing service and put a link to it in your next post
If you have updated to win 8.1 and you get the error message « the system cannot find the file specified» it is a known problem. The work around is to edit the registry. If you are not comfortable doing this DONT. If you are, backup the key before you do
Press Win+»R» and input regedit
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels. Delete «Microsoft-Windows-DxpTaskRingtone/Analytic»
Как решить проблему с пробуждением из спящего режима?
В прошлом уже спрашивал насчёт этого, но до сих пор не удаётся найти решение.
Суть проблемы: незапланированное самопробуждение Windows 10 через некоторое время после перехода в спящий режим (как правило, через несколько часов). То есть пробуждение скорее всего запланированное, но не с моей стороны.
Записи из системного журнала Windows:
Компьютер сам перезагружается Windows 10. «kernel power 41»
@
Имя журнала: System
Источник: Microsoft-Windows-Kernel-General
Дата: 19 Октября 2018 1:24:42
Код события: 1
Категория задачи:(5)
Уровень: Сведения
Ключевые слова:Time
Пользователь: Н/Д
Компьютер: DESKTOP
Описание:
Системное время изменено с 2018-10-18T16:24:43.929897300Z на 2018-10-18T19:24:42.500000000Z.
Причина изменения: System time synchronized with the hardware clock.
@
Имя журнала: System
Источник: Microsoft-Windows-Kernel-Power
Дата: 19 Октября 2018 1:24:42
Код события: 131
Категория задачи:(33)
Уровень: Сведения
Ключевые слова:(1024),(4)
Пользователь: Н/Д
Компьютер: DESKTOP
Описание:
Значения времени встроенного ПО для S3. ResumeCount: 1, FullResume: 664, AverageResume: 664
@
Имя журнала: System
Источник: Microsoft-Windows-Kernel-Power
Дата: 19 Октября 2018 1:24:43
Код события: 105
Категория задачи:(100)
Уровень: Сведения
Ключевые слова:(1024),(4)
Пользователь: Н/Д
Компьютер: DESKTOP
Описание:
Смена источника питания.
@
Имя журнала: System
Источник: Microsoft-Windows-Power-Troubleshooter
Дата: 19 Октября 2018 1:24:44
Код события: 1
Категория задачи:Отсутствует
Уровень: Сведения
Ключевые слова:
Пользователь: LOCAL SERVICE
Компьютер: DESKTOP
Описание:
Система вышла из состояния пониженного энергопотребления.
@
Имя журнала: System
Источник: Microsoft-Windows-Kernel-Power
Дата: 19 Октября 2018 1:24:45
Код события: 42
Категория задачи:(64)
Уровень: Сведения
Ключевые слова:(1024),(4)
Пользователь: Н/Д
Компьютер: DESKTOP
Описание:
Система переходит в спящий режим.
Причина: Hibernate from Sleep — Fixed Timeout
@
Имя журнала: System
Источник: Microsoft-Windows-Kernel-Power
Дата: 19 Октября 2018 1:24:46
Код события: 107
Категория задачи:(102)
Уровень: Сведения
Ключевые слова:(1024),(64),(4)
Пользователь: Н/Д
Компьютер: DESKTOP
Описание:
Система возобновила работу после режима сна.
@
Как пробовал решать проблему:
1. Отключение таймеров пробуждения: Электропитание — Изменение параметров схемы — Изменить дополнительные параметры питания — Сон — Разрешить таймеры пробуждения — Отключено.
2. Отключение быстрого запуска: Электропитание — Действие кнопок питания — Включить быстрый запуск (рекомендуется) — Отключено.
3. Запрет устройствам будить компьютер (powercfg -devicequery wake_armed — ни одного устройства).
4. Отключение автообновления времени (синхронизация с сервером Windows)
Говорят, ещё может помочь отключение задач в планировщике, которые выводятся по команде: powercfg /waketimers
То есть это те таймеры пробуждения, которые я уже отключал в разделе Электропитание.
Вчера в списке была задача по запуску службы UpdateOrchestrator, которая, как я понял, отвечает за автообновление Windows 10 и создается автоматически, но сегодня в списке powercfg /waketimers только:
C:\Windows\system32>powercfg /waketimers
Таймер, установленный [PROCESS] \Device\HarddiskVolume3\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe, действителен до 0:00:00
Скопировал всё, что вывелось.
В общем, есть ли ещё какие-то варианты решения?
P.S. БИОС, точнее в UEFI, тоже полный порядок. Нет ничего, что могло бы выводить из спящего режима.
- Вопрос задан более трёх лет назад
- 10751 просмотр
5 комментариев
Простой 5 комментариев
Похожие статьи
-
Проверьте целостность имеющихся в системе кабелей питания, а также плотность их подключениях к соответствующим разъёмам ПК; Проверьте работоспособность…
-
ЗЫ: мемтест отклонений не выявил. Event id 41 kernel power Установил windows 7 64 bit. После установки происходят регулярные перезагрузки с вылетом в…
-
Microsoft windows kernel processor power
Microsoft-Windows-Kernel-Processor-Power Event ID 37: The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in…