BSOD aléatoires sur laptop

Recherche :

Mot : Pseudo : Filtrer
Bas de page
Auteur	Sujet : BSOD aléatoires sur laptop

fafane84

Salut à tous !

Depuis peu, je rencontre des problèmes aléatoires de BSOD au démarrage sur mon PC Portable ACER A515-43-R9M8 acheter en mai 2020.

Les écrans bleus interviennent au démarrage ce qui provoque un redémarrage du laptop (quelquefois 2 redemarrages) et ensuite tout fonctionne correctement.

En cherchant un peu sur Internet, j'ai lu que cela pouvait être provoqué par un driver obsolète et qu'une simple mise à jour pouvait régler ce problème.

J'ai donc installer BlueScreenView dont voici le rapport :

Citation :

==================================================
Dump File : 083020-7468-01.dmp
Crash Time : 30/08/2020 10:17:06
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000020
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff806`734305c3
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c23c0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+1c23c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\083020-7468-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 18362
Dump File Size : 740 676
Dump File Time : 30/08/2020 10:18:46
==================================================

Seulement voilà le driver ne semble pas identifier.

Comment trouver la cause du problème ?

J'ai réussi à sortir la liste des drivers, mais il y en a tellement, que je ne sais comment trouver le défectueux.

Merci d'avance pour votre aide.

---------------
Mon Topic de Vente Hardware

Publicité

nex84

Dura lex, sed lex

Regarde dans les journaux d'événements de Windows aux heures où ça se produit pour voir si tu as des erreurs qui expliqueraient le BSOD.

Regarde aussi si tu as des warnings dans le gestionnaire de périphériques (et met aussi tous tes drivers à jour).

Dans le même temps, peux tu poster le rapport généré par le logiciel Whocrashed ?

Message cité 1 fois

---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts

fafane84

Salut et merci pour ton aide.

Désolé de ne pas t'avoir répondu plus t^to mais j'ai eu un décés dans la famille et je n'ai pas eu le temps de m'occuper de ce problème.

nex84 a écrit :

Regarde dans les journaux d'événements de Windows aux heures où ça se produit pour voir si tu as des erreurs qui expliqueraient le BSOD.

Je n'ai pas trouvé à l'heure exacte, mais peu après : "L’arrêt système précédant à 10:17:00 le ‎30/‎08/‎2020 n’était pas prévu."

Citation :

Nom du journal :System
Source : EventLog
Date : 30/08/2020 10:18:27
ID de l’événement :6008
Catégorie de la tâche :Aucun
Niveau : Erreur
Mots clés : Classique
Utilisateur : N/A
Ordinateur : LAPTOP-PM96AGQK
Description :
L’arrêt système précédant à 10:17:00 le ‎30/‎08/‎2020 n’était pas prévu.
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-08-30T08:18:27.430753200Z" />
<EventRecordID>28189</EventRecordID>
<Channel>System</Channel>
<Computer>LAPTOP-PM96AGQK</Computer>
<Security />
</System>
<EventData>
<Data>10:17:00</Data>
<Data>‎30/‎08/‎2020</Data>
<Data>
</Data>
<Data>
</Data>
<Data>7</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>E407080000001E000A0011000000A701E407080000001E00080011000000A7013C0000003C000000000000000000000000000000000000000100000000000000</Binary>
</EventData>
</Event>

nex84 a écrit :

Regarde aussi si tu as des warnings dans le gestionnaire de périphériques (et met aussi tous tes drivers à jour).

Non pas de warning.
Mettre tous les drivers à jour, il y en a tellement !!!
Existe-il un logiciel qui pourrait me dire quels drivers ne sont pas à jour ?

nex84 a écrit :

Dans le même temps, peux tu poster le rapport généré par le logiciel Whocrashed ?

Citation :

Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. Only 5 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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:

qcamain1.sys

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.

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 Topic de Vente Hardware

nex84

Dura lex, sed lex

Il faudrait le rapport complet de Whocrashed.
Mais à priori ça viendrait du chipset Wifi Atheros. Tu peux peut-être commencer par mettre à jour celui-là.

Message cité 1 fois

---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts

fafane84

Merci beaucoup [:b-rabbit]

nex84 a écrit :

Il faudrait le rapport complet de Whocrashed.

A priori, pour cela il faut la version payante

nex84 a écrit :

Mais à priori ça viendrait du chipset Wifi Atheros. Tu peux peut-être commencer par mettre à jour celui-là.

qcamain1.sys ?

Cela fait plusieurs jours que cela ne s'est reproduit, mais je doute que ce type de crash se résolve tout seul.
Je vais m'orienter sur la piste Atheros, mais Windows Update ne devrait pas me signaler une mise à jour ?

Message cité 1 fois
Message édité par fafane84 le 07-09-2020 à 09:48:21

---------------
Mon Topic de Vente Hardware

nex84

Dura lex, sed lex

fafane84 a écrit :

A priori, pour cela il faut la version payante

Euh non, il n'y a pas de raison.

---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts

fafane84

Ah bin alors je n'ai pas trouvé comment le générer.

L'anglais et moi on n'est pas copain.

Message édité par fafane84 le 07-09-2020 à 10:17:40

---------------
Mon Topic de Vente Hardware

nex84

Dura lex, sed lex

Une fois que tu as lancé l'analyse, il t'affiche le rapport.
Il faut tout copier/coller, et pas seulement la conclusion.

---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts

fafane84

Ah d'accord !!!

J'essaye de faire çà ce soir.

---------------
Mon Topic de Vente Hardware

fafane84

Ce soir au démarrage çà l'a refait.

Voici le rapport :

Citation :

System Information (local)
--------------------------------------------------------------------------------

Computer name: LAPTOP-xxxxxxxx
Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\Windows
Hardware: Aspire A515-43, Acer, PK, Grumpy_PK
CPU: AuthenticAMD AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx AMD8664, level: 23
8 logical processors, active mask: 255
RAM: 6378106880 bytes (5,9GB)

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Mon 07/09/2020 21:17:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090720-7437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23C0)
Bugcheck code: 0xA (0x20, 0x2, 0x1, 0xFFFFF8062C6305C3)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 07/09/2020 21:17:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0xE018D)
Bugcheck code: 0xA (0x20, 0x2, 0x1, 0xFFFFF8062C6305C3)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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: qcamain1.sys .
Google query: qcamain1.sys IRQL_NOT_LESS_OR_EQUAL

On Thu 03/09/2020 18:11:47 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090320-8312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23C0)
Bugcheck code: 0xA (0x20, 0x2, 0x1, 0xFFFFF8011B4A8477)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 03/09/2020 16:55:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090320-8140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23C0)
Bugcheck code: 0xA (0x20, 0x2, 0x1, 0xFFFFF8030EC305C3)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 30/08/2020 10:17:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\083020-7468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23C0)
Bugcheck code: 0xA (0x20, 0x2, 0x1, 0xFFFFF806734305C3)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\Minidump\083020-7453-01.dmp

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. Only 5 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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:

qcamain1.sys

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.

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 Topic de Vente Hardware

Publicité

nex84

Dura lex, sed lex

Je confirme que ça a un rapport avec ton chipset Wifi Atheros.
Tu as essayé de le mettre à jour ?

---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts

fafane84

Salut !

Non pas encore, j'attendais la confirmation.

Par contre je l'ai téléchargé. Çà n'a d'ailleurs pas été facile d'identifier le bon, mais je pense y être arrivé.

Normalement, je devrai l'installer ce soir.

---------------
Mon Topic de Vente Hardware

fafane84

Voilà !

Driver mis à jour.

Wait and see.

---------------
Mon Topic de Vente Hardware

fafane84

Çà n'a pas fonctionné.

BSOD hier à 22h25 :

Citation :

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Wed 09/09/2020 22:25:11 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090920-8437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23C0)
Bugcheck code: 0xA (0x20, 0x2, 0x1, 0xFFFFF80007A305C3)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 09/09/2020 22:25:11 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0xE0CBD)
Bugcheck code: 0xA (0x20, 0x2, 0x1, 0xFFFFF80007A305C3)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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: qcamain1.sys .
Google query: qcamain1.sys IRQL_NOT_LESS_OR_EQUAL

On Mon 07/09/2020 21:17:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090720-7437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23C0)
Bugcheck code: 0xA (0x20, 0x2, 0x1, 0xFFFFF8062C6305C3)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 03/09/2020 18:11:47 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090320-8312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23C0)
Bugcheck code: 0xA (0x20, 0x2, 0x1, 0xFFFFF8011B4A8477)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 03/09/2020 16:55:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090320-8140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23C0)
Bugcheck code: 0xA (0x20, 0x2, 0x1, 0xFFFFF8030EC305C3)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 30/08/2020 10:17:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\083020-7468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23C0)
Bugcheck code: 0xA (0x20, 0x2, 0x1, 0xFFFFF806734305C3)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

qcamain1.sys

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.

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 Topic de Vente Hardware

nex84

Dura lex, sed lex

Il y a vraiment un truc que le driver n'aime pas...

C'est un chipset intégrée à la carte mère ?
Tu peux essayer en désactivant la carte, pour voir si ça continue.

---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts

fafane84

C'est un PC Portable donc j'imagine que c'est un chipset intégré.

Je désactive la carte wifi dans le gestionnaire de périphérique ?

Bien sûr si je fais çà, je n'aurai plus de connexion Internet, n'est-ce pas ?

Message cité 1 fois

---------------
Mon Topic de Vente Hardware

nex84

Dura lex, sed lex

fafane84 a écrit :

Soit dans le BIOS/UEFI s'il le permet, soit dans le gestionnaire de périphérique.
En tout cas oui, ça suppose que tu te connectes en RJ45 ou via un dongle Wifi USB en attendant, ou encore que tu sois déconnecté le temps suffisant pour tester.

---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts

fafane84

Salut !

Je n'ai pas désactivé la carte WiFi, mais ce matin, 2 BSOD.

A priori le driver Qualcom n'est plus mentionné dans le rapport :

Citation :

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sun 13/09/2020 07:44:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091320-9593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2990)
Bugcheck code: 0x139 (0x3, 0xFFFFF08CE9E7B600, 0xFFFFF08CE9E7B558, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 13/09/2020 07:44:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8219)
Bugcheck code: 0x139 (0x3, 0xFFFFF08CE9E7B600, 0xFFFFF08CE9E7B558, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 13/09/2020 07:41:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091320-7765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2990)
Bugcheck code: 0xA (0x20, 0x2, 0x1, 0xFFFFF8077DE305C3)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 12/09/2020 07:52:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091220-8437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2990)
Bugcheck code: 0x139 (0x3, 0xFFFF8389F8D87450, 0xFFFF8389F8D873A8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 12/09/2020 07:49:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091220-8015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2990)
Bugcheck code: 0xA (0x71, 0x2, 0x1, 0xFFFFF80214CA7647)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 12/09/2020 07:47:12 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091220-8140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2990)
Bugcheck code: 0xA (0x20, 0x2, 0x1, 0xFFFFF8040E0305C3)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 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.

Cà viendrait de W10 (problème logiciel) ou d'un problème matériel ?

---------------
Mon Topic de Vente Hardware

nex84

Dura lex, sed lex

Que te donne la commande sfc /scannow lancée en mode admin ?

Message cité 1 fois
Message édité par nex84 le 14-09-2020 à 09:41:04

---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts

fafane84

nex84 a écrit :

Que te donne la commande sfc /scannow lancée en mode admin ?

Citation :

C:\Windows\system32>sfc /scannow

Début de l’analyse du système. Cette opération peut nécessiter un certain temps.

Démarrage de la phase de vérification de l’analyse du système.
La vérification est à 100% terminée.

Le programme de protection des ressources Windows n’a trouvé aucune violation d’intégrité.

C:\Windows\system32>

A priori, pas grand chose :??:

En tout cas merci pour ta patience

Message édité par fafane84 le 14-09-2020 à 21:06:23

---------------
Mon Topic de Vente Hardware

nex84

Dura lex, sed lex

C'est embêtant, car la seule raison qui reste est un problème matériel.
Et sur un portable, ça veut dire SAV et/ou remplacement...

---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts

fafane84

Salut et merci encore pour ta réponse [:b-rabbit]

Le problème est qu'avant de le ramener au SAV, j'aimerai être sûr de la panne, car sinon je sais comment cela va se passer, ils ne trouveront pas, me diront que c'est réparé et j'aurai perdu 1 mois pour rien car le problème reviendra tôt ou tard.

Je préférerai tout compte fait que la carte me lâche complètement.

Ce serai plus simple.

Et si je désinstalle le driver au redémarrage il se réinstalle en version d'origine ?
Çà ne risque rien ?

Message édité par fafane84 le 15-09-2020 à 17:42:32

---------------
Mon Topic de Vente Hardware

nex84

Dura lex, sed lex

Si tu désinstalles un pilote et que tu redémarres, Windows va tenter de réinstaller la dernière version de Windows Update.

Ça peut éventuellement corriger le souci si ça vient du driver.
Pour moi le seul risque est de se retrouver avec un driver plus ancien ayant moins de fonctionnalités.

---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts

Publicité

FORUM HardWare.fr

Windows & Software

Win 10

BSOD aléatoires sur laptop

Sujets relatifs
Plantage aléatoire sans BSOD	plantage Windows 10 sans BSOD
[RESOLUE] Laptop restart tout seul, après migration Windows 7 à 10.	LAPTOP : Mise en veille ne fonctionne pas sur une installation en UEFI
[résolu] BSOD sur nouvelle config (c'était le CPU !)	BSOD "Bugcode ndis driver"
BSOD Multiples en quelques jours	Bsod après maj windows 10
BSOD lié à ntkrnlmp.exe / IRQL NOT LESS OR EQUAL	BSOD THREAD_STUCK_IN_DEVICE_DRIVER_M
Plus de sujets relatifs à : BSOD aléatoires sur laptop

Page générée en 0.094 secondes