Page 1 of 3 123 LastLast
  1.    13 Mar 2017 #1
    Join Date : Mar 2017
    Posts : 13
    windows 10

    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"http://msdl.microsoft.com/download/symbols

    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.
      My ComputerSystem Spec
  2.    13 Mar 2017 #2
    Join Date : Jul 2014
    San Jose, California
    Posts : 2,154
    Ubuntu14.04x64 MintMate17x64 Win10Prox64

    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.
      My ComputerSystem Spec
  3.    14 Mar 2017 #3
    Join Date : Mar 2017
    Posts : 13
    windows 10
    Thread Starter

    ok.I do not have any BSOD errors yet.

    I have been experiencing whea/kernel based crash reports from a mod..sometimes...
      My ComputerSystem Spec
  4.    14 Mar 2017 #4
    Join Date : Jun 2015
    Posts : 12,873
    Windows 10 Pro

    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.
      My ComputersSystem Spec
  5.    14 Mar 2017 #5
    Join Date : Mar 2017
    Posts : 13
    windows 10
    Thread Starter

    ok,I did not successfully get the dmp test file or one of my files to go into debugger...the screenshot above explains.
      My ComputerSystem Spec
  6.    14 Mar 2017 #6
    Join Date : Jul 2014
    San Jose, California
    Posts : 2,154
    Ubuntu14.04x64 MintMate17x64 Win10Prox64

    Quote Originally Posted by agenthunk View Post
    ok,I did not successfully get the dmp test file or one of my files to go into debugger...the screenshot above explains.
    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.
      My ComputerSystem Spec
  7.    14 Mar 2017 #7
    Join Date : Mar 2017
    Posts : 13
    windows 10
    Thread Starter

    here are images showing my files...


    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
      My ComputerSystem Spec
  8.    14 Mar 2017 #8
    Join Date : Mar 2017
    Posts : 13
    windows 10
    Thread Starter

    WhoCrashed report


    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.


      My ComputerSystem Spec
  9.    14 Mar 2017 #9
    Join Date : Mar 2017
    Posts : 13
    windows 10
    Thread Starter

    Test file


    Quote Originally Posted by topgundcp View Post
    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.
    Attachment 125115

    I did and this is the result.
      My ComputerSystem Spec
  10.    14 Mar 2017 #10
    Join Date : Jun 2015
    Posts : 12,873
    Windows 10 Pro

    Did you save the workspace after inserting the symbol search path?
      My ComputersSystem Spec

 
Page 1 of 3 123 LastLast


Similar Threads
Thread Forum
Windows 10 XML file generator for unattended setup
Anyone ran across a Windows 10 XML file generator for unattended setup? That Works!!!:D
Installation and Upgrade
Install SETUP file after download
A friend has downloaded Win 10 to a Win 7 PC. Now he wants to install. A directory (folder) contains the files, with SETUP.exe to kick off the process, but I don't recall where it is located. Been too long, so please jog my memory. Was it...
Installation and Upgrade
File History Setup
I am looking for some assistance on my setup. There is 4 people on my family (dad, mom, 2 kids). Mom, kid1, and kid2 have each their laptops. I have setup a microsoft family and they are all on the same homegroup. They all login with their own MS...
Backup and Restore
BSOD where WinDbg suspects ntkrnlmp.exe
Hello. I have been having BSOD issues for the last several months on this laptop. They most commonly appear when I'm playing music and/or games, and it has gotten to the point where I am hesitant to even play online games anymore, as I often end...
BSOD Crashes and Debugging
Solved DPC_WATCHDOG_VIOLATION BSOD, Windbg unable to load symbols
Windows 10 Insider Preview Build 10130 WIN-A82HE7DTDIP-Fri_06_05_2015_172808_86.zip attached PC Specs are in profile :P So I have windbg, I followed the how to install guide (Using both the win8.1 and win10 SDK, both give the same errors,...
BSOD Crashes and Debugging
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 04:08.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums