After installing intel core 2 duo pc keeps crashing

The whole screen turns blue while windows r running n it's only for split second.

Yes I have done that too but no success

i did install bluescreenview infact another prog whocrash was better to understand, it picked up last 11 crashes and they all seem different error.

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 28/07/2013 19:40:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072813-26312-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCD604)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF921EBFB8, 0xFFFFFFFF97FD1B04, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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 that cannot be identified at this time.



On Sun 28/07/2013 19:40:01 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngLockSurface+0x2E1)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF921EBFB8, 0xFFFFFFFF97FD1B04, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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 28/07/2013 19:37:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072813-24187-01.dmp
This was probably caused by the following module: avgtdix.sys (avgtdix+0x2411)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFFFFF8973B411)
Error: DRIVER_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 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: avgtdix.sys (AVG Network connection watcher, AVG Technologies CZ, s.r.o.).
Google query: AVG Technologies CZ, s.r.o. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sun 28/07/2013 19:16:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072813-25421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD1574)
Bugcheck code: 0x1A (0x41201, 0xFFFFFFFFC01B4D88, 0x7200C005, 0xFFFFFFFF863A2120)
Error: MEMORY_MANAGEMENT
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 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 25/07/2013 18:41:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072513-26828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD1574)
Bugcheck code: 0x1A (0x41201, 0xFFFFFFFFC0016200, 0x79F3D867, 0xFFFFFFFF8687D730)
Error: MEMORY_MANAGEMENT
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 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 25/07/2013 18:04:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072513-32296-01.dmp
This was probably caused by the following module: luafv.sys (luafv+0x97B1)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF908AE7B1, 0xFFFFFFFF8E102C34, 0xFFFFFFFF8E102810)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\luafv.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: LUA File Virtualization Filter Driver
Bug check description: This indicates that a system thread 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.



12 crash dumps have been found and analyzed. 2 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:

avgidsdriverx.sys (IDS Application Activity Monitor Driver., AVG Technologies CZ, s.r.o.)
avgtdix.sys (AVG Network connection watcher, AVG Technologies CZ, s.r.o.)



checked all my driver are upto date.

Thanks vipervoid1 n others who tried to help with best of their knowledge. I have checked disk. Nothing wrong. My current pentium 4 processor is working fine with no problem. I can't find ne thing on bios which should I alter for core 2 duo like voltage etc. I have posted problems above. It's asking to update avg drivers but I can't locate them as avg is the antivirus software. So I think I give up presuming that CPU is faulty.