Question Windows crashes constantly and I've no idea where to start ?

[Madster]

System:
OS: Windows 10, 10.0, version 2009, build: 19045
Motherboard: ASUSTeK COMPUTER INC., PRIME X470-PRO
CPU Name: AuthenticAMD AMD Ryzen 7 5800x 8-Core Processor
CPU Model: Family: 00, Model: 00, Stepping: 0, Ext. Family: 19, Ext.Model: 21, Rev:
Clock Speed: 3793 MHz(base), bus speed: 100 MHz
Processors: 16 logical processors, 1 group(s)
RAM: 75 MB total
System Drive: C: 931 GB total, 251 GB available (27.0%) (SSD)

What is happening?
When I load up a game, primarily Overwatch, sometimes it plays just fine, sometimes the screen completely freezes, the audio starts skipping, then audio drops. The computer will stay frozen until I restart it. Sometimes on restart, the PC boots up, but the monitors do not detect anything. When this happens, I have to flip the switch on my PSU, then restart and all is working fine.

Running WhoCrashed:

Crash dump file:	C:\Windows\Minidump\050124-8765-01.dmp (Minidump)
Bugcheck code:	0x1A(0x3F, 0x1A3, 0x2C0CCAB8, 0x5D12F491)
Bugcheck name:	MEMORY_MANAGEMENT
Driver or module in which error occurred:	FLTMGR.SYS (FLTMGR+0x4A43)
File path:	FLTMGR.SYS
Description:	Microsoft Filesystem Filter Manager
Product:	Microsoft® Windows® Operating System
Company:	Microsoft Corporation
Bug check description:	This indicates that a severe memory management error occurred.
Analysis:	This is possibly a software problem. This is likely a case of memory corruption. This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues The crash took place in a file system driver. Since there is no other responsible driver detected, 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.

Event Viewer errors:

Error 1:
The GameInput Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service.

Error 2:
The GameInput Service service terminated with the following error:
The compound file GameInput Service was produced with a newer version of storage.

I also cant update windows?:
Installation Failure: Windows failed to install the following update with error 0x8024200B: 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441).


Edit: All drivers are up to date as of now 05/2/2024.

 

[kanewolf]

System:
OS: Windows 10, 10.0, version 2009, build: 19045
Motherboard: ASUSTeK COMPUTER INC., PRIME X470-PRO
CPU Name: AuthenticAMD AMD Ryzen 7 5800x 8-Core Processor
CPU Model: Family: 00, Model: 00, Stepping: 0, Ext. Family: 19, Ext.Model: 21, Rev:
Clock Speed: 3793 MHz(base), bus speed: 100 MHz
Processors: 16 logical processors, 1 group(s)
RAM: 75 MB total
System Drive: C: 931 GB total, 251 GB available (27.0%) (SSD)

What is happening?
When I load up a game, primarily Overwatch, sometimes it plays just fine, sometimes the screen completely freezes, the audio starts skipping, then audio drops. The computer will stay frozen until I restart it. Sometimes on restart, the PC boots up, but the monitors do not detect anything. When this happens, I have to flip the switch on my PSU, then restart and all is working fine.

Running WhoCrashed:

Crash dump file:	C:\Windows\Minidump\050124-8765-01.dmp (Minidump)
Bugcheck code:	0x1A(0x3F, 0x1A3, 0x2C0CCAB8, 0x5D12F491)
Bugcheck name:	MEMORY_MANAGEMENT
Driver or module in which error occurred:	FLTMGR.SYS (FLTMGR+0x4A43)
File path:	FLTMGR.SYS
Description:	Microsoft Filesystem Filter Manager
Product:	Microsoft® Windows® Operating System
Company:	Microsoft Corporation
Bug check description:	This indicates that a severe memory management error occurred.
Analysis:	This is possibly a software problem. This is likely a case of memory corruption. This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues The crash took place in a file system driver. Since there is no other responsible driver detected, 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.

Event Viewer errors:

Error 1:
The GameInput Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service.

Error 2:
The GameInput Service service terminated with the following error:
The compound file GameInput Service was produced with a newer version of storage.

I also cant update windows?:
Installation Failure: Windows failed to install the following update with error 0x8024200B: 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441).

