Windows 10: NVME BSOD

Hi There,


I have been having an issue with my NVME SSD since installed it about 3 weeks ago.


Everything runs perfectly well, until i play any game. between 5 minutes and half an hour of any game being played my computer crashes. this did not happen before i installed this nvme ssd on my pc.


I have tried everything. Here is a list:

• remove all sata connections
• switch GPU PCI-E lanes
• bought new ram was upgrading my ram anyway
• ran diagnostic tools Samsung magician for my 970 evo plus
• updated all drivers
• chkdsk this made my computer bluescreen while it was completing, but it did complete and found nothing lol
• monitoring cpu and gpu temps:
  • have a z63 so I get the temps at crash time, the highest for these are cpu 35 gpu 60 but more the time it runs at cpu 25 gpu 55 which should not cause crashes.
• Firmware updates for evo and mobo

My guess, it it could be something wrong with the EVO 970, but running diagnostics from Samsung magician which can be quite in-depth shows nothing. this plus the fact it is brand new and the errors im getting like watchdog timeout and a few others I cant remember off the top of my head are all memory related.


I believe this is a problem maybe to do with how my mobo is ingesting data to the cpu/ram from the evo but I have no way of knowing for sure. My mobo is 4 channel though so I don't know why it would be corrupting data this way. My main guess at this point, is that it could be sharing lanes with the GPU at some stage, because gaming and rarely watching netflix is when this occours, it could be sharing the PCIE lane with the M.2 slot, but as i said before, i tried a separate pcie slot on the mobo and i still got the same error.


I am all out of ideas. I would really appreciate if someone, anyone had any suggestions for things I have not tried


Here are my computer specs:


CPU: 6800k i7 hex core LGA 2011-3 not overclocked, will be moving to amd as soon as a 5000 becomes available

Mobo: Fatality gaming x99 i7 https://www.asrock.com/mb/Intel/Fatal1ty%20X99%20Professional%20Gaming%20i7/index.asp

RAM: 32gb Corsair vengeance at 3600 mhz

GPU 1080 upgrading to 3070 soon

2x SSD

2x HDD

1x Evo970 Nvme M.2 SSD


Let me know if you need any more info <3

:)

 

Windows 10 installer don't detect NVMe drive

I have 2 drives:

• disk1 (SATA SSD, with Ubuntu 16.04)
  • partition1 (sda1: flag /boot)
  • partition2 (sda2: flag /home, encrypted by LUKS)
• disk2 (NVMe SSD)

So, the goal is to install Windows 10 on disk2 and boot it from GRUB (which is on sda1).

What is the problem ?

In disk-choose step, disk2 is missing. However Ubuntu 14.04 installer "see" this disk, so I assume that is software issue, rather than my hardware.

What I tried to solve this problem ?

• loaded Samsung NVMe drivers from this thread
• patched Windows image using DISM tool by adding 2 updates. I followed this guide
• tried to run Windows 10 installed on USB stick to install it

All of them failed.

Please help me to solve this issue.

 

Windows 10 installer don't detect NVMe drive

Thanks. This helped but only partly.

NVMe disk is now listed in choose-disk step but installer says that its unable to install WIndows on this disk because it has MBR partition. Windows can only be installed on GPT disks in EFI systems.

What should i do now ?

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.