Windows 10: Critical error Event ID 41 after every shutdown and bootup.

==> NOTE <==

I placed this thread under the "bsod-crashes-debugging" forum because I wasn't sure where it belonged. If the moderator is able to move it to a more appropriate forum, please do so. If it is moved to a different forum, please inform me via email. Thanks in advance for any assistance with this issue.

-----------------

BACKGROUND:

Prior to upgrading to Windows 10, my system was running Windows 7 Home Premium SP1. When running my previous OS (WIN 7) I rarely had errors listed in Event Viewer. Now after upgrading to Windows 10, I get errors/warnings I never used to get under Windows 7.

The error I would like help with today is of the "Critical" level in Event Viewer.

PROBLEM:

After doing a normal shutdown, and then booting my system, I check Event Viewer and always find the following critical error:

"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

---------------------- START: Event Viewer XML error text ---------------------

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>3</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000200000000002</Keywords>
<TimeCreated SystemTime="2015-08-30T00:58:14.880836200Z" />
<EventRecordID>11290</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Ghost-Machine</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">6</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">3221225684</Data>
</EventData>
</Event>

---------------------- END : Event Viewer XML error text ---------------------

REQUEST:

I never used to get this error after doing a normal shutdown (prior to upgrade to Windows 10, when I was on Windows 7). Now it happens all the time.

Can you help me figure out why this error is occurring after doing a normal shutdown followed by a boot?

I suspect it's a glitch with the first production release of Windows 10, but I have no proof of that. My system runs fine, yet I get the above error (and a number of other errors) since I upgraded to Windows 10.

:)

 

The previous system shutdown was unexpected windows 10

ok i went in Event Viewer and found 4 Critical so i went and looked at Reliability Monitor as well and seen that all 4 Critical line up with when my pc rebooted on me. all the reboots seem to happen about 20 min's after it say's The Previous system shutdown
so i hope this helps to fix this problem.

Event Viewer

--------------

Level Date and Time Source Event ID Task Category KeyWords OpCode

------- ----------------- ----------- ----------- ---------------- ------------- ----------

Critical 9/15/2016 6:47:28 pm Kernel-Power 41 (63) (70368744177664),(2) info

Critical 9/14/2016 7:21:16 pm Kernel-Power 41 (63) (70368744177664),(2) info

Critical 9/7/2016 12:36:31 pm Kernel-Power 41 (63) (70368744177664),(2) info

Critical 8/29/2016 1:15:39 pm Kernel-Power 41 (63) (70368744177664),(2) info

Reliability Monitor

---------------------

The previous system shutdown at 6:35:44 PM on ‎9/‎15/‎2016 was unexpected. = Rebooted at 6:48 pm.

The previous system shutdown at 7:01:05 PM on ‎9/‎14/‎2016 was unexpected. = Rebooted at 7:21 pm.

The previous system shutdown at 12:11:16 PM on ‎9/‎7/‎2016 was unexpected. = Rebooted at 12:36 pm.

The previous system shutdown at 12:50:57 PM on ‎8/‎29/‎2016 was unexpected. = Rebooted at 1:15 pm.

 

Restarts

Thought things were too good to last, it started again this morning after 3 good days and about every hour since. Went through all same procedures as last time plus Norton super clean but this has made no difference. Shows on Event Viewer as 7 Critical
event ID 41 Kernel-power on System, today with a lot of errors as well as lots of audit failures.

 

RESOLVED:

Since placing this thread, I was addressing other errors I found in the event logs. One of those had to do with "Metadata staging failed".

Researching about this error let me to the URL:

http://www.eightforums.com/bsod-cras...-failed-3.html

where poster Saammy gave the following possible solution:

I have the solution for the problem.
Searches on regedit for the following entry: DeviceMetadataServiceURL
There you change the URL in the following: http://dmd.metaservices.microsoft.com/dms/metadata.svc
after you have closed the editor is saved the change.
Now the problem is solved and it will also re-loaded device information.

As instructed, I used regedit and searched for "DeviceMetadataServiceURL", and it's value was set to:

http://go.microsoft.com/fwlink/?Link...69&clcid=0x409

I changed the value to "http://dmd.metaservices.microsoft.com/dms/metadata.svc" and then rebooted.

The end result was that this did indeed fix the "Metadata staging failed" errors, and interestingly enough the Event ID 41 is no longer showing up in the event logs after shutdown/reboot. I did 5 shutdown/reboot sequences... 1 per hour, and neither problem has occurred since making the above change.

 

I have done what you said, and I still receive the same error. It can happen once a day, once a week, or several times in the same day.

The computer only lists the error after shutdown, My PC does not loose power during normal usage. From a bystander`s
perspective everything is ok.

What I am asking is this: Does windows lists the error as a false positive ? Or does the PC actually somehow looses power during shutdown ?

 

I'm experiencing the same issue and haven't been able to resolve it. I even did a clean install of Win 10, version 1511.

Thanks,

Rick

 

If you two would start your own threads, you would probably get a better response. This thread has been marled solved, so most people will not look at it.