Since you have a memory management error listed, I would start by running memtest86 for overnight.

 

[Madster]

Since you have a memory management error listed, I would start by running memtest86 for overnight.

Hey, thanks for the suggestion. All RAM sticks have been tested overnight, individually:


Test 1:
2024-05-12 07:38:47 - Test result: PASS (Errors: 0)
2024-05-12 09:04:16 - Display test result summary
2024-05-12 09:04:33 - Saving test report to MemTest86-Report-20240512-034516.html
2024-05-12 09:04:33 - poll_timings_ryzen - [MC0] DramConfiguration=00000100
2024-05-12 09:04:33 - poll_timings_ryzen - [MC0] DebugMisc=000000C8
2024-05-12 09:04:33 - poll_timings_ryzen - [MC1] DramConfiguration=00000520
2024-05-12 09:04:33 - poll_timings_ryzen - [MC1] DebugMisc=000000F8
2024-05-12 09:04:34 - Test report was successfully saved


Test 2:
2024-05-12 13:04:47 - Test result: PASS (Errors: 0)
2024-05-12 20:44:25 - Display test result summary
2024-05-12 20:44:32 - Saving test report to MemTest86-Report-20240512-091118.html
2024-05-12 20:44:32 - poll_timings_ryzen - [MC0] DramConfiguration=00000100
2024-05-12 20:44:32 - poll_timings_ryzen - [MC0] DebugMisc=000000C8
2024-05-12 20:44:32 - poll_timings_ryzen - [MC1] DramConfiguration=00000520
2024-05-12 20:44:32 - poll_timings_ryzen - [MC1] DebugMisc=000000F8
2024-05-12 20:44:32 - Test report was successfully saved

 

[kanewolf]

Hey, thanks for the suggestion. All RAM sticks have been tested overnight, individually:


Test 1:
2024-05-12 07:38:47 - Test result: PASS (Errors: 0)
2024-05-12 09:04:16 - Display test result summary
2024-05-12 09:04:33 - Saving test report to MemTest86-Report-20240512-034516.html
2024-05-12 09:04:33 - poll_timings_ryzen - [MC0] DramConfiguration=00000100
2024-05-12 09:04:33 - poll_timings_ryzen - [MC0] DebugMisc=000000C8
2024-05-12 09:04:33 - poll_timings_ryzen - [MC1] DramConfiguration=00000520
2024-05-12 09:04:33 - poll_timings_ryzen - [MC1] DebugMisc=000000F8
2024-05-12 09:04:34 - Test report was successfully saved


Test 2:
2024-05-12 13:04:47 - Test result: PASS (Errors: 0)
2024-05-12 20:44:25 - Display test result summary
2024-05-12 20:44:32 - Saving test report to MemTest86-Report-20240512-091118.html
2024-05-12 20:44:32 - poll_timings_ryzen - [MC0] DramConfiguration=00000100
2024-05-12 20:44:32 - poll_timings_ryzen - [MC0] DebugMisc=000000C8
2024-05-12 20:44:32 - poll_timings_ryzen - [MC1] DramConfiguration=00000520
2024-05-12 20:44:32 - poll_timings_ryzen - [MC1] DebugMisc=000000F8
2024-05-12 20:44:32 - Test report was successfully saved

Individual DIMM testing is not as good as testing all at once. There could be incompatabilities between DIMMs.

 

[Madster]

Individual DIMM testing is not as good as testing all at once. There could be incompatabilities between DIMMs.

Even if its the same ram, purchased together?

I did also run a test with both, which also passed. This is not a new build by any means. Pushing on probably 5+ years now with no issues until recently.

 

[ubuysa]

A MEMORY_MANAGEMENT bugcheck is not always a RAM problem - though that's the obvious place to start. The other key information in your post if that the WIndows fltmgr.sys driver was flagged as the faulting driver. It's not at fault of course, because it's a Microsoft driver, but this driver manages many third-party filter drivers and it's likely that one of these caused the BSOD. We need to see the dumps at least but it would be wise to get some detailed troubleshooting data.

Can you please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

 

[Madster]

