WinDBG - The Basics for Debugging Crash Dumps in Windows 10  

Page 2 of 5 FirstFirst 1234 ... LastLast

  1. Posts : 364
    Windows 10
       #10

    derekimo said:
    It would be better if you show us what you get, I have no idea which one of those dumps you are reading, let's stick to one dump and see what might be the problem.


    There is no driver getting flagged so you wouldn't see it.
    Thanks.I was examining the newest dump. Nevermind,I understand it isn't necessary that driver gets flagged in BSOD.What are the other methods?
      My Computer


  2. Posts : 1,092
    Win 10 Pro x64
       #11

    This is from the bottom of that section,

    This method can be applied to all drivers that appear in stacks within dump files. It is worth noting however that not all dump files will show drivers as the problem, in some instances it may be hardware that is causing issues but if the STOP code is one that normally indicates a driver as being the problem it may be necessary to run Driver Verifier to weed out the offending driver. These calls come with experience, and identifying drivers as causes of BSODs is just the tip of the proverbial iceberg.
      My Computer


  3. Posts : 364
    Windows 10
       #12

    Sorry to bother you experts again, but I want to know if there is a way from the minidumps only to get the drivers list loaded during the crash with date of the driver?
    In MS community forums we don't use DM log collector so we don't have a driver.txt file.
      My Computer


  4. Posts : 14,903
    Windows 10 Pro
       #13

    The drivers list can be found without command, in the menu go to debug and choose modules.
      My Computers


  5. Posts : 155
    Windows 10
       #14

    Debugging a crash and i need help. Don't want you to do all the work, just give me a way to follow.
      My Computer


  6. Posts : 14,903
    Windows 10 Pro
       #15

    Where are you stuck exactly?
      My Computers


  7. Posts : 155
    Windows 10
       #16

    Give you some lines.

    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE_256_c0000005_memory_corruption!HITMAN

    BUCKET_ID: MEMORY_CORRUPTION_NULL_CLASS_PTR_READ_LARGE_256_memory_corruption!HITMAN

    The thread in question gives an "Error Access Violation" 0xC0000005:
    HITMAN!AK::MemoryMgr::GetPoolName

    Is a game crash.

    Thinking to a lack of permissions and putting all the executable files on run as administrator.

      My Computer


  8. Posts : 14,903
    Windows 10 Pro
       #17

    Please note that the tutorial is meant for system crash dumps, game crash dumps contain different information and thus not all the steps in the tutorial work for a game crash dump.
      My Computers


  9. Posts : 155
    Windows 10
       #18

    K, there's another tutorial should i follow to solve the problem? Can you help me anyway?
      My Computer


  10. Posts : 14,903
    Windows 10 Pro
       #19

    There are on this site no other tutorials I know of that can help, but there are many I'm not aware of.

    Maybe, but I would like to see the dump. I would ask that you create a new thread at the BSOD section, zip the dump and upload it. This thread isn't the right one for your problem.
    Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums
      My Computers


 

Tutorial Categories

WinDBG - The Basics for Debugging Crash Dumps in Windows 10 Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:34.
Find Us




Windows 10 Forums