BSOD (driver) irql not less or equal

BSOD (driver) irql not less or equal - Win 7 - Windows & Software

Marsh Posté le 06-06-2013 à 13:56:51    

Bonjour,
 
Depuis que j'ai réinstallé mon pc la semaine dernière j'ai des BSOD complètement aléatoires.
 
J'ai cherché sur les internettes une solution à mon problème mais premièrement les rapports de crash sont différents de l'un à l'autre (ciblant chacun un problème différent) et deuxièmement les solutions sont diverses et variées et ne me concernent pas forcément.
 
J'en viens donc faire appel à votre aide.
 
Voici les rapports de crash via Whocrashed.
 

Citation :

On Thu 06/06/2013 11:41:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060613-9796-01.dmp
This was probably caused by the following module: em008_64.dat (0xFFFFFA800B4BEB40)  
Bugcheck code: 0xD1 (0xFFFFF8810CDB6A8C, 0x2, 0x0, 0xFFFFFA800B4BEB40)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Program Files\ESET\ESET Smart Security\em008_64.dat
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: em008_64.dat .  
Google query: em008_64.dat DRIVER_IRQL_NOT_LESS_OR_EQUAL
 
 
 
On Thu 06/06/2013 11:41:01 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: em008_64.dat (em008_64+0x12B40)  
Bugcheck code: 0xD1 (0xFFFFF8810CDB6A8C, 0x2, 0x0, 0xFFFFFA800B4BEB40)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Program Files\ESET\ESET Smart Security\em008_64.dat
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: em008_64.dat .  
Google query: em008_64.dat DRIVER_IRQL_NOT_LESS_OR_EQUAL
 
 
 
On Tue 04/06/2013 18:34:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060413-10888-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)  
Bugcheck code: 0xA (0xFFFFF881036FD710, 0x2, 0x1, 0xFFFFF80002C774B3)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Tue 04/06/2013 13:53:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060413-9578-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)  
Bugcheck code: 0x119 (0x7000000, 0xFFFFFA800AD4A410, 0xFFFFFA800B2F8010, 0xFFFFFA800AE79E20)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.  
 
 
 
On Tue 04/06/2013 09:18:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060413-9640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)  
Bugcheck code: 0x1A (0x41287, 0x4A00003E, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Thu 30/05/2013 11:42:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053013-9547-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5788)  
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88004C74428, 0xFFFFF88004C73C90, 0xFFFFF88001AD42FA)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.  
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.

 
 
Comme vous le voyez à quasiment chaque rapport la "source" est différente, je sais pas trop où donner de la tête.
 
Merci à vous!

Reply

Marsh Posté le 06-06-2013 à 13:56:51   

Reply

Marsh Posté le 06-06-2013 à 23:02:50    

Plantage aléatoires ?
Fait un test de ta mémoire avec Memtest+


---------------
Liberkey, colection d'utilitaires sur clef USB / Silverstone DS380 - Mini tour ITX 8 baies Hot-swap 3.5"
Reply

Sujets relatifs:

Leave a Replay

Make sure you enter the(*)required information where indicate.HTML code is not allowed