F5F Stay Refreshed Software Operating Systems I need assistance with issues occurring on my new gaming PC.

I need assistance with issues occurring on my new gaming PC.

I need assistance with issues occurring on my new gaming PC.

Pages (2): 1 2 Next
R
raskin
Junior Member
13
01-21-2023, 08:54 AM
#1
I've experienced this computer for under a year, and it's been crashing frequently this week—about ten times already. Usually the screen and keyboard go dark and it restarts, but the tower keeps running. Sometimes it shows a blue screen, though that only happens once every ten crashes. The only clue I have is this.
R
raskin
01-21-2023, 08:54 AM #1

I've experienced this computer for under a year, and it's been crashing frequently this week—about ten times already. Usually the screen and keyboard go dark and it restarts, but the tower keeps running. Sometimes it shows a blue screen, though that only happens once every ten crashes. The only clue I have is this.

T
207
01-21-2023, 12:37 PM
#2
full system spec? include brand and model of the psu
or if it is a prebuild, need the exact model
T
ToastaStroodel
01-21-2023, 12:37 PM #2

full system spec? include brand and model of the psu
or if it is a prebuild, need the exact model

O
oliseli123
Member
59
01-21-2023, 02:31 PM
#3
It is a custom-built unit; here are the specifications. I will return with the PSU to verify 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 OS, x64-based processor
Pen and touch: No input 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
O
oliseli123
01-21-2023, 02:31 PM #3

It is a custom-built unit; here are the specifications. I will return with the PSU to verify 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 OS, x64-based processor
Pen and touch: No input 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

B
BM0_M1NECRAFT
Member
156
01-28-2023, 01:10 AM
#4
the psu is
Asus ROG Thor1000W Platinum 2
B
BM0_M1NECRAFT
01-28-2023, 01:10 AM #4

the psu is
Asus ROG Thor1000W Platinum 2

L
lizzard89
Senior Member
707
01-30-2023, 09:37 AM
#5
Check Reliability History/Monitor and Event Viewer.
Both tools might record error codes, warnings, or other events shortly before or during the BSODs.
L
lizzard89
01-30-2023, 09:37 AM #5

Check Reliability History/Monitor and Event Viewer.
Both tools might record error codes, warnings, or other events shortly before or during the BSODs.

B
Bunge014
Junior Member
9
01-30-2023, 02:30 PM
#6
bugcheck 0x1a with parameter 1 =3f indicates windows attempted to load data from disk but encountered a CRC checksum failure during transfer. Typically, verify data cable connections or use crystaldiskinfo.exe to assess drive health. Depending on the drive type, other factors may apply. For example, an SSD might lack sufficient free space for garbage collection—ensure ample free space, update firmware, boot into BIOS, and let the drive idle for an hour. Run DISM.exe /Online /Cleanup-Image /RestoreHealth to fix CRC errors and restore modified files not affected by checksums. Note that using cmd.exe as administrator can help with this process.
B
Bunge014
01-30-2023, 02:30 PM #6

bugcheck 0x1a with parameter 1 =3f indicates windows attempted to load data from disk but encountered a CRC checksum failure during transfer. Typically, verify data cable connections or use crystaldiskinfo.exe to assess drive health. Depending on the drive type, other factors may apply. For example, an SSD might lack sufficient free space for garbage collection—ensure ample free space, update firmware, boot into BIOS, and let the drive idle for an hour. Run DISM.exe /Online /Cleanup-Image /RestoreHealth to fix CRC errors and restore modified files not affected by checksums. Note that using cmd.exe as administrator can help with this process.

C
ColumXB
Member
209
01-31-2023, 08:07 PM
#7
When requested for complete details, provide all relevant hardware information such as your GPU, motherboard, drives, CPU cooler, and RAM specifications (brand, model, timing). Also consider examining the .dmp files produced after crashes using WinDbg, as outlined here: https://www.wikihow.com/Read-Dump-Files. If the same module consistently appears, it simplifies identifying and resolving the issue.
C
ColumXB
01-31-2023, 08:07 PM #7

When requested for complete details, provide all relevant hardware information such as your GPU, motherboard, drives, CPU cooler, and RAM specifications (brand, model, timing). Also consider examining the .dmp files produced after crashes using WinDbg, as outlined here: https://www.wikihow.com/Read-Dump-Files. If the same module consistently appears, it simplifies identifying and resolving the issue.

M
Minimater_2003
Junior Member
48
02-01-2023, 02:16 AM
#8
I share the same view with @johnbl that this could be due to poor RAM, a faulty paging file, or a failing system drive. You haven't provided the RAM model number or the clock speed you're using. Initially, I recommend disabling any overclocking (through XMP/DOCP) and running the RAM at its standard speed to determine if that resolves the BSODs.
M
Minimater_2003
02-01-2023, 02:16 AM #8

I share the same view with @johnbl that this could be due to poor RAM, a faulty paging file, or a failing system drive. You haven't provided the RAM model number or the clock speed you're using. Initially, I recommend disabling any overclocking (through XMP/DOCP) and running the RAM at its standard speed to determine if that resolves the BSODs.

