Kernel 41 crashes, PC hangs at playing games, CPU Vcore huge fluctuation (HWMonitor)

tsarkyyy

Commendable
Mar 29, 2018
9
0
1,510
CPU : I5-7500 3,4 Ghz
GPU : Asus ROG RX 470
PSU : EVGA 500B
MB : MSI H270 GAMING M3

I reinstalled my computer, still having same sympthoms playing games like Warframe.

My temperatures should be fine, well under the threshold.

On OCCT, i'm getting weird fluctations on voltages
https://imgur.com/erFmoPH
Hard to tell, but (VIN8) spikes between 0,7 - 1,08V

I'm currently in a process of RMA'ing my PSU and exclude it out of the equation.
My computer is only a year old, i need help fixing this.

If u need more diagnostics / reports, let me know.

Update : After posting this on a different thread that has exact same issues,
I did use HWMonitor and getting same results
CPU Vcore : Min. 0.688V - Max. 1.096V

See : https://imgur.com/6cpeJ3S

On PSU Tier List,
I found my EVGA 500W in Tier 3
Some Haswell compatible, some not (maybe unconfirmed). Still safe to use and stable, just lower quality components.
Not really ideal in serious overclocking or super-high load situations,
such as a Bitcoin mining rig or a high end gaming system.
My rig is not really high-end but videocard suppose to run most game with 60fps @1080p
I'm just worried that my PSU is my culprit and trying to find any1 who could help
me walk through all of this and fix the issues together.
 
Solution
The bug check error 0x00000116 refers to corrupted drivers or an issue with graphics device and that appears to be the issue with your computer.
The GPU might be busy processing something (a game, 3D render, etc...) and it stop refreshing the screen. The OS will wait (a set time) to refresh the GPU, the system instruct the driver not to access the hardware or memory and if the GPU cannot be refreshed within the set time then you get the BSOD.
So, disable any overclocking on the system, GPU or GPU software.
Check that all power connections are firmly in place and that the GPU is fully inserted and secured.
Also check that no foreign materials are laying or touching the video card.
Many thins could cause this, like defective memory...
Hi there,
Your vcore voltages are OK since it will fluctuate depending on CPU load. It will stay down to save power and it will spike depending on CPU usage.
I don't see the GPU voltages but everything on that image looks normal.
Just keep an eye on the +12 voltage, which should not go below 11.4V or above 12.6V.
The same apply to the +5V, it should be between 4.750V and 5.250V.
I don't see anything wrong on that PSU. But you should check when the system is at max load to see if the PSU can handle it.
 

tsarkyyy

Commendable
Mar 29, 2018
9
0
1,510
I'll share GPU voltages as soon as I get home (GMT +1)
And I'll try and play Warframe windowed with HWMonitor beside it to keep an eye on the voltage readings.
Maybe it will still hang, maybe it won't. Haven't tried to play it windowed.
Maybe there will be a difference, that it just hangs and screen will not turn dark.

Then I'll stress test with Prime95, first time i'll be using it.
Will use Blend Mode throughout the evening and see if it comes with any results.

Will it help if i send some dumpfiles for some more troubleshooting?

I really was hoping that CPU Vcore was the cause.
I have no experience when it comes to reading voltages and to see what is wrong with it.

 
The dumpfiles help, if you have any critical errors present in the 'Event Viewer'.

Open 'Event Viewer'
On the left, expand 'Custom Views', and click 'Administrative Events'
First, don’t freak out, since the most stable systems have hundres ( sometimes thousands) of errors and warnings.
Look for 'critical' errors and if found look for 'Log Name', 'Source' and 'Event ID'
 

tsarkyyy

Commendable
Mar 29, 2018
9
0
1,510
All I see is alot of warnings about "Source : FilterManager - ID 4"
Some criticals about Skype "Source : AppModel-Runtime - ID 79 and 80"
And a bit more errors in "Source : DistributedCOM - ID 10016"

Just 1 error in "Source : Kernel-EventTracing - ID 2"

I did recently installed windows, so i lost all my log files before i reinstalled.
Did a complete format on recovery partitions as well as all the other partitions
After reinstall and playing Warframe in fullscreen, it immediatly replicated the crash/hang of computer, but only happend once, as of yet.

I do have logs uploaded on a different forum before reinstall using their tools.
See : https://www.bleepingcomputer.com/forums/index.php?app=core&module=attach&section=attach&attach_id=203411
Maybe that is of any use to you or otherwise obsolete since these logs are from 28th of March

