Windows 10: Frequent and random appearing BSOD 'internal power error'.

1) Startup and recovery > system failure > un-check automatic restart
2) Ccleaner > un-check Memory dumps and Windows log files
3) Download and install Whocrashed > in the left upper corner above analyze click on tools > crash dump test > type: ACCEPThttp://www.resplendence.com/whocrashed
4) Click analyze > look for dead or deaddead in the results > post the results into the thread
5) Run the DM log collector after all of the above steps and post a zip into the thread:
BSOD - Posting Instructions - Windows 10 Forums

 

1) done
2) done
3) done
4) see:







5) see attached zip-file

 

Please indicate any problems that you are currently experiencing with the computer regarding: BSOD, crashes, freezes, display artifacts, temperature problems, etc.

The last spontaneous BSOD was on 12/13/2017 with bugcheck 18.


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.[/quote] Code: atikmdag atikmdag.sys Fri Feb 26 14:29:22 2016 (56D0B5A2) atikmpag atikmpag.sys Fri Feb 26 13:58:13 2016 (56D0AE55)[/quote]
Code: Name AMD Radeon HD 6700 SeriesPNP Device ID PCI\VEN_1002&DEV_68BA&SUBSYS_220C1458&REV_00\4&20898ED5&0&0010 Adapter Type AMD Radeon Graphics Processor (0x68BA), Advanced Micro Devices, Inc. compatible Adapter Description AMD Radeon HD 6700 Series Adapter RAM 1.00 GB (1,073,741,824 bytes) Installed Drivers aticfx64.dll,aticfx64.dll,aticfx64.dll,amdxc64.dll Driver Version 15.301.1901.0 INF File oem21.inf (ati2mtag_Evergreen section) Color Planes Not Available Color Table Entries 4294967296 Resolution 1920 x 1080 x 60 hertz Bits/Pixel 32 Memory Address 0xD0000000-0xDFFFFFFF Memory Address 0xFDFC0000-0xFDFDFFFF I/O Port 0x0000EE00-0x0000EEFF IRQ Channel IRQ 4294967294 I/O Port 0x000003B0-0x000003BB I/O Port 0x000003C0-0x000003DF Memory Address 0xA0000-0xBFFFF Driver c:\windows\system32\drivers\atikmpag.sys (8.14.1.6489, 668.13 KB (684,160 bytes), 27-Nov-17 20:08)[/quote]

Code: 09-Dec-17 21:45 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Niet beschikbaar Cab Id: 0 Problem signature: P1: 18 P2: 0 P3: ffffa002c9264240 P4: 2 P5: fffffffffffffffe P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\120917-14140-01.dmp \\?\C:\WINDOWS\TEMP\WER-21765-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B1E.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B1F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B40.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_18_668e7f5a55798dd0ae6dbeabcc2a9c4b7f849b1d_00000000_cab_19ec6dec Analysis symbol: Rechecking for solution: 0 Report Id: 118b28d9-ce4f-46b5-801d-5e5e0b59b66d Report Status: 2049 Hashed bucket:09-Dec-17 21:45 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Niet beschikbaar Cab Id: 0 Problem signature: P1: 18 P2: 0 P3: ffffa002c9264240 P4: 2 P5: fffffffffffffffe P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\120917-14140-01.dmp \\?\C:\WINDOWS\TEMP\WER-21765-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B1E.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B1F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B40.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_18_668e7f5a55798dd0ae6dbeabcc2a9c4b7f849b1d_00000000_02f86b3d Analysis symbol: Rechecking for solution: 0 Report Id: 118b28d9-ce4f-46b5-801d-5e5e0b59b66d Report Status: 4 Hashed bucket: 13-Dec-17 22:54 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Niet beschikbaar Cab Id: 0 Problem signature: P1: 18 P2: 0 P3: ffffd686feebb430 P4: 2 P5: ffffffffffffffff P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\121317-13968-01.dmp \\?\C:\WINDOWS\TEMP\WER-22078-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER76B6.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER76D5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7705.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_18_6ffc57f6c52cdb33ae7b5b0c3eefb33cef383d4_00000000_cab_1b48786c Analysis symbol: Rechecking for solution: 0 Report Id: bc1e88b0-86e8-4fe5-b79d-45c0587b8ce1 Report Status: 2049 Hashed bucket: 13-Dec-17 22:54 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Niet beschikbaar Cab Id: 0 Problem signature: P1: 18 P2: 0 P3: ffffd686feebb430 P4: 2 P5: ffffffffffffffff P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\121317-13968-01.dmp \\?\C:\WINDOWS\TEMP\WER-22078-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER76B6.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER76D5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7705.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_18_6ffc57f6c52cdb33ae7b5b0c3eefb33cef383d4_00000000_02ec7714 Analysis symbol: Rechecking for solution: 0 Report Id: bc1e88b0-86e8-4fe5-b79d-45c0587b8ce1 Report Status: 4 Hashed bucket: 15-Dec-17 13:06 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Niet beschikbaar Cab Id: 0 Problem signature: P1: deaddead P2: 0 P3: 0 P4: 19ae2fa8 P5: 3c2a58ed P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\121517-13859-01.dmp \\?\C:\WINDOWS\TEMP\WER-21375-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER63BB.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER63DA.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER63FA.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_deaddead_ad12b35b9139b918f562617cb8dc7211e23c09_00000000_cab_166864c4 Analysis symbol: Rechecking for solution: 0 Report Id: 73719b0f-7f0f-43cb-aa9c-d2a87bd31fd4 Report Status: 2049 Hashed bucket: 15-Dec-17 13:06 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Niet beschikbaar Cab Id: 0 Problem signature: P1: deaddead P2: 0 P3: 0 P4: 19ae2fa8 P5: 3c2a58ed P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\121517-13859-01.dmp \\?\C:\WINDOWS\TEMP\WER-21375-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER63BB.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER63DA.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER63FA.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_deaddead_ad12b35b9139b918f562617cb8dc7211e23c09_00000000_02f863f9 Analysis symbol: Rechecking for solution: 0 Report Id: 73719b0f-7f0f-43cb-aa9c-d2a87bd31fd4 Report Status: 4 Hashed bucket:[/quote]

 

