Brume

Bonsoir à tous, c'est mon premier message sur ce forum.

Malgré moultes recherches et essais, je suis à court de solutions pour ce problème. Si certains peuvent apporter un peu de lumière, ce ne serait pas de refus.

Le problème semble être apparu après changement de disque dur (pas sur de ça), mais j'ai testé une nouvelle installation sur un autre, même chose. J'ai effectué un memtest, rien d'anormal, tenté de changer le voltage de la RAM en le mettant à 1.51V après qu'on me l'ait suggéré. Toujours pareil. La carte mère est neuve, ainsi que la CG et le disque dur.

Config :
Windows 7 64 bits
CM ASUS M5A97 LE R2.0
AMD Phenom(tm) II X4955 Processor 3.20 GHZ
MSI GTX 770 Twin Frozr
4 GB RAM 1600MHZ 1.50V Corsair
DD interne WD 500Go
Alim' Lepa B650-MB 650W


Voici ce que dit l'analyse du minidump par Whocrashed :


windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., M5A97 LE R2.0
CPU: AuthenticAMD AMD Phenom(tm) II X4 955 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4208332800 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 05/12/2014 16:51:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120514-18860-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA8004A47078, 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 05/12/2014 16:51:27 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, 0xFFFFFA8004A47078, 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 Wed 26/11/2014 15:13:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112614-35599-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA8007A5B078, 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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider 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 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.


Voilà, si vous avez une idée, une suggestion. Merci d'avance!