No new dumpfiles has been created yet. After posting this i'll try and recreate the crash again. And see if Windows create some dumpfiles. Since this been happening, it has been consistent though.

Here are some reports of HWMonitor

GPU Voltages Idle : https://imgur.com/VHXq2A8
All voltages and temperatures (except HDD) after playing Warframe : https://imgur.com/eoMoRCN

I find it weird that it does not read GPU Voltages.
 

tsarkyyy

Commendable
Mar 29, 2018
9
0
1,510
I can split it in 2 if thats ok. Cannot get all data on 1 screenshot.

This is while playing Warframe fullscreen for a few mins.

https://imgur.com/n7sY2q0
https://imgur.com/YfoLkBb

Meanwhile, i did get a crash and dumpfile. Used WhoCrashed to read it

On Thu 5-4-2018 18:51:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: atikmpag.sys (0xFFFFF805653EF7E8)
Bugcheck code: 0x116 (0xFFFFD28BA58B7010, 0xFFFFF805653EF7E8, 0xFFFFFFFFC0000001, 0x3)
Error: VIDEO_TDR_ERROR
file path: C:\WINDOWS\System32\DriverStore\FileRepository\c0323831.inf_amd64_1212be4b9fe2386c\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR
 
It could be corrupted drivers.
Also a failing disc or a disc with bad sectors could be the culprit.

Lets do a clean display drivers setup.
- Download the latest drivers for your GPU fromAMD
- Download DDU
- Click Window + R type Msconfig, select the Boot tab the select 'Safe boot' under Boot Options, click OK the Apply and finally reboot.
- Run DDU, select: AMD Software and drivers then select: Clean, do not restart.
- Click Window + R type Msconfig, select the Boot tab the uncheck 'Safe boot' under Boot Options, click OK the Apply and finally reboot.
- Windows reboots on normal mode.
- Install the previously downloaded AMD drivers, select: Custom Install, uncheck everything except the AMD display drivers
-Finish the installation and reboot.
 

tsarkyyy

Commendable
Mar 29, 2018
9
0
1,510
I followed your instructions by the letter and it didn't work.
Getting the same error :

On Fri 6-4-2018 22:45:07 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040618-22171-01.dmp
This was probably caused by the following module: atikmpag.sys (0xFFFFF80C1F15F818)
Bugcheck code: 0x116 (0xFFFF9600A0D9C4A0, 0xFFFFF80C1F15F818, 0xFFFFFFFFC0000001, 0x3)
Error: VIDEO_TDR_ERROR
file path: C:\WINDOWS\System32\DriverStore\FileRepository\c0326037.inf_amd64_6cad8aeb5717c52d\B326079\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR

Also these are the eventvwr logs that im worried about when crash happens.
This is consistent as well.

Type Date Time Event Source Category

