Windows 10: BSOD started when playing Fallout 4

Attachment 48342

The first BSOD was while playing fallout 4. After it happened a 2nd time i ran driver verifier /standard /all. This sent the machine into a boot loop. I disabled driver verifier. My PC seems to run fine under normal conditions, but this is worrying.

The PC was overclocked when the fist BSOD happened. I reset the BIOS to default values before running driver verifier. I also ran the Samsung Magician program which listed the health of both SSDs as good. I also ran the Windows Memory Diagnostic tool which indicated no errors.

The first BSOD simply pointed to NTOSKRL as the problem. From there it was MACHINE CHECK, then HIDCLASS.sys.

Any help would be greatly appreciated!

:)

 

Fallout 4 won't load

what do you have for a rig, Fallout 4 is kinda demanding

FALLOUT 4

 

Computer shuts off when playing Fallout 4 infrequently

My computer shuts off sometimes when playing fallout 4, it is random. It has happened once when not playing fallout 4. This problem happens infrequently, usually less then once a day or so but it completely cuts power to the pc and is seemingly random when
it occurs. I can be playing for hours and no problem, but then the next day start it up and it will happen after 10 minutes.

Here is my Onedrive with Speccy, Driverview, Event logs and System information. Thank you so much for the help, this is maddening!

Troubleshooting documents

 

Hi cylon58,

Welcome to the 10forums.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

• Uninstall Daemon Tools
• Download the SPTD standalone installer and follow these steps:
  • Double click the executable to open it
  • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window

Please update your Logitech software and drivers
Driver Reference Table - LGVirHid.sys
Code: *** WARNING: Unable to verify timestamp for LGVirHid.sys *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys 0: kd> lmvm LGVirHid start end module name fffff801`10e20000 fffff801`10e22480 LGVirHid T (no symbols) Loaded symbol image file: LGVirHid.sys Image path: LGVirHid.sys Image name: LGVirHid.sys Timestamp: Tue Nov 24 02:36:48 2009 (4B0B38B0) CheckSum: 00012CDE ImageSize: 00002480 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]