thats the program im using, i just thought its too long but ok...
System Information (local)
--------------------------------------------------------------------------------
computer name: DJORDJE-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X4 965 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 8587370496 total
VM: 2147352576, free: 1929097216
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 04/12/2013 13:27:01 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: analysis.sys (0x770B2BBA)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800032C9E94, 0xFFFFF8800719FDE0, 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: analysis.sys .
Google query: analysis.sys SYSTEM_SERVICE_EXCEPTION
On Wed 04/12/2013 13:27:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120413-20716-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Tue 03/12/2013 14:10:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120313-22620-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF880011DB7F2)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
A third party driver was identified as the probable root cause of this system error.
Google query: KMODE_EXCEPTION_NOT_HANDLED
On Tue 03/12/2013 00:47:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120313-23181-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800B16FE38, 0xFFFFF8800B16F690, 0xFFFFF8000327BDB0)
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
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Mon 02/12/2013 21:35:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120213-23072-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xD0, 0x2, 0x0, 0xFFFFF80003302474)
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
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 01/12/2013 17:03:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120113-22885-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF880041D27F2)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
A third party driver was identified as the probable root cause of this system error.
Google query: KMODE_EXCEPTION_NOT_HANDLED
On Tue 26/11/2013 17:40:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112613-19266-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF88006A587F2)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
A third party driver was identified as the probable root cause of this system error.
Google query: KMODE_EXCEPTION_NOT_HANDLED
On Fri 22/11/2013 17:29:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112213-16333-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF88006FC57F2)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
A third party driver was identified as the probable root cause of this system error.
Google query: KMODE_EXCEPTION_NOT_HANDLED
On Fri 22/11/2013 17:15:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112213-25069-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75169)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000357B957, 0xFFFFF8800CD80090, 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 Tue 19/11/2013 19:37:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111913-16598-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000000.sys (Unloaded_Unknown_Module_00000000`00000000+0x32E3C3)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000326B504, 0xFFFFF88007050F50, 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: unknown_module_00000000`00000000.sys .
Google query: unknown_module_00000000`00000000.sys SYSTEM_SERVICE_EXCEPTION
On Sun 17/11/2013 21:50:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111713-20030-01.dmp
This was probably caused by the following module: _.sys (_+0x39)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001603313, 0xFFFFF8800D11AD90, 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: _.sys .
Google query: _.sys SYSTEM_SERVICE_EXCEPTION
On Sun 17/11/2013 18:49:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111713-19375-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF80003292B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
A third party driver was identified as the probable root cause of this system error.
Google query: KMODE_EXCEPTION_NOT_HANDLED
On Wed 13/11/2013 11:02:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111313-19328-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x17939F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880131A339F, 0xFFFFF88007DC4F28, 0xFFFFF88007DC4780)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a system thread 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.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Sun 10/11/2013 18:12:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111013-18002-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80003294E3F)
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 Sun 10/11/2013 00:09:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111013-17362-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF880010617F2)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003297F5B, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
A third party driver was identified as the probable root cause of this system error.
Google query: KMODE_EXCEPTION_NOT_HANDLED
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
23 crash dumps have been found and analyzed. Only 15 are included in this report. 6 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:
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
_.sys
unknown_module_ffffffffffffffff.sys
unknown_module_00000000_00000002.sys
analysis.sys
unknown_module_00000000`00000000.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.
Read the topic general suggestions for troubleshooting system crashes for more information.
Facebook
Twitter
Instagram