BSOD - fileinfo.sys and ntoskrnl.exe

That is what I was eager to know ....

Best of luck.

According the the crash dump, it is memory corruption.

Code:

STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8000344066f - nt!MiLogFailedDriverLoad+ff
    [ ff:bf ]
1 error : !nt (fffff8000344066f)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

You may follow it: Guide to using Memtest86+ - Geeks to Go Forums

BTW, how many slots are there, and how many RAM modules do you have? What is the temperature of your motherboard and CPU after a substantially high time of run? Upload a screenshot of Speccy summery tab after a few hours of computer run.

Heating cannot be the issue there, as I am seeing.

The recent crash is network related, but nothing precise.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88001797718, fffff880035858b8, fffff88003585110}

Probably caused by : NETIO.SYS ( NETIO!NetiopIoWorkItemRoutine+38 )

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

Network, disc and memory ... at the same time ....scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Is there any ?

bigdave said:

I noticed my ram was at 1333 instead of 1600 frequency, would that cause the issues I've had?

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89cda26de, b3b7465eef56f634, fffff80003400514, 1}

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

Followup: memory_corruption
---------

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89cda26de, Reserved
Arg2: b3b7465eef56f634, Reserved
Arg3: fffff80003400514, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

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


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800030e2fc0

STACK_TEXT:  
fffff880`03377498 00000000`00000000 : 00000000`00000109 a3a039d8`9cda26de b3b7465e`ef56f634 fffff800`03400514 : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8000340066f - nt!SepRemoveDisabledGroupsAndPrivileges+15b
    [ d2:92 ]
1 error : !nt (fffff8000340066f)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

Memory corruption, for sure. Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

Also, if you are sure that there are some abnormal reduction in RAM voltage, you may increase it back to default.