A MEMORY_MANAGEMENT bugcheck is not always a RAM problem - though that's the obvious place to start. The other key information in your post if that the WIndows fltmgr.sys driver was flagged as the faulting driver. It's not at fault of course, because it's a Microsoft driver, but this driver manages many third-party filter drivers and it's likely that one of these caused the BSOD. We need to see the dumps at least but it would be wise to get some detailed troubleshooting data.

Can you please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

Does this typically take a while to run? Says it's not hung, but its been about 20 minutes.

 

[Madster]

A MEMORY_MANAGEMENT bugcheck is not always a RAM problem - though that's the obvious place to start. The other key information in your post if that the WIndows fltmgr.sys driver was flagged as the faulting driver. It's not at fault of course, because it's a Microsoft driver, but this driver manages many third-party filter drivers and it's likely that one of these caused the BSOD. We need to see the dumps at least but it would be wise to get some detailed troubleshooting data.

Can you please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

https://drive.google.com/drive/folders/1N4CzsElGdCdjpdBzJwcIcyrPwHwlW3WJ?usp=sharing

Go ahead and request access and ill grant. I didn't mess with anything inside of the zip, so all original for you.

 

[ubuysa]

I prefer no to distribute my email address in this way. Please make it public (anyone with the link). There is nothing sensitive in there.

 

[Bob.B]

System:
OS: Windows 10, 10.0, version 2009, build: 19045
Motherboard: ASUSTeK COMPUTER INC., PRIME X470-PRO
CPU Name: AuthenticAMD AMD Ryzen 7 5800x 8-Core Processor
CPU Model: Family: 00, Model: 00, Stepping: 0, Ext. Family: 19, Ext.Model: 21, Rev:
Clock Speed: 3793 MHz(base), bus speed: 100 MHz
Processors: 16 logical processors, 1 group(s)
RAM: 75 MB total
System Drive: C: 931 GB total, 251 GB available (27.0%) (SSD)

What is happening?
When I load up a game, primarily Overwatch, sometimes it plays just fine, sometimes the screen completely freezes, the audio starts skipping, then audio drops. The computer will stay frozen until I restart it. Sometimes on restart, the PC boots up, but the monitors do not detect anything. When this happens, I have to flip the switch on my PSU, then restart and all is working fine.

Running WhoCrashed:

Crash dump file:	C:\Windows\Minidump\050124-8765-01.dmp (Minidump)
Bugcheck code:	0x1A(0x3F, 0x1A3, 0x2C0CCAB8, 0x5D12F491)
Bugcheck name:	MEMORY_MANAGEMENT
Driver or module in which error occurred:	FLTMGR.SYS (FLTMGR+0x4A43)
File path:	FLTMGR.SYS
Description:	Microsoft Filesystem Filter Manager
Product:	Microsoft® Windows® Operating System
Company:	Microsoft Corporation
Bug check description:	This indicates that a severe memory management error occurred.
Analysis:	This is possibly a software problem. This is likely a case of memory corruption. This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues The crash took place in a file system driver. Since there is no other responsible driver detected, 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.

Event Viewer errors:

Error 1:
The GameInput Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service.

Error 2:
The GameInput Service service terminated with the following error:
The compound file GameInput Service was produced with a newer version of storage.

I also cant update windows?:
Installation Failure: Windows failed to install the following update with error 0x8024200B: 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441).


Edit: All drivers are up to date as of now 05/2/2024.

How do you get 75MB of ram?

 

[Madster]

I prefer no to distribute my email address in this way. Please make it public (anyone with the link). There is nothing sensitive in there.

https://drive.google.com/file/d/1cUawjZ_utaiNHUcUdcDW6-9JUeQilfdp/view?usp=sharing

Here is public.

 

[Madster]

The crashes are becoming more and more frequent.

I was just browsing the web with two tabs open and the entire pc freezes. it will stay like this until i force reset it.

 

[Madster]

It’s dead. I’ve rebooted(counted) 67 times. It posted, started loading into windows, but crashed. Can’t get it to post at all anymore.

GGs.

 

[ubuysa]

The five dumps you uploaded all have different bugchecks. Four would seem to be graphics related, because all fail during graphical operations...

