Hi. . .
Below are the 2 RAM sticks that were in your system at the time of the BSOD with Bugcheck:
0x12b (ffffffffc00002c4,,,) = Faulty_hardware_corrupted_page caused by an unknown hardware component error likely related to "hardware memory"
Bugcheck
0X12b = Faulty_hardware_corrupted_page
NT Status Code (1st number inside the parenthesis of the full Bugcheck) =
0xffffffffc00002c4 =
hardware memory error
Many BSOD Analysts believe a "hardware memory error" to be RAM (physical memory). More below; near end.
You have 2 sticks of 16 GB RAM with the RAM stick specs listed below (from your Sysnative BSOD File zip output (Thank you!) that you provided in post #1.
For info, to get to 17+ GB when it is listed as a 16 GB RAM stick. . . (
EB after
16 = "
Extended Byte" (or "Extra Byte) by some); then the simple formula is used to figure out the number of bytes as seen by a Windows System:
Code:
2^64 = 16EB = 17,179,869,184 bytes
. . .(which matches the "Capacity below in the HTML chart).
Code:
2 Instances of Win32_PhysicalMemory
| Node | BankLabel | Capacity | DataWidth | Description | DeviceLocator | FormFactor | HotSwappable | InstallDate | InterleaveDataDepth | InterleavePosition | Manufacturer | MemoryType | Model | Name | OtherIdentifyingInfo | PartNumber | PositionInRow | PoweredOn | Removable | Replaceable | SerialNumber | SKU | Speed | Status | Tag | TotalWidth | TypeDetail | Version |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | |
DESKTOP-KEDQOKB | P0 CHANNEL A. | 17179869184 | 64 . | Physical Memory. | DIMM 0. | 8 . | . | . | . | . | Unknown. | 0 . | . | Physical Memory. | . | CMK32GX4M2E3200C16. | . | . | . | . | 00000000. | . | 2133 . | . | Physical Memory 0. | 64 . | 16512 . | . |
DESKTOP-KEDQOKB | P0 CHANNEL B. | 17179869184 . | 64 . | Physical Memory. | DIMM 0. | 8 . | . | . | . | . | Unknown. | 0 . | . | Physical Memory. | . | CMK32GX4M2E3200C16. | . | . | . | . | 00000000. | . | 2133 . | . | Physical Memory 2. | 64 . | 16512 . | . |
From the
systeminfo.txt file in the zip file -- this likely refers to the initial date that you turned on your new system and Windows took you through the install/setup procedure.
Code:
Original Install Date: 24/01/2023, 15:16:40
Did the Gigabyte Technology Co., Ltd. X570 GAMING X system come with Windows OEM version Windows 10 Pro or did you purchase the full retail copy of this same software?
Have you ever reinstalled Windows onto this system? If YES, what was the source of W10 Pro?
If not and the "Original Install Date" is
24/01/2023, be sure to contact the system manufacturer immediately to get on record that you are experiencing a huge issue with a ~6 month old system. Usually, you have up to one year for OEM warranty.
EDIT:
Code:
AllocatedBaseSize=4864
Caption=C:\pagefile.sys
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=20200808103705.539091+000
Name=C:\pagefile.sys
PeakUsage=0
Status=
TempPageFile=FALSE
From another file provided in the zip file "recoveros.txt" -- the above date of 08-08-2020 tells me that this was the original boot-up date of your new system or that Windows was reinstalled at that time. I believe your warranty has lapsed, but I would call anyway.
*** END EDIT ***
*** PLEASE FOLLOW ALL RECOMMENDATIONS OF OTHER BSOD ANALYSTS IN THIS THREAD. Thank you.
The minidump with bugcheck 0x1000007E (NTFS.SYS) you posted says: "this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK to check your drive(s) for errors.": chkdsk c: /scan /perf
I agree with @xilolee 100%. Bugcheck 0x24 NTFS FILE SYSTEM often points to an issue with the hard drive.
Remember that the NTSTATUS code (in P1) = 0xffffffffc00002c4 = hardware memory error ?
Now with the addition of a BSOD with Bugcheck 0x24, the internal hard drives need to be looked into as the "hardware memory error" being described during the processing of the BSOD dumps COULD BE indicating that there is a problem with a hard drive. Your OS drive is c:
When Windows is running, files, drivers, apps, etc... are constantly being written between RAM (physical memory) and c:\page file on the hard drive (virtual memory). Given that both are used as system memory (RAM much more often, of course) the possibility exists in my opinion that a hard drive could be involved.
Please run SEA TOOLS FOR DOS on each drive - except D: - and see what the results are. You never know!
Rich (BB code):
------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 72.8 GB Drive: G:
Total Space: 228.2 GB Free Space: 69.1 GB
File System: NTFS Total Space: 228.2 GB
Model: CT240BX500SSD1 File System: FAT32
Model: n/a
Drive: D:
Free Space: 0.1 GB Drive: S:
Total Space: 0.1 GB Free Space: 463.4 GB
File System: NTFS Total Space: 953.9 GB
Model: ST2000DM001-1ER164 File System: NTFS
Model: CT1000BX500SSD1
Drive: E:
Free Space: 1239.8 GB
Total Space: 1907.1 GB
File System: NTFS
Model: ST2000DM001-1ER164
*** PLEASE FOLLOW ALL RECOMMENDATIONS OF OTHER BSOD ANALYSTS IN THIS THREAD. Thank you.
Regards. . .
jcgriff2
