Unexpected Shutdowns, Event 41 Category 63

Hi all,
hope this is the right section, please feel free to move.

a long time back, in Win 7 days, my computer started doing sporadic power-offs, that i could never track down. Eventually, it just stopped altogether so i kinda forgot about them. Since i've gone to Win 10, i've had 2, one on the 17th and one just now.
on the 17th, it fired back up and was doing an update, so i went into the Updates bit and set the thing to "show notification when a restart is needed". tonight, it seems to have done it again after an update, as looking through the installed updates log it says it installed KB2267602. However, there was an update on the 18th, 19th and 20th too - same KB but different versions - that didn't cause the power off.

tonight's Event;
- System
- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331c3b3a-2005-44c2-ac5e-77220c37d6b4}

EventID 41
Version 6
Level 1
Task 63
Opcode 0
Keywords 0x8000400000000002
- TimeCreated
[ SystemTime] 2020-01-21T17:00:05.782067200Z
EventRecordID 2159
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8
Channel System
Computer Leviatha
- Security
[ UserID] S-1-5-18
EventData
BugcheckCode 0
BugcheckParameter1 0x0
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 0
CsEntryScenarioInstanceId 0
BugcheckInfoFromEFI false
CheckpointStatus 0

Computer wasn't stressed so it wasn't a heat issue etc, i was just on the internet looking at emails.
hope someone can help, this got me stressed out last time, hope it's not going to be a recurring thing again :-(

TIA


EDIT;
if it means anything, or might be a factor; i looked in the device manager, no "!" symbols etc, but both my mouse and keyboard have duplicated entries. under the keyboard properties -> events tab it says, "device not migrate" from the date i put Win 10 on, and
"Device HID\VID_046D&PID_C31C&MI_00\7&9409e4f&0&0000 was not migrated due to partial or ambiguous match.
Last Device Instance Id: HID\VID_046D&PID_C31C&MI_00\7&28B6C23E&0&0000
Class Guid: {4d36e96b-e325-11ce-bfc1-08002be10318}
Location Path:
Migration Rank: 0xF0001000FFFFF100
Present: true
Status: 0xC0000451"

the mouse is the same;
"Device HID\VID_258A&PID_1007&MI_00\7&70fbf39&0&0000 was not migrated due to partial or ambiguous match.

Last Device Instance Id: HID\VID_046D&PID_C069\6&26E92714&0&0000
Class Guid: {4d36e96f-e325-11ce-bfc1-08002be10318}
Location Path:
Migration Rank: 0xF000F000FFFFF100
Present: false
Status: 0xC0000451"

wolfie138 said:

ta, but not really helpful, i'm not overclocking etc.
"

1. Right-click My Computer, then select Properties > Advanced system settings > Advanced.
2. In the Startup and Recovery section, select Settings.
3. Clear the Automatically restart check box.

"
i can't find that :-/

the power supply is good, it's not a power issue because i've been living w/ power issues for about 4 months, where the supply to the house was dipping, and it never caused these issues. none of the fans are going silly.


edit, from last time, not that it's much help i guess
Unexpected Shutdowns :-/ - Windows 7 Help Forums

same symptoms though...

- - - Updated - - -

Ok, just an update/further info. had a look through my System events leading up to the power off, no criticals, just Infos and Warnings. too many to list but the following are a couple that i think seem odd:
172, task category 203 "Connectivity state in standby: Disconnected, Reason: NIC compliance"
219, task category 212 "The driver \Driver\WudfRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&2."
27, no task category, source e1i65x64, "Intel(R) Ethernet Connection (2) I218-V
Network link is disconnected."

10016, DistributedCOM "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{22279AF5-03AE-4CAF-989D-2530918B2F1C}
and APPID
{0773CCD6-59A2-4D26-B235-19247767E645}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
[there's lots of these Distributed COM ones]

15, source ACPI ": The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS."

7045, service control manager "A service was installed in the system.

Service Name: Nal Service
Service File Name: C:\WINDOWS\system32\Drivers\iqvw64e.sys
Service Type: kernel mode driver
Service Start Type: demand start
Service Account: "

7026, service control manager, "The following boot-start or system-start driver(s) did not load:
dam"

and, as mentioned above, the last thing to be logged was the update installation. systems was up about 15, 20 mins before the power off.

all the events about my drives report them as healthy, no action needed.

Also, in case @zbook happens along, i should mention this isn't the machine he's previously helped me w/.

TIA

- - - Updated - - -

Hi wolfie138,

Please upload V2 into this thread:
BSOD - Posting Instructions

Hi zbook, thanks for dropping by

V2 attached.

1) Check the motherboard manufacturer's website > upgrade the BIOS
(post a URL or hyperlink into the thread)
(update to the most recent non-beta BIOS)

2) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free
Download Speccy | Find your computer specs, free!
Download Speccy | Find your computer specs, free!
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer


3) Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan


4) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools for Windows |
Seagate
How to use SeaTools for Windows | Seagate Support US

5) Open administrative command prompt and type or copy and paste:
6) sfc /scannow
7) dism /online /cleanup-image /scanhealth
8) dism /online /cleanup-image /restorehealth
9) sfc /scannow
10) chkdsk /scan
11) wmic recoveros set autoreboot = false
12) wmic recoveros set DebugInfoType = 7
13) wmic recoveros get autoreboot
14) wmic recoveros get DebugInfoType
15) bcdedit /enum {badmemory}

16) 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

17) Make sure that there is no over clocking while troubleshooting

Hi,
1) i'll get onto this when I get home.
i'll get the 2801 BIOS from here: Z97-A/USB 3.1 Driver & Tools | Motherboards | ASUS Global

2) I've already got HWMonitor. Nothing untoward shows in it whilst running, and I've run it a lot around the times I was getting crashes; when I crash of course, it loses the open log so I can't tell what was happening. I also ran that memtest fur shader thing, which I didn't really want to do as I don't believe in stressing a system needlessly - there were no problems.

the other stuff, i'll do. I did most of it when the problems occurred back in Win 7 and all looked fine, but another run won't hurt.

if it's of any help, the situation is basically this;
- i'm 99.999% sure it's not a hardware issue. Apart from the random times this happens, the system is rock steady; you can barely hear the fans going most of the time as it's not doing anything stressful.
- I don't do much to stress my system; Photoshop and modelling in Blender is 95% of my stuff. Even when doing a big render, the VGU and temperatures etc have all behaved.
- System is fairly basic, I don't fiddle or overclock. about the only thing I changed in the BIOS was a memory setting (sorry, can't recall, it was to use the full speed of the memory, or such like - just had a quick google, might have been the XMP thing?) and turn off the ASUS anti-surge feature, which to all accounts is horrible and pointless. regardless, all that was done when I built the system and it was solid for about 2 years before the first occurrence of this issue, and I've never changed anything since.
- As mentioned, I've been living w/ some pretty awful power issues for the past 4 months (now sorted), where the voltage has dropped and caused flickering lights. The computer has not been affected, no power-offs occurred because of it, and to counter the other side of the coin, the computer is plugged into a surge-protected socket.
- the power-offs always occur w/in about 30 mins or so of boot-up. As mentioned above and on the W7 threads, this seems to be in line w/ an update thing, though I don't know why this might be. doesn't seem logical, but...
- ...as a possible addition to that, I changed W7 to notify me of updates so I could pick and choose the downloads, and when - after I did that, I never got another power-off [over two years].

I really wish W10 handled updates the same way, I don't like things getting downloaded and installed w/out giving me the courtesy of notification. my web speed is pathetic, so updates choke everything down to a standstill usually which is really annoying if i'm on the net researching stuff.

cheers

- - - Updated - - -

So just to prove me wrong, another power-off tonight, 9 mins after boot, no updates. Not a blip for the 2+ hours uptime after that. so what's going on in the first 10~20 mins after boots...?
Anyways ~

1) Didn't get to the BIOS, had DNS issues as per my post elsewhere. I'm really loathe to mess w/ BIOS stuff, though, but i will if you still think it's worth it.
2) as above, nothing untoward on HWInfo
3) ahh...issues, but not on my OS disc:
OS disc:
Attachment 264245Attachment 264246Attachment 264247

2nd disc:
Attachment 264248Attachment 264249Attachment 264250
3rd disc:


4) only had time for quick and short generic tests - no issues reported.

5 ~ 16) attached file. i'm a bit peeved that there were SFC issues less than a week after a new upgrade, any idea how/why that might be?

Does your Reliability History give any reports immediately following the problem event?

joeandmarg0 said:

Does your Reliability History give any reports immediately following the problem event?

hi,
didn't seem to be anything useful, just listed the related "didn't shut down properly" event, didn't indicate what the cause might have been.

- - - Updated - - -

don't know what happened to those pics, they were there in the preview.
anyways:
OS disc


2nd disc:


argh, sorry about the prompt mistake. :-/ file attached.
ran your commands again in the command prompt;
Microsoft Windows [Version 10.0.18363.592]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
512512 file records processed.
File verification completed.
6583 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
2968 reparse records processed.
707570 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
2968 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
97530 data files processed.
CHKDSK is verifying Usn Journal...
36109080 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

249392486 KB total disk space.
146994080 KB in 406602 files.
279412 KB in 97531 indexes.
0 KB in bad sectors.
627794 KB in use by the system.
65536 KB occupied by the log file.
101491200 KB available on disk.

4096 bytes in each allocation unit.
62348121 total allocation units on disk.
25372800 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\LEVIATHA\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\LEVIATHA\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\WINDOWS\system32>