Constant Crashes

[HSlatter]

So built up a new(ish) pc recently Ryzen 5 7600x crucial 32gb ram MSI b650m-a pro motherboard and recently I've experienced a lot of crashes I've been playing the finals for a few weeks and out of the blue mid game it would crash and show a blue screen its stopped showing the bluescreen now and just goes to black I turned the ram from 5600 to 4800 and it seemed ok I played a few games no problem then I returned it to 5200 MHz problem stared again went to 4800 problem persisted instead of fixing Note that it had yet to happen in any other games yet as I wasn't playing anything played some Fireteams elite no problem then tried some DRL (drone flying game) and it crashed like usual so I don't think its any specific game though most noticeable on the finals Id really appreciate some help on fixing the problem no XMP profile running I think new bios is confusing a tad and I even locked my CPU to 4.7 ghz to see if that was a problem again no difference, I have ran cinebench for an hour no problem and I ran Superstition benchmark for 30 mins no problem running out of ideas would really appreciate some help.

 

SysnativeFileCollectionApp.zip

Edited December 28, 2023 by HSlatter

[problemsolver]

17 minutes ago, HSlatter said:

So built up a new(ish) pc recently Ryzen 5 7600x crucial 32gb ram MSI b650m-a pro motherboard and recently I've experienced a lot of crashes I've been playing the finals for a few weeks and out of the blue mid game it would crash and show a blue screen its stopped showing the bluescreen now and just goes to black I turned the ram from 5600 to 4800 and it seemed ok I played a few games no problem then I returned it to 5200 MHz problem stared again went to 4800 problem persisted instead of fixing Note that it had yet to happen in any other games yet as I wasn't playing anything played some Fireteams elite no problem then tried some DRL (drone flying game) and it crashed like usual so I don't think its any specific game though most noticeable on the finals Id really appreciate some help on fixing the problem no XMP profile running I think new bios is confusing a tad and I even locked my CPU to 4.7 ghz to see if that was a problem again no difference, I have ran cinebench for an hour no problem and I ran Superstition benchmark for 30 mins no problem running out of ideas would really appreciate some help.

Please post the dumps if possible.

[Bjoolz]

Please reply back if you don't have dump files as well. WHEA crashes means a hardware issue with the CPU or a PCIe device, the most common culprit these days is the NVMe SSD. If the SSD goes offline because of the crash, it can't write the data needed for the dump file. If it freezes on the BSOD screen, I see that it's on 0% in both screenshots, that's an indication that it's not able to write any data which in turn indicates that it's the SSD. 

 

On a new build I would first re-seat the NVMe SSD. To confirm if it's the SSD or not (Note that we can't tell the difference between the M.2 slot/motherboard and the SSD, but a faulty SSD is way more common) we have two options. We can move the page file to a different drive as this is where it writes the data before creating a dump file using that data on the next boot. You don't have to change the location of where it writes the dump file itself. You should now get dump files to share. The second option is to add a registry value so that we can see the parameters of the crash right on the BSOD screen.

 

"We need to see the arguments of the BSOD crash (Think of them as sub-errors). If it already hangs on the BSOD screen (As you can't get dump files) then this step is not necessary, but if it reboots normally after a few seconds then go to the guide for changing dump type posted by the bot (Top comment usually) and on this screen remove the check for automatically restart. To restart manually, just use the power button.

 

To make the BSOD screen display the additional info on the BSOD screen we need to add a field to the registry. If you are not comfortable editing the registry then do not do this step. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl, right click on the empty area on the right section and select New → DWORD value with the name "DisplayParameters". Right click on it, modify and set the value data to 1 (Does not matter if you use Hexadecimal or Decimal). It should look like this once done. Reboot to apply the registry change.

 

The next time you BSOD, you should have these extra numbers in the top left corner.

If Arg1 is 0x0000000000000010 then Windows is blaming the NVMe SSD. Again, note that it can't tell the difference between the SSD and M.2 slot/motherboard."

[HSlatter]

12 hours ago, problemsolver said:

Please post the dumps if possible.

Have just attached them to the main post and to this message here.

 

SysnativeFileCollectionApp.zip

[HSlatter]

On 12/28/2023 at 12:41 AM, problemsolver said:

Please post the dumps if possible.

Let me know if this is right

 

SysnativeFileCollectionApp.zip

[Bjoolz]

On 1/4/2024 at 12:54 AM, HSlatter said:

Let me know if this is right

 

SysnativeFileCollectionApp.zip 468.25 kB · 3 downloads

There are no dump files included which makes the NVMe the main suspect.