Random BSOD (critical process died)

webhead93 · 10 Feb 2017

Ztruker said:

My guess is a defective CPU. You have a hundred or more of the Processor Core Machine Check entries.

Code:

Event[1552]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2016-11-20T14:00:58.638
  Event ID: 19
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-665J3HP
  Description: 
A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Bus/Interconnect Error
Processor APIC ID: 36

The details view of this entry contains further information.

Please post the info from a details view of one of these entries, see if anything useful is in there.

Good catch, but looking through the event viewer, the last reported warning was 1/13/2017, and that was the date I replaced the CPU's, so it seems that cleared up the warnings, but still the crashes persist...

Ztruker · 11 Feb 2017

Okay, that's good then.

The only dump we've had to work with is the 1/28 Driver Verifier generated dump which indicated memory_corruption that was caused by a device driver, but it did not indicate which one.

Looking at it again, I did notice in the thread trace (!thread then dps) that LGBusEnum was in there several times. This is LGBusEnum.sys:

Driver Description: Logitech Keyboard
Driver Update Site: Logitech Support + Downloads

The one you have is recent (Mon Jun 13 14:47:08 2016) but check to see if there is a newer one. If not then try an older one or remove the Logitech keyboard and use a different one for awhile as a test.