Windows 10: Multiple Random BSODs 0x00000109

On my Windows 10 desktop I've got muliple random BSODs with the same error 0x00000109It happens randomly, even few minutes after first boot in the morningMy first attempt was to change cooler (to prevent overheating) - no resultThen I test another memory modules - same BSOD All drivers is up-to-date (checked with Driver Booster 4)DM logs in attachment

:)

 

Windows 10 pro (Avgntflt.sys) - BSOD

I got lots of BSOD since avira install on my windows 10 pro (Avgntflt.sys) and always while shuting down.

Uninstall AVIRA: NO MORE BSOD !

Eddy

 

random Freezing leads to BSOD. I give up.

Stop code is random.

like CRITICAL_PROCESS_DIED, BAD_SYSTEM_CONFIG_INFO, DPC_WATCHDOG_VIOLATION..

I've got multiple BSOD and the stop code is that random.

right now after multiple debugging the issue, I hypothetically assume it's my nvme fault.

I've ordered a new nvme drive and gonna retest the system if this will works.

 

All your latest dumpfiles are
Code: Use !analyze -v to get detailed debugging information. BugCheck 109, {a3a000e860d574ff, b3b70d6eb3551639, ffffc18fc1856040, 1f} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 2: 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: a3a000e860d574ff, Reserved Arg2: b3b70d6eb3551639, Reserved Arg3: ffffc18fc1856040, Failure type dependent information Arg4: 000000000000001f, 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[/quote] There are a few older drivers in your driver modules list.
But i found these two drivers
Itcs_cng_krn64 Thu Jun 25 15:00:20 2015 (558BFB64)
Itcspe64 Thu Jun 25 15:06:51 2015
These drivers belong to infotec VIPnet and is know for BSOD in windows 10.
See this link https://answers.microsoft.com/en-us/...5c4e90f?page=2

Look for a newer version and/or uninstall and see if this stops your BSOD problem.

 

It seems working!
Full day without crashes.
Thanks a lot!