BSOD Playing PUBG, Win 10: 0x61941 ntoskrnl.exe (nt+0x14EC00)

Hi Ztrucker,
Using Microsoft (R) Windows Debugger Version 10.0.15063.137 AMD64 I saw 2 dumps probably caused by ntkrnlmp.exe and one that was inconclusive. The memory information that you posted I did not see. Where do you see the memory speed information? Is it supposed to be with all the debuggers?



The event log has Event[37062] so impossible to get through it. These are some notable findings.

The event log has virtual memory too low.

Code:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000019 (0x0000000000000021, 0xffffd28a6ea33000, 0x0000000000003070, 0x003400360057004f). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: bdfe7e53-868e-4aa0-88f3-08dc23fbc73d.

.

Code:

The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.

Code:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000019 (0x0000000000000021, 0xffff960d3214e000, 0x0000000000005e30, 0x005c00730077006f). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 37587efa-147b-4eec-bc5d-a12e9092920e.

Code:

The driver \Driver\LGSHidFilt failed to load for the device HID\VID_046D&PID_C537&MI_00\9&23b60947&0&0000.

Code:

LGSHidFilt.Sys
Logitech Gaming KMDF HID driver 
KB or mouse
http://www.logitech.com/en-us/suppor...oads/downloads

Code:

Crash dump initialization failed!

Code:

The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume3.

Code:

{Delayed Write Failed} Windows was unable to save all the data for the file \System Volume Information\smartdb_Volume{5be57f4a-0000-0000-0000-f01500000000}.sdb. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

Code:

Application pop-up: Windows - Delayed Write Failed : Exception Processing Message 0xc0000222 Parameters 0x7ff884941d28 0x7ff884941d28 0x7ff884941d28 0x7ff884941d28

Code:

The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{9ff58b0a-a8ff-11e6-9c48-806e6f6e6963}#0000000015F00000.

Code:

Installation Failure: Windows failed to install the following update with error 0x80073D02: Mail and Calendar.

Code:

The system failed to flush data to the transaction log. Corruption may occur in VolumeId: G:, DeviceName: \Device\HarddiskVolume1.

Code:

The file system structure on volume D: cannot be corrected.

Code:

A corruption was found in a file system index structure.  The file reference number is 0x1000000000019.  The name of the file is "<unable to determine file name>".  The corrupted index attribute is ":$O:$INDEX_ROOT".  The corrupted index block is located at Vcn 0xffffffffffffffff, Lcn 0xffffffffffffffff.  The corruption begins at offset 112 within the index block.

There were problems in the event log with corruption and failure to fix on the drive.
There were failure to load for the Logitec driver.

Consider running:
1) chkdsk /x /f /r overnight as it may take many hours
2) seatools for windows SMART, short, and long generic tests
3) uninstall and reinstall the Logitech drivers.

@zbook, use the !sysinfo smbios command and look under all the [Memory Device [Type 17]] entries.

Just type !sysinfo smbios in the command input area of windbg.

Attachment 138384

You can get a list of commands by going to help > Index in the menu, keep in mind that you cannot use many commands with minidumps.
Minidumps only contain a small portion of data, many commands will provide data that only kernel dumps can provide.

No offense meant, but that question means that you didn't read my PM('s) and/or video I made for you.