locked
BSOD RRS feed

  • Question

  • I have been having BSOD:ds so im asking is there any fix for these bsods or do i have to get new parts.

    Here are the  dump files 

    ==================================================
    Dump File         : 051114-14383-01.dmp
    Crash Time        : 11.5.2014 9:27:41
    Bug Check String  : CRITICAL_OBJECT_TERMINATION
    Bug Check Code    : 0x000000f4
    Parameter 1       : 00000000`00000003
    Parameter 2       : fffffa80`0a2c2640
    Parameter 3       : fffffa80`0a2c2920
    Parameter 4       : fffff800`033d77b0
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+75bc0
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\051114-14383-01.dmp
    Processors Count  : 4
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 297 744
    Dump File Time    : 11.5.2014 9:28:47
    ==================================================

    ==================================================
    Dump File         : 050514-5928-01.dmp
    Crash Time        : 5.5.2014 19:10:55
    Bug Check String  : KERNEL_DATA_INPAGE_ERROR
    Bug Check Code    : 0x0000007a
    Parameter 1       : fffff6fc`40024768
    Parameter 2       : ffffffff`c000000e
    Parameter 3       : 00000002`24f7b860
    Parameter 4       : fffff880`048ed01a
    Caused By Driver  : dxgkrnl.sys
    Caused By Address : dxgkrnl.sys+7401a
    File Description  : 
    Product Name      : 
    Company           : 
    File Version      : 
    Processor         : x64
    Crash Address     : ntoskrnl.exe+75bc0
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\050514-5928-01.dmp
    Processors Count  : 4
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 297 744
    Dump File Time    : 5.5.2014 19:11:33
    ==================================================

    ==================================================
    Dump File         : 040914-6084-01.dmp
    Crash Time        : 9.4.2014 14:04:54
    Bug Check String  : MEMORY_MANAGEMENT
    Bug Check Code    : 0x0000001a
    Parameter 1       : 00000000`00041790
    Parameter 2       : fffffa80`063a3aa0
    Parameter 3       : 00000000`0000ffff
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+75bc0
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\040914-6084-01.dmp
    Processors Count  : 4
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 297 744
    Dump File Time    : 9.4.2014 14:06:26
    ==================================================

    Sunday, May 18, 2014 9:28 AM

Answers

  • Hi,

    The issue is caused by DirectX Graphics MMS. Please update your graphic card driver to check the results.

    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    dxgmms1!VidMmTerminateAllocation+da
    fffff880`049adbf6 488b00          mov     rax,qword ptr [rax]
    
    CONTEXT:  fffff88009a47c60 -- (.cxr 0xfffff88009a47c60;r)
    rax=0000000000000000 rbx=fffffa800a24f000 rcx=00000000000007ff
    rdx=0000000000000175 rsi=fffff8a00df08808 rdi=fffff8a009cffaf0
    rip=fffff880049adbf6 rsp=fffff88009a48640 rbp=fffffa800b8fe170
     r8=0000000000000801  r9=0000000000000174 r10=fffff80003603760
    r11=fffff88009a48610 r12=fffff8a00bcffb50 r13=fffff880048d6a08
    r14=0000000000000038 r15=0000000000000001
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    dxgmms1!VidMmTerminateAllocation+0xda:
    fffff880`049adbf6 488b00          mov     rax,qword ptr [rax] ds:002b:00000000`00000000=????????????????
    Last set context:
    rax=0000000000000000 rbx=fffffa800a24f000 rcx=00000000000007ff
    rdx=0000000000000175 rsi=fffff8a00df08808 rdi=fffff8a009cffaf0
    rip=fffff880049adbf6 rsp=fffff88009a48640 rbp=fffffa800b8fe170
     r8=0000000000000801  r9=0000000000000174 r10=fffff80003603760
    r11=fffff88009a48610 r12=fffff8a00bcffb50 r13=fffff880048d6a08
    r14=0000000000000038 r15=0000000000000001
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    dxgmms1!VidMmTerminateAllocation+0xda:
    fffff880`049adbf6 488b00          mov     rax,qword ptr [rax] ds:002b:00000000`00000000=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880049adbf6
    
    STACK_TEXT:  
    fffff880`09a48640 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidMmTerminateAllocation+0xda
    
    
    FOLLOWUP_IP: 
    dxgmms1!VidMmTerminateAllocation+da
    fffff880`049adbf6 488b00          mov     rax,qword ptr [rax]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  dxgmms1!VidMmTerminateAllocation+da
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13
    
    IMAGE_VERSION:  6.1.7601.18126
    
    STACK_COMMAND:  .cxr 0xfffff88009a47c60 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VidMmTerminateAllocation+da
    
    BUCKET_ID:  X64_0x3B_dxgmms1!VidMmTerminateAllocation+da
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x3b_dxgmms1!vidmmterminateallocation+da
    
    FAILURE_ID_HASH:  {f88a42dc-6b8f-f85a-0ee1-455a5d348100}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm dxgmms1
    start             end                 module name
    fffff880`049ac000 fffff880`049f2000   dxgmms1    (pdb symbols)          d:\symbols\dxgmms1.pdb\93AB163000A844D5BF442A979FB6FF991\dxgmms1.pdb
        Loaded symbol image file: dxgmms1.sys
        Mapped memory image file: d:\symbols\dxgmms1.sys\5164DC1346000\dxgmms1.sys
        Image path: \SystemRoot\System32\drivers\dxgmms1.sys
        Image name: dxgmms1.sys
        Timestamp:        Wed Apr 10 11:27:15 2013 (5164DC13)
        CheckSum:         00043C9B
        ImageSize:        00046000
        File version:     6.1.7601.18126
        Product version:  6.1.7601.18126
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     dxgmms1.sys
        OriginalFilename: dxgmms1.sys
        ProductVersion:   6.1.7601.18126
        FileVersion:      6.1.7601.18126 (win7sp1_gdr.130409-1534)
        FileDescription:  DirectX Graphics MMS
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    


    Kate Li
    TechNet Community Support

    • Proposed as answer by Cloud_TS Thursday, May 22, 2014 1:47 AM
    • Marked as answer by Cloud_TS Wednesday, June 4, 2014 1:44 AM
    Monday, May 19, 2014 9:48 AM

