PROBLEMA BSOD errore irql_not_less_or_equal

Matt975

Nuovo Utente
58
1
salve , è da un paio di giorni che ogni volta che guardo un video a schermo intero dopo pochi minuti compare una schermata blu con questo errore : irql_not_less_or_equal
pensando che l'errore fosse dovuto a dei drivers della scheda video ho provato ad aggiornarli ma il problema continuava a mostrarsi , cosi ho usato DDU per disinstallare i drivers e ho provato a reinstallarli ma non si è risolto niente .
mi potete aiutare a risolvere questo errore ?
 
Ultima modifica:

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 , è da un paio di giorni che ogni volta che guardo un video dopo pochi minuti compare una schermata blu con questo errore : irql_not_less_or_equal
pensando che l'errore fosse dovuto a dei drivers della scheda video ho provato ad aggiornarli ma il problema continuava a mostrarsi , cosi ho usato DDU per disinstallare i drivers e ho provato a reinstallarli ma non si è risolto niente .
mi potete aiutare a risolvere questo errore ?

ciao controlla prima di tutto con whocrashed Resplendence Software - Free Downloads per la ram testala con MEMTEST86 MemTest86 - Offical Site of the x86 Memory Testing Tool ma secondo me è più la ram che altro
 
  • Mi piace
Reazioni: Matt975

Matt975

Nuovo Utente
58
1
ciao controlla prima di tutto con whocrashed Resplendence Software - Free Downloads per la ram testala con MEMTEST86 MemTest86 - Offical Site of the x86 Memory Testing Tool ma secondo me è più la ram che altro

whocrashed mi da :
[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 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 Fri 19/08/2016 03:57:58 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgkrnl.sys[/FONT] (dxgkrnl!TraceDxgkFunctionProfiler+0xA014)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80233369503)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics Kernel
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.


[/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]On Thu 18/08/2016 08:27:06 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081816-17484-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, 0xFFFFF8023976A503)
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 05:17:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081816-17968-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0xEF503)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80036D0E503, 0xFFFFD001B00EA5E8, 0xFFFFD001B00E9E00)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/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 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.


[/FONT]
[FONT=Segoe UI, Arial]On Wed 17/08/2016 20:05:40 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081716-16468-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, 0xFFFFF8034A374503)
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 Wed 17/08/2016 19:00:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081716-18718-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, 0xFFFFF800CAD67503)
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 Wed 17/08/2016 09:23:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081716-25156-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, 0xFFFFF80187962503)
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 Wed 17/08/2016 02:31:20 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081716-51859-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, 0xFFFFF8010F578503)
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]9 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


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.

per
[/FONT]MEMTEST86 devo metterl o su una chiavetta o va ben pure usare daemon tools per la versione iso ?
 

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
whocrashed mi da :
[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 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 Fri 19/08/2016 03:57:58 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgkrnl.sys[/FONT] (dxgkrnl!TraceDxgkFunctionProfiler+0xA014)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80233369503)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics Kernel
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.


[/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]On Thu 18/08/2016 08:27:06 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081816-17484-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, 0xFFFFF8023976A503)
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 05:17:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081816-17968-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0xEF503)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80036D0E503, 0xFFFFD001B00EA5E8, 0xFFFFD001B00E9E00)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/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 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.


[/FONT]
[FONT=Segoe UI, Arial]On Wed 17/08/2016 20:05:40 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081716-16468-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, 0xFFFFF8034A374503)
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 Wed 17/08/2016 19:00:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081716-18718-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, 0xFFFFF800CAD67503)
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 Wed 17/08/2016 09:23:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081716-25156-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, 0xFFFFF80187962503)
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 Wed 17/08/2016 02:31:20 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081716-51859-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, 0xFFFFF8010F578503)
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]9 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


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.

per
[/FONT]MEMTEST86 devo metterl o su una chiavetta o va ben pure usare daemon tools per la versione iso ?

metti la iso su pen o masterizza il dvd devi farlo partire da usb o da cd trattandosi di una live atta a testare la ram... posta anche le caratteristiche del pc compreso di periferiche usb usa anche questo strumento https://msdn.microsoft.com/it-it/library/windows/hardware/ff545448(v=vs.85).aspx#how_to_start_dv di win per controllare i driver
 
Ultima modifica:

Matt975

Nuovo Utente
58
1
metti la iso su pen o masterizza il dvd devi farlo partire da usb o da cd trattandosi di una live atta a testare la ram... posta anche le caratteristiche del pc compreso di periferiche usb usa anche questo strumento https://msdn.microsoft.com/it-it/library/windows/hardware/ff545448(v=vs.85).aspx#how_to_start_dv di win per controllare i driver

non ci sarebbe qualche altro software oltre memtest86 ?
perchè non so come entrare nel bios e selezionare l'usb come boot

ho visto 2 tutorial ma non ci ho capito più di tanto
 
Ultima modifica:

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
non ci sarebbe qualche altro software oltre memtest86 ?
perchè non so come entrare nel bios e selezionare l'usb come boot

ho visto 2 tutorial ma non ci ho capito più di tanto

è abbastanza semplice... o premi F2 o Canc O F11 a seconda della scheda madre... visto che è asrock potrebbe essere F11 per l'accesso all'avvio rapido

oppure

tieni premuto shift in fase di arresto del sistema poi vai in impostazioni avanzate e segui qui http://www.tomshw.it/forum/windows/531527-windows-10-entrare-nel-bios.html#post5006886 ma è abbastanza semplice
 

Matt975

Nuovo Utente
58
1
è abbastanza semplice... o premi F2 o Canc O F11 a seconda della scheda madre... visto che è asrock potrebbe essere F11 per l'accesso all'avvio rapido

oppure

tieni premuto shift in fase di arresto del sistema poi vai in impostazioni avanzate e segui qui http://www.tomshw.it/forum/windows/531527-windows-10-entrare-nel-bios.html#post5006886 ma è abbastanza semplice


ho provato a usare driver verifier , si è riavviato il pc ma non ha dato nulla
una volta messa l'usb come boot ed eseguito il test quando riavvierò il pc dovro scegliere il boot o sceglierà in automatico l'hard disk con windows ?
comunque grazie dell'aiuto che mi stai dando
 

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
ho provato a usare driver verifier , si è riavviato il pc ma non ha dato nulla
una volta messa l'usb come boot ed eseguito il test quando riavvierò il pc dovro scegliere il boot o sceglierà in automatico l'hard disk con windows ?
comunque grazie dell'aiuto che mi stai dando

fallo girare qualche ora una volta terminato spegni togli la chiavetta o cd e fallo partire normalmente
 

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

Matt975

Nuovo Utente
58
1
fallo girare più di qualche ora non è lento ma serve per testare a fondo la ram


giusto perché voglio essere sicuro visto che il pc sara inutilizzabile per diverse ore

il problema della BSOD che mi capita solo quando guardo video a schermo intero e non mentre gioco o faccio altro è causato da problemi della ram ?
 

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
giusto perché voglio essere sicuro visto che il pc sara inutilizzabile per diverse ore

il problema della BSOD che mi capita solo quando guardo video a schermo intero e non mentre gioco o faccio altro è causato da problemi della ram ?

potrebbe come potrebbe essere qualche altra cosa... ma intanto testa la ram a fondo
 

Matt975

Nuovo Utente
58
1
potrebbe come potrebbe essere qualche altra cosa... ma intanto testa la ram a fondo

non riesco ad accedere al bios
nel senso ho letto il manuale della scheda madre per sapere con quale tasto entrare nel bios ma quando accendo il pc la prima schermata che compare è direttamente il caricamento del so .
prima non mi capitava l'ho notato solo di recente
 
  • Mi piace
Reazioni: NikLink

NikLink

Utente Attivo
544
121
In Windows, apri le opzioni di Arresto e tieni premuto Shift mentre clicchi s Riavvia il Sistema.

Il PC ti dirà "Attendi..." e verranno caricate le impostazioni avanzate, tu devi trovare le opzioni quella di nome "Riavvia in UEFI" o simile.
In questo modo Windows ritarda l'avvio per caricare UEFI e dovrai cambiare l'ordine di Boot (non ricordo se puoi aprire direttamente la lista di boot senza cambiare l'ordine di avvio).

Cambia l'ordine e imposta la USB con memtest e lascialo avviare. Dopo, fai lavorare memtest.
Comunque vedendo i crash report, sembra sia proprio la Ram.
Hai già provato a vedere se crasha con un modulo di Ram in più slot?
 

Matt975

Nuovo Utente
58
1
In Windows, apri le opzioni di Arresto e tieni premuto Shift mentre clicchi s Riavvia il Sistema.

Il PC ti dirà "Attendi..." e verranno caricate le impostazioni avanzate, tu devi trovare le opzioni quella di nome "Riavvia in UEFI" o simile.
In questo modo Windows ritarda l'avvio per caricare UEFI e dovrai cambiare l'ordine di Boot (non ricordo se puoi aprire direttamente la lista di boot senza cambiare l'ordine di avvio).

Cambia l'ordine e imposta la USB con memtest e lascialo avviare. Dopo, fai lavorare memtest.
Comunque vedendo i crash report, sembra sia proprio la Ram.
Hai già provato a vedere se crasha con un modulo di Ram in più slot?

no non ho provato a cambiare slot della ram
 

Entra

oppure Accedi utilizzando
Discord Ufficiale Entra ora!

Discussioni Simili