Windows 10: Kernal Power 41 Event 63 Please Help

Chkdsk is finished.
---



Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
346880 file records processed. File verification completed.
13946 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
482674 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Cleaning up 223 unused index entries from index $SII of file 0x9.
Cleaning up 223 unused index entries from index $SDH of file 0x9.
Cleaning up 223 unused security descriptors.
Security descriptor verification completed.
67898 data files processed. CHKDSK is verifying Usn Journal...
39813864 USN bytes processed. Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
346864 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...
159855069 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.
No further action is required.

976181247 KB total disk space.
336135016 KB in 215517 files.
140660 KB in 67899 indexes.
0 KB in bad sectors.
485291 KB in use by the system.
65536 KB occupied by the log file.
639420280 KB available on disk.

4096 bytes in each allocation unit.
244045311 total allocation units on disk.
159855070 allocation units available on disk.

Internal Info:
00 4b 05 00 cd 52 04 00 36 bb 07 00 00 00 00 00 .K...R..6.......
3c 02 00 00 3a 0e 00 00 00 00 00 00 00 00 00 00 <...:...........

Windows has finished checking your disk.
Please wait while your computer restarts.

 

Chkdsk had some findings that it corrected. There was no corruption.
For the new user were you able to compare performance to the current user?
Was it better, worse, or same? Start menu, task bar, etc.

Stress test the GPU:
http://www.geeks3d.com/20170502/furmark-1-19-gpu-burner-stress-test-opengl-benchmark/
It is very important to monitor temperatures.
Download and install one of the software temperature monitoring applications.
Watch temperatures and images on the monitor and look for artifacts and high temperatures.
If temperatures remain high abort the testing. See the link for more information:

Please make note of the importance of temperature monitoring and aborting the test in the GPU link.

FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials: FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials

All of these test should be done with the bios reset and no over clocking.

For each of the above tests please record maximum temperatures.

And please make sure that you use the Microsoft snipping tool to post images of each into the thread.

Take Screenshot in Windows 10 Windows 10 General Tips Tutorials


Choose one of the applications below to monitor computer hardware temperatures:

HWMONITOR | Softwares | CPUID

SpeedFan - Access temperature sensor in your computer SpeedFan - Access temperature sensor in your computer

Open Hardware Monitor - Core temp, fan speed and voltages in a free software gadget

Speccy - System Information - Free Download

 

I finished the test but unfortunately got some poor results. As soon as the test finished my computer crashed and now will not post. It maxed out at 65°C.

 

Run through the steps in this link:
POST troubleshooting steps

 

Just reseated the ram, reset bios, disconnected second monitor, and am noe using an HDMI to dvi cable directly to the gpu. It booted up fine. Could the cable have been an issue?

ALSO: I just re-ran the benchmark and got the same temperature but this time no crash. I have now connected my second monitor with an HDMI cable to see how it goes.

 

CRASHED AGAIN. I am getting tired of this. Am contemplating never buying a NVidia product again. Same issue:

"The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer."

Have read online that downgrading to 314.22 NVidia driver solves the problem, only issue is I CANNOT DOWNGRADE because my system is too new for it. The oldest driver I can install is 372.70 and it DOES NOT solve the problem. I need major help with this. I spent 3000 dollars on this computer and up to 1000 just replacing things. WHAT CAN I DO?

 

Please post an undated zip.
There have been other similar reports on the web.
Nvidia has direct support. Please post a link on their website and see what solutions they may have.

 

I have found something that may be the problem.
I have dug through my event viewer system logs, and every time I have gotten the "kernel power 41 task (63)" crash, it was immediately after the filter manager loaded two different filters. One being "npsvctrig," and the other being "FileCrypt."

Here are some screens:

Attachment 146669

The NPSVCTRIG Filter:
Attachment 146670

And the FILECRYPT Filter:
Attachment 146671

Bear in mind this has been consistent with every crash as far as I can see in the logs and I am confident this is some unsolved driver issue that no one seems to know the answer to. Yes, I have searched around online about these two filters and people are having identical problems to what I have been having.

This is definitely NOT a hardware issue.

Here is an updated zip:
Dropbox - JONAH-Tue_08_01_2017_162102_79.zip

 

There were no new bsod in the logs since 7/23/2017
Today there were several: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
These are some faulting applications in windows error reporting:
1) Uninstall MSI gaming
2) reinstall MSI gaming
3) if you can use other games instead of MSI gaming then keep MSI gaming uninstalled during the troubleshooting
4) In the left lower corner search type settings > privacy > on the left pane click background apps > turn off groove music
5) if you use groove music reboot then turn it back on otherwise keep it off during the troubleshooting
6) uninstall terraria
7) reinstall terraria
8) if you can use other game sites and not use terrari please keep it uninstalled during the troubleshooting


Code: 7/7/2017 7:15 AM Application Error Faulting application name: MsiGamingOSD_x64.exe, version: 1.0.0.5, time stamp: 0x5799965d Faulting module name: KERNELBASE.dll, version: 10.0.14393.1358, time stamp: 0x59327897 Exception code: 0xe0434352 Fault offset: 0x0000000000033c58 Faulting process id: 0x720 Faulting application start time: 0x01d2f6f0bee3a191 Faulting application path: C:\Program Files (x86)\MSI\Gaming APP\OSD\x64\MsiGamingOSD_x64.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: 3b2620a9-24f3-4d03-874b-61892ad27213 Faulting package full name: Faulting package-relative application ID:7/11/2017 7:08 AM Application Error Faulting application name: MsiGamingOSD_x64.exe, version: 1.0.0.5, time stamp: 0x5799965d Faulting module name: KERNELBASE.dll, version: 10.0.14393.1358, time stamp: 0x59327897 Exception code: 0xe0434352 Fault offset: 0x0000000000033c58 Faulting process id: 0x728 Faulting application start time: 0x01d2fa145e3857c8 Faulting application path: C:\Program Files (x86)\MSI\Gaming APP\OSD\x64\MsiGamingOSD_x64.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: 10849fcc-a43b-4932-82e4-cc7a54eb0993 Faulting package full name: Faulting package-relative application ID:7/26/2017 2:40 AM Application Error Faulting application name: MsiGamingOSD_x64.exe, version: 1.0.0.5, time stamp: 0x5799965d Faulting module name: KERNELBASE.dll, version: 10.0.14393.1378, time stamp: 0x594a146b Exception code: 0xe0434352 Fault offset: 0x0000000000033c58 Faulting process id: 0x718 Faulting application start time: 0x01d305b8800dfa38 Faulting application path: C:\Program Files (x86)\MSI\Gaming APP\OSD\x64\MsiGamingOSD_x64.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: 34bc1662-d396-4e7a-a6e0-b0f7525c94e2 Faulting package full name: Faulting package-relative application ID:7/30/2017 4:39 PM Application Error Faulting application name: MsiGamingOSD_x64.exe, version: 1.0.0.5, time stamp: 0x5799965d Faulting module name: KERNELBASE.dll, version: 10.0.14393.1378, time stamp: 0x594a146b Exception code: 0xe0434352 Fault offset: 0x0000000000033c58 Faulting process id: 0x72c Faulting application start time: 0x01d3095252059a07 Faulting application path: C:\Program Files (x86)\MSI\Gaming APP\OSD\x64\MsiGamingOSD_x64.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: d17b4e87-11a0-4826-a6d4-71193de2c394 Faulting package full name: Faulting package-relative application ID:7/11/2017 7:07 AM Application Error Faulting application name: MsiGamingOSD_x86.exe, version: 1.0.0.5, time stamp: 0x5799965d Faulting module name: KERNELBASE.dll, version: 10.0.14393.1358, time stamp: 0x59327ae2 Exception code: 0xe0434352 Fault offset: 0x000da9f2 Faulting process id: 0x76c Faulting application start time: 0x01d2fa145e39777d Faulting application path: C:\Program Files (x86)\MSI\Gaming APP\OSD\x86\MsiGamingOSD_x86.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: 25ebc296-7807-481d-b457-c949c992552b Faulting package full name: Faulting package-relative application ID:7/7/2017 7:15 AM Application Error Faulting application name: MsiGamingOSD_x86.exe, version: 1.0.0.5, time stamp: 0x5799965d Faulting module name: KERNELBASE.dll, version: 10.0.14393.1358, time stamp: 0x59327ae2 Exception code: 0xe0434352 Fault offset: 0x000da9f2 Faulting process id: 0x774 Faulting application start time: 0x01d2f6f0bee56fa2 Faulting application path: C:\Program Files (x86)\MSI\Gaming APP\OSD\x86\MsiGamingOSD_x86.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: 9f98e929-f3d6-4ba2-be3a-8a98f1fa60f1 Faulting package full name: Faulting package-relative application ID:7/26/2017 2:40 AM Application Error Faulting application name: MsiGamingOSD_x86.exe, version: 1.0.0.5, time stamp: 0x5799965d Faulting module name: KERNELBASE.dll, version: 10.0.14393.1378, time stamp: 0x594a13be Exception code: 0xe0434352 Fault offset: 0x000da9f2 Faulting process id: 0x778 Faulting application start time: 0x01d305b88011442f Faulting application path: C:\Program Files (x86)\MSI\Gaming APP\OSD\x86\MsiGamingOSD_x86.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: f33dd147-7201-4352-a698-a5971d056ea1 Faulting package full name: Faulting package-relative application ID:7/30/2017 4:39 PM Application Error Faulting application name: MsiGamingOSD_x86.exe, version: 1.0.0.5, time stamp: 0x5799965d Faulting module name: KERNELBASE.dll, version: 10.0.14393.1378, time stamp: 0x594a13be Exception code: 0xe0434352 Fault offset: 0x000da9f2 Faulting process id: 0x78c Faulting application start time: 0x01d309525207fc3a Faulting application path: C:\Program Files (x86)\MSI\Gaming APP\OSD\x86\MsiGamingOSD_x86.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: 27b03c3c-5d8a-4106-ae4f-7dca63821a55 Faulting package full name: Faulting package-relative application ID:[/quote] Code: 7/30/2017 4:51 PM Application Error Faulting application name: Music.UI.exe, version: 10.17062.1411.0, time stamp: 0x59708782 Faulting module name: Windows.UI.Xaml.dll, version: 10.0.14393.1378, time stamp: 0x594a17be Exception code: 0xc000027b Fault offset: 0x00000000006d6abb Faulting process id: 0x1ed8 Faulting application start time: 0x01d30953f9cb2a03 Faulting application path: C:\Program Files\WindowsApps\Microsoft.ZuneMusic_10.17062.14111.0_x64__8wekyb3d8bbwe\Music.UI.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: 1f9e1de2-df3c-4bf9-aa7b-94160e829f2c Faulting package full name: Microsoft.ZuneMusic_10.17062.14111.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: Microsoft.ZuneMusic[/quote]

