Here is the analysis report, I had no idea it had crashed that many times. Beware, this is a long paste.
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 1/2/2009 12:54:04 AM your computer crashed
This was likely caused by the following module: mfehidk.sys
Bugcheck code: 0x7A (0x2, 0xC0000005, 0x83F201E0, 0x60000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\mfehidk.sys
product: SYSCORE.14.0.0.291.x86
company: McAfee, Inc.
description: Host Intrusion Detection Link Driver
On Sun 12/14/2008 7:12:59 PM your computer crashed
This was likely caused by the following module: mfehidk.sys
Bugcheck code: 0x7A (0x2, 0xC0000005, 0x86C96020, 0x60000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\mfehidk.sys
product: SYSCORE.14.0.0.291.x86
company: McAfee, Inc.
description: Host Intrusion Detection Link Driver
On Mon 12/8/2008 5:35:35 AM your computer crashed
This was likely caused by the following module: mfehidk.sys
Bugcheck code: 0x1000000A (0x1C, 0x2, 0x1, 0x805257A1)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\mfehidk.sys
product: SYSCORE.14.0.0.291.x86
company: McAfee, Inc.
description: Host Intrusion Detection Link Driver
On Fri 12/5/2008 11:45:00 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x4128B, 0x7DF201, 0x1000000, 0xC0883000)
Error: MEMORY_MANAGEMENT
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 Fri 11/28/2008 1:43:36 AM your computer crashed
This was likely caused by the following module: mfehidk.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x2, 0xA4900B14, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\mfehidk.sys
product: SYSCORE.14.0.0.291.x86
company: McAfee, Inc.
description: Host Intrusion Detection Link Driver
On Mon 11/17/2008 1:11:41 AM your computer crashed
This was likely caused by the following module: mfehidk.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x2, 0xA60DEB14, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\mfehidk.sys
product: SYSCORE.14.0.0.291.x86
company: McAfee, Inc.
description: Host Intrusion Detection Link Driver
On Sun 11/16/2008 2:26:20 PM your computer crashed
This was likely caused by the following module: mfehidk.sys
Bugcheck code: 0x7A (0x2, 0xC0000005, 0x83F96020, 0x60000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\mfehidk.sys
product: SYSCORE.14.0.0.291.x86
company: McAfee, Inc.
description: Host Intrusion Detection Link Driver
On Wed 11/12/2008 6:40:56 PM your computer crashed
This was likely caused by the following module: mfehidk.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x2, 0xA476BB14, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\mfehidk.sys
product: SYSCORE.14.0.0.291.x86
company: McAfee, Inc.
description: Host Intrusion Detection Link Driver
On Tue 11/11/2008 1:32:53 PM your computer crashed
This was likely caused by the following module: mfehidk.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x2, 0xA4F9CB14, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\mfehidk.sys
product: SYSCORE.14.0.0.291.x86
company: McAfee, Inc.
description: Host Intrusion Detection Link Driver
On Wed 10/29/2008 9:25:25 PM your computer crashed
This was likely caused by the following module: mfehidk.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x80636F97, 0xA48C6B14, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\mfehidk.sys
product: SYSCORE.14.0.0.291.x86
company: McAfee, Inc.
description: Host Intrusion Detection Link Driver
On Mon 10/27/2008 10:45:35 PM your computer crashed
This was likely caused by the following module: mfehidk.sys
Bugcheck code: 0x1000000A (0x1C, 0x2, 0x1, 0x80525791)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\mfehidk.sys
product: SYSCORE.14.0.0.291.x86
company: McAfee, Inc.
description: Host Intrusion Detection Link Driver
On Sat 9/27/2008 8:48:56 AM your computer crashed
This was likely caused by the following module: mfehidk.sys
Bugcheck code: 0x1000000A (0x1C, 0x2, 0x1, 0x80524A6D)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\mfehidk.sys
product: SYSCORE.14.0.0.291.x86
company: McAfee, Inc.
description: Host Intrusion Detection Link Driver
On Sun 6/8/2008 11:54:14 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x4128B, 0x41DD201, 0x0, 0xC0883000)
Error: MEMORY_MANAGEMENT
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 6/5/2008 11:44:32 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x859B, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
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/1/2008 1:49:49 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x21AA7, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
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/1/2008 2:23:21 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE45ED000, 0x0, 0x8063398B, 0x1)
Error: Unknown
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 Wed 4/2/2008 3:12:42 PM your computer crashed
This was likely caused by the following module: mfehidk.sys
Bugcheck code: 0x1000000A (0x8848AA98, 0x2, 0x0, 0x8050E252)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\mfehidk.sys
product: SYSCORE.14.0.0.291.x86
company: McAfee, Inc.
description: Host Intrusion Detection Link Driver
On Sat 3/8/2008 8:37:52 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x1C, 0x2, 0x1, 0x80524A6D)
Error: Unknown
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 Fri 2/29/2008 4:25:24 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x1C, 0x2, 0x1, 0x80524A6D)
Error: Unknown
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 Wed 2/13/2008 6:03:06 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xC0012F78, 0x2, 0x0, 0x80510C42)
Error: Unknown
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 Tue 11/6/2007 1:36:24 PM your computer crashed
This was likely caused by the following module: symevent.sys
Bugcheck code: 0x1000000A (0x1C, 0x2, 0x1, 0x80524A6D)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on symevent.sys
On Thu 11/1/2007 2:05:49 AM your computer crashed
This was likely caused by the following module: cxfalcon.sys
Bugcheck code: 0x100000D1 (0x88A4C000, 0x2, 0x0, 0xF6ABDAF9)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\cxfalcon.sys
product: cxfalcon.sys
company: Conexant Systems, Inc.
description: Conexant Falcon Driver
On Mon 10/29/2007 11:28:49 PM your computer crashed
This was likely caused by the following module: cxfalcon.sys
Bugcheck code: 0x100000D1 (0x866CC000, 0x2, 0x0, 0xF714AAF9)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\cxfalcon.sys
product: cxfalcon.sys
company: Conexant Systems, Inc.
description: Conexant Falcon Driver
On Sat 10/27/2007 1:03:51 AM your computer crashed
This was likely caused by the following module: cxfalcon.sys
Bugcheck code: 0x100000D1 (0x869C5000, 0x2, 0x0, 0xF714AAF9)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\cxfalcon.sys
product: cxfalcon.sys
company: Conexant Systems, Inc.
description: Conexant Falcon Driver
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
24 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.