Recurrent Random BSOD, error: 0x000000f4

[Vaska90]

Two or three months back, my user account got corrupted and I couldn't login. I did chkdsk and was able to log on to a temporary account where I had no files or apps. As per the advice on Microsoft website, I created a new user account, transferred all my files into it, and later deleted the corrupted account. Ever since then, I am getting random recurrent BSODs with the error code 0x000000f4. Following are the steps I took:
a) Chkdsk (no issues)
b) Sfc scannow (no issues)
c) MSE virus scan (no viruses)
d) BIOS driver update
After updating BIOS driver, the error code changed to 0x0000007A. I have attached zip file from DM Log collector below.

 

[Arc]

0XF4 and 0x7A are the same thing, different expression.

Some file is missing there in your upload, so upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

We can suggest you the troubleshooting steps after checking that file.

____________________________________________________

BugCheck 7A, {fffff6fc806153a0, ffffffffc00000c0, 11042d880, fffff900c2a7401c}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+d4288 )

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

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

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc806153a0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc00000c0, error status (normally i/o status code)
Arg3: 000000011042d880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff900c2a7401c, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc00000c0 - This device does not exist.

BUGCHECK_STR:  0x7a_c00000c0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  SearchIndexer.

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

TRAP_FRAME:  fffff8800bbef4d0 -- (.trap 0xfffff8800bbef4d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c0210000 rbx=0000000000000000 rcx=fffff900c2a74010
rdx=0000000000000777 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000164288 rsp=fffff8800bbef668 rbp=fffff8800bbefa1f
 r8=fffff900c0213bb8  r9=0000000000000000 r10=fffff80003a0d000
r11=fffffa8009da6060 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
win32k+0xd4288:
fffff960`00164288 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003af2032 to fffff80003a7fa40

STACK_TEXT:  
fffff880`0bbef1b8 fffff800`03af2032 : 00000000`0000007a fffff6fc`806153a0 ffffffff`c00000c0 00000001`1042d880 : nt!KeBugCheckEx
fffff880`0bbef1c0 fffff800`03aa748b : fffffa80`0a2ef170 fffff880`0bbef330 fffff880`073abc00 fffffa80`0a2ef170 : nt! ?? ::FNODOBFM::`string'+0x3593a
fffff880`0bbef2a0 fffff800`03a8dd19 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff880`0bbef405 : nt!MiIssueHardFault+0x28b
fffff880`0bbef370 fffff800`03a7db6e : 00000000`00000000 fffff900`c2a7401c 00000000`00000000 00000000`0201027d : nt!MmAccessFault+0x1399
fffff880`0bbef4d0 fffff960`00164288 : fffff960`00160039 00000000`00000f2c 00000000`00000f2c fffff880`0bbefa00 : nt!KiPageFault+0x16e
fffff880`0bbef668 fffff960`00160039 : 00000000`00000f2c 00000000`00000f2c fffff880`0bbefa00 00000000`ffffffff : win32k+0xd4288
fffff880`0bbef670 00000000`00000f2c : 00000000`00000f2c fffff880`0bbefa00 00000000`ffffffff fffffa80`081738d0 : win32k+0xd0039
fffff880`0bbef678 00000000`00000f2c : fffff880`0bbefa00 00000000`ffffffff fffffa80`081738d0 fffff960`002c2109 : 0xf2c
fffff880`0bbef680 fffff880`0bbefa00 : 00000000`ffffffff fffffa80`081738d0 fffff960`002c2109 fffffa80`09cac1c0 : 0xf2c
fffff880`0bbef688 00000000`ffffffff : fffffa80`081738d0 fffff960`002c2109 fffffa80`09cac1c0 00000000`00000001 : 0xfffff880`0bbefa00
fffff880`0bbef690 fffffa80`081738d0 : fffff960`002c2109 fffffa80`09cac1c0 00000000`00000001 fffffa80`08f267c0 : 0xffffffff
fffff880`0bbef698 fffff960`002c2109 : fffffa80`09cac1c0 00000000`00000001 fffffa80`08f267c0 fffffa80`09cac060 : 0xfffffa80`081738d0
fffff880`0bbef6a0 fffffa80`09cac1c0 : 00000000`00000001 fffffa80`08f267c0 fffffa80`09cac060 fffff900`c2a76cd0 : win32k+0x232109
fffff880`0bbef6a8 00000000`00000001 : fffffa80`08f267c0 fffffa80`09cac060 fffff900`c2a76cd0 fffff960`0015778c : 0xfffffa80`09cac1c0
fffff880`0bbef6b0 fffffa80`08f267c0 : fffffa80`09cac060 fffff900`c2a76cd0 fffff960`0015778c 00000000`00000f2c : 0x1
fffff880`0bbef6b8 fffffa80`09cac060 : fffff900`c2a76cd0 fffff960`0015778c 00000000`00000f2c fffff880`0bbefa00 : 0xfffffa80`08f267c0
fffff880`0bbef6c0 fffff900`c2a76cd0 : fffff960`0015778c 00000000`00000f2c fffff880`0bbefa00 fffff900`c2a76cd0 : 0xfffffa80`09cac060
fffff880`0bbef6c8 fffff960`0015778c : 00000000`00000f2c fffff880`0bbefa00 fffff900`c2a76cd0 00000000`00000000 : 0xfffff900`c2a76cd0
fffff880`0bbef6d0 00000000`00000f2c : fffff880`0bbefa00 fffff900`c2a76cd0 00000000`00000000 fffffa80`09cac060 : win32k+0xc778c
fffff880`0bbef6d8 fffff880`0bbefa00 : fffff900`c2a76cd0 00000000`00000000 fffffa80`09cac060 fffff960`00156e40 : 0xf2c
fffff880`0bbef6e0 fffff900`c2a76cd0 : 00000000`00000000 fffffa80`09cac060 fffff960`00156e40 fffff900`c2a76cd0 : 0xfffff880`0bbefa00
fffff880`0bbef6e8 00000000`00000000 : fffffa80`09cac060 fffff960`00156e40 fffff900`c2a76cd0 fffff880`0bbefae0 : 0xfffff900`c2a76cd0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k+d4288
fffff960`00164288 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32k+d4288

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x7a_c00000c0_win32k+d4288

BUCKET_ID:  X64_0x7a_c00000c0_win32k+d4288

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7a_c00000c0_win32k+d4288

FAILURE_ID_HASH:  {955e8e02-8c37-1a3d-e881-c09d2afd273d}

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

 

[Vaska90]

MSINFO32 and other files added

Hi Arc, Thanks for responding. I have uploaded a new zip file with all the needed files including MSINFO32.

 

[Arc]

Your C drive is running out of space.

ITEM | VALUE
Drive | C:
Size | 58.50 GB (62,809,698,304 bytes)
Free Space | 3.80 GB (4,082,069,504 bytes)

Free up at least 10 GB, and see how it goes. Let us know.

 

[Vaska90]

Persistent but with reduced frequency

Hi Arc,
I freed up more than 10GB and observed for few days. BSOD persists, but with reduced frequency. Earlier it used to be twice everyday, now it's like once every 2 days or 1 and a half days.

Regards,
Vasanth

 

[Arc]

It is better to have a bigger C drive. 58 GB is not enough for it.

If possible, back up the data, Format the HDD, allot some more space to the C drive (80to 100 GB would be preferable) and perform a clean reinstall.

Hopefully that will be better.