BSOD, BCCode: 109

By radish
May 5, 2011
Post New Reply
  1. I'm having trouble with my computer with this BSOD memory dump. I get this BSOD often sometimes it does it few days . If someone will help me step by step to fixing this problem. This computer is new i buyed him 2 weeks ago.
    Thank You

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.
    Locale ID: 1045

    Additional information about the problem:
    BCCode: 109
    BCP1: A3A039D89EF72650
    BCP2: B3B7465EF173F846
    BCP3: FFFFF80003282000
    BCP4: 0000000000000001
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Do the following...

    How to find and post your Minidump Files:

    My Computer > C Drive > Windows Folder > Minidump Folder > Minidump Files.

    It is these files that we need (not the folder). Attach to your next post the five most recent dumps. Notice the Manage Attachments button at the bottom when you go to post the next time. You can Zip up to five files per Zip; if you only have one or two you don’t need to zip them, just attach as is. Please do us a favor and don’t Zip each one individually.
  3. Mark56

    Mark56 TechSpot Paladin Posts: 1,889

    If you have not made any changes to this PC at only two weeks old I would return it to the supplier without hesitation.

    The error code 109 is often a faulty device driver but that is not likely in a new PC if you have not added anything, the other more common reason is hardware and the most likely thing is the memory. Take it back and get it replaced.
  4. radish

    radish TS Rookie Topic Starter

    I have something like that:

    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [ ]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is:
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Machine Name:
    Kernel base = 0xfffff800`0300a000 PsLoadedModuleList = 0xfffff800`03247e50
    Debug session time: Thu May 5 13:29:32.193 2011 (GMT+2)
    System Uptime: 5 days 17:03:00.729
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * *
    * Bugcheck Analysis *
    * *

    Use !analyze -v to get detailed debugging information.

    BugCheck 109, {a3a039d89ef72650, b3b7465ef173f846, fffff80003282000, 1}

    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    Followup: MachineOwner

    4: 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 (URL)
    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: a3a039d89ef72650, Reserved
    Arg2: b3b7465ef173f846, Reserved
    Arg3: fffff80003282000, 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



    PROCESS_NAME: System


    LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8000307a740

    fffff880`0337e598 00000000`00000000 : 00000000`00000109 a3a039d8`9ef72650 b3b7465e`f173f846 fffff800`03282000 : nt!KeBugCheckEx



    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME: Unknown_Image



    Followup: MachineOwner

    4: kd> lmvm Unknown_Module
    start end module name
  5. Mark56

    Mark56 TechSpot Paladin Posts: 1,889

    I would put my money on that being faulty RAM, return the PC and get it replaced.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...