I need help reading some Mini-dumps to solve some Bsods that have been just out of arms reach

[JosiahCrawford]

Here are some of the more recent bsods, link to my Onedrive

https://1drv.ms/u/s!AmSGGFeCFoVOlBLFmda0pNdvbALy
https://1drv.ms/u/s!AmSGGFeCFoVOlBMYbG2PXQKfxIMg
https://1drv.ms/u/s!AmSGGFeCFoVOlBRqn230uGtHC2Xq
https://1drv.ms/u/s!AmSGGFeCFoVOlBVzEMl9hunALB4w

Also here is some stuff Who Crashed Gave me


On Thu 8/10/2017 4:51:55 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\081017-22468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x19 (0x20, 0xFFFF9683D3852710, 0xFFFF9683D3852810, 0xC080004)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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 Thu 8/10/2017 4:51:55 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x19 (0x20, 0xFFFF9683D3852710, 0xFFFF9683D3852810, 0xC080004)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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 8/7/2017 5:30:59 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\080717-22421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C550)
Bugcheck code: 0xA (0xFFFFC881CDEA7071, 0xFF, 0x0, 0xFFFFF8010C609044)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 8/7/2017 5:30:59 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0xB492)
Bugcheck code: 0xA (0xFFFFC881CDEA7071, 0xFF, 0x0, 0xFFFFF8010C609044)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 8/5/2017 3:05:07 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\080517-19828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C550)
Bugcheck code: 0xA (0x0, 0xE, 0x1, 0xFFFFF8039917BB8C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[gardenman]

I ran the memory.dmp file through the debugger and it was full of errors. This is a known problem with the debugger. I edited out most of the errors got the following results: https://pastebin.com/pEsHT6vF

File: MEMORY.DMP (Sat Aug 19 22:14:59 2017)
BugCheck: [CLOCK_WATCHDOG_TIMEOUT (101)] {18, 0, ffff8c01fa2aa180, 6}
Probably caused by: memory_corruption (Process: GameOverlayUI.exe)

Colif, it's unlikely that the drivers list is complete due to the errors.

I can't help you with this. Wait for someone else to reply. Good luck.

 

[Colif]

The results (as gardenman hinted) aren't behaving, you can wait and see if Johnbl can see anything different in them or you can look at posting suggestions on this page and ask on there, as they may be able to extract workable results: https://www.tenforums.com/bsod-crashes-debugging/

we were assuming John would reply, hence no reactions for a week.