Stop Code: INTERNAL POWER ERROR

I started getting this BSOD occasionally a day or two ago. It only happens when the PC goes to sleep. The PC works fine on restart.
Attachment 245941

Hi Involute,

Welcome to TF's BSOD forum.

For all tests / steps please post images into the thread.
For any problems posting images please use share links (one drive, drop box, google drive, or amazon)

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) bcdedit /enum {badmemory}

10) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

11) Make sure that there is no over clocking while troubleshooting.

12) The BIOS: Version/Date American Megatrends Inc. 1401, 11/9/2016
Upgrade the BIOS to the most up to date non-beta BIOS: 1401 > 1802
X99-DELUXE II Driver & Tools | Motherboards | ASUS USA

13) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

14) Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan


15) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools for Windows |
Seagate
How to use SeaTools for Windows | Seagate Support US

16) Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot


17) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10


18) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

Code:

Event[1548]:
  Log Name: System
  Source: disk
  Date: 2019-09-05T09:51:34.985
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Karls-Desktop
  Description: 
The device, \Device\Harddisk1\DR1, has a bad block.

I already posted the V2 log collector output. Is this just a generic autoreply, or the result of the output? It’s a lot of work. I’m happy to do it if it’s called for, but if the log output hasn’t been analyzed yet, and may point to some other solution, I’d prefer to wait.

The data needed for troubleshooting are in the files.

Each BSOD creates new files.

Windows can deleted needed files.

For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

So there’s no point in performing the 18 steps until the next BSOD? And there’s nothing Ten Forums can tell me until then?

Each of the steps / tests should be performed to document the findings.

zbook said:

Each of the steps / tests should be performed to document the findings.

I’m sorry, Zbook, but I’m still confused. If, as you say, “Windows can deleted needed files,” what’s the point of performing all the steps now, long after the last BSOD? If you always need these steps performed, why not list them with the sticky instructions at the top of the forum asking for the V2 log collector to be run?

- - - Updated - - -

Thanks, krzemien. I’ll update my driver and see if that fixes it, though I’m on whatever came after 1803 (1905? I’m not at my PC at the moment).

To work up the problems with the computer there are steps and tests that need to be performed.

These are diagnostic tests.

All tests have false positives and false negatives.

The purpose of the tests are to find the cause.

The cause can be misbehaving drivers, problems in the BIOS, malfunctioning hardware, etc.

Zbook:

Perhaps because you deal with so many users you are confusing me with someone else, because you repeatedly fail to answer my question. I can’t tell if you are asking me to perform the steps now (even though I’ve restarted my machine two or three times since the last BSOD and, according to you, Windows may have destroyed relevant files) or I should wait until the next BSOD to perform them.