BSOD Randomnly throughout the Week

[techdave]

• 
  A brief description of your problem (but you can also include the steps you tried) -Intermittent BSOD every day, or every other day. Install all updates and update drivers.
• System Manufacturer?-ASUS
• Laptop or Desktop?-Desktop
• Exact model number (if laptop, check label on bottom)-ASUS Motherboard TUF B360M-PLUS GAMING (LGA1151)
• OS ? (Windows 11, 10, 8.1, 8, 7, Vista)-Win10
• x86 (32bit) or x64 (64bit)?-x64
• What was original installed OS on system?-10
• Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?-Purchased
• Age of system? (hardware)-2 years
• Age of OS installation?-1/22/21
• Have you re-installed the OS?-no
• CPU-i7
• RAM (brand, EXACT model, what slots are you using?)
• Video Card
• MotherBoard - (if NOT a laptop)-ASUS Motherboard TUF B360M-PLUS GAMING (LGA1151
• Power Supply - brand & wattage (if laptop, skip this one)
• Is driver verifier enabled or disabled?-Disabled
• What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)-Windows Defender
• Are you using proxy, vpn, ipfilters or similar software?-no
• Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)-Acronis
• Are you currently under/overclocking? Are there overclocking software installed on your system?-No

 

[ubuysa]

Hello, and welcome to the forum!

I've looiked at the six most recent dumps and a pattern has already emerged. I think you have an issue with your SATA SSD (the KINGSTON SQ500S37480G). Most of the bugchecks are WINLOGON_FATAL_ERROR, all with an exception code (0xC000006) indicating an I/O error during a paging operation. There is also a KERNEL_DATA_INPAGE_ERROR bugcheck with exception codes (0xC0000006 and 0xC000000E), the latter indicating that an I/O device does not exist. All these exceptions point squarely at a problem with your system drive.

I'd first suggest that you check the SATA and power connectors, at both the SSD drive and the motherboard.

Kingston don't have a diagnostics tool but the Kingston SSD Manager can display the SMART data. Please upload a screenshot of the SMART data output from this tool.

Also, Seagate have an SSD testing tool (called Seatools) which, although primarily for Seagate drives, can be used to good effect on other vendor's drives. I would download Seatools and run the 'Long Drive Self Test' on your SSD. Post a screenshot of the results.

 

[jcgriff2]

I agree -- hard drive issue.

 

[techdave]

Hey, sorry for the long delay. I was able to gather the information from the Kingston SSD Manager, but the Seagate tools was unable to run a long self test on the machine. I have also attached the error operation screenshot relating to the self test.

 

[ubuysa]

That's a strange way to present the SMART data (in your first image). The way they present it, it looks to me as though you may have excessive Uncorrectable Errors on that drive. Could you possibly download CrystalDiskInfo and post a screenshot of the SMART data for that drive?

 

[techdave]

Sorry for the delay. Here are the results.

 

[ubuysa]

Can you please run the Seatools diagnostic tool I linked to and see what that says about your SSD.

 

[techdave]

I uploaded the results of the seatools diagnostic tool above, I was unable to run a long self test as it was not supported by the drive.

 

[ubuysa]

I uploaded the results of the seatools diagnostic tool above, I was unable to run a long self test as it was not supported by the drive.

Nope, just CrystalDiskInfo output was uploaded.

Have you checked the power and SATA connectors - at both ends?

Run a chkdsk /f on the drive and post the results.

It might be worth removing the paging file, rebooting, and then enabling a system managed paging file again. It might just be a glitch in the paging file.

 

[techdave]

These are from the Seatools tool

 

[ubuysa]

Can you also do the other things I asked above?

 

[techdave]

Sorry for the delay in response. We did check the connectors on the drive. I have attached event log and will perform the last instruction you provided when the user leaves today.

 

[ubuysa]

That chkdsk output is encouraging because your filesysyem looks to be fine. These errors are minor and can be ignored...

Stage 3: Examining security descriptors ...
Cleaning up 1348 unused index entries from index $SII of file 0x9.
Cleaning up 1348 unused index entries from index $SDH of file 0x9.
Cleaning up 1348 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 95.05 milliseconds.
  273879 data files processed.

The important message is this one...

Windows has made corrections to the file system.
No further action is required.

I've looked back at earlier dumps in your upload and they are all similar failures, with 0xC0000006 and 0xC000000E bugchecks (mostly 0xC0000006). If the issue isn't with the system drive then it may well be with RAM. Looking at your motherboard support page we can see that the RAM you have installed (Crucial BLS8G4D26BFSBK.8FD) is not on the QVL for your motherboard. In fact the only Crucial RAM on the QVL are these.

Crucial CT16G4DFD8213.16FB1 16GB 15-15-15-36 1.2
Crucial CT4G4DFS8213.8FA2 4GB 15-15-15-36 1.2
Crucial CT4G4DFS8213.8FB1 4GB 15-15-15-36 1.2
Crucial CT8G4DFD8213.16FA1 8GB 15-15-15-37 1.2
Crucial CT8G4DFS8213.8FB1 8GB 15-15-15-36 1.2

According to the Crucial website the RAM you have is this...

BLS8G4D26BFSBK 8GB Single Rank DDR4-2666 CL16 (16-18-18) 1.2V

Those timings (16-16-18-18) are not supported by any of the RAM on the QVL. That doesn't mean that it won't work, but it does indicate that your RAM has not been tested and verified as compatible, and that always makes the RAM suspect - especially when there are timing differences.

In addition, you have the RAM installed in slots 1 and 3 according to the RAM details in your upload...

CRUCIAL    BLS8G4D26BFSBK.8FD    E2027053    2666 MHz    8 GB    BANK 1    ChannelA-DIMM2    8    64
CRUCIAL    BLS8G4D26BFSBK.8FD    E20845A0    2666 MHz    8 GB    BANK 3    ChannelB-DIMM2    8    64

Your motherboard manual doesn't specify which slots you must use for only two sticks (some do) but I think it might be worth trying your RAM sticks in slots 2 and 4 to see whether that makes any difference?

I would also like you to test your RAM using Memtest86...

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

Let's see what that tells us...