Windows 10: Windows Server 2019 BSOD - identifying an offending driver

Discus and support Windows Server 2019 BSOD - identifying an offending driver in Windows 10 Drivers and Hardware to solve the problem; Hello, I know Windows 10 and 2019 are fairly similar, so I'm hoping it's okay to post this question here. I recently had a server BSOD on me, and... Discussion in 'Windows 10 Drivers and Hardware' started by DanielCOMESA, Apr 9, 2020.

  1. DANIELCOMESA
    DanielCOMESA Win User

    Windows Server 2019 BSOD - identifying an offending driver


    Hello,


    I know Windows 10 and 2019 are fairly similar, so I'm hoping it's okay to post this question here.

    I recently had a server BSOD on me, and was trying to determine which vendor's driver was at fault.
    From WinDbg, I have the following two lines:

    FAILURE_ID_HASH_STRING: km:0x1e_c0000094_stackptr_error_disk!diskdevicecontrol

    FAULTING_IP: CLASSPNP!DeviceProcessDsmTrimRequest+88


    So it's likely in the Windows disk subsystem, and the source of the error may be SSD/trim related. Any thoughts on which vendor I should be talking to at this point?


    Thank you,


    - Daniel


    The full output from the WinDbg analysis follows:






    Microsoft R Windows Debugger Version 10.0.18362.1 AMD64

    Copyright c Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Windows\MEMORY.DMP]

    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.





    ************* Path validation summary **************

    Response Time ms Location

    Deferred srv*c:\Symbols*http://msdl.microsoft.com/download/symbols

    Symbol search path is: srv*c:\Symbols*http://msdl.microsoft.com/download/symbols

    Executable search path is:

    Windows 10 Kernel Version 17763 MP 16 procs Free x64

    Product: Server, suite: TerminalServer DataCenter SingleUserTS

    Built by: 17763.1.amd64fre.rs5_release.180914-1434

    Machine Name:

    Kernel base = 0xfffff801`796ba000 PsLoadedModuleList = 0xfffff801`79ad46d0

    Debug session time: Wed Apr 8 21:42:35.717 2020 UTC - 6:00

    System Uptime: 19 days 11:01:25.531

    Loading Kernel Symbols

    .......................................Page 2005f39d1 too large to be in the dump file.

    Page 2005f39d0 too large to be in the dump file.

    ........................

    ................................................................

    .....................................................

    Loading User Symbols



    Loading unloaded module list

    ......................

    For analysis of this file, run !analyze -v

    6: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    KMODE_EXCEPTION_NOT_HANDLED 1e

    This is a very common bugcheck. Usually the exception address pinpoints

    the driver/function that caused the problem. Always note this address

    as well as the link date of the driver/image that contains this address.

    Arguments:

    Arg1: ffffffffc0000094, The exception code that was not handled

    Arg2: fffff8018bcfbc84, The address that the exception occurred at

    Arg3: 0000000000000001, Parameter 0 of the exception

    Arg4: 0000000000000000, Parameter 1 of the exception



    Debugging Details:

    ------------------





    KEY_VALUES_STRING: 1





    PROCESSES_ANALYSIS: 1



    SERVICE_ANALYSIS: 1



    STACKHASH_ANALYSIS: 1



    TIMELINE_ANALYSIS: 1





    DUMP_CLASS: 1



    DUMP_QUALIFIER: 401



    BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434



    SYSTEM_MANUFACTURER: Dell Inc.



    SYSTEM_PRODUCT_NAME: PowerEdge R640



    SYSTEM_SKU: SKU=NotProvided;ModelName=PowerEdge R640



    BIOS_VENDOR: Dell Inc.



    BIOS_VERSION: 2.4.8



    BIOS_DATE: 11/26/2019



    BASEBOARD_MANUFACTURER: Dell Inc.



    BASEBOARD_PRODUCT: 0HG0J8



    BASEBOARD_VERSION: A01



    DUMP_TYPE: 1



    BUGCHECK_P1: ffffffffc0000094



    BUGCHECK_P2: fffff8018bcfbc84



    BUGCHECK_P3: 1



    BUGCHECK_P4: 0



    EXCEPTION_CODE: NTSTATUS 0xc0000094 - {EXCEPTION} Integer division by zero.



    FAULTING_IP:

    CLASSPNP!DeviceProcessDsmTrimRequest+88

    fffff801`8bcfbc84 49f7f2 div rax,r10



    EXCEPTION_PARAMETER1: 0000000000000001



    BUGCHECK_STR: 0x1E_c0000094



    CPU_COUNT: 10



    CPU_MHZ: 82f



    CPU_VENDOR: GenuineIntel



    CPU_FAMILY: 6



    CPU_MODEL: 55



    CPU_STEPPING: 4



    CPU_MICROCODE: 6,55,4,0 F,M,S,R SIG: 2000065'00000000 cache 2000065'00000000 init



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXPNP: 1 !blackboxpnp





    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



    PROCESS_NAME: System



    CURRENT_IRQL: 0



    ANALYSIS_SESSION_HOST: CVSVR7



    ANALYSIS_SESSION_TIME: 04-09-2020 07:33:30.0055



    ANALYSIS_VERSION: 10.0.18362.1 amd64fre



    EXCEPTION_RECORD: ffffa58fa64ec5f2 -- .exr 0xffffa58fa64ec5f2

    ExceptionAddress: 2d333737342d3634

    ExceptionCode: 00302e34

    ExceptionFlags: 34653900

    NumberParameters: 892352568

    Parameter[0]: 6265613265623866

    Parameter[1]: 0000000000000066

    Parameter[2]: 0000000000000000

    Parameter[3]: 0000000000000000

    Parameter[4]: 0000000000000000

    Parameter[5]: 0000000000000000

    Parameter[6]: 0000000000000000

    Parameter[7]: 0000000000000000

    Parameter[8]: 0000000000000000

    Parameter[9]: 0000000000000000

    Parameter[10]: 0000000000000000

    Parameter[11]: 0000000000000000

    Parameter[12]: 0000000000000000

    Parameter[13]: 0000000000000000

    Parameter[14]: 0000000000000000



    TRAP_FRAME: ffffa58fa64ec5f7 -- .trap 0xffffa58fa64ec5f7

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    Unable to get program counter

    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000

    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

    rip=ffa58fa5460620ff rsp=ffa58fad1340a0ff rbp=ffa58fa64ecc30e1

    r8=0000000000000000 r9=0000000000000000 r10=0000000000000000

    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=3 vif nv up di pl nz na pe nc

    00ff:20ff ?? ???

    Resetting default scope



    BAD_STACK_POINTER: ffa58fad1340a0ff



    IP_IN_FREE_BLOCK: 0



    UNALIGNED_STACK_POINTER: ffa58fad1340a0ff



    LAST_CONTROL_TRANSFER: from fffff801798b05dd to fffff80179871a90



    STACK_TEXT:

    ffffa28b`135a6af8 fffff801`798b05dd : 00000000`0000001e ffffffff`c0000094 fffff801`8bcfbc84 00000000`00000001 : nt!KeBugCheckEx

    ffffa28b`135a6b00 fffff801`798833c2 : ffffa58f`a64ec5f2 00000000`00000004 ffffa58f`a64ec5f7 00000000`00000025 : nt!KiDispatchException+0x19708d

    ffffa28b`135a71b0 fffff801`7987c3f5 : ffffa28b`00000006 00000000`002d9404 fffff801`8bd35000 ffffa58f`b3d70490 : nt!KiExceptionDispatch+0xc2

    ffffa28b`135a7390 fffff801`8bcfbc84 : 00000000`000000ff ffffa58f`00000080 00000000`00000000 00000000`00000000 : nt!KiDivideErrorFault+0x2f5

    ffffa28b`135a7520 fffff801`8bcf281e : 00000000`00000000 ffffa58f`ad1340a0 00000000`00000000 00000000`00000000 : CLASSPNP!DeviceProcessDsmTrimRequest+0x88

    ffffa28b`135a7670 fffff801`8bcf54b9 : 00000000`002d9404 00000000`00000000 ffffa58f`f56cfbe0 00000000`39436353 : CLASSPNP!ClasspDeviceTrimProcess+0x286

    ffffa28b`135a77a0 fffff801`8bcd17fb : ffffa58f`b3d70000 00000000`00000480 00000000`002d9404 fffff801`798f3835 : CLASSPNP!ClassDeviceControl+0x619

    ffffa28b`135a7910 fffff801`8bcf8532 : ffffa581`03576f50 ffffa58f`a64f47b0 ffffa58f`ad1341f0 00000000`00000001 : disk!DiskDeviceControl+0x8b

    ffffa28b`135a79a0 fffff801`8bcf1404 : ffffa58f`a53b90a0 ffffa58f`ad1340a0 ffffa58f`f56cfbe0 ffffa58f`00000006 : CLASSPNP!ClassDeviceControlDispatch+0x82

    ffffa28b`135a7a40 fffff801`797c33c9 : 00000000`00000080 ffffe401`3ec98000 00000000`00000000 00000000`00000000 : CLASSPNP!ClassGlobalDispatch+0x24

    ffffa28b`135a7a70 fffff80f`5bdbc6f2 : 00000000`00000000 00000000`00000001 00000000`00000000 fffff801`797cb48b : nt!IofCallDriver+0x59

    ffffa28b`135a7ab0 fffff80f`5bda3cde : ffffa58f`f56cfb00 00000000`00000000 00000000`00000000 ffffa58f`f56cfbe0 : partmgr!PmIoctlRedirect+0x4e

    ffffa28b`135a7b20 fffff80f`5bda1f21 : ffffa58f`fc45fb20 ffffa58f`ac5de200 ffffa58f`b3d704c0 00000000`00000000 : partmgr!PmFilterDeviceControl+0x31e

    ffffa28b`135a7b70 fffff801`797c33c9 : ffffa58f`fc45fb20 fffff801`797efc54 00000000`00000000 ffffa58f`00000001 : partmgr!PmGlobalDispatch+0x21

    ffffa28b`135a7ba0 fffff80f`5bdbca35 : ffffa58f`fc45fb10 ffffa58f`ac5de200 ffffa58f`b3d704c0 00000000`00000000 : nt!IofCallDriver+0x59

    ffffa28b`135a7be0 fffff80f`5bda2a95 : ffffa58f`b3d704f0 00000000`00000000 ffffa28b`135a7d70 00000000`00000000 : partmgr!PartitionIoctlDsm+0x2c9

    ffffa28b`135a7c60 fffff80f`5bda2937 : 00000000`00000000 ffffa581`03576ec0 00000000`00000004 ffffa28b`14c36478 : partmgr!PmPartitionDeviceControl+0x145

    ffffa28b`135a7c90 fffff80f`5bda1f21 : ffffa58f`a4c425c0 fffff80f`5bda189e 00000000`00001000 ffffa581`03576e30 : partmgr!PmLegacyDeviceControl+0x27

    ffffa28b`135a7cc0 fffff801`797c33c9 : 00000000`00000000 ffffa58f`a4c425c0 00000000`00000000 fffff780`00000008 : partmgr!PmGlobalDispatch+0x21

    ffffa28b`135a7cf0 fffff80f`5be8128c : ffffa58f`a4c425c0 ffffa28b`135a7d70 00000000`00000000 ffffa58f`b7b74660 : nt!IofCallDriver+0x59

    ffffa28b`135a7d30 fffff801`797c33c9 : ffffa58f`f56cfbe0 00000000`00000000 ffffa58f`bb46e180 ffffa58f`bb46e180 : volmgr!VmDeviceControl+0x27c

    ffffa28b`135a7da0 fffff801`8bc0102e : 00000000`00000000 fffff801`8bc0102e 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x59

    ffffa28b`135a7de0 fffff801`797c33c9 : 00000000`00000000 fffff801`797c33c9 00000000`00000000 00000000`00000000 : volume!VolumePassThrough+0x1e

    ffffa28b`135a7e10 fffff801`8bc2cd77 : 00000000`00000000 fffff801`8bc114e4 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x59

    ffffa28b`135a7e50 fffff801`797c33c9 : 00000000`00000000 00000000`00000000 ffffa58f`e3cb8040 00000000`00000000 : volsnap!VolSnapDeviceControl+0xc7

    ffffa28b`135a7f10 fffff80f`5c2f02c7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x59

    ffffa28b`135a7f50 fffff801`7987526e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsStorageDriverCallout+0x17

    ffffa28b`135a7f80 fffff801`7987522c : 00000000`00006000 00000000`00000000 ffffa58f`e3cb8040 fffff801`79784df6 : nt!KxSwitchKernelStackCallout+0x2e

    ffffa28b`1404f100 fffff801`79784df6 : 00000000`00000012 00000000`00000012 ffffa58f`00000000 ffffa58f`00000000 : nt!KiSwitchKernelStackContinue

    ffffa28b`1404f120 fffff801`79784b3c : fffff80f`5c2f02b0 ffffa28b`1404f300 00000000`00000000 fffff801`00000000 : nt!KiExpandKernelStackAndCalloutOnStackSegment+0x256

    ffffa28b`1404f1b0 fffff801`797849b3 : ffffa58f`aa76b180 ffffa58f`bb46e030 00000000`00000002 00001f80`00000000 : nt!KiExpandKernelStackAndCalloutSwitchStack+0xdc

    ffffa28b`1404f220 fffff801`7978496d : fffff80f`5c2f02b0 ffffa28b`1404f300 ffffa58f`f56cfbe0 00000000`00000004 : nt!KeExpandKernelStackAndCalloutInternal+0x33

    ffffa28b`1404f290 fffff80f`5c2dd363 : ffffa58f`f56cfef0 ffffa58f`fc45faf0 00000000`00000030 ffffa28b`1404f380 : nt!KeExpandKernelStackAndCalloutEx+0x1d

    ffffa28b`1404f2d0 fffff80f`5c3a849d : ffffa28b`00000306 00000f4a`8c47f9f3 ffffa58f`ad7adda0 fffff80f`5c2f3c6e : Ntfs!NtfsCallStorageDriver+0x47

    ffffa28b`1404f340 fffff80f`5c2dcffe : 00000f4a`8c47f9f3 ffffa28b`1404f449 ffffa58f`aa76b180 ffffa58f`ad7adda0 : Ntfs!NtfsDeviceIoControlAsync3+0xad

    ffffa28b`1404f3a0 fffff801`797c115a : ffffa58f`928a2450 ffffa58f`e3cb8040 ffffa58f`aa76b860 ffffa58f`928a2450 : Ntfs!NtfsMarkUnusedContextPreTrimWorkItemProcessing+0x2ee

    ffffa28b`1404f4b0 fffff801`797333a5 : ffffa58f`e3cb8040 ffffa58f`92897300 ffffa58f`e3cb8040 b78d92d9`1f01ff62 : nt!ExpWorkerThread+0x16a

    ffffa28b`1404f550 fffff801`79878f0c : ffffe401`3f2c0180 ffffa58f`e3cb8040 fffff801`79733350 0000001e`004ed789 : nt!PspSystemThreadStartup+0x55

    ffffa28b`1404f5a0 00000000`00000000 : ffffa28b`14050000 ffffa28b`14049000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c





    THREAD_SHA1_HASH_MOD_FUNC: 2b8ed5d6387beb7521594d7d3d699f77dbb7662f



    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 9ba0efef6deb463cd07f6ef4ebd15bc2dcb11d6a



    THREAD_SHA1_HASH_MOD: 55a9899141249d4d9a4f29448e278627a88ed842



    FOLLOWUP_IP:

    disk!DiskDeviceControl+8b

    fffff801`8bcd17fb 0f1f440000 nop dword ptr [rax+rax]



    FAULT_INSTR_CODE: 441f0f



    SYMBOL_STACK_INDEX: 7



    SYMBOL_NAME: disk!DiskDeviceControl+8b



    FOLLOWUP_NAME: MachineOwner



    MODULE_NAME: disk



    IMAGE_NAME: disk.sys



    DEBUG_FLR_IMAGE_TIMESTAMP: 0



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 8b



    FAILURE_BUCKET_ID: 0x1E_c0000094_STACKPTR_ERROR_disk!DiskDeviceControl



    BUCKET_ID: 0x1E_c0000094_STACKPTR_ERROR_disk!DiskDeviceControl



    PRIMARY_PROBLEM_CLASS: 0x1E_c0000094_STACKPTR_ERROR_disk!DiskDeviceControl



    TARGET_TIME: 2020-04-09T03:42:35.000Z



    OSBUILD: 17763



    OSSERVICEPACK: 0



    SERVICEPACK_NUMBER: 0



    OS_REVISION: 0



    SUITE_MASK: 400



    PRODUCT_TYPE: 3



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    OSEDITION: Windows 10 Server TerminalServer DataCenter SingleUserTS



    OS_LOCALE:



    USER_LCID: 0



    OSBUILD_TIMESTAMP: unknown_date



    BUILDDATESTAMP_STR: 180914-1434



    BUILDLAB_STR: rs5_release



    BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434



    ANALYSIS_SESSION_ELAPSED_TIME: 4dc0



    ANALYSIS_SOURCE: KM



    FAILURE_ID_HASH_STRING: km:0x1e_c0000094_stackptr_error_disk!diskdevicecontrol



    FAILURE_ID_HASH: {bbb78e64-dd2a-6a0d-fe43-a16b66b133cd}



    Followup: MachineOwner

    ---------

    :)
     
    DanielCOMESA, Apr 9, 2020
    #1
  2. BRIAN TILLMAN [OUTLOOK MVP 2007-2019] ON DIRECTLY
    Brian Tillman [Outlook MVP 2007-2019] on Directly Win User
    Brian Tillman [Outlook MVP 2007-2019] on Directly, Apr 10, 2020
    #2
  3. AHHZZ
    Ahhzz Win User
    Office 2019

    Only supported on Win10. Sorry, 8.1 users, only 4 years old, gotta go.

    Microsoft Office 2019 will only work on Windows 10

    https://blogs.technet.microsoft.com...-to-office-and-windows-servicing-and-support/

    Spoiler Office 2019
    Last year at Ignite, we announced Office 2019 – the next perpetual version of Office that includes apps (including Word, Excel, PowerPoint, and Outlook, and Skype for Business) and servers (including Exchange, SharePoint, and Skype for Business). Today we’re pleased to share the following updates:

    • Office 2019 will ship in H2 of 2018. Previews of the new apps and servers will start shipping in the second quarter of 2018.
    • Office 2019 apps will be supported on:
      • Any supported Windows 10 SAC release
      • Windows 10 Enterprise LTSC 2018
      • The next LTSC release of Windows Server
    • The Office 2019 client apps will be released with Click-to-Run installation technology only. We will not provide MSI as a deployment methodology for Office 2019 clients. We will continue to provide MSI for Office Server products.
     
    Ahhzz, Apr 10, 2020
    #3
  4. DANIELCOMESA
    DanielCOMESA Win User

    Windows Server 2019 BSOD - identifying an offending driver

    Windows Server 2019 BSOD - identifying an offending driver

    Hello,

    I know Windows 10 and 2019 are fairly similar, so I'm hoping it's okay to post this question here.

    I recently had a server BSOD on me, and was trying to determine which vendor's driver was at fault.

    From WinDbg, I have the following two lines:

    FAILURE_ID_HASH_STRING: km:0x1e_c0000094_stackptr_error_disk!diskdevicecontrol

    FAULTING_IP: CLASSPNP!DeviceProcessDsmTrimRequest+88

    So it's likely in the Windows disk subsystem, and the source of the error may be SSD/trim related. Any thoughts on which vendor I should be talking to at this point?

    Thank you,

    - Daniel

    The full output from the WinDbg analysis follows:

    Code:
     

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

************* Path validation summary **************Response                         Time (ms)     LocationDeferred                                       srv*c:\Symbols*http://msdl.microsoft.com/download/symbolsSymbol search path is: srv*c:\Symbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows 10 Kernel Version 17763 MP (16 procs) Free x64Product: Server, suite: TerminalServer DataCenter SingleUserTSBuilt by: 17763.1.amd64fre.rs5_release.180914-1434Machine Name:Kernel base = 0xfffff801`796ba000 PsLoadedModuleList = 0xfffff801`79ad46d0Debug session time: Wed Apr  8 21:42:35.717 2020 (UTC - 6:00)System Uptime: 19 days 11:01:25.531Loading Kernel Symbols.......................................Page 2005f39d1 too large to be in the dump file.Page 2005f39d0 too large to be in the dump file..............................................................................................................................................Loading User Symbols

Loading unloaded module list......................For analysis of this file, run !analyze -v6: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)This is a very common bugcheck.  Usually the exception address pinpointsthe driver/function that caused the problem.  Always note this addressas well as the link date of the driver/image that contains this address.Arguments:Arg1: ffffffffc0000094, The exception code that was not handledArg2: fffff8018bcfbc84, The address that the exception occurred atArg3: 0000000000000001, Parameter 0 of the exceptionArg4: 0000000000000000, Parameter 1 of the exception

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

KEY_VALUES_STRING: 1

PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER:  Dell Inc.

SYSTEM_PRODUCT_NAME:  PowerEdge R640

SYSTEM_SKU:  SKU=NotProvided;ModelName=PowerEdge R640

BIOS_VENDOR:  Dell Inc.

BIOS_VERSION:  2.4.8

BIOS_DATE:  11/26/2019

BASEBOARD_MANUFACTURER:  Dell Inc.

BASEBOARD_PRODUCT:  0HG0J8

BASEBOARD_VERSION:  A01

DUMP_TYPE:  1

BUGCHECK_P1: ffffffffc0000094

BUGCHECK_P2: fffff8018bcfbc84

BUGCHECK_P3: 1

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

FAULTING_IP: CLASSPNP!DeviceProcessDsmTrimRequest+88fffff801`8bcfbc84 49f7f2          div     rax,r10

EXCEPTION_PARAMETER1:  0000000000000001

BUGCHECK_STR:  0x1E_c0000094

CPU_COUNT: 10

CPU_MHZ: 82f

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 55

CPU_STEPPING: 4

CPU_MICROCODE: 6,55,4,0 (F,M,S,R)  SIG: 2000065'00000000 (cache) 2000065'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXPNP: 1 (!blackboxpnp)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  CVSVR7

ANALYSIS_SESSION_TIME:  04-09-2020 07:33:30.0055

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

EXCEPTION_RECORD:  ffffa58fa64ec5f2 -- (.exr 0xffffa58fa64ec5f2)ExceptionAddress: 2d333737342d3634   ExceptionCode: 00302e34  ExceptionFlags: 34653900NumberParameters: 892352568   Parameter[0]: 6265613265623866   Parameter[1]: 0000000000000066   Parameter[2]: 0000000000000000   Parameter[3]: 0000000000000000   Parameter[4]: 0000000000000000   Parameter[5]: 0000000000000000   Parameter[6]: 0000000000000000   Parameter[7]: 0000000000000000   Parameter[8]: 0000000000000000   Parameter[9]: 0000000000000000   Parameter[10]: 0000000000000000   Parameter[11]: 0000000000000000   Parameter[12]: 0000000000000000   Parameter[13]: 0000000000000000   Parameter[14]: 0000000000000000

TRAP_FRAME:  ffffa58fa64ec5f7 -- (.trap 0xffffa58fa64ec5f7)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.Unable to get program counterrax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000rip=ffa58fa5460620ff rsp=ffa58fad1340a0ff rbp=ffa58fa64ecc30e1 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000r11=0000000000000000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=3     vif nv up di pl nz na pe nc00ff:20ff ??              ???Resetting default scope

BAD_STACK_POINTER:  ffa58fad1340a0ff

IP_IN_FREE_BLOCK: 0

UNALIGNED_STACK_POINTER:  ffa58fad1340a0ff

LAST_CONTROL_TRANSFER:  from fffff801798b05dd to fffff80179871a90

STACK_TEXT:  ffffa28b`135a6af8 fffff801`798b05dd : 00000000`0000001e ffffffff`c0000094 fffff801`8bcfbc84 00000000`00000001 : nt!KeBugCheckExffffa28b`135a6b00 fffff801`798833c2 : ffffa58f`a64ec5f2 00000000`00000004 ffffa58f`a64ec5f7 00000000`00000025 : nt!KiDispatchException+0x19708dffffa28b`135a71b0 fffff801`7987c3f5 : ffffa28b`00000006 00000000`002d9404 fffff801`8bd35000 ffffa58f`b3d70490 : nt!KiExceptionDispatch+0xc2ffffa28b`135a7390 fffff801`8bcfbc84 : 00000000`000000ff ffffa58f`00000080 00000000`00000000 00000000`00000000 : nt!KiDivideErrorFault+0x2f5ffffa28b`135a7520 fffff801`8bcf281e : 00000000`00000000 ffffa58f`ad1340a0 00000000`00000000 00000000`00000000 : CLASSPNP!DeviceProcessDsmTrimRequest+0x88ffffa28b`135a7670 fffff801`8bcf54b9 : 00000000`002d9404 00000000`00000000 ffffa58f`f56cfbe0 00000000`39436353 : CLASSPNP!ClasspDeviceTrimProcess+0x286ffffa28b`135a77a0 fffff801`8bcd17fb : ffffa58f`b3d70000 00000000`00000480 00000000`002d9404 fffff801`798f3835 : CLASSPNP!ClassDeviceControl+0x619ffffa28b`135a7910 fffff801`8bcf8532 : ffffa581`03576f50 ffffa58f`a64f47b0 ffffa58f`ad1341f0 00000000`00000001 : disk!DiskDeviceControl+0x8bffffa28b`135a79a0 fffff801`8bcf1404 : ffffa58f`a53b90a0 ffffa58f`ad1340a0 ffffa58f`f56cfbe0 ffffa58f`00000006 : CLASSPNP!ClassDeviceControlDispatch+0x82ffffa28b`135a7a40 fffff801`797c33c9 : 00000000`00000080 ffffe401`3ec98000 00000000`00000000 00000000`00000000 : CLASSPNP!ClassGlobalDispatch+0x24ffffa28b`135a7a70 fffff80f`5bdbc6f2 : 00000000`00000000 00000000`00000001 00000000`00000000 fffff801`797cb48b : nt!IofCallDriver+0x59ffffa28b`135a7ab0 fffff80f`5bda3cde : ffffa58f`f56cfb00 00000000`00000000 00000000`00000000 ffffa58f`f56cfbe0 : partmgr!PmIoctlRedirect+0x4effffa28b`135a7b20 fffff80f`5bda1f21 : ffffa58f`fc45fb20 ffffa58f`ac5de200 ffffa58f`b3d704c0 00000000`00000000 : partmgr!PmFilterDeviceControl+0x31effffa28b`135a7b70 fffff801`797c33c9 : ffffa58f`fc45fb20 fffff801`797efc54 00000000`00000000 ffffa58f`00000001 : partmgr!PmGlobalDispatch+0x21ffffa28b`135a7ba0 fffff80f`5bdbca35 : ffffa58f`fc45fb10 ffffa58f`ac5de200 ffffa58f`b3d704c0 00000000`00000000 : nt!IofCallDriver+0x59ffffa28b`135a7be0 fffff80f`5bda2a95 : ffffa58f`b3d704f0 00000000`00000000 ffffa28b`135a7d70 00000000`00000000 : partmgr!PartitionIoctlDsm+0x2c9ffffa28b`135a7c60 fffff80f`5bda2937 : 00000000`00000000 ffffa581`03576ec0 00000000`00000004 ffffa28b`14c36478 : partmgr!PmPartitionDeviceControl+0x145ffffa28b`135a7c90 fffff80f`5bda1f21 : ffffa58f`a4c425c0 fffff80f`5bda189e 00000000`00001000 ffffa581`03576e30 : partmgr!PmLegacyDeviceControl+0x27ffffa28b`135a7cc0 fffff801`797c33c9 : 00000000`00000000 ffffa58f`a4c425c0 00000000`00000000 fffff780`00000008 : partmgr!PmGlobalDispatch+0x21ffffa28b`135a7cf0 fffff80f`5be8128c : ffffa58f`a4c425c0 ffffa28b`135a7d70 00000000`00000000 ffffa58f`b7b74660 : nt!IofCallDriver+0x59ffffa28b`135a7d30 fffff801`797c33c9 : ffffa58f`f56cfbe0 00000000`00000000 ffffa58f`bb46e180 ffffa58f`bb46e180 : volmgr!VmDeviceControl+0x27cffffa28b`135a7da0 fffff801`8bc0102e : 00000000`00000000 fffff801`8bc0102e 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x59ffffa28b`135a7de0 fffff801`797c33c9 : 00000000`00000000 fffff801`797c33c9 00000000`00000000 00000000`00000000 : volume!VolumePassThrough+0x1effffa28b`135a7e10 fffff801`8bc2cd77 : 00000000`00000000 fffff801`8bc114e4 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x59ffffa28b`135a7e50 fffff801`797c33c9 : 00000000`00000000 00000000`00000000 ffffa58f`e3cb8040 00000000`00000000 : volsnap!VolSnapDeviceControl+0xc7ffffa28b`135a7f10 fffff80f`5c2f02c7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x59ffffa28b`135a7f50 fffff801`7987526e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsStorageDriverCallout+0x17ffffa28b`135a7f80 fffff801`7987522c : 00000000`00006000 00000000`00000000 ffffa58f`e3cb8040 fffff801`79784df6 : nt!KxSwitchKernelStackCallout+0x2effffa28b`1404f100 fffff801`79784df6 : 00000000`00000012 00000000`00000012 ffffa58f`00000000 ffffa58f`00000000 : nt!KiSwitchKernelStackContinueffffa28b`1404f120 fffff801`79784b3c : fffff80f`5c2f02b0 ffffa28b`1404f300 00000000`00000000 fffff801`00000000 : nt!KiExpandKernelStackAndCalloutOnStackSegment+0x256ffffa28b`1404f1b0 fffff801`797849b3 : ffffa58f`aa76b180 ffffa58f`bb46e030 00000000`00000002 00001f80`00000000 : nt!KiExpandKernelStackAndCalloutSwitchStack+0xdcffffa28b`1404f220 fffff801`7978496d : fffff80f`5c2f02b0 ffffa28b`1404f300 ffffa58f`f56cfbe0 00000000`00000004 : nt!KeExpandKernelStackAndCalloutInternal+0x33ffffa28b`1404f290 fffff80f`5c2dd363 : ffffa58f`f56cfef0 ffffa58f`fc45faf0 00000000`00000030 ffffa28b`1404f380 : nt!KeExpandKernelStackAndCalloutEx+0x1dffffa28b`1404f2d0 fffff80f`5c3a849d : ffffa28b`00000306 00000f4a`8c47f9f3 ffffa58f`ad7adda0 fffff80f`5c2f3c6e : Ntfs!NtfsCallStorageDriver+0x47ffffa28b`1404f340 fffff80f`5c2dcffe : 00000f4a`8c47f9f3 ffffa28b`1404f449 ffffa58f`aa76b180 ffffa58f`ad7adda0 : Ntfs!NtfsDeviceIoControlAsync3+0xadffffa28b`1404f3a0 fffff801`797c115a : ffffa58f`928a2450 ffffa58f`e3cb8040 ffffa58f`aa76b860 ffffa58f`928a2450 : Ntfs!NtfsMarkUnusedContextPreTrimWorkItemProcessing+0x2eeffffa28b`1404f4b0 fffff801`797333a5 : ffffa58f`e3cb8040 ffffa58f`92897300 ffffa58f`e3cb8040 b78d92d9`1f01ff62 : nt!ExpWorkerThread+0x16affffa28b`1404f550 fffff801`79878f0c : ffffe401`3f2c0180 ffffa58f`e3cb8040 fffff801`79733350 0000001e`004ed789 : nt!PspSystemThreadStartup+0x55ffffa28b`1404f5a0 00000000`00000000 : ffffa28b`14050000 ffffa28b`14049000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c

THREAD_SHA1_HASH_MOD_FUNC:  2b8ed5d6387beb7521594d7d3d699f77dbb7662f

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  9ba0efef6deb463cd07f6ef4ebd15bc2dcb11d6a

THREAD_SHA1_HASH_MOD:  55a9899141249d4d9a4f29448e278627a88ed842

FOLLOWUP_IP: disk!DiskDeviceControl+8bfffff801`8bcd17fb 0f1f440000      nop     dword ptr [rax+rax]

FAULT_INSTR_CODE:  441f0f

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  disk!DiskDeviceControl+8b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: disk

IMAGE_NAME:  disk.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  8b

FAILURE_BUCKET_ID:  0x1E_c0000094_STACKPTR_ERROR_disk!DiskDeviceControl

BUCKET_ID:  0x1E_c0000094_STACKPTR_ERROR_disk!DiskDeviceControl

PRIMARY_PROBLEM_CLASS:  0x1E_c0000094_STACKPTR_ERROR_disk!DiskDeviceControl

TARGET_TIME:  2020-04-09T03:42:35.000Z

OSBUILD:  17763

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  400

PRODUCT_TYPE:  3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 Server TerminalServer DataCenter SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  180914-1434

BUILDLAB_STR:  rs5_release

BUILDOSVER_STR:  10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME:  4dc0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1e_c0000094_stackptr_error_disk!diskdevicecontrol

FAILURE_ID_HASH:  {bbb78e64-dd2a-6a0d-fe43-a16b66b133cd}

Followup:     MachineOwner---------
     
    DanielCOMESA, Apr 10, 2020
    #4
Thema:

Windows Server 2019 BSOD - identifying an offending driver

Loading...

  1. Windows Server 2019 BSOD - identifying an offending driver - Similar Threads - Server 2019 BSOD

  2. Identify driver causing BSOD

    in Windows 10 Gaming
    Identify driver causing BSOD: I receive a bluescreen on reboot, it occurs twice and then when I go to the troubleshooter and select normal reboot, it starts fine. I have run windbg on the .dmp file and it appears to be a driver issue, but I cannot identify which one. Can I upload the .dmp file to be...

  3. Identify driver causing BSOD

    in Windows 10 Software and Apps
    Identify driver causing BSOD: I receive a bluescreen on reboot, it occurs twice and then when I go to the troubleshooter and select normal reboot, it starts fine. I have run windbg on the .dmp file and it appears to be a driver issue, but I cannot identify which one. Can I upload the .dmp file to be...

  4. RNDIS driver update with Windows server 2019

    in Windows 10 Gaming
    RNDIS driver update with Windows server 2019: Hi I have checked the windows server 2019 update history. Only Intel system for driver update. Does any driver updates on Windows server 2019 OS for RNDIS driver recently? Thanks...

  5. RNDIS driver update with Windows server 2019

    in Windows 10 Software and Apps
    RNDIS driver update with Windows server 2019: Hi I have checked the windows server 2019 update history. Only Intel system for driver update. Does any driver updates on Windows server 2019 OS for RNDIS driver recently? Thanks...

  6. Problems with Game, BSOD, Driver Identifier, DUMPS, Memtest? ; Identifying broken driver...

    in Windows 10 Drivers and Hardware
    Problems with Game, BSOD, Driver Identifier, DUMPS, Memtest? ; Identifying broken driver...: Hello there people, as seen in the Subject, it is a very complicated one and I will split it up in the parts I have in the subject. Link to the dump files so you can read while downloading: https://workupload.com/archive/msqLSVcQ password is dumpydump as I didn't want anybody...

  7. Windows 10 / Server 2019 winquic.sys BSOD

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 / Server 2019 winquic.sys BSOD: Hey guys, Posting an answer more so than a question, was following "https://answers.microsoft.com/en-us/windows/forum/all/bsod-0x7e-after-updating-windows-server-2019/137fa419-3dbf-4802-ba32-28a491dd9caa" and after months of working and looking for a solution we ended up...

  8. Identifying driver causing BSOD

    in Windows 10 BSOD Crashes and Debugging
    Identifying driver causing BSOD: My laptop suddenly went into BSOD with the error IRQL_NOTLESS_OR_EQUAL. I tried using a bsod viewer to identify the driver but it just states ntoskrnl.exe. I have the dump files available, will it be helpful in identifying the driver that is causing this issue?...

  9. Windows Server 2019

    in Windows 10 BSOD Crashes and Debugging
    Windows Server 2019: Hello, I have a question to the new Windows Server 2019. Is it possible to divide a windows host server for performance sharing? With multiple users working on it at the same time. As an example, that multiple users can play simultaneously on this server? Thus, only the...

  10. Figure out the offending driver

    in Windows 10 Drivers and Hardware
    Figure out the offending driver: On the ASRock machine in my specs, using Acronis True Image 2018, I get the following BSOD error when trying to back to one of the M.2 SSDs. Backing up to a traditional SATA 2.5" SSD works fine. "Driver IRQL not less or equal" Someone on the Acronis site, suggested I figure...