Windows 10: Multiple BDOS after installing m2. 970 samsung 1tb

Hi

I upgraded my system with a m2. 970 samsung 1tb,

after installing windows on the m2, everything seems to work great. The day after my computer started getting BSOD, sometimes right after I start, sometimes 5-10 min in.


I tried reinstalling windows twice and I am still having the same issue.


I originaly followed this guide to make the m2 bootable.

https://forums.tomshardware.com/threads/cant-install-windows-10-on-m-2.3082008/

I tried updating all drivers, updating windows, updated the m2 drivers from samsung, chipsetdrivers etc.


The clean install of windows, I did with the creation tool and a usb stick.


I have installed WhoCrashed and here is the report it spit out, I am hoping someone can help me, because at this point I am out of ideas.



Let me know if you need anymore information.


Thank you in advance.


Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\WINDOWS
Hardware: MS-7C02, Micro-Star International Co., Ltd, B450 TOMAHAWK MS-7C02
CPU: AuthenticAMD AMD Ryzen 5 3600 6-Core Processor AMD8664, level: 23
12 logical processors, active mask: 4095
RAM: 17128062976 bytes 16,0GB





Crash Dump Analysis



Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Sat 18.04.2020 15:47:42 GMT your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041820-6484-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C14E0
Bugcheck code: 0x192 0xFFFFA30514EBE080, 0xFFFFA30509BFD490, 0x0, 0x0
Error: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 18.04.2020 15:47:42 GMT your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys FLTMGR!FltDecodeParameters+0x1E35
Bugcheck code: 0x192 0xFFFFA30514EBE080, 0xFFFFA30509BFD490, 0x0, 0x0
Error: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: Filterbehandling for Microsoft filsystem
Bug check description: This indicates that a lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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.



On Sat 18.04.2020 15:45:52 GMT your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041820-6187-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C14E0
Bugcheck code: 0x4E 0x6, 0xFFFFFF3591AC4743, 0x3E25618C0, 0xE25628C0
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number PFN list is corrupted.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 18.04.2020 15:44:48 GMT your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041820-6109-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C14E0
Bugcheck code: 0x3B 0xC0000005, 0xFFFFF8017A3E74FD, 0xFFFFC08C33D40E40, 0x0
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 18.04.2020 15:43:34 GMT your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041820-6078-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C14E0
Bugcheck code: 0x3B 0xC0000005, 0xFFFFF80113DEDFE6, 0xFFFFD30162F68590, 0x0
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 18.04.2020 14:38:11 GMT your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041820-5234-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C14E0
Bugcheck code: 0x192 0xFFFFE109475CF080, 0xFFFFE1093E4FDAE0, 0x0, 0x0
Error: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.






Conclusion



6 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


:)

 

gigabyte Z370 HD3 + Samsung EVO 970 won't install Windows 10

Newly assembled system:

• Gigabyte Z370 HD3 V1.0 motherboard
  
• Intel i7-8700 CPU
  
• 2x DDR4-3200 16GB RAM (F4-3200C16D-32GVK)
  
• Samsung EVO 970 500 GB M.2 SSD (MZ-V6E500)
  
• Thermaltake TR2 S 500 W PSU (TRS-0500P-2)
  
• Deepcool Tesseract case (seems doesn't matter)
  

All components come new, unpacked.

Windows 10 Pro installation failed at the step "Getting files ready for installation." when about 70-80% complete.

I used both the original Windows 10 Pro DVD and a USB stick prepared by a Microsoft tool; the result is the same.

I tried to use the pre-installation SATA driver from the Gigabyte website.
Once I installed this driver at the step "Where do you want to install Windows", my M2 drive had disappeared from the list.

The same situation repeated with another set of components.

By the way, when I try the same set of components but with an ASUS Z370-P motherboard, there is no problem with Windows 10 installation.

I still need to assemble some systems with Gigabyte motherboards.

Update: It was easy to install Windows 10 on the SATA SSD. Same conditions: Gigabyte motherboard, but SATA SSD instead of M2 SSD.

Any suggestion what to do in order to install Window properly?

 

Samsung 970 EVO 500GB M2 - Windows 10 Install Issues various error codes

I am trying to install a clean install of Windows 10 Pro on a Samsung MZ-V7E500BW 970 EVO 500 GB V-NAND M.2 PCI Express Solid State Drive which is installed in a Asus Z97-A motherboard with latest BIOS.

The SSD has been installed in the M2 slot. M2 slot set as activate as PCI-E.

Secure boot has been disabled and the keys cleared

Set to other OS (not Windows UEFI)

Boot priory confirmed as Samsung 970 EVO.

All other SATA drives disconnected.

Trying to install Windows 10 Pro from a UEFI USB created media (from MS media creation tool), tried both in USB2 & 3 port. Also have tried the DVD way but couldn't load the NVMe drivers from the disc.

Error messages are one of the following if Windows 10 happens to find the drive 0x80070057, 0x80004005, 0x80070001, 0x80300002.

I have also tried using the diskpart command (via Shift F10 command prompt etc) to select the drive and clean it so that I can select the unallocated space and click next to install Windows but still get any of the above errors (mainly 0x80070057) when it moves
onto the next stage.

Can somebody suggest a way to get Windows 10 installed on this drive with this motherboard or could the drive be faulty.

 

Samsung introduces the Samsung 970 PRO and EVO NVMe M.2 SSDs

Samsung 970 PRO and EVO NVMe M.2 SSDs now available.

Order *Arrow SSD 970 PRO NVMe M.2 512GB Memory & Storage - MZ-V7P512BW | Samsung US

Order *Arrow SSD 970 PRO NVMe M.2 1TB Memory & Storage - MZ-V7P1T0BW | Samsung US


Order *Arrow SSD 970 EVO NVMe M.2 250GB Memory & Storage - MZ-V7E250BW | Samsung US

Order *Arrow SSD 970 EVO NVMe M.2 500GB Memory & Storage - MZ-V7E500BW | Samsung US

Order *Arrow SSD 970 EVO NVMe M.2 1TB Memory & Storage - MZ-V7E1T0BW | Samsung US

Order *Arrow SSD 970 EVO NVMe M.2 2TB Memory & Storage - MZ-V7E2T0BW | Samsung US