PROBLEMA Blue Screen Of Death - Pc Portatile

diego.colo

Nuovo Utente
6
0
Buonasera

E' da quasi una settimana che il mio pc portatile Acer Aspire 5732z, ogni volta che viene accesso, dopo qualche minuto dall'accesso all'account mostra il Blue Screen, oppure si riavvia improvvisamente.

Adesso lo sto utilizzando in modalità provvisoria e, con l'ausilio di un Hard Disk esterno, sono riuscito a salvare tutti i file importanti. Dopodiché ho formattato il pc e ora è come nuovo, senza nessun programma installato...

Tuttavia il problema persiste ancora, seppur con meno frequenza.
Cosa posso fare?

Si è creato un file Minidump, ma io non so leggerlo.
Ve lo posto qui.

Visualizza allegato Minidump.zip

Grazie in anticipo.

PS: Io non sono molto bravo con queste cose, anche perché è la prima volta che mi capita. :sisi:
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,207
6,218
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 7 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows10x64pro
Posta il DMP letto con whocrashed
 

diego.colo

Nuovo Utente
6
0
Ecco quello che ho trovato utilizzando WhoCrashed:

"[FONT=Segoe UI, Arial]System Information (local)
[/FONT]
[FONT=Segoe UI, Arial]computer name: PC_DI_DIEGO
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: Aspire 5732Z , Acer
CPU: GenuineIntel Pentium(R) Dual-Core CPU T4400 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4221542400 total


[/FONT]
[FONT=Segoe UI, Arial]
Crash Dump Analysis

[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 03/11/2014 18:44:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110314-28735-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]athrx.sys[/FONT] (athrx+0x9580D)
Bugcheck code: 0xD1 (0x64, 0x2, 0x1, 0xFFFFF880040FA80D)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\athrx.sys
product: [FONT=Segoe UI, Arial]Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter[/FONT]
company: [FONT=Segoe UI, Arial]Atheros Communications, Inc.[/FONT]
description: Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: [FONT=Segoe UI, Arial]Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Mon 03/11/2014 18:44:06 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]athrx.sys[/FONT] (athrx+0x9580D)
Bugcheck code: 0xD1 (0x64, 0x2, 0x1, 0xFFFFF880040FA80D)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\athrx.sys
product: [FONT=Segoe UI, Arial]Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter[/FONT]
company: [FONT=Segoe UI, Arial]Atheros Communications, Inc.[/FONT]
description: Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: [FONT=Segoe UI, Arial]Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]
Conclusion

[/FONT]
[FONT=Segoe UI, Arial]2 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:

[FONT=Segoe UI, Arial]athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)[/FONT]

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is 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. "
[/FONT]
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,207
6,218
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 7 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows10x64pro
Ecco quello che ho trovato utilizzando WhoCrashed:

"[FONT=Segoe UI, Arial]System Information (local)
[/FONT]
[FONT=Segoe UI, Arial]computer name: PC_DI_DIEGO
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: Aspire 5732Z , Acer
CPU: GenuineIntel Pentium(R) Dual-Core CPU T4400 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4221542400 total


[/FONT]
[FONT=Segoe UI, Arial]
Crash Dump Analysis

[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 03/11/2014 18:44:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110314-28735-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]athrx.sys[/FONT] (athrx+0x9580D)
Bugcheck code: 0xD1 (0x64, 0x2, 0x1, 0xFFFFF880040FA80D)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\athrx.sys
product: [FONT=Segoe UI, Arial]Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter[/FONT]
company: [FONT=Segoe UI, Arial]Atheros Communications, Inc.[/FONT]
description: Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: [FONT=Segoe UI, Arial]Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Mon 03/11/2014 18:44:06 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]athrx.sys[/FONT] (athrx+0x9580D)
Bugcheck code: 0xD1 (0x64, 0x2, 0x1, 0xFFFFF880040FA80D)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\athrx.sys
product: [FONT=Segoe UI, Arial]Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter[/FONT]
company: [FONT=Segoe UI, Arial]Atheros Communications, Inc.[/FONT]
description: Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: [FONT=Segoe UI, Arial]Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]
Conclusion

[/FONT]
[FONT=Segoe UI, Arial]2 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:

[FONT=Segoe UI, Arial]athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)[/FONT]

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is 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. "
[/FONT]
Sembrano le RAM testuale x qualche ora con memtestx86 e aggiorna i driver del wireless potrebbero fare qualche noia
 

lions1991

Nuovo Utente
75
3
Ecco quello che ho trovato utilizzando WhoCrashed:

"System Information (local)
computer name: PC_DI_DIEGO
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: Aspire 5732Z , Acer
CPU: GenuineIntel Pentium(R) Dual-Core CPU T4400 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4221542400 total




Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 03/11/2014 18:44:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110314-28735-01.dmp
This was probably caused by the following module: athrx.sys (athrx+0x9580D)
Bugcheck code: 0xD1 (0x64, 0x2, 0x1, 0xFFFFF880040FA80D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\athrx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Mon 03/11/2014 18:44:06 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: athrx.sys (athrx+0x9580D)
Bugcheck code: 0xD1 (0x64, 0x2, 0x1, 0xFFFFF880040FA80D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\athrx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL




Conclusion

2 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:

athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is 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. "

Dal dump si evince un problema del driver della scheda di rete wireless lan, il mio consiglio è di disinstallarlo completamente tramite Revo Unistaller oppure iObit così facendo sei sicuro di eliminare qualsiasi voce o chiave anche dal registro di sistema ed evitare di creare conflitti con i nuovi driver che andrai ad installare. Per sicurezza lancia anche Ccleaner (ultima versione) ed effettua una scansione al registro di sistema, sicuramente anche lui troverà qualche chiave danneggiata od obsoleta, dopodichè riavvia il pc e scarica ed installa dal sito ufficiale del produttore della scheda di rete i nuovi driver. Facci sapere.
Enter Cookie as format:
(ex: name=val;) separate with ';'

OKCancel
 
Ultima modifica:

diego.colo

Nuovo Utente
6
0
Rieccomi! :)

Intanto ringrazio tutti per le pronte risposte.

Allora, ho scaricato DriverBooster2 da iObit e ho aggiornato tutti i driver. Ho disinstallato la mia scheda di rete wireless Atheros AR5B93. Poi si è reinstallata da sola al riavvio ma si è ripresentato il Blue Screen.

Ho riutilizzato WhoCrashed ed ecco il nuovo esito:

"[FONT=Segoe UI, Arial]Crash Dump Analysis
[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Tue 04/11/2014 15:20:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110414-25927-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x71F00)
Bugcheck code: 0x1A (0x41287, 0xEBFFFD95F4, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 04/11/2014 15:20:29 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41287, 0xEBFFFD95F4, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]
Conclusion

[/FONT]
[FONT=Segoe UI, Arial]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. "
[/FONT]
Mi sembra diverso rispetto a quello dell'ultima volta. Ci sono altri problemi? D:

Vi ringrazio ancora per la disponibilità
 

lions1991

Nuovo Utente
75
3
Rieccomi! :)

Intanto ringrazio tutti per le pronte risposte.

Allora, ho scaricato DriverBooster2 da iObit e ho aggiornato tutti i driver. Ho disinstallato la mia scheda di rete wireless Atheros AR5B93. Poi si è reinstallata da sola al riavvio ma si è ripresentato il Blue Screen.

Ho riutilizzato WhoCrashed ed ecco il nuovo esito:

"Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 04/11/2014 15:20:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110414-25927-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41287, 0xEBFFFD95F4, 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 Tue 04/11/2014 15:20:29 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: 0x1A (0x41287, 0xEBFFFD95F4, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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.




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

Mi sembra diverso rispetto a quello dell'ultima volta. Ci sono altri problemi? D:

Vi ringrazio ancora per la disponibilità

Il test alle memorie Ram già lo hai eseguito ? In che stato è messo il disco rigido ?
Testalo con Crystaldiskinfo e HD tune entrambi sono ottimi tools. Ciao
 

diego.colo

Nuovo Utente
6
0
Il Disco Rigido dice che è in stato "Buono" (ho allegato l'immagine con tutti i dati scritti, che magari voi capite di più di me (ci vuole poco! xD) ).
CrystalDisk.png

Il test della memorie Ram è il Memtest86?
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,207
6,218
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 7 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows10x64pro
Si è memtest86
 

diego.colo

Nuovo Utente
6
0
Eccomi di nuovo! :)

Allora, ho fatto il Memtest86 e mi ha detto che non ci sono errori.

I Blue Screen continuano a presentarsi... D:
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,207
6,218
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 7 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows10x64pro
Fai uno scandisk con i parametri /f /r
 

diego.colo

Nuovo Utente
6
0
Ho eseguito uno ScanDisk dell'Hard Disk principale impostando anche "Cerca i settori danneggiati e tenta di ripararli"... Ma il problema persiste...
In che senso mettere i parametri /f /r? (Scusa la mia ignoranza in materia D: )
 

Entra

oppure Accedi utilizzando

Hot: E3 2021, chi ti è piaciuto di più?

  • Ubisoft

    Voti: 14 16.1%
  • Gearbox

    Voti: 1 1.1%
  • Xbox & Bethesda

    Voti: 62 71.3%
  • Square Enix

    Voti: 3 3.4%
  • Capcom

    Voti: 5 5.7%
  • Nintendo

    Voti: 13 14.9%
  • Altro (Specificare)

    Voti: 7 8.0%