PROBLEMA BSOD errore DRIVER_IRQL_NOT_LESS_OR_EQUAL (MijXfilt.sys)

Matt975

Nuovo Utente
58
1
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]
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,407
6,323
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 15 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows11x64pro
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]

disinstalla il driver del joipad della play3 o controlla che MotioninJoy abbia un aggiornamento per win10
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,407
6,323
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 15 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows11x64pro

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,407
6,323
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 15 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows11x64pro
il problema è che il joystick funzionava solo con motioninjoy , sto problema me l'ho dà da quando si è aggiornato windows 10

prova così con revo unistaller rimuovi il programma facendo una disinstallazine moderata che serve per rimuovere file nascosti e chiavi di registro dal sistema e installalo da capo
 

Matt975

Nuovo Utente
58
1
ho provato ma è proprio un driver che causa la schermata blu , ora appena apro motioninjoy e collego il joystick il programma prova a installare i driver ma compare subito il blue screen
 

ZPH

Utente Attivo
519
149
CPU
Intel Core i7 3770K 3.50GHz
Dissipatore
Cooler Master Seidon 240M
Scheda Madre
MSI Z77 MPower
HDD
SSD Samsung 840 EVO 500GB (OS), 2x HDD Seagate ST2000DM001 2TB (Dati)
RAM
Corsair Vengeance 16GB (4x4) DDR3
GPU
MSI GeForce GTX 970
Monitor
Samsung T24D390 24" FULLHD, LG 43UH750V 43" 4K HDR
PSU
CoolerMaster Silent Pro M2 720W
Case
CM Storm Scout II
Periferiche
Back-UPS APC 1400, Stampante HP Photosmart B110a, Altoparlanti Creative SBS 380 2.1, 2x HDD WD Elements 2TB (Backup), Controller PS3
OS
Windows 10 Pro 64bit
ho provato con altri programmi ma non va nessuno
Ho avuto lo stesso problema tempo fa.
Fai così: rimuovi il driver e motioninjoy e verifica che in C:\Windows\System32\Drivers non ci sia più il file MijXfilt.sys
Per continuare ad usare il controller, anche senza fili, segui questa guida. Con questo programma non avrai più bisogno di aprire niente, basta premere il tasto PS e il controller si collegherà da solo al PC e non riceverai più bluescreens.
 

Matt975

Nuovo Utente
58
1
Ho avuto lo stesso problema tempo fa.
Fai così: rimuovi il driver e motioninjoy e verifica che in C:\Windows\System32\Drivers non ci sia più il file MijXfilt.sys
Per continuare ad usare il controller, anche senza fili, segui questa guida. Con questo programma non avrai più bisogno di aprire niente, basta premere il tasto PS e il controller si collegherà da solo al PC e non riceverai più bluescreens.

si puo fare pure via usb senza il bluetooth del controller ?

lo sto scaricando ma devo scaricare solo il setup o anche il codice sorgente formato zip ?
 
Ultima modifica:

ZPH

Utente Attivo
519
149
CPU
Intel Core i7 3770K 3.50GHz
Dissipatore
Cooler Master Seidon 240M
Scheda Madre
MSI Z77 MPower
HDD
SSD Samsung 840 EVO 500GB (OS), 2x HDD Seagate ST2000DM001 2TB (Dati)
RAM
Corsair Vengeance 16GB (4x4) DDR3
GPU
MSI GeForce GTX 970
Monitor
Samsung T24D390 24" FULLHD, LG 43UH750V 43" 4K HDR
PSU
CoolerMaster Silent Pro M2 720W
Case
CM Storm Scout II
Periferiche
Back-UPS APC 1400, Stampante HP Photosmart B110a, Altoparlanti Creative SBS 380 2.1, 2x HDD WD Elements 2TB (Backup), Controller PS3
OS
Windows 10 Pro 64bit
si puo fare pure via usb senza il bluetooth del controller ?

lo sto scaricando ma devo scaricare solo il setup o anche il codice sorgente formato zip ?

Si, funziona anche col cavo.
Scarica solo il file .exe
 

Matt975

Nuovo Utente
58
1
Si, funziona anche col cavo.
Scarica solo il file .exe

