Here is the report from Whocrashed. I'm doing the other steps also. I will let you know what happens. Thanks
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 7/23/2009 4:21:07 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x77 (0xC0000185, 0xC0000185, 0x0, 0xC1F2000)
Error: KERNEL_STACK_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Thu 7/23/2009 1:41:44 AM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x7A (0xE19466B8, 0xC0000185, 0xBF8CEBFC, 0xACD9860)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Thu 7/16/2009 8:18:17 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x77 (0xC0000185, 0xC0000185, 0x0, 0x9318000)
Error: KERNEL_STACK_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sat 7/4/2009 1:06:13 AM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x7A (0xC070B498, 0xC0000185, 0xE1693004, 0x89628C0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Thu 6/18/2009 12:41:34 AM your computer crashed
This was likely caused by the following module: ati2mtag.sys
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\drivers\ati2mtag.sys
product: ATI Radeon WindowsNT Miniport Driver
company: ATI Technologies Inc.
description: ATI Radeon WindowsNT Miniport Driver
On Mon 6/15/2009 12:52:45 PM your computer crashed
This was likely caused by the following module: sr.sys
Bugcheck code: 0x7A (0xC07BA120, 0xC0000185, 0xF74249DC, 0x11D0A860)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\sr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: System Restore Filesystem Filter Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sun 6/14/2009 6:17:55 PM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x8432CAE8, 0x8432CC5C, 0x805C8C88)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Fri 6/12/2009 4:10:22 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7A (0xC07BA128, 0xC000000E, 0xF7425016, 0x163DF860)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sun 6/7/2009 4:41:12 AM your computer crashed
This was likely caused by the following module: ati2mtag.sys
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\drivers\ati2mtag.sys
product: ATI Radeon WindowsNT Miniport Driver
company: ATI Technologies Inc.
description: ATI Radeon WindowsNT Miniport Driver
On Wed 6/3/2009 7:23:05 PM your computer crashed
This was likely caused by the following module: ati2mtag.sys
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\drivers\ati2mtag.sys
product: ATI Radeon WindowsNT Miniport Driver
company: ATI Technologies Inc.
description: ATI Radeon WindowsNT Miniport Driver
On Tue 5/26/2009 11:19:24 PM your computer crashed
This was likely caused by the following module: sr.sys
Bugcheck code: 0x7A (0xC07BA120, 0xC0000185, 0xF74249DC, 0xCCCF860)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\sr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: System Restore Filesystem Filter Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Tue 4/28/2009 10:55:57 PM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x843A4770, 0x843A48E4, 0x805C8C88)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Tue 4/21/2009 1:22:16 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7A (0xC0601C40, 0xC0000185, 0xC0388D10, 0xA2DA884)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Mon 4/20/2009 11:54:40 PM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x84390490, 0x84390604, 0x805C8C88)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Mon 4/20/2009 12:30:23 PM your computer crashed
This was likely caused by the following module: atapi.sys
Bugcheck code: 0x7A (0xC070A538, 0xC000000E, 0xE14A7000, 0x19B278C0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sat 4/18/2009 9:05:13 PM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x7A (0xE1912C88, 0xC0000185, 0xBF9883A3, 0x15466860)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Fri 4/17/2009 1:23:26 AM your computer crashed
This was likely caused by the following module: pfc027.sys
Bugcheck code: 0x100000D0 (0x2626262A, 0x2, 0x1, 0x80542DE9)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\pfc027.sys
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
17 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.