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"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.

:)

 

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.

 

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

 

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.

 

ok.I do not have any BSOD errors yet.

I have been experiencing whea/kernel based crash reports from a mod..sometimes...

 

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.

 

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.

 

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

 

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.

 

Attachment 125115

I did and this is the result.

 

Did you save the workspace after inserting the symbol search path?

 

I believe I did.I followed a tutorial video on youtube.
Install and configure WinDBG - YouTube

Attachment 125116

 

I see what the problem is, replace the quotes ( " ) with *

 

SRV*C:\SymCache*Symbol information

like this?