ci ho provato e durante l'installazione dei driver mi ha chiesto di installare scarlet.crush productions e poi è crashato il pc
riporto analisi di whocrashed :

Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 11/09/2016 15:33:56 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\091116-27218-01.dmp
This was probably caused by the following module: scpvbus.sys (ScpVBus+0xB174)
Bugcheck code: 0xC9 (0x21F, 0xFFFFF8017F38B174, 0xFFFFCF819E002DC0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\WINDOWS\system32\drivers\scpvbus.sys
product: Scp Virtual Bus Driver
company: Scarlet.Crush Productions
description: Scp Virtual Bus Driver
Bug check description: This is the bug check code for all Driver Verifier
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: scpvbus.sys (Scp Virtual Bus Driver, Scarlet.Crush Productions).
Google query: Scarlet.Crush Productions DRIVER_VERIFIER_IOMANAGER_VIOLATION



On Sun 11/09/2016 15:33:56 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: scpvbus.sys (0xFFFFF8017F38B174)
Bugcheck code: 0xC9 (0x21F, 0xFFFFF8017F38B174, 0xFFFFCF819E002DC0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\WINDOWS\system32\drivers\scpvbus.sys
product: Scp Virtual Bus Driver
company: Scarlet.Crush Productions
description: Scp Virtual Bus Driver
Bug check description: This is the bug check code for all Driver Verifier
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: scpvbus.sys (Scp Virtual Bus Driver, Scarlet.Crush Productions).
Google query: Scarlet.Crush Productions DRIVER_VERIFIER_IOMANAGER_VIOLATION



On Sun 11/09/2016 15:10:41 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\091116-26250-01.dmp
This was probably caused by the following module: scpvbus.sys (ScpVBus+0xB174)
Bugcheck code: 0xC9 (0x21F, 0xFFFFF80168B2B174, 0xFFFFCF8163924DC0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\WINDOWS\system32\drivers\scpvbus.sys
product: Scp Virtual Bus Driver
company: Scarlet.Crush Productions
description: Scp Virtual Bus Driver
Bug check description: This is the bug check code for all Driver Verifier
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: scpvbus.sys (Scp Virtual Bus Driver, Scarlet.Crush Productions).
Google query: Scarlet.Crush Productions DRIVER_VERIFIER_IOMANAGER_VIOLATION
 

ZPH

Utente Attivo
519
149
CPU
Intel Core i7 3770K 3.50GHz
Dissipatore
Cooler Master Seidon 240M
Scheda Madre
MSI Z77 MPower
HDD
SSD Samsung 840 EVO 500GB (OS), 2x HDD Seagate ST2000DM001 2TB (Dati)
RAM
Corsair Vengeance 16GB (4x4) DDR3
GPU
MSI GeForce GTX 970
Monitor
Samsung T24D390 24" FULLHD, LG 43UH750V 43" 4K HDR
PSU
CoolerMaster Silent Pro M2 720W
Case
CM Storm Scout II
Periferiche
Back-UPS APC 1400, Stampante HP Photosmart B110a, Altoparlanti Creative SBS 380 2.1, 2x HDD WD Elements 2TB (Backup), Controller PS3
OS
Windows 10 Pro 64bit
ci ho provato e durante l'installazione dei driver mi ha chiesto di installare scarlet.crush productions e poi è crashato il pc
riporto analisi di whocrashed :

Hai collegato il controller alla porta USB prima?
Prova anche a disattivare l'antivirus.
Ah, ovviamente devi usare sempre la stessa porta USB. Se decidessi di collegare il controller ad un altra porta dovrai rifare l'installazione del driver.
 

Matt975

Nuovo Utente
58
1
Hai collegato il controller alla porta USB prima?
Prova anche a disattivare l'antivirus.
Ah, ovviamente devi usare sempre la stessa porta USB. Se decidessi di collegare il controller ad un altra porta dovrai rifare l'installazione del driver.


si uso sempre la stessa porta usb e antivirus non c'entra pero crasha come con motioninjoy ma con errore diverso
 

ZPH

Utente Attivo
519
149
CPU
Intel Core i7 3770K 3.50GHz
Dissipatore
Cooler Master Seidon 240M
Scheda Madre
MSI Z77 MPower
HDD
SSD Samsung 840 EVO 500GB (OS), 2x HDD Seagate ST2000DM001 2TB (Dati)
RAM
Corsair Vengeance 16GB (4x4) DDR3
GPU
MSI GeForce GTX 970
Monitor
Samsung T24D390 24" FULLHD, LG 43UH750V 43" 4K HDR
PSU
CoolerMaster Silent Pro M2 720W
Case
CM Storm Scout II
Periferiche
Back-UPS APC 1400, Stampante HP Photosmart B110a, Altoparlanti Creative SBS 380 2.1, 2x HDD WD Elements 2TB (Backup), Controller PS3
OS
Windows 10 Pro 64bit
si uso sempre la stessa porta usb e antivirus non c'entra pero crasha come con motioninjoy ma con errore diverso

Quindi, dopo aver spuntato la prima e la terza opzione e aver selezionato il controller nel menù a tendina e cliccato su Install, il PC crasha se installi quel scarlet.crush? Prova a non installarlo.
Ora non ricordo di preciso come ho fatto la prima volta ma non ricordo nessun scarlet.crush. Appena posso provo su un altro PC e vedo se crasha anche a me.
 

Entra

oppure Accedi utilizzando
Discord Ufficiale Entra ora!

Discussioni Simili