Stop Code: INTERNAL POWER ERROR

> Run HD Tune overnight so that all drives are tested.

Which HD Tune test?

Here are the chkdsk results for E:

C:\WINDOWS\system32>chkdsk /r /v E:
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 Data (RAID).

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

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

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

Stage 4: Looking for bad clusters in user file data ...
131824 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters ...
701820224 free clusters processed.
Free space verification is complete.

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

3815314 MB total disk space.
1099213552 KB in 115603 files.
32920 KB in 15961 indexes.
0 KB in bad sectors.
355191 KB in use by the system.
65536 KB occupied by the log file.
2741485 MB available on disk.

4096 bytes in each allocation unit.
976720639 total allocation units on disk.
701820224 allocation units available on disk.

C:\WINDOWS\system32>

- - - Updated - - -

So far, updating the Samsung SSD driver seems to have fixed my problem. I'll post here again if it comes back. Thanks, everyone.

Involute said:

- - - Updated - - -
So far, updating the Samsung SSD driver seems to have fixed my problem. I'll post here again if it comes back. Thanks, everyone.

For clarity and so we all know the resolution: This statement is slightly at odds with your earlier post:

Stop Code: INTERNAL POWER ERROR

So can you definitely confirm - at this stage, you will know within a week, two - that it looks that it indeed was an obsolete NVMe driver that was to blame for these BSODs?

Irrespective of that, one of your Samsung SSDs seems to have damaged sectors - worth thinking about the replacement (or at least having fresh backup in place, as ZBook already suggested).

As far as I can tell, the obsolete NVMe driver was the cause of the BSODs. I don't think I need to come back in a couple of weeks and reconfirm that everything's still fine. If the BSODs come back, I'll be back.

Regarding the SSD with faulty sectors, I think I'll look into replacing it with a larger one since they're relatively inexpensive these days. It gets backed up (along with my other drives) every night, so I think I'm safe for now. I'll need to migrate all my apps and OS to the new SSD, though, so if you can point me to a tutorial for doing that on Ten Forums, that would be great. Otherwise, I'll start digging once I get the replacement.