Frequent BSOD, error 0x1000007e

[Martin60]

My sister's computer has been crashing every couple of days since January, usually during the day when she is at work.
I have tried scanning for virus/malware with McAfee and Malwarebytes, running Memtest86, updating video drivers, and running windows update all with negative results.
Thanks for any help you can give me.
DM Log Collector file attached.

 

[cipley]

Hi, welcome to seven forums

there are 2 most common errors in your dump files, which are:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff96000100e41, fffff88003785848, fffff880037850a0}

Probably caused by : win32k.sys ( win32k!CAutoMutex::CAutoMutex+15 )
Followup: MachineOwner
---------

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.

and:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8800155ba10, 2, 8, fffff8800155ba10}

Probably caused by : CLFS.SYS ( CLFS!CClfsContainer::Close+23 )

Followup: MachineOwner
---------

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.

both of them point to a system file...

try to do the following:
- Open elevated command prompt (Start > Run... > type cmd then enter
- type chkdsk /f
then see if it finds any error...

I'll try to go through it when I got home

 

[Martin60]

Ran chkdisk /f

Only error:

CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

Would that cause BSOD?