Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are disabled for your computer.
On Fri 6/5/2009 8:52:22 PM your computer crashed
This was likely caused by the following module: saskutil.sys
Bugcheck code: 0x10000050 (0xF1B01434, 0x0, 0x82F1EF51, 0x0)
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 saskutil.sys
On Fri 6/5/2009 5:50:10 AM your computer crashed
This was likely caused by the following module: saskutil.sys
Bugcheck code: 0x10000050 (0xF06277EC, 0x0, 0x82F20F51, 0x0)
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 saskutil.sys
On Fri 6/5/2009 1:36:35 AM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x10000050 (0xF0A3B9DC, 0x0, 0x82F20F51, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System 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/4/2009 5:34:18 AM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x10000050 (0xF115A5C4, 0x0, 0x82F89F51, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System 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/4/2009 3:29:19 AM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x10000050 (0xF176B73C, 0x0, 0x82F8BF51, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System 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/4/2009 3:03:28 AM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x10000050 (0xF14524D4, 0x0, 0x82F8BF51, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System 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/4/2009 2:52:23 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D1 (0xE194D000, 0x2, 0x0, 0xF6779B00)
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 Thu 6/4/2009 12:17:58 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D1 (0xE1902000, 0x2, 0x0, 0xF677DB00)
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 Thu 6/4/2009 12:02:16 AM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x82DF9538, 0x82DF96AC, 0x805FB046)
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 Wed 6/3/2009 11:52:18 PM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x82DBD9A8, 0x82DBDB1C, 0x805FB046)
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 Wed 6/3/2009 11:16:04 PM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x82BA0270, 0x82BA03E4, 0x805FB046)
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 Thu 5/28/2009 4:36:50 AM your computer crashed
This was likely caused by the following module: rtccpxxoqoufnlqb.sys
Bugcheck code: 0x1000007E (0xC0000005, 0x82416C0D, 0xF8A44A10, 0xF8A4470C)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 rtccpxxoqoufnlqb.sys
On Sat 5/9/2009 12:10:48 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D1 (0xE1953000, 0x2, 0x0, 0xF67D1CF1)
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 Thu 5/7/2009 6:30:07 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D1 (0xE1956000, 0x2, 0x0, 0xF6734CF1)
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 Mon 5/4/2009 5:16:00 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D1 (0xE1958000, 0x2, 0x0, 0xF6788CF1)
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 5/1/2009 12:52:16 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D1 (0xE18FC000, 0x2, 0x0, 0xF679ACF1)
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 7/11/2007 7:04:23 AM your computer crashed
This was likely caused by the following module: nv4_disp.dll
Bugcheck code: 0x1000008E (0xC0000005, 0xBFA20D85, 0xF16391A0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 30.82
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 30.82
--------------------------------------------------------------------------------
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.