Currently, I am (only) experiencing problems while playing Dungeons2 (my favorite game currently).
Mostly, when I am near the end of a level (with lot's of items and units in the game), the game freezes regularly. I get an error message which states that the game is not responding, and it gives me the option to either close the game or wait for it to respond. It may look like the screen sort of glitches as a whole, and then the game freezes.

I do not remember the game freezing at the beginning of a level.
I do not have problems with temperature.

In case of a BSOD, freeze or any other problem, I will update my post.

(I do not understand what you mean with "bugcheck 18". Should/can I do something with that information? *Nerd )

 

When there is a BSOD there is a bugcheck which displays a message and characters (numbers, letters, or numbers and letters).

Can you uninstall and reinstall the software?
The graphics driver may need to be uninstalled and re-installed again.
Can you find a friend, neighbor, relative, or local store to swap the video card?
If so test the video card in another computer and test another video card in the problematic computer and report results into the thread.

Create a brand new restore point.
Review the methods to turn off Windows driver verifier.
Make sure you have made a backup image using Macrium per the earlier post.
Run windows driver verifier for 48 hours.
Post a zip if there are any BSOD.
Use this link for the test settings:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Read this link for the methods to turn off windows driver verifier:
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

 

A brief update: 2 freezes during the game yesterday. See DM collector zip.

I will continue with your other instructions the next few days.

 

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.[/quote] 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.[/quote] 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.[/quote] 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.[/quote] 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.[/quote] 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.[/quote]

 

- 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:






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

 

here is de WhoCrashed analyze result:

Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.

On Mon 25-Dec-17 21:26:31 your computer crashed
crash dump file: C:\WINDOWS\Minidump\122517-13453-01.dmp
This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x19AFC246, 0x3C2A58ED)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\WINDOWS\system32\drivers\rspcrash64.sys
product: WhoCrashed
company: Resplendence Software Projects Sp.
description: Resplendence WhoCrashed Crash Dump Test
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel
debugger or the keyboard.This bug check belongs to the crash dump test that
you have performed with WhoCrashed or other software. It means that a crash dump
file was properly written out.

On Mon 25-Dec-17 21:26:31 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x19AFC246, 0x3C2A58ED)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\WINDOWS\system32\drivers\rspcrash64.sys
product: WhoCrashed
company: Resplendence Software Projects Sp.
description: Resplendence WhoCrashed Crash Dump Test
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel
debugger or the keyboard.This bug check belongs to the crash dump test that
you have performed with WhoCrashed or other software. It means that a crash dump
file was properly written out.
Conclusion2 crash dumps have been found and analyzed. No offending third party drivers have been found.
Connsider using WhoCrashed Professional which offers more detailed analysis
using symbol resolution. Also configuring your system to produce a full memory
dump may help you.

I continued with driver verifier with the new instructions:












I booted into windows normally.
These are the settings I am running now. I will repost when a BSOD happens.

 

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:



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:




Then it froze:




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)[/quote] Code: RTKVHD64 RTKVHD64.sys Tue Jun 19 03:50:56 2012 (4FE03D70)[/quote] Code: intcazaudaddservice Service for Realtek HD Audio (WDM) c:\windows\system32\drivers\rtkvhd64.sys Kernel Driver Yes Manual Running OK Normal No Yes[/quote]

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:[/quote]