Bonjour à tous,
j’ai monté mon PC récemment :
Boitier PC ZALMAN Z11 Plus
Carte mère MSI Z77A-G45
i5-3570K - 3.4 GHz - HD 4000 - Socket LGA1155
COOLERMASTER Hyper 212 EVO
MSI R7950 Twin Frozr 2GD5/OC - Radeon HD7950 - 3048 Mo
Alimentation ANTEC High Current Gamer Series - HCG 520W - 80+ Bronze
kingston DDR3 PC3-12800 - hyperx Grey series Genesis- 2 x 4 Go (8Go) 1600 mhz - cas 9
SSD Intel 330 240Go
Disque dur interne 3,5’’ 500 Go - Barracuda 7200.14 - SATA III
Graveur Samsung (“Basique”)
A savoir que mon disque dur 500Go est défectueux, je vais le renvoyer au SAV, il est donc déconnecté de mon PC.
Mon problème est que lorsque je joue à GW2, parfois même quand je n’y joue pas, j’ai un Bsod, ça reviens souvent. J’ai fait les manipulations suivantes sur “Invite des commandes” : sfc /verifyonly et sfc /scannow. Des problèmes on étés détectés mais W a pu les réparer. A la suite de ça, Bsod, encore une fois. Je m’adresse donc ici pour savoir si il y a une solution et comment procéder dans ce cas.
Je vous met le Crash Dump Analisis de ‘Whocrashed’ :
[b][i]
Welcome to WhoCrashed (HOME EDITION) v 4.01
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report …
Home Edition Notice
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
System Information (local)
computer name: REVOK-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™ i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8535699456 total
VM: 2147352576, free: 1959194624
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 20/12/2012 16:29:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122012-5803-01.dmp
This was probably caused by the following module: msrpc.sys (msrpc+0x50880)
Bugcheck code: 0x7A (0xFFFFF6FC400099C0, 0xFFFFFFFFC000000E, 0x1E7899860, 0xFFFFF88001338880)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\msrpc.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Remote Procedure Call Provider
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 20/12/2012 16:29:17 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: msrpc.sys (msrpc!I_RpcGetBuffer+0x1510)
Bugcheck code: 0x7A (0xFFFFF6FC400099C0, 0xFFFFFFFFC000000E, 0x1E7899860, 0xFFFFF88001338880)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\msrpc.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Remote Procedure Call Provider
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 20/12/2012 15:52:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122012-6115-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8007D67B30, 0xFFFFFA8007D67E10, 0xFFFFF800033C8460)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 20/12/2012 15:39:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122012-5397-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x7A (0xFFFFF6FB40000110, 0xFFFFFFFFC000000E, 0x20C087884, 0xFFFFF68000022000)
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 17/12/2012 15:57:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121712-6754-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8007D83B30, 0xFFFFFA8007D83E10, 0xFFFFF80003381460)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
5 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
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.
[/i][/b]
J’espère que vous pourrez m’ader. Merci d’avoir lu.
