Strangely, it didn't freeze for a couple of nights. But this morning, its all frozen at 3:50 am once again. The results form VEW.exe and whocrashed are below, but they don't seem to tell anything. The WhoCrashed report shows no crashes since 04/02/2010 - the VEW.exe has nothing to report. Maybe because its a freeze, not a crash. Where do we go from here?
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 04/02/2010 4:00:55 AM your computer crashed
This was likely caused by the following module: procexp111.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x8244E6EE, 0x98F4092C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\Mini020310-01.dmp
file path: \??\C:\Windows\system32\Drivers\PROCEXP111.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on procexp111.sys
On Wed 20/01/2010 8:04:20 AM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x18 (0x83E9D5C0, 0x8542C2D8, 0x2, 0xFFFFFFFD)
Error: REFERENCE_BY_POINTER
Dump file: C:\Windows\Minidump\Mini012010-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Fri 15/01/2010 7:43:31 AM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x18 (0x83E9D5C0, 0x84A2C458, 0x2, 0xFFFFFFFF)
Error: REFERENCE_BY_POINTER
Dump file: C:\Windows\Minidump\Mini011510-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Thu 14/01/2010 7:53:28 AM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x18 (0x83E94D40, 0x84F7D198, 0x2, 0xFFFFFFFF)
Error: REFERENCE_BY_POINTER
Dump file: C:\Windows\Minidump\Mini011410-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Wed 06/01/2010 5:08:06 AM your computer crashed
This was likely caused by the following module: procexp111.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x8245E6EE, 0xAF3B192C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\Mini010610-01.dmp
file path: \??\C:\Windows\system32\Drivers\PROCEXP111.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on procexp111.sys
On Sat 12/12/2009 8:31:22 AM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x18 (0x83A9D5C0, 0x8523CF80, 0x2, 0xFFFFFFFF)
Error: REFERENCE_BY_POINTER
Dump file: C:\Windows\Minidump\Mini121209-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Fri 11/12/2009 7:09:28 PM your computer crashed
This was likely caused by the following module: procexp111.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x820516EE, 0xA6CE192C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\Mini121109-01.dmp
file path: \??\C:\Windows\system32\Drivers\PROCEXP111.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on procexp111.sys
On Sat 28/11/2009 7:49:24 AM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x18 (0x83A9D5C0, 0x85328D48, 0x2, 0xFFFFFFFF)
Error: REFERENCE_BY_POINTER
Dump file: C:\Windows\Minidump\Mini112809-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Wed 25/11/2009 9:56:39 AM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x18 (0x83A9D5C0, 0x84E4AAA8, 0x2, 0xFFFFFFFF)
Error: REFERENCE_BY_POINTER
Dump file: C:\Windows\Minidump\Mini112509-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Mon 23/11/2009 7:50:44 AM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x18 (0x83A94EC0, 0x8494F0C8, 0x2, 0xFFFFFFFF)
Error: REFERENCE_BY_POINTER
Dump file: C:\Windows\Minidump\Mini112309-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Wed 21/10/2009 3:06:37 AM your computer crashed
This was likely caused by the following module: procexp111.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x820866EE, 0x9C8CB92C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\Mini102009-01.dmp
file path: \??\C:\Windows\system32\Drivers\PROCEXP111.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on procexp111.sys
On Tue 06/10/2009 2:28:10 AM your computer crashed
This was likely caused by the following module: procexp111.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x820766EE, 0xA7FE392C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\Mini100509-01.dmp
file path: \??\C:\Windows\system32\Drivers\PROCEXP111.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on procexp111.sys
On Tue 25/08/2009 1:06:47 AM your computer crashed
This was likely caused by the following module: procexp111.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x820536EE, 0x8BC1C92C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\Mini082409-01.dmp
file path: \??\C:\Windows\system32\Drivers\PROCEXP111.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on procexp111.sys
On Tue 18/08/2009 1:41:36 AM your computer crashed
This was likely caused by the following module: procexp111.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x81E526EE, 0x8162992C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\Mini081709-02.dmp
file path: \??\C:\Windows\system32\Drivers\PROCEXP111.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on procexp111.sys
On Mon 17/08/2009 8:50:19 AM your computer crashed
This was likely caused by the following module: dxgkrnl.sys
Bugcheck code: 0x100000EA (0x8368F378, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Dump file: C:\Windows\Minidump\Mini081709-01.dmp
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Sun 02/08/2009 11:16:13 PM your computer crashed
This was likely caused by the following module: procexp111.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x81E816EE, 0xB04D892C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\Mini080209-01.dmp
file path: \??\C:\Windows\system32\Drivers\PROCEXP111.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on procexp111.sys
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
16 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.
=================================================
Output from VEW.exe
=================================================
Vino's Event Viewer v01c run on Windows Vista in English
Report run at 13/02/2010 7:52:19 AM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
No 'Application' log Error events found from 13/02/2010 to 13/02/2010
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
No 'Application' log Information events found from 13/02/2010 to 13/02/2010
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
No 'Application' log Warning events found from 13/02/2010 to 13/02/2010
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
No 'System' log Error events found from 13/02/2010 to 13/02/2010
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
No 'System' log Information events found from 13/02/2010 to 13/02/2010
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
No 'System' log Warning events found from 13/02/2010 to 13/02/2010