Redemarrage de windows
Fermé
stefrol
-
16 nov. 2011 à 11:00
le druide Messages postés 40156 Date d'inscription vendredi 16 avril 2004 Statut Contributeur Dernière intervention 15 octobre 2023 - 16 nov. 2011 à 16:14
le druide Messages postés 40156 Date d'inscription vendredi 16 avril 2004 Statut Contributeur Dernière intervention 15 octobre 2023 - 16 nov. 2011 à 16:14
A voir également:
- Redemarrage de windows
- Forcer redemarrage windows - Guide
- Clé windows 10 gratuit - Guide
- Windows 10 gratuit - Guide
- Windows 12 - Guide
- Windows ne démarre pas - Guide
2 réponses
le druide
Messages postés
40156
Date d'inscription
vendredi 16 avril 2004
Statut
Contributeur
Dernière intervention
15 octobre 2023
6 606
Modifié par le druide le 16/11/2011 à 11:53
Modifié par le druide le 16/11/2011 à 11:53
salut,
quelques détails supplémentaires serait le bienvenue, pour affiner la recherche de la panne.
Depuis combien de temps possède tu ce pc
Quel système est installé dessus
Est-ce que tu as fais des modif. matériel ou logiciel juste avant le problème
le druide sans la potion.
quelques détails supplémentaires serait le bienvenue, pour affiner la recherche de la panne.
Depuis combien de temps possède tu ce pc
Quel système est installé dessus
Est-ce que tu as fais des modif. matériel ou logiciel juste avant le problème
le druide sans la potion.
le druide
Messages postés
40156
Date d'inscription
vendredi 16 avril 2004
Statut
Contributeur
Dernière intervention
15 octobre 2023
6 606
16 nov. 2011 à 12:51
16 nov. 2011 à 12:51
test le en mode sans échec pour voir si c'est pareil, après je te propose de l'utiliser avec un live cd Linux pour voir comment il ce comporte. Surtout pas installer Linux, tu l'utilises en mode test directement depuis le cd ou possibilité avec une clé usb.
Ubuntu est pas mal, si tu veux le mettre sur une clé il faut récupérer Unetbootin.
Ubuntu est pas mal, si tu veux le mettre sur une clé il faut récupérer Unetbootin.
ok merci pour les conseils perso j ai deja essaye linux ubuntu je l ai trouve moche et pas terrible d utilisation j aimerais rester fidel a mon bon vieux xp...c ce que je connais de mieux...
mode sans echec vais essayer, mais ca sent surtout que je vais tout formater...marre et re-mare de planter...
mode sans echec vais essayer, mais ca sent surtout que je vais tout formater...marre et re-mare de planter...
le druide
Messages postés
40156
Date d'inscription
vendredi 16 avril 2004
Statut
Contributeur
Dernière intervention
15 octobre 2023
6 606
16 nov. 2011 à 13:48
16 nov. 2011 à 13:48
Ubuntu c'est juste pour voir comment ton pc ce comporte, çà permet de procéder par élimination
j ai finalement analyse le pc avec who crashed en voici le rapport si quelqu un peut m aider ???
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 3.03
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: CAMORA-CFD9V7R4
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel(R) Celeron(R) M CPU 420 @ 1.60GHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 2137108480 total
VM: 2147352576, free: 2040651776
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 16/11/2011 14:13:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111611-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CB5)
Bugcheck code: 0x1A (0x41284, 0xA4B001, 0x813, 0xFFFFFFFFC0883000)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 which cannot be identified at this time.
On Wed 16/11/2011 13:05:21 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111611-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x47E76)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF8051EE76)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 16/11/2011 06:48:41 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111611-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CB5)
Bugcheck code: 0x4E (0x99, 0x4F0FA, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 15/11/2011 14:12:14 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111511-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CB5)
Bugcheck code: 0x4E (0x99, 0x5E968, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 Mon 14/11/2011 16:27:34 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111411-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xDF32D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805B632D, 0xFFFFFFFFB975E96C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 14/11/2011 13:08:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111411-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2A7D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF80544605, 0xFFFFFFFFB96AA160, 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.
On Mon 14/11/2011 12:42:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111411-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CB5)
Bugcheck code: 0x4E (0x99, 0x0, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 Sat 12/11/2011 13:49:27 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111211-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xB91D9)
Bugcheck code: 0x4E (0x99, 0x3B75D, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
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 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 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 Fri 11/11/2011 21:18:39 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111111-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CB5)
Bugcheck code: 0x4E (0x99, 0x606FD, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 Fri 11/11/2011 18:14:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111111-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2A7D)
Bugcheck code: 0x1A (0x41785, 0xFFFFFFFFC0E00000, 0x7BC33, 0x0)
Error: MEMORY_MANAGEMENT
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 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 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 Fri 11/11/2011 13:06:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111111-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x9D15)
Bugcheck code: 0x1A (0x41284, 0xBE35001, 0x4C13, 0xFFFFFFFFC0883000)
Error: MEMORY_MANAGEMENT
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 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 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 Thu 10/11/2011 22:40:07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111011-03.dmp
This was probably caused by the following module: hal.dll (hal+0x276E)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF804F9D26)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 Thu 10/11/2011 14:44:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111011-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CB5)
Bugcheck code: 0x4E (0x99, 0x0, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 Thu 10/11/2011 10:15:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111011-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x42392)
Bugcheck code: 0xDE (0x2, 0xFFFFFFFFE2E32D48, 0xFFFFFFFFE2D110F1, 0x4BD6C8C6)
Error: POOL_CORRUPTION_IN_FILE_AREA
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a driver has corrupted pool memory that is used for holding pages destined for disk.
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 08/11/2011 21:58:21 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini110811-01.dmp
This was probably caused by the following module: hal.dll (hal+0x276E)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF804F9D26)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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
--------------------------------------------------------------------------------
29 crash dumps have been found and analyzed. Only 15 are included in this report. 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:
avgidsfilter.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.
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 3.03
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: CAMORA-CFD9V7R4
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel(R) Celeron(R) M CPU 420 @ 1.60GHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 2137108480 total
VM: 2147352576, free: 2040651776
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 16/11/2011 14:13:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111611-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CB5)
Bugcheck code: 0x1A (0x41284, 0xA4B001, 0x813, 0xFFFFFFFFC0883000)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 which cannot be identified at this time.
On Wed 16/11/2011 13:05:21 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111611-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x47E76)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF8051EE76)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 16/11/2011 06:48:41 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111611-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CB5)
Bugcheck code: 0x4E (0x99, 0x4F0FA, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 15/11/2011 14:12:14 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111511-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CB5)
Bugcheck code: 0x4E (0x99, 0x5E968, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 Mon 14/11/2011 16:27:34 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111411-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xDF32D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805B632D, 0xFFFFFFFFB975E96C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 14/11/2011 13:08:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111411-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2A7D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF80544605, 0xFFFFFFFFB96AA160, 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.
On Mon 14/11/2011 12:42:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111411-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CB5)
Bugcheck code: 0x4E (0x99, 0x0, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 Sat 12/11/2011 13:49:27 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111211-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xB91D9)
Bugcheck code: 0x4E (0x99, 0x3B75D, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
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 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 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 Fri 11/11/2011 21:18:39 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111111-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CB5)
Bugcheck code: 0x4E (0x99, 0x606FD, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 Fri 11/11/2011 18:14:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111111-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2A7D)
Bugcheck code: 0x1A (0x41785, 0xFFFFFFFFC0E00000, 0x7BC33, 0x0)
Error: MEMORY_MANAGEMENT
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 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 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 Fri 11/11/2011 13:06:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111111-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x9D15)
Bugcheck code: 0x1A (0x41284, 0xBE35001, 0x4C13, 0xFFFFFFFFC0883000)
Error: MEMORY_MANAGEMENT
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 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 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 Thu 10/11/2011 22:40:07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111011-03.dmp
This was probably caused by the following module: hal.dll (hal+0x276E)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF804F9D26)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 Thu 10/11/2011 14:44:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111011-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CB5)
Bugcheck code: 0x4E (0x99, 0x0, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 Thu 10/11/2011 10:15:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111011-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x42392)
Bugcheck code: 0xDE (0x2, 0xFFFFFFFFE2E32D48, 0xFFFFFFFFE2D110F1, 0x4BD6C8C6)
Error: POOL_CORRUPTION_IN_FILE_AREA
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a driver has corrupted pool memory that is used for holding pages destined for disk.
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 08/11/2011 21:58:21 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini110811-01.dmp
This was probably caused by the following module: hal.dll (hal+0x276E)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF804F9D26)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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
--------------------------------------------------------------------------------
29 crash dumps have been found and analyzed. Only 15 are included in this report. 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:
avgidsfilter.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.
le druide
Messages postés
40156
Date d'inscription
vendredi 16 avril 2004
Statut
Contributeur
Dernière intervention
15 octobre 2023
6 606
16 nov. 2011 à 16:14
16 nov. 2011 à 16:14
lorsque tu démarres sur le cd ou clé usb, tu aura le choix une fois arrivé sur le bureau d'Ubuntu, Tester ou Installer.
16 nov. 2011 à 12:37
surement telecharger quelques logiciel depuis que j ai supprimes car finalement inutiles
il y a un mois j ai fait une analyse avec antimalware qui m a trouve 9 fichiers infectes il me les a degages et depuis ne me trouve plus rien
j ai ce pc un portable "acer travelmate 2480" depuis plusieurs annees