No problem and I will watch for your results tomorrow. 
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: SERGERAS-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon 64 X2 Dual Core Processor 5400+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 2146820096 total
VM: 2147352576, free: 2006679552
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 7/18/2011 2:18:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071811-32744-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x23199D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A3199D, 0xFFFFFFFFA3D3FC60, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_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 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.
On Sun 7/17/2011 11:39:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071811-20092-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x12044)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x0, 0xFFFFFFFF853528B0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that the current thread is making a bad pool request.
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 Sun 7/17/2011 8:37:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071711-21621-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x245A63)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A9AA63, 0xFFFFFFFFA49FBB8C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_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 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.
On Sun 7/17/2011 3:06:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071711-23134-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD8F8D)
Bugcheck code: 0x1A (0x5003, 0xFFFFFFFFC0802000, 0x5E1, 0xAAA9C2)
Error: MEMORY_MANAGEMENT
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 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 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 7/16/2011 10:51:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071711-16239-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x388D)
Bugcheck code: 0xD1 (0x6C756166, 0x2, 0x0, 0xFFFFFFFF8E60B88D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port 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.
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 7/16/2011 9:01:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071711-12012-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xC6D9)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFFFFF828AC3EF)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 which cannot be identified at this time.
On Sat 7/16/2011 8:48:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071611-11700-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCE3C)
Bugcheck code: 0xC2 (0x99, 0xFFFFFFFF84C114C0, 0x0, 0x0)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 Sat 7/16/2011 1:23:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071611-26754-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x270EA3)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A87EA3, 0xFFFFFFFFA0F05AF0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_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 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.
On Sat 7/16/2011 11:56:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071611-20311-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x805AA)
Bugcheck code: 0x1A (0x5003, 0xFFFFFFFF88E00000, 0x1566, 0x15958CC)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 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 7/16/2011 11:38:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071611-20389-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xC28EC)
Bugcheck code: 0x1A (0x782, 0xFFFFFFFF85948160, 0xFFFFFFFF8FC00000, 0xFFFFFFFF9FF4CA20)
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 Sat 7/16/2011 11:33:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071611-25194-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x3155F2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82B505F2, 0xFFFFFFFF97713BDC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_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 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.
On Sat 7/16/2011 12:28:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071611-14274-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x2314CD)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A414CD, 0xFFFFFFFF9AAC4C60, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_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 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.
On Fri 7/15/2011 5:02:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071511-32198-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
Bugcheck code: 0xA (0x17, 0x2, 0x0, 0xFFFFFFFF82878BE8)
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 which cannot be identified at this time.
On Fri 7/15/2011 3:18:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071511-14430-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x245593)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A7E593, 0xFFFFFFFF9978BC2C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_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 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.