BSOD Multiple Times Daily After Windows 10 Upgrade on Dell XPS 720


  1. Posts : 2
    Windows 10
       #1

    BSOD Multiple Times Daily After Windows 10 Upgrade on Dell XPS 720


    Please see the attached V2 collector log and let me know if you need anything else. Computer has passed the Windows Memory Diagnostic. The bug check code is: 0x00000109 referring to it being caused by driver ntoskrnl.exe at address: ntoskrnl.exe+1bc900. I have also noticed the system will sometimes freeze up for a minute or two and then resume normal operation in Windows etc.. Thanks for your help.
    BSOD Multiple Times Daily After Windows 10 Upgrade on Dell XPS 720 Attached Files
      My ComputerSystem Spec


  2. Posts : 274
    Windows 8.1 Enterprise x64
       #2

    The CRITICAL_STRUCTURE_CORRUPTION bug check has a value of 0x00000109. This indicates that the kernel has detected critical kernel code or data corruption.
    Parameter 0x4 = 0x1c - driver object corruption
    Code:
    Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\071119-14937-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*
    Symbol search path is: SRV*
    Executable search path is: 
    Windows 10 Kernel Version 18362 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 18362.1.amd64fre.19h1_release.190318-1202
    Machine Name:
    Kernel base = 0xfffff805`08200000 PsLoadedModuleList = 0xfffff805`086432f0
    Debug session time: Fri Jul 12 01:57:29.536 2019 (UTC + 2:00)
    System Uptime: 0 days 0:12:00.343
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ..............
    Loading User Symbols
    Loading unloaded module list
    ....................
    For analysis of this file, run !analyze -v
    1: kd> !analyze
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 109, {a39fc0dac418d820, b3b6cd61169b0d79, ffff81822f63ed90, 1c}
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    Followup:     MachineOwner
    ---------
    
    1: 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: a39fc0dac418d820, Reserved
    Arg2: b3b6cd61169b0d79, Reserved
    Arg3: ffff81822f63ed90, Failure type dependent information
    Arg4: 000000000000001c, 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
    	8   : Object type
    	9   : A processor IVT
    	a   : Modification of a system service function
    	b   : A generic session data region
    	c   : Modification of a session function or .pdata
    	d   : Modification of an import table
    	e   : Modification of a session import table
    	f   : Ps Win32 callout modification
    	10  : Debug switch routine modification
    	11  : IRP allocator modification
    	12  : Driver call dispatcher modification
    	13  : IRP completion dispatcher modification
    	14  : IRP deallocator modification
    	15  : A processor control register
    	16  : Critical floating point control register modification
    	17  : Local APIC modification
    	18  : Kernel notification callout modification
    	19  : Loaded module list modification
    	1a  : Type 3 process list corruption
    	1b  : Type 4 process list corruption
    	1c  : Driver object corruption
    	1d  : Executive callback object modification
    	1e  : Modification of module padding
    	1f  : Modification of a protected process
    	20  : A generic data region
    	21  : A page hash mismatch
    	22  : A session page hash mismatch
    	23  : Load config directory modification
    	24  : Inverted function table modification
    	25  : Session configuration modification
    	26  : An extended processor control register
    	27  : Type 1 pool corruption
    	28  : Type 2 pool corruption
    	29  : Type 3 pool corruption
    	2a  : Type 4 pool corruption
    	2b  : Modification of a function or .pdata
    	2c  : Image integrity corruption
    	2d  : Processor misconfiguration
    	2e  : Type 5 process list corruption
    	2f  : Process shadow corruption
    	30  : Retpoline code page corruption
    	101 : General pool corruption
    	102 : Modification of win32k.sys
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
    
    PROCESSES_ANALYSIS: 1
    
    SERVICE_ANALYSIS: 1
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202
    
    SYSTEM_MANUFACTURER:  Dell Inc.                
    
    SYSTEM_PRODUCT_NAME:  Dell XPS720                  
    
    BIOS_VENDOR:  Dell Inc.                
    
    BIOS_VERSION:  A06
    
    BIOS_DATE:  04/01/2008
    
    BASEBOARD_MANUFACTURER:  Dell Inc.          
    
    BASEBOARD_PRODUCT:  0P611C
    
    BASEBOARD_VERSION:  A00
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: a39fc0dac418d820
    
    BUGCHECK_P2: b3b6cd61169b0d79
    
    BUGCHECK_P3: ffff81822f63ed90
    
    BUGCHECK_P4: 1c
    
    CPU_COUNT: 4
    
    CPU_MHZ: a6b
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 17
    
    CPU_STEPPING: 7
    
    CPU_MICROCODE: 6,17,7,0 (F,M,S,R)  SIG: 70B'00000000 (cache) 70B'00000000 (init)
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    
    BLACKBOXNTFS: 1 (!blackboxntfs)
    
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    
    BLACKBOXWINLOGON: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  BAD_STACK_0x109
    
    BUGCHECK_STR:  0x109
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_SESSION_HOST:  MICHAL
    
    ANALYSIS_SESSION_TIME:  07-12-2019 17:07:40.0047
    
    ANALYSIS_VERSION: 10.0.18362.1 amd64fre
    
    STACK_TEXT:  
    ffff918f`40778fc8 00000000`00000000 : 00000000`00000109 a39fc0da`c418d820 b3b6cd61`169b0d79 ffff8182`2f63ed90 : nt!KeBugCheckEx
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  81a83ae0317433a47fcc36991983df3b6e638b71
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6e16edd8c7dd677734fdbcd2397a2e35e9fae964
    
    THREAD_SHA1_HASH_MOD:  76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3
    
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Unknown_Module
    
    IMAGE_NAME:  Unknown_Image
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    BUCKET_ID:  BAD_STACK_0x109
    
    PRIMARY_PROBLEM_CLASS:  BAD_STACK_0x109
    
    FAILURE_BUCKET_ID:  BAD_STACK_0x109
    
    TARGET_TIME:  2019-07-11T23:57:29.000Z
    
    OSBUILD:  18362
    
    OSSERVICEPACK:  239
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  272
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  1972-02-02 09:33:06
    
    BUILDDATESTAMP_STR:  190318-1202
    
    BUILDLAB_STR:  19h1_release
    
    BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202
    
    ANALYSIS_SESSION_ELAPSED_TIME:  11be
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:bad_stack_0x109
    
    FAILURE_ID_HASH:  {b4d7023a-05c3-49b2-3ea4-6240fe57d90e}
    
    Followup:     MachineOwner
    ---------
    
    1: kd> .load pde
    =========================================================================================
     PDE v11.3 - Copyright 2017 Andrew Richards
    =========================================================================================
    1: kd> !dpx
    Start memory scan  : 0xffff918f40778fc8 ($csp)
    End memory scan    : 0xffff918f4077a000 (Kernel Stack Base)
    
                    r9 : 0xffff81822f63ed90 : 0xfffff8050d6fbae0 : Ntfs!NtfsFsdCreate
    0xffff918f40778fe8 : 0xffff81822f63ed90 : 0xfffff8050d6fbae0 : Ntfs!NtfsFsdCreate
    
    1: kd> !blackboxpnp
        PnpActivityId      : {00000000-0000-0000-0000-000000000000}
        PnpActivityTime    : 132073626232589974
        PnpEventInformation: 3
        PnpEventInProgress : 0
        PnpProblemCode     : 24
        PnpVetoType        : 0
        DeviceId           : SW\{DDF4358E-BB2C-11D0-A42F-00A0C9223196}\{97EBAACB-95BD-11D0-A3EA-00A0C9223196}
        VetoString         :
    The analysis did not show what driver might be guilty, therefore I recommend that you enable Driver Verifier (Enable and Disable Driver Verifier in Windows 10) to detect a faulty driver
      My ComputerSystem Spec


  3. Posts : 26,550
    windows 10 professional version 1607 build 14393.969 64 bit
       #3

    See rule #4.

    https://www.tenforums.com/misc.php?do=showrules

    Code:
    No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc) - it is forum policy that no help shall be given to people who knowingly steal software or services.
      My ComputerSystem Spec


  4. Posts : 2
    Windows 10
    Thread Starter
       #4

    I enabled driver verifier and had the crash again. Please see the attached minidump file.
    BSOD Multiple Times Daily After Windows 10 Upgrade on Dell XPS 720 Attached Files
      My ComputerSystem Spec


  5. Posts : 274
    Windows 8.1 Enterprise x64
       #5

    1. Disable Driver Verifier
    2. Run Driver Verifier Manager
    3. Select "Create custom settings (for code developers)"
    4. Select all standard settings and 2 additional settings ("Force pending I/O requests" and "IRP Logging")
    5. Select "select driver names from a list"
    6. Select all drivers except Microsoft drivers
    7. Reboot computer
      My ComputerSystem Spec

  6.    #6

    FYI - the system can still BSOD "normally" even if Driver Verifier is enabled.
    It depends on how the drivers react to the stresses that DV places on them.
    For example, a regular BSOD crash can occur BEFORE the driver succumbs to the strss of Driver Verifier
    In cases like this, I usually suggest running Driver Verifier through at least 3 crashes - to increase the likelihood of capturing at least 1 Driver Verifier enabled memory dump.
      My ComputerSystem Spec



  7. Posts : 274
    Windows 8.1 Enterprise x64
       #7

    The cause of BSoD is fixed. The object of some driver is damaged. But as you can see, it is impossible to determine which is why I suggested turning on the Driver Verifier to determine what driver it is. Unless there is a way to determine the driver having a damaged object
      My ComputerSystem Spec

  8. Ztruker's Avatar
    Posts : 8,524
    Windows 10 Pro X64 1903 189362.439
       #8

    Folks, the OP has been banned so no point in continuing this thread. @Brink, can you lock it?
      My ComputersSystem Spec


 

Related Threads
random BSOD issues multiple times daily in BSOD Crashes and Debugging
Hello, I am getting a BSOD at random multiple times daily. I have run the windbg and can only find a crash related to csrss.exe but I can't figure out how to fix it. This is a new windows 10 Enterprise installation which I was getting BSOD on...
86517 Hey. So, I built my computer in August of 2015, and since then I've had nearly daily problems with BSODs. For a few months (between October 2015 and March 2016) they had gone away (no idea what happened to make them stop), but then randomly...
My problem is very similar to one described by tomzino earlier this month in this forum. Since upgrading from windows 7 home premium to windows 10, my computer gets a BSOD and reboots daily; so far in November it has crashed 20 times. The only...
I have tried upgrading my Dell venue 8 Pro many times from GWX, installation media and direct download in normal and also after reset of tablet with secure boot and also removing secure boot, removing fast boot and with fast boot using all...
Solved Multiple daily BSOD since Upgrade to Win10 in BSOD Crashes and Debugging
Hi, I am losing my mind and have run out of places to check for help, so hoping someone here can assist: I installed Win 10 on 8/8. Since then receiving the same 2 BSOD multiple times every day, but no indication as to the cause. I have...
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 06:32.
Find Us