0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (there are two of these)
0x10E VIDEO_MEMORY_MANAGEMENT_INTERNAL
0x119 VIDEO_SCHEDULER_INTERNAL_ERROR

Ordinarily we'd be suggesting focusing on the graphics driver nvlddmkm.sys and/or the graphics card. However, the fifth dump is different and probably more useful...

0x1A MEMORY_MANAGEMENT
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 000000000000003f, An inpage operation failed with a CRC error. Parameter 2 contains
    the pagefile offset. Parameter 3 contains the page CRC value.
    Parameter 4 contains the expected CRC value.
Arg2: 00000000000001a3
Arg3: 000000002c0ccab8
Arg4: 000000005d12f491

This particular BSOD happened because a page-in operation failed with a CRC error, as you can see from the dump triage above. The dump triage also makes it clear what happened...

ADDITIONAL_DEBUG_TEXT:  Memory Manager detected corruption of a pagefile page while performing an in-page operation.
The data read from storage does not match the original data written.
This indicates the data was corrupted by the storage stack, or device hardware.

The problem here then could be RAM, but you say you've tested ALL RAM sticks, yet you have only two 16GB sticks installed in these dumps. Also, in your OP you talk about having 75MB in total, which is a complete nonsense of course. Where did that figure come from I wonder?

Anyway, let's assume that your RAM is probably OK, as Memtst86 suggests. In addition I see no indication in the logs of bad RAM. That leaves the paging drive, which is your system drive; the Samsung 970 EVO NVMe SSD. That it's now crashing all the time strengthens my thinking that this may be a bad NVMe SSD.

M.2 ports seem a tad less reliable than others, so try removing the Samsung 970 EVO and re-seating it properly (at an angle as you insert it). You may need to replace the heat sink pad when you do this - if you have one.

See whether that helps?

 

[Madster]

The five dumps you uploaded all have different bugchecks. Four would seem to be graphics related, because all fail during graphical operations...

0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (there are two of these)
0x10E VIDEO_MEMORY_MANAGEMENT_INTERNAL
0x119 VIDEO_SCHEDULER_INTERNAL_ERROR

Ordinarily we'd be suggesting focusing on the graphics driver nvlddmkm.sys and/or the graphics card. However, the fifth dump is different and probably more useful...

0x1A MEMORY_MANAGEMENT
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 000000000000003f, An inpage operation failed with a CRC error. Parameter 2 contains
    the pagefile offset. Parameter 3 contains the page CRC value.
    Parameter 4 contains the expected CRC value.
Arg2: 00000000000001a3
Arg3: 000000002c0ccab8
Arg4: 000000005d12f491

This particular BSOD happened because a page-in operation failed with a CRC error, as you can see from the dump triage above. The dump triage also makes it clear what happened...

ADDITIONAL_DEBUG_TEXT:  Memory Manager detected corruption of a pagefile page while performing an in-page operation.
The data read from storage does not match the original data written.
This indicates the data was corrupted by the storage stack, or device hardware.

The problem here then could be RAM, but you say you've tested ALL RAM sticks, yet you have only two 16GB sticks installed in these dumps. Also, in your OP you talk about having 75MB in total, which is a complete nonsense of course. Where did that figure come from I wonder?

Anyway, let's assume that your RAM is probably OK, as Memtst86 suggests. In addition I see no indication in the logs of bad RAM. That leaves the paging drive, which is your system drive; the Samsung 970 EVO NVMe SSD. That it's now crashing all the time strengthens my thinking that this may be a bad NVMe SSD.

M.2 ports seem a tad less reliable than others, so try removing the Samsung 970 EVO and re-seating it properly (at an angle as you insert it). You may need to replace the heat sink pad when you do this - if you have one.

See whether that helps?

Would a bad nvme cause bios to freeze?

I was finally able to boot into bios. But after about 30 seconds, the entire screen froze up just as it does when in windows. It never restarts itself, I would have to manually restart it. This makes me think it’s a cpu or motherboard dying on me.

I gave it one last boot this morning, was able to get into windows for about 5 minutes, and then same thing again, all screens freeze, and have to manually reboot.

 

[ubuysa]

It's definitely hardware then. The BIOS setup is pretty self-contained so my initial suspect in that case would be the PSU.