All replies

  • Hi,

    In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.

    If you don't know where .DMP files are located, here's how to get to them:

    1. Navigate to the %systemroot%\Minidump folder.

    2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.

    3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Prefered sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers.

    4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.

    If you are going to use Onedrive but don't know how to upload to it, please visit the following:

    Upload photos and files to Onedrive.

    Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete .DMP files upon use.

    If your computer is not generating .DMP files, please do the following:

    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

    4. Double check that the WERS is ENABLED:

    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

    If you cannot get into normal mode to do any of this, please do this via Safe Mode.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Sunday, May 18, 2014 11:09 AM
  • Hi.

    Here is a link to .dmp files that i uploaded on Onedrive. https://onedrive.live.com/redir?resid=179A69DD046E54E2%21181 .

    Sunday, May 18, 2014 11:36 AM
  • 'This item may not exist or may not be available'.

    It appears you'll need to adjust the sharing permissions for that link.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Sunday, May 18, 2014 11:49 AM
  • To upload click on this link:
    https://onedrive.live.com/

    Place the cursor on Files and click on Upload.
    A window opens with Choose File to Upload. Place the cursor on the file to be uploaded and click on the Open button.
    A rectangular box appears containing the file that has been uploaded. Check the box in the top right corner of the rectangular box.
    Click on Share and then click on Get a Link.
    Click on Public
    Click on Create Link
    Click on Everyone under Shared with.
    Click on Shorten.
    Place the cursor in the shortened link, right click and select Copy.
    Paste into your reply to these forums.
    Click on Done.

    It is important to Paste the link before clicking on Done to avoid pasting the wrong link.

    To post a link access your OneDrive where you placed the files to be shared. Place the cursor in the Address Bar, right click and select Select All. Right click again and select Copy to place the address in your Clipboard. Place the cursor in an open message here, right click and select Paste.


    Hope this helps, Gerry

    Sunday, May 18, 2014 12:38 PM
  • I think i may have missclicked dot on the end try to search without it and you should find it. I have set the sharing on evryone*.

    Edit: if it doesnt work this one should http://1drv.ms/1nab2N3

    • Edited by Epicpasta Sunday, May 18, 2014 2:47 PM
    Sunday, May 18, 2014 12:40 PM
  • The crash dumps within this zip are ~4 months old. Before I take a look, are these the latest crash dumps/is there nothing newer?

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Sunday, May 18, 2014 9:33 PM
  • Hi,

    The issue is caused by DirectX Graphics MMS. Please update your graphic card driver to check the results.

    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    dxgmms1!VidMmTerminateAllocation+da
    fffff880`049adbf6 488b00          mov     rax,qword ptr [rax]
    
    CONTEXT:  fffff88009a47c60 -- (.cxr 0xfffff88009a47c60;r)
    rax=0000000000000000 rbx=fffffa800a24f000 rcx=00000000000007ff
    rdx=0000000000000175 rsi=fffff8a00df08808 rdi=fffff8a009cffaf0
    rip=fffff880049adbf6 rsp=fffff88009a48640 rbp=fffffa800b8fe170
     r8=0000000000000801  r9=0000000000000174 r10=fffff80003603760
    r11=fffff88009a48610 r12=fffff8a00bcffb50 r13=fffff880048d6a08
    r14=0000000000000038 r15=0000000000000001
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    dxgmms1!VidMmTerminateAllocation+0xda:
    fffff880`049adbf6 488b00          mov     rax,qword ptr [rax] ds:002b:00000000`00000000=????????????????
    Last set context:
    rax=0000000000000000 rbx=fffffa800a24f000 rcx=00000000000007ff
    rdx=0000000000000175 rsi=fffff8a00df08808 rdi=fffff8a009cffaf0
    rip=fffff880049adbf6 rsp=fffff88009a48640 rbp=fffffa800b8fe170
     r8=0000000000000801  r9=0000000000000174 r10=fffff80003603760
    r11=fffff88009a48610 r12=fffff8a00bcffb50 r13=fffff880048d6a08
    r14=0000000000000038 r15=0000000000000001
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    dxgmms1!VidMmTerminateAllocation+0xda:
    fffff880`049adbf6 488b00          mov     rax,qword ptr [rax] ds:002b:00000000`00000000=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880049adbf6
    
    STACK_TEXT:  
    fffff880`09a48640 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidMmTerminateAllocation+0xda
    
    
    FOLLOWUP_IP: 
    dxgmms1!VidMmTerminateAllocation+da
    fffff880`049adbf6 488b00          mov     rax,qword ptr [rax]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  dxgmms1!VidMmTerminateAllocation+da
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13
    
    IMAGE_VERSION:  6.1.7601.18126
    
    STACK_COMMAND:  .cxr 0xfffff88009a47c60 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VidMmTerminateAllocation+da
    
    BUCKET_ID:  X64_0x3B_dxgmms1!VidMmTerminateAllocation+da
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x3b_dxgmms1!vidmmterminateallocation+da
    
    FAILURE_ID_HASH:  {f88a42dc-6b8f-f85a-0ee1-455a5d348100}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm dxgmms1
    start             end                 module name
    fffff880`049ac000 fffff880`049f2000   dxgmms1    (pdb symbols)          d:\symbols\dxgmms1.pdb\93AB163000A844D5BF442A979FB6FF991\dxgmms1.pdb
        Loaded symbol image file: dxgmms1.sys
        Mapped memory image file: d:\symbols\dxgmms1.sys\5164DC1346000\dxgmms1.sys
        Image path: \SystemRoot\System32\drivers\dxgmms1.sys
        Image name: dxgmms1.sys
        Timestamp:        Wed Apr 10 11:27:15 2013 (5164DC13)
        CheckSum:         00043C9B
        ImageSize:        00046000
        File version:     6.1.7601.18126
        Product version:  6.1.7601.18126
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     dxgmms1.sys
        OriginalFilename: dxgmms1.sys
        ProductVersion:   6.1.7601.18126
        FileVersion:      6.1.7601.18126 (win7sp1_gdr.130409-1534)
        FileDescription:  DirectX Graphics MMS
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    


    Kate Li
    TechNet Community Support

    • Proposed as answer by Cloud_TS Thursday, May 22, 2014 1:47 AM
    • Marked as answer by Cloud_TS Wednesday, June 4, 2014 1:44 AM
    Monday, May 19, 2014 9:48 AM