I keep getting BSOD when playing games after installing new SSD

Question

I keep getting BSOD when playing games after installing new SSD

A.H Rafi 20

I've recently purchased a new m.2 NVMe (BIWINTECH 512GB) and Installed Win (10) on it. Have a 2TB HDD. But after installing SSD on my PC, I keep getting BSOD when trying to play games specially ( The Quarry and Hogwarts Legacy). These games used to run okay with only HDD installed.

I tried installing the game on both SSD and HDD but same result.
Tried page file on HDD/SSD.
Updated all of my drivers
Went back to old drivers for GPU
Checked SSD health, no prob was found
Did fresh windows installation
Performed memory with Memtest86, All okay and no error was found

I am out of options now, please someone help me with this.

------------------
System Information
------------------
             Machine name: DESKTOP-29J41O6
               Machine Id: {75E8D082-B9B1-44F9-A061-D5DD5F0A8DF5}
         Operating System: Windows 10 Pro N 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406)
                 Language: English (Regional Setting: English)
      System Manufacturer: Gigabyte Technology Co., Ltd.
             System Model: B150M-D3H
                     BIOS: F24 (type: UEFI)
                Processor: Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz (4 CPUs), ~3.3GHz
                   Memory: 16384MB RAM
      Available OS Memory: 16332MB RAM
                Page File: 6338MB used, 45992MB available
              Windows Dir: C:\Windows
          DirectX Version: DirectX 12
      DX Setup Parameters: Not found
         User DPI Setting: 96 DPI (100 percent)
       System DPI Setting: 96 DPI (100 percent)
          DWM DPI Scaling: Disabled
                 Miracast: Available, no HDCP
Microsoft Graphics Hybrid: Not Supported

Event log:

Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          3/22/2023 8:34:35 PM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (70368744177664),(2)
User:          SYSTEM
Computer:      DESKTOP-29J41O6
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
    <EventID>41</EventID>
    <Version>8</Version>
    <Level>1</Level>
    <Task>63</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000400000000002</Keywords>
    <TimeCreated SystemTime="2023-03-22T14:34:35.6321061Z" />
    <EventRecordID>1058</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>DESKTOP-29J41O6</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="BugcheckCode">0</Data>
    <Data Name="BugcheckParameter1">0x0</Data>
    <Data Name="BugcheckParameter2">0x0</Data>
    <Data Name="BugcheckParameter3">0x0</Data>
    <Data Name="BugcheckParameter4">0x0</Data>
    <Data Name="SleepInProgress">0</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
    <Data Name="BootAppStatus">0</Data>
    <Data Name="Checkpoint">0</Data>
    <Data Name="ConnectedStandbyInProgress">false</Data>
    <Data Name="SystemSleepTransitionsToOn">1</Data>
    <Data Name="CsEntryScenarioInstanceId">0</Data>
    <Data Name="BugcheckInfoFromEFI">false</Data>
    <Data Name="CheckpointStatus">0</Data>
    <Data Name="CsEntryScenarioInstanceIdV2">0</Data>
    <Data Name="LongPowerButtonPressDetected">false</Data>
  </EventData>
</Event>

DxDiag.txt SSD health.jpg Bluescreen view.jpg

Michael Taylor 60,326 Reputation points

2023-03-22T19:24:10.2033333+00:00

This seems to indicate a potential BIOS issue. Are you overclocking your machine? If so then don't and see if the issue goes away. Also ensure you're running the latest BIOS update for your machine. If you've also replaced memory then there could be a memory clock speed issue with the MB or perhaps mismatched latency that is causing hardware failures.
A.H Rafi 20 Reputation points

2023-03-23T15:24:42.93+00:00

Another crash report says different thing

crash again.jpg
A.H Rafi 20 Reputation points

2023-03-23T15:30:47.95+00:00

No. Im not overclocking, and i've updated my bios with the latest one i've found on Gigabyte website. Since yesterday, after BSOD, my PC can't find the boot device (the SSD). but if i turn off and on the main power line..then it comes back.

And no, i have not replaced any memory.
Michael Taylor 60,326 Reputation points

2023-03-23T17:48:00.29+00:00

This sounds like either a bad NVMe port on the motherboard or a bad SSD. If you have another NVMe port then move the SSD to that one (you'll probably have to repair the Windows install after that). Otherwise try using a different SSD on the same port.
A.H Rafi 20 Reputation points

2023-03-24T04:29:34.8033333+00:00

Please note its only happening with 2 games, Other games run fine plus everything else is. But those 2 games doesn't give BSOD if windows is on HDD
Michael Taylor 60,326 Reputation points

2023-03-24T13:18:07.1133333+00:00

Bad circuits/chips on the SSD can cause some areas of the drive to be bad. A game won't BS Windows. No software outside kernel software can do that. Thus the issue isn't with the games but whatever kernel software those games may be using that ultimately is failing (graphics, DRM, memory, storage, etc). It is quite possible the games are using up so much memory that it is being paged out and the page file is using bad space on the disk. There are countless ways this can go wrong. Again, we're guessing at the potential cause and provided ways to test it. All you can do is test it and see.

Accepted answer

4 additional answers

Your answer

Michael Taylor 60,326 Reputation points

2023-03-22T19:24:10.2033333+00:00

This seems to indicate a potential BIOS issue. Are you overclocking your machine? If so then don't and see if the issue goes away. Also ensure you're running the latest BIOS update for your machine. If you've also replaced memory then there could be a memory clock speed issue with the MB or perhaps mismatched latency that is causing hardware failures.
A.H Rafi 20 Reputation points

2023-03-23T15:24:42.93+00:00

Another crash report says different thing

crash again.jpg
A.H Rafi 20 Reputation points

2023-03-23T15:30:47.95+00:00

No. Im not overclocking, and i've updated my bios with the latest one i've found on Gigabyte website. Since yesterday, after BSOD, my PC can't find the boot device (the SSD). but if i turn off and on the main power line..then it comes back.

And no, i have not replaced any memory.
Michael Taylor 60,326 Reputation points

2023-03-23T17:48:00.29+00:00

This sounds like either a bad NVMe port on the motherboard or a bad SSD. If you have another NVMe port then move the SSD to that one (you'll probably have to repair the Windows install after that). Otherwise try using a different SSD on the same port.
A.H Rafi 20 Reputation points

2023-03-24T04:29:34.8033333+00:00

Please note its only happening with 2 games, Other games run fine plus everything else is. But those 2 games doesn't give BSOD if windows is on HDD
Michael Taylor 60,326 Reputation points

2023-03-24T13:18:07.1133333+00:00

Bad circuits/chips on the SSD can cause some areas of the drive to be bad. A game won't BS Windows. No software outside kernel software can do that. Thus the issue isn't with the games but whatever kernel software those games may be using that ultimately is failing (graphics, DRM, memory, storage, etc). It is quite possible the games are using up so much memory that it is being paged out and the page file is using bad space on the disk. There are countless ways this can go wrong. Again, we're guessing at the potential cause and provided ways to test it. All you can do is test it and see.

Answer 1

The BSOD says a critical process died. Unfortunately it doesn't have much useful information but that would lead me to believe a core OS process failed and that brough the system down. Really you need the crash dump analysis. Go to the MS store and download WinDbg Preview from Microsoft.

After it is installed then run it. On the File menu select the option to open a dump file. Click browse and go to C:\windows\minidumpwhich is the default location where crash dump files should be generated. Within here should be a series of .dmp or .mdmp files which are the crash dumps. Load up one that matches when you had a BSOD. After it loads type !analyze -v in the command window to have it analyze the crash. If you're lucky it'll tell you what went wrong and hopefully the likely process that caused it. What is important for debugging these types of things is the actual error, the stack trace that it generated and any analyze information like the potential process. This will help identify the issue.

One possible cause is that your SSD is bad (it happens) so swapping out drives may resolve the issue. Another problem could be the MBs interface to it. But with just the information given it would be hard to pinpoint anything.

Answer 2

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`40a00000 PsLoadedModuleList = 0xfffff800`4162a310
Debug session time: Thu Mar 23 00:17:22.007 2023 (UTC + 6:00)
System Uptime: 0 days 0:53:44.648
Loading Kernel Symbols
...............................................................
.......Page 40c7c7 not present in the dump file. Type ".hh dbgerr004" for details
.........................................................
..........................................
Loading User Symbols

Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`40dfa110 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff810f`7d250390=0000000000000124
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000010, Device Driver Error
Arg2: ffffdb023658b028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffffdb02214ad92c
Arg4: ffffdb022147c1a0

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3296

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3360

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 1718

    Key  : Analysis.Init.Elapsed.mSec
    Value: 13477

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 90

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x124

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x124

    Key  : Bugcheck.Code.Register
    Value: 0x124

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  124

BUGCHECK_P1: 10

BUGCHECK_P2: ffffdb023658b028

BUGCHECK_P3: ffffdb02214ad92c

BUGCHECK_P4: ffffdb022147c1a0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

STACK_TEXT:  
ffff810f`7d250388 fffff800`40fb8a4c     : 00000000`00000124 00000000`00000010 ffffdb02`3658b028 ffffdb02`214ad92c : nt!KeBugCheckEx
ffff810f`7d250390 fffff800`40fb95a9     : ffffdb02`2ed97090 ffffdb02`2ed97090 ffffdb02`214ad900 ffffdb02`36576168 : nt!WheaReportHwError+0x3ec
ffff810f`7d250470 fffff800`40fb96c5     : 00000000`00000000 00000000`00000062 ffffdb02`2ed97090 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffff810f`7d2504a0 fffff800`429237b1     : 00000000`00000000 ffff810f`7d2506c0 ffffdb02`2147c1a0 01000000`00100000 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffff810f`7d250500 fffff800`4291cb80     : 00000000`00000000 ffffdb02`2147c1a0 ffffdb02`214851a0 00000000`00000001 : storport!StorpWheaReportError+0x9d
ffff810f`7d250590 fffff800`428ef07c     : 00000000`00000000 ffffffff`fffe7960 00000000`00000000 00000000`00000000 : storport!StorpMarkDeviceFailed+0x358
ffff810f`7d250820 fffff800`428ac33d     : fffff800`41725440 ffffdb02`21483020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x91c
ffff810f`7d2508f0 fffff800`428af55a     : ffffdb02`00000001 00000000`c1000002 ffffdb02`21483020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffff810f`7d250970 fffff800`428ae4af     : ffffdb02`21483020 ffffdb02`2147c050 ffffdb02`3018d880 80000000`00002000 : stornvme!NVMeControllerReset+0x10a
ffff810f`7d2509a0 fffff800`4291a276     : ffffdb02`3018d880 ffffdb02`2147c050 ffffdb02`21445040 ffffdb02`1fa89c30 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffff810f`7d2509d0 fffff800`40c07df5     : ffffdb02`35410530 ffffdb02`35410530 ffffdb02`2147c050 fffff800`421ac5c0 : storport!StorPortWorkItemRoutine+0x46
ffff810f`7d250a00 fffff800`40cbdef5     : ffffdb02`214ce080 ffffdb02`214ce080 fffff800`40c07cc0 ffffdb02`00000000 : nt!IopProcessWorkItem+0x135
ffff810f`7d250a70 fffff800`40c55485     : ffffdb02`214ce080 00000000`00000080 ffffdb02`1faa6080 000fa4ef`bd9bbfff : nt!ExpWorkerThread+0x105
ffff810f`7d250b10 fffff800`40e02d48     : ffffc981`8ada8180 ffffdb02`214ce080 fffff800`40c55430 25ce6e22`8131c28c : nt!PspSystemThreadStartup+0x55
ffff810f`7d250b60 00000000`00000000     : ffff810f`7d251000 ffff810f`7d24a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {37af9407-4a3e-0b08-acdd-dadffdc34c3c}

Followup:     MachineOwner
---------

Michael Taylor 60,326 Reputation points

2023-03-22T19:42:37.8933333+00:00

Refer to the following recommendations. Points to a hardware issue. Given this is an NVMe then it could be a bad connection or faulty connection on the MB, a BIOS issue or something else failing. If you have a different SSD you could try using that to see if the problem goes away. If you use another NVMe and the problem goes away it was likely a drive issue or a bad connection. If it still happens then switch to a SATA SSD (or use the other NVMe port if you have one). If the problem goes away then it leans towards a problem with the MB port.

Answer 3

Docs 15,761

Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

https://www.elevenforum.com/t/bsod-posting-instructions.103/

A.H Rafi 20 Reputation points

2023-03-23T15:38:07.4333333+00:00

https://1drv.ms/u/s!Av7NGpaoY-lNgWmg7iFKoplyHIEc?e=gjEu2y

I can't post there. New registration is currently not available

Answer 4

John Griffith 0

Hi. . .

"a critical process died" is almost always related to a faulty hard drive - SSD or HDD.

If you have an SSD, go to the SSD manufacturer's support site and check for a firmware update.

Regards. . .

jcgriff2

Microsoft MVP, 2009-2021 (Ret.)

Docs 15,761 Reputation points

2023-06-29T06:27:57.5566667+00:00

The new Windows installation displayed piracy / crack.

Please clean install Windows so that the installation is properly licensed / activated.

Answer 5

xxdolcexx 0

something wrong with write buffer on your device (on board cache), you might want to turn it off if its unstable

open device manager, under disk drives find your drive and double click it to get to properties, switch tab to Policies and disable write cache

and if your ssd is your main C:

you get bsod your drive is schutting down

i have Same prob whth my drive k: and j: nvme ssd so try tis and see if that works

Share via

I keep getting BSOD when playing games after installing new SSD

4 additional answers

Your answer