Windows 10: BSOD/WinDBG setup and DMP file help?

Discus and support BSOD/WinDBG setup and DMP file help? in Windows 10 BSOD Crashes and Debugging to solve the problem; I have followed the instructions to setup WinDBG in this videolink: Install and configure WinDBG - YouTube I did the setup instructions in this... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by agenthunk, Mar 13, 2017.

  1. agenthunk Win User

    BSOD/WinDBG setup and DMP file help?


    I have followed the instructions to setup WinDBG in this videolink:
    Install and configure WinDBG - YouTube

    I did the setup instructions in this video for windows debugger and have the symbol file path saved.
    SRV"C:\SymCache"Symbol information

    I do not have the DMP file uploaded online,what I need help with is to manually put the DMP file in the debugger whenever I have a error report.
    Attachment 125045

    I have the setup for DMP file checked as Complete File.

    I do not know or remember if I did where the Folder by default for DMP files are located and do not know how to use the SDK debugging tool and how to manually move the DMP file to the Debugger X64.

    I followed the instructions through this forums link:
    Install and Configure WinDBG for BSOD Analysis

    Attachment 125046

    So Am I done?this is my first time using this.

    Some help will be appreciated.
    Thanks in advance.

    :)
     
    agenthunk, Mar 13, 2017
    #1

  2. Getting multiple BSOD's and query about reading DMP files on Windows 10 computer

    Old title: WindBG DMP File Help - BSOD

    Hello,

    Finally got tired of multiple BSOD and decided to learn how to debug. Unfortunately reading the DMP file is harder than I thought!.

    Can someone please help me figure this out?

    Your help is greatly appreciated!

    I recently reset Windows 10 and have only installed a few base program, nothing fancy.

    DMP file:

    062116-20656-01.dmp

    Thanks.
     
    Oliver1234_999, Mar 13, 2017
    #2
  3. AndyLun Win User
    Windows 10 BSOD pci.sys

    I've been getting BSOD on my laptop since I upgraded to Windows 10, and the Windbg says its caused by pci.sys (DRIVER_POWER_STATE_FAILURE).

    After some searching on the internet, I know that something else must have caused pci.sys to crash.

    112315-35515-01.dmp |
    Windbg Log

    MEMORY.dmp (File is 6.9GB, I can't upload it) |
    Windbg Log


    Please help me thank you very much
     
    AndyLun, Mar 13, 2017
    #3
  4. topgundcp Win User

    BSOD/WinDBG setup and DMP file help?

    The dmp file is saved to: %SystemRoot%\MEMORY.dmp (ie. C:\Windows\MEMORY.dmp) as shown in the screen shot. You would need to copy it to somewhere else, e.g. desktop. Or you could set to save it to desktop (%USERPROFILE%\Desktop\MEMORY.DMP) if BSOD occurs.
    Next, just run windbg then drag and drop the dmp file into it.
     
    topgundcp, Mar 13, 2017
    #4
  5. agenthunk Win User
    ok.I do not have any BSOD errors yet.

    I have been experiencing whea/kernel based crash reports from a mod..sometimes...
     
    agenthunk, Mar 13, 2017
    #5
  6. axe0 New Member
    A dump is created after a system crash. If a WHEA error results in a BSOD it creates a dump.
    A kernel crash will always provide a dump since the system cannot run without it.
     
  7. agenthunk Win User
    ok,I did not successfully get the dmp test file or one of my files to go into debugger...the screenshot above explains.
     
    agenthunk, Mar 13, 2017
    #7
  8. topgundcp Win User

    BSOD/WinDBG setup and DMP file help?

    For testing purpose, just go to the BSOD section of the forum and download one of the ZIP file, use the dmp file to test with.
     
    topgundcp, Mar 13, 2017
    #8
  9. agenthunk Win User
    Attachment 125105


    Attachment 125106

    the top one is the file explorer before I scrolled down.
    the bottom is the bottom of the file explorer list...
    most of what is missing is other dmp files from game release folders from my x86 steam folders...

    this one is the first folder you see called minidump at the top....
    Attachment 125108

    so I did the to desktop from that folder and it gave me this error...
    Attachment 125109
     
    agenthunk, Mar 13, 2017
    #9
  10. agenthunk Win User
    System Information (local)
    Computer name: LAPTOP-CQ24RH6L
    Windows version: Windows 10 , 10.0, build: 14393
    Windows dir: C:\WINDOWS
    Hardware: HP Notebook, HP, 81F9
    CPU: AuthenticAMD AMD A10-9600P RADEON R5, 10 COMPUTE CORES 4C+6G AMD586, level: 21
    4 logical processors, active mask: 15
    RAM: 6005317632 bytes total



    Crash Dump Analysis
    Crash dump directory: C:\WINDOWS\Minidump

    Crash dumps are enabled on your computer.

    On Thu 3/9/2017 11:22:10 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\030917-33671-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x6BB153)
    Bugcheck code: 0x124 (0x0, 0xFFFF880FE407F3A8, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Wed 3/8/2017 6:20:32 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\030817-28171-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x6BB153)
    Bugcheck code: 0x124 (0x0, 0xFFFFD90A0915E038, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Wed 3/1/2017 6:29:46 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\030117-29062-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x6BB153)
    Bugcheck code: 0x124 (0x0, 0xFFFFCF0CC5A888F8, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Wed 3/1/2017 5:59:33 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\030117-28859-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x6BB153)
    Bugcheck code: 0x124 (0x0, 0xFFFFC2098C1588F8, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 2/6/2017 5:49:12 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\020617-28093-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x6BB153)
    Bugcheck code: 0x124 (0x0, 0xFFFFBA09C35C8038, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




    Conclusion
    6 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


    Read the topic general suggestions for troubleshooting system crashes for more information.

    Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
     
    agenthunk, Mar 13, 2017
    #10
  11. agenthunk Win User
    Attachment 125115

    I did and this is the result.
     
    agenthunk, Mar 13, 2017
    #11
  12. axe0 New Member
    Did you save the workspace after inserting the symbol search path?
     
  13. agenthunk Win User

    BSOD/WinDBG setup and DMP file help?

    agenthunk, Mar 13, 2017
    #13
  14. axe0 New Member
    I see what the problem is, replace the quotes ( " ) with *
     
  15. agenthunk Win User
    SRV*C:\SymCache*Symbol information

    like this?
     
    agenthunk, Mar 14, 2017
    #15
Thema:

BSOD/WinDBG setup and DMP file help?

Loading...
  1. BSOD/WinDBG setup and DMP file help? - Similar Threads - BSOD WinDBG setup

  2. Help reading DMP file

    in Windows 10 BSOD Crashes and Debugging
    Help reading DMP file: Hello, I've being having difficulty with my machine crashing recently. I know when it crashes with a BSOD a dump file is created but I can't seem to read it, I've tried to read it by installing some software but It isn't really working. could someone either direct me in...
  3. BSOD .dmp file

    in Windows 10 BSOD Crashes and Debugging
    BSOD .dmp file: Hello, I hope that this is the correct place to post this .dmp file from a BSOD I just experienced, thank you https://iowa-my.sharepoint.com/:u:/g/personal/jalmanza_uiowa_edu/EV4I7cab_RpIkAdW7S-9E4YBhog_P8Qto6JkYYBwVsQu4g?e=LOxu1N...
  4. Need help to read these dmp files

    in Windows 10 BSOD Crashes and Debugging
    Need help to read these dmp files: Hello, my computer constantly BSOD's and I was wondering if anyone could help me read these dump files. Any help would be appreciated! https://drive.google.com/drive/folders/109a7bVr0IyRCFPDv2yA0qH1xIjsa2YsA?usp=sharing...
  5. Help with BSOD - Unexpected store exception - help with reading dmp file

    in Windows 10 BSOD Crashes and Debugging
    Help with BSOD - Unexpected store exception - help with reading dmp file: Hi, i have been having trouble lately with my laptop constantly crashing. I get the stop code: unexpected store exception. I have 2 compressed dmp files, but im not sure how to upload it in here. Can anyone help?...
  6. BSOD .dmp file and system info

    in Windows 10 BSOD Crashes and Debugging
    BSOD .dmp file and system info: Hi there I hope I'm posting this in the right place? I was following the "Driver Verifier-- tracking down a mis-behaving driver." thread and have got the .dmp file and system info links here: - https://1drv.ms/u/s!AmXfeEzR1K_YgR_LigraN-Ixp9wz...
  7. BSOD and uploading dmp files.

    in Windows 10 BSOD Crashes and Debugging
    BSOD and uploading dmp files.: Hello, Since a few weeks I am getting BSODs randomly when I boot or reboot my computer. I have tried reinstalling windows 10 pro (64bit) but the crashes still occur. It is not always when I boot, sometimes it al goes ok. While looking on the web I found the page to use...
  8. DMP File Help? Fortnite UE4

    in Windows 10 BSOD Crashes and Debugging
    DMP File Help? Fortnite UE4: Anyone know what this could be? Code: Microsoft (R) Windows Debugger Version 10.0.17134.12 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\above\OneDrive\Desktop\UE4Minidump.dmp] User Mini Dump File: Only registers, stack and...
  9. DMP File Help?

    in Windows 10 BSOD Crashes and Debugging
    DMP File Help?: Anyone help me with this problem Microsoft (R) Windows Debugger Version 10.0.17134.12 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\above\OneDrive\Desktop\UE4Minidump.dmp] User Mini Dump File: Only registers, stack and portions...
  10. BSOD with DMP files attached

    in Windows 10 BSOD Crashes and Debugging
    BSOD with DMP files attached: Hello, I was hoping someone can look at my DMP files and analyze what is causing my computer to crash. I'm am not exactly sure I need to provide more details, because I believe the DMP files are all that is necessarily. The crashes have occurred lately while I was importing...