Windows 7 - Freeze when cold boot 2 or 3 Times.. Help

Computer freeze 2 or 3 times, just after turn on when is cold,, just after 2 or 3 freeze it works fine without any problems

i use memtest86 most of the time no errors but other during test computer freeze without found any error ....

I had 2x1Gb OCZ GOLD no problems, but after upgrade to 4GB start ramdom BSOD, but im no sure it is memory cause report always said no errors,.......Also upgrade from windows 7 32 bits to 64tis

memory 2x2gb G Skill F2-6400CL4-2GBPI-B
Motherboard ECS G31T-M V1.0

MiniDump with whocrashed detailed


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


windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4284735488 total
VM: 2147352576, free: 1995296768



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 23/05/2011 01:06:07 p.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\052311-16380-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x50 (0xFFFFF8A01330F1F3, 0x1, 0xFFFFF880012D4956, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 which cannot be identified at this time.


On Mon 23/05/2011 01:06:07 p.m. GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tdrpm273.sys (tdrpm273+0x46F3E)
Bugcheck code: 0x50 (0xFFFFF8A01330F1F3, 0x1, 0xFFFFF880012D4956, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\tdrpm273.sys
product: Acronis Try&Decide
company: Acronis
description: Acronis Try&Decide Volume Filter Driver
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.
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: tdrpm273.sys (Acronis Try&Decide Volume Filter Driver, Acronis).
Google query: tdrpm273.sys Acronis PAGE_FAULT_IN_NONPAGED_AREA




On Sun 22/05/2011 11:19:03 p.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\052211-15974-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0xD1 (0xFFFFF7FF84BC0F67, 0x9, 0x0, 0xFFFFF7FF84BC0F67)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 which cannot be identified at this time.


On Tue 17/05/2011 07:21:08 p.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\051711-16614-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000000.sys (Unloaded_Unknown_Module_00000000`00000000+0x27A32B)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002DB5DB2, 0xFFFFF8800912BA80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
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_module_00000000`00000000.sys .
Google query: unknown_module_00000000`00000000.sys SYSTEM_SERVICE_EXCEPTION




On Tue 17/05/2011 11:58:03 a.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\051711-16972-01.dmp
This was probably caused by the following module: fileinfo.sys (fileinfo+0x12E2)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88000C4D2E2, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
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 10/05/2011 07:43:08 p.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\051011-20264-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x4146)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF88001249146, 0xFFFFF88007977150, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Administrador de filtros del sistema de archivos de Microsoft
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 which cannot be identified at this time.


On Tue 10/05/2011 12:11:25 p.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\051011-22339-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88009631900, 0x0, 0x0)
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 which cannot be identified at this time.

Uninstall Acronis as it's the only 3rd party driver identified in the above reports.
Other than that, please provide this info: Blue Screen of Death (BSOD) Posting Instructions