       |
le 07 Mai 2012 18:38
le 07 Mai 2012 19:31
batman73 a écrit:Bonjour!!
Nous revoilà de nouveau!!!
Depuis quelques jours nous avons de nouveau des blue screen,apres plusieurs mois sans aucun problemes,je precise que nous avions deja fait changé les barrettes memoires etant donné que le problème venait de là à l'époque.
Help....
merci
le 09 Mai 2012 08:49
System Information (local)
--------------------------------------------------------------------------------
computer name: LILYETBATMAN-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) II X3 440 Processor AMD586, level: 16
3 logical processors, active mask: 7
RAM: 3755532288 total
VM: 2147352576, free: 1979539456
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 07/05/2012 06:25:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050712-24882-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC50)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a 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 07/05/2012 06:25:13 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ataport.sys (ataport+0xA6CE)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
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 23/04/2012 15:53:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042312-23228-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0x1 (0xFFFFF800035CDBE0, 0x0, 0xF, 0x1)
Error: APC_INDEX_MISMATCH
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that there has been a mismatch in the APC state index.
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 09/03/2012 21:18:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030912-18096-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800034D8B65, 0xFFFFF88002AEAE80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 06/12/2011 14:53:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120611-32869-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800594EA00, 0xFFFFF800047EB748, 0xFFFFFA8003C72520)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 09/09/2011 11:39:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090911-20311-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x403, 0xFFFFF68000BF7228, 0xC7F000002903B867, 0xFFFFF68000BF3228)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 07/09/2011 08:59:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090711-16317-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xDDB21)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600010DB21, 0xFFFFF88008126230, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 29/08/2011 12:47:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082911-22230-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF8A00D23DFF8, 0x0, 0xFFFFF88006605657, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that 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 Fri 26/08/2011 11:53:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082611-17378-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3625C3)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800037AF5C3, 0xFFFFF88003177968, 0xFFFFF880031771C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 22/08/2011 18:48:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082211-23961-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x403, 0xFFFFF68000B46898, 0x84B000009AF85867, 0xFFFFF68000B42898)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 20/08/2011 20:18:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082011-16723-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0xA23B)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800378623B, 0xFFFFF8800989F8E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. SYSTEM_SERVICE_EXCEPTION
On Sat 20/08/2011 13:24:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082011-17628-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xFC (0xFFFFF88002B36480, 0x80000000717BF963, 0xFFFFF88002B36220, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that 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 Wed 10/08/2011 16:09:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081011-21200-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x3452, 0x3843000, 0xFFFFF70001080648, 0x200)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 10/08/2011 09:37:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081011-33072-01.dmp
This was probably caused by the following module: hal.dll (hal+0x7B21)
Bugcheck code: 0xA (0x4830265C, 0x2, 0x1, 0xFFFFF80003408B21)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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 26/07/2011 19:14:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072611-15802-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFFFFFFF7B59D3, 0x8, 0xFFFFFFFFFF7B59D3, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
51 crash dumps have been found and analyzed. Only 15 are included in this report. 2 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:
aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software)
atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)
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 09 Mai 2012 12:27
[Réglé] Bleu screen en lançant un jeu sur Win 11 Problème ouverture lecteur Blue-Ray Purple screen after reboot Black screen windows 8.1 températures r9 280x en dual screen Blue screen au démarrage de Windows 7 Blue screen après réinitiatlisation de l'OSUtilisateurs parcourant ce forum: Aucun utilisateur enregistré et 129 invités
|
.: Nous contacter :: Flux RSS :: Données personnelles :. |