Bonjour à toutes et à tous,
Je vous demande de l'aide car mon PC enchaîne les BSOD (écran bleu) depuis hier.
Dès que j'accède à mon ouverture de session, le PC reste bloqué sur "Bienvenue" et finit par générer un BSOD. Sans que je n'y comprenne quoique ce soit.
Le PC fonctionne en mode sans échec avec Internet aussi. Je l'utilise pour vous envoyer tout ça.
Ce qui a été fait jusqu'ici:
Restauration du système => N'a rien changé au problème
J'ai essayé de vérifier mes drivers avec maconfig.com mais je ne peux plus faire de détection apparemment...
J'ai regardé sur internet et j'ai installé WhoCrashed.
Le problème c'est que je ne sais pas quoi faire avec le rapport que j'ai obtenu...
Je l'ai copié ici. Un problème récurrent est celui de ntoskrnl.exe, mais je ne suis pas plus avancé...
Bref, si une personne avait une idée, ça serait avec plaisir!
Merci beaucoup!
System Information (local)
Computer name: WAJDI-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: N56VZ, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 6322737152 bytes total
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 25/12/2015 15:36:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122515-28953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xFFA93)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000006, 0xFFFFF80003763A93, 0xFFFFF880085A2558, 0xFFFFF880085A1DB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 Fri 25/12/2015 15:36:04 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: 0x7E (0xFFFFFFFFC0000006, 0xFFFFF80003763A93, 0xFFFFF880085A2558, 0xFFFFF880085A1DB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 25/12/2015 15:34:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122515-24429-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Mon 06/04/2015 22:19:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040715-36285-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0x50 (0x7FFFFFDC000, 0x1, 0xFFFFF80003783469, 0x8)
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 Mon 23/02/2015 21:36:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022315-39983-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x80, 0x2, 0x1, 0xFFFFF800034CCF1F)
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 Sat 08/11/2014 17:31:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110814-32479-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8002573790, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 06/11/2014 12:00:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110614-34554-01.dmp
This was probably caused by the following module: igdkmd64.sys (0xFFFFF88007DA6069)
Bugcheck code: 0x50 (0xFFFFF8A010B668D4, 0x1, 0xFFFFF88007DA6069, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\igdkmd64.sys
product: Intel Graphics Accelerator Drivers for Windows 8(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
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: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: Intel Corporation PAGE_FAULT_IN_NONPAGED_AREA
On Fri 31/10/2014 22:22:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103114-34055-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41287, 0x30, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 11/10/2014 16:55:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101114-79201-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x80, 0x2, 0x1, 0xFFFFF80003488F1F)
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 Wed 17/07/2013 12:47:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071713-26707-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x78A7A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80051F7660, 0xFFFFF80003C073D0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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:
igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel 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.
