Ecran Bleu
Fermé
eykish
Messages postés
10
Date d'inscription
mercredi 19 août 2015
Statut
Membre
Dernière intervention
10 septembre 2015
-
19 août 2015 à 23:35
eykish Messages postés 10 Date d'inscription mercredi 19 août 2015 Statut Membre Dernière intervention 10 septembre 2015 - 10 sept. 2015 à 16:18
eykish Messages postés 10 Date d'inscription mercredi 19 août 2015 Statut Membre Dernière intervention 10 septembre 2015 - 10 sept. 2015 à 16:18
A voir également:
- Ecran Bleu
- Double ecran - Guide
- Écran bleu - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée
- Capture d'écran samsung - Guide
- Retourner ecran windows - Guide
16 réponses
Buenos74
Messages postés
4347
Date d'inscription
vendredi 20 avril 2012
Statut
Membre
Dernière intervention
13 février 2016
848
20 août 2015 à 03:06
20 août 2015 à 03:06
Slt,
config stp...
Quel(s) jeu(x) ?
config stp...
Quel(s) jeu(x) ?
eykish
Messages postés
10
Date d'inscription
mercredi 19 août 2015
Statut
Membre
Dernière intervention
10 septembre 2015
20 août 2015 à 12:44
20 août 2015 à 12:44
ma configuration : carte graphique Nvidia GeForce GTX 660, processeur intel core i5 3570, ram 8Go DDR3, carte mère Asustek computer inc. P8Z77-V LX.
j'ai eu ces problèmes en jouant a different jeux, par exemple Rust et Path of Exile recemment.
j'ai eu ces problèmes en jouant a different jeux, par exemple Rust et Path of Exile recemment.
Buenos74
Messages postés
4347
Date d'inscription
vendredi 20 avril 2012
Statut
Membre
Dernière intervention
13 février 2016
848
22 août 2015 à 01:11
22 août 2015 à 01:11
Slt,
télécharge ça et poste le rapport stp :
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/
télécharge ça et poste le rapport stp :
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/
eykish
Messages postés
10
Date d'inscription
mercredi 19 août 2015
Statut
Membre
Dernière intervention
10 septembre 2015
22 août 2015 à 11:10
22 août 2015 à 11:10
voila le rapport :
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 19/08/2015 20:38:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081915-14929-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0xA (0x7A800AD92528, 0x2, 0x0, 0xFFFFF8000314435F)
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 19/08/2015 20:38:39 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: 0xA (0x7A800AD92528, 0x2, 0x0, 0xFFFFF8000314435F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 19/08/2015 19:16:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081915-12870-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0xA (0x7A800C1A0560, 0x2, 0x0, 0xFFFFF80003074F38)
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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 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.
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 19/08/2015 20:38:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081915-14929-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0xA (0x7A800AD92528, 0x2, 0x0, 0xFFFFF8000314435F)
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 19/08/2015 20:38:39 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: 0xA (0x7A800AD92528, 0x2, 0x0, 0xFFFFF8000314435F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 19/08/2015 19:16:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081915-12870-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0xA (0x7A800C1A0560, 0x2, 0x0, 0xFFFFF80003074F38)
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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 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.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Buenos74
Messages postés
4347
Date d'inscription
vendredi 20 avril 2012
Statut
Membre
Dernière intervention
13 février 2016
848
23 août 2015 à 00:22
23 août 2015 à 00:22
Slt,
va ici :
https://www.driverscloud.com/fr/demarrer
Installe l'agent et démarre la détection, puis mets tes pilotes à jours si besoin.
va ici :
https://www.driverscloud.com/fr/demarrer
Installe l'agent et démarre la détection, puis mets tes pilotes à jours si besoin.
eykish
Messages postés
10
Date d'inscription
mercredi 19 août 2015
Statut
Membre
Dernière intervention
10 septembre 2015
24 août 2015 à 23:25
24 août 2015 à 23:25
je viens de subir un nouvel ecran bleu , voila le rapport WhoCrashed :
On Mon 24/08/2015 21:17:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082415-19546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF800030B17E0)
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 24/08/2015 21:17:26 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x292DF)
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF800030B17E0)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Mon 24/08/2015 21:17:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082415-19546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF800030B17E0)
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 24/08/2015 21:17:26 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x292DF)
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF800030B17E0)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
Buenos74
Messages postés
4347
Date d'inscription
vendredi 20 avril 2012
Statut
Membre
Dernière intervention
13 février 2016
848
25 août 2015 à 03:03
25 août 2015 à 03:03
Slt,
ok...
tes 8 go de Ram sont bien reconnus ? Barrette défectueuse ou mal installée ?
Qu'est-ce que tu as comme DD ou SSD ?
Tu as de la place pour augmenter la taille du fichier d'échange Ram-DD ?
ok...
tes 8 go de Ram sont bien reconnus ? Barrette défectueuse ou mal installée ?
Qu'est-ce que tu as comme DD ou SSD ?
Tu as de la place pour augmenter la taille du fichier d'échange Ram-DD ?
eykish
Messages postés
10
Date d'inscription
mercredi 19 août 2015
Statut
Membre
Dernière intervention
10 septembre 2015
25 août 2015 à 12:34
25 août 2015 à 12:34
salut,
mes 8go de Ram sont bien reconnus, j'ai utilisé le logiciel memtest86 ainsi que l'outil windows pour vérifier si mes barrettes sont défectueuses et je n'ai eu aucune erreur.
je n'ai pas encore essaye de les déplacées ou les réinstallées.
mon disque dur est un seagate SATA-600 1000go, st1000dm003-1ch162.
je ne connais pas cette manipulation. mon disque dur est séparé en deux partition d'environs 500go chacune, j'ai 412go libres sur la première et 217 go libres sur la seconde.
mes 8go de Ram sont bien reconnus, j'ai utilisé le logiciel memtest86 ainsi que l'outil windows pour vérifier si mes barrettes sont défectueuses et je n'ai eu aucune erreur.
je n'ai pas encore essaye de les déplacées ou les réinstallées.
mon disque dur est un seagate SATA-600 1000go, st1000dm003-1ch162.
je ne connais pas cette manipulation. mon disque dur est séparé en deux partition d'environs 500go chacune, j'ai 412go libres sur la première et 217 go libres sur la seconde.
Buenos74
Messages postés
4347
Date d'inscription
vendredi 20 avril 2012
Statut
Membre
Dernière intervention
13 février 2016
848
27 août 2015 à 03:28
27 août 2015 à 03:28
Slt,
ok...
Augmente le fichier d'échange sus-nommé :
--> Panneau de configuration\Tous les Panneaux de configuration\Système
--> Propriétés Système
--> Paramètres Systèmes Avancés
--> dans "Performances" --> Paramètres
--> Onglet "Avancé"
--> Mémoire virtuelle --> Modifier
--> Augmente la taille de celui-ci
Mets 16384 Mo comme valeur personnalisée...
"I am the Lizard King............... I can do everything"
Jim morrison (RIP)
ok...
Augmente le fichier d'échange sus-nommé :
--> Panneau de configuration\Tous les Panneaux de configuration\Système
--> Propriétés Système
--> Paramètres Systèmes Avancés
--> dans "Performances" --> Paramètres
--> Onglet "Avancé"
--> Mémoire virtuelle --> Modifier
--> Augmente la taille de celui-ci
Mets 16384 Mo comme valeur personnalisée...
"I am the Lizard King............... I can do everything"
Jim morrison (RIP)
eykish
Messages postés
10
Date d'inscription
mercredi 19 août 2015
Statut
Membre
Dernière intervention
10 septembre 2015
31 août 2015 à 14:50
31 août 2015 à 14:50
salut,
j'arrive a afficher la fenêtre pour modifier la valeur de la mémoire virtuelle.
premièrement je peux choisir pour chaque lecteur, de base le C: est géré par le système alors que le D: n'a aucun fichier d'échange.
ensuite j'ai beau selectionné le lecteur C: puis coché valeur personnalisée et inscrire 16384 Mo cela n'est pas pris en compte.
il est proposé deux valeurs , taille initiale et taille maximale, je choisis 16384 pour les deux valeurs ?
j'arrive a afficher la fenêtre pour modifier la valeur de la mémoire virtuelle.
premièrement je peux choisir pour chaque lecteur, de base le C: est géré par le système alors que le D: n'a aucun fichier d'échange.
ensuite j'ai beau selectionné le lecteur C: puis coché valeur personnalisée et inscrire 16384 Mo cela n'est pas pris en compte.
il est proposé deux valeurs , taille initiale et taille maximale, je choisis 16384 pour les deux valeurs ?
Buenos74
Messages postés
4347
Date d'inscription
vendredi 20 avril 2012
Statut
Membre
Dernière intervention
13 février 2016
848
2 sept. 2015 à 02:35
2 sept. 2015 à 02:35
Slt,
Mets le sur D...
Mets aucun fichier d'échanges sur C, sélectionne D puis "personnalisé" comme expliqué précédemment.
Mets le sur D...
Mets aucun fichier d'échanges sur C, sélectionne D puis "personnalisé" comme expliqué précédemment.
eykish
Messages postés
10
Date d'inscription
mercredi 19 août 2015
Statut
Membre
Dernière intervention
10 septembre 2015
3 sept. 2015 à 10:08
3 sept. 2015 à 10:08
salut,
j'ai fais comme tu m'as indique, aucun fichier d'échange sur C et valeur personnalisé sur D 12288-16384.
j'ai fais comme tu m'as indique, aucun fichier d'échange sur C et valeur personnalisé sur D 12288-16384.
Buenos74
Messages postés
4347
Date d'inscription
vendredi 20 avril 2012
Statut
Membre
Dernière intervention
13 février 2016
848
5 sept. 2015 à 02:03
5 sept. 2015 à 02:03
Slt,
Et ?
D'autres Blue Screen ??
Et ?
D'autres Blue Screen ??
eykish
Messages postés
10
Date d'inscription
mercredi 19 août 2015
Statut
Membre
Dernière intervention
10 septembre 2015
5 sept. 2015 à 02:30
5 sept. 2015 à 02:30
salut,
pour l'instant je n'ai pas eu d'autres blue screen.
pour l'instant je n'ai pas eu d'autres blue screen.
Buenos74
Messages postés
4347
Date d'inscription
vendredi 20 avril 2012
Statut
Membre
Dernière intervention
13 février 2016
848
Modifié par Buenos74 le 5/09/2015 à 02:38
Modifié par Buenos74 le 5/09/2015 à 02:38
ok....
C cool... Mais t'as le droit de le dire pour nous tenir au courant...
Croise les doigts et les doigts de pied....
;))
C cool... Mais t'as le droit de le dire pour nous tenir au courant...
Croise les doigts et les doigts de pied....
;))
eykish
Messages postés
10
Date d'inscription
mercredi 19 août 2015
Statut
Membre
Dernière intervention
10 septembre 2015
5 sept. 2015 à 10:41
5 sept. 2015 à 10:41
merci bien, je vous tiendrai au courant s'il ya une rechute.
eykish
Messages postés
10
Date d'inscription
mercredi 19 août 2015
Statut
Membre
Dernière intervention
10 septembre 2015
10 sept. 2015 à 16:18
10 sept. 2015 à 16:18
salut,
mon pc a eu une rechute, un nouvel écran bleu IRQL .
voila le rapport whocrashed :
Computer name: LACHOSE
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-3570 CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8537497600 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 10/09/2015 14:06:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091015-27346-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0xA (0xFFFFFA801AF56010, 0x2, 0x1, 0xFFFFF8000314C2E6)
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 10/09/2015 14:06:09 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: 0xA (0xFFFFFA801AF56010, 0x2, 0x1, 0xFFFFF8000314C2E6)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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 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.
mon pc a eu une rechute, un nouvel écran bleu IRQL .
voila le rapport whocrashed :
Computer name: LACHOSE
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-3570 CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8537497600 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 10/09/2015 14:06:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091015-27346-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0xA (0xFFFFFA801AF56010, 0x2, 0x1, 0xFFFFF8000314C2E6)
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 10/09/2015 14:06:09 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: 0xA (0xFFFFFA801AF56010, 0x2, 0x1, 0xFFFFF8000314C2E6)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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 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.