PROBLEMA windows 7: blue screen driver_irql_not_less_or_equal

Pubblicità
Stato
Discussione chiusa ad ulteriori risposte.
Settedifiori

Settedifiori

Nuovo Utente
Messaggi
24
Reazioni
1
Punteggio
25
Salve, da un po' di giorni mi è capitato ( 4 volte ) che Windows si arresta con una blue screen driver_irql_not_less_or_equal ..... come potrei risolvere? un paio di settimane fa ho cambiato alimentatore (antec 520m) e scheda video (gigabyte 660 oc) montata su una msi h55m-e33 con intel i3 530 e 8 gb di ram dd3 1033mhz la blue screen mi capita mentre sto su internet o su team speack 3 ma mai in gaming.... ho un paio di domande, il problema è dato da 2 driver che vanno in conflitto o sbaglio? mi devo preoccupare o il problema è risolvibile? penso che non sia un virus visto che uso Kav cmq farò una scansione per sicurezza... grazie per le risposte
 
System Information (local)

computer name:
EMPIRE-PC
windows version: Windows 7 Service Pack 1, 6.1, build:
7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU
530 @ 2.93GHz Intel586, level: 6
4 logical processors, active mask:
15
RAM: 8513511424 total
VM: 2147352576, free:
1878953984



[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 06/09/2013 14:26:06 GMT your computer crashed
crash dump file:
C:\Windows\Minidump\090613-21075-01.dmp
This was probably caused by the
following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0xD1
(0xC00C0001, 0x2, 0x8, 0xC00C0001)
Error: [FONT=Segoe UI, Arial]DRIVER_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 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.
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 06/09/2013 14:26:06 GMT your computer crashed
crash dump file:
C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]klim6.sys[/FONT] (klim6+0x2889)
Bugcheck code: 0xD1
(0xC00C0001, 0x2, 0x8, 0xC00C0001)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path:
C:\Windows\system32\drivers\klim6.sys
product: [FONT=Segoe UI, Arial]Kaspersky Anti-Virus[/FONT]
company: [FONT=Segoe UI, Arial]Kaspersky
Lab ZAO[/FONT]
description: Kaspersky Lab Intermediate Network
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: klim6.sys (Kaspersky Lab Intermediate Network Driver,
Kaspersky Lab ZAO).
Google query: [FONT=Segoe UI, Arial]Kaspersky Lab ZAO
DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Thu 05/09/2013 18:54:12 GMT
your computer crashed
crash dump file:
C:\Windows\Minidump\090513-24882-01.dmp
This was probably caused by the
following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0xD1 (0x0,
0x2, 0x8, 0x0)
Error: [FONT=Segoe UI, Arial]DRIVER_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 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.
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]
Conclusion
[/FONT]
[FONT=Segoe UI, Arial]3 crash dumps
have been found and analyzed. 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]klim6.sys (Kaspersky Lab Intermediate Network Driver, Kaspersky
Lab ZAO)[/FONT]

If no updates for these drivers are available, try
searching with Google on the names of these drivers in combination the errors
that have been reported for these drivers and include the brand and model name
of your computer as well in the query. This often yields interesting results
from discussions from 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 actually 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]
 
è l'antivirus come puoi vedere...aggiornalo, ma non le definizioni proprio la versione del programma.
 
cavolo, l'ho reinstallato un mese fa è Kav 13 unltima versione gli aggiornamenti se li fa da solo quindi è sempre aggiornato...
 
ok, sorry non avevo visto che era disponibile la 2014 ora cambio e vedo... il bello è che dal 2011 uso kav ma non mi aveva mai dato problemi
 
ok, installato, una volta disinstallato il 2013 ho controllato se aveva disinstallato il file klim6.sys e non c'era però l'ho ritrovato dopo aver installato il 2014 vediamo che succede :D
 
Stato
Discussione chiusa ad ulteriori risposte.
Pubblicità
Pubblicità
Indietro
Top