unexoected BSOD results in Crash Dump

Hello everyone,

I have recently had many crash dump files it appears in c:\windows\minidump.
I am uploadin it here, for these who many wish to review it. However, i cannot specefiy what the cause of this problema may have been.

Some one can help me, please?


System Information (local)

---

computer name: OI-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2145964032 total
VM: 2147352576, free: 1978925056

---

Crash Dump Analysis

---

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 12-04-2012 18:31:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041212-14437-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E3FF)
Bugcheck code: 0xBE (0xFFFFFFFF82873A4C, 0x2873121, 0xFFFFFFFF8078AEDC, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 12-04-2012 18:31:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x2C2F1)
Bugcheck code: 0xBE (0xFFFFFFFF82873A4C, 0x2873121, 0xFFFFFFFF8078AEDC, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: RunTime da Estrutura de Controladores de Modo de Kernel
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 which cannot be identified at this time.


On Thu 05-04-2012 18:01:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040512-20312-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEF04)
Bugcheck code: 0x1A (0x41284, 0x72B21001, 0xAEC, 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 which cannot be identified at this time.


On Wed 04-04-2012 19:26:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040412-29671-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x620C)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x2C7068, 0xFFFFFFFF9FE4B978, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Gestor de Filtros de Sistema de Ficheiros da Microsoft
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 which cannot be identified at this time.


On Tue 03-04-2012 18:53:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040312-17765-01.dmp
This was probably caused by the following module: ew_jucdcacm.sys (ew_jucdcacm+0x4E96)
Bugcheck code: 0x10D (0x5, 0x0, 0x1024, 0xFFFFFFFF8638D5D8)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\ew_jucdcacm.sys
product: ew_jucdcacm Driver (x86)
company: Huawei Technologies Co., Ltd.
description: ew_jucdcacm Driver
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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: ew_jucdcacm.sys (ew_jucdcacm Driver, Huawei Technologies Co., Ltd.).
Google query: ew_jucdcacm.sys Huawei Technologies Co., Ltd. WDF_VIOLATION




On Tue 03-04-2012 08:51:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040312-17640-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x43813)
Bugcheck code: 0x1 (0xFFFFFFFF82A3E62E, 0x0, 0xFFFF, 0x0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 02-04-2012 18:14:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040212-13421-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1456EB)
Bugcheck code: 0x50 (0xFFFFFFFFFD98B4E4, 0x1, 0xFFFFFFFF8295B943, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador Win32 para vários utilizadores
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 which cannot be identified at this time.


On Sat 31-03-2012 13:51:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\033112-12421-01.dmp
This was probably caused by the following module: hal.sys (hal+0x5CBA)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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: hal.sys .
Google query: hal.sys UNEXPECTED_KERNEL_MODE_TRAP




On Sat 31-03-2012 13:49:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\033112-13328-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x465A5)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF807C7750, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
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 trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 20-03-2012 17:40:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032012-13171-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x858E3)
Bugcheck code: 0xBE (0xFFFFFFFF8287B788, 0x287B121, 0xFFFFFFFF8BE63B94, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 16-03-2012 18:12:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031612-21593-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x1A (0x5003, 0xFFFFFFFFC0802000, 0x9E2, 0x1A0D009)
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 which cannot be identified at this time.


On Fri 16-03-2012 18:11:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031612-18015-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x858E3)
Bugcheck code: 0x1A (0x41287, 0x63416D4D, 0x0, 0x0)
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 which cannot be identified at this time.


On Fri 16-03-2012 18:07:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031612-19640-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF82648F2B)
Bugcheck code: 0x7F (0x5, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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: Unknown .
Google query: Unknown UNEXPECTED_KERNEL_MODE_TRAP

same problem here!! anybody can help??