Stop Code: INTERNAL POWER ERROR

krzemien · 06 Sep 2019

Involute said:

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).

I'm fairly confident that this will be the culprit - the thread I linked to clearly indicates that's the case and I have not-so-distant memories of this issue from earlier this year.

But of course I can be mistaken!

zbook · 06 Sep 2019

1) When available please post the results for steps / tests in post #2.

2) These steps will:
a) report whether there is or is not operating system corruption
b) report whether there is or is not drive file system corruption
c) optimize the settings for creation of dump files
d) check additional settings for dump file settings
e) report whether Windows had found problems with RAM and made modifications
f) optimize BIOS settings:

Code:

Improved DRAM stability
Fix Logitech devices issue.
Fixed memtest86 issue
Fixed Plextor device issu
Fixed Acceleretor TACC2 FPGA card issue
Improve system performance
Add in turn-off function of LED under S3/S4/S5 status.
Fixed Samsung device (SM961, printer) issues.

g) test and report the status of the drives

3) Steps may fix BSOD or BSOD may continue
4) Uploading new V2 after new BSOD will provide new files and folders for troublehooting/debugging
5) New steps / tests may be posted based on the new log files and test results

Involute · 08 Sep 2019

I've confirmed that the PC going to sleep (not the display) triggers the BSOD. I have two Samsung EVO 960 SSDs. I confirmed (through Samsung's Magician s/w) that one had an out-of-date driver, which I updated. Unfortunately, I still have the problem, so I'll spend some time later tonight or tomorrow collecting the data zbook has requested.

- - - Updated - - -

Starting to run the tests. Here are the results from items 2 - 9 (I'll make several posts to make sure I don't lose anything):

Microsoft Windows [Version 10.0.18362.295](c) 2019 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection found corrupt files and successfully repaired them.For online repairs, details are included in the CBS log file located atwindir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offlinerepairs, details are included in the log file provided by the /OFFLOGFILE flag.C:\WINDOWS\system32>dism /online /cleanup-image /scanhealthDeployment Image Servicing and Management toolVersion: 10.0.18362.1Image Version: 10.0.18362.295[==========================100.0%==========================] No component store corruption detected.The operation completed successfully.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.18362.1Image Version: 10.0.18362.295[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 1353984 file records processed.File verification completed. 23370 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 1350 reparse records processed. 1723796 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 1350 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 184907 data files processed.CHKDSK is verifying Usn Journal... 37445376 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 486975945 KB total disk space. 390882460 KB in 1055631 files. 591376 KB in 184908 indexes. 0 KB in bad sectors. 1532869 KB in use by the system. 65536 KB occupied by the log file. 93969240 KB available on disk. 4096 bytes in each allocation unit. 121743986 total allocation units on disk. 23492310 allocation units available on disk.C:\WINDOWS\system32>wmic recoveros set autoreboot = falseUpdating property(s) of '\\KARLS-DESKTOP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk2\\Partition2"'Property(s) update successful.C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7Updating property(s) of '\\KARLS-DESKTOP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk2\\Partition2"'Property(s) update successful.C:\WINDOWS\system32>bcdedit /enum {badmemory}RAM Defects-----------identifier {badmemory}C:\WINDOWS\system32>

- - - Updated - - -

Here are items 13 and 14 (I'll update the BIOS (item 12) last).

Comments for item 14:

14a_HD Tune-Health: Nothing displays on this tab, just the countdown until the next update, at which point it starts over. This happens for all drives.14a_HD Tune-ErrorScan-1: This is a 4TB HDD (RAID 1) and would take > seven hours to run. I'll hold off until necessary. In case it's relevant, I only store data on this drive. Programs are stored on drive 2 (SSD).14a_HD Tune-Benchmark-2: Read error. Test aborted. If it matters, this disk is an SSD, but disk 3 is identical and ran the benchmark with no problems.
Attachment 246703 Attachment 246704 Attachment 246705 Attachment 246706 Attachment 246707 Attachment 246709

- - - Updated - - -

Here's the Sea Tools screen grab for one SSD:
Attachment 246721
It may be both SSDs, though, since the serial number listed is just the start of the number and is the same for both of my SSDs (which are identical). Otherwise, I don't know why both SSDs aren't listed.

The RAID 1 Volume is 4TB of HDD and will take several hours to run, so I'll hold off on that unless it becomes necessary.

I'm also attaching the latest V2 log: Attachment 246722

zbook · 08 Sep 2019

The attachment for Sea Tools results did not open.
Please post a new link.

When available please post the results of chkdsk /r /v (all drives)

1) The first scannow result displayed fixed corruption.
There were no corrupt files on the second scannow.

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

2) Backup all important files on the drive with errors.

3) Run HD Tune overnight so that all drives are tested.

4) Run HD Sentinel: (free or trial edition)
Hard Disk Sentinel - HDD health and temperature monitoring
Hard Disk Sentinel - HDD health and temperature monitoring
Post images of each of these tabs into the thread:
Overview tab
Temperature
SMART
Disk performance

5) Run Crystal Disk: (all drives)
CrystalDiskInfo – Crystal Dew World

6) Run Macrorit on the SSD with errors:
Download Macrorit Disk Scanner Portable 4.3.5

7) Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
Disk Management - How to Post a Screenshot of

Code:

Event[3768]:
  Log Name: System
  Source: disk
  Date: 2019-09-08T21:04:25.723
  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.

Event[3769]:
  Log Name: System
  Source: disk
  Date: 2019-09-08T21:04:25.742
  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.

Event[3770]:
  Log Name: System
  Source: disk
  Date: 2019-09-08T21:04:25.761
  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.

Event[3771]:
  Log Name: System
  Source: disk
  Date: 2019-09-08T21:04:25.780
  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.

Event[3772]:
  Log Name: System
  Source: disk
  Date: 2019-09-08T21:04:25.798
  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.

Event[3773]:
  Log Name: System
  Source: disk
  Date: 2019-09-08T21:04:25.817
  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.

Event[3774]:
  Log Name: System
  Source: disk
  Date: 2019-09-08T21:04:25.835
  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.

Event[3775]:
  Log Name: System
  Source: disk
  Date: 2019-09-08T21:04:25.854
  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.

Event[3776]:
  Log Name: System
  Source: disk
  Date: 2019-09-08T21:04:25.872
  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.

Involute · 08 Sep 2019

Sorry about the bad link. It worked (and still works) for me. Here's one to imgur.

- - - Updated - - -

Here's the chkdsk log for drive C:

Chkdsk was executed in scan mode on a volume snapshot.

Checking file system on C:
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
1353984 file records processed. File verification completed.
23370 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
1350 reparse records processed. 1723796 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered to lost and found. 1350 reparse records processed.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
184907 data files processed. CHKDSK is verifying Usn Journal...
37445376 USN bytes processed. Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

486975945 KB total disk space.
390882460 KB in 1055631 files.
591376 KB in 184908 indexes.
0 KB in bad sectors.
1532869 KB in use by the system.
65536 KB occupied by the log file.
93969240 KB available on disk.

4096 bytes in each allocation unit.
121743986 total allocation units on disk.
23492310 allocation units available on disk.

----------------------------------------------------------------------

Stage 1: Examining basic file system structure ...

Stage 2: Examining file name linkage ...

Stage 3: Examining security descriptors ...

zbook · 09 Sep 2019

When posting if there are layout problems from text > click edit post > re-post > click save changes

Involute · 09 Sep 2019

The layout ‘s fine when a I copy it, then screws up on pasting. How will reposting fix that?

zbook · 09 Sep 2019

Edit followed by re-post typically fixes layout posting problems from text.

If problems are not fixed the use share links (one drive, drop box, or google drive)

Involute · 09 Sep 2019

Here's the chkdsk for drive D:

C:\WINDOWS\system32>chkdsk /r /v D:
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is Scratch.

Stage 1: Examining basic file system structure ...
1792 file records processed.
File verification completed.
0 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
113 reparse records processed.
2948 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
113 reparse records processed.

Stage 3: Examining security descriptors ...
Cleaning up 4 unused index entries from index $SII of file 9.
Cleaning up 4 unused index entries from index $SDH of file 9.
Cleaning up 4 unused security descriptors.
Security descriptor verification completed.
579 data files processed.
CHKDSK is verifying Usn Journal...
1253904 USN bytes processed.
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
Windows replaced bad clusters in file 1BE
of name \Bucky swims\00014.MTS.
Windows replaced bad clusters in file 1C2
of name \Bucky swims\00015.MTS.
Windows replaced bad clusters in file 1C7
of name \Bucky swims\00017.MTS.
Windows replaced bad clusters in file 2BC
of name \Spec.LA\11-15-18\Screen\GrantKeller1.MOV.
Windows replaced bad clusters in file 484
of name \Spec.LA\10-18-18\Speaker\PeterGustev1.MTS.
1776 files processed.
File data verification completed.
An unspecified error occurred (766f6c756d652e63 470).

C:\WINDOWS\system32>

zbook · 09 Sep 2019

Code:

Stage 4: Looking for bad clusters in user file data ...
Windows replaced bad clusters in file 1BE
of name \Bucky swims\00014.MTS.
Windows replaced bad clusters in file 1C2
of name \Bucky swims\00015.MTS.
Windows replaced bad clusters in file 1C7
of name \Bucky swims\00017.MTS.
Windows replaced bad clusters in file 2BC
of name \Spec.LA\11-15-18\Screen\GrantKeller1.MOV.
Windows replaced bad clusters in file 484
of name \Spec.LA\10-18-18\Speaker\PeterGustev1.MTS.
1776 files processed.
File data verification completed.
An unspecified error occurred (766f6c756d652e63 470).

Make sure that the important files are backed up.