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

CodeZeta · 11 Oct 2023

Well, its settled then, might have rolled the dice wrong on this one. The RAM is from early 2022, but the motherboard is from this year, IIRC, so it might have coincided.
The best and not-overpriced RAM I found to purchase currently was a KF432C16BB/8, which is not on the QVL, but the KF432C16BB1K4/64 is, which is the 16Gb version of that model times 4.
Would that also be considered risky, in your expert opinion? The rest really is currently overpriced for me right now.

Since I have just performed a clean install on windows, I'm not sure I'll immediately spare the time to do a clean install again. But I will try the other things you've sent pronto.

Crucial Scanner is leading me to an infinitely loading webpage saying "while we're finding compatible upgrades for your compute" with an ad underneath. It stayed this way for the past 20 minutes. Is that normal?

zbook · 11 Oct 2023

For RAM check vendor return policy and restocking fees as it is needed for testing purposes.

There were drive problems reported in the log files after the most recent clean install.

Is the computer stable or unstable with QVL RAM?

Is the computer stable or unstable with only the Windows drive?

There are confounding factors having multiple drive problems and non-QVL RAM.

CodeZeta · 12 Oct 2023

For RAM, I'll be borrowing a friend's sticks this Saturday for testing before purchashing any. It is also NOT exactly on the QVL, only has one similar. His are two HX421C14FB/4 and the QVL mentions a HX421C14FBK4/64, so a 16Gb version of the model. As I'd asked before, can yo utell me if this will be a problem?

You said there were drive problems on the most recent install, but those were on drives G: and E:, correct? These were just usb sticks I had plugged on for backup purposes, like college files, photos and basic softwares. You'll notice I had one more (8Gb USB) connected to my machine on the first new v2 log, this is the usb stick I was using memtest86+ with.

Your mention on QVL vexes me, however, since I'm not using a Zen1 or Zen+ CPU. If my computer can't work with RAMs running at recommended speeds by the manufacturer for their respective CPU just because they weren't tested at the time, isn't the motherboard faulty and unstable? What if I need a different RAM in the future? I shouldn't be tied to a list of availeable hardware from another continent, from 2018 and from before the pandemic. Most people don't even mention QVL when PC building, since, as the manufacturer states: "Memory modules listed below just for reference only. Considering multi variety memory models in market, we can only verify some of them."

Outside of that, my computer seems to have the very same stability with, and without, other drives connected: My games run stable up to the point where I have one too may programs opened and then it crashes instantly.
For personal testing: I've ran memtest 86 once now, and plan to do it again with more tests (sticks in different slots) but after 8 passes it had not found an error. I'll report if it does.
I've added two V2 reports to the link inside the "No HDD folder". One was with my USB connected so you might see an extra drive there, another with nothing else but the Windows drive connected. For those, I have forced a BSOD on it (by opening two games a the same time), and V2 is still telling me that no memory dumps are being created. I'd be very grateful if you could help me more with this matter. I have followed all steps given in this forum for it.

Just a refresher that might help: These crashes only happened to me ONCE this entire year outside of gaming sessions, they can happen instantly, or after long playing sessions. Reducing the settings of the games makes my computer stable for much longer, but it still will have a random chance that, 6h into a session, if I alt-Tab one too many times or the game starts loading something it was loading fine 10 minutes ago (like a dialogue scene), it will crash. I can also replay the very same scene or thing with the computer under the same apparent load and the game under the exact same settings and have no problems in a 12h playing session.
These crashes seem to happen WAY more frequently when running games with the Vulkan API instead of DX11. And finally, something I don't think I have mentioned: You'll notice from the BSODs I've sent way back, they are all under 0% loading, and they have always been. MY BSOD never finish loading whatever they are supposed to load even after many hours, when they DO go away, and sometimes they haven't, it leads to the black screen/BIOS situation I've mentioned (no drive detected/BOOTMGR is missing") so to restart I always have to hard reset my computer anyways. I don't know if this helps with the minidump situation.

zbook · 12 Oct 2023

Any RAM module may or may not cause BSOD.

The QVL RAM are the best tested modules.

Using QVL RAM removes incompatibility problems.

Memtest86 was designed to test for malfunctioning RAM.

Memtest86 was not designed to test for incompatible RAM.

Whenever possible it's best to reduce confounding factors.

If you're able to test using QVL RAM it improves the testing environment.