G
GalHarosh234
Junior Member
21
02-01-2023, 09:49 AM
#9
I checked the reliability monitor and only errors appear during blue screens, which accounts for about 1 in 10 crashes. This was the last update of information.

Problem signature
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 issue: 071925-59234-01.dmp, sysdata.xml, WERInternalMetadata.xml, memory.csv, sysinfo.txt, WERInternalRequest.xml

According to the specifications I shared, the details from my PC settings page might be more comprehensive. There’s a section on the parts installed. My motherboard is an Asus ROG Strix X670e-f gaming Wi-Fi card. The GPU is an NVIDIA GeForce RTX 4090 with 24GB VRAM. RAM is between 2 and 16 GB, using Corsair Vengeance RGB DDR5 5600MHz. Cooling includes the ASUS ROG Ryujin 3 360 RAM cooler.

I’m not overclocking anything; I’m unsure how to do it. I don’t know if the seller had this configuration before sending it. On Windows, it tried to load data from disk but encountered a CRC checksum error during transfer. My main drive is an SSD, but I also have an internal 2TB drive that’s malfunctioning. After copying files to it, it reported a 10TB usage even when empty, and formatting failed. It indicated another program or process was using the drive, so I should close any disk utilities or other applications using it. There are no other issues with that drive, though it’s unclear if this is the main problem.
G
GalHarosh234
02-01-2023, 09:49 AM #9

I checked the reliability monitor and only errors appear during blue screens, which accounts for about 1 in 10 crashes. This was the last update of information.

Problem signature
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 issue: 071925-59234-01.dmp, sysdata.xml, WERInternalMetadata.xml, memory.csv, sysinfo.txt, WERInternalRequest.xml

According to the specifications I shared, the details from my PC settings page might be more comprehensive. There’s a section on the parts installed. My motherboard is an Asus ROG Strix X670e-f gaming Wi-Fi card. The GPU is an NVIDIA GeForce RTX 4090 with 24GB VRAM. RAM is between 2 and 16 GB, using Corsair Vengeance RGB DDR5 5600MHz. Cooling includes the ASUS ROG Ryujin 3 360 RAM cooler.

I’m not overclocking anything; I’m unsure how to do it. I don’t know if the seller had this configuration before sending it. On Windows, it tried to load data from disk but encountered a CRC checksum error during transfer. My main drive is an SSD, but I also have an internal 2TB drive that’s malfunctioning. After copying files to it, it reported a 10TB usage even when empty, and formatting failed. It indicated another program or process was using the drive, so I should close any disk utilities or other applications using it. There are no other issues with that drive, though it’s unclear if this is the main problem.

M
MrGitarre
Member
160
02-01-2023, 01:18 PM
#10
Verify the link with the faulty storage device.
If it's a SATA connection, occasionally the data cable might become unstable, and factors like vibrations or thermal changes can cause intermittent disconnections.
You could try disabling the BIOS reading of that drive to prevent error notifications.
It may also help to turn off the SATA port connected to the drive until you identify the issue.
The Windows system process initiates a background repair about five minutes after the drive becomes idle.
This process repeatedly attempts to read data when CRC errors appear, then tries to move the information elsewhere.
Uncertain whether a clean data copy will succeed if relocated and a new CRC error occurs—consider checking cables or disabling the drive as a possible solution.
Hard mechanical drives, such as spinning hard disks, usually last 3 to 4 years before showing CRC errors due to wear, or they may misalign because servo motors no longer match the sector markers written on the disk.
This often requires using specialized software to reprogram the drive (low-level format).
Most such tools are no longer available.
Since Windows attempts repairs while idle, by the time CRC errors become visible, the drive is likely nearing the end of its life—provided the cable isn't loose, which is typical for SATA devices.
It's worth also checking if the SATA port on the faulty drive supports hot-swapping. If it does, a loose cable is more probable cause.
M
MrGitarre
02-01-2023, 01:18 PM #10

Verify the link with the faulty storage device.
If it's a SATA connection, occasionally the data cable might become unstable, and factors like vibrations or thermal changes can cause intermittent disconnections.
You could try disabling the BIOS reading of that drive to prevent error notifications.
It may also help to turn off the SATA port connected to the drive until you identify the issue.
The Windows system process initiates a background repair about five minutes after the drive becomes idle.
This process repeatedly attempts to read data when CRC errors appear, then tries to move the information elsewhere.
Uncertain whether a clean data copy will succeed if relocated and a new CRC error occurs—consider checking cables or disabling the drive as a possible solution.
Hard mechanical drives, such as spinning hard disks, usually last 3 to 4 years before showing CRC errors due to wear, or they may misalign because servo motors no longer match the sector markers written on the disk.
This often requires using specialized software to reprogram the drive (low-level format).
Most such tools are no longer available.
Since Windows attempts repairs while idle, by the time CRC errors become visible, the drive is likely nearing the end of its life—provided the cable isn't loose, which is typical for SATA devices.
It's worth also checking if the SATA port on the faulty drive supports hot-swapping. If it does, a loose cable is more probable cause.

Pages (2): 1 2 Next