Lexx
New Member
- Messages
- 2
Hi dear Community!
I have planty of Problems with my Laptop or with windows 8.1 Pro and cannot figure it out what it is.
Maybe someone can tell me if it is a Software or Hardware problem. Any help would be great =)
Here are my Dump files.
-Done all Windows Updates
-Done all Software Updates for each driver
-Installed Windows 8.1 (clean) the 3rd time
-Deinstalled bad drivers
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 08.12.2014 09:00:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120814-5546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1A (0x8887, 0xFFFFFA800355C770, 0xFFFFFA800355C740, 0x105)
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 Mon 08.12.2014 08:48:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120814-4906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0xBE (0xFFFFC000704CF084, 0x800000010B553121, 0xFFFFD000C8F0D580, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.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 Sun 07.12.2014 14:56:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120714-4328-01.dmp
This was probably caused by the following module: athwbx.sys (athwbx+0x309948)
Bugcheck code: 0xFC (0xFFFFE001D90E0AF0, 0x80000001D5A009E3, 0xFFFFF800767C33D0, 0x3)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug check description: This indicates that an attempt was made to execute non-executable memory.
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. 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: athwbx.sys .
Google query: athwbx.sys ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
On Sun 07.12.2014 14:17:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120714-4031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x19 (0xD, 0xFFFFC000388D8190, 0xED5C00D8B7C93568, 0xED5C00D8B7CB3568)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 07.12.2014 14:16:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120714-4671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802CA3CF814, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 Mon 08.12.2014 09:00:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120814-5546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1A (0x8887, 0xFFFFFA800355C770, 0xFFFFFA800355C740, 0x105)
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 Mon 08.12.2014 09:00:40 GMT 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: 0x1A (0x8887, 0xFFFFFA800355C770, 0xFFFFFA800355C740, 0x105)
Error: MEMORY_MANAGEMENT
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.
I have planty of Problems with my Laptop or with windows 8.1 Pro and cannot figure it out what it is.
Maybe someone can tell me if it is a Software or Hardware problem. Any help would be great =)
Here are my Dump files.
-Done all Windows Updates
-Done all Software Updates for each driver
-Installed Windows 8.1 (clean) the 3rd time
-Deinstalled bad drivers
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 08.12.2014 09:00:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120814-5546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1A (0x8887, 0xFFFFFA800355C770, 0xFFFFFA800355C740, 0x105)
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 Mon 08.12.2014 08:48:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120814-4906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0xBE (0xFFFFC000704CF084, 0x800000010B553121, 0xFFFFD000C8F0D580, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.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 Sun 07.12.2014 14:56:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120714-4328-01.dmp
This was probably caused by the following module: athwbx.sys (athwbx+0x309948)
Bugcheck code: 0xFC (0xFFFFE001D90E0AF0, 0x80000001D5A009E3, 0xFFFFF800767C33D0, 0x3)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug check description: This indicates that an attempt was made to execute non-executable memory.
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. 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: athwbx.sys .
Google query: athwbx.sys ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
On Sun 07.12.2014 14:17:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120714-4031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x19 (0xD, 0xFFFFC000388D8190, 0xED5C00D8B7C93568, 0xED5C00D8B7CB3568)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 07.12.2014 14:16:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120714-4671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802CA3CF814, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 Mon 08.12.2014 09:00:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120814-5546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1A (0x8887, 0xFFFFFA800355C770, 0xFFFFFA800355C740, 0x105)
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 Mon 08.12.2014 09:00:40 GMT 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: 0x1A (0x8887, 0xFFFFFA800355C770, 0xFFFFFA800355C740, 0x105)
Error: MEMORY_MANAGEMENT
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.
My Computer
System One
-
- OS
- Windows 8.1 Pro 64 bit
- Computer type
- Laptop
- System Manufacturer/Model
- Acer Aspire V3-772G
- CPU
- i7-4702MQ @2,2GHz
- Motherboard
- Acer - Intel Haswell
- Memory
- 8GB RAM
- Graphics Card(s)
- Nvidia GT750m 4GB
- Screen Resolution
- 1900x1080
- Hard Drives
- Samsung SSD Evo 120GB
- Internet Speed
- 125mbit