Any BSOD experts? Have 7 attached here just from this month

Wver 22H2
Back in Jan~February I was having one, or two, inconsistent types of BSODs: WHEA_UNCORRECTABLE_ERROR and KERNEL_DATA_STORAGE_ERROR.
It would happen at random during longer periods of gaming or when multiple light programs were open simultaneously, this could be Chrome, plus some editing software and a lighter game, or two light games at the same time (which I do during slow D&D sessions). No tech support could figure it out so I brought it to a friend's house, and even when during the MOST stress I had ever put my PC through: FurMark+AIDA64+3 medium to heavy games open simultaneously, it just didn't happen... As I brought my PC to my house, repeated the hyper-stress-test, and the issue seemed 100% fixed.

Flashforward a month, the issue comes back, I go to reddit's r/techsupport and two guys helped me out narrow it down: Since the top line error for the blue screens ended all in 10 it was "the NVMe SSD or the M.2 slot/motherboard. Probably something moved when you moved the PC over to another house and back". I switched both and the issue was, indeed, solved! Until this month.

I have recently been getting new BSODs though. Here are the bluescreens. As you can see, no longer xxxxx10 in the error line! So thats one thing off the list.
I thought there were all because of some recent launch/memory leak issues with Baldur's Gate 3, since that's the only thing I've been playing (that's where the first 4 BSOD are from). Andd then I got it on this Sunday twice:
- Once from just opening my editing software while in a discord call with friends during a virtual tabletop session (very simple simulation of a 3D table with some assets). That's the 5th BSOD in the linked album
- Then the night of the same day, from adjusting my browser tabs and open documents while generating AI images for our D&D characters in the background, which is GPU intensive. That's the 6th image.

Since then I've tested, again, with Furmark, which doesn't make it crash after 2 minutes of stress testing on a much more resource intensive stressor than Baldur's Gate, at least GPU wise.
When I was getting the first 4 BSOD's I performed the windows check up of RAM, but the results mistified me:
- I tested with both sticks in, found one problem.
- I tested with one stick in at a time, found a problem with one of them.
- Redid the test on the same one on another slot, found no problem but removed it nonetheless!
- Played with just one stick in, got a BSOD.
- Connected the old (supposedly bad) RAM stick in. Redid the test, said there were no problems with it! So which is it?

Today I forcefully opened a bunch of games at the same time and got the 7th BSOD in the album.
Do these BSOD's mean anything to the experts out there? I'm about to call this a curse on my computer.

Whenever possible we would like to improve the website.

How come the posting instructions were not seen or followed?

What modifications if any would be useful?

Hi zbook.

The answer is I`m an idiot and just posted everywhere I could before going to work today so I could try fixing stuff after getting home. You`re all super helpful and your posts are easy to follow. This was 100% a user-sided mistake.

Here are the files requested by the rules

I`d like to add that my computer does not egenerate minidump files. I`ve read that it could be an SSD problem. My Start-up Recovery settings (in the advanced system settings) ARE set to small memory dump (256Kbps), I have the `Write an event to the system log` box checked and the small dump directory IS %SystemRoot%\Minidump, which is an existing folder, path "C:\Windows\Minidump".

The logs files indicated:

a) insufficient drive free space
b) drive problems
c) hibernation problems


Please perform the following steps: (in sequence)


1) Run: Tuneup plus > post a share link into this thread using one drive, drop box, or google drive

https://www.tenforums.com/attachment...p_plus_log.bat

Batch files for use in BSOD debugging


2) Free up space on C: so that there is > 30 GB free space


3) Open administrative command prompt and type or copy and paste:

powercfg -h off


4) Reboot


5) Run Sea Tools for Windows Long Generic test (all drives) > post images or share links into this thread using one drive, drop box, or google drive

https://www.seagate.com/content/dam/...00869623_B.pdf

https://www.seagate.com/content/dam/...sInstaller.exe



6) Run HD Tune: (free or trial version) (all drives):

HD Tune website

Post images or share links for results on these tabs:

a) Health
b) Benchmark
c) Full error scan



7) Open administrative command prompt and type or copy and paste:

chkdsk /b /v

Run these chkdsk switches on all drives using the syntax: chkdsk /b /v C: , chkdsk /b /v D: , chkdsk /b /v E: , etc.

Make sure that chkdsk /b /v C: is run overnight while sleeping


C:\WINDOWS\system32>chkdsk /b /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 as needed.


8) After completing chkdsk /b /v on all drives run:

https://www.tenforums.com/attachment...kfromevent.bat



9) These tests can run overnight while sleeping:

a) Sea Tools for Windows Long Generic test
b) HD Tune Full error scan
c) chkdsk /b /v


10) For new BSOD post a new V2 share link into the newest post

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 22.5 GB
Total Space: 487.7 GB
File System: NTFS
      Model: Asgard AN3.0 512GNVMe-M.2/80

      Drive: D:
 Free Space: 102.7 GB
