Ecran bleu, rapport d'analyse, aidez moi svp :)
SamiGH
Messages postés
5
Date d'inscription
Statut
Membre
Dernière intervention
-
Malekal_morte- Messages postés 180304 Date d'inscription Statut Modérateur, Contributeur sécurité Dernière intervention -
Malekal_morte- Messages postés 180304 Date d'inscription Statut Modérateur, Contributeur sécurité Dernière intervention -
Salut à tous, ça fait quelque jours que j'ai commencé a avoir des écrans bleus, je m'y connais pas à fond en informatique et j'aimerais savoir si c'était possible d'avoir de l'aide pour résoudre ces problèmes par étape. Merci d'avance !
Voilà la crash dump analyze:
System Information (local)
--------------------------------------------------------------------------------
Computer name: SAMI-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., P8Z77-V LX
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8540065792 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 14.10.2015 12:54:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101415-33368-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x50 (0xFFFFFAC00CE04BC0, 0x0, 0xFFFFF80002CE5D80, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 14.10.2015 12:54:52 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFFAC00CE04BC0, 0x0, 0xFFFFF80002CE5D80, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 14.10.2015 09:28:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101415-19219-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x19 (0x3, 0xFFFFFA800CD5ACB0, 0xFFFFFA800CD5ACB0, 0xFFFFFAC00CD5ACB0)
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 13.10.2015 20:03:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101315-15802-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x109 (0xA3A039D89E9D550F, 0x0, 0x290239510F6BC474, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Fri 09.10.2015 09:18:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100915-15990-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002CC5510)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Thu 08.10.2015 16:32:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100815-12573-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x37F3C)
Bugcheck code: 0x50 (0xFFFFFAC00C2A2D88, 0x1, 0xFFFFF880051AEEFF, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 Thu 08.10.2015 15:36:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100815-19188-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF88005D34E6B)
Bugcheck code: 0x50 (0xFFFFFAC00AFFD088, 0x0, 0xFFFFF88005D34E6B, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 353.62
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 353.62
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.
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 353.62 , NVIDIA Corporation).
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA
On Sun 27.09.2015 11:31:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092715-11029-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x109 (0xA3A039D89E9D5560, 0x0, 0xB8B70B9823B13D02, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Wed 23.09.2015 11:45:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092315-14539-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x109 (0xA3A039D89E9D1642, 0x0, 0x65C9FEE7215A1C1, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Mon 21.09.2015 20:29:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092115-10186-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFFA800CD57750)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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.
--------------------------------------------------------------------------------
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 353.62 , NVIDIA Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Voilà la crash dump analyze:
System Information (local)
--------------------------------------------------------------------------------
Computer name: SAMI-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., P8Z77-V LX
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8540065792 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 14.10.2015 12:54:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101415-33368-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x50 (0xFFFFFAC00CE04BC0, 0x0, 0xFFFFF80002CE5D80, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 14.10.2015 12:54:52 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFFAC00CE04BC0, 0x0, 0xFFFFF80002CE5D80, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 14.10.2015 09:28:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101415-19219-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x19 (0x3, 0xFFFFFA800CD5ACB0, 0xFFFFFA800CD5ACB0, 0xFFFFFAC00CD5ACB0)
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 13.10.2015 20:03:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101315-15802-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x109 (0xA3A039D89E9D550F, 0x0, 0x290239510F6BC474, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Fri 09.10.2015 09:18:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100915-15990-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002CC5510)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Thu 08.10.2015 16:32:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100815-12573-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x37F3C)
Bugcheck code: 0x50 (0xFFFFFAC00C2A2D88, 0x1, 0xFFFFF880051AEEFF, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 Thu 08.10.2015 15:36:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100815-19188-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF88005D34E6B)
Bugcheck code: 0x50 (0xFFFFFAC00AFFD088, 0x0, 0xFFFFF88005D34E6B, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 353.62
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 353.62
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.
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 353.62 , NVIDIA Corporation).
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA
On Sun 27.09.2015 11:31:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092715-11029-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x109 (0xA3A039D89E9D5560, 0x0, 0xB8B70B9823B13D02, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Wed 23.09.2015 11:45:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092315-14539-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x109 (0xA3A039D89E9D1642, 0x0, 0x65C9FEE7215A1C1, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Mon 21.09.2015 20:29:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092115-10186-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFFA800CD57750)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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.
--------------------------------------------------------------------------------
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 353.62 , NVIDIA Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
A voir également:
- Ecran bleu, rapport d'analyse, aidez moi svp :)
- Supprimer rond bleu whatsapp - Guide
- Double ecran - Guide
- Écran bleu - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée
- Retourner ecran pc - Guide
6 réponses
Salut,
oui je les mets à jour quotidiennement, j'ai peut-être fais 2 ou 3 MaJ depuis que j'ai ces soucis d'écran bleu
oui je les mets à jour quotidiennement, j'ai peut-être fais 2 ou 3 MaJ depuis que j'ai ces soucis d'écran bleu
la restauration système a pas fonctionnée. ça a rencontré une erreur indeterminée...
pour résoudre mon problème je devrais peut etre mettre a jour mon BIOS je pense, non? sauf que je sais pas comment faire
pour résoudre mon problème je devrais peut etre mettre a jour mon BIOS je pense, non? sauf que je sais pas comment faire
Tu peux toujours tenter pour le BIOS.
Regarde aussi les conseils de ce sujet : Comprendre les BSOD.
Tenter de désinstaller l'antivirus.
Démarrer en Windows minimal etc.
Regarde aussi les conseils de ce sujet : Comprendre les BSOD.
Tenter de désinstaller l'antivirus.
Démarrer en Windows minimal etc.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Salut,
les messages bleus continuent, je sais pas comment m'y prendre...
le crash test:
On Sun 01.11.2015 00:09:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110115-19936-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x109 (0xA3A039D89E9D453A, 0x0, 0xB4EF8D4BF43F4161, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Sat 31.10.2015 17:34:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103115-19578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x109 (0xA3A039D89E9D3820, 0x0, 0x4D92E00435CBE66, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Fri 30.10.2015 00:54:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103015-16629-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x109 (0xA3A039D89E9D8584, 0x0, 0x24EA3ED5CD7871ED, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Thu 29.10.2015 09:20:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102915-15600-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x34 (0x50853, 0xFFFFF8800377E688, 0xFFFFF8800377DEE0, 0xFFFFF80002F7E20B)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
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.10.2015 21:31:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102715-16707-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x50 (0xFFFFF80003400000, 0x0, 0xFFFFFA800CD5769B, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 23.10.2015 22:42:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102415-19515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002D134F0)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 19.10.2015 20:26:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101915-11544-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0xD1 (0xFFFFF8C000EBA1B0, 0x2, 0x8, 0xFFFFF8C000EBA1B0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 17.10.2015 12:20:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101715-22666-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x109 (0xA3A039D89E9D66F4, 0x0, 0xECF148203AE9B41, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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.
les messages bleus continuent, je sais pas comment m'y prendre...
le crash test:
On Sun 01.11.2015 00:09:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110115-19936-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x109 (0xA3A039D89E9D453A, 0x0, 0xB4EF8D4BF43F4161, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Sat 31.10.2015 17:34:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103115-19578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x109 (0xA3A039D89E9D3820, 0x0, 0x4D92E00435CBE66, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Fri 30.10.2015 00:54:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103015-16629-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x109 (0xA3A039D89E9D8584, 0x0, 0x24EA3ED5CD7871ED, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Thu 29.10.2015 09:20:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102915-15600-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x34 (0x50853, 0xFFFFF8800377E688, 0xFFFFF8800377DEE0, 0xFFFFF80002F7E20B)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
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.10.2015 21:31:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102715-16707-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x50 (0xFFFFF80003400000, 0x0, 0xFFFFFA800CD5769B, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 23.10.2015 22:42:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102415-19515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002D134F0)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 19.10.2015 20:26:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101915-11544-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0xD1 (0xFFFFF8C000EBA1B0, 0x2, 0x8, 0xFFFFF8C000EBA1B0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 17.10.2015 12:20:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101715-22666-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x109 (0xA3A039D89E9D66F4, 0x0, 0xECF148203AE9B41, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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.
Bonsoir,
driver incompatible peut afficher un écran BSOD
programme incompatible peut afficher un écran BSOD exemple un jeux gourmand en pixel processeurs , RAM , carte graphique ne supportent pas le jeux
matériel incompatible peut afficher un écran BSOD exemple ajout d'une barrette de mémoire ou modification de la carte graphique etc
anomalie fichiers du système peut afficher un écran BSOD
anomalie dans le disque dur principal peut afficher un écran BSOD
depuis quelques jours que votre écran affiche plusieurs fois un BSOD vous avez modifié quelque chose dans le système " machine "
vous n'avez rien modifier ni pousser Windows a se crasher alors c'est un problème HARDWARE le plus souvent dans la ligne de mire le disque dur principal de temps en temps une barrette qui jette l'éponge , parfois un ventilateur qui a du mal a évacuer la chaleur , une petite pincée de hausse de chaleur exemple ->CPU Pâte thermique .
driver incompatible peut afficher un écran BSOD
programme incompatible peut afficher un écran BSOD exemple un jeux gourmand en pixel processeurs , RAM , carte graphique ne supportent pas le jeux
matériel incompatible peut afficher un écran BSOD exemple ajout d'une barrette de mémoire ou modification de la carte graphique etc
anomalie fichiers du système peut afficher un écran BSOD
anomalie dans le disque dur principal peut afficher un écran BSOD
depuis quelques jours que votre écran affiche plusieurs fois un BSOD vous avez modifié quelque chose dans le système " machine "
vous n'avez rien modifier ni pousser Windows a se crasher alors c'est un problème HARDWARE le plus souvent dans la ligne de mire le disque dur principal de temps en temps une barrette qui jette l'éponge , parfois un ventilateur qui a du mal a évacuer la chaleur , une petite pincée de hausse de chaleur exemple ->CPU Pâte thermique .
