Blue screen windows 7 Problem :: Pc Klinika ~ Doktori za vas kompjuter

Skinuo sam taj program i ovo mi pise

computer name: FILIP-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) II X4 620 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 2146738176 total
VM: 2147352576, free: 2009681920

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 5/6/2014 8:42:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050614-13088-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x6CCD6)
Bugcheck code: 0x50 (0xFFFFFFFFFFB14B6C, 0x0, 0xFFFFFFFF979BCC3F, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 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 Tue 5/6/2014 8:42:38 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngFreeMem+0xB6C)
Bugcheck code: 0x50 (0xFFFFFFFFFFB14B6C, 0x0, 0xFFFFFFFF979BCC3F, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 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 5/4/2014 6:20:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050414-15085-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x6CCD6)
Bugcheck code: 0x50 (0xFFFFFFFFFBF4601C, 0x0, 0xFFFFFFFF9751CC3F, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 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 5/3/2014 7:44:12 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050314-13369-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0xB7C7)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A95F01, 0xFFFFFFFF99A07A4C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HAND LED_M
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display 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 Sat 4/26/2014 12:11:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042614-19765-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBBD01)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF974CBD01, 0xFFFFFFFF903F4B98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HAND LED_M
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 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 Sat 4/26/2014 9:20:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042614-19219-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x6CCD6)
Bugcheck code: 0x50 (0xFFFFFFFFFDD9D424, 0x0, 0xFFFFFFFF971CCC3F, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 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 Fri 4/25/2014 4:21:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042514-15038-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0xB7C7)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82AC2F01, 0xFFFFFFFF9FD0BA4C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HAND LED_M
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display 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 Thu 4/24/2014 8:43:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042414-12698-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0xB527)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82AC8F01, 0xFFFFFFFF8F9F0B40, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HAND LED_M
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display 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 Thu 4/24/2014 7:30:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042414-11980-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBBD01)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9771BD01, 0xFFFFFFFF8F9D8B98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HAND LED_M
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 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 Wed 4/23/2014 1:46:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042314-13291-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x4E (0x99, 0x0, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 4/22/2014 6:04:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042214-12948-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x1276)
Bugcheck code: 0x10E (0x1F, 0xFFFFFFFF9C5126B8, 0x0, 0x271EF)
Error: VIDEO_MEMORY_MANAGEMENT_INTERN AL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
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 Tue 4/22/2014 5:18:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042214-12651-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x4E (0x99, 0x3BBBC, 0x2, 0x3BBBB)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 4/22/2014 8:30:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042214-14430-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x3DA9)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF82B3FBA8, 0xFFFFFFFF82B3FBB8, 0xFFFFFFFF82B3FBB8)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 Fri 4/18/2014 12:02:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041814-15756-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBBD01)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF98B8BD01, 0xFFFFFFFF901E4BC4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HAND LED_M
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 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 Fri 4/18/2014 7:29:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041814-16239-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x858E3)
Bugcheck code: 0x50 (0xFFFFFFFFB35D1C50, 0x0, 0xFFFFFFFF82AAC813, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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.

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

17 crash dumps have been found and analyzed. Only 15 are included in this report. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.