- 271
- 7
- CPU
- Intel Core i5 660 3.30
- Scheda Madre
- ASrock H55M-LE (socket 1156)
- RAM
- 4 GB
- GPU
- R7 240 2GB
- PSU
- VulTec 500w
- Case
- Aerocool xWarrior Devil red
- OS
- Windows 10 Pro N
ciao. il mio pc va continuamente in bsod, non so più che fare.
lo fa casualmente: a volte giocando, a volte lavorando (ho perso un'ora e mezzo di lavoro su adobe illustrator per un esame mannagggggg ), e a volte semplicemente sul desktop.
Ho provato a formattare, fare 9 ore di memtest86+ senza risultati, riparare l'hard disk (via comandi da terminale), ma niente
sto impazzendo
che poi per arrivare da lord gwyn ci vuole una vita e quando crasho nell'arena sclero
il mio hardware è:
-AMD Radeon r7 240 (non dovrebbe essere il problema siccome lo faceva anche prima, con una HD 6450)
-ASRock H55M-LE
-4GB RAM nanya elixir
-500w PSU VulTec
-Intel i5 660 3.30Ghz
(serve altro?)
posto gli ultimi bsod registrati da whocrashed:
ultimamente ho notato una certa varietà nelle cause dei bsod, fino a qualche tempo fa la causa era sempre ntoskrnl.exe, e non saprei identificare il motivo di questo cambiamento.
aggiungo inoltre che ho appena scoperto ed attivato la funzione dei dump completi, quindi appena ne avrò li posterò.
lo fa casualmente: a volte giocando, a volte lavorando (ho perso un'ora e mezzo di lavoro su adobe illustrator per un esame mannagggggg ), e a volte semplicemente sul desktop.
Ho provato a formattare, fare 9 ore di memtest86+ senza risultati, riparare l'hard disk (via comandi da terminale), ma niente
sto impazzendo
che poi per arrivare da lord gwyn ci vuole una vita e quando crasho nell'arena sclero
il mio hardware è:
-AMD Radeon r7 240 (non dovrebbe essere il problema siccome lo faceva anche prima, con una HD 6450)
-ASRock H55M-LE
-4GB RAM nanya elixir
-500w PSU VulTec
-Intel i5 660 3.30Ghz
(serve altro?)
posto gli ultimi bsod registrati da whocrashed:
Codice:
System Information (local)
--------------------------------------------------------------------------------
Computer name: JARVIS
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: ASRock, H55M-LE
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 660 @ 3.33GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4285583360 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Tue 18/04/2017 14:24:32 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041817-30218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8023D846EC0, 0x0, 0x343B9118)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program 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 Tue 18/04/2017 14:24:32 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xA29C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8023D846EC0, 0x0, 0x343B9118)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
Bug check description: This indicates that a kernel-mode program 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 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 Tue 18/04/2017 14:02:02 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041817-27937-01.dmp
This was probably caused by the following module: hal.dll (hal+0x1AE4)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8004DC8EAE4, 0xFFFF8281DC295170, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Tue 18/04/2017 13:13:14 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041817-31953-01.dmp
This was probably caused by the following module: hal.dll (hal+0x1AE4)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8002E699AE4, 0xFFFFD000D75FE160, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Tue 18/04/2017 12:35:45 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041817-25531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800B9863EC0, 0xFFFFB60151905620, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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
--------------------------------------------------------------------------------
14 crash dumps have been found and analyzed. Only 5 are included in this report. 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.ultimamente ho notato una certa varietà nelle cause dei bsod, fino a qualche tempo fa la causa era sempre ntoskrnl.exe, e non saprei identificare il motivo di questo cambiamento.
aggiungo inoltre che ho appena scoperto ed attivato la funzione dei dump completi, quindi appena ne avrò li posterò.
