salve
quando collego il joystick della ps3 al pc mi compare una schermata blu con questo errore : DRIVER_IRQL_NOT_LESS_OR_EQUAL (MijXfilt.sys)
prima non mi capitava e ora tutto a un tratto mi capita questa cosa non so cosa fare , ho provato ad aggiornare i driver ma niente
potete aiutarmi a risolvere , grazie
- - - Updated - - -
allego analisi di whocrashed
[FONT=Segoe UI, Arial]System Information (local)
[/FONT]
[FONT=Segoe UI, Arial]Computer name: DESKTOP-6HNLPOG
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: ASRock, Z170 Pro4
CPU: GenuineIntel Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8537522176 bytes total
[/FONT]
[FONT=Segoe UI, Arial]
Crash Dump Analysis
[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\WINDOWS\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Tue 23/08/2016 11:38:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082316-21750-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]mijxfilt.sys[/FONT] (MijXfilt+0x1B638)
Bugcheck code: 0xD1 (0xFFFFF8010755B638, 0x2, 0x8, 0xFFFFF8010755B638)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\drivers\mijxfilt.sys
product: [FONT=Segoe UI, Arial]MotioninJoy DS3 driver[/FONT]
company: [FONT=Segoe UI, Arial]MotioninJoy[/FONT]
description: MotioninJoy DS3 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: mijxfilt.sys (MotioninJoy DS3 driver, MotioninJoy).
Google query: [FONT=Segoe UI, Arial]MotioninJoy DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
[/FONT]
[FONT=Segoe UI, Arial]On Tue 23/08/2016 11:38:01 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]mijxfilt.sys[/FONT] (MijXfilt+0x1B638)
Bugcheck code: 0xD1 (0xFFFFF8010755B638, 0x2, 0x8, 0xFFFFF8010755B638)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\drivers\mijxfilt.sys
product: [FONT=Segoe UI, Arial]MotioninJoy DS3 driver[/FONT]
company: [FONT=Segoe UI, Arial]MotioninJoy[/FONT]
description: MotioninJoy DS3 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: mijxfilt.sys (MotioninJoy DS3 driver, MotioninJoy).
Google query: [FONT=Segoe UI, Arial]MotioninJoy DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
[/FONT]
[FONT=Segoe UI, Arial]On Tue 23/08/2016 11:02:27 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082316-25531-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]mijxfilt.sys[/FONT] (MijXfilt+0x1B638)
Bugcheck code: 0xD1 (0xFFFFF800A79CB638, 0x2, 0x8, 0xFFFFF800A79CB638)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\drivers\mijxfilt.sys
product: [FONT=Segoe UI, Arial]MotioninJoy DS3 driver[/FONT]
company: [FONT=Segoe UI, Arial]MotioninJoy[/FONT]
description: MotioninJoy DS3 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: mijxfilt.sys (MotioninJoy DS3 driver, MotioninJoy).
Google query: [FONT=Segoe UI, Arial]MotioninJoy DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
[/FONT]
[FONT=Segoe UI, Arial]On Tue 23/08/2016 10:59:14 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082316-22375-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]mijxfilt.sys[/FONT] (MijXfilt+0x1B638)
Bugcheck code: 0xD1 (0xFFFFF8007130B638, 0x2, 0x8, 0xFFFFF8007130B638)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\drivers\mijxfilt.sys
product: [FONT=Segoe UI, Arial]MotioninJoy DS3 driver[/FONT]
company: [FONT=Segoe UI, Arial]MotioninJoy[/FONT]
description: MotioninJoy DS3 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: mijxfilt.sys (MotioninJoy DS3 driver, MotioninJoy).
Google query: [FONT=Segoe UI, Arial]MotioninJoy DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
[/FONT]
[FONT=Segoe UI, Arial]On Mon 22/08/2016 12:21:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082216-19703-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x142940)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF801400F0503)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]
[FONT=Segoe UI, Arial]On Sun 21/08/2016 08:33:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082116-22015-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x142940)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF8028E17F503)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]
[FONT=Segoe UI, Arial]On Sat 20/08/2016 19:34:08 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082016-21968-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x142940)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF8008F973503)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]
[FONT=Segoe UI, Arial]On Sat 20/08/2016 05:55:45 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082016-20921-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x142940)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF8002BB05503)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]
[FONT=Segoe UI, Arial]On Fri 19/08/2016 03:57:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081916-20500-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x142940)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80233369503)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]
[FONT=Segoe UI, Arial]On Thu 18/08/2016 20:06:06 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081816-18890-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x142940)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF801ADD7E503)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]
Conclusion
[/FONT]
[FONT=Segoe UI, Arial]16 crash dumps have been found and analyzed. Only 10 are included in this report. 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:
[FONT=Segoe UI, Arial]mijxfilt.sys (MotioninJoy DS3 driver, MotioninJoy)[/FONT]
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.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
[/FONT]
quando collego il joystick della ps3 al pc mi compare una schermata blu con questo errore : DRIVER_IRQL_NOT_LESS_OR_EQUAL (MijXfilt.sys)
prima non mi capitava e ora tutto a un tratto mi capita questa cosa non so cosa fare , ho provato ad aggiornare i driver ma niente
potete aiutarmi a risolvere , grazie
- - - Updated - - -
allego analisi di whocrashed
[FONT=Segoe UI, Arial]System Information (local)
[/FONT]
[FONT=Segoe UI, Arial]Computer name: DESKTOP-6HNLPOG
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: ASRock, Z170 Pro4
CPU: GenuineIntel Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8537522176 bytes total
[/FONT]
[FONT=Segoe UI, Arial]
Crash Dump Analysis
[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\WINDOWS\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Tue 23/08/2016 11:38:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082316-21750-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]mijxfilt.sys[/FONT] (MijXfilt+0x1B638)
Bugcheck code: 0xD1 (0xFFFFF8010755B638, 0x2, 0x8, 0xFFFFF8010755B638)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\drivers\mijxfilt.sys
product: [FONT=Segoe UI, Arial]MotioninJoy DS3 driver[/FONT]
company: [FONT=Segoe UI, Arial]MotioninJoy[/FONT]
description: MotioninJoy DS3 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: mijxfilt.sys (MotioninJoy DS3 driver, MotioninJoy).
Google query: [FONT=Segoe UI, Arial]MotioninJoy DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
[/FONT]
[FONT=Segoe UI, Arial]On Tue 23/08/2016 11:38:01 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]mijxfilt.sys[/FONT] (MijXfilt+0x1B638)
Bugcheck code: 0xD1 (0xFFFFF8010755B638, 0x2, 0x8, 0xFFFFF8010755B638)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\drivers\mijxfilt.sys
product: [FONT=Segoe UI, Arial]MotioninJoy DS3 driver[/FONT]
company: [FONT=Segoe UI, Arial]MotioninJoy[/FONT]
description: MotioninJoy DS3 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: mijxfilt.sys (MotioninJoy DS3 driver, MotioninJoy).
Google query: [FONT=Segoe UI, Arial]MotioninJoy DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
[/FONT]
[FONT=Segoe UI, Arial]On Tue 23/08/2016 11:02:27 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082316-25531-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]mijxfilt.sys[/FONT] (MijXfilt+0x1B638)
Bugcheck code: 0xD1 (0xFFFFF800A79CB638, 0x2, 0x8, 0xFFFFF800A79CB638)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\drivers\mijxfilt.sys
product: [FONT=Segoe UI, Arial]MotioninJoy DS3 driver[/FONT]
company: [FONT=Segoe UI, Arial]MotioninJoy[/FONT]
description: MotioninJoy DS3 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: mijxfilt.sys (MotioninJoy DS3 driver, MotioninJoy).
Google query: [FONT=Segoe UI, Arial]MotioninJoy DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
[/FONT]
[FONT=Segoe UI, Arial]On Tue 23/08/2016 10:59:14 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082316-22375-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]mijxfilt.sys[/FONT] (MijXfilt+0x1B638)
Bugcheck code: 0xD1 (0xFFFFF8007130B638, 0x2, 0x8, 0xFFFFF8007130B638)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\drivers\mijxfilt.sys
product: [FONT=Segoe UI, Arial]MotioninJoy DS3 driver[/FONT]
company: [FONT=Segoe UI, Arial]MotioninJoy[/FONT]
description: MotioninJoy DS3 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: mijxfilt.sys (MotioninJoy DS3 driver, MotioninJoy).
Google query: [FONT=Segoe UI, Arial]MotioninJoy DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
[/FONT]
[FONT=Segoe UI, Arial]On Mon 22/08/2016 12:21:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082216-19703-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x142940)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF801400F0503)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]
[FONT=Segoe UI, Arial]On Sun 21/08/2016 08:33:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082116-22015-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x142940)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF8028E17F503)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]
[FONT=Segoe UI, Arial]On Sat 20/08/2016 19:34:08 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082016-21968-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x142940)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF8008F973503)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]
[FONT=Segoe UI, Arial]On Sat 20/08/2016 05:55:45 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082016-20921-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x142940)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF8002BB05503)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]
[FONT=Segoe UI, Arial]On Fri 19/08/2016 03:57:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081916-20500-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x142940)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80233369503)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]
[FONT=Segoe UI, Arial]On Thu 18/08/2016 20:06:06 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081816-18890-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x142940)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF801ADD7E503)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]
Conclusion
[/FONT]
[FONT=Segoe UI, Arial]16 crash dumps have been found and analyzed. Only 10 are included in this report. 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:
[FONT=Segoe UI, Arial]mijxfilt.sys (MotioninJoy DS3 driver, MotioninJoy)[/FONT]
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.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
[/FONT]