Question Need some help with crashes on my new gaming pc

Jul 21, 2025
5
0
10
So I have had this pc less then a year and its starting to crash alot so far this week its done it like 10 times and I cannot find out why normally the screen and keyboard go dark and it reboots but the tower stays on and sometimes it blue screens but that only happens once in every 10 crashes the only lead I have is this

Problem signature
Problem Event Name: BlueScreen
Code: 1a
Parameter 1: 3f
Parameter 2: 2468c
Parameter 3: b9b3ae90
Parameter 4: 6cb0a0e
OS version: 10_0_26100
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.26100.2.0.0.256.48
Locale ID: 2057

Files that help describe the problem
071925-59234-01.dmp
sysdata.xml
WERInternalMetadata.xml
memory.csv
sysinfo.txt
WERInternalRequest.xml
 
ok its custom built heres the specs I will be back with the psu need to check my documentation

Device name My-Gaming-PC
Processor AMD Ryzen 9 7900X 12-Core Processor (4.70 GHz)
Installed RAM 32.0 GB (31.2 GB usable)
Device ID F8B43C10-04E0-4022-9C14-22CA22FD218C
Product ID 00330-53976-71096-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

Edition Windows 11 Pro
Version 24H2
Installed on ‎31/‎12/‎2024
OS build 26100.4484
Experience Windows Feature Experience Pack 1000.26100.128.0
 
bugcheck 0x1a with parameter 1 =3f
means that windows tried to page in data from disk but got a CRC checksum error on the data transfer.

normally, you check data cable connections. or run crystaldiskinfo.exe and read the smart data from your drive to check the drive health. maybe a overheated drive depending on what drive you have.
depending on what kind of drive there are other things to look for. ssd might not have enough free space to for its garbage collection. (just make sure there is plenty of free space, update firmware, boot into bios and let the drive sit idle for a hour to run garbage collection)

note: I would also start cmd.exe as an admin and run
DISM.exe /Online /Cleanup-Image /RestoreHealth

this should repair any files that had a crc error while when originally copied to the system.
it should also repair files that were modified . (not crc error related)

certain overclock software can cause crc errors.
 
When asked for full specs, you need to give the full specs. You didn't list your GPU, your motherboard, you drive(s), your CPU cooler, your RAM (the amount of RAM does help much, you have to give the brand, model and currently selected timing).

You might also want to analyze the .dmp files generated after the crashes with WinDbg as explained here:

https://www.wikihow.com/Read-Dump-Files

If it's always the same module that is involved, it gets easier to isolate the problem and find a fix.
 
I'm in agreement with @johnbl that this is either bad RAM. a bad paging file, or a bad system drive. You don't specify the model number of your RAM, nor the clock speed you're running it at. In the first instance I would remove any RAM overclock (via XMP/DOCP) and run the RAM at its native speed. See whether that stops the BSODs.
 
I have looked in the reliability monitor and only get error detail when it blue screens which is like 1 in 10 of the crashes this was the last info

Problem signature
Problem Event Name: BlueScreen
Code: 1a
Parameter 1: 3f
Parameter 2: 2468c
Parameter 3: b9b3ae90
Parameter 4: 6cb0a0e
OS version: 10_0_26100
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.26100.2.0.0.256.48
Locale ID: 2057

Files that help describe the problem
071925-59234-01.dmp
sysdata.xml
WERInternalMetadata.xml
memory.csv
sysinfo.txt
WERInternalRequest.xml


as for the specs the ones I posted I got from the settings my pc specs page is there a better way to get more full specs

on list of parts fitted

motherboard is Asus ROG Strix x670e-f gaming wi fi
gpu nvidia geforce rtx 4090 24gb
ram 2- 16gb corsair vengence rdb ddr5 5600mhz
cooling asus rog ryujin 3 360 ram

also my pc is not overclocked I have no idea how to do that not sure the place I got it from would have done that before they sent it to me

on eans that windows tried to page in data from disk but got a CRC checksum error on the data transfer

my main drive is an SSD but I also have a internal 2tb drive that is messed up I was copying something to it and it failed since then it has shown a 10tb file usage when the drive is empty and when I try and format it

it say it is being used by another program or process and I should quit any disk utillties or other program using it

only issue there none using that drive not sure if that is the issue
 
Last edited:
check the connection to the messed up drive.
if it is a sata drive, sometimes the data cable can be loose and vibrations or thermal expansion can make and break the connection several times a second.
you may also go into bios and disable the reading of the smart data from that drive so that errors are not reported.
you might also be able to disable the sata port that the drive is connected to until you figure out the problem.

windows system process does start a background process that attempts to repair drives 5 minutes after the drive goes idle.
this process will try over and over again to read data when CRC errors occur. Then it will try to relocate the info to another part of the drive. Not sure what will happen if it finally gets a clean copy of the data but tries to relocate it to another spot and gets a CRC error. Check the cables or disable the drive might be the best action.
mechanical ie spinning hard drives, tend to last 3 or 4 years and will start to show CRC errors as the drive wears. (or gets bumped) the servo motors that position the heads over the plater end up not matching the sector locators written to disk when the drive was new. You end up having to use a special software tool to rewrite the markers. (low level format)
mostly the tools are not available any more. Since windows does the repair at idle, by the time people start to see crc errors the drive is at end of life. (assuming it is not a loose cable, which is common for SATA drives) I would also check to see if the sata port for the bad drive has hot swap enabled. if it is enabled, then a loose cable is more likely.

I would focus on the questionable drive.
generally, bad ram results in incorrect memory addresses being used and the error codes tend to result in an access violtaion code. cpu crc errors due to collisions in the cache levels tend to get caught by the cpu memory controller and end up with a different bugcheck code.
 
Last edited:
The pc itself tried to fix it after a shut down when I rebooted it before it came on it was trying to repair the drive which seemed to work only then I had to go into bios as my boot order vanished and I had to tell it to boot from the ssd and still the hard drive is broke

thanks for the info I i will look into what you said its funny the only error showing in event viewer is

error 1796 TPM-WMI