C'est mon 1er post sur un forum!! Mais là je suis vraiment bloquée.
Après une bonne semaine d'écran bleu, de blocage du PC et de recherche sur pas mal de forum, je sollicite votre aide.
J'ai donc ce soucis d'écran bleu avec
driver_irql_not_less_or equal.....
check to make sure any....
If problem continu... (blablabla)
Mon PC doit avoir 4 ans.
C'est un HP intel pentium E2220
Carte graphique: nvidia GeForce 9300
carte réseau: nvidia nForce 10/100/1000 Mbps Ethernet
Et je suis sous vista edition familiale basique
J'ai utilisé Whocrashed et voici le résultat:
- Code: Tout sélectionner
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 12/06/2012 17:49:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061212-06.dmp
This was probably caused by the following module: sptd.sys (sptd+0x11BA0)
Bugcheck code: 0xFE (0x5, 0xFFFFFFFF874E50E0, 0x10DE0AA7, 0xFFFFFFFF87ADAB24)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\sptd.sys
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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: sptd.sys .
Google query: sptd.sys BUGCODE_USB_DRIVER
On Tue 12/06/2012 17:49:38 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT!USBPORT_RegisterUSBPortDriver+0xBA09)
Bugcheck code: 0xFE (0x5, 0xFFFFFFFF874E50E0, 0x10DE0AA7, 0xFFFFFFFF87ADAB24)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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.
On Tue 12/06/2012 16:33:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061212-05.dmp
This was probably caused by the following module: sptd.sys (sptd+0x11BA0)
Bugcheck code: 0xD1 (0x28, 0x2, 0x1, 0xFFFFFFFF8A157A06)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\sptd.sys
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: sptd.sys .
Google query: sptd.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Tue 12/06/2012 16:02:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061212-04.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF)
Bugcheck code: 0x4E (0x9A, 0x5CD08, 0x2, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 which cannot be identified at this time.
On Tue 12/06/2012 15:20:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061212-03.dmp
This was probably caused by the following module: nvmfdx32.sys (nvmfdx32+0x3D35F)
Bugcheck code: 0xA (0xFFFFFFFF8D875018, 0x2, 0x1, 0xFFFFFFFF82DBEEDE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvmfdx32.sys
product: NVIDIA Networking Driver
company: NVIDIA Corporation
description: NVIDIA MCP Networking Function Driver.
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.
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: nvmfdx32.sys (NVIDIA MCP Networking Function Driver., NVIDIA Corporation).
Google query: nvmfdx32.sys NVIDIA Corporation IRQL_NOT_LESS_OR_EQUAL
On Tue 12/06/2012 13:24:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061212-02.dmp
This was probably caused by the following module: fileinfo.sys (fileinfo+0xA382)
Bugcheck code: 0x18 (0xFFFFFFFF84DC3DB0, 0xFFFFFFFF85977658, 0x2, 0xFFFFFFFFFFFFFFFF)
Error: REFERENCE_BY_POINTER
file path: C:\Windows\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 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.
On Tue 12/06/2012 08:33:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061212-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x24A7D0)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82C577D0, 0xFFFFFFFF81359830, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program 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 which cannot be identified at this time.
On Mon 11/06/2012 17:45:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061112-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x98339)
Bugcheck code: 0xFC (0xFFFFFFFFB11A7CF8, 0x1D316963, 0xFFFFFFFFB11A7B94, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 11/06/2012 07:23:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061112-01.dmp
This was probably caused by the following module: sptd.sys (sptd+0x11BA0)
Bugcheck code: 0xA (0x54, 0x1B, 0x1, 0xFFFFFFFF82A09FE9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\sptd.sys
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.
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: sptd.sys .
Google query: sptd.sys IRQL_NOT_LESS_OR_EQUAL
On Sun 10/06/2012 10:17:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061012-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x17B1)
Bugcheck code: 0xC2 (0x99, 0xFFFFFFFFAF1650C8, 0x0, 0x0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that the current thread is making a bad pool request.
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.
On Sat 09/06/2012 17:52:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini060912-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0xBA5A)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBBD3FFB0, 0xFFFFFFFFB078B914, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that a kernel-mode program 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.
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 08/06/2012 06:45:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini060812-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x11A064)
Bugcheck code: 0xD1 (0xC896, 0x9, 0x1, 0xFFFFFFFF8E120064)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 180.70
company: NVIDIA Corporation
description: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 180.70
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: nvlddmkm.sys (NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 180.70 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Wed 16/05/2012 12:36:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini051612-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x14CE)
Bugcheck code: 0xC2 (0x7, 0x110B, 0x0, 0xFFFFFFFF8546E100)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that the current thread is making a bad pool request.
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
--------------------------------------------------------------------------------
13 crash dumps have been found and analyzed. 4 third party drivers have 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:
nvlddmkm.sys (NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 180.70 , NVIDIA Corporation)
aswsp.sys (avast! self protection module, AVAST Software)
nvmfdx32.sys (NVIDIA MCP Networking Function Driver., NVIDIA Corporation)
sptd.sys
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.
Vu la taille du résultat ça m'inquiète!!!!
Je pense avoir compris qu'il y a déjà un pb avec ma carte graphique, les drivers, les MAJ ??!!!
Je suis toute petite dans le monde informatique en me dépannant grâce aux forum!
J'ai également utilisé "ma config.com" pour connaitre la composition mais c'est pareil là c'est le flou total.
Je ne sais plus quoi faire!!!!
Merci de m'avoir lu et j'espère que qq'1 pourra m'aider.
c'est que probablement la Ram est Ok
