1 réponse
J'ai tester la mémoire, ça n'a rien donner.
Du coup, j'ai effectuer une restauration du système à une date antérieure (3jours avant le premier crash), ça n'a rien donner.
J'ai lancer WhoCrashed dont voilà le résultat :
System Information (local)
--------------------------------------------------------------------------------
computer name: SEB
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware:
CPU: GenuineIntel Intel(R) Pentium(R) CPU 2020M @ 2.40GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4175085568 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 19/02/2015 16:01:03 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 (0x4, 0x0, 0xFFFFE0015E493130, 0xFFFFF801E4180010)
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
One crash dump has 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.
Du coup, j'ai effectuer une restauration du système à une date antérieure (3jours avant le premier crash), ça n'a rien donner.
J'ai lancer WhoCrashed dont voilà le résultat :
System Information (local)
--------------------------------------------------------------------------------
computer name: SEB
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware:
CPU: GenuineIntel Intel(R) Pentium(R) CPU 2020M @ 2.40GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4175085568 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 19/02/2015 16:01:03 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 (0x4, 0x0, 0xFFFFE0015E493130, 0xFFFFF801E4180010)
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
One crash dump has 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.