BSOD after installing Cumulative Update KB4343909 Windows 10 v1803 Aug

Win10 Pro
Completed all updates last night - no issues
Woke machine this early afternoon and had a BSOD but missed reading complete details (may have said driver issue)
Rebooted ok and found that I had no sound
Rebooted again and still n/g
Troubleshooter was n/g
Restored prior to updates
After restart sound returned ok
Blocked updates for now.

Hi

Welcome to Ten Forums BSOD forum.
There were no dump files collected by the log collector.
The driver support for the computer ended with Windows 7.
There are two log collectors: DM and BETA
At some time the BETA log collector will replace the DM log collector.
The BETA log collector collects more useful files.
Run the BETA log collector and post a zip into this thread:
https://www.tenforums.com/attachment...-v2-beta15.zip
(extract > open)
Use the txt and images in this thread in case there are any problems running the beta log collector: (post #5)
DM Log tool problem

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) 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
6) Make sure that there is no over clocking while troubleshooting.
7) Sometimes there are problems in the bios that produce bsod.
The BIOS: BIOS Version/Date American Megatrends Inc. 5.29, 9/17/2010
8) Please check to see if this is the most up to date version.
9) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.
10) To ensure that there are no improper bios settings please reset the bios.
11) Sometimes there can be failure to boot after resetting the bios.
12) Backup the computer files to another drive or to the cloud.
13) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free
14) And please create a brand new restore point.

How to Clear Your Computers CMOS to Reset BIOS Settings:
https://www.howtogeek.com/131623/how...bios-settings/
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

15) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread
16) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

Code:

8/15/2018 6:40 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: d1
P2: ffffa20c57aa6098
P3: 2
P4: 0
P5: fffff8048c19c1f0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\081518-9765-01.dmp
\\?\C:\Windows\TEMP\WER-15562-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4ECD.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EDE.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EDD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EEE.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d1_b612738b9097b1f8d8d8506483bec2d672cf17f_00000000_cab_02e44eeb

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2447919d-9b48-4c39-b538-fce5275aaf40
Report Status: 4
Hashed bucket: 
Cab Guid: 0

Code:

8/15/2018 6:44 PM	Windows Error Reporting	Fault bucket AV_IDSvia64!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 799747bd-4620-4f36-b489-77f4acc64af3

Problem signature:
P1: d1
P2: ffffa20c57aa6098
P3: 2
P4: 0
P5: fffff8048c19c1f0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\081518-9765-01.dmp
\\?\C:\Windows\TEMP\WER-15562-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4ECD.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EDE.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EDD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EEE.tmp.txt
\\?\C:\Windows\Temp\WERCEDB.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_b612738b9097b1f8d8d8506483bec2d672cf17f_00000000_cab_16939d2b

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2447919d-9b48-4c39-b538-fce5275aaf40
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
8/15/2018 6:40 PM	Windows Error Reporting	Fault bucket LKD_0x1cc_EXRESOURCE_TIMEOUT_OWNERTHREAD_nt!IopLiveDumpEndMirroringCallback, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: bba17ecf-30bd-494d-9a7c-43be4d6c3a3e

Problem signature:
P1: 1cc
P2: ffffab8a2eb6aa20
P3: ffffab8a2473f080
P4: 4
P5: 96
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\ResourceTimeout\ResourceTimeout-20180813-1031.dmp
\\?\C:\Windows\TEMP\WER-15562-0.sysdata.xml
\\?\C:\Windows\LiveKernelReports\ResourceTimeout-20180813-1031.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E3F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E4F.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E6E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EAD.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1cc_b4ea4cdcb01f36d114df8a5432d57460569532_00000000_cab_1690a344

Analysis symbol: 
Rechecking for solution: 0
Report Id: 189e7b06-f920-4a69-9b37-ac2d666fffb8
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0

Code:

USB camera	USB\VID_045E&PID_00F5&MI_00\7&E59C498&0&0000	The drivers for this device are not installed.

Still no dump files but here are the other outputs.

1) The computer settings and software may need to be modified so that dump files properly form and are not cleaned/deleted.
2) When available post images for steps 15 and 16.

3) Download and install: Everything
voidtools
4) Copy and paste: ResourceTimeout-20180813-1031.dmp
zip the file > post a one drive or drop box share link into this thread

Code:

ResourceTimeout-20180813-1031.dmp 8/13/2018 10:31:40 AM   1674.09

4) copy and paste: VX3000
Use the snipping tool and post an image of the displayed results into the thread

5) Open administrative command prompt and type or copy and paste:
6) Powercfg -h off
7) shutdown /r

8) Run HD Tune: (free edition) (on all drives)
Post images into the thread for results on these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan

9) Open administrative command prompt and type or copy and paste:
chkdsk /r /v
Run this command on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive
This may take many hours so plan to run overnight.

C:\WINDOWS\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

type: Y
reboot

10) Use the txt and images in this thread to find the chkdsk reports in the event viewer > copy and paste > notepad > post one drive or drop box share links into the thread
Read Chkdsk Log in Event Viewer in Windows 10

Code:

8/15/2018 6:40 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: d1
P2: ffffa20c57aa6098
P3: 2
P4: 0
P5: fffff8048c19c1f0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\081518-9765-01.dmp
\\?\C:\Windows\TEMP\WER-15562-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4ECD.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EDE.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EDD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EEE.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d1_b612738b9097b1f8d8d8506483bec2d672cf17f_00000000_cab_02e44eeb

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2447919d-9b48-4c39-b538-fce5275aaf40
Report Status: 4
Hashed bucket: 
Cab Guid: 0

Code:

8/15/2018 6:44 PM	Windows Error Reporting	Fault bucket AV_IDSvia64!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 799747bd-4620-4f36-b489-77f4acc64af3

Problem signature:
P1: d1
P2: ffffa20c57aa6098
P3: 2
P4: 0
P5: fffff8048c19c1f0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\081518-9765-01.dmp
\\?\C:\Windows\TEMP\WER-15562-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4ECD.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EDE.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EDD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EEE.tmp.txt
\\?\C:\Windows\Temp\WERCEDB.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_b612738b9097b1f8d8d8506483bec2d672cf17f_00000000_cab_16939d2b

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2447919d-9b48-4c39-b538-fce5275aaf40
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
8/15/2018 6:40 PM	Windows Error Reporting	Fault bucket LKD_0x1cc_EXRESOURCE_TIMEOUT_OWNERTHREAD_nt!IopLiveDumpEndMirroringCallback, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: bba17ecf-30bd-494d-9a7c-43be4d6c3a3e

Problem signature:
P1: 1cc
P2: ffffab8a2eb6aa20
P3: ffffab8a2473f080
P4: 4
P5: 96
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\ResourceTimeout\ResourceTimeout-20180813-1031.dmp
\\?\C:\Windows\TEMP\WER-15562-0.sysdata.xml
\\?\C:\Windows\LiveKernelReports\ResourceTimeout-20180813-1031.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E3F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E4F.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E6E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EAD.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1cc_b4ea4cdcb01f36d114df8a5432d57460569532_00000000_cab_1690a344

Analysis symbol: 
Rechecking for solution: 0
Report Id: 189e7b06-f920-4a69-9b37-ac2d666fffb8
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0

Code:

+++ WER6 +++:
Fault bucket AV_IDSvia64!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 799747bd-4620-4f36-b489-77f4acc64af3

Problem signature:
P1: d1
P2: ffffa20c57aa6098
P3: 2
P4: 0
P5: fffff8048c19c1f0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10:

Code:

Event[3588]:
  Log Name: Application
  Source: ESENT
  Date: 2018-08-06T13:59:06.932
  Event ID: 399
  Task: Database Page Cache
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: StudioOfficePC
  Description: 
SearchIndexer (6520,D,29) Windows: The database page read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 113770496 (0x0000000006c80000) (database page 3471 (0xD8F)) for 32768 (0x00008000) bytes failed verification. Bit 70430 was corrupted and has been corrected.  This problem is likely due to faulty hardware and may continue. Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem containing this file.  Please contact your hardware vendor for further assistance diagnosing the problem.

John,

The system restore you performed likely cleared out the dump files generated from the initial crash. Until another bugcheck occurs we won't be able to look over the dump files.

Given that you encountered sound issues after this happened, I would look into seeing if there are any newer drivers for your Creative sound card. Your current driver is from 2010, and is likely not fully supported on Windows 10. Given the age of the device, there is the possibility that this is a hardware failure, see if you can remove it and use onboard audio for a while to rule out your sound card as the culprit.

Also, your VX3000 webcam is no longer supported on Windows 10, and I don't see any drivers for anything newer than Windows 7. In fact, it's reporting that no drivers are even loaded for the device so I'm not sure it's even functional on your computer right now. Consider unplugging it.