CodeZeta · 12 Oct 2023

Memtest86 was not designed to test for incompatible RAM.

I get that if it doesn't say there is an error we can't rule out a RAM issue. But if does point to an error, wouldn't that help?

By the way, the link for the drive is here

Sadly my friend's RAM stick is the best thing I can get until next month.

zbook · 12 Oct 2023

Run:

HDSentinel (trial version)(all drives) (results are instantaneous)
Hard Disk Sentinel - HDD health and temperature monitoring
Post results for:
a) Overview
b) Temperature
c) SMART

After posting share links Plan:
a) to detach all disk drives except the disk drive with the Windows operating system
b) not reattaching any drives for one week (flash, external, internal, etc.)
c) for any BSOD post a new V2 share link into the newest post

Code:

Event[1435]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T04:22:48.9200000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk2\DR4 during a paging operation.

Event[1436]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T04:22:48.9200000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk2\DR4 during a paging operation.

Event[1437]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T04:22:48.9200000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk2\DR4 during a paging operation.

Event[1438]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T04:22:48.9200000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk2\DR4 during a paging operation.

Event[1439]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T04:22:48.9200000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk2\DR4 during a paging operation.

Event[1440]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T04:22:48.9200000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk2\DR4 during a paging operation.

Event[1441]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T04:22:48.9200000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk2\DR4 during a paging operation.

Event[1442]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T04:22:48.9200000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk2\DR4 during a paging operation.

Event[1443]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T04:22:48.9200000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk2\DR4 during a paging operation.

Event[1444]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T04:22:48.9200000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk2\DR4 during a paging operation.

Event[1445]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T04:22:48.9200000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk2\DR4 during a paging operation.

Event[1446]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T04:22:48.9200000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk2\DR4 during a paging operation.

Event[1447]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T04:22:48.9200000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk2\DR4 during a paging operation.

Code:

Event[1422]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T04:03:15.9840000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Code:

Event[1368]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T00:55:47.1600000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Event[1369]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T00:56:17.4730000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Event[1370]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T00:56:17.4730000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Event[1371]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T00:56:17.4730000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Event[1372]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T00:56:17.4730000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Event[1373]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T00:56:17.4730000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Event[1374]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T00:56:17.4730000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Event[1375]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T00:56:17.4730000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Event[1376]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T00:56:17.4730000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Event[1377]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T00:56:17.4730000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Event[1378]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T00:56:17.4730000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Event[1379]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T00:56:17.4730000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Event[1380]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T00:56:17.4730000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Event[1381]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T00:56:17.4730000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Event[1382]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T00:56:17.4730000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Event[1383]:
  Log Name: System
  Source: disk
  Date: 2023-10-11T00:56:17.4730000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Code:

Event[1114]:
  Log Name: System
  Source: Microsoft-Windows-Ntfs
  Date: 2023-10-10T23:36:17.5040000Z
  Event ID: 98
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-44484IE
  Description: 
Volume G: (\Device\HarddiskVolume7) needs to be taken offline to perform a Full Chkdsk.  
Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" 
locally or remotely via PowerShell.

Code:

Event[425]:
  Log Name: System
  Source: Microsoft-Windows-Ntfs
  Date: 2023-10-08T21:06:29.0380000Z
  Event ID: 98
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-44484IE
  Description: 
Volume E: (\Device\HarddiskVolume8) needs to be taken offline to perform a Full Chkdsk.  
Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" 
locally or remotely via PowerShell.

Code:

Event[1970]:
  Log Name: System
  Source: volmgr
  Date: 2023-10-12T18:01:23.4430000Z
  Event ID: 161
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-44484IE
  Description: 
Dump file creation failed due to error during dump creation.

Code:

Error code: (NTSTATUS) 0xc0000006 (3221225478) - The instruction at 0x%p referenced memory at 0x%p. 
The required data was not placed into memory because of an I/O error status of 0x%x.

Code:

Description	Disk drive
Manufacturer	(Standard disk drives)
Model	Generic Mass-Storage USB Device
Bytes/Sector	512
Media Loaded	Yes
Media Type	Removable Media
Partitions	1
SCSI Bus	0
SCSI Logical Unit	0
SCSI Port	0
SCSI Target ID	0
Sectors/Track	63
Size	7.21 GB (7,739,988,480 bytes)
Total Cylinders	941
Total Sectors	15,117,165
Total Tracks	239,955
Tracks/Cylinder	255
Partition	Disk #1, Partition #0
Partition Size	7.21 GB (7,740,588,032 bytes)
Partition Starting Offset	4,194,304 bytes
	
Description	Disk drive
Manufacturer	(Standard disk drives)
Model	XPG GAMMIX S11 Pro
Bytes/Sector	512
Media Loaded	Yes
Media Type	Fixed hard disk
Partitions	3
SCSI Bus	0
SCSI Logical Unit	0
SCSI Port	1
SCSI Target ID	0
Sectors/Track	63
Size	953.86 GB (1,024,203,640,320 bytes)
Total Cylinders	124,519
Total Sectors	2,000,397,735
Total Tracks	31,752,345
Tracks/Cylinder	255
Partition	Disk #0, Partition #0
Partition Size	100.00 MB (104,857,600 bytes)
Partition Starting Offset	1,048,576 bytes
Partition	Disk #0, Partition #1
Partition Size	953.25 GB (1,023,540,834,304 bytes)
Partition Starting Offset	122,683,392 bytes
Partition	Disk #0, Partition #2
Partition Size	519.00 MB (544,210,944 bytes)
Partition Starting Offset	1,023,663,931,392 bytes

zbook · 12 Oct 2023

CodeZeta said:

Crucial Scanner is leading me to an infinitely loading webpage saying "while we're finding compatible upgrades for your compute" with an ad underneath. It stayed this way for the past 20 minutes. Is that normal?

Tonight it worked on the computer used to type this post.

See if it is able to run on the problematic computer > post a link into this thread

Crucial System Scanner | Memory Upgrade Scanner | Crucial | Crucial.com

CodeZeta · 13 Oct 2023

Crucial System Scanner worked this time! Results: ASRock B450M Steel Legend | Memory RAM & SSD Upgrades | Crucial.com
The recommended RAM sticks seems to not be on the QVL.

Results of HDSentinel after reconnecting my HDD just so we could scan it. But its the same HDD previously scanned before my swapping of SSD. All included in the linked folder here

I have restarted the computer and disconnected the HDD again, leaving only my SSD with Windows as the only drive.

Questions:
1) Once I have my friend's RAM, what should I test? I can't hold onto them for an entire day, so it'd be good to already know what to do for the sake of tests in this forum.
2) What can I do to make my computer produce minidumps? Given that I've tried all these steps (linked are printscreened proof of steps followed)

zbook · 13 Oct 2023

How come the HD Sentinel results for c) SMART were not included in the share links?

How come the startup and recovery settings were modified?

Is someone telling you to modify them or are you doing this on your own?

Run Tuneup plus again > post new share links for Tuneup plus and V2.

Let's plan to stop troubleshooting and close this thread if the settings must keep being reset.

Contact Crucial, Amazon, etc. and other RAM vendors for information about return polices, restocking fees, warranties, etc. so that you have sufficient time for testing.

Download and install third party software to make backup images.
(some may have free and pay versions)
(Acronis, Aoemi, EaseUS, Macrium, Paragon, etc.)
Macrium may now be pay.
Backup and Restore with Macrium Reflect

Find a flash drive that you can format (> or = 8 GB).

Create a bootable Media Creation Tool (MCT) (Windows 10 iso)

Download Windows 10 ISO File

https://www.microsoft.com/en-us/soft...load/windows10

Post share links displaying SMART for all drives.

Indicate when you've created the Windows 10 MCT and when you've made backup images.

CodeZeta · 13 Oct 2023

How come the HD Sentinel results for c) SMART were not included in the share links?

Are "Screenshot 2023-10-13 141944" and "Screenshot 2023-10-13 141956" not on the drive link I sent for you? Are they not what you meant? I thought those were the SMART results you needed.

How come the startup and recovery settings were modified? Is someone telling you to modify them or are you doing this on your own?

I modified it following these forum recommendations to get minidumps so we could get more answers. It frustrates me that Step 2 worked on the SSD I had before and not on this one and I've requested some help without getting answers, so I took it upon myself to try and fix it while still following recommended guidelines from this forum. That is all.

I have contacted XPG. They have a lifetime return and refund policy. Do we already know it is the RAM though, or is this just something else to test? I am still confused on this.

I'll notify you of the MCT and backup images.

Here's the newest V2 Log of the recent BSOD.