Irql not less or equal

Fermé
martine95 Messages postés 42 Date d'inscription dimanche 27 avril 2008 Statut Membre Dernière intervention 23 janvier 2011 - 23 janv. 2011 à 10:20
Bonjour,
bjr depuis ce matin j ai ce message(voir ci dessus titre)avec ecran bleu j ai un ordinateur portable hp sous windows 7 64 bits je n ai plus de fonctions meme en mode sans echec et l ecran bleu me met des msg differents avec
stopx0000000a
ou 11
ou 2
ou 1
je ne comprends rien la seule chose que j ai fait hier c est que ja i desactive le partage d ordi entre celui de ma fille et le mien c est tout
es ce un virus ec se que je vais perdre mes donnees il n a que deux ans je suis ecoeuree!!!!merci de votre aide precieuse
j ai fait un zhpdiag
voir sur site https://www.cjoint.com/?0bqxeudjelp et aussi verifie avec whocrashed

windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU P7450 @ 2.13GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4260560896 total
VM: 2147352576, free: 1989844992



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 23/01/2011 08:53:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012311-45427-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x6F8, 0xFFFFF80002E5E0D2)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 23/01/2011 08:53:19 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x6F8, 0xFFFFF80002E5E0D2)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 23/01/2011 08:51:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012311-45552-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x7FF, 0x2, 0x0, 0xFFFFF80002EAF436)
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 which cannot be identified at this time.


On Sun 23/01/2011 08:39:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012311-47315-01.dmp
This was probably caused by the following module: msrpc.sys (msrpc+0x1616)
Bugcheck code: 0xF7 (0x2B990CED4620, 0x2B992DDFA232, 0xFFFFD466D2205DCD, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\Windows\system32\drivers\msrpc.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Remote Procedure Call Provider
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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 which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

4 crash dumps have been found and analyzed.
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.
merc




merci de votre