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

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.

 

Please continue testing all drivers with windows driver verifier.
If there are no longer any BSOD with the current test settings please increase the testing parameters per the earlier post.

 

I continued with testing, and got a BSOD today. This happened right after adding a new parameter.

This was the actual parameter list. "DMA checking" was the latest addition.




After adding DMA checking, I restarted the PC.
Windows booted normally, and I entered my password at the logon screen.
Windows continued and about 5 seconds later, the BSOD appeared. (I forgot the error code.)

I rebooted and got into windows normally. I reset verifier and rebooted again. Then I ran DM_collector.
Attached is the new ZIP.

 

The misbehaving drivers were the AMD graphics drivers:
atikmpag.sys
atikmdag.sys

It will be trial and error to find a stable driver.
Please make note of each driver model/date as you try them.

Uninstall using DDU
Check the box for "clean install"
Install only the graphics driver.
Official Display Driver Uninstaller DDU Download
Display Driver Uninstaller: How to use - Windows 7 Help Forums
AMD Graphics Drivers - Install Without Catalyst Install Manager - Windows 7 Help Forums
Download Drivers

Previous


Code: atikmdag atikmdag.sys Wed Nov 4 15:39:32 2015 (563A7B14) atikmpag atikmpag.sys Wed Nov 4 15:16:43 2015 (563A75BB)[/quote] Code: Name AMD Radeon HD 6700 Series PNP 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.201.1151.1008 INF File oem26.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.6463, 658.48 KB (674,288 bytes), 17-Dec-17 00:40)[/quote] Code: amdkmdag amdkmdag amdkmdag Kernel Manual Running OK TRUE FALSE 11,354,112 8,728,576 0 04-Nov-15 22:39:32 C:\WINDOWS\system32\DRIVERS\atikmdag.sys 8,192 amdkmdap amdkmdap amdkmdap Kernel Manual Running OK TRUE FALSE 8,192 376,832 0 04-Nov-15 22:16:43 C:\WINDOWS\system32\DRIVERS\atikmpag.sys 4,096[/quote]

 

Thanks for your instructions.
I have tried a number of drivers in the AMD list, but windows refuses to install most of them.
I was only able to install 3 drivers:

To be precise:

tested drivers:
amd-catalyst-15.7.1-win10-64bit ---> tested, games "dungeons2" and "dungeons3" freezes occasionally (current installed drivers)
amd non-whql-win10-64bit-radeon-software-crimson-relive-16.2.1-sep20 --> tested, games "dungeons2" and "dungeons3" freezes occasionally
amd whql-win10-64bit-radeon-software-crimson-16.10.1-oct13 ---> tested for a very short time. Driver could not do 1920 x 1200 resolution (max was 1600x1200), so no real option.

win10 refused to install the drivers below:
amd Catalyst Software Suite 13.9_win7_win8_32_dd_ccc_whql
amd whql-64bit-radeon-software-crimson-16.1.1-win10-win8.1-win7-feb12
amd radeon-crimson-16.6.2-with-dotnet45-win7-32bit
Gigabyte vga_driver_amd_vista(win7)_8.82

With 15.7.1 installed (conform above instruction), I continued with driver verifier.
I just switched to these settings below (I added the lowest checkmark), when I got a BSOD right after rebooting:




I turned verifier off (after a reboot)
Then rebooted again, ran DM-Collecter and attached the zip.

If you don't conclude something else, I assume it simply is the videocard being (too) old in combination with old drivers for windows 10 and new games. The result is then compatibility issues that may arise in some (newer) games....(?)

 

So far the graphics card driver was not found in the latest BSOD mini dump.
There was 1 BSOD mini dump file with bugcheck A.
Debugging this file displayed 1 new misbehaving software driver: FSgk.sys
Uninstall this software (see if they have an uninstall tool so that the AV product is removed from the registry)

With the ongoing troubleshooting with AMD graphics it would be best to use Windows defender during the troubleshooting process.
If the VPN feature is needed see if you can find an alternative product or wait 2 weeks to have a stable computer environment before reinstalling the software.

