Frequent and random appearing BSOD 'internal power error'.

Code:

Event[4562]:  Log Name: System  Source: Display  Date: 2017-12-16T00:10:19.304  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Antec  Description: Display driver amdkmdap stopped responding and has successfully recovered.

Code:

Event[3855]:  Log Name: System  Source: Display  Date: 2017-12-12T18:50:14.902  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Antec  Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[3856]:  Log Name: System  Source: Display  Date: 2017-12-12T18:55:48.746  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Antec  Description: Display driver amdkmdap stopped responding and has successfully recovered.

Code:

Event[3747]:  Log Name: System  Source: Display  Date: 2017-12-11T22:14:16.680  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Antec  Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[3748]:  Log Name: System  Source: Display  Date: 2017-12-11T23:24:21.917  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Antec  Description: Display driver amdkmdap stopped responding and has successfully recovered.

Code:

Event[3545]:  Log Name: System  Source: Display  Date: 2017-12-10T23:57:42.038  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Antec  Description: Display driver amdkmdap stopped responding and has successfully recovered.

Code:

Event[2829]:  Log Name: System  Source: Display  Date: 2017-12-09T00:27:53.541  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Antec  Description: Display driver amdkmdap stopped responding and has successfully recovered.

Code:

Event[2827]:  Log Name: System  Source: Display  Date: 2017-12-09T00:00:22.082  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Antec  Description: Display driver amdkmdap stopped responding and has successfully recovered.

- I reinstalled the graphics driver. The computer still freezes during my game.
- I am not able to test another graphics card in my PC.
- Today, I planned to use driver verifier for the next 48 hours. I created a new restore point. I turned on driver verifier, and rebooted my PC.
The PC crashed during booting, and also when rebooting again. Then win10 opened the recovery menu en I tried to disable verifier through command prompt. That didn't seem to work (again a crash during reboot), so I restored the PC to a previous restore point. That worked.

This is the BSOD I saw three times:
Attachment 169507
Attachment 169508
amdxata.sys

Then, I ran DM collector and attached the zip.

In this link are 3 methods to turn off windows driver verifier:


1) startup options > restart > select #6 safe mode with command prompt > type: verifier /reset
2) command prompt> Administrator X:\windows\system32\cmd.exe > type: verifier /bootmode resetonbootfail
3) system restore

The steps should be done in the order above and only move from one step to the next if there is failure.
Using step #3, system restore often leads to loss of the BSOD dump and little progress is made in the troubleshooting.

There was no dump in the zip.
See if you can use: verifier /bootmode resetonbootfail


See this link for additional information on turning off windows driver verifier:
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

OK, ran driver verifier again, and had some challenge to turn it off again. I repeatedly got a BSOD while booting. (Always amdxata.sys)

I did the following:
- I turned on driver verifier again according to: https://answers.microsoft.com/en-us/...3-c48669e4c983 as instructed in post #49
- I get a BSOD while booting (see images post #52). I restart the PC by pressing the reset button in de PC case. This happens twice
- Then windows boots into recovery menu.
- I follow method 1 in post #53. After entering "verifier /reset" I restart the PC by pressing the reset button. On reboot, I get a BSOD again.
- I press the reset button to restart the PC
- I follow method 2 in post #53. After entering "verifier /bootmode resetonbootfail" I type exit. The command prompt closes, but nothing happens further. I am looking at a black screen. So I consequently press the reset button on my PC.
(Question: How do I do a soft reboot after starting in command prompt?).
- The PC reboots, and I get a BSOD. I press the reset button. (I think this happens twice)
- The PC reboots, I get into the recovery menu and I follow method 1. After entering " verifier /reset", I press CTRL-ALT-DEL en select restart in the right-bottom corner.
- The PC reboots, and now continues to windows normally.

I run DM collector and attached the zip file.
I notice that no mini-dump files are present according to DM-collector.

The last dump and bugcheck were on 12/15/2017 with whocrashed testing.

The problems turning off windows driver verifier may be improved by reducing the number of tests.

Use this link for the test settings:
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

First perform a test dump with whocrashed:
above analyze click on tools > crash dump test > type: ACCEPT
click analyze > post results into the thread

From command prompt to reboot > type: shutdown /r
The same command can be enter with task manger: file > run new task > type: shutdown /r

After 24 hours if there are no bsod you can add one additional testing parameter (compare these two links for testing parameters):

Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Then continue to add 1 new testing parameter every 4 hours.
This may allow BSOD to appear with the testing and not lose them by having to perform system restore.

Since yesterday (late) evening, I was running these verifier settings:
Attachment 169733
The most recent addition was "force IRQLsetting".

PC was running OK yesterday evening and this morning. When I turned on the computer just now (approximately 13:45u), the screen froze during booting.

PC is booting:
Attachment 169734

Then it froze:
Attachment 169735

Computer did not respond to CTRL-ALT-DEL, so I pressed reset button.
Above happened twice, then the computer starts up in recovery options mode.
I choose "restart in safe mode with command prompt", and when in command prompt I entered "verifier /reset" and "shutdown /r".
The computer then booted normally.
I ran DM_collector and attached the zip.

I see 1 minidump file, with timestamp 10:45u(??). Please note that (I think around that same time) I switched the on/off button of the computer off and on again. I am not sure if the computer was running at that same time. Perhaps it is related.

The new misbehaving driver was a hardware driver.

Update: rtkvhd64.sys Realtek HD Audio

Updating a driver: Updating a driver. - Microsoft Community

Code:

Name    AMD High Definition Audio DeviceManufacturer    Advanced Micro DevicesStatus    OKPNP Device ID    HDAUDIO\FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100&REV_1002\5&263889D8&2&0001Driver    c:\windows\system32\drivers\atihdwt6.sys (10.0.0.1, 100.50 KB (102,912 bytes), 17-Dec-17 00:40)    Name    Realtek High Definition AudioManufacturer    RealtekStatus    OKPNP Device ID    HDAUDIO\FUNC_01&VEN_10EC&DEV_0885&SUBSYS_1458A102&REV_1001\4&26981C23&0&0001Driver    c:\windows\system32\drivers\rtkvhd64.sys (6.0.1.6662, 3.88 MB (4,065,296 bytes), 25-Dec-13 11:00)

Code:

RTKVHD64 RTKVHD64.sys Tue Jun 19 03:50:56 2012 (4FE03D70)

Code:

intcazaudaddservice    Service for Realtek HD Audio (WDM)    c:\windows\system32\drivers\rtkvhd64.sys    Kernel Driver    Yes    Manual    Running    OK    Normal    No    Yes

RTKVHD64.sys

Realtek High Definition Audio Function Driver

http://www.realtek.com.tw/downloads/...Level=3&Conn=2

Code:

Event[145]:  Log Name: System
  Source: Service Control Manager
  Date: 2017-11-25T14:13:21.814
  Event ID: 7045
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Antec
  Description: 
A service was installed in the system.


Service Name:  Service for Realtek HD Audio (WDM)
Service File Name:  \SystemRoot\system32\drivers\RTKVHD64.sys
Service Type:  stuurprogramma voor kernelmodus
Service Start Type:  starten op aanvraag
Service Account:

Great, thanks!

I downloaded new drivers from the Realtek site.
According to the instruction; I uninstalled the old driver through device manager, and then installed the new drivers.
The file RTKVHD64.sys now has a creation date of today.

I assume I should wait and see if the problem is gone now the coming days, before going further with windows verifier.