Total Space: 871.3 GB
File System: NTFS
      Model: ST1000DM010-2EP102

      Drive: F:
 Free Space: 19.6 GB
Total Space: 78.0 GB
File System: NTFS
      Model: ST1000DM010-2EP102

I was looking at more guides to make dumpfiles appear, and it seems to have finally worked. My computer crashed during step 1, while running Tuneup Plus along with other stuff I was using at the time.
Weirdly enough I didn`t get to see a Blue Screen, but it did make a minidump file this time!
Just to make sure, as I`ll still be following the steps provided, I`ve remade the log collection and deleted the culprit for occupying so much hardrive space
I added it to the drive as the `2nd run` zip file. I`ll probably stick to that sequential naming convention.
Underneath is the code. I`m trying to post it separately from this post but its just adding it below this one. I hope its not a problem

Code:

 Microsoft Windows 10 Pro  Version 22H2 (OS Build 19045.3448)
  
==================================================================

    Started on 27/09/2023 at  2:40:50.81 
	
        [SFC /ScanNow] 
	
Beginning system scan.  This process will take some time.

Results: 
 
Windows Resource Protection did not find any integrity violations.
 
==================================================================

    Started on 27/09/2023 at  2:42:16.76 

        [DISM /online /cleanup-image /ScanHealth] 

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19045.3448 
 
No component store corruption detected.

The operation completed successfully. 
 
==================================================================

    Started on 27/09/2023 at  2:43:30.16 

        [DISM /online /cleanup-image /RestoreHealth] 

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19045.3448 
 
The restore operation completed successfully.

The operation completed successfully. 
 
==================================================================

The second "SFC /ScanNow" was skipped, as the first output the following:

Windows Resource Protection did not find any integrity violations.
 
==================================================================

    Started on 27/09/2023 at  2:44:47.66 

        [ChkDsk /Scan]  
 
The type of the file system is NTFS.
 
Stage 1: Examining basic file system structure ... 
951808 file records processed.                                                        
File verification completed.
Phase duration (File record verification): 12.26 seconds.
13515 large file records processed.                                   
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.                                     
Phase duration (Bad file record checking): 0.05 milliseconds.
 
Stage 2: Examining file name linkage ... 
360 reparse records processed.                                      
1311080 index entries processed.                                                       
Index verification completed.
Phase duration (Index verification): 18.32 seconds.
0 unindexed files scanned.                                        
Phase duration (Orphan reconnection): 3.80 seconds.
0 unindexed files recovered to lost and found.                    
Phase duration (Orphan recovery to lost and found): 0.11 milliseconds.
360 reparse records processed.                                      
Phase duration (Reparse point and Object ID verification): 3.35 milliseconds.
 
Stage 3: Examining security descriptors ... 
Security descriptor verification completed.
Phase duration (Security descriptor verification): 18.85 milliseconds.
179637 data files processed.                                           
Phase duration (Data attribute verification): 0.05 milliseconds.
CHKDSK is verifying Usn Journal...
38330552 USN bytes processed.                                                           
Usn Journal verification completed.
Phase duration (USN journal verification): 110.42 milliseconds.

Windows has scanned the file system and found no problems.

No further action is required.
 
499454571 KB total disk space. 
352511132 KB in 639660 files.
389880 KB in 179638 indexes.
0 KB in bad sectors.
1077347 KB in use by the system.
65536 KB occupied by the log file.
145476212 KB available on disk.
 
4096 bytes in each allocation unit. 
124863642 total allocation units on disk.
36369053 allocation units available on disk.
Total duration: 34.53 seconds (34534 ms).
 
==================================================================
 
    Started on 27/09/2023 at  2:45:31.26 
 
AutoReboot   
 
TRUE        
 
==================================================================
 
        [Set AutoReboot = False] 
 
Updating property(s) of '\\DESKTOP-5R7004M\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk1\\Partition3"'

Property(s) update successful.

==================================================================
 
AutoReboot   
 
FALSE       
 
==================================================================
 
DebugInfoType   
 
2              
 
==================================================================

        [Set DebugInfoType = 7]

Updating property(s) of '\\DESKTOP-5R7004M\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk1\\Partition3"'

Property(s) update successful.

==================================================================
 
DebugInfoType   
 
7              
 
==================================================================

        [WMIC PageFile list]

AllocatedBaseSize=16384
CurrentUsage=60
Description=C:\pagefile.sys
InstallDate=20230927022627.065816-180
Name=C:\pagefile.sys
PeakUsage=61
Status=
TempPageFile=FALSE
 
==================================================================
 
AutomaticManagedPagefile   
 
TRUE                      
 
==================================================================

        [Set AutomaticManagedPagefile = True]

Updating property(s) of '\\DESKTOP-5R7004M\ROOT\CIMV2:Win32_ComputerSystem.Name="DESKTOP-5R7004M"'

Property(s) update successful.

==================================================================
 
AutomaticManagedPagefile   
 
TRUE                      
 
==================================================================

        [BcdEdit /enum {badmemory}]

RAM Defects
-----------
identifier              {badmemory}
 
==================================================================

    Finished on 27/09/2023 at  2:45:32.39
    It took 4 minutes and 42 seconds to complete the operations.

The settings are not yet optimal > when available post tuneup plus results

The V2 ran before tuneup plus.

So looks good now.


Which Sony hardware was recently attached to the computer?


Free space is excellent now

Code:

      Drive: C:
 Free Space: 139.2 GB
Total Space: 487.7 GB
File System: NTFS
      Model: Asgard AN3.0 512GNVMe-M.2/80

Code:

Event[2850]:
  Log Name: System
  Source: disk
  Date: 2023-09-24T01:16:52.0820000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-5R7004M
  Description: 
The device, \Device\Harddisk1\DR1, has a bad block.

Event[2851]:
  Log Name: System
  Source: disk
  Date: 2023-09-24T01:16:52.0820000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-5R7004M
  Description: 
The device, \Device\Harddisk1\DR1, has a bad block.

Event[2852]:
  Log Name: System
  Source: disk
  Date: 2023-09-24T01:16:52.0820000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-5R7004M
  Description: 
The device, \Device\Harddisk1\DR1, has a bad block.

In the one dump that was uploaded - and it's never wise to make a firm diagnosis based on one dump - we see a failure during a page-in operation. The reported exception code is a 0xC0000006, which indicates a page-in error. That means we're looking at either RAM (and the RAM page used was bad) or a paging device failure (and the page in the paging file was in a bad drive block).

In the dump call stack (which you read from the bottom up) we see the folllwing...

Code:

               rsp : 0xfffffe838b0d6c48 : 0xfffff80340410e29 : nt!KiBugCheckDispatch+0x69
0xfffffe838b0d6c48 : 0xfffff80340410e29 : nt!KiBugCheckDispatch+0x69
0xfffffe838b0d6c60 : 0xfffff803406b63f1 : nt!HvpGetCellPaged+0xc1
0xfffffe838b0d6c78 : 0xfffff80343edd955 : Ntfs!NtfsCheckFileRecord+0x155

Here was can see the Windows ntfs.sys driver checking a file record (Ntfs!NtfsCheckFileRecord) followed by the kernel getting the next cell from the paging file (nt!HvpGetCellPaged) and then we get the bugcheck. This suggests that the paging file drive is the more likely candidate for the root cause.

This hypothesis is confirmed in the System log, where there are many of these errors...

Code:

  Log Name: System
  Source: disk
  Date: 2023-09-24T01:16:52.0820000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-5R7004M
  Description: 
The device, \Device\Harddisk1\DR1, has a bad block.

That's going to be your Asgard AN3.0 512GNVMe-M.2 SSD. I don't think there is an Asgard-specific diagnostic tool, so the Seatools tests suggested above is probably your best option.

Edit: The SONY hardware could have been either my headset or my controller, which constantly disconnect and reconnect due to bluetooth errors and fiddling from bluettoth to cabled so they can charge, etc.

Ha, who could have guessed that my gamble to trade a budget off-brand SSD that was giving me problems for yet another budget off-brand SSD was the equivalent of shooting myself in the other foot.

I'm running Seatools as we speak now, both on SSD and HDD. HDD is taking a really long time, 45 minutes and its only now 1/3 of the way through.

SSD weirdly enough is Auto-Aborting the Long Generic Test. I'm going to try running it again by itself after the HDD one is done, instead of both at the same time.
But this is it for me for today. I'll touch back, and get back to the tests in about 15h from no. Just so we can say, as for sure as we can, that this is just an ssd problem.

Thanks for all the help and patience! See you tomorrow with an update

Please see step #9.


The HD Tune Full error scan often displays bad blocks.

Hello zbook and ubuysa! I did see your message before going away yesterday zbook, its just that I've also been a bit overworked and there were power outtages yesterday, slowing me down.
I'm back and with all but one test completely done.

I've uploaded all files requested in their respective files in this link

You'll notice most Sea Tools test didn't even complete on the SSD.

The only test missing, you'll notice, is HD Tune Pro's error scan on my HDD specifically. That'd be because of a power outtage that cut it short after the 50% mark. I'm currently reapplying the test starting at the halfway point, and will inform if it comes up with anything but an all-green, unless you really want to look at it yourselves regardless of the all-green squares.
Additionally, still on HD Tun Pro, I've performed a test just this morning, instead of yesterday, after the chkdsk runs, and now it was able to complete the test without errors. I've labeled it #2.

Finally, you might notice one weird word or another on the chkdsk log, because, for one reason or another, some of the scanning came up in my native language, I manually translated it cross-referencing the correct wording from others logs I found on google.