Problème de BlueScreen [Whocrashed]
Posté : sam. 31 août 2013 17:44
Bonjour à tous,
j'ai des problèmes de bluescreen sur un appareil et des problèmes de crash sur le deuxième. J'ai donc fait un rapport Whocrashed afin de trouver les solutions, pouvez vous donc me dire d'où viens le problème et surtout comment le résoudre parce que c'est insupportable. J'ai déjà regardé les autres posts à ce sujet mais je n'ai pas trouvé mes solutions.
Je tiens à dire que le premier ordi à 2 semaines et donc que Windows 7 viens d'être installé (en quelque sorte).
Et le second est quant à lui plus vieux et possède donc légèrement moins de crash (pas de screenblue).
1ère machine (bluescreen):
Welcome to WhoCrashed (HOME EDITION) v 4.02
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 http://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: GISÈLE-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD A8-5600K APU with Radeon(tm) HD Graphics AMD586, level: 21
4 logical processors, active mask: 15
RAM: 3706060800 total
VM: 2147352576, free: 1903423488
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 31/08/2013 11:30:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083113-36083-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0xA16C0)
Bugcheck code: 0x7A (0xFFFFF6FC4001D988, 0xFFFFFFFFC000009D, 0x6D85A860, 0xFFFFF88003B316C0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Sat 31/08/2013 11:30:42 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!DpiGetDriverVersion+0x21B5C)
Bugcheck code: 0x7A (0xFFFFF6FC4001D988, 0xFFFFFFFFC000009D, 0x6D85A860, 0xFFFFF88003B316C0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Sat 31/08/2013 09:46:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083113-16894-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006C85730, 0xFFFFFA8006C85A10, 0xFFFFF8000338F350)
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 Sat 31/08/2013 08:27:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083113-17035-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006BF4710, 0xFFFFFA8006BF49F0, 0xFFFFF800033CE350)
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 Fri 30/08/2013 17:44:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083013-16192-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006C14060, 0xFFFFFA8006C14340, 0xFFFFF800033CD350)
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 Fri 30/08/2013 16:09:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083013-17706-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006C0C9E0, 0xFFFFFA8006C0CCC0, 0xFFFFF800033E4350)
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 Fri 30/08/2013 14:21:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083013-17955-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x7A (0xFFFFF6FC50054208, 0xFFFFFFFFC000009D, 0x10A9F5880, 0xFFFFF8A00A841120)
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 Tue 27/08/2013 08:01:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082713-16629-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0xA16C0)
Bugcheck code: 0x7A (0xFFFFF6FC4008EBD8, 0xFFFFFFFFC000009D, 0x12406D860, 0xFFFFF88011D7B6C0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Mon 26/08/2013 19:11:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082613-16036-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006066B30, 0xFFFFFA8006066E10, 0xFFFFF800033D8350)
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 Mon 26/08/2013 17:27:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082613-16941-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA8005750078, 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 26/08/2013 11:28:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082613-17300-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006245690, 0xFFFFFA8006245970, 0xFFFFF800033DE350)
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 Mon 26/08/2013 10:17:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082613-17472-01.dmp
This was probably caused by the following module: rtkvhd64.sys (RTKVHD64+0x2E0AF4)
Bugcheck code: 0x7A (0xFFFFF6FC4002EBA8, 0xFFFFFFFFC000009D, 0x390E3860, 0xFFFFF88005D75AF4)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\rtkvhd64.sys
product: Realtek(r) High Definition Audio Function Driver
company: Realtek Semiconductor Corp.
description: Realtek(r) High Definition Audio Function Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rtkvhd64.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.).
Google query: Realtek Semiconductor Corp. KERNEL_DATA_INPAGE_ERROR
On Mon 26/08/2013 07:59:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082613-16270-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80060D8B30, 0xFFFFFA80060D8E10, 0xFFFFF8000338D350)
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 Sat 24/08/2013 21:16:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082413-25147-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA80066E67C8, 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
14 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
rtkvhd64.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
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.
Seconde machine crash :
Welcome to WhoCrashed (HOME EDITION) v 4.02
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 http://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: UTILISATEUR-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8558768128 total
VM: 2147352576, free: 1898426368
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 27/08/2013 15:18:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082713-13899-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8009413DE0, 0xFFFFFA8009413E60, 0x4080008)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time.
On Tue 27/08/2013 15:18:18 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalSendSoftwareInterrupt+0x123E)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8009413DE0, 0xFFFFFA8009413E60, 0x4080008)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 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.
Conclusion
2 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.
Cordialement, FloydsHD
j'ai des problèmes de bluescreen sur un appareil et des problèmes de crash sur le deuxième. J'ai donc fait un rapport Whocrashed afin de trouver les solutions, pouvez vous donc me dire d'où viens le problème et surtout comment le résoudre parce que c'est insupportable. J'ai déjà regardé les autres posts à ce sujet mais je n'ai pas trouvé mes solutions.
Je tiens à dire que le premier ordi à 2 semaines et donc que Windows 7 viens d'être installé (en quelque sorte).
Et le second est quant à lui plus vieux et possède donc légèrement moins de crash (pas de screenblue).
1ère machine (bluescreen):
Welcome to WhoCrashed (HOME EDITION) v 4.02
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 http://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: GISÈLE-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD A8-5600K APU with Radeon(tm) HD Graphics AMD586, level: 21
4 logical processors, active mask: 15
RAM: 3706060800 total
VM: 2147352576, free: 1903423488
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 31/08/2013 11:30:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083113-36083-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0xA16C0)
Bugcheck code: 0x7A (0xFFFFF6FC4001D988, 0xFFFFFFFFC000009D, 0x6D85A860, 0xFFFFF88003B316C0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Sat 31/08/2013 11:30:42 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!DpiGetDriverVersion+0x21B5C)
Bugcheck code: 0x7A (0xFFFFF6FC4001D988, 0xFFFFFFFFC000009D, 0x6D85A860, 0xFFFFF88003B316C0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Sat 31/08/2013 09:46:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083113-16894-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006C85730, 0xFFFFFA8006C85A10, 0xFFFFF8000338F350)
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 Sat 31/08/2013 08:27:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083113-17035-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006BF4710, 0xFFFFFA8006BF49F0, 0xFFFFF800033CE350)
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 Fri 30/08/2013 17:44:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083013-16192-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006C14060, 0xFFFFFA8006C14340, 0xFFFFF800033CD350)
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 Fri 30/08/2013 16:09:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083013-17706-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006C0C9E0, 0xFFFFFA8006C0CCC0, 0xFFFFF800033E4350)
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 Fri 30/08/2013 14:21:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083013-17955-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x7A (0xFFFFF6FC50054208, 0xFFFFFFFFC000009D, 0x10A9F5880, 0xFFFFF8A00A841120)
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 Tue 27/08/2013 08:01:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082713-16629-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0xA16C0)
Bugcheck code: 0x7A (0xFFFFF6FC4008EBD8, 0xFFFFFFFFC000009D, 0x12406D860, 0xFFFFF88011D7B6C0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Mon 26/08/2013 19:11:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082613-16036-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006066B30, 0xFFFFFA8006066E10, 0xFFFFF800033D8350)
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 Mon 26/08/2013 17:27:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082613-16941-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA8005750078, 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 26/08/2013 11:28:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082613-17300-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006245690, 0xFFFFFA8006245970, 0xFFFFF800033DE350)
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 Mon 26/08/2013 10:17:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082613-17472-01.dmp
This was probably caused by the following module: rtkvhd64.sys (RTKVHD64+0x2E0AF4)
Bugcheck code: 0x7A (0xFFFFF6FC4002EBA8, 0xFFFFFFFFC000009D, 0x390E3860, 0xFFFFF88005D75AF4)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\rtkvhd64.sys
product: Realtek(r) High Definition Audio Function Driver
company: Realtek Semiconductor Corp.
description: Realtek(r) High Definition Audio Function Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rtkvhd64.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.).
Google query: Realtek Semiconductor Corp. KERNEL_DATA_INPAGE_ERROR
On Mon 26/08/2013 07:59:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082613-16270-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80060D8B30, 0xFFFFFA80060D8E10, 0xFFFFF8000338D350)
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 Sat 24/08/2013 21:16:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082413-25147-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA80066E67C8, 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
14 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
rtkvhd64.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
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.
Seconde machine crash :
Welcome to WhoCrashed (HOME EDITION) v 4.02
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 http://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: UTILISATEUR-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8558768128 total
VM: 2147352576, free: 1898426368
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 27/08/2013 15:18:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082713-13899-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8009413DE0, 0xFFFFFA8009413E60, 0x4080008)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time.
On Tue 27/08/2013 15:18:18 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalSendSoftwareInterrupt+0x123E)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8009413DE0, 0xFFFFFA8009413E60, 0x4080008)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 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.
Conclusion
2 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.
Cordialement, FloydsHD
Il ne faut pas d'erreur dans le cadre en bas à droite.