BSOD (minidump included)

By freshhh
Oct 19, 2008
  1. BSOD (minidump included)
    Windows XP x64 PRO
    v5.2 Build 3790.srv03_sp2_gdr.080813-1204
    Fully updated til october 2008 !
    Flash & Shockwave players updated.

    Hi folks,

    I keep having BSOD so please help me to find what is guilty !

    Most error reports have got the same error, only the latest is a different error and seems to be related to Netlimiter (only happend once) so I need support for others in priority...

    Feel free to download all minidumps (attached file) or here :



    Windows XP x64 PRO
    v5.2 Build 3790.srv03_sp2_gdr.080813-1204
    Fully updated til october 2008 !
    Flash & Shockwave players updated.

    Microsoft (R) Windows Debugger Version 6.9.0003.113 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\TEST\MINIDUMP\Mini101808-20.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Executable search path is:
    *** WARNING: Unable to verify checksum for ntkrnlmp.exe
    Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 3790.srv03_sp2_gdr.080813-1204
    Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
    Debug session time: Sat Oct 18 21:38:12.281 2008 (GMT+2)
    System Uptime: 0 days 0:37:45.408
    *** WARNING: Unable to verify checksum for ntkrnlmp.exe
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * *
    * Bugcheck Analysis *
    * *

    Use !analyze -v to get detailed debugging information.

    BugCheck 109, {a3a03a382ae616fc, b3b746be7d64f410, fffffadf9cc8ead8, 8}

    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    Followup: MachineOwner

    3: 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: a3a03a382ae616fc, Reserved
    Arg2: b3b746be7d64f410, Reserved
    Arg3: fffffadf9cc8ead8, Failure type dependent information
    Arg4: 0000000000000008, 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 fffff8000102e890

    fffffadf`90eb0838 00000000`00000000 : 00000000`00000109 a3a03a38`2ae616fc b3b746be`7d64f410 fffffadf`9cc8ead8 : nt!KeBugCheckEx



    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME: Unknown_Image



    Followup: MachineOwner
Topic Status:
Not open for further replies.

Similar Topics

Add your comment to this article

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