none
How to fix windbg error: The debugging session could not be started: Access to the path 'C:\Windows\Memory.dmp' is denied and Cannot open the crash dump at C:\windows\memory.dmp. You must manually elevate the debugger to continue RRS feed

  • Question

  • How to fix windbg error:  The debugging session could not be started:  Access to the path 'C:\Windows\Memory.dmp' is denied and Cannot open the crash dump at C:\windows\memory.dmp.  You must manually elevate the debugger to continue

    The computer that I'm using to type this post had a BSOD today.

    Windows Version 10.0.17763.379

    WinDbg Version 1.0.1902.07001

    It was able to debug the mini dump however there were problems with the memory dump import or file configuration.

    These were the errors seen today:

    How do you fix:  The debugging session could not be started:  Access to the path 'C:\Windows\Memory.dmp' is denied

    In the right lower corner it displayed that it found bugcheck 139.  So it processed something to post it.

    Using file explorer and then creating a desktop shortcut did not alter the access problem.

    If the right lower corner notice is clicked to open the memory dump the error message displayed:

    Microsoft Windows [Version 10.0.17763.379]
    (c) 2018 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan.  This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1

    Image Version: 10.0.17763.379

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.

    C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.

    Stage 1: Examining basic file system structure ...
      431360 file records processed.
    File verification completed.
      11428 large file records processed.
      0 bad file records processed.

    Stage 2: Examining file name linkage ...
      869 reparse records processed.
      571564 index entries processed.
    Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered to lost and found.
      869 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
      70103 data files processed.
    CHKDSK is verifying Usn Journal...
      34202520 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

     248570090 KB total disk space.
     171160400 KB in 275660 files.
        209620 KB in 70104 indexes.
             0 KB in bad sectors.
        548446 KB in use by the system.
         65536 KB occupied by the log file.
      76651624 KB available on disk.

          4096 bytes in each allocation unit.
      62142522 total allocation units on disk.
      19162906 allocation units available on disk.

    How do you manually elevate the debugger?

    (The mini dump was able to be debugged without permission problems)

    Saturday, April 6, 2019 3:15 AM

All replies

  • Would think, your Memory.dmp has restricted access:

    SYSTEM and Administrators:

    Then you may want e.g. to start 'Windbg Preview' elevated in the 'Start Menu'
    Right-click 'WinDbg Preview' ->'More'->'Run as Administrator'
    or for legacy 'Windbg' you can use an elevated command prompt.

     
    With kind regards
    Saturday, April 6, 2019 8:41 AM
  • What are the steps to open the above image?

    When the right click windbg run as administrator is done:

    a) how do you get windbg to automatically find the computer's memory.dmp file from the recent BSOD?

    (it had the pop up in the right lower corner in the image but it did not reappear when windbg was just opened)

    b) if it is no longer able to find it automatically how do you direct it?

    (windows may have deleted the file?)

    Permissions on the computer had never been modified.  What had happened?

    The mini and memory dump files from the recent crash can no longer be found on the computer.

    Cleaning software was not ran so this was an automatic windows process.

    Startup and recovery displays:

    C:\windows\memory.dmp

    unchecked:  overwrite any existing file

    checked:  disable automatic deletion of memory dumps when disk space is low

    How are the mini dumps being deleted and how do you prevent any future deletions?

    How are the memory dumps being deleted and how do you prevent any future deletions?

    Saturday, April 6, 2019 9:10 PM
  • a) how do you get windbg to automatically find the computer's memory.dmp file

    The memory.dmp file is only one (unlike numerous minidumps) so you just check if it exists.

    b) if it is no longer able to find it automatically how do you direct it?

    If memory.dmp does not exist, you cannot open it. Check that the configured type of dump is not a minidump.

    how do you prevent any future deletions?

    If you need  to save minidumps, copy them from the machine to other place. A Windows system is not an attic for stale minidumps.

    -- pa

    Sunday, April 7, 2019 1:48 AM
  • 1) Which setting in Windows is automatically deleting mini dump files?

    2) In Windows 1607 mini dump files were infrequently deleted.

    How do you modify the settings in Windows 1809 for two weeks so that mini dump files remain in the mini dump folder?

    3) How do you modify the settings in Windows 1809 for two weeks so that memory dump files remain in the memory dump folder?

    4) What are the steps to open the image in the prior thread?


    Today is April 6 2019.  The memory and mini dump files were created during the BSOD on April5, 2015.

    How come Windows default is to clean mini dump files in < 24 hours?

    How do you modify the time period?

    Crash dump found at C:\WINDOWS\MEMORY.DMP
    Creation date: 04/05/2019 13:14:07
    Size on disk: 2486 MB

    .

    .

        Directory: C:\WINDOWS\Minidump

    Mode                LastWriteTime         Length Name

    -a----         4/5/2019   1:14 PM        1972172 040519-10812-01.dmp

    .

    .

    April 6, 2019

    C:\WINDOWS\MEMORY.DMP was not found

    C:\WINDOWS\Minidump contains no dump files.


    Sunday, April 7, 2019 4:23 AM
  • I would create a scheduled task to backup the minidumps as soon as the machine starts.

    -- pa

    Sunday, April 7, 2019 10:45 AM
  • On a very frequent basis I troubleshoot BSOD for end users.

    The were/are many end users that do not have mini or memory dump log files to collect as windows had already cleaned/deleted the log files.

    This BSOD happened on one of my computers and I was surprised to see the quick and automatic deletion.

    So a fix is needed on many computes.



    Sunday, April 7, 2019 11:02 AM
  • On a very frequent basis I troubleshoot BSOD for end users.

    My sincere sympathies.

    So a fix is needed on many computes.

    A scheduler task can be exported and then imported on other computers.

    -- pa

    Sunday, April 7, 2019 1:28 PM
  • 1)What are examples of tasks to save each mini and memory dumps?

    2) Windows 1607 will maintain mini dump files.  How can Windows 1809 be modified so that it behaves like 1607?

    3) Where in 1809 is the setting that displays how mini dump files are being cleaned or deleted?

    4) Where in 1809 is the setting that displays how memory dump files are being cleaned or deleted?

    Sunday, April 7, 2019 4:49 PM
  • My Windows 10 1809 Build (17763.437) claims (deprecated?) 'cleanmgr.exe' is deleting system error memory dump file in Windows directory:


    As it happens, about the same time Windows maintenance task 'SilentCleanup' is running

    with:
    %windir%\system32\cleanmgr.exe /autoclean /d %systemdrive%

    (By the way, I did not configure this new 'Storage Sense' yet).

    No warranty
    With kind regards
    Thursday, April 18, 2019 4:20 PM