Code: f-secure gatekeeper F-Secure Gatekeeper \??\c:\program files (x86)\safe online\apps\computersecurity\anti-virus\minifilter\fsgk.sys Kernel Driver Yes Manual Running OK Ignore No Yes[/quote] fsgk.sys F-Secure Gatekeeper F-Secure | Cyber Security Solutions for your Home and Business
Database Updates | F-Secure Labs
F-Secure Help Center

 

OK. I installed the anti-virus software yesterday, but removed it now. I used the normal uninstall option in "windows settings - apps".
I will continue with verifier now.

---

 

I bought a new graphics card (MSI Geforce GTX 770) yesterday, and installed it with the newest drivers from Nvidia.
(390.65-desktop-win10-64bit-international-whql, jan 2018)

After succesfull installation, I turned on Verifier and got a BSOD during booting with the error message "Driver verifier iomanager violation"

The DM log file is attached.

Could you advise in the next step?

 

How is the new graphics car performing?

There was 1 BSOD mini dump file.
The debugging displayed: ctxusbm.sys Citrix ICA Client USB Monitor Driver
Updating a driver: Updating a driver. - Microsoft Community

After the driver is fixed or for any other computer problems run this version of the log collector and post a zip into the thread:
log collector v2-beta06.zip



Code: ctxusbm Citrix USB Monitor Driver c:\windows\system32\drivers\ctxusbm.sys Kernel Driver Yes System Running OK Normal No Yes[/quote]
ctxusbm.sys Citrix ICA Client USB Monitor Driver Downloads

 

The new graphics card is way faster than the old one.

3Dmark test with old card:




new card:




I notice that my 'dungeons3' game is running more smoothly now. *Biggrin
(But the game froze once when I exit the game back to desktop...)

I use Citrix Receiver to work from home to acces my corporate account and workplace. It is a web-based application (as far as I now).
I had this version installed and I uninstalled it:




I downloaded the newest version with the link provided (see below), but did not install it yet. I will do so later, as soon as I need it.




I hope this is OK and it fixes the Citrix USB driver that was malfunctioning.
I did not expect Citrix to have need for a USB driver, and I cannot link Citrix to any hardware installed on my PC. But I must admit, I also didn't search for it in device manager.

I ran the new log collector. See attached.
If I need to do it differently, please advise.

 

The mini and memory dumps have disappeared.

Open system control panel > advanced system settings > startup and recovery > settings > post an image into the thread.
In system properties advanced tab under performance > click on settings > on performance options click on the advanced tab > under virtual memory click on change > post an image of the virtual memory windows into the thread

Open Ccleaner > windows tab > scroll down > post an image into the thread.

In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread.

 

Note: I did not have a new BSOD since post #67.
I was under the impression the (old) DM_log_collector deletes logs that it has already collected.

Anyhow, here are the requested screenshots:

 

With my new graphics card, I did not have any issues, BSOD or freezes while using my computer.
Then, after a week I started with verifier again. When I used the settings below, I got a BSOD during booting.




I added the bottom 3 checkboxes in the last step.

After disabling verifier, I tried to run the "new" collector you provided, but it does not seem to work correctly. I clicked on the shortcut, and I briefly see a command prompt window opening up with some tekst, but then it is gone. Am I doing something wrong?

Then I ran DM_Collector (see attached), but there is no dump file. I do not know why the dump file is missing.

Since I have nog BSOD when I use my computer normally, or is it safe to say I am "bug free" now?

 

The last BSOD was on 1/13.
The last unexpected reboot was on 1/18.
For windows driver verifier testing please uncheck DDI compliance checking (additional)
If there is a crash the window for the BSOD should remain open since there is no automatically restart.
Is should display a bugcheck. Sometimes it may display a misbehaving driver in the form *.sys
If there is a BSOD record this information and post it into the thread.
The image for the windows driver verifier was cut off. Please make sure that randomized low resource stimulation is unchecked
The beta log collector is in testing. Some computers may have a flash of the administrative command prompt box and no run of the collector. It may take some time to iron out the quirks but when it works it has additional useful information.
The log collectors should not delete files.
The windows disk cleanup and Ccleaner are the most common causes of lost dump files.

 

Again, a BSOD during booting, just after I turned on verifier with these settings:





I just added the "code integrity checks". The others were already activated.

I took a photo of the monitor before pressing the reset button:






Driver verifier detected violation
AMDXATA.SYS

And then I ran DM collector. No minidump file present *Sad