Error 6-4-2018 22:47:18 1001 BugCheck None
De computer is opnieuw opgestart na een bugcontrole. De bugcontrole is 0x00000116 (0xffff9600a0d9c4a0, 0xfffff80c1f15f818, 0xffffffffc0000001, 0x0000000000000003). Er is een dump opgeslagen in: C:\WINDOWS\MEMORY.DMP. Rapport-id: 5121b9a5-c3bd-4e40-8fbc-6fd4cd2cdfce.
Information 6-4-2018 22:46:54 7001 Microsoft-Windows-Winlogon (1101)
Melding van gebruikersafmelding voor het Programma voor verbetering van klantervaringen
Information 6-4-2018 22:46:41 7026 Service Control Manager None
De volgende opstart- of systeemstartstuurprogramma's zijn niet geladen:
dam
Information 6-4-2018 22:46:39 12 Microsoft-Windows-UserModePowerService (10)
Proces C:\Windows\System32\DriverStore\FileRepository\c0326037.inf_amd64_6cad8aeb5717c52d\B326079\atieclxx.exe (proces-id:1736) beleidsschema terugzetten van {381B4222-F694-41F0-9685-FF5BB260DF2E} naar {381B4222-F694-41F0-9685-FF5BB260DF2E}
Information 6-4-2018 22:46:39 51046 Microsoft-Windows-DHCPv6-Client Gebeurtenis servicestatus
DHCPv6-clientservice is gestart
Information 6-4-2018 22:46:39 50103 Microsoft-Windows-Dhcp-Client Gebeurtenis servicestatus
DHCPv4-client geregistreerd voor afsluitmelding
Information 6-4-2018 22:46:39 50036 Microsoft-Windows-Dhcp-Client Gebeurtenis servicestatus
DHCPv4-clientservice is gestart
Information 6-4-2018 22:46:38 6 Microsoft-Windows-FilterManager None
Bestandssysteemfilter 'storqosflt' (10.0, 2005-04-24T11:53:05.000000000Z) is geladen en bij Filterbeheer geregistreerd.
Information 6-4-2018 22:46:38 6 Microsoft-Windows-FilterManager None
Bestandssysteemfilter 'CldFlt' (10.0, 2071-09-04T03:26:16.000000000Z) is geladen en bij Filterbeheer geregistreerd.
Information 6-4-2018 22:46:38 6 Microsoft-Windows-FilterManager None
Bestandssysteemfilter 'wcifs' (10.0, 2006-08-05T15:52:50.000000000Z) is geladen en bij Filterbeheer geregistreerd.
Information 6-4-2018 22:46:38 6 Microsoft-Windows-FilterManager None
Bestandssysteemfilter 'luafv' (10.0, 1971-04-04T16:11:08.000000000Z) is geladen en bij Filterbeheer geregistreerd.
Information 6-4-2018 22:46:37 16962 Microsoft-Windows-Directory-Services-SAM None
Externe aanroepen naar de SAM-database worden beperkt met de standaard security descriptor: O:SYG:SYD:(A;;RC;;;BA).
Zie http://go.microsoft.com/fwlink/?LinkId=787651 voor meer informatie.
Information 6-4-2018 22:46:37 14 Microsoft-Windows-Wininit None
Configuratie van Credential Guard (LsaIso.exe): 0, 0
Information 6-4-2018 22:46:31 98 Microsoft-Windows-Ntfs None
*The description for Event ID ( 98 ) in Source ( Microsoft-Windows-Ntfs ) could not be found.
Either the component that raises this event is not installed on the computer or the installation is corrupted.You can install or repair the component or try to change Description Server.

The following information was included with the event (insertion strings):
\\?\Volume{1720d097-3602-42e8-8d25-43ad3aba91bd}
\Device\HarddiskVolume1
0
Information 6-4-2018 22:46:21 2 MEIx64 None
Intel(R) Management Engine Interface driver has started successfully.
Information 6-4-2018 22:46:20 55 Microsoft-Windows-Kernel-Processor-Power (47)
De logische Hyper-V-processor 3 biedt de volgende energiebeheermogelijkheden:
Type niet-actieve status: 1 (2 status(sen))
Type prestatiestatus: 3
Nominale frequentie (MHz): 3408
Maximumpercentage voor prestaties: 750
Minimumpercentage voor prestaties: 26
Minimumversnellingspercentage: 2
Information 6-4-2018 22:46:20 55 Microsoft-Windows-Kernel-Processor-Power (47)
De logische Hyper-V-processor 2 biedt de volgende energiebeheermogelijkheden:
Type niet-actieve status: 1 (2 status(sen))
Type prestatiestatus: 3
Nominale frequentie (MHz): 3408
Maximumpercentage voor prestaties: 750
Minimumpercentage voor prestaties: 26
Minimumversnellingspercentage: 2
Information 6-4-2018 22:46:20 55 Microsoft-Windows-Kernel-Processor-Power (47)
De logische Hyper-V-processor 1 biedt de volgende energiebeheermogelijkheden:
Type niet-actieve status: 1 (2 status(sen))
Type prestatiestatus: 3
Nominale frequentie (MHz): 3408
Maximumpercentage voor prestaties: 750
Minimumpercentage voor prestaties: 26
Minimumversnellingspercentage: 2
Information 6-4-2018 22:46:20 55 Microsoft-Windows-Kernel-Processor-Power (47)
De logische Hyper-V-processor 0 biedt de volgende energiebeheermogelijkheden:
Type niet-actieve status: 1 (2 status(sen))
Type prestatiestatus: 3
Nominale frequentie (MHz): 3408
Maximumpercentage voor prestaties: 750
Minimumpercentage voor prestaties: 23
Minimumversnellingspercentage: 2
Information 6-4-2018 22:46:20 98 Microsoft-Windows-Ntfs None
*The description for Event ID ( 98 ) in Source ( Microsoft-Windows-Ntfs ) could not be found.
Either the component that raises this event is not installed on the computer or the installation is corrupted.You can install or repair the component or try to change Description Server.

