Après avoir formaté ce week-end, pour des problèmes d'écrans bleus à répétition (pensant que ce n'était pas matériel), je me retrouve dans la même situation 3 jours après.
Le rapport whocrashed :
computer name: BEN-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) 64 Processor 3800+ AMD586, level: 15
1 logical processors, active mask: 1
RAM: 1878581248 total
VM: 2147352576, free: 1973776384
On Tue 31/05/2011 21:34:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053111-36660-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x318725)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002D6B725, 0xFFFFF88002F85868, 0xFFFFF88002F850C0)
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 Tue 31/05/2011 21:34:23 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: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80002D6B725, 0xFFFFF88002F85868, 0xFFFFF88002F850C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 31/05/2011 14:31:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053111-18673-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800079E6C0, 0xFFFF, 0x0)
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 Tue 31/05/2011 13:57:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053111-21169-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80011AD830, 0xFFFF, 0x0)
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 Tue 31/05/2011 13:52:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053111-35973-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41284, 0x1001B001, 0x8319, 0xFFFFF70001080000)
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 Tue 31/05/2011 13:17:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053111-25053-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1328CC)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001928CC, 0xFFFFF880024AEEB0, 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 Tue 31/05/2011 11:28:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053111-19390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002B10105, 0xFFFFF88003818C90, 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.
J'avais lancé un memtest, à 20% il y'avait 15 erreurs de ce style : http://www.cijoint.fr/cj201106/cijX9VqFUl.png puis la bécane à planté.
Dans le même temps, j'avais lancé un scan via l'invité de commande (sfc/scannow), j'attends le résultat.
Pensez-vous que ce soit simplement un problème de ram cuites ?
le problème viendrait d'une barrette de mémoire défectueuse, je tourne sur une, et pas d'écran bleu depuis plus de 3 heures.
aucune erreur après un memtest, aucune erreur après un scan du système.
J ai un acer 5742z avec windows 7 64x et 'j'ai aussi l écran bleu au lancement de windows. J ai 2 ddl de 2go chacune j ai ete voir un tecnicien, il a seulemenent retiré une des ddl. je vous savoir comment faire pour pouvoir employer les 2 pour avoir 4 go de memoire ram dois je faire les même procedures ?
