Bonjours depuis quelque jours mon ordi redémarre sans raison ensuite un message d'erreur de windows me dit que c'est un bluecreen , je n'ai pas compris . pouvez-vous m'aider ?
je suis sous windows vista merci d'avance .
Bluecreen
Modérateur : Mods Windows
Re: Bluecreen
System Information (local)
--------------------------------------------------------------------------------
computer name: PC-DE-DINK
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
Hardware: MS-7358, MEDIONPC, MICRO-STAR INTERNATIONAL CO., LTD
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3486990336 total
VM: 2147352576, free: 1958387712
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 15/11/2013 12:30:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111513-02.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6EE02)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFD8, 0x2, 0x0, 0xFFFFFFFF8DA74E02)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Fri 15/11/2013 12:30:30 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6EE02)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFD8, 0x2, 0x0, 0xFFFFFFFF8DA74E02)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Fri 15/11/2013 11:54:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111513-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x20598)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8D4EE598, 0xFFFFFFFFAFE8B73C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 14/11/2013 12:38:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111413-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x22E33F)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF84C7E33F, 0xFFFFFFFFA75D6C44, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 13/11/2013 12:29:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111313-05.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x71304)
Bugcheck code: 0x35 (0xFFFFFFFF877001FD, 0x0, 0x0, 0x0)
Error: NO_MORE_IRP_STACK_LOCATIONS
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This bug check occurs when the IoCallDriver packet has no more stack locations remaining.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Wed 13/11/2013 12:25:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111313-04.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A05F)
Bugcheck code: 0x24 (0x1904AA, 0xFFFFFFFFA4F723E4, 0xFFFFFFFFA4F720E0, 0xFFFFFFFF8DC1E58F)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Wed 13/11/2013 12:21:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111313-03.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DECD)
Bugcheck code: 0xA (0xB086, 0x1B, 0x0, 0xFFFFFFFF84AE3A9D)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 13/11/2013 11:57:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111313-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DECD)
Bugcheck code: 0xA (0xFFFFFFFFA0417D34, 0xFF, 0x1, 0xFFFFFFFF84ABAE60)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 12/11/2013 23:53:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111313-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DECD)
Bugcheck code: 0xA (0xFFFFFFFFFFFE7962, 0x1F, 0x0, 0xFFFFFFFF84AB6280)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 11/11/2013 23:52:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111213-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x65533)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF84A7B168, 0xFFFFFFFF81A30B94, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 311.06
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 311.06
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 311.06 , NVIDIA Corporation).
Google query: NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
12 crash dumps have been found and analyzed. Only 10 are included in this report. 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 311.06 , NVIDIA Corporation)
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.
--------------------------------------------------------------------------------
computer name: PC-DE-DINK
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
Hardware: MS-7358, MEDIONPC, MICRO-STAR INTERNATIONAL CO., LTD
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3486990336 total
VM: 2147352576, free: 1958387712
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 15/11/2013 12:30:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111513-02.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6EE02)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFD8, 0x2, 0x0, 0xFFFFFFFF8DA74E02)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Fri 15/11/2013 12:30:30 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6EE02)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFD8, 0x2, 0x0, 0xFFFFFFFF8DA74E02)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Fri 15/11/2013 11:54:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111513-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x20598)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8D4EE598, 0xFFFFFFFFAFE8B73C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 14/11/2013 12:38:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111413-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x22E33F)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF84C7E33F, 0xFFFFFFFFA75D6C44, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 13/11/2013 12:29:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111313-05.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x71304)
Bugcheck code: 0x35 (0xFFFFFFFF877001FD, 0x0, 0x0, 0x0)
Error: NO_MORE_IRP_STACK_LOCATIONS
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This bug check occurs when the IoCallDriver packet has no more stack locations remaining.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Wed 13/11/2013 12:25:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111313-04.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A05F)
Bugcheck code: 0x24 (0x1904AA, 0xFFFFFFFFA4F723E4, 0xFFFFFFFFA4F720E0, 0xFFFFFFFF8DC1E58F)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Wed 13/11/2013 12:21:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111313-03.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DECD)
Bugcheck code: 0xA (0xB086, 0x1B, 0x0, 0xFFFFFFFF84AE3A9D)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 13/11/2013 11:57:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111313-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DECD)
Bugcheck code: 0xA (0xFFFFFFFFA0417D34, 0xFF, 0x1, 0xFFFFFFFF84ABAE60)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 12/11/2013 23:53:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111313-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DECD)
Bugcheck code: 0xA (0xFFFFFFFFFFFE7962, 0x1F, 0x0, 0xFFFFFFFF84AB6280)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 11/11/2013 23:52:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111213-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x65533)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF84A7B168, 0xFFFFFFFF81A30B94, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 311.06
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 311.06
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 311.06 , NVIDIA Corporation).
Google query: NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
12 crash dumps have been found and analyzed. Only 10 are included in this report. 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 311.06 , NVIDIA Corporation)
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.
Re: Bluecreen
Bonsoir,
Le PC chauffe ?
As-tu déjà dépoussiéré l'intérieur de celui-ci ?
Le PC chauffe ?
As-tu déjà dépoussiéré l'intérieur de celui-ci ?
Re: Bluecreen
J'ai bien fait les mise a jours et aussi dépoussiérer mon ordie mais le probleme persiste ! autre solutions ?
Re: Bluecreen
Bonjour,
Poste un nouveau rapport WhoCrashed.
Poste un nouveau rapport WhoCrashed.
Regarde du côté matériel : http://forum.malekal.com/tester-materie ... 44006.htmlSkyTech a écrit :Le PC chauffe ?
Re: Bluecreen
System Information (local)
--------------------------------------------------------------------------------
computer name: PC-DE-DINK
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
Hardware: MS-7358, MEDIONPC, MICRO-STAR INTERNATIONAL CO., LTD
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3486990336 total
VM: 2147352576, free: 1966669824
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 01/12/2013 04:28:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini120113-02.dmp
This was probably caused by the following module: netio.sys (NETIO+0x1089)
Bugcheck code: 0xD1 (0xFFFFFFFFE3B3A0E0, 0x2, 0x0, 0xFFFFFFFF8DBB0089)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Sun 01/12/2013 04:28:27 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: netio.sys (NETIO+0x1089)
Bugcheck code: 0xD1 (0xFFFFFFFFE3B3A0E0, 0x2, 0x0, 0xFFFFFFFF8DBB0089)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Sun 01/12/2013 00:33:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini120113-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x77321)
Bugcheck code: 0xD1 (0x478B1845, 0x2, 0x1, 0xFFFFFFFF8DC79321)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Fri 29/11/2013 22:20:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112913-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCACB0)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9EB5ACB0, 0xFFFFFFFF84279CE4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 28/11/2013 22:38:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112813-04.dmp
This was probably caused by the following module: afd.sys (afd+0x21B59)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\afd.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 28/11/2013 20:20:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112813-03.dmp
This was probably caused by the following module: netio.sys (NETIO+0x1089)
Bugcheck code: 0xD1 (0x899B1C0, 0x2, 0x0, 0xFFFFFFFF8DBB3089)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 28/11/2013 00:46:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112813-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCB12E)
Bugcheck code: 0xA (0x4, 0x1B, 0x0, 0xFFFFFFFF84AC6F9A)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 28/11/2013 00:24:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112813-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x1089)
Bugcheck code: 0xD1 (0xFFFFFFFFE39F4160, 0x2, 0x0, 0xFFFFFFFF8DBB1089)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Tue 26/11/2013 21:07:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112613-02.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x1DDE)
Bugcheck code: 0x50 (0xFFFFFFFFBF8FEDFF, 0x1, 0xFFFFFFFF807BBDDE, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Tue 26/11/2013 19:27:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112613-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x7DDD8)
Bugcheck code: 0xBE (0x76D8C05A, 0xFFFFFFFFAA3A0005, 0xFFFFFFFF8039D810, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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
--------------------------------------------------------------------------------
45 crash dumps have been found and analyzed. Only 10 are included in this report. 4 third party drivers have 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 331.82 , NVIDIA Corporation)
fastfat.sys (Fast FAT File System Driver, Microsoft Corporation)
iastor.sys (Intel Rapid Storage Technology driver - x86, Intel Corporation)
?
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.
--------------------------------------------------------------------------------
computer name: PC-DE-DINK
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
Hardware: MS-7358, MEDIONPC, MICRO-STAR INTERNATIONAL CO., LTD
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3486990336 total
VM: 2147352576, free: 1966669824
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 01/12/2013 04:28:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini120113-02.dmp
This was probably caused by the following module: netio.sys (NETIO+0x1089)
Bugcheck code: 0xD1 (0xFFFFFFFFE3B3A0E0, 0x2, 0x0, 0xFFFFFFFF8DBB0089)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Sun 01/12/2013 04:28:27 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: netio.sys (NETIO+0x1089)
Bugcheck code: 0xD1 (0xFFFFFFFFE3B3A0E0, 0x2, 0x0, 0xFFFFFFFF8DBB0089)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Sun 01/12/2013 00:33:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini120113-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x77321)
Bugcheck code: 0xD1 (0x478B1845, 0x2, 0x1, 0xFFFFFFFF8DC79321)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Fri 29/11/2013 22:20:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112913-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCACB0)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9EB5ACB0, 0xFFFFFFFF84279CE4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 28/11/2013 22:38:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112813-04.dmp
This was probably caused by the following module: afd.sys (afd+0x21B59)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\afd.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 28/11/2013 20:20:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112813-03.dmp
This was probably caused by the following module: netio.sys (NETIO+0x1089)
Bugcheck code: 0xD1 (0x899B1C0, 0x2, 0x0, 0xFFFFFFFF8DBB3089)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 28/11/2013 00:46:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112813-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCB12E)
Bugcheck code: 0xA (0x4, 0x1B, 0x0, 0xFFFFFFFF84AC6F9A)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 28/11/2013 00:24:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112813-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x1089)
Bugcheck code: 0xD1 (0xFFFFFFFFE39F4160, 0x2, 0x0, 0xFFFFFFFF8DBB1089)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Tue 26/11/2013 21:07:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112613-02.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x1DDE)
Bugcheck code: 0x50 (0xFFFFFFFFBF8FEDFF, 0x1, 0xFFFFFFFF807BBDDE, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Tue 26/11/2013 19:27:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112613-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x7DDD8)
Bugcheck code: 0xBE (0x76D8C05A, 0xFFFFFFFFAA3A0005, 0xFFFFFFFF8039D810, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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
--------------------------------------------------------------------------------
45 crash dumps have been found and analyzed. Only 10 are included in this report. 4 third party drivers have 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 331.82 , NVIDIA Corporation)
fastfat.sys (Fast FAT File System Driver, Microsoft Corporation)
iastor.sys (Intel Rapid Storage Technology driver - x86, Intel Corporation)
?
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.
Re: Bluecreen
Bonjour,
Fais les tests pour le matériel, en particuler la mémoire RAM et le disque dur.
Fais les tests pour le matériel, en particuler la mémoire RAM et le disque dur.
Re: Bluecreen
Avec les outils indiqués dans le lien de mon message précédent : http://forum.malekal.com/tester-materie ... 44006.html