[SOLVED] Help with BSOD error messages on new build

[SMOG81]

Hi all,

I've recently completed a new build and have been getting repeated crashes with a blue screen error. The crashes are pretty random and can range from a couple of times an hour to up to ten times an hour!

Specs are

Windows 10 Pro 64bit

x570 xtreme motherboard

64gb DDR4 G.skill ram 3600mhz (x4 sticks at 16gb each)

Gigabyte 2080ti GPU

970 EVO M.2 SSD Samsung

Aorus 360 liquid cooler

750w gold rated PSU.

I've done five clean installs of windows now and its made no difference. I have also downloaded drivers from maufacturers rather than rely on Windows update and I have performed a Memtest on memory overnight with 8 passes and no fails. I have also run diognostics on the harddrive which has returned no errors...

DMP file info....

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sun 16/08/2020 10:46:22 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081620-9187-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF807751F1767)
Bugcheck code: 0x50 (0xFFFF8D80663C01E8, 0x3, 0xFFFFF807751F1767, 0xD)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
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 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 Sun 16/08/2020 10:46:22 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (0xFFFFF807751F1767)
Bugcheck code: 0x50 (0xFFFF8D80663C01E8, 0x3, 0xFFFFF807751F1767, 0xD)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
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 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 Sun 16/08/2020 10:22:31 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081620-9312-01.dmp
This was probably caused by the following module: dxgkrnl.sys (0xFFFFF802490EF295)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802490EF295, 0xFFFFA38EDCAC2B60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 15/08/2020 19:07:00 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081520-9859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDF40)
Bugcheck code: 0xEF (0xFFFFC20FE60082C0, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
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 15/08/2020 18:02:22 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081520-9312-01.dmp
This was probably caused by the following module: volsnap.sys (0xFFFFF80369C0001A)
Bugcheck code: 0xBE (0xFFFFF80369C0001A, 0x5C00121, 0xFFFFC10FECF4EF80, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\volsnap.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Volume Shadow Copy driver
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 15/08/2020 17:22:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081520-9109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDF40)
Bugcheck code: 0x139 (0x3, 0xFFFFB9085A978F90, 0xFFFFB9085A978EE8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[MeanMachine41]

You have possible corruption in your windows system32 files.
Bring up an elevated command prompt and run "sfc /scannow" without the quotation marks. This will interrogate the files structure and attempt to rectify. any bad files. Report back on this file check.

Next go to your Control Panel>device manager and check for any yellow triangles which indicate a bad or missing driver,If so then uninstall and update the driver from the manufacturers website. report back.
As dxgkrnl.sys is involved, Pay attention to your graphics card driver as it may require an update.
I would also do a chkdsk to check your storage drive.

 

[SMOG81]

You have possible corruption in your windows system32 files.
Bring up an elevated command prompt and run "sfc /scannow" without the quotation marks. This will interrogate the files structure and attempt to rectify. any bad files. Report back on this file check.

Next go to your Control Panel>device manager and check for any yellow triangles which indicate a bad or missing driver,If so then uninstall and update the driver from the manufacturers website. report back.
As dxgkrnl.sys is involved, Pay attention to your graphics card driver as it may require an update.
I would also do a chkdsk to check your storage drive.

Thanks for the advice,

I've applied all of the above with the following results,

Scannow returned a corrupted file and made the repairs

Updated graphics card drivers direct from NVIDIA

Checked device manager and no yellow triangles are displayed against anything.

I've had three crashes since making the above updates which are as follows,,,

On Sun 16/08/2020 07:21:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: wdfilter.sys (WdFilter+0x584DF)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF0, 0x0, 0xFFFFF80128E72317, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\wdfilter.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft antimalware file system filter driver
Bug check description: This indicates that invalid system memory has been referenced.
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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 16/08/2020 07:11:47 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081620-9312-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDF40)
Bugcheck code: 0x34 (0x9FF, 0xFFFFFFFFC0000420, 0x0, 0x0)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 16/08/2020 06:34:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081620-9406-01.dmp
This was probably caused by the following module: gdrv2.sys (0xFFFFF802CAB816A4)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802CAB816A4, 0xFFFFEE828236AA10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\gdrv2.sys
product: GIGA-BYTE Software driver
company: GIGA-BYTE TECHNOLOGY CO., LTD.
description: GIGA-BYTE NonPnP Driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: gdrv2.sys (GIGA-BYTE NonPnP Driver, GIGA-BYTE TECHNOLOGY CO., LTD.).
Google query: gdrv2.sys GIGA-BYTE TECHNOLOGY CO., LTD. SYSTEM_SERVICE_EXCEPTION

 

[MeanMachine41]

Do you have any third party gigabyte software interacting with your system. ? If so try to stop it from running.
The problem is with gdrv.sys which is a third party driver from Gigabyte and if you remove it your blue screening may go away.
Run services.msc and see if anything related to DESA (Dynamic Energy Saver Advanced) and check to see if any service associated with Gigabyte can be stopped.
Iv'e also heard APP Center and RGB Fusion can be an issue if installed.