- Oct 28, 2016
- 50
- 0
- 10,530
Hi
m getting alot of IRQL not less or equal BSOD, ive installed who crashed and here are the reports :
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 6/9/2017 6:07:53 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\060917-28296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0xA (0xFFFFC915E20C0802, 0x2, 0x0, 0xFFFFF803D62CFD43)
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 Fri 6/9/2017 6:07:53 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: afd.sys (afd+0x55957)
Bugcheck code: 0xA (0xFFFFC915E20C0802, 0x2, 0x0, 0xFFFFF803D62CFD43)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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 Fri 6/9/2017 5:34:16 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\060917-25437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800829881B1, 0x0, 0xFFFFFFFFFFFFFFFF)
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 Fri 6/9/2017 4:36:26 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\060917-28218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x139 (0x3, 0xFFFFDB80F28DF820, 0xFFFFDB80F28DF778, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 6/9/2017 4:25:44 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\060917-27781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xA (0xFFFF9607298E3FFF, 0x2, 0x0, 0xFFFFF800C63F35E9)
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.
can someone please help this is really getting annoying.
Thanks!!
m getting alot of IRQL not less or equal BSOD, ive installed who crashed and here are the reports :
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 6/9/2017 6:07:53 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\060917-28296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0xA (0xFFFFC915E20C0802, 0x2, 0x0, 0xFFFFF803D62CFD43)
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 Fri 6/9/2017 6:07:53 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: afd.sys (afd+0x55957)
Bugcheck code: 0xA (0xFFFFC915E20C0802, 0x2, 0x0, 0xFFFFF803D62CFD43)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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 Fri 6/9/2017 5:34:16 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\060917-25437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800829881B1, 0x0, 0xFFFFFFFFFFFFFFFF)
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 Fri 6/9/2017 4:36:26 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\060917-28218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x139 (0x3, 0xFFFFDB80F28DF820, 0xFFFFDB80F28DF778, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 6/9/2017 4:25:44 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\060917-27781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xA (0xFFFF9607298E3FFF, 0x2, 0x0, 0xFFFFF800C63F35E9)
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.
can someone please help this is really getting annoying.
Thanks!!
Facebook
Twitter
Instagram