The following information was included with the event (insertion strings):
D:
\Device\HarddiskVolume5
0
Information 6-4-2018 22:46:18 172 Microsoft-Windows-Kernel-Power (203)
*The description for Event ID ( 172 ) in Source ( Microsoft-Windows-Kernel-Power ) could not be found.
Either the component that raises this event is not installed on the computer or the installation is corrupted.You can install or repair the component or try to change Description Server.

The following information was included with the event (insertion strings):
2
6
Information 6-4-2018 22:46:18 41 Microsoft-Windows-Kernel-Power (63)
*The description for Event ID ( 41 ) in Source ( Microsoft-Windows-Kernel-Power ) could not be found.
Either the component that raises this event is not installed on the computer or the installation is corrupted.You can install or repair the component or try to change Description Server.

The following information was included with the event (insertion strings):
278
0xffff9600a0d9c4a0
0xfffff80c1f15f818
0xffffffffc0000001
0x3
0
0
0
0
false
0
0
true
0
Information 6-4-2018 22:46:18 6 Microsoft-Windows-FilterManager None
Bestandssysteemfilter 'npsvctrig' (10.0, 2070-05-05T16:38:28.000000000Z) is geladen en bij Filterbeheer geregistreerd.
Information 6-4-2018 22:46:18 6 Microsoft-Windows-FilterManager None
Bestandssysteemfilter 'FileCrypt' (10.0, 2013-05-08T14:49:03.000000000Z) is geladen en bij Filterbeheer geregistreerd.
Information 6-4-2018 22:46:18 98 Microsoft-Windows-Ntfs None
*The description for Event ID ( 98 ) in Source ( Microsoft-Windows-Ntfs ) could not be found.
Either the component that raises this event is not installed on the computer or the installation is corrupted.You can install or repair the component or try to change Description Server.

The following information was included with the event (insertion strings):
C:
\Device\HarddiskVolume4
0
Information 6-4-2018 22:46:16 6 Microsoft-Windows-FilterManager None
Bestandssysteemfilter 'WdFilter' (10.0, 2008-01-30T19:51:28.000000000Z) is geladen en bij Filterbeheer geregistreerd.
Information 6-4-2018 22:46:16 6 Microsoft-Windows-FilterManager None
Bestandssysteemfilter 'Wof' (10.0, 2102-10-28T01:46:39.000000000Z) is geladen en bij Filterbeheer geregistreerd.
Information 6-4-2018 22:46:16 6 Microsoft-Windows-FilterManager None
Bestandssysteemfilter 'FileInfo' (10.0, 1983-09-10T10:46:43.000000000Z) is geladen en bij Filterbeheer geregistreerd.
Information 6-4-2018 22:46:39 6013 EventLog None
Het systeem is 23 seconden in gebruik.
Information 6-4-2018 22:46:39 6005 EventLog None
De Event Log-service is gestart.
Information 6-4-2018 22:46:39 6009 EventLog None
Microsoft (R) Windows (R) 10.00. 16299 ? Multiprocessor Free.
Error 6-4-2018 22:46:39 6008 EventLog None
De vorige afsluiting van het systeem om 22:37:28 op ?6-?4-?2018 is onverwacht gebeurd.
Information 6-4-2018 22:46:15 30 Microsoft-Windows-Kernel-Boot (21)
*The description for Event ID ( 30 ) in Source ( Microsoft-Windows-Kernel-Boot ) could not be found.
Either the component that raises this event is not installed on the computer or the installation is corrupted.You can install or repair the component or try to change Description Server.

The following information was included with the event (insertion strings):
0
8969
8993
10874
10876
Information 6-4-2018 22:46:15 25 Microsoft-Windows-Kernel-Boot (32)
*The description for Event ID ( 25 ) in Source ( Microsoft-Windows-Kernel-Boot ) could not be found.
Either the component that raises this event is not installed on the computer or the installation is corrupted.You can install or repair the component or try to change Description Server.

The following information was included with the event (insertion strings):
1
Information 6-4-2018 22:46:15 27 Microsoft-Windows-Kernel-Boot (33)
*The description for Event ID ( 27 ) in Source ( Microsoft-Windows-Kernel-Boot ) could not be found.
Either the component that raises this event is not installed on the computer or the installation is corrupted.You can install or repair the component or try to change Description Server.

The following information was included with the event (insertion strings):
0
NOEXECUTE=OPTIN
Information 6-4-2018 22:46:15 20 Microsoft-Windows-Kernel-Boot (31)
*The description for Event ID ( 20 ) in Source ( Microsoft-Windows-Kernel-Boot ) could not be found.
Either the component that raises this event is not installed on the computer or the installation is corrupted.You can install or repair the component or try to change Description Server.

The following information was included with the event (insertion strings):
false
false
11
2
Information 6-4-2018 22:46:15 32 Microsoft-Windows-Kernel-Boot (58)
The Scenario Event Mapper started a scenario for provider 0 (event ID (null)) with (null) context providers. The context logger dropped event count was (null).
Information 6-4-2018 22:46:15 18 Microsoft-Windows-Kernel-Boot (57)
Succeeded to fix state locations for package 1.
Information 6-4-2018 22:46:15 153 Microsoft-Windows-Kernel-Boot (62)
*The description for Event ID ( 153 ) in Source ( Microsoft-Windows-Kernel-Boot ) could not be found.
Either the component that raises this event is not installed on the computer or the installation is corrupted.You can install or repair the component or try to change Description Server.

The following information was included with the event (insertion strings):
0
0
0
Information 6-4-2018 22:46:15 12 Microsoft-Windows-Kernel-General Mogelijke detectie van CVE: %1
Aanvullende informatie: %2

deze gebeurtenis w
Het besturingssysteem is gestart op systeemtijd 2018-04-06T20:46:15.497979400Z.

Especially :
Type : Information
Date : 6-4-2018
Time : 22:46:18
Event : 41
Source : Microsoft-Windows-Kernel-Power
Category : (63)
User : \SYSTEM

Description:
*The description for Event ID ( 41 ) in Source ( Microsoft-Windows-Kernel-Power ) could not be found.
Either the component that raises this event is not installed on the computer or the installation is corrupted.You can install or repair the component or try to change Description Server.

The following information was included with the event (insertion strings):
278
0xffff9600a0d9c4a0
0xfffff80c1f15f818
0xffffffffc0000001
0x3
0
0
0
0
false
0
0
true
0

If u want this in different format like html or the actual event log file, let me know.
 
The bug check error 0x00000116 refers to corrupted drivers or an issue with graphics device and that appears to be the issue with your computer.
The GPU might be busy processing something (a game, 3D render, etc...) and it stop refreshing the screen. The OS will wait (a set time) to refresh the GPU, the system instruct the driver not to access the hardware or memory and if the GPU cannot be refreshed within the set time then you get the BSOD.
So, disable any overclocking on the system, GPU or GPU software.
Check that all power connections are firmly in place and that the GPU is fully inserted and secured.
Also check that no foreign materials are laying or touching the video card.
Many thins could cause this, like defective memory modules and motherboards, programs running in the background, memory configuration and timings, GPU overheating,

Open COMMAND Prompt as Admin and copy or type 'sfc /scannow' and hit enter.
Also, updating drivers (video, sound, network, etc) from your manufacturer could fix the issue.

The critical error 41 just means that the PC has rebooted or lost power without cleanly shutting down first.


 
Solution

tsarkyyy

Commendable
Mar 29, 2018
9
0
1,510
Can't believe it.. we finally fix it!!! THANK YOU! :D

The problem might have been GPU not seated properly. I removed it and put it back in.
Also some cables were hanging loose that i don't use, i secured those cables with some zip-ties.
PSU is not modular, so i secured them more properly and some chassis cables that i have no idea what to use them for (maybe u can explain those, case is a Corsair 100R Silent)

It's crazy that such a simple oversight can bring such problems.

I was playing Warframe for at least 2 hours, so i have faith that the problem is solved!
Other games like 7 Days to Die works just fine, been playing that at least 6 hours this weekend ^^"

If problem returns i'll come back and make a new thread and might refer this thread for further troubleshooting.

I can't thank you enough for your insight and expertise to get me through this.
You saved me from €30,- inspection costs and any further costs
You also saved me from returning this PSU with "Advanced RMA"
They charged me with "collateral charge fee" of €50,-! That is not what i am used to using warranty...

In short, you saved me alot of wasted money and/or hassle. I thank you!

 
I am glad I was able to help and that you are able to enjoy using your system.
You are right! Little things, could cause havoc in a PC, even as simple as specks of dusts lying on top of the motherboard.

The Corsair 100R is a pretty slick case. It comes with a couple of fans which can be controlled from the fan switch on the back. So besides the fan connections (front & back) it also have have a fan speed switch cable.
Also there are several cables coming from the front panel: USB 3.0 ports , HDaudio, power button, reset button, HDD LED, power LED+ and power LED-.