Witam
Specyfikacja mojego komputera to :
Intel-Core i56400 2,7GHz
Gtx 970 4GB
Płyta głowna : H110M-K
HyperX DDR4-2133 8GB
Zasilacz Corsair VS Series 550W
Problem z częstymi bluescreenami zaczął się pod koniec września. Występują one głownie podczas grania. Ich podłoże jest różne. Mimo serwisowania i stwierdzeniu przez serwis , że była to wina systemu i ponownej go reinstalacji problem nadal występuję . Próbowałem wszystkiego:
- zaktualizowałem wszystkie sterowniki
- robiłem reinstall windowsa
- robiłem hd tune który wyszedł pozytywnie
Komputer został kupiony na początku sierpnia poprzez Komputronik tak więc był już złożony i gotowy do korzystania. Co byście mi doradzili ? Na Mem Teście wychodzi jakieś 8848 błędów .
Tutaj zamieszczam raport z aplikacji who crushed
Specyfikacja mojego komputera to :
Intel-Core i56400 2,7GHz
Gtx 970 4GB
Płyta głowna : H110M-K
HyperX DDR4-2133 8GB
Zasilacz Corsair VS Series 550W
Problem z częstymi bluescreenami zaczął się pod koniec września. Występują one głownie podczas grania. Ich podłoże jest różne. Mimo serwisowania i stwierdzeniu przez serwis , że była to wina systemu i ponownej go reinstalacji problem nadal występuję . Próbowałem wszystkiego:
- zaktualizowałem wszystkie sterowniki
- robiłem reinstall windowsa
- robiłem hd tune który wyszedł pozytywnie
Komputer został kupiony na początku sierpnia poprzez Komputronik tak więc był już złożony i gotowy do korzystania. Co byście mi doradzili ? Na Mem Teście wychodzi jakieś 8848 błędów .
Tutaj zamieszczam raport z aplikacji who crushed
Spoiler:
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 23.01.2017 00:00:53 your computer crashed
crash dump file: C:\Windows\Minidump\012317-5281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x45608C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803F08CB08C, 0xFFFFD0015D71F868, 0xFFFFD0015D71F080)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 23.01.2017 00:00:53 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: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF803F08CB08C, 0xFFFFD0015D71F868, 0xFFFFD0015D71F080)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread 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 Sun 22.01.2017 01:58:33 your computer crashed
crash dump file: C:\Windows\Minidump\012217-5281-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x7C24)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80131447C24, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
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 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 Sun 22.01.2017 01:52:48 your computer crashed
crash dump file: C:\Windows\Minidump\012217-5609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142970)
Bugcheck code: 0xA (0xFFFFFF00D083C280, 0x2, 0x1, 0xFFFFF803F3367DEF)
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 Sun 22.01.2017 00:43:07 your computer crashed
crash dump file: C:\Windows\Minidump\012217-4953-01.dmp
This was probably caused by the following module: mfefirek.sys (mfefirek+0x4D719)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8015A5BD719, 0xFFFFD00119CDA9E8, 0xFFFFD00119CDA200)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\mfefirek.sys
product: SYSCORE
company: McAfee, Inc.
description: McAfee Core Firewall Engine Driver
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.
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: mfefirek.sys (McAfee Core Firewall Engine Driver, McAfee, Inc.).
Google query: McAfee, Inc. KMODE_EXCEPTION_NOT_HANDLED
Crash dumps are enabled on your computer.
On Mon 23.01.2017 00:00:53 your computer crashed
crash dump file: C:\Windows\Minidump\012317-5281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x45608C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803F08CB08C, 0xFFFFD0015D71F868, 0xFFFFD0015D71F080)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 23.01.2017 00:00:53 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: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF803F08CB08C, 0xFFFFD0015D71F868, 0xFFFFD0015D71F080)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread 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 Sun 22.01.2017 01:58:33 your computer crashed
crash dump file: C:\Windows\Minidump\012217-5281-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x7C24)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80131447C24, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
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 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 Sun 22.01.2017 01:52:48 your computer crashed
crash dump file: C:\Windows\Minidump\012217-5609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142970)
Bugcheck code: 0xA (0xFFFFFF00D083C280, 0x2, 0x1, 0xFFFFF803F3367DEF)
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 Sun 22.01.2017 00:43:07 your computer crashed
crash dump file: C:\Windows\Minidump\012217-4953-01.dmp
This was probably caused by the following module: mfefirek.sys (mfefirek+0x4D719)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8015A5BD719, 0xFFFFD00119CDA9E8, 0xFFFFD00119CDA200)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\mfefirek.sys
product: SYSCORE
company: McAfee, Inc.
description: McAfee Core Firewall Engine Driver
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.
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: mfefirek.sys (McAfee Core Firewall Engine Driver, McAfee, Inc.).
Google query: McAfee, Inc. KMODE_EXCEPTION_NOT_HANDLED
