Windows 10: BSOD during machine bootup because of a WPF application

Discus and support BSOD during machine bootup because of a WPF application in Windows 10 Drivers and Hardware to solve the problem; Hi, I am experiencing a BSOD quite consistently in my new Lenovo laptops(T470 and E480).Crash dump analysis refers to my .net application. But the... Discussion in 'Windows 10 Drivers and Hardware' started by Venkat_G, Nov 27, 2018.

  1. VENKAT_G
    Venkat_G Win User

    BSOD during machine bootup because of a WPF application


    Hi,

    I am experiencing a BSOD quite consistently in my new Lenovo laptops(T470 and E480).Crash dump analysis refers to my .net application. But the module refers to display driver. I need help on this.

    thanks in advance. Below is the windbg out.



    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************



    Use !analyze -v to get detailed debugging information.

    BugCheck 1A, {41790, fffffb800424a070, 75, 76}

    Probably caused by : dxgmms2.sys ( dxgmms2!VIDMM_RECYCLE_HEAP_PHYSICAL_VIEW::LockRange+30c1c )

    Followup: MachineOwner
    ---------

    nt!KeBugCheckEx:
    fffff800`e27c6690 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8602`d6ac6550=000000000000001a
    6: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
    Arg2: fffffb800424a070
    Arg3: 0000000000000075
    Arg4: 0000000000000076

    Debugging Details:
    ------------------


    KEY_VALUES_STRING: 1


    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 401

    BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

    SYSTEM_MANUFACTURER: LENOVO

    SYSTEM_PRODUCT_NAME: 20KNS0V400

    SYSTEM_SKU: LENOVO_MT_20KN_BU_Think_FM_ThinkPad E480

    SYSTEM_VERSION: ThinkPad E480

    BIOS_VENDOR: LENOVO

    BIOS_VERSION: R0PET47W (1.24 )

    BIOS_DATE: 08/29/2018

    BASEBOARD_MANUFACTURER: LENOVO

    BASEBOARD_PRODUCT: 20KNS0V400

    BASEBOARD_VERSION: SDK0J40697 WIN

    DUMP_TYPE: 1

    BUGCHECK_P1: 41790

    BUGCHECK_P2: fffffb800424a070

    BUGCHECK_P3: 75

    BUGCHECK_P4: 76

    BUGCHECK_STR: 0x1a_41790

    CPU_COUNT: 8

    CPU_MHZ: 708

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 8e

    CPU_STEPPING: a

    CPU_MICROCODE: 6,8e,a,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)

    BLACKBOXBSD: 1 (    !blackboxbsd)


    BLACKBOXPNP: 1 (    !blackboxpnp)


    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    PROCESS_NAME: iMobility.exe

    CURRENT_IRQL: 2

    ANALYSIS_SESSION_HOST: DESKTOP-78P4QL8

    ANALYSIS_SESSION_TIME: 11-20-2018 02:45:57.0763

    ANALYSIS_VERSION: 10.0.18239.1000 amd64fre

    LAST_CONTROL_TRANSFER: from fffff800e2725476 to fffff800e27c6690

    STACK_TEXT:
    ffff8602`d6ac6548 fffff800`e2725476 : 00000000`0000001a 00000000`00041790 fffffb80`0424a070 00000000`00000075 : nt!KeBugCheckEx
    ffff8602`d6ac6550 fffff800`e2707cea : 00000000`00000000 ffff8602`d6ac6e10 00000000`00000000 00000000`00000000 : nt!MiDeletePteRun+0xe46
    ffff8602`d6ac6740 fffff800`e2709b01 : ffff8602`d6ac6919 00000000`00000000 ffff8602`d6ac6919 ffff8602`d6ac6e70 : nt!MiDeleteVaTail+0xba
    ffff8602`d6ac68a0 fffff800`e2709aa2 : ffff8602`d6ac6e70 ffffca80`00074b00 ffff8602`00000000 ffff8602`00000000 : nt!MiWalkPageTablesRecursively+0x701
    ffff8602`d6ac6980 fffff800`e2709aa2 : ffff8602`d6ac6e70 ffffcae5`400003a0 ffff8602`00000001 ffff8602`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
    ffff8602`d6ac6a60 fffff800`e2709aa2 : ffff8602`d6ac6e70 ffffcae5`72a00000 ffff8602`00000002 ffff8602`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
    ffff8602`d6ac6b40 fffff800`e27077a7 : ffff8602`d6ac6e70 ffffcae5`72b95000 ffffe786`00000003 ffff8602`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
    ffff8602`d6ac6c20 fffff800`e26f1eb3 : ffff8602`d6ac6e70 ffffba01`00000001 ffffba01`00000000 ffffba01`00000000 : nt!MiWalkPageTables+0x1e7
    ffff8602`d6ac6d10 fffff800`e2b9e863 : ffffba01`00000004 ffffba01`9f7f3700 ffffba01`a1964b90 00000000`00000000 : nt!MiDeleteVad+0x8d3
    ffff8602`d6ac7040 fffff800`e2ad00e0 : ffffba01`a1964b90 00000000`00000000 00000000`0e570000 00000000`00000000 : nt!MiUnmapVad+0xa7
    ffff8602`d6ac7070 fffff800`e2acdb1f : 00000000`00000000 ffffba01`a2769000 00000000`00000000 00000000`00000000 : nt!MiUnmapViewOfSection+0x120
    ffff8602`d6ac7150 fffff800`e25994cc : ffffe786`dbf070b0 00000000`0e570000 00000000`d6ac6d00 ffffe786`dbf070b0 : nt!MmUnmapViewOfSection+0xf
    ffff8602`d6ac7180 fffff800`e25815f3 : 00000000`003f0000 ffffe786`db70db70 00000000`00000000 ffffba01`9f7ff930 : dxgmms2!VIDMM_RECYCLE_HEAP_PHYSICAL_VIEW::LockRange+0x30c1c
    ffff8602`d6ac7210 fffff800`e257f9a8 : ffffe786`dbb495b0 00000000`003f0000 00000000`00000000 0000000c`00001000 : dxgmms2!VIDMM_RECYCLE_RANGE::Lock+0x77
    ffff8602`d6ac7260 fffff800`e257d88b : ffffe786`db8a4830 ffffe786`db70db70 00000000`00000000 00000000`003f0000 : dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Lock+0x78
    ffff8602`d6ac72c0 fffff800`e256e43a : ffffe786`db8a4830 ffffba01`9f96ee00 00000000`00000000 ffff8602`d6ac7400 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR:BSOD during machine bootup because of a WPF application :probeAndLockAllocation+0x7b
    ffff8602`d6ac7340 fffff800`e258214f : ffffba01`9f96ee00 00000000`00000000 00000000`00000000 00000000`00000001 : dxgmms2!VIDMM_GLOBAL:BSOD during machine bootup because of a WPF application :probeAndLockAllocation+0x56
    ffff8602`d6ac7390 fffff800`e2581ddf : ffffba01`9f7ff930 ffffba01`9f96eea8 ffffe786`db70db70 00000000`00000000 : dxgmms2!VIDMM_SEGMENT::LockAllocationBackingStore+0xab
    ffff8602`d6ac7450 fffff800`e2570923 : ffffba01`a2a8b580 ffffba01`9f96eea8 00000000`00000000 ffffba01`9f96e000 : dxgmms2!VIDMM_SYSMEM_SEGMENT::CommitResource+0x8f
    ffff8602`d6ac7490 fffff800`e2574551 : 00000000`00000000 00000000`00000000 ffff8602`00000000 ffff8602`d6ac76a0 : dxgmms2!VIDMM_GLOBAL:BSOD during machine bootup because of a WPF application :pageInOneAllocation+0x1e3
    ffff8602`d6ac75a0 fffff800`e258fd86 : 00000000`00000001 ffff8602`00000000 00000000`001ad275 00000000`00000001 : dxgmms2!VIDMM_GLOBAL:BSOD during machine bootup because of a WPF application :processDeferredCommand+0x861
    ffff8602`d6ac7910 fffff800`e258f0b9 : ffffe786`d0fc6290 fffff800`e2793401 ffffe786`d0fc6300 00000000`00000000 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xc16
    ffff8602`d6ac7ae0 fffff800`e26904f7 : ffffba01`9f7f3700 fffff800`e258f0b0 ffffa581`51c00180 000005ed`bd9bbfff : dxgmms2!VidMmWorkerThreadProc+0x9
    ffff8602`d6ac7b10 fffff800`e27cdb06 : ffffa581`51c00180 ffffba01`9f7f3700 fffff800`e26904b0 00610077`00650072 : nt!PspSystemThreadStartup+0x47
    ffff8602`d6ac7b60 00000000`00000000 : ffff8602`d6ac8000 ffff8602`d6ac1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    THREAD_SHA1_HASH_MOD_FUNC: 1743fd896e0c5efc8e0cf2f5718674f37bdad743

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: c004c718ae9fcee55c43eb84398b8fef2d0b74c3

    THREAD_SHA1_HASH_MOD: c3ebb425d8917d4cd41701fb32814d8505d2bbc4

    FOLLOWUP_IP:
    dxgmms2!VIDMM_RECYCLE_HEAP_PHYSICAL_VIEW::LockRange+30c1c
    fffff800`e25994cc 90 nop

    FAULT_INSTR_CODE: f4f3e990

    SYMBOL_STACK_INDEX: c

    SYMBOL_NAME: dxgmms2!VIDMM_RECYCLE_HEAP_PHYSICAL_VIEW::LockRange+30c1c

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME:     dxgmms2

    IMAGE_NAME: dxgmms2.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    IMAGE_VERSION: 10.0.17134.407

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 30c1c

    FAILURE_BUCKET_ID: 0x1a_41790_dxgmms2!VIDMM_RECYCLE_HEAP_PHYSICAL_VIEW::LockRange

    BUCKET_ID: 0x1a_41790_dxgmms2!VIDMM_RECYCLE_HEAP_PHYSICAL_VIEW::LockRange

    PRIMARY_PROBLEM_CLASS: 0x1a_41790_dxgmms2!VIDMM_RECYCLE_HEAP_PHYSICAL_VIEW::LockRange

    TARGET_TIME: 2018-11-19T15:07:59.000Z

    OSBUILD: 17134

    OSSERVICEPACK: 0

    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: 2018-11-01 12:26:19

    BUILDDATESTAMP_STR: 180410-1804

    BUILDLAB_STR: rs4_release

    BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

    ANALYSIS_SESSION_ELAPSED_TIME: cbf

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x1a_41790_dxgmms2!vidmm_recycle_heap_physical_view::lockrange

    FAILURE_ID_HASH: {1140bfce-fb26-e25c-55cf-3aacd3065201}

    Followup: MachineOwner

    :)
     
    Venkat_G, Nov 27, 2018
    #1
  2. MRSEANKON
    MrSeanKon Win User

    Enable visual styles in WPF application

    EUREKA!

    Steps:
    1) I made a Windows form (HostWPF namespace, Form1 is the form).
    2) I added a reference => System.Windows.Forms.Integration which contains classes that enable interoperation between the Windows Forms and WPF technologies. When you use System.Windows.Forms.Integration classes, you can host Windows Forms controls on WPF pages, and WPF elements in Windows Forms-based applications.
    3) Then added a control (damn Vi$ual $tudio 2010 does not allow to add a WPF window) but after adding I edited the XMAL code in the way I want *Wink BSOD during machine bootup because of a WPF application ;)
    4) The next steps are simple. Download the first attachment. But => see the photo.
    It crashes!!!!!
    5) Finally???
    We must use System.Windows.Forms.Application.Exit(); command because the WPF window behaves like a classical Windows Form.
    Download the second attachment. Note that the Windows form's name is Initial.
    Enjoy!
     
    MrSeanKon, Nov 27, 2018
    #2
  3. MRSEANKON
    MrSeanKon Win User
    Terminate WPF/Windows forms applications....

    WPF has no concept of MDI applications. In fact Microsoft is trying to discourage any one using that form of application. I'm new to WPF and I really like MDI applications. It allows me to move quickly between windows and compare the content of different windows. Furthermore, sometime the content of one window is useful for another so I can copy and paste. I think it's a great user experience for working mode.
    To continue, download the attachment!
    It includes two folders, they are very simple code.
    The point is how you can terminate an application (Windows Form and WPF).
     
    MrSeanKon, Nov 27, 2018
    #3
  4. FORDGT90CONCEPT
    FordGT90Concept Win User

    BSOD during machine bootup because of a WPF application

    Enable visual styles in WPF application

    I think WPF is incompatible with Visual Styles. Visual Styles is for WinForms. WPF is an entirely different animal.
     
    FordGT90Concept, Nov 27, 2018
    #4
Thema:

BSOD during machine bootup because of a WPF application

Loading...

  1. BSOD during machine bootup because of a WPF application - Similar Threads - BSOD during machine

  2. File open dialog crashes randomly in WPF application

    in Windows 10 Gaming
    File open dialog crashes randomly in WPF application: Hi,In my application file open dialog crashes randomly in WPF application based .Net framework. In event viewer logs, it reports Access violation exception in ntdll.dllThis issue occurs only with new style file open dialog box for file dialogs from both Microsoft.Win32 and...

  3. File open dialog crashes randomly in WPF application

    in Windows 10 Software and Apps
    File open dialog crashes randomly in WPF application: Hi,In my application file open dialog crashes randomly in WPF application based .Net framework. In event viewer logs, it reports Access violation exception in ntdll.dllThis issue occurs only with new style file open dialog box for file dialogs from both Microsoft.Win32 and...

  4. Asking for Administrator permission in a WPF application despite setting...

    in Windows 10 Gaming
    Asking for Administrator permission in a WPF application despite setting...: 0I developed a WPF application using .NET 5 and I must run it with administrator privileges. I have created a setup project and added the primary output of my WPF application to it.To accomplish this, I have made sure to set the requestedExecutionLevel attribute to...

  5. BSOD on bootup

    in Windows 10 BSOD Crashes and Debugging
    BSOD on bootup: Hey, i get BSOD on bootup. I cant do anything. I have tried every solution. I have heard about resetting pc with USB, if so. How do i do that. Thanks https://answers.microsoft.com/en-us/windows/forum/all/bsod-on-bootup/677dc20e-952d-4edb-9da1-db1f622ac0f2

  6. BSOD on bootup

    in Windows 10 BSOD Crashes and Debugging
    BSOD on bootup: Hey, i get BSOD on bootup. I cant do anything. I have tried every solution. I have heard about resetting pc with USB, if so. How do i do that. Thanks https://answers.microsoft.com/en-us/windows/forum/all/bsod-on-bootup/9afc0361-db50-42de-8e6b-43ee89203042

  7. BSOD during bootup (black screen 2min -> BSOD)

    in Windows 10 BSOD Crashes and Debugging
    BSOD during bootup (black screen 2min -> BSOD): Hello I recently upgraded to Windows 10 from 7. I did choose the non-clean install, and i wish to keep it this way. i do NOT wish to clean install, as id rather just fix the problem. Anyways, my problem is; During the boot process, the pc startet to take a long time,...

  8. Keyboard dead during bootup

    in Windows 10 Drivers and Hardware
    Keyboard dead during bootup: I'm trying to replace my old Dell keyboard with a G.Skill Ripjaws gaming keyboard. Unfortunately, it only works after the system boots up, which means I can't use function keys at bootup. I've written to G.Skill already. But just in case this problem is not a glitch in...

  9. Black screen and WAIT during bootup

    in Windows 10 Performance & Maintenance
    Black screen and WAIT during bootup: For two years I have had three hard drives installed. One small one went bad and at bootup I would get that information with "Press F1 to resume" which I would do and then windows would load. I upgraded to windows 10 from 7 three weeks ago, same message, and no problem, as it...

  10. black screen during bootup

    in Windows 10 Support
    black screen during bootup: During boot up I get a black screen for about 1 min then the login for my account. I notice a lot of hard drive activity during the black screen. I'm using amd-catalyst-15.10beta-64bit-win10-win8.1-win7-oct12.exe (latest one). Win 10 works fine except for the black screen....