locked
Bugcheck 0x00000050 RRS feed

  • Question

  • Can someone take a look at this dump file and see what happen?

    Thanks in advance!

    https://andersonrasorpartners.sharefile.com/d-s3084e2b735e472eb

    Tuesday, March 15, 2016 8:46 PM

Answers

  • The error seems to be graphics related referencing the dxgmms1.sys :

    BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_DEVICE::RemoveCommitment+31

    Try updating the Intel graphics driver - HP seems to have a more recent driver:

    http://h20564.www2.hp.com/hpsc/swd/public/detail?swItemId=vc_155560_1


    Tuesday, March 15, 2016 11:21 PM
  • Hi SHesser,

     

    I agree with auggy, it is probably caused by dxmms1.sys.

    Please refer to auggy’s suggestion to have a test.

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff8d002666e50, 1, fffff880045ba559, 5}
    
    
    Could not read faulting driver name
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DEVICE::RemoveCommitment+31 )
    
    Followup:     MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except.
    Typically the address is just plain bad or it is pointing at freed memory.
    Arguments:
    Arg1: fffff8d002666e50, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff880045ba559, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000005, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  7601.19160.amd64fre.win7sp1_gdr.160211-0600
    
    SYSTEM_MANUFACTURER:  Hewlett-Packard
    
    SYSTEM_PRODUCT_NAME:  HP Compaq Pro 6300 SFF
    
    SYSTEM_SKU:  B5N04UT#ABA
    
    BIOS_VENDOR:  Hewlett-Packard
    
    BIOS_VERSION:  K01 v02.99
    
    BIOS_DATE:  09/15/2015
    
    BASEBOARD_MANUFACTURER:  Hewlett-Packard
    
    BASEBOARD_PRODUCT:  339A
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: fffff8d002666e50
    
    BUGCHECK_P2: 1
    
    BUGCHECK_P3: fffff880045ba559
    
    BUGCHECK_P4: 5
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034b3100
    Unable to get MmSystemRangeStart
     fffff8d002666e50 
    
    FAULTING_IP: 
    dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
    fffff880`045ba559 ff0b            dec     dword ptr [rbx]
    
    MM_INTERNAL_CODE:  5
    
    CPU_COUNT: 4
    
    CPU_MHZ: cdc
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 2a
    
    CPU_STEPPING: 7
    
    CPU_MICROCODE: 6,2a,7,0 (F,M,S,R)  SIG: 28'00000000 (cache) 28'00000000 (init)
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_SESSION_HOST:  V-JINX086636VM
    
    ANALYSIS_SESSION_TIME:  03-16-2016 14:45:42.0369
    
    ANALYSIS_VERSION: 10.0.10586.567 amd64fre
    
    TRAP_FRAME:  fffff88002e98590 -- (.trap 0xfffff88002e98590)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000ffff0000 rbx=0000000000000000 rcx=fffff8a002992cd0
    rdx=fffffa8003f07dc0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880045ba559 rsp=fffff88002e98728 rbp=0000000000000000
     r8=fffffa8003f07d70  r9=fffff8a002992cd0 r10=fffff8a005348830
    r11=fffff8a0053878e0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x31:
    fffff880`045ba559 ff0b            dec     dword ptr [rbx] ds:00000000`00000000=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800032f0c4a to fffff80003276080
    
    STACK_TEXT:  
    fffff880`02e98428 fffff800`032f0c4a : 00000000`00000050 fffff8d0`02666e50 00000000`00000001 fffff880`02e98590 : nt!KeBugCheckEx
    fffff880`02e98430 fffff800`032741ae : 00000000`00000001 fffff8d0`02666e50 00000000`00000000 fffff8d0`02666e50 : nt! ?? ::FNODOBFM::`string'+0x3fe51
    fffff880`02e98590 fffff880`045ba559 : fffff880`045b36f8 fffffa80`05c7d000 fffff8a0`05348830 fffffa80`05938c58 : nt!KiPageFault+0x16e
    fffff880`02e98728 fffff880`045b36f8 : fffffa80`05c7d000 fffff8a0`05348830 fffffa80`05938c58 fffff800`032785ea : dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x31
    fffff880`02e98730 fffff880`045b612b : fffff8a0`00c8afa8 fffff8a0`05348938 fffff8a0`00c8afa8 fffff8a0`05348938 : dxgmms1!VIDMM_GLOBAL::NotifyAllocationEviction+0x38
    fffff880`02e98760 fffff880`045b301c : fffff8a0`05348830 fffffa80`044d8140 fffffa80`05c7d000 00000000`00000002 : dxgmms1!VIDMM_GLOBAL::EvictAllocation+0x67
    fffff880`02e987a0 fffff880`045afff7 : 00000000`00000000 fffffa80`0a072078 00000000`00000004 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x218
    fffff880`02e987d0 fffff880`045ca7d9 : 00000000`00000000 fffff8a0`02992cd0 fffffa80`00000000 fffffa80`06325200 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
    fffff880`02e989a0 fffff880`045ca514 : fffff880`009eff40 fffff880`045c9f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
    fffff880`02e98b90 fffff880`045ca012 : 00000000`00000000 fffffa80`05434890 00000000`00000080 fffffa80`05402410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880`02e98bc0 fffff800`03510c6a : 00000000`043b96a9 fffffa80`05938b50 fffffa80`03695360 fffffa80`05938b50 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`02e98c00 fffff800`03267086 : fffff880`009eb180 fffffa80`05938b50 fffff880`009f5fc0 fffff880`00ec03bb : nt!PspSystemThreadStartup+0x5a
    fffff880`02e98c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    THREAD_SHA1_HASH_MOD_FUNC:  eb3e0497e1d7b7ccd34666c5c23a60a70530e747
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  d114db912353b2efae2d01c0d47b1d126ecce804
    
    THREAD_SHA1_HASH_MOD:  a24c6c92904eff104d57a6dd6eb14ea6c5df3dae
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
    fffff880`045ba559 ff0b            dec     dword ptr [rbx]
    
    FAULT_INSTR_CODE:  8b490bff
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13
    
    IMAGE_VERSION:  6.1.7601.18126
    
    FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
    
    BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
    
    PRIMARY_PROBLEM_CLASS:  X64_0x50_dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
    
    TARGET_TIME:  2016-03-15T20:10:36.000Z
    
    OSBUILD:  7601
    
    OSSERVICEPACK:  1000
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  272
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 7
    
    OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  2016-02-12 01:40:22
    
    BUILDDATESTAMP_STR:  160211-0600
    
    BUILDLAB_STR:  win7sp1_gdr
    
    BUILDOSVER_STR:  6.1.7601.19160.amd64fre.win7sp1_gdr.160211-0600
    
    ANALYSIS_SESSION_ELAPSED_TIME: a7f
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x50_dxgmms1!vidmm_device::removecommitment+31
    
    FAILURE_ID_HASH:  {66133ecc-07d3-e18b-b5b6-0e933e5dea42}
    
    Followup:     MachineOwner


    Wednesday, March 16, 2016 9:22 AM

All replies

  • The error seems to be graphics related referencing the dxgmms1.sys :

    BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_DEVICE::RemoveCommitment+31

    Try updating the Intel graphics driver - HP seems to have a more recent driver:

    http://h20564.www2.hp.com/hpsc/swd/public/detail?swItemId=vc_155560_1


    Tuesday, March 15, 2016 11:21 PM
  • Hi SHesser,

     

    I agree with auggy, it is probably caused by dxmms1.sys.

    Please refer to auggy’s suggestion to have a test.

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff8d002666e50, 1, fffff880045ba559, 5}
    
    
    Could not read faulting driver name
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DEVICE::RemoveCommitment+31 )
    
    Followup:     MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except.
    Typically the address is just plain bad or it is pointing at freed memory.
    Arguments:
    Arg1: fffff8d002666e50, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff880045ba559, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000005, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  7601.19160.amd64fre.win7sp1_gdr.160211-0600
    
    SYSTEM_MANUFACTURER:  Hewlett-Packard
    
    SYSTEM_PRODUCT_NAME:  HP Compaq Pro 6300 SFF
    
    SYSTEM_SKU:  B5N04UT#ABA
    
    BIOS_VENDOR:  Hewlett-Packard
    
    BIOS_VERSION:  K01 v02.99
    
    BIOS_DATE:  09/15/2015
    
    BASEBOARD_MANUFACTURER:  Hewlett-Packard
    
    BASEBOARD_PRODUCT:  339A
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: fffff8d002666e50
    
    BUGCHECK_P2: 1
    
    BUGCHECK_P3: fffff880045ba559
    
    BUGCHECK_P4: 5
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034b3100
    Unable to get MmSystemRangeStart
     fffff8d002666e50 
    
    FAULTING_IP: 
    dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
    fffff880`045ba559 ff0b            dec     dword ptr [rbx]
    
    MM_INTERNAL_CODE:  5
    
    CPU_COUNT: 4
    
    CPU_MHZ: cdc
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 2a
    
    CPU_STEPPING: 7
    
    CPU_MICROCODE: 6,2a,7,0 (F,M,S,R)  SIG: 28'00000000 (cache) 28'00000000 (init)
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_SESSION_HOST:  V-JINX086636VM
    
    ANALYSIS_SESSION_TIME:  03-16-2016 14:45:42.0369
    
    ANALYSIS_VERSION: 10.0.10586.567 amd64fre
    
    TRAP_FRAME:  fffff88002e98590 -- (.trap 0xfffff88002e98590)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000ffff0000 rbx=0000000000000000 rcx=fffff8a002992cd0
    rdx=fffffa8003f07dc0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880045ba559 rsp=fffff88002e98728 rbp=0000000000000000
     r8=fffffa8003f07d70  r9=fffff8a002992cd0 r10=fffff8a005348830
    r11=fffff8a0053878e0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x31:
    fffff880`045ba559 ff0b            dec     dword ptr [rbx] ds:00000000`00000000=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800032f0c4a to fffff80003276080
    
    STACK_TEXT:  
    fffff880`02e98428 fffff800`032f0c4a : 00000000`00000050 fffff8d0`02666e50 00000000`00000001 fffff880`02e98590 : nt!KeBugCheckEx
    fffff880`02e98430 fffff800`032741ae : 00000000`00000001 fffff8d0`02666e50 00000000`00000000 fffff8d0`02666e50 : nt! ?? ::FNODOBFM::`string'+0x3fe51
    fffff880`02e98590 fffff880`045ba559 : fffff880`045b36f8 fffffa80`05c7d000 fffff8a0`05348830 fffffa80`05938c58 : nt!KiPageFault+0x16e
    fffff880`02e98728 fffff880`045b36f8 : fffffa80`05c7d000 fffff8a0`05348830 fffffa80`05938c58 fffff800`032785ea : dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x31
    fffff880`02e98730 fffff880`045b612b : fffff8a0`00c8afa8 fffff8a0`05348938 fffff8a0`00c8afa8 fffff8a0`05348938 : dxgmms1!VIDMM_GLOBAL::NotifyAllocationEviction+0x38
    fffff880`02e98760 fffff880`045b301c : fffff8a0`05348830 fffffa80`044d8140 fffffa80`05c7d000 00000000`00000002 : dxgmms1!VIDMM_GLOBAL::EvictAllocation+0x67
    fffff880`02e987a0 fffff880`045afff7 : 00000000`00000000 fffffa80`0a072078 00000000`00000004 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x218
    fffff880`02e987d0 fffff880`045ca7d9 : 00000000`00000000 fffff8a0`02992cd0 fffffa80`00000000 fffffa80`06325200 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
    fffff880`02e989a0 fffff880`045ca514 : fffff880`009eff40 fffff880`045c9f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
    fffff880`02e98b90 fffff880`045ca012 : 00000000`00000000 fffffa80`05434890 00000000`00000080 fffffa80`05402410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880`02e98bc0 fffff800`03510c6a : 00000000`043b96a9 fffffa80`05938b50 fffffa80`03695360 fffffa80`05938b50 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`02e98c00 fffff800`03267086 : fffff880`009eb180 fffffa80`05938b50 fffff880`009f5fc0 fffff880`00ec03bb : nt!PspSystemThreadStartup+0x5a
    fffff880`02e98c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    THREAD_SHA1_HASH_MOD_FUNC:  eb3e0497e1d7b7ccd34666c5c23a60a70530e747
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  d114db912353b2efae2d01c0d47b1d126ecce804
    
    THREAD_SHA1_HASH_MOD:  a24c6c92904eff104d57a6dd6eb14ea6c5df3dae
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
    fffff880`045ba559 ff0b            dec     dword ptr [rbx]
    
    FAULT_INSTR_CODE:  8b490bff
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13
    
    IMAGE_VERSION:  6.1.7601.18126
    
    FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
    
    BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
    
    PRIMARY_PROBLEM_CLASS:  X64_0x50_dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
    
    TARGET_TIME:  2016-03-15T20:10:36.000Z
    
    OSBUILD:  7601
    
    OSSERVICEPACK:  1000
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  272
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 7
    
    OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  2016-02-12 01:40:22
    
    BUILDDATESTAMP_STR:  160211-0600
    
    BUILDLAB_STR:  win7sp1_gdr
    
    BUILDOSVER_STR:  6.1.7601.19160.amd64fre.win7sp1_gdr.160211-0600
    
    ANALYSIS_SESSION_ELAPSED_TIME: a7f
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x50_dxgmms1!vidmm_device::removecommitment+31
    
    FAILURE_ID_HASH:  {66133ecc-07d3-e18b-b5b6-0e933e5dea42}
    
    Followup:     MachineOwner


    Wednesday, March 16, 2016 9:22 AM
  • Sorry guys! I took the hd drive out and put it into another like box. Just want to make sure it's not the vga display port over the driver.

    Thanks again

    Wednesday, March 23, 2016 2:48 PM