Windows 10: Sporadic BSOD No Obvious Cause Or Pattern

Hi,

On and off for the last year or so I've been having random BSOD or freezes on my desktop PC. It seems to happen sporadically where I'll have several crashes in a day or week and then I won't see it again for a few months. I have no idea what might be causing it and I hope you'll be able to point me in the right direction. Everytime a BSOD occurs it shows a different error message. Here is the last one I received: 'system_scan_at_raised_irql_caught_improper_driver_unload'. After the BSOD I updated my GPU driver and audio software drivers but the system has frozen a few times after.

My main uses of my computer are for Composing/Producing music with Cockos Reaper and Programming with Visual Studio (C++) and Unity as well as gaming.

Here is the .zip file from the forum tool.
COMPOSER-Wed_03_01_2018_225610_37.zip

Thank you so much for any help you can give!
- Caleb Faith

:)

 

ActiveSync encountered a proble on the desktop Vista - WM6.1

That is good to hear that it is resolved Colin. Too bad there was no obvious pattern but you resolved it so that is all that matters.

 

Get a BSOD.

I have a computer that sporadically will display a BSOD. I have tried recreating it and the only weay I was able to recreate it was via verifier. After running and customizing it, it would boot and go in to a BSOD. Had to restart in Safe Mode and reset verifier
so that I could get in to the OS. I was able to get the mimidmp files and msiconfig as well. My question is what driver is causing the BSOD?

BSOD - Dump.zip

I followed the steps here Unexpected computer shutdowns.

Thanks!

 

Hi calebfaith ,

There were no BSOD mini dump files.
The logs displayed insufficient free disk space.
Windows BSOD dumps were deleted.
There were problems with Windows dump formation.

1) How To Fill Out Your System Specs
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Site Use 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

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, etc.)

2) For all tests / steps please post images into the thread.
If there are any problems posting images please post one drive or drop box share links.

3) For the Windows drive please create 30 GB free space.

4) Open administrative command prompt and type or copy and paste:
5) sfc /scannow
6) dism /online /cleanup-image /restorehealth
7) chkdsk /scan
8) 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
9) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

10) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread

11) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
11a) > on the advanced tab under startup and recovery click settings > post an image of the startup and recovery into the thread.
11b) > on the advanced tab under performance > click on settings > click on advanced tab > under virtual memory click on change > post an image of the virtual memory tab into the thread

12) In the left lower corner search type services > open windows error reporting service > scroll to the startup type column > right click > left click on properties > post an image into the thread

13) Download and install Whocrashed > in the left upper corner above analyze click on tools > crash dump test > type: ACCEPT
http://www.resplendence.com/whocrashed14) Click analyze > look for dead or deaddead in the results > post the results into the thread

14) Run the DM log collector after all of the above steps and post a zip into the thread:
BSOD - Posting Instructions - Windows 10 Forums
BSOD - Posting Instructions - Windows 10 Forums

15) Perform Windows updates > post an image of the update status into the thread
16) Click on Windows update history > post an image into the thread

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

18) Sometimes there are problems in the bios that produce bsod.
The BIOS: Version/Date American Megatrends Inc. P1.70, 4/06/2014
19) Please check to see if this is the most up to date version.

20) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.

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

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

23) Make sure your files are backed up.

24) Please make a backup image with Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free

25) And please create a brand new 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

26) There were two misbehaving hardware drivers in the logs:
a) Graphics card driver
b) network card driver
To view active dumps there is a tool to view misbehaving drivers.

27) Please read these links on Windows driver verifier:

Use this link for the test settings:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Use this link for the methods to turn off windows driver verifier:
BSOD - Posting Instructions - Windows 10 Forums

There are 3 methods to turn off Windows driver verifier and all are done using the Windows advanced troubleshooting menu:
1) startup options (not startup repair) > restart > select #6 safe mode with command prompt > type:
verifier /reset
2) command prompt > Administrator X:\Windows\system32\cmd.exe > type:
verifier /bootmode resetonbootfail
3) system restore
The methods used to turn off windows driver verifier should always be done with step #1 and advanced to the other methods if the prior method failed. Using system restore often leads to a loss of the BSOD mini dump file and little progress is made in the troubleshooting.

28) When you have created > 30 GB free space on the drive, backed up all files, made a backup image, made a brand new restore point, and are comfortable with the methods to turn off windows driver verifier you can start using the tool.
Plan to use Windows driver verifier for 48 hours.
There may be sluggishness of the computer while using the tool.
After the last BSOD plan to use Windows driver verifier for an additional 36 hours of typical computer use.
After each BSOD please post a new zip into the thread for troubleshooting.
BSOD - Posting Instructions - Windows 10 Forums










Code: Event[29582]: Log Name: System Source: Microsoft-Windows-ResetEng Date: 2018-01-03T15:31:53.986 Event ID: 4502 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Composer Description: Attempt to reset the system has failed. Changes to the system have been undone.[/quote] Code: Event[29538]: Log Name: System Source: volmgr Date: 2018-01-03T15:31:34.960 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Composer Description: Crash dump initialization failed![/quote] Code: Event[24925]: Log Name: System Source: Microsoft-Windows-Kernel-PnP Date: 2017-12-21T16:10:18.013 Event ID: 219 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Composer Description: The driver \Driver\vwifibus failed to load for the device PCI\VEN_1814&DEV_5392&SUBSYS_3C061186&REV_00\4&3829c974&0&0050.Event[24926]: Log Name: System Source: Microsoft-Windows-Kernel-PnP Date: 2017-12-21T16:10:18.018 Event ID: 219 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Composer Description: The driver \Driver\vwifibus failed to load for the device PCI\VEN_1814&DEV_5392&SUBSYS_3C061186&REV_00\4&3829c974&0&0050.Event[24927]: Log Name: System Source: Microsoft-Windows-Kernel-PnP Date: 2017-12-21T16:10:18.022 Event ID: 219 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Composer Description: The driver \Driver\vwifibus failed to load for the device PCI\VEN_1814&DEV_5392&SUBSYS_3C061186&REV_00\4&3829c974&0&0050.Event[24928]: Log Name: System Source: Microsoft-Windows-Kernel-PnP Date: 2017-12-21T16:10:18.027 Event ID: 219 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Composer Description: The driver \Driver\vwifibus failed to load for the device PCI\VEN_1814&DEV_5392&SUBSYS_3C061186&REV_00\4&3829c974&0&0050.Event[24929]: Log Name: System Source: Microsoft-Windows-Kernel-PnP Date: 2017-12-21T16:10:18.033 Event ID: 219 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Composer Description: The driver \Driver\vwifibus failed to load for the device PCI\VEN_1814&DEV_5392&SUBSYS_3C061186&REV_00\4&3829c974&0&0050.Event[24930]: Log Name: System Source: Microsoft-Windows-Kernel-PnP Date: 2017-12-21T16:10:18.038 Event ID: 219 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Composer Description: The driver \Driver\vwifibus failed to load for the device PCI\VEN_1814&DEV_5392&SUBSYS_3C061186&REV_00\4&3829c974&0&0050.[/quote] Code: Event[10850]: Log Name: System Source: Display Date: 2017-10-06T08:55:19.945 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: Composer Description: Display driver amdkmdap stopped responding and has successfully recovered.[/quote] Code: Event[21792]: Log Name: System Source: Display Date: 2017-12-10T14:16:35.930 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: Composer Description: Display driver amdkmdap stopped responding and has successfully recovered.[/quote] Code: Event[28970]: Log Name: System Source: Display Date: 2018-01-02T23:32:37.089 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: Composer Description: Display driver amdkmdap stopped responding and has successfully recovered.[/quote] Code: Event[29699]: Log Name: System Source: storahci Date: 2018-01-03T21:32:20.896 Event ID: 129 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Composer Description: Reset to device, \Device\RaidPort2, was issued.[/quote] Code: Event[9244]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-09-22T15:38:25.896 Event ID: 1018 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Composer Description: The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.[/quote] Code: Event[10424]: Log Name: System Source: volmgr Date: 2017-10-02T13:42:07.149 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Composer Description: Dump file creation failed due to error during dump creation.[/quote] Code: Event[11537]: Log Name: System Source: Microsoft-Windows-Subsys-SMSS Date: 2017-10-09T19:28:37.036 Event ID: 12 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Composer Description: The crash dump file could not be created due to a lack of free space on the destination drive. Increasing the amount of free space on the destination drive may help prevent this error.[/quote] Code: Event[29333]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2018-01-03T14:48:33.531 Event ID: 1018 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Composer Description: The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.[/quote] Code: Event[29379]: Log Name: System Source: volmgr Date: 2018-01-03T15:04:08.897 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Composer Description: Crash dump initialization failed![/quote] Code: 3/01/2018 3:48 AM Windows Error Reporting Fault bucket 0xD4_UNLOADED_MODULE_ANALYSIS_INCONCLUSIVE!unknown_function, type 0 Event Name: BlueScreen Response: Not available Cab Id: 86f8fa62-7c42-4a36-ab3b-66db3b4c76d2 Problem signature: P1: d4 P2: ffffffffe P3: 2 P4: 2000 P5: fffff802ca5fb08c P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010318-9390-01.dmp \\?\C:\WINDOWS\TEMP\WER-10390-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4333.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4352.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4372.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d4_b86782f2323144459bd67a50a0d073f0519019_00000000_cab_19986ef6 Analysis symbol: Rechecking for solution: 0 Report ID: 620b41e5-25b0-4dfe-9e17-04ce2cf9424e Report Status: 268435456 Hashed bucket:[/quote] Code: 22/09/2017 5:38 AM Windows Error Reporting Fault bucket AV_atikmdag!SiBltDevice::Init3dDrawBltContextSetting, type 0 Event Name: BlueScreen Response: Not available Cab Id: 41fbec83-9665-45a4-b8c1-a8106612cc3b Problem signature: P1: 1000007e P2: ffffffffc0000005 P3: fffff80edabaac42 P4: ffffb681bd2c6318 P5: ffffb681bd2c5b60 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\092217-8828-01.dmp \\?\C:\Windows\Temp\WER-11937-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C0C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C3B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C8A.tmp.txt \\?\C:\Windows\Temp\WER7E68.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_23c51743a83d969fbd9b77d8570b7c5b97baff8_00000000_cab_1f208ca0 Analysis symbol: Rechecking for solution: 0 Report ID: d0c5726d-5531-4e1f-8d9b-24633a93dd30 Report Status: 268435456 Hashed bucket:25/09/2017 7:08 AM Windows Error Reporting Fault bucket AV_R_INVALID_win32k!unknown_function, type 0 Event Name: BlueScreen Response: Not available Cab Id: d9713131-25b0-4d41-8b4d-ee0f5e6b2bf1 Problem signature: P1: 50 P2: ffff9959b5354000 P3: 0 P4: ffffd2094ece8af7 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\092517-8968-01.dmp \\?\C:\Windows\Temp\WER-12484-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4853.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4872.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4893.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_da96f87dd55a7fdde398465d3d181eadaa5273fd_00000000_cab_17f469f5 Analysis symbol: Rechecking for solution: 0 Report ID: 6d99453a-ec35-44b3-a729-6f81bd3a91c4 Report Status: 268435456 Hashed bucket:2/01/2018 12:32 PM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 08786a33-322c-4fe5-9384-ae6b703a7047 Problem signature: P1: 141 P2: ffffd68a1ba47010 P3: fffff8048cedf654 P4: 0 P5: 25b4 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180102-2332.dmp \\?\C:\WINDOWS\TEMP\WER-17705875-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A58.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A67.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A78.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_53bd4160bcf5c5204bfa88724810405ae3a8322_00000000_cab_35ae6f72 Analysis symbol: Rechecking for solution: 0 Report ID: e7b7adf1-29ef-4406-a6a1-006bda8007fd Report Status: 268435456 Hashed bucket:3/11/2017 9:56 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 4aaf48c4-7625-4bec-b53c-48be2d9cfdfb Problem signature: P1: 141 P2: ffff93805d16e010 P3: fffff80ffc17f654 P4: 0 P5: 22c8 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171103-2055.dmp \\?\C:\Windows\Temp\WER-15620437-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6897.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER68A7.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER68C7.tmp.txt \\?\C:\Windows\Temp\WERB7B2.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_90656976531a8e93e54633977f63f5f274ac657_00000000_cab_285ebcb3 Analysis symbol: Rechecking for solution: 0 Report ID: 097090a3-a6a2-4cba-8ac3-289d310e211b Report Status: 268435456 Hashed bucket:29/12/2017 11:51 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 50cb6607-82a1-42f6-992f-f6aa623be341 Problem signature: P1: 141 P2: ffffd00b7d0034a0 P3: fffff80f2881f654 P4: 0 P5: a00 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171229-2250.dmp \\?\C:\WINDOWS\TEMP\WER-10783265-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9CA0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9CAF.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9CCF.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_47465714c8d1ebc0a8ba739792cab3a55fd15061_00000000_cab_2b70d39e Analysis symbol: Rechecking for solution: 0 Report ID: 55dae33c-0926-4d4c-8b9d-839d611597b7 Report Status: 268435456 Hashed bucket:29/12/2017 2:13 PM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 6594ae65-d71c-4b2b-adbf-9f34615f460f Problem signature: P1: 141 P2: ffffd00b7d373010 P3: fffff80f2881f654 P4: 0 P5: 302c P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171230-0113.dmp \\?\C:\WINDOWS\TEMP\WER-19337968-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22B0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22B2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22F1.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_e36998579d36f5985f3133c0d0d43a8466e907c_00000000_cab_16db6b03 Analysis symbol: Rechecking for solution: 0 Report ID: 92e51f93-0443-44cb-8b02-0f97f49a6785 Report Status: 268435456 Hashed bucket:5/10/2017 9:55 PM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 6d590e04-21b7-412d-9121-580c0b49b1f4 Problem signature: P1: 141 P2: ffffc60085d154a0 P3: fffff802984ef654 P4: 0 P5: 5c8 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171006-0855.dmp \\?\C:\Windows\Temp\WER-144718-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4982.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4992.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER49B2.tmp.txt \\?\C:\Windows\Temp\WER896B.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_9d3b9095d1777bccab3635d1a7e4dc9cfe44989f_00000000_cab_371e8d71 Analysis symbol: Rechecking for solution: 0 Report ID: 25713214-7daf-4f9f-a6f4-14c8223f55a7 Report Status: 268435456 Hashed bucket:10/12/2017 3:16 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: a2f6bf6c-6958-43d0-b54d-15c9358e905e Problem signature: P1: 141 P2: ffffe28abe8ca010 P3: fffff802a439f654 P4: 0 P5: 3138 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171210-1416.dmp \\?\C:\WINDOWS\TEMP\WER-15918718-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF776.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF776.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF796.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_e7b0b3e02b63c5cda9b248988d156de6d791f5_00000000_cab_1f4f3114 Analysis symbol: Rechecking for solution: 0 Report ID: f0071b42-52c8-4ff2-bd69-f00b26ea5597 Report Status: 268435456 Hashed bucket:[/quote] Code: 5/12/2017 3:24 AM Windows Error Reporting Fault bucket LKD_0x144_COMMAND_ABORT_FAILED_USBXHCI!TelemetryData_CreateReport_VEN_1B6F_DEV_7052_REV_00_FW_100800, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 03b923a2-fa1f-4c24-854f-7a55a348d44e Problem signature: P1: 144 P2: 1009 P3: ffffdb814e58b970 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\USBXHCI\USBXHCI-20171205-1249.dmp \\?\C:\WINDOWS\TEMP\WER-12986968-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A85.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A85.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3AA5.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_34f71d7f64cb76477c968bac59a9e7f81aa2_00000000_cab_209d2fef Analysis symbol: Rechecking for solution: 0 Report ID: 53756ffb-7bcc-449d-8777-ca712c1a7a45 Report Status: 268435460 Hashed bucket:20/12/2017 9:57 PM Windows Error Reporting Fault bucket LKD_0x144_COMMAND_ABORT_FAILED_USBXHCI!TelemetryData_CreateReport_VEN_1B6F_DEV_7052_REV_00_FW_100800, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 935a59b4-ab3d-471b-8145-f9ee67e28375 Problem signature: P1: 144 P2: 1009 P3: ffff93018bc49970 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\USBXHCI\USBXHCI-20171221-0856.dmp \\?\C:\WINDOWS\TEMP\WER-1084703-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9E74.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9E84.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9EA4.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_ece8f5f36455c783e981f7ce4337a40d1e4e5f5_00000000_cab_2f74ecf2 Analysis symbol: Rechecking for solution: 0 Report ID: 56cd8e47-7edf-4e48-b46f-ccf4642e5399 Report Status: 268435456 Hashed bucket:15/11/2017 11:21 AM Windows Error Reporting Fault bucket LKD_0x144_CONTEXT_ERROR_AFTER_STOP_USBXHCI!TelemetryData_CreateReport_VEN_1B6F_DEV_7052_REV_00_FW_100800, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 19dbd575-b9bd-42cf-9ca0-702b4dee62b1 Problem signature: P1: 144 P2: 1004 P3: ffffaa007085b970 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\USBXHCI\USBXHCI-20171115-2221.dmp \\?\C:\Windows\Temp\WER-3246171-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER975F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER975F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER977F.tmp.txt \\?\C:\Windows\Temp\WERB21C.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_f2ea7c86499c8ac9741b68529c6117bcf252cb7_00000000_cab_1c55b9bc Analysis symbol: Rechecking for solution: 0 Report ID: 257c60ee-cc37-482a-9e2c-4af0b41d7041 Report Status: 268435456 Hashed bucket:15/10/2017 2:53 AM Windows Error Reporting Fault bucket LKD_0x144_CONTEXT_ERROR_AFTER_STOP_USBXHCI!TelemetryData_CreateReport_VEN_1B6F_DEV_7052_REV_00_FW_100800, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 20b4882b-cd22-44d6-901d-e73308698232 Problem signature: P1: 144 P2: 1004 P3: ffffa00163cdd970 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\USBXHCI\USBXHCI-20171015-1352.dmp \\?\C:\Windows\Temp\WER-2918890-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA002.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA012.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA032.tmp.txt \\?\C:\Windows\Temp\WERC762.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_2b4b615916ccb5abae6d7f6092fbb33f74abba8_00000000_cab_39bcccb0 Analysis symbol: Rechecking for solution: 0 Report ID: 6ad43d72-c651-41a0-a067-50796b8034c4 Report Status: 270532608 Hashed bucket:27/12/2017 10:09 AM Windows Error Reporting Fault bucket LKD_0x144_CONTEXT_ERROR_AFTER_STOP_USBXHCI!TelemetryData_CreateReport_VEN_1B6F_DEV_7052_REV_00_FW_100800, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 35177751-bba5-4d64-8272-bc44a442ca7d Problem signature: P1: 144 P2: 1004 P3: ffffb7015e65c970 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\USBXHCI\USBXHCI-20171227-2108.dmp \\?\C:\WINDOWS\TEMP\WER-39030031-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB99D.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB99D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB9CD.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_23cd1bddaadda3fee82de612b519ac34a07162_00000000_cab_13f43574 Analysis symbol: Rechecking for solution: 0 Report ID: 7220573f-2a50-4ed4-8976-7e1cbed1b196 Report Status: 268435456 Hashed bucket:19/12/2017 1:11 AM Windows Error Reporting Fault bucket LKD_0x144_CONTEXT_ERROR_AFTER_STOP_USBXHCI!TelemetryData_CreateReport_VEN_1B6F_DEV_7052_REV_00_FW_100800, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 3fb780ec-b3c4-4b2a-bb8a-42fdb4089e5b Problem signature: P1: 144 P2: 1004 P3: ffff8c8153506970 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\USBXHCI\USBXHCI-20171219-1133.dmp \\?\C:\WINDOWS\TEMP\WER-6831843-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER52B9.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER52C9.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER52E9.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_696c46b3fd7b66ad383b4fae2ec52e5ff1fbaf90_00000000_cab_25b6aa89 Analysis symbol: Rechecking for solution: 0 Report ID: cb3b4468-f707-4889-9c47-20d3d2bc4e24 Report Status: 268435556 Hashed bucket:22/12/2017 7:10 AM Windows Error Reporting Fault bucket LKD_0x144_CONTEXT_ERROR_AFTER_STOP_USBXHCI!TelemetryData_CreateReport_VEN_1B6F_DEV_7052_REV_00_FW_100800, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 519069a8-4ed4-4fa7-a1b3-8e955231711f Problem signature: P1: 144 P2: 1004 P3: ffff8d014570a970 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\USBXHCI\USBXHCI-20171222-1810.dmp \\?\C:\WINDOWS\TEMP\WER-32328906-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E6D.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E6D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E8E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_4d6d2abcab4a8c017f541b0444072cae9ebec5f_00000000_cab_20bdaec0 Analysis symbol: Rechecking for solution: 0 Report ID: a505256d-3880-4f58-bb53-015dff9e82de Report Status: 268435456 Hashed bucket:14/10/2017 4:25 AM Windows Error Reporting Fault bucket LKD_0x144_CONTEXT_ERROR_AFTER_STOP_USBXHCI!TelemetryData_CreateReport_VEN_1B6F_DEV_7052_REV_00_FW_100800, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: a7ff2955-924e-42fb-a96a-4a78a6a5be30 Problem signature: P1: 144 P2: 1004 P3: ffffbd01983ce970 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\USBXHCI\USBXHCI-20171014-1524.dmp \\?\C:\Windows\Temp\WER-1926953-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A24.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A24.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A44.tmp.txt \\?\C:\Windows\Temp\WERB6E0.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_97936664d91220fd3caac8263c912be13511ec8_00000000_cab_0c99bda5 Analysis symbol: Rechecking for solution: 0 Report ID: cbf9317e-923e-44a7-b25e-2ed49625eb43 Report Status: 270532608 Hashed bucket:28/11/2017 2:22 AM Windows Error Reporting Fault bucket LKD_0x15E_FILT_StuckOID_20106_STACKPTR_ERROR_IMAGE_wfplwfs.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 1000015e P2: 25 P3: 24 P4: ffff8e828c90eed8 P5: 20106 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\NDIS\NDIS-20171127-2224.dmp \\?\C:\WINDOWS\TEMP\WER-6328656-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA2E4.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA2F3.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA314.tmp.txt \\?\C:\Windows\Temp\WERD9A.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000015e_de85852b2276ad5519c6b23af49125f3aeee04a_00000000_cab_29aca313 Analysis symbol: Rechecking for solution: 0 Report ID: ccea5a47-d311-4f3e-8dc2-266bd8e797c3 Report Status: 388 Hashed bucket:28/11/2017 2:21 AM Windows Error Reporting Fault bucket LKD_0x15E_FILT_StuckOID_20106_STACKPTR_ERROR_IMAGE_wfplwfs.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 19f4544b-7d05-494c-9fa2-27131497111e Problem signature: P1: 1000015e P2: 25 P3: 24 P4: ffff8e828c90eed8 P5: 20106 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\NDIS\NDIS-20171127-2224.dmp \\?\C:\WINDOWS\TEMP\WER-6328656-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA2E4.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA2F3.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA314.tmp.txt \\?\C:\Windows\Temp\WERD9A.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000015e_de85852b2276ad5519c6b23af49125f3aeee04a_00000000_cab_29aca313 Analysis symbol: Rechecking for solution: 0 Report ID: ccea5a47-d311-4f3e-8dc2-266bd8e797c3 Report Status: 388 Hashed bucket:17/12/2017 10:42 AM Windows Error Reporting Fault bucket LKD_0x15E_Mini_Nbl_Leak_IMAGE_Dnetr28x.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: b2a319af-94f4-4b09-979b-0ee7ad648723 Problem signature: P1: 15e P2: 30 P3: ffffb90f975c91a0 P4: ffffb90f95da1060 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\NDIS\NDIS-20171217-1627.dmp \\?\C:\WINDOWS\TEMP\WER-3051828-0.sysdata.xml \\?\C:\WINDOWS\LiveKernelReports\NDIS-20171217-1627.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA393.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA393.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA3D2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_15e_fe2bf0b7c9b92b3daac7fe1cf6ff8196d47bbe54_00000000_cab_2e801cd7 Analysis symbol: Rechecking for solution: 0 Report ID: 7d90ed68-c840-429b-8b63-f59a737373c1 Report Status: 268435456 Hashed bucket:[/quote] Code: 17/12/2017 10:42 AM Windows Error Reporting Fault bucket LKD_0x15E_Mini_Nbl_Leak_IMAGE_Dnetr28x.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: b2a319af-94f4-4b09-979b-0ee7ad648723 Problem signature: P1: 15e P2: 30 P3: ffffb90f975c91a0 P4: ffffb90f95da1060 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\NDIS\NDIS-20171217-1627.dmp \\?\C:\WINDOWS\TEMP\WER-3051828-0.sysdata.xml \\?\C:\WINDOWS\LiveKernelReports\NDIS-20171217-1627.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA393.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA393.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA3D2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_15e_fe2bf0b7c9b92b3daac7fe1cf6ff8196d47bbe54_00000000_cab_2e801cd7 Analysis symbol: Rechecking for solution: 0 Report ID: 7d90ed68-c840-429b-8b63-f59a737373c1 Report Status: 268435456 Hashed bucket:[/quote]
Dnetr28x.sys Ralink 802.11n Wireless Adapters. Included in D-Link DWA-525 Wireless N 150 Desktop Adapter Broadband Wi-Fi or
Assistance

Code: netr28x Ralink 802.11n Extensible Wireless Driver c:\windows\system32\drivers\netr28x.sys Kernel Driver Yes Manual Running OK Normal No Yes[/quote] Code: 22/09/2017 5:38 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1000007e P2: ffffffffc0000005 P3: fffff80edabaac42 P4: ffffb681bd2c6318 P5: ffffb681bd2c5b60 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\092217-8828-01.dmp \\?\C:\Windows\Temp\WER-11937-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C0C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C3B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C8A.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000007e_23c51743a83d969fbd9b77d8570b7c5b97baff8_00000000_cab_03004c99 Analysis symbol: Rechecking for solution: 0 Report ID: d0c5726d-5531-4e1f-8d9b-24633a93dd30 Report Status: 4 Hashed bucket:25/09/2017 7:08 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 50 P2: ffff9959b5354000 P3: 0 P4: ffffd2094ece8af7 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\092517-8968-01.dmp \\?\C:\Windows\Temp\WER-12484-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4853.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4872.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4893.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_da96f87dd55a7fdde398465d3d181eadaa5273fd_00000000_cab_02fc4892 Analysis symbol: Rechecking for solution: 0 Report ID: 6d99453a-ec35-44b3-a729-6f81bd3a91c4 Report Status: 4 Hashed bucket:3/01/2018 3:48 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: d4 P2: ffffffffe P3: 2 P4: 2000 P5: fffff802ca5fb08c P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010318-9390-01.dmp \\?\C:\WINDOWS\TEMP\WER-10390-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4333.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4352.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4372.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d4_b86782f2323144459bd67a50a0d073f0519019_00000000_cab_03004371 Analysis symbol: Rechecking for solution: 0 Report ID: 620b41e5-25b0-4dfe-9e17-04ce2cf9424e Report Status: 4 Hashed bucket:[/quote] Code: Drive: C: Free Space: 17.5 GB Total Space: 228.1 GB File System: NTFS Model: SanDisk SDSSDA240G Drive: F: Free Space: 42.6 GB Total Space: 238.5 GB File System: NTFS Model: ST3250620AS Drive: K: Free Space: 1.4 GB Total Space: 953.8 GB File System: NTFS Model: HGST TOURO S USB Device Drive: M: Free Space: 6.5 GB Total Space: 122.1 GB File System: NTFS Model: Samsung SSD 840 PRO Series Drive: N: Free Space: 1.6 GB Total Space: 114.5 GB File System: NTFS Model: KINGSTON SV300S37A120G ATA Device Drive: O: Free Space: 8.4 GB Total Space: 56.6 GB File System: NTFS Model: INTEL SSDSC2CW060A3 Drive: Y: Free Space: 760.7 GB Total Space: 953.9 GB File System: NTFS Model: ST1000LM024 HN-M101MBB Drive: Z: Free Space: 9.0 GB Total Space: 953.9 GB File System: NTFS Model: WDC WD10EACS-11BHUB0 Drive: J: Model: TSSTcorp CDDVDW SH-224DB ATA Device Driver: c:\windows\system32\drivers\cdrom.sys, 10.00.15063.0000 (English), , 0 bytes[/quote]

 

Hi Caleb

The recent bugcheck might have saved a memory.dmp file in your windows directory. If possible please share this via OneDrive or dropbox.

Code: Event[29284]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2018-01-03T14:48:26.624 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: COMPOSER Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d4 (0x0000000ffffffffe, 0x0000000000000002, 0x0000000000002000, 0xfffff802ca5fb08c). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 620b41e5-25b0-4dfe-9e17-04ce2cf9424e.[/quote]

 

philc43,
After the bugcheck there was another event post displaying:

Code: Event[29333]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2018-01-03T14:48:33.531 Event ID: 1018 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Composer Description: The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.[/quote]

Date: 2018-01-03T14:48:26.624 > Date: 2018-01-03T14:48:33.531

 

Date: 2018-01-03T14:48:26.624 > Date: 2018-01-03T14:48:33.531[/quote] Thanks @zbook - I missed that.

 

Thanks so much for the detailed response. I'll get started on all the things you've mentioned and get back to you!

 

I've added all the info I can for my system specs.

3. Complete - C:\ 46.5GB Free

5.
Code: Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>sfc /scannowBeginning 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>[/quote] 6.
Code: Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth Deployment Image Servicing and Management toolVersion: 10.0.15063.0 Image Version: 10.0.15063.0 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully. C:\WINDOWS\system32>[/quote] 7.
Code: Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>chkdsk /scan The type of the file system is NTFS. Stage 1: Examining basic file system structure ... 1777408 file records processed. File verification completed. 32072 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 2234172 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. 228383 data files processed. CHKDSK is verifying Usn Journal... 35124224 USN bytes processed. Usn Journal verification completed. Windows has scanned the file system and found no problems. No further action is required. 233539975 KB total disk space. 183174508 KB in 1008425 files. 554336 KB in 228384 indexes. 0 KB in bad sectors. 1893683 KB in use by the system. 65536 KB occupied by the log file. 47917448 KB available on disk. 4096 bytes in each allocation unit. 58384993 total allocation units on disk. 11979362 allocation units available on disk. C:\WINDOWS\system32>[/quote] 9.




10.






11. a.



b.




12.

 

13.




14.
Attachment 170751

15.



16.




17. No overclocking.

19.




20.
ASRock > 990FX Extreme9

 

CMOS Cleared - BIOS reset

Driver Verifier Started

 

1) Turn off windows driver verifier as the dumps need to be fixed first.
Only after whocrashed displays a valid test dump can windows driver verifier be used.
2) For Ccleaner:
a) un-check memory dumps and windows log files
3) For startup and recovery > settings > system failure > un-check automatic restart

 

Computer won't boot to Windows with Driver Verifier running.

Here is the .zip file generated after I ran in safe mode and disabled driver verifier: COMPOSER-Thu_04_01_2018_105711_08.zip

 

Sorry just saw this doing now:

 

The zip as expected did not have dump files as the dump problem has not yet been fixed.
For windows error reporting service properties change manual to automatic > click start > reboot
For the attachment in #14 it could not be opened. Please re-post.
After the changes have been made to: startup and recovery, ccleaner, windows error reporting, etc. > open whocrashed > perform dump test > click analyze > post results into the thread. When working properly it will display dead or deaddead.