Code: 7/27/2017 2:26 AM Application Error Faulting application name: Terraria.exe, version: 1.3.5.3, time stamp: 0x58ffb460 Faulting module name: KERNELBASE.dll, version: 10.0.14393.1378, time stamp: 0x594a13be Exception code: 0xe0434352 Fault offset: 0x000da9f2 Faulting process id: 0x1684 Faulting application start time: 0x01d3067fd143dc57 Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Terraria\Terraria.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: 52374cf5-336e-46a0-8ed4-93c388cad1c2 Faulting package full name: Faulting package-relative application ID:[/quote]

 

Can you tell that the applications are direct causes to the crashing?

 

What was the maximum temperature and duration of time during the GPU testing?
Please post an image of the Memtest86+ for 8 or more passes.
When these results are available we can use windows driver verifer to find misbehaving drivers

 

I believe it ran for a minute and the max temperature was 65 degrees Celsius.
Also, is the memtest completely necessary? I replaced my ram in attempt to solve the problem and it was to no avail. In addition to that I also UNDER-clocked my memory and that also did not fix the crashes.

 

Unfortunately new ram can be defective.
It is found by testing the memory.
A significant portion of the memory testing can be done while you are sleeping or away from the computer.
Plan to start running it in the evening or when you will be away from the computer for a day.

Are you able to test the GPU for longer than 1 minute? Can you run it for 30 minutes without temperature or image problems?
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials