Dell Studio XPS
Windows 7-64 bit

Computer keeps crashing most of the time @ startup, but will occassionaly lockup after a while. It's been doing it for quite a while. After seeing WhoCrashed posted here, I downloaded and ran it after the latest crash. Report following..

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

computer name: JEAN-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 4285517824 total
VM: 2147352576, free: 1978798080

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 7/27/2013 11:13:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072713-59373-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x50 (0xFFFFF8000575D772, 0x8, 0xFFFFF8000575D772, 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 that cannot be identified at this time.

On Sat 7/27/2013 11:13:10 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFF8000575D772, 0x8, 0xFFFFF8000575D772, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 that cannot be identified at this time.

On Mon 7/1/2013 10:46:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070113-24195-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x1092)
Bugcheck code: 0xD1 (0xF249A, 0x2, 0x1, 0xFFFFF88004B1A092)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
description: Processor Device 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 that cannot be identified at this time.
Google query: Microsoft Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Fri 6/28/2013 10:34:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062813-20373-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000399DDD0, 0xFFFFF88009375F30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 6/24/2013 11:21:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062413-20560-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800036BA5B6, 0xFFFFF8800CCBBFC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 6/6/2013 11:13:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060613-27768-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x42808)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF88001842808, 0x0, 0xFFFFF8800886CE00)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
description: TCP/IP 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 6/2/2013 11:06:57 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060213-23556-01.dmp
This was probably caused by the following module: cdd.sys (cdd+0x980D)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960006F980D, 0xFFFFF88009E317C0, 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: cdd.sys .
Google query: cdd.sys SYSTEM_SERVICE_EXCEPTION

On Thu 5/30/2013 12:46:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052913-26036-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x6F8, 0xFFFFF8000367C314)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 5/20/2013 10:27:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052013-23961-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C10)
Bugcheck code: 0x1E (0x0, 0x0, 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 that cannot be identified at this time.

On Wed 5/15/2013 10:57:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051513-25490-01.dmp
This was probably caused by the following module: unknown_module_00000000`00029601.sys (Unloaded_Unknown_Module_00000000`00029601+0x250D51)
Bugcheck code: 0x7E (0xFFFFFFFF80000003, 0xFFFFF88004BAB222, 0xFFFFF8800404F6C8, 0xFFFFF8800404EF20)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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`00029601.sys .
Google query: unknown_module_00000000`00029601.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

On Wed 4/10/2013 4:56:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041013-22308-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x50 (0xFFFFF88022F64188, 0x0, 0xFFFFF800036BF030, 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 that cannot be identified at this time.

On Sun 3/17/2013 11:45:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031713-28329-01.dmp
This was probably caused by the following module: usbuhci.sys (usbuhci+0x48B5)
Bugcheck code: 0xD1 (0x4, 0x2, 0x1, 0xFFFFF8800646E8B5)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbuhci.sys
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
description: UHCI USB Miniport 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 that cannot be identified at this time.

On Sat 10/27/2012 10:54:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102712-25833-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x6F8, 0xFFFFF80002F03A8D)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 9/3/2012 3:33:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090312-24960-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E9BBEC, 0xFFFFF8800AB76CD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 8/22/2012 8:33:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082212-31215-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6FAD)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000186FAD, 0xFFFFF8800CCE7D40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 that cannot be identified at this time.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

18 crash dumps have been found and analyzed. Only 15 are included in this report. 3 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:

intelppm.sys (Processor Device Driver, Microsoft Corporation)
cdd.sys
unknown_module_00000000`00029601.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.