PROBLEMA Crash di Window 7

MikiTro

Nuovo Utente
1
0
Salve a tutti!!! Da qualche giorno ho continui crash con window ma non conosco la causa.
Di seguito riporto il report di whocrashed



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


Computer name: MICHELETRONATI
Windows version: Windows 7 , 6.1, build: 7600
Windows dir: C:\Windows
Hardware: Aspire 4810T, Acer
CPU: GenuineIntel Genuine Intel(R) CPU U4100 @ 1.30GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4193034240 bytes total








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


Crash dump directory: C:\Windows\Minidump


Crash dumps are enabled on your computer.


On Wed 27/01/2016 10:57:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012716-21294-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x7A (0xFFFFF6FC4001BA00, 0xFFFFFFFFC0000185, 0x4E06BBE0, 0xFFFFF88003740000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 27/01/2016 10:57:50 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: 0x7A (0xFFFFF6FC4001BA00, 0xFFFFFFFFC0000185, 0x4E06BBE0, 0xFFFFF88003740000)
Error: KERNEL_DATA_INPAGE_ERROR
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 27/01/2016 09:11:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012716-16863-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF800033E6477)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800033E6477)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Wed 27/01/2016 09:00:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012716-15943-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF80002E1B477)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002E1B477)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Tue 26/01/2016 22:23:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012616-17253-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x13A000)
Bugcheck code: 0x7A (0xFFFFF6FC40009A10, 0xFFFFFFFFC0000185, 0x433CF860, 0xFFFFF88001342000)
Error: KERNEL_DATA_INPAGE_ERROR
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 bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 26/01/2016 14:46:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012616-14820-01.dmp
This was probably caused by the following module: bowser.sys (bowser+0xA0BC)
Bugcheck code: 0x7A (0xFFFFF6FC4001A878, 0xFFFFFFFFC0000185, 0x2E962860, 0xFFFFF8800350F0BC)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\bowser.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Lan Manager Datagram Receiver Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 26/01/2016 13:26:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012616-14913-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF80002E1E477)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002E1E477)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Sun 10/01/2016 23:26:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011116-19016-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600028887E)
Bugcheck code: 0x50 (0xFFFFF900C1C6ACF0, 0x0, 0xFFFFF9600028887E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 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
--------------------------------------------------------------------------------


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

Entra

oppure Accedi utilizzando
Discord Ufficiale Entra ora!

Discussioni Simili