Multiple Random BSODs 0x00000109 Solved

  1. Posts : 2
    Windows 10 Home
       18 Feb 2017 #1

    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
      My ComputerSystem Spec

  2.    18 Feb 2017 #2

    All your latest dumpfiles are
    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                                    *
    *                                                                             *
    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
    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.
    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
    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

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

  3. Posts : 2
    Windows 10 Home
    Thread Starter
       19 Feb 2017 #3

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


Related Threads
Hi, I would really appreciate it if anyone could shed any light on this. The PC was originally Windows 7 and I upgraded to Windows 10 last year. The crashes seem to be random, sometimes when it's sitting idle, sometimes whilst I'm working. ...
I'm at the end of my rope TenForums. I have been dealing with random BSODs for a while now and I just don't know what to do. Please help me, I am desperate. Logs are attached. PS If you guys can't help me, can you at least tell me how you analyze...
Random BSODs in BSOD Crashes and Debugging
Hi hope u guys can help me. would be very thankful :) Got a new system 1-2 Months old. Fresh installed Windows 10 Pro Build 1511. But I am getting Bluescreens (not sure what the cause is) random. For example once I plugged in an USB-Stick I got...
Heres my minidumps: 35760 Specs: i5 4690k @ stock speeds, GTX 980ti @ 1416mhz (Gaming 6G Custom cooler by MSI), 24gb of DDR3 (I did a MEMTest on this and it completed fine. Peripherals: Steelseries Rival gaming mouse, Cooler Master Quickfire...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 20:01.
Find Us