Colif :
download and run whocrashed;
http://www.resplendence.com/whocrashed
it will look at errors and give a summary - might show cause as well.
Copy/paste results in here.
Thats a start, next follow option one here:
http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD
that creates a file in c/windows/minidumps
copy that file to your documents
upload the copy to a cloud server and share the link here - someone who can read the dumps will figure it out for you
Watchdog error violations are normally CPU related, but i won't guess until i see whocrashed results.
Hi, thank you very much for your answer, I genuinely appreciate it! It took a few days for me to get back into town, but so far I have done a clean install on my video drivers and still got the BSODs after a few hours of usage. So I ran WhoCrashed and here is the result (currently running a malware scan as well just in case):
On Fri 8/5/2016 1:37:19 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080416-8265-01.dmp
This was probably caused by the following module: hal.dll (hal+0x35F1F)
Bugcheck code: 0x124 (0x0, 0xFFFFE0011A8C8028, 0xB0800000, 0x40151)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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 Fri 8/5/2016 1:37:19 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x165151)
Bugcheck code: 0x124 (0x0, 0xFFFFE0011A8C8028, 0xB0800000, 0x40151)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. WHEA_UNCORRECTABLE_ERROR
On Fri 8/5/2016 1:34:29 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080416-9343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80025A3BA32, 0xFFFFD001E9B0CF10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Fri 7/29/2016 5:04:05 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072916-5453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x124 (0x0, 0xFFFFE0019BED5028, 0xB8800000, 0x20F0F)
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 Fri 7/29/2016 1:31:03 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072816-5812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x50 (0xFFFFF8022FDD1220, 0x10, 0xFFFFF8022BDD1220, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Fri 7/29/2016 1:26:23 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072816-5531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFD0012ADEF180, 0x6)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware 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 Fri 7/29/2016 1:24:21 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072816-5203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80272C39A32, 0xFFFFD00132845D40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Fri 7/29/2016 1:23:30 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072816-6062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802B3A99A32, 0xFFFFD00102B928C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Fri 7/29/2016 1:22:19 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072816-6390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6808CF63D80, 0x20000000000000, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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.
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 7/28/2016 1:03:50 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072816-5906-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
Facebook
Twitter
Instagram