Windows 10: Different BSODs or freezing while gaming or at desktop

Recently I had been getting BSODs or freezing (no response from input, no pointer movement, screen stuck, last sound looping through speakers) that seemed to start around the time that the Win10 Creator Update hit my windows update. That was roughly a week ago. The frequency of the crashes has varied, with some coming in groups of 2 or 3 within minutes, and others hours or days apart. Usually in between the crashes, which can be infrequent, everything seems to run normally. I haven't found one action or program that can set it off, as it's happened during online gaming, while AFK at the desktop, and everywhere in between. It also doesn't consistently give the same bluescreen error.

I tried a fresh install of Win10, in case I had gotten a bad creator update, but the BSODs kept coming, both with the fresh Windows 10 install, and after it downloaded the creator update once again. I tried replacing the ram with different sticks earlier today (8/19), but I had another no-BSOD freeze since. I attempted to run Driver Verifier, but that caused a BSOD either on startup, or shortly after, and it didn't give a file name on the bluescreens that it caused. I ended up trying it twice, both times shutting it off after a few restarts.

Thank you for any help.

:)

 

Freezing while gaming and BSODs probably about drivers

You're welcome!

Happy gaming

 

Freezing while gaming and BSODs probably about drivers

I've installed windows 10 recently with the Microsoft's installer by an usb flash drive. The thing is mostly while playing games which is kinda hard to run like Witcher 3 screen freezes and sound comes like *brrrrrrrrr* but the thing is if I reset my pc
I get Bluescreen unless I shutdown my pc and open it again.

I've installed all drives with Driver Booster and probably the problem is about the drives I'm gonna post the BSOD Dump file and a screenshot of a program. The things I've tried are;

sfc /scannow, chkdsk and other HDD things, used driver verifier which took me in a bsod loop and managed to get out with a system restore point

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR) Online Crash Dump Analysis Service See OSR Online - The Home Page for Windows Driver Developers for more information Windows 8 Kernel Version 16299 MP (8 procs)
Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 16299.15.amd64fre.rs3_release.170928-1534 Machine Name: Kernel base = 0xfffff800`d9c00000 PsLoadedModuleList = 0xfffff800`d9f61ff0 Debug session time: Mon Dec 18 11:40:01.919 2017 (UTC -
5:00) System Uptime: 0 days 0:01:27.622 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
(1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception
code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger
gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff800d9c44f42, The address that the exception occurred at Arg3: fffffa0c0b0fafa8,
Exception Record Address Arg4: fffffa0c0b0fa7f0, Context Record Address Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction
at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". FAULTING_IP: nt!KxWaitForLockOwnerShipWithIrql+12 fffff800`d9c44f42 48890a mov qword ptr [rdx],rcx EXCEPTION_RECORD: fffffa0c0b0fafa8 -- (.exr 0xfffffa0c0b0fafa8) ExceptionAddress:
fffff800d9c44f42 (nt!KxWaitForLockOwnerShipWithIrql+0x0000000000000012) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff
CONTEXT: fffffa0c0b0fa7f0 -- (.cxr 0xfffffa0c0b0fa7f0) rax=0000000000000000 rbx=ffffe20f9bfedd70 rcx=fffffa0c0b0fb240 rdx=2080000000000000 rsi=ffffe20f971d7040 rdi=fffffa0c0b0fb240 rip=fffff800d9c44f42 rsp=fffffa0c0b0fb1e0 rbp=fffff80cbbfb3a60 r8=fffffa0c0b0fb278
r9=fffffa0c0b0fb2a0 r10=0000000000000078 r11=0000000000000000 r12=ffffe20f970cd900 r13=ffffe20f94879030 r14=fffffa0c0b0fb2e0 r15=ffffe20f992f3330 iopl=0 nv up di ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010086 nt!KxWaitForLockOwnerShipWithIrql+0x12:
fffff800`d9c44f42 48890a mov qword ptr [rdx],rcx ds:002b:20800000`00000000=???????????????? Resetting default scope DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart unable to get nt!MmSizeOfNonPagedPoolInBytes ffffffffffffffff FOLLOWUP_IP: nt!KxWaitForLockOwnerShipWithIrql+12 fffff800`d9c44f42 48890a mov qword ptr [rdx],rcx BUGCHECK_STR: AV EXCEPTION_STR: 0x0 LAST_CONTROL_TRANSFER:
from fffff800d9ca34c3 to fffff800d9c44f42 STACK_TEXT: fffffa0c`0b0fb1e0 fffff800`d9ca34c3 : ffffe20f`9bfedd70 00000000`00000000 fffffa0c`0b0fb2d0 fffffa0c`0b0fb2e0 : nt!KxWaitForLockOwnerShipWithIrql+0x12 fffffa0c`0b0fb210 fffff80c`bbf569d8 : 00000000`00000000
fffffa0c`0b0fb202 ffffa287`2a0a8150 00000000`00000000 : nt!ExReleaseResourceLite+0xe3 fffffa0c`0b0fb270 fffff800`da0cf2bd : ffffe20f`95fab410 ffffe20f`95fab410 fffff80c`bbfb3a60 00000000`00000000 : NTFS!NtfsReleaseForCreateSection+0x68 fffffa0c`0b0fb2a0 fffff800`da0e328a
: 00000000`00000000 fffffa0c`0b0fb6e0 ffffa287`29f4e7c0 ffffe20f`991eb640 : nt!FsRtlReleaseFile+0x13d fffffa0c`0b0fb550 fffff800`da0e1f4a : fffffa0c`0b0fb6e0 fffffa0c`0b0fb6e0 ffffe20f`971d7040 ffffe20f`992f3330 : nt!MiShareExistingControlArea+0xae fffffa0c`0b0fb580
fffff800`da0e16ae : ffffe20f`991eb640 00000000`00000000 ffffe20f`992f3330 00000000`00000000 : nt!MiCreateImageOrDataSection+0x18a fffffa0c`0b0fb670 fffff800`da0e158c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiCreateSection+0xde
fffffa0c`0b0fb7d0 fffff800`da0e2325 : 00000000`00000000 fffffa0c`0b0fb9d1 00000000`00000002 00000000`11000000 : nt!MmCreateSection+0xec fffffa0c`0b0fb860 fffff800`da037591 : ffffa287`2cd8a428 ffffa287`2cd80390 fffffa0c`0b0fb980 00000002`00000000 : nt!NtCreateSection+0x155
fffffa0c`0b0fb8f0 fffff800`da0370d0 : 00000000`00000000 00000000`00001000 ffffa287`2c458e40 ffffa287`000000e8 : nt!PfSnGetSectionObject+0x249 fffffa0c`0b0fba20 fffff800`d9c3ce05 : ffffe20f`94844430 ffffe20f`971d7040 ffffe20f`94844430 ffffe20f`98ce7880 : nt!PfSnPopulateReadList+0x2a0
fffffa0c`0b0fbb80 fffff800`d9c28f87 : fffff800`da014380 00000000`00000080 ffffe20f`948d6040 ffffe20f`971d7040 : nt!ExpWorkerThread+0xf5 fffffa0c`0b0fbc10 fffff800`d9d69676 : fffff800`d9653180 ffffe20f`971d7040 fffff800`d9c28f40 00000000`00000000 : nt!PspSystemThreadStartup+0x47
fffffa0c`0b0fbc60 00000000`00000000 : fffffa0c`0b0fc000 fffffa0c`0b0f6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KxWaitForLockOwnerShipWithIrql+12 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 5a29b8d4 STACK_COMMAND: .cxr 0xfffffa0c0b0fa7f0 ; kb FAILURE_BUCKET_ID: X64_AV_nt!KxWaitForLockOwnerShipWithIrql+12 BUCKET_ID: X64_AV_nt!KxWaitForLockOwnerShipWithIrql+12 Followup: MachineOwner

And the screenshot

---------

 

Hi JKBNSINH ,

Welcome to Ten Forums.
There were 8 bsod mini dump files debugged.
There were 5 misbehaving drivers.
There were 2 software misbehaving drivers and 3 hardware misbehaving drivers.
Windows fast start up failed.

Open administrative command prompt and type or copy and paste these commands:
1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) chkdsk /scan

4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

5) Run memtest86+ version 5.01 for at least 8 runs.
This may take many hours so plan to run it overnight.
http://www.memtest.org/
When Memtest86+ has completed 8 or more runs use a camera or smart phone camera to take a picture and post an image into the thread.
Memtest86+ is perform not by time but by passes.
The more passes the better.
Fewer than 8 passes has a high incidence of false negatives.
A false negative is a pass with Malfunctioning RAM.
There is 16 GB RAM on the computer.
Memtest 86+ takes approximately 1 - 2 hours / GB RAM.
Just 1 error is a fail and you can abort testing.
Then test 1 RAM at a time in the same DIMM for 8 passes each.
If the RAM testing fails when tested together and passes when tested independently the RAM needs to be tested again in another DIMM to differentiate malfunctioning RAM from malfunctioning DIMM/MB.
After each test please use a camera or smart phone camera to take pictures and post images into the thread.

https://answers.microsoft.com/en-us/windows/wiki/windows_10-update/memory-problems/21c3f63f-f570-4522-b2ef-ecc7b7ff6461

https://www.windowsphoneinfo.com/threads/memtest86-test-ram.2010/

7) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials

8) Make sure that there is no over clocking while troubleshooting.

Sometimes there are problems in the bios that produce bsod.

The bios in your computer: BIOS Version/Date American Megatrends Inc. F4, 10/20/2015

9) Please check to see if this is the most up to date version.

10) To ensure that there are no improper bios settings please reset the bios.

Sometimes there can be failure to boot after resetting the bios.

11) So please make sure your files are backed up.

12) Please make a backup image with Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Your Image is Everything

13) And please create a restore point.

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings

3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

14) Uninstall all Trend Microsoftware
Home and Home Office Support | Trend Micro
Maximum Security Support - Home and Home Office Support | Trend Micro

15) Turn on Windows defender

16) Use device manager to uninstall Killer Bandwidth Control filter driver bwcW10x64.sys
Reinstall: Support

17) Use device manager to uninstall Realtek Hi definition Audio driver: MBfilt64.sys
Reinstall: Realtek

18) The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller and install new drivers from the computer manufacturer's website or from the Nvidia website.

The computer manufacturer's web site is preferred.
Enter the computer's serial or product number and the operating system to view available drivers.

If you use the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.

Official Display Driver Uninstaller DDU Download
Display Driver Uninstaller Download version 17.0.7.2

Display Driver Uninstaller: How to use - Windows 7 Help Forums

NVIDIA

19) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials


Code: ffff9b81`2eaa49e0 fffff80a`ddd99760Unable to load image \SystemRoot\system32\DRIVERS\tmcomm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for tmcomm.sys*** ERROR: Module load completed but symbols could not be loaded for tmcomm.sys[/quote] tmcomm.sys Trend Micro Internet Security/ Housecall scanner http://us.trendmicro.com/us/download...nd-homeoffice/

tmevtmgr.sys Trend Micro Internet Security Software.net – Trend Micro Home & Home Office – Internet Security, Maximum Security, AntiVirus+ Security, Premium Security, PC-cillin, Smart Surfing for Mac – Web Security Software Code: ffff9901`057bca38 fffff809`22294c30Unable to load image \SystemRoot\system32\DRIVERS\bwcW10x64.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for bwcW10x64.sys*** ERROR: Module load completed but symbols could not be loaded for bwcW10x64.sys bwcW10x64+0x4c30[/quote] bwcw10x64.sys Killer Bandwidth Control Filter Driver Download - http://www.killernetworking.com/supp...iver-downloads
Support - Contact Killer Network | Ethernet Killer | Killernetworking Code: BfLwf Killer Bandwidth Contr Killer Bandwidth Contr Kernel System Running OK TRUE FALSE 0 102,400 0 9/15/2016 12:22:54 PM C:\WINDOWS\system32\DRIVERS\bwcW10x64.sys 8,192[/quote] Code: ffff9901`057bc138 fffff809`21ca4909Unable to load image \SystemRoot\system32\DRIVERS\tmeevw.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for tmeevw.sys*** ERROR: Module load completed but symbols could not be loaded for tmeevw.sys tmeevw+0x4909[/quote] Code: BugCheck C4, {2000, fffff80c620f4b94, 0, 774e6350}*** WARNING: Unable to verify timestamp for MBfilt64.sys*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sysProbably caused by : MBfilt64.sys ( MBfilt64+4b94 )[/quote] MBfilt64.sys Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver) - Was found in the latest Win8 version available from Realtek on 07Sep2013 http://www.realtek.com.tw/downloads/...&GetDown=false Code: MBfilt MBfilt MBfilt Kernel Manual Running OK TRUE FALSE 4,096 12,288 0 7/30/2009 11:40:32 PM C:\WINDOWS\system32\drivers\MBfilt64.sys 8,192[/quote] Code: ffffbf00`6ddb2d08 fffff807`e328f1a4Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x15f1a4[/quote] Code: nvlddmkm nvlddmkm nvlddmkm Kernel Manual Running OK TRUE FALSE 5,820,416 6,438,912 0 5/1/2017 3:55:53 PM C:\WINDOWS\system32\DriverStore\FileRepository\n 36,864[/quote] nvlddmkm.sys nVidia Video drivers Download Drivers | NVIDIA
Get from OEM for laptops



Code: Windows failed fast startup with error status 0xC00000D4.[/quote]

 

Thank you for the welcome and reply! The CMD prompt copy/paste:

Code: Microsoft Windows [Version 10.0.15063] (c) 2017 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.15063.0 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully. C:\WINDOWS\system32>chkdsk /scan The type of the file system is NTFS. Stage 1: Examining basic file system structure ... 327168 file records processed. File verification completed. 12381 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 442838 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ... Security descriptor verification completed. 57836 data files processed. CHKDSK is verifying Usn Journal... 34952376 USN bytes processed. Usn Journal verification completed. Windows has scanned the file system and found no problems. No further action is required. 116343308 KB total disk space. 70040060 KB in 238735 files. 179416 KB in 57837 indexes. 0 KB in bad sectors. 437252 KB in use by the system. 65536 KB occupied by the log file. 45686580 KB available on disk. 4096 bytes in each allocation unit. 29085827 total allocation units on disk. 11421645 allocation units available on disk. C:\WINDOWS\system32>[/quote]
Memtest:
Unfortunately, I ran into an issue here. I started memtest before going to bed, as suggested, and while it had found no errors when I checked, the program itself seemed to have frozen after 4 passes. The little spinning "active" indicator wasn't moving, the test and pass progress had stalled, and the count of how long the test was running for had been stopped for a while when I checked it. I tried C to open config, and then ESC to exit out, but it didn't respond to either and I had to manually power off to get out of it. I can attempt to run it again tonight, or run one of the single DIMM tests, but I'm not sure if it would do the same.

Fast Start:
I went into power options and turned Fast Start off.

BIOS and Overlock:
I updated from the 10/2015 (F4) BIOS to 06/2017 (F22) and loaded the BIOS default settings. I don't overclock this PC manually, but I'm not positive if there are settings that do an automatic overclock in the BIOS. It's a "Gaming" motherboard, so it's possible, but there are pages of settings that I never touched, all set to "Auto". I'll look into that.

Drivers:
- I used the Trend Micro uninstall and remnant remover tools to remove the antivirus and its components. Windows Defender turned itself on automatically.

- I removed the Killer LAN drivers from Gigabyte and switched to the newer ones on Killer's support site.

- I removed the Realtek drivers from Gigabyte and switched to the ones on the Realtek site linked.

- My PC is a home build, so I installed the most recent WHQL drivers from NVIDIA's site (385.28) after a DDU uninstall, only installing the graphics and physX driver.

I think that's everything on the list that I was able to complete, outside of the memtest issue mentioned above.

 

Nice progress.
Many of the mini dump files have indicated probable memory corruption.
There were many dump files.
The RAM / DIMM /Motherboard are important parts of the troubleshooting.
Please repeat the Memtest86+ so that there are at least 8 passes. The more the better.
The Memtest86+ will then enable you to rule in / rule out hardware (RAM /DIMM /MB) as potential causes of the bsods.
Please use a camera or smart phone camera to take a picture and post an image into the thread.


Code: Use !analyze -v to get detailed debugging information.BugCheck 3B, {c0000005, fffff801236fbe65, ffff9b812eaa4570, 0}Probably caused by : memory_corruption[/quote] Code: BugCheck DA, {504, ffffc24c409c6f40, 0, 138de8}*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption[/quote] Code: BugCheck 50, {ffffd78577ad7d40, 0, fffff80350f91750, 2}Could not read faulting driver nameProbably caused by : memory_corruption[/quote]

Code: BugCheck A, {300001f88, 2, 0, fffff802de0ff047}*** WARNING: Unable to verify timestamp for MBfilt64.sys*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption[/quote] Code: BugCheck A, {200001f88, 2, 0, fffff8022f47c047}*** WARNING: Unable to verify timestamp for MBfilt64.sys*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption[/quote]

 

I ran Memtest again last night and was able to get through 8 passes this time.
(Apologies for the swirly bits, camera phone autofocus.)

Attachment 149862

 

Now use the computer under typical use for a few days to see if there is anything else of concern.

 

Had another BSOD, unfortunately. (Page fault in nonpaged area)

 

Looks like Killer Networking released a new driver update here:

Downloads

 

There was 1 new bsod mini dump file debugged and this did not display a definitive misbehaving driver.
There was an error in the event viewer from yesterday:

cannot zero sectors on the disk

Code: Event[3163]: Log Name: System Source: VDS Basic Provider Date: 2017-08-20T16:15:20.444 Event ID: 5 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0GN41V3 Description: Cannot zero sectors on disk \\?\PhysicalDrive2. Error code: 5@0101000F[/quote] Was that related to a USB drive or using diskpart?

Please fill out the system specifications:
How To Fill Out Your System Specs

How To Fill Out Your System Specs
System Specs - Fill in at Ten Forums:

System Specs - Fill in at Ten Forums Windows 10 General Tips Tutorials

In the left corner below in your post you find 'My System Specs'.

After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

In addition to the information in the links above please post information on: PSU, cooler, case, and peripherals: (mouse, keyboard, joystick, etc.)



Windows driver verifer is a tool that is used to find misbehaving drivers.
It will repetitively produce bsod until misbehaving drivers are fixed or until it is turned off.
Each bsod should create a mini dump that can be debugged to find the misbehaving drivers.
In order to use this tool you must know how to turn it off after each bsod and be able to return to the desktop to fix the misbehaving drivers.
There are 3 methods and all of them are done through the windows recovery or advanced troubleshooting menu:
1) startup options (not startup repair) > #6 safe mode with command prompt > type: verifier /reset
2) command prompt > Administrator X:\Windows\system32\cmd.exe > type verifier /bootmode resetonbootfail
3) restore
The methods to turn off windows driver verifer should be done in the above order and only advance if the prior method fails to turn off the tool. The restore method leads to a loss of the bsod mini dump file and little progress is made in the troubleshooting.
To practice the methods to turn off windows driver verifier open administrative command prompt by typing or copying and pasting: shutdown /r /o /f //t 00
For each bsod there will be a stop code, typically driver verifier detected violation, and there may be a displayed misbehaving driver in the form *.sys. If you see the driver displayed please record it and post it into the thread.
Use the instructions in this link to make sure you have time to view the bsod window by unchecking automatic restart:

Microsoft Community

After each bsod you will return to the desktop and run bluescreenview and whocrashed to find the misbehaving driver. Also post a new zip with each bsod so that we can guide you through the process:

Blue screen of death (STOP error) information in dump files.
Resplendence Software - WhoCrashed, automatic crash dump analyzer
BSOD - Posting Instructions - Windows 10 Forums

Use the settings in this link to turn on and customize windows driver verifier:

Microsoft Community

Review the methods in this link to turn off windows driver verifier:
Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials

Before turning on windows driver verifier make sure you perform the following steps:
1) create a brand new restore
2) backup all files
3) create a backup image using Macrium:
Macrium Software | Your Image is Everything
4) save the image to another drive

Also make sure that you are comfortable with the 3 methods to turn off windows driver verifier.

Once all misbehaving drivers are fixed windows driver verifier will run for an additional 36 hours of normal computer use. If there are no more bsod then the troubleshooting and preventative maintenance will be completed.

 

"Cannot zero sectors on the disk": Was that related to a USB drive or using diskpart?
- I did use diskpart to reclaim space on a USB drive. I ran the memtest+ tests using the automatic USB drive maker, and since the first test didn't run to completion, I wanted to try a newer drive for the second run. I tried to get the space back on my first drive, (It was only being recognized as 90MB usable) but I couldn't seem to touch the partitions on a USB with the Win10 Disk Management tool, so I used diskpart.

System specs:
I've filled them out with as much accuracy as I can recall, but the first "How To Fill Out Your System Specs" link gave me permission denied, so if there were additional instructions there, I may have missed them.

Driver Verifier:
Running verifier caused an immediate BSOD before even the windows login screen:

IRQL_NOT_LESS_OR_EQUAL - Both bluescreenview and whocrashed point to "ntoskrnl.exe", but caution that it's likely another driver that can't be identified.

Once I restarted from that, I was able to log into Win10 with verifier running, but after a minute or so it hit another BSOD:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED - While bluescreenview points again to "ntoskrnl.exe", whocrashed this time blames "hidclass.sys", which it says is another Windows file and likely not the cause.

Whocrashed also includes a 3rd entry that bluescreenview doesn't have:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M - This once more points to "ntoskrnl.exe".

 

There were 2 misbehaving drivers detected.
1 was recurrent.
1 was new.

1) Using device manager uninstall and reinstall the Logitech Gaming Virtual Bus Enumerator: LGBusEnum.sys
Logitech Support

2) Using device manager uninstall and reinstall the Creative audio driver: MBfilt64.sys
Please find all available drivers for windows 10, 8.1 and 7.0 and post them into the thread.
Post the steps that you had made with the prior un-installation and re-installation.
Creative Worldwide Support > Sound Blaster



LGBusEnum.sys Logitech Keyboard http://www.logitech.com/en-us/suppor...oads/downloads
Code: LGBusEnum Logitech Gaming Virtua Logitech Gaming Virtua Kernel Manual Running OK TRUE FALSE 5,248 7,552 0 6/13/2016 2:47:08 PM C:\WINDOWS\system32\drivers\LGBusEnum.sys 1,664[/quote] Code: Event[2162]: Log Name: System Source: Service Control Manager Date: 2017-08-20T00:38:07.160 Event ID: 7045 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-0GN41V3 Description: A service was installed in the system.Service Name: Logitech Gaming Virtual Bus Enumerator DriverService File Name: \SystemRoot\system32\drivers\LGBusEnum.sysService Type: kernel mode driverService Start Type: demand startService Account:[/quote]

MBfilt64.sys Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver) - Was found in the latest Win8 version available from Realtek on 07Sep2013 http://www.realtek.com.tw/downloads/...&GetDown=false
Code: MBfilt MBfilt MBfilt Kernel Manual Running OK TRUE FALSE 4,096 12,288 0 7/30/2009 11:40:32 PM C:\WINDOWS\system32\drivers\MBfilt64.sys 8,192[/quote]
Code: Event[50]: Log Name: System Source: Service Control Manager Date: 2017-08-17T07:19:33.040 Event ID: 7045 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-0GN41V3 Description: A service was installed in the system.Service Name: MBfiltService File Name: \SystemRoot\system32\drivers\MBfilt64.sysService Type: kernel mode driverService Start Type: demand startService Account:[/quote]

 

I will try to reinstall those two drivers again.

The "uninstall device" doesn't actually appear for the Logitech Gaming Virtual Bus Enumerator entry in device manager, I only had the options to update driver, scan for hardware changes, or open properties. It seems like it's all just packaged in their "Logitech Gaming" software and has to be uninstalled and reinstalled with it.

For the Realtek driver, I can see several installation options available, but they're all for the most recent driver on their support site, and each covers all editions of Windows since Vista.
Driver R2.82 - 2017/7/26
32-bit exe (Vista, 7, 8, 8.1, 10)
64-bit exe (Vista, 7, 8, 8.1, 10)
32/64-bit exe (Vista, 7, 8, 8.1, 10)
32/64-bit zip (Vista, 7, 8, 8.1, 10)

For the previous installation, I chose the 64-bit .exe. To remove the old driver, and install the new one, I:
1) Right-clicked the entry under "Sound, video, and game controllers" for "Realtek High Definition Audio," and chose Uninstall Device. When prompted, I checked "Delete the driver software for this device" and continued.
2) Rebooted after the uninstall (following the readme), and then ran setup after reboot.
3) After running setup for the reinstall, the installer asked to reboot once more, which I did.

*The readme also says that the installer should automatically remove any remaining drivers if it detects them, and prompt for a reboot before the new installation, which it does after the uninstall. I think Win10 automatically plugs a driver in for it after the uninstall and reboot, and it has to reboot again to remove it.

 

If you can uninstall all logitech and then reinstall using control panel that works.
When you use device manager to uninstall > right click on any row > left click properties > left click driver > left click driver details > make sure it is the identical driver to install.

When you view the rows does MBfilt64.sys appear in the driver details for the Realtek audio?