PROBLEMA Problema Windows 7 Blue screen !!!!!!!!!!!!

gioretta

Nuovo Utente
1
0
Ho un problema gigantesco!!! il mio portatile Dell crasha continuamente,l'ho ripristinato,ho fatto di tutto ma non funziona!! Mi potete dare una mano??? Ho letto di whocrashed e vi posto i risultati :cav::cav::cav::cav::cav::grat::grat::grat::grat::grat: P.S ogni tanto si spegne senza blue screen
Crash dumps are enabled on your computer.

On Mon 16/09/2013 18:45:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091613-23743-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40B7F)
Bugcheck code: 0xA (0xD, 0x2, 0x0, 0xFFFFFFFF82EB2C8A)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 16/09/2013 18:45:16 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x28B7)
Bugcheck code: 0xA (0xD, 0x2, 0x0, 0xFFFFFFFF82EB2C8A)
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL






On Sun 15/09/2013 12:40:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091513-21496-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x5F6D)
Bugcheck code: 0xBE (0xFFFFFFFF8B560858, 0x3A7C121, 0xFFFFFFFFAEAFCACE, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Gestione filtri file system Microsoft
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Fri 13/09/2013 12:05:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091313-29593-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8D879)
Bugcheck code: 0x50 (0xFFFFFFFFF0C18BD0, 0x1, 0xFFFFFFFF82EA8CE4, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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 Tue 10/09/2013 11:43:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091013-25474-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD149B)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF826F149B, 0xFFFFFFFFAB077B0C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver Win32 multiutente
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 Mon 09/09/2013 16:35:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090913-22479-01.dmp
This was probably caused by the following module: avgtdix.sys (avgtdix+0x4052)
Bugcheck code: 0xA (0x5A8, 0x2, 0x0, 0xFFFFFFFF82E9F413)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\avgtdix.sys
product: AVG Internet Security
company: AVG Technologies CZ, s.r.o.
description: AVG Network connection watcher
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.
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: avgtdix.sys (AVG Network connection watcher, AVG Technologies CZ, s.r.o.).
Google query: AVG Technologies CZ, s.r.o. IRQL_NOT_LESS_OR_EQUAL






On Sun 08/09/2013 09:51:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090813-22916-01.dmp
This was probably caused by the following module: bcmwl6.sys (bcmwl6+0x53003)
Bugcheck code: 0xD1 (0xFFFFFFFFC685B70C, 0x2, 0x1, 0xFFFFFFFF9745A003)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\bcmwl6.sys
product: Broadcom 802.11 Network Adapter wireless driver
company: Broadcom Corporation
description: Broadcom 802.11 Network Adapter wireless 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: bcmwl6.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
Google query: Broadcom Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL






On Sat 07/09/2013 12:50:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090713-35771-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x17853A)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: ATI Technologies Inc. UNEXPECTED_KERNEL_MODE_TRAP






On Wed 04/09/2013 08:43:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090413-27502-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x18405)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: ATI Technologies Inc. UNEXPECTED_KERNEL_MODE_TRAP






On Sun 25/08/2013 12:58:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082513-24570-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEBFC)
Bugcheck code: 0x1A (0x41284, 0xBFC8001, 0x7410, 0xFFFFFFFFC0802000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.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 22/08/2013 20:48:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082213-27565-01.dmp
This was probably caused by the following module: afd.sys (afd+0x1345)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\afd.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 Wed 21/08/2013 07:17:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082113-38189-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40B7F)
Bugcheck code: 0xD1 (0x22330, 0x2, 0x1, 0xFFFFFFFFAED65B6D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
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 17/08/2013 15:45:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081713-31262-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x4A6A)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF8B4A2A6A, 0xFFFFFFFF8EF51254, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ndis.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver NDIS 6.20
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 Sat 10/08/2013 23:41:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081113-20685-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCC5FE)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF877135D8, 0xFFFFFFFF87713628, 0x80A0008)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver Win32 multiutente
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 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 Fri 09/08/2013 11:57:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080913-21387-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x8C22A)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFA32D4383, 0xFFFFFFFF91DD8BCC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver Win32 multiutente
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.








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


51 crash dumps have been found and analyzed. Only 15 are included in this report. 5 third party drivers have 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:


atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)
bcmwl6.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation)
avgtdix.sys (AVG Network connection watcher, AVG Technologies CZ, s.r.o.)
ntkrpamp.exe
hal.sys


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

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
ciao sembra essere la ram controllala con memetest prendilo dalla mia firma e mettilo su usb
 

Matarael

Utente Attivo
1,099
144
Beh, visti i tanti bsod diversi, anche io controllerei tutto l'hardware prima, ovviamente partendo dalla ram. E controllando le temperature.

Se tutti i test danno esito negativo, aggiorna i drivers, e prova lanciando il computer in modalità diagnostica, per vedere se, senza tutti i servizi opzionali, ti da comunque questo problema. Ovviamente attento perchè in modalità diagnostica non dovrebbe caricare neppure l'antivirus, quindi, occhio.
 

Entra

oppure Accedi utilizzando

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

  • Ubisoft

    Voti: 14 16.5%
  • Gearbox

    Voti: 1 1.2%
  • Xbox & Bethesda

    Voti: 60 70.6%
  • Square Enix

    Voti: 3 3.5%
  • Capcom

    Voti: 5 5.9%
  • Nintendo

    Voti: 13 15.3%
  • Altro (Specificare)

    Voti: 6 7.1%

Discussioni Simili