JustPaste.it

Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sat 2019-09-07 14:09:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090719-13322-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4097A)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF9E224CAC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Sat 2019-09-07 14:09:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrpamp.exe (nt!RtlAppendUnicodeToString+0x46E)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF9E224CAC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 2019-09-07 11:41:20 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090719-13026-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xE2DF0)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFFFFF807C5120, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntkrnlpa.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 can be caused by non-responding hardware or by a overheated CPU (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 Sat 2019-09-07 11:22:39 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090719-15724-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8B3BD)
Bugcheck code: 0xBE (0xFFFFFFFF907C003A, 0x23E3F101, 0xFFFFFFFF807E3CA8, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Sat 2019-09-07 10:57:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090719-12355-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xE2DF0)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFFFFF807C5120, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntkrnlpa.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 can be caused by non-responding hardware or by a overheated CPU (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 2019-09-06 22:25:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090619-12921-01.dmp
This was probably caused by the following module: amdk8.sys (amdk8+0x1BB6)
Bugcheck code: 0x101 (0x60, 0x0, 0xFFFFFFFF807C4120, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\drivers\amdk8.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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 can be caused by non-responding hardware or by a overheated CPU (thermal issue).
The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.



On Thu 2019-09-05 21:11:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090519-13875-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8B3BD)
Bugcheck code: 0x50 (0xFFFFFFFF83BD500C, 0x0, 0xFFFFFFFF82E66352, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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 Tue 2019-09-03 17:44:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090319-14750-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0xFC (0x40000, 0xFFFFFFFF9FA18E4F, 0xFFFFFFFF807E2B84, 0x0)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
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: hardware.sys .
Google query: hardware.sys ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY



On Tue 2019-09-03 17:24:43 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090319-34562-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x46C67)
Bugcheck code: 0xD1 (0x2C38EB7, 0x2, 0x8, 0x2C38EB7)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 2019-08-28 11:32:42 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\082819-21125-01.dmp
This was probably caused by the following module: acpi.sys (ACPI+0xDD6F)
Bugcheck code: 0xA (0xFFFFFFFFBBE00018, 0x0, 0x0, 0xFFFFFFFF82CC7DC5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\acpi.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Sterownik ACPI dla systemu NT
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a 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.





Conclusion



On your computer a total of 15 crash dumps have been found. Only 10 have been analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

hardware.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.