Bonsoir,
voilà sa va faire 1mois que j'ai installé w7 sur mon pc et j'ai de + en + de crash (écran bleu) et encore plus depuis que j'ai installé just cause 2 (un jeux vidéo) qui me prend pas mal de ressource (demande 3go de ram en config max.), j'ai testé ma mémoire avec le diagnostic Windows et avec memtest rien trouvé du coté de la mémoire (je pense) et sa m'arrive le plus souvent quand je joue.
je joue en mode fenetre, qui bouffe plus de RAM je crois peut etre que sa a une influence.
Ma config est :
Intel core 2 duo E8500 3,16 GHZ
2 GO DDR2
GE force 260 GTX - 895 DDR3
Windows 7 pro 32 bits
Est ce que sa pourrait venir de w7 ? car j'ai installé les dernier driver de la carte graphique. de plus je ne pense pas que sa vienne de la memoire vive car j'ai tester le jeux avec plusieurs autre application (film, jeux, internet ...etc. SIMILTANEMENT)
PROBLEME w7 et ecran bleu.
-
grimpeur
Re: PROBLEME w7 et ecran bleu.
Bonjour beubeu
sur jeuxvideo.com ils donnent ceci
Configuration minimale requise :
Windows Vista/Windows 7
Pentium D 3GHz/Athlon 64 X2 4200
GeForce 8800/Radeon HD 2600 Pro (256 Mo compatible DirectX 10)
2 Go de RAM
10 Go de libre sur le DD
Configuration recommandée :
Windows Vista/Windows 7
Core 2 Duo 2,6 GHz/Phenom X3 2,4 GHz
GeForce GTS 250/Radeon HD 5750 (512 Mo compatible DirectX 10)
3 Go de RAM
10 Go de libre sur le DD
et il faut donner le(s) message(s) d'erreur(s) pour qu'une aide du forum soit plus précise
voir dans le chapitre tutoriels du forum par ici
http://www.forum-seven.com/whocrashed-o ... -bleus-996
et voici le lien général des tutoriels topic329.html
sur jeuxvideo.com ils donnent ceci
Configuration minimale requise :
Windows Vista/Windows 7
Pentium D 3GHz/Athlon 64 X2 4200
GeForce 8800/Radeon HD 2600 Pro (256 Mo compatible DirectX 10)
2 Go de RAM
10 Go de libre sur le DD
Configuration recommandée :
Windows Vista/Windows 7
Core 2 Duo 2,6 GHz/Phenom X3 2,4 GHz
GeForce GTS 250/Radeon HD 5750 (512 Mo compatible DirectX 10)
3 Go de RAM
10 Go de libre sur le DD
et il faut donner le(s) message(s) d'erreur(s) pour qu'une aide du forum soit plus précise
voir dans le chapitre tutoriels du forum par ici
http://www.forum-seven.com/whocrashed-o ... -bleus-996et voici le lien général des tutoriels
topic329.htmlRe: PROBLEME w7 et ecran bleu.
Voilà le rapport de WhoCrashed
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 20/04/2011 16:51:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042011-16286-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x859EB)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF1, 0x0, 0xFFFFFFFF82AB17DD, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Wed 20/04/2011 16:51:25 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KeReleaseQueuedSpinLock+0x2D)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF1, 0x0, 0xFFFFFFFF82AB17DD, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
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: hal.sys .
Google query: hal.sys PAGE_FAULT_IN_NONPAGED_AREA
On Wed 20/04/2011 09:09:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042011-15506-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xF0C84)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFF8, 0x2, 0x0, 0xFFFFFFFF9272FC84)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 270.61
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 270.61
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 Windows Kernel Mode Driver, Version 270.61 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Wed 20/04/2011 09:01:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042011-16520-01.dmp
This was probably caused by the following module: avgmfx86.sys (avgmfx86+0x276F)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9A6AE02D, 0xFFFFFFFF8EBF4570, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\avgmfx86.sys
product: AVG Internet Security
company: AVG Technologies CZ, s.r.o.
description: AVG Resident Shield Minifilter Driver
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: avgmfx86.sys (AVG Resident Shield Minifilter Driver, AVG Technologies CZ, s.r.o.).
Google query: avgmfx86.sys AVG Technologies CZ, s.r.o. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Tue 19/04/2011 22:49:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042011-21886-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x8A20)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF922F2A20, 0xFFFFFFFF90DDDC60, 0xFFFFFFFF90DDD840)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 19/04/2011 13:56:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041911-20061-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x276F71)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82C77F71, 0xFFFFFFFFA16DDAE8, 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 18/04/2011 23:50:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041911-20701-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1181BE)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF919441BE, 0xFFFFFFFF9F9239F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 270.61
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 270.61
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 270.61 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Mon 18/04/2011 13:02:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041811-23415-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x11F46A)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82B3046A, 0xFFFFFFFF8AAF4A8C, 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 Fri 15/04/2011 12:40:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041511-26644-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1EDEE)
Bugcheck code: 0x50 (0xFFFFFFFF8F351456, 0x1, 0xFFFFFFFF9184FD0F, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 270.61
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 270.61
Bug check description: This indicates that invalid system memory has been referenced.
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 Windows Kernel Mode Driver, Version 270.61 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA
On Wed 13/04/2011 17:52:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041311-20373-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x322493)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85902024, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
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 a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 13/04/2011 17:48:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041311-17518-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0xA885)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82FAD885, 0xFFFFFFFFA19ED7D4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 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/04/2011 12:12:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041211-21528-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCDFC)
Bugcheck code: 0x18 (0xFFFFFFFF8483BED8, 0xFFFFFFFF8513FD48, 0x1, 0xFFFFFFFFD3000A00)
Error: REFERENCE_BY_POINTER
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 10/04/2011 18:02:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041011-14180-01.dmp
This was probably caused by the following module: lv302v32.sys (LV302V32+0x1B17)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x81D0001, 0xFFFFFFFF8649B598)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\lv302v32.sys
product: Logitech QuickCam
company: Logitech Inc.
description: Logitech QuickCam Driver
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.
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: lv302v32.sys (Logitech QuickCam Driver, Logitech Inc.).
Google query: lv302v32.sys Logitech Inc. BAD_POOL_CALLER
On Thu 31/03/2011 22:12:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040111-23446-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4681B)
Bugcheck code: 0xA (0xFFFFFFFFBBCC919C, 0x0, 0x0, 0xFFFFFFFF8288A720)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Tue 29/03/2011 12:59:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032911-17986-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBD7C2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9763D7C2, 0xFFFFFFFF9CDACA60, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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
--------------------------------------------------------------------------------
24 crash dumps have been found and analyzed. Only 15 are included in this report. 9 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 Windows Kernel Mode Driver, Version 270.61 , NVIDIA Corporation)
lv302v32.sys (Logitech QuickCam Driver, Logitech Inc.)
avgmfx86.sys (AVG Resident Shield Minifilter Driver, AVG Technologies CZ, s.r.o.)
hal.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.
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 20/04/2011 16:51:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042011-16286-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x859EB)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF1, 0x0, 0xFFFFFFFF82AB17DD, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Wed 20/04/2011 16:51:25 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KeReleaseQueuedSpinLock+0x2D)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF1, 0x0, 0xFFFFFFFF82AB17DD, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
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: hal.sys .
Google query: hal.sys PAGE_FAULT_IN_NONPAGED_AREA
On Wed 20/04/2011 09:09:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042011-15506-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xF0C84)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFF8, 0x2, 0x0, 0xFFFFFFFF9272FC84)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 270.61
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 270.61
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 Windows Kernel Mode Driver, Version 270.61 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Wed 20/04/2011 09:01:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042011-16520-01.dmp
This was probably caused by the following module: avgmfx86.sys (avgmfx86+0x276F)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9A6AE02D, 0xFFFFFFFF8EBF4570, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\avgmfx86.sys
product: AVG Internet Security
company: AVG Technologies CZ, s.r.o.
description: AVG Resident Shield Minifilter Driver
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: avgmfx86.sys (AVG Resident Shield Minifilter Driver, AVG Technologies CZ, s.r.o.).
Google query: avgmfx86.sys AVG Technologies CZ, s.r.o. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Tue 19/04/2011 22:49:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042011-21886-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x8A20)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF922F2A20, 0xFFFFFFFF90DDDC60, 0xFFFFFFFF90DDD840)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 19/04/2011 13:56:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041911-20061-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x276F71)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82C77F71, 0xFFFFFFFFA16DDAE8, 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 18/04/2011 23:50:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041911-20701-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1181BE)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF919441BE, 0xFFFFFFFF9F9239F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 270.61
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 270.61
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 270.61 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Mon 18/04/2011 13:02:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041811-23415-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x11F46A)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82B3046A, 0xFFFFFFFF8AAF4A8C, 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 Fri 15/04/2011 12:40:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041511-26644-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1EDEE)
Bugcheck code: 0x50 (0xFFFFFFFF8F351456, 0x1, 0xFFFFFFFF9184FD0F, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 270.61
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 270.61
Bug check description: This indicates that invalid system memory has been referenced.
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 Windows Kernel Mode Driver, Version 270.61 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA
On Wed 13/04/2011 17:52:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041311-20373-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x322493)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85902024, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
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 a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 13/04/2011 17:48:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041311-17518-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0xA885)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82FAD885, 0xFFFFFFFFA19ED7D4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 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/04/2011 12:12:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041211-21528-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCDFC)
Bugcheck code: 0x18 (0xFFFFFFFF8483BED8, 0xFFFFFFFF8513FD48, 0x1, 0xFFFFFFFFD3000A00)
Error: REFERENCE_BY_POINTER
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 10/04/2011 18:02:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041011-14180-01.dmp
This was probably caused by the following module: lv302v32.sys (LV302V32+0x1B17)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x81D0001, 0xFFFFFFFF8649B598)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\lv302v32.sys
product: Logitech QuickCam
company: Logitech Inc.
description: Logitech QuickCam Driver
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.
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: lv302v32.sys (Logitech QuickCam Driver, Logitech Inc.).
Google query: lv302v32.sys Logitech Inc. BAD_POOL_CALLER
On Thu 31/03/2011 22:12:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040111-23446-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4681B)
Bugcheck code: 0xA (0xFFFFFFFFBBCC919C, 0x0, 0x0, 0xFFFFFFFF8288A720)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Tue 29/03/2011 12:59:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032911-17986-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBD7C2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9763D7C2, 0xFFFFFFFF9CDACA60, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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
--------------------------------------------------------------------------------
24 crash dumps have been found and analyzed. Only 15 are included in this report. 9 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 Windows Kernel Mode Driver, Version 270.61 , NVIDIA Corporation)
lv302v32.sys (Logitech QuickCam Driver, Logitech Inc.)
avgmfx86.sys (AVG Resident Shield Minifilter Driver, AVG Technologies CZ, s.r.o.)
hal.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.
-
grimpeur
Re: PROBLEME w7 et ecran bleu.
Bonsoir beubeu
juste pour avancer un peu car je ne suis pas expert il faut regarder au niveau de tes pilotes qui ne sont pas à jour .
Ton message de fin dit :[/u
]9 pilotes tiers ont été identifiés pour être à l'origine plantage du système sur votre ordinateur. Il est fortement recommandé que vous vérifiez les mises à jour de ces pilotes sur leurs sites Web d'entreprise ou chez le fabricant de ton pc si portable .
voir aussi dans le gestionnaire de tes périphériques si tout est ok en attendant une autre
juste pour avancer un peu car je ne suis pas expert il faut regarder au niveau de tes pilotes qui ne sont pas à jour .
Ton message de fin dit :[/u
]9 pilotes tiers ont été identifiés pour être à l'origine plantage du système sur votre ordinateur. Il est fortement recommandé que vous vérifiez les mises à jour de ces pilotes sur leurs sites Web d'entreprise ou chez le fabricant de ton pc si portable .
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 270.61 , NVIDIA Corporation)
lv302v32.sys (Logitech QuickCam Driver, Logitech Inc.)
avgmfx86.sys (AVG Resident Shield Minifilter Driver, AVG Technologies CZ, s.r.o.)
voir aussi dans le gestionnaire de tes périphériques si tout est ok en attendant une autre
Re: PROBLEME w7 et ecran bleu.
Nan rien dans mon gestionnaire ^^.
en fait j'ai supprimé un partition qui me servait a rien avec partition magic et et remis les bons driver pour la cam et depuis pas de nouvel des ecrans bleu =)
(j'ai aussi passé un coup d'aspirateur et ouvert un peu le capot de la machine)
Merci pour ton aide.
en fait j'ai supprimé un partition qui me servait a rien avec partition magic et et remis les bons driver pour la cam et depuis pas de nouvel des ecrans bleu =)
(j'ai aussi passé un coup d'aspirateur et ouvert un peu le capot de la machine)
Merci pour ton aide.
Re: PROBLEME w7 et ecran bleu.
partition magic ? avec seven ?
j'ai aussi un problème récurrent de crash !
je n'ai aucun jeu
le crash se produit de façon totalement aléatoire ! parfois plusieurs jours sans problèmes et l'ordi reste branché en permanence
Pouvez-vous m'aider ?
Merci
System Information (local)
--------------------------------------------------------------------------------
computer name: PC-DE-SERGE
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) 8250e Triple-Core Processor AMD586, level: 16
3 logical processors, active mask: 7
RAM: 4293451776 total
VM: 2147352576, free: 1887182848
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 18/04/2011 19:05:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041811-35833-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x1EA08)
Bugcheck code: 0x100000B8 (0xFFFFFA80046BC040, 0xFFFFF8800336DF80, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Mon 18/04/2011 19:05:52 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: 0xB8 (0xFFFFFA80046BC040, 0xFFFFF8800336DF80, 0x0, 0x0)
Error: ATTEMPTED_SWITCH_FROM_DPC
Bug check description: This indicates that an illegal operation was attempted by a delayed procedure call (DPC) routine.
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 Fri 25/03/2011 02:01:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032511-33072-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x82EDA)
Bugcheck code: 0x100000B8 (0xFFFFFA80046F1690, 0xFFFFF8800336DF80, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 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.
j'ai aussi un problème récurrent de crash !
je n'ai aucun jeu
le crash se produit de façon totalement aléatoire ! parfois plusieurs jours sans problèmes et l'ordi reste branché en permanence
Pouvez-vous m'aider ?
Merci
System Information (local)
--------------------------------------------------------------------------------
computer name: PC-DE-SERGE
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) 8250e Triple-Core Processor AMD586, level: 16
3 logical processors, active mask: 7
RAM: 4293451776 total
VM: 2147352576, free: 1887182848
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 18/04/2011 19:05:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041811-35833-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x1EA08)
Bugcheck code: 0x100000B8 (0xFFFFFA80046BC040, 0xFFFFF8800336DF80, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Mon 18/04/2011 19:05:52 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: 0xB8 (0xFFFFFA80046BC040, 0xFFFFF8800336DF80, 0x0, 0x0)
Error: ATTEMPTED_SWITCH_FROM_DPC
Bug check description: This indicates that an illegal operation was attempted by a delayed procedure call (DPC) routine.
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 Fri 25/03/2011 02:01:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032511-33072-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x82EDA)
Bugcheck code: 0x100000B8 (0xFFFFFA80046F1690, 0xFFFFF8800336DF80, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 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.
Re: PROBLEME w7 et ecran bleu.
Ce n'etait pas partition magic mais je me souviens plus du logiciels lol.
http://forum.zebulon.fr/comment-reparer ... 55305.html Fais les deux premiere methodes et regarde le reste si tu vois vois quelque chose qui correspond a ton probleme.
Apparament ton dernier crash est du au module dxgkrnl.sys regarde sur internet les probleme qui y sont liésThis was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x1EA08)
http://forum.zebulon.fr/comment-reparer ... 55305.html Fais les deux premiere methodes et regarde le reste si tu vois vois quelque chose qui correspond a ton probleme.
Re: PROBLEME w7 et ecran bleu.
merci mais déjà fait le grand nettoyage !je cherche les derniers drivers sinon peut-être tout pêter !