Depuis un certain temps mon pc s’arrête et redémarre inopinément. Mon disque dur a fini par rendre l'ame il y a quelques jours. J'en ai donc remis un neuf et fait une réinstallation de Win7. Cela n'a pas résolu mon problème de bluescreen. Voici le rapport de Window:
Signature du problème : Nom d’événement de problème: BlueScreen Version du système: 6.1.7601.2.1.0.256.48 Identificateur de paramètres régionaux: 1036
Informations supplémentaires sur le problème : BCCode: 7a BCP1: 0000000000000020 BCP2: FFFFFFFFC000009D BCP3: FFFFFA80029DC078 BCP4: 0000000000000000 OS Version: 6_1_7601 Service Pack: 1_0 Product: 256_1
Fichiers aidant à décrire le problème : C:\Windows\Minidump\120213-15147-01.dmp C:\Users\pcmaison\AppData\Local\Temp\WER-83179-0.sysdata.xml
Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion : C:\Windows\system32\fr-FR\erofflps.txt[/i][/i]
et celui de whocrashed:
computer name: PCMAISON-PC windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows Hardware: VN417AA-ABF MS215fr, HP-Pavilion, Hewlett-Packard , Capirona CPU: AuthenticAMD AMD Athlon(tm) X2 Dual Core Processor 3250e AMD586, level: 15 2 logical processors, active mask: 3 RAM: 1877401600 total VM: 2147352576, free: 1939472384
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 02/12/2013 14:01:15 GMT your computer crashed crash dump file: C:\Windows\Minidump\120213-15147-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA80029DC078, 0x0) Error: KERNEL_DATA_INPAGE_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 the requested page of kernel data from the paging file could not be read into memory. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 02/12/2013 14:01:15 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: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA80029DC078, 0x0) Error: KERNEL_DATA_INPAGE_ERROR Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 30/11/2013 15:56:27 GMT your computer crashed crash dump file: C:\Windows\Minidump\113013-24710-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA800321C7C8, 0x0) Error: KERNEL_DATA_INPAGE_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 the requested page of kernel data from the paging file could not be read into memory. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 29/11/2013 19:22:16 GMT your computer crashed crash dump file: C:\Windows\Minidump\112913-19032-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x7A (0xFFFFF6FC40015658, 0xFFFFFFFFC000000E, 0x500ECBE0, 0xFFFFF88002ACB000) Error: KERNEL_DATA_INPAGE_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 the requested page of kernel data from the paging file could not be read into memory. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
4 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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 fait un test avec Memtest et il n'a rien trouvé.
Marsh Posté le 02-12-2013 à 18:03:20
Bonjour,
Depuis un certain temps mon pc s’arrête et redémarre inopinément. Mon disque dur a fini par rendre l'ame il y a quelques jours. J'en ai donc remis un neuf et fait une réinstallation de Win7. Cela n'a pas résolu mon problème de bluescreen.
Voici le rapport de Window:
Signature du problème :
Nom d’événement de problème: BlueScreen
Version du système: 6.1.7601.2.1.0.256.48
Identificateur de paramètres régionaux: 1036
Informations supplémentaires sur le problème :
BCCode: 7a
BCP1: 0000000000000020
BCP2: FFFFFFFFC000009D
BCP3: FFFFFA80029DC078
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Fichiers aidant à décrire le problème :
C:\Windows\Minidump\120213-15147-01.dmp
C:\Users\pcmaison\AppData\Local\Temp\WER-83179-0.sysdata.xml
Lire notre déclaration de confidentialité en ligne :
http://go.microsoft.com/fwlink/?li [...] cid=0x040c
Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion :
C:\Windows\system32\fr-FR\erofflps.txt[/i][/i]
et celui de whocrashed:
computer name: PCMAISON-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: VN417AA-ABF MS215fr, HP-Pavilion, Hewlett-Packard , Capirona
CPU: AuthenticAMD AMD Athlon(tm) X2 Dual Core Processor 3250e AMD586, level: 15
2 logical processors, active mask: 3
RAM: 1877401600 total
VM: 2147352576, free: 1939472384
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 02/12/2013 14:01:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120213-15147-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA80029DC078, 0x0)
Error: KERNEL_DATA_INPAGE_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 the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 02/12/2013 14:01:15 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: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA80029DC078, 0x0)
Error: KERNEL_DATA_INPAGE_ERROR
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 30/11/2013 15:56:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\113013-24710-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA800321C7C8, 0x0)
Error: KERNEL_DATA_INPAGE_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 the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 29/11/2013 19:22:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112913-19032-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FC40015658, 0xFFFFFFFFC000000E, 0x500ECBE0, 0xFFFFF88002ACB000)
Error: KERNEL_DATA_INPAGE_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 the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
4 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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 fait un test avec Memtest et il n'a rien trouvé.
Merci d'avance de votre aide,