windows 10 BSOD with new ssd

Question

processor: Intel(r) core(tm) i9-9900K CPU @ 3.60GHz 3.6 GHz

Installed memory (ram): 32 GB

system type: 64-bit

Motherboard: MAG z390 tomahawk (MS-7B18)

Graphics card: NVIDIA GEForce RTX 2080

SSD: samsung ssd 970 evo plus 2TB

Ever since I added this new ssd to my computer i've had frequent blue screens of death and can not figure out how to fix it.

So far i ran samsung magician diagnostic tool it says driver is good.
I downloaded the new NVME drivers. Tried to download firmware. version 2B2QEXM7 says latest versions
Bought a heat sink.
I have several minidumps that I don't know hot to open and checked reliability viewer.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x0000000080000003, 0xfffff8031ea422d0, 0xffffc70e7f1f9db0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.

Problem signature
Problem Event Name: BlueScreen
Code: 3b
Parameter 1: c0000005
Parameter 2: fffff8056ae42321
Parameter 3: ffffdf0288286db0
Parameter 4: 0
OS version: 10_0_18363
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.18363.2.0.0.768.101
Locale ID: 1033

are some of the errors.

please help.

Answer 1

1. Download windbg.
2. If not yet configured point windbg to the symbol server so it can download symbol files. Paths are defined here. Note that you'll probably need to open a workspace first and ensure you save the workspace when you're done so you don't have to do it again.
3. Load the crash dump that Windows generated for the BSOD into windbg using Open Crash Dump option on File menu.
4. Run the command !analyze -show to have the debugger analyze the crash. Alternatively use !analyze -v.

What you should get besides the stop code is an assessment of where things went wrong and most importantly the module and call stack where it failed. This will point you to where the problem likely is. If the module and stack trace point to storage then the issue is with the SSD or immediate storage. If it is pointing to graphics or something else then the SSD itself is not the issue but may be causing a failure in another component. At that point I generally start googling for people who have had these kinds of problems (including the stop code as it is important).

Answer 2

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff80679867f03 - nt!KiReadyThread+33
[ 48:00 ]
1 error : !nt (fffff80679867f03)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

MEMORY_CORRUPTOR: ONE_BYTE

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ad110d6a-3b33-2c0a-c931-570eae1ba92d}

Followup: memory_corruption

---

the short end of the debugger i'm running the analyze on a few of the memory dumps

Answer 3

Ok this is getting a little above my head, but after reading through the debugger information. It appears that a game called Path of Exile is causing my system crash. However, i originally thought that my be the case and reinstalled it already. I'm searching online now for crash causes and fixes. I'll come back if the issue occurs again.

Answer 4

Hi,

I've had the same problem like the thread starter...

semms like smartscreen is causing my bsod.

any ideas what to do except disabling smartscreen?

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041202, The subtype of the bugcheck.
Arg2: ffffe6002869f020
Arg3: 000000000000e500
Arg4: ffff860748a77d80

Debugging Details:

---

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 1624

Key  : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on RSI

Key  : Analysis.DebugData
Value: CreateObject

Key  : Analysis.DebugModel
Value: CreateObject

Key  : Analysis.Elapsed.mSec
Value: 8460

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

Key  : Analysis.System
Value: CreateObject

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

ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

BUGCHECK_CODE: 1a

BUGCHECK_P1: 41202

BUGCHECK_P2: ffffe6002869f020

BUGCHECK_P3: e500

BUGCHECK_P4: ffff860748a77d80

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: smartscreen.exe

STACK_TEXT:
fffffb0dfd52f438 fffff80656a2006d : 000000000000001a 0000000000041202 ffffe6002869f020 000000000000e500 : nt!KeBugCheckEx
fffffb0dfd52f440 fffff80656a1e9c5 : 0000000000000000 0000000000000000 fffffb0dfd52f518 fffffb0dfd52f514 : nt!MiGetPageProtection+0x74d
fffffb0dfd52f4c0 fffff80656aa47ef : 0000000000000000 00000050d3e03000 0000000000040282 fffff80656a5e7ab : nt!MiQueryAddressState+0x4b5
fffffb0dfd52f6d0 fffff80656e3519c : fffffb0dfd520000 0000000000000000 ffff860700000000 ffff860700000000 : nt!MiQueryAddressSpan+0xcf
fffffb0dfd52f790 fffff80656e34945 : 0000000000000000 0000000000000000 0000000010000000 000000020819f290 : nt!MmQueryVirtualMemory+0x83c
fffffb0dfd52f940 fffff80656c074b5 : 0000000000000000 0000000000000000 0000000077566d4d fffffb0dfd52f9e8 : nt!NtQueryVirtualMemory+0x25
fffffb0dfd52f990 00007ff9e57aca84 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
000000020819eff8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff9`e57aca84

SYMBOL_NAME: nt!MiGetPageProtection+74d

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.804

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 74d

FAILURE_BUCKET_ID: 0x1a_41202_nt!MiGetPageProtection

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f0b0cf68-a44f-c0c2-6870-6a13e4de4705}

Followup: MachineOwner