BSOD 'Machine Check Exception' Error

J0ckieboy · 27 Mar 2016

Can anyone help figure this one out?

Last night Defender was updated. No new hardware installed.
This morning the machine freezes and I've also had a BSOD with 'Machine check exception' error.

Experienced similar freezes last week with a 'Driver power state failure' error but I solved it by updating the wifi drivers.

It seems that both times I've managed to stall the inevitable freeze by removing the power supply and the battery for a few minutes between restarts.

Ztruker · 27 Mar 2016

The last 5 or 6 dumps all point to FLxHCIh.sys whihc belongs to Fresco Logic xHCI (USB3) Hub Driver. The driver is very old, dated 2012 and needs to be updated, that should fix this problem.

J0ckieboy · 27 Mar 2016

Ztruker said:

The last 5 or 6 dumps all point to FLxHCIh.sys whihc belongs to Fresco Logic xHCI (USB3) Hub Driver. The driver is very old, dated 2012 and needs to be updated, that should fix this problem.

Thanks for your advice. I updated the Fresco USB hub driver but the freezes continue.
I've attached the latest log.

Ztruker · 27 Mar 2016

No new dump s not much I can look at.

Is this an external device or built into the system board?
If external, disconnect it.

Looking at your device drivers, you have a lot of very old drivers.

Code:

25/09/2008 03:28:20    C:\WINDOWS\system32\drivers\SiSRaid2.sys
02/10/2008 06:56:04    C:\WINDOWS\system32\drivers\sisraid4.sys
02/07/2009 18:13:26    \??\C:\Program Files (x86)\ASUS\ATK Package\ATKG
18/09/2009 04:54:16    C:\WINDOWS\system32\drivers\HECIx64.sys
24/11/2009 10:36:48    C:\WINDOWS\system32\drivers\LGBusEnum.sys
24/11/2009 10:36:48    C:\WINDOWS\system32\drivers\LGVirHid.sys
31/07/2009 12:40:32    C:\WINDOWS\system32\drivers\MBfilt64.sys
13/05/2009 10:04:54    C:\WINDOWS\system32\DRIVERS\ATK64AMD.sys
06/03/2010 03:22:43    C:\WINDOWS\system32\DRIVERS\SynTP.sys
12/04/2011 03:48:16    C:\WINDOWS\system32\drivers\iaStorV.sys
12/12/2012 06:21:44    C:\WINDOWS\system32\drivers\amdsbs.sys
27/11/2012 09:02:51    C:\WINDOWS\system32\drivers\stexstor.sys
05/02/2013 04:47:18    C:\WINDOWS\system32\drivers\bxvbda.sys
27/03/2013 06:36:54    C:\WINDOWS\system32\drivers\HpSAMD.sys
01/04/2013 12:15:17    C:\WINDOWS\system32\drivers\L1C63x64.sys
31/05/2013 00:16:33    C:\WINDOWS\system32\DRIVERS\LGSHidFilt.Sys
31/05/2013 00:15:44    C:\WINDOWS\system32\DRIVERS\LGSUsbFilt.Sys
16/03/2013 08:39:38    C:\WINDOWS\system32\drivers\lsi_sss.sys
04/06/2013 07:02:39    C:\WINDOWS\system32\drivers\megasr.sys
22/01/2013 04:00:28    C:\WINDOWS\system32\drivers\vstxraid.sys
16/03/2014 19:07:36    C:\WINDOWS\system32\drivers\bcmfn2.sys
24/05/2014 05:39:04    C:\WINDOWS\system32\drivers\mvumis.sys
22/04/2014 03:28:42    C:\WINDOWS\system32\drivers\nvraid.sys
22/04/2014 03:34:03    C:\WINDOWS\system32\drivers\nvstor.sys
23/04/2014 04:21:41    C:\WINDOWS\system32\drivers\vsmraid.sys

See if you can find a more recent Chipset driver for your main board. I'm not seeing any but maybe you will have better luck. If not, I suggest doing an image back and or saving any data you don't want to lose then do a Windows 10 - Clean Install

J0ckieboy · 28 Mar 2016

The USB root hub is internal, so built into the system board.
I've used the 'Intel Driver Update Utility' to identify newer Chipset Device Software. Once installed and having given the machine some time to check for any further freezes, I'll post a reply or 'Mark as Solved'.

Ztruker · 28 Mar 2016

Okay, good luck.

axe0 · 29 Mar 2016

Warning

Programs that claim to update your drivers install either the wrong or corrupted drivers.
If you have installed any driver with Driver Identifier, please remove them as it may cause trouble.

With laptops you only need to install the drivers your manufacturer provides.

Update the drivers of your Logitech mouse, that looks to be the cause of the crashes.

Code:

0: kd> !irp ffffe000`0d347c10
Irp is active with 10 stacks 6 is current (= 0xffffe0000d347e48)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe0000f9aa560 00000000 00000000-00000000    pending
           \Driver\FLxHCIh
            Args: 00051100 00000001 00000001 00000002
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe0000f9903f0 00000000 fffff80147a81e00-00000000 Success Error Cancel pending
          *** WARNING: Unable to verify timestamp for LGSUsbFilt.Sys
*** ERROR: Module load completed but symbols could not be loaded for LGSUsbFilt.Sys
 \Driver\LGSUsbFilt    hidusb!HumPowerCompletion
            Args: 00051100 00000001 00000001 00000002
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e0 ffffe0000f8326a0 00000000 fffff80147aa4c30-ffffe0000f8327f0 Success Error Cancel 
           \Driver\HidUsb    HIDCLASS!HidpFdoPowerCompletion
            Args: 00051100 00000001 00000001 00000002
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe0000f8326a0 00000000 fffff800383230b8-ffffe0000f50c130 Success Error Cancel pending
           \Driver\HidUsb    nt!PopRequestCompletion
            Args: 00051100 00000001 00000001 00000002
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffe0000f50c130    

            Args: 00000000 00000000 00000000 00000000
0: kd> !devobj ffffe0000f9903f0
Device object (ffffe0000f9903f0) is for:
 InfoMask field not found for _OBJECT_HEADER at ffffe0000f9903c0
 \Driver\LGSUsbFilt DriverObject ffffe0000f813e60
Current Irp 00000000 RefCount 0 Type 0000002a Flags 00002000
Dacl ffffc101e1984e91 DevExt ffffe0000f98e850 DevObjExt ffffe0000f990568 
ExtensionFlags (0000000000)  
Characteristics (0x00000180)  FILE_AUTOGENERATED_DEVICE_NAME, FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffe0000f8326a0 \Driver\HidUsb
AttachedTo (Lower) ffffe0000f9aa560 \Driver\FLxHCIh
Device queue is not busy.
0: kd> !devobj ffffe0000f9aa560
Device object (ffffe0000f9aa560) is for:
 Cannot read info offset from nt!ObpInfoMaskToOffset
 \Driver\FLxHCIh DriverObject ffffe0000f6a4a50
Current Irp 00000000 RefCount 0 Type 0000002a Flags 00003040
Dacl ffffc101e1984e91 DevExt ffffe0000f83cc70 DevObjExt ffffe0000f9aa6d8 DevNode ffffe0000ea3ca90 
ExtensionFlags (0000000000)  
Characteristics (0x00000180)  FILE_AUTOGENERATED_DEVICE_NAME, FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffe0000f9903f0 \Driver\LGSUsbFilt
Device queue is not busy.

0: kd> lmvm lgsusbfilt
Browse full module list
start             end                 module name
fffff801`47a70000 fffff801`47a80000   LGSUsbFilt T (no symbols)           
    Loaded symbol image file: LGSUsbFilt.Sys
    Image path: \SystemRoot\system32\DRIVERS\LGSUsbFilt.Sys
    Image name: LGSUsbFilt.Sys
    Browse all global symbols  functions  data
    Timestamp:        Thu May 30 17:15:44 2013 (51A76D20)
    CheckSum:         00013993
    ImageSize:        00010000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

J0ckieboy · 30 Mar 2016

Thank you very much for your advice.
I've now updated my Logitech mouse drivers.

I'll get back to this thread after a while to either update with more freezes or to 'Mark as Solved'.

J0ckieboy · 17 Apr 2016

J0ckieboy said:

Thank you very much for your advice.
I've now updated my Logitech mouse drivers.

I'll get back to this thread after a while to either update with more freezes or to 'Mark as Solved'.

OK, it seems to have worked. Updating drivers solved the problem.

Many thanks.

axe0 · 17 Apr 2016

Good to hear :)