BOSD when trying to play any games

I am at my wits end here. For the last 2-3 months Ive been getting BSODs whenever I try and play ANY games (PUBG, CS:GO, Fortnite... anything). Ive tried everything I could find or think of. All drivers were updated, BiOS was updated to latest version. Today I decided to do a complete fresh install of Win 10. Installed all my drivers, downloaded PUBG... and BSOD, Critical process failed (like always). According to "WhoCrashed", the dump files point to ntdll.sys and ntoskrnl.exe, but that's where I hit a brick wall. My system was built in July, and ran perfect for the first 2 or 3 months before this happened. When it first happened, I had just updated my GPU drivers, and ran a BiOS update. I'm thinking this is probably a hardware issue, since right now my system is as fresh as it can be, I'm just not sure exactly what piece of hardware is the issue.

Ive attached the results from the dm_log_collector.

Please help.

Attachment 168510

Hi jburke232 .

Welcome to Ten Forums BSOD Forum.

There were 2 BSOD mini dump files.
When debugged they did not display a definitive misbehaving driver.
The bugcheck was: 0xEF: Critical process died.

Open administrative command prompt and type or copy and paste:
1) sfc /scannow
2) dism /online /clean-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) create a brand new restore point

6) Windows driver verifier is a tool that will repetitively produce BSOD until misbehaving drivers are fixed or the tool is turned off.
There are 3 methods to turn off the tool and all are done using the Windows advanced troubleshooting menu:
a) startup options (not startup repair) > click restart > select #6 safe mode with command prompt > type: verifier /reset
b) command prompt > Administrator X:\windows\system32.cmd.exe > type: verifier /bootmode resetonbootfail
c) system restore

The methods to turn off windows driver verifer should be done a > b > c only if the prior mode has failed. Using system restore often leads to loss of the dump with little progress in the troubleshooting.

7) Modify the startup and recovery settings so that automatic restart is un-checked:
In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings > on the advanced tab under startup and recovery click settings > under system failure un-check automatically restart

After each BSOD there will be a displayed bugcheck and there may be a displayed misbehaving driver. If you see the driver displayed in the form *.sys post this information into the thread.

Each misbehaving driver will be uninstalled. A replacement driver can be immediately installed or can be installed after all misbehaving are uninstalled. The end result should be the same.

Plan to run Windows driver verifer for 48 hours. After the last dump windows driver verifier will be run for an additional 36 hours. If there are no longer any BSOD the troubleshooting with the tool will be completed.

There may be some sluggishness while using Windows driver verifier.

8) After each BSOD run the DM log collector and place a new zip into the thread:
BSOD - Posting Instructions - Windows 10 Forums

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

Use the information in this link for turning off windows driver verifier:
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

1) Open administrative command prompt and type or copy and paste:
2) dism /online /cleanup-image /scanhealth
3) dism /online /cleanup-image /restorehealth
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

I went ahead and ran "dism /online /cleanup-image /restorehealth". Below is the output:
____________________________________________________________________________________________
C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.16299.15

Image Version: 10.0.16299.125
[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>

Ran /scanhealth, and /restorehealth. Below are the outputs of each:

____________________________________________________________________________________

Microsoft Windows [Version 10.0.16299.125]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.16299.15

Image Version: 10.0.16299.125

[==========================100.0%==========================]

No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.16299.15

Image Version: 10.0.16299.125

[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>

Okay. Later today if you have made a brand new restore point and are comfortable with the Windows advanced troubleshooting menu you can start using Windows driver verifier.

To practice using the windows advanced troubleshooting menu:
1) open administrative command prompt and type or copy and paste:
shutdown /r /o /f /t 00
or
2) click the left lower corner Microsoft icon > click power icon > hold down the shift key > click restart while holding down the shift key

Ran driver verifier and got a fail at boot with "I2ChkBurn.sys"

Booted into safe mode and deleted I2ChkBurn.sys from the drivers folder.
rebooted and restarted the verifier.
Got another immediate BSOD, this time with "LGBusEnum.sys".

This is going to be a VERY long process if this keeps happening at every reboot

These were misbehaving drivers:
lgbusenum.sys Logitech Gaming Virtual Bus Enumerator Driver Keyboard
vhidmini.sys Virtual Hid Device

It will be faster to use this technique to update the driver:Updating a driver: Updating a driver. - Microsoft Community

Sometimes drivers must be uninstalled and reinstalled.
And sometimes they need to be completely uninstalled.
And other times rolled back.

So use device manger and follow the the link for updating at this time.

Code:

lgbusenum    Logitech Gaming Virtual Bus Enumerator Driver    c:\windows\system32\drivers\lgbusenum.sys    Kernel Driver    Yes    Manual    Running    OK    Normal    No    Yes

Code:

vhidmini    Virtual Hid Device    c:\windows\system32\drivers\vhidmini.sys    Kernel Driver    Yes    Manual    Running    OK    Ignore    No    Yes

vhidmini.sys

most likely an IVT Corporation BlueSolei Bluetooth HID Mini driver

http://www.bluesoleil.com/download/Default.aspx

LGBusEnum.sys

Logitech Keyboard

http://www.logitech.com/en-us/suppor...oads/downloads

Code:

12/17/2017 9:29 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: c4
P2: 2004
P3: ffffd78c59fc2b48
P4: fffff8051de301f0
P5: ffffaf8cd21020c8
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121717-16312-01.dmp
\\?\C:\WINDOWS\TEMP\WER-18000-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER52D3.tmp.WERInternalMetadata.xml

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 05d7dd73-0338-4f40-a172-db0eaf31d15a
Report Status: 4
Hashed bucket:12/17/2017 8:17 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: c9
P2: 220
P3: fffff80041c31e50
P4: ffff97899b6c2d80
P5: ffff988cfe7ee060
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121717-20234-01.dmp
\\?\C:\WINDOWS\TEMP\WER-24281-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6F5E.tmp.WERInternalMetadata.xml

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: c13faebb-45e4-448e-bdc6-f60e1cc882f1
Report Status: 4
Hashed bucket:

Code:

12/17/2017 9:31 AM    Windows Error Reporting    Fault bucket 0xc4_2004_nt!MmLoadSystemImageEx, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: fdbf80c5-3994-45e8-82f7-c59e20c9a7b9

Problem signature:
P1: c4
P2: 2004
P3: ffffd78c59fc2b48
P4: fffff8051de301f0
P5: ffffaf8cd21020c8
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121717-16312-01.dmp
\\?\C:\WINDOWS\TEMP\WER-18000-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER52D3.tmp.WERInternalMetadata.xml

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 05d7dd73-0338-4f40-a172-db0eaf31d15a
Report Status: 268435456
Hashed bucket: