Here you go fella.........thx.......
i also have just updated drivers+CCC for my Sapp.Radeon X1650pro which i hope might help..
--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 05/01/2009 23:39:20 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007F (0x8, 0xF7717D70, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
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 05/01/2009 22:36:45 your computer crashed
This was likely caused by the following module: unknown_image
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_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 unknown_image
On Mon 05/01/2009 19:14:40 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
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 02/01/2009 07:15:04 your computer crashed
This was likely caused by the following module: unknown_image
Bugcheck code: 0x8E (0xC0000005, 0xA84C0D7A, 0xA5F957E8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
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 unknown_image
On Fri 02/01/2009 03:21:48 your computer crashed
This was likely caused by the following module: unknown_module_a6040000
Bugcheck code: 0xD1 (0xFFFFFFEE, 0x2, 0x1, 0xA606FC48)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 unknown_module_a6040000
On Thu 01/01/2009 20:10:49 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x34, 0x2, 0x1, 0x80703A16)
Error: IRQL_NOT_LESS_OR_EQUAL
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 09/11/2008 04:33:27 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x24 (0x1902FE, 0xF78BAAA8, 0xF78BA7A4, 0x804F6478)
Error: NTFS_FILE_SYSTEM
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 12/09/2008 15:06:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x80552211, 0xA5B738FC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 03/08/2008 18:17:47 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xE3 (0x88C3AAE0, 0x8969C020, 0x0, 0x2)
Error: RESOURCE_NOT_OWNED
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 01/08/2008 16:52:05 your computer crashed
This was likely caused by the following module: ???????????????????????????????????????
Bugcheck code: 0x1000007E (0xC000001D, 0xA6077694, 0xA69D2BAC, 0xA69D28A8)
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 ???????????????????????????????????????
On Sun 27/07/2008 22:44:06 your computer crashed
This was likely caused by the following module: ativvaxx.dll
Bugcheck code: 0x1000008E (0xC0000005, 0xBF532B78, 0xA56A4B18, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ativvaxx.dll
product: ATI Technologies Inc. Radeon Video Acceleration Universal Driver
company: ATI Technologies Inc.
description: Radeon Video Acceleration Universal Driver
On Sun 27/07/2008 17:11:34 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1902FE, 0xA63565C0, 0xA63562BC, 0xF7B76D46)
Error: NTFS_FILE_SYSTEM
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
13 crash dumps have been found on your computer. Only 12 have been 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.
Edited by jacktro, 05 January 2009 - 08:13 PM.