u pitanju je racunar koji je tek kupljen (pre mozda 2-3 meseca)
ovo mi iskace skoro svaki put kad radi duze od recimo 10 sati dnevno
stvarno ne znam sta je u pitanju,pa ako bi mogli ovde da mi pomognete
ako je potrebno da znate koja je konfiguracija,recite...

http://img40.imageshack.us/img40/6767/errorqy.jpg

 Preuzmi instalaciju za WhoCrashed program sa sledeceg linka:
http://www.resplendence.com/download/whocrashedSetup.exe
Ovaj program ce analizom pokusati proveriti koji drajver je uzrocnik greske.
Napomena: ovaj program zahteva instalaciju.


Dvoklikom pokreni instalaciju i klikni Next.

• Stikliraj opciju I Accept the agreement pa zatim ponovo na Next.
  Program instaliraj na onu lokaciju i pod onim imenom koju ti program ponudi.
  
• Klikni na Next i u sledecem prozoru klikni Next
  
• Stikliraj opciju Create a Desktop Icon i potom klikni na Next pa zatim na Install.
  
  
  
  
   Kada instaliras WhoCrashed program,pokreni ga.
  
  Napomena: Ukoliko ti program izbaci obavestenje koje bi trebalo da izgleda ovako:
  
  Klikni na Download the requested file from Microsoft site now i pricekaj da se proces
  preuzimanja dodatnih fajlova i njihova instalacija dovrsi.
  
  
  Kada se program pokrene klikni na dugme Analyze.
  Kada program zavrsi analizu izbacice ti prozor sa obavestenjem. Klikni Ok.
  
  
• Desni klik na prostor stranice programa sa izvestajem i izaberi opciju Select All.
  
• Desni klik na prostor stranice programa sa izvestajem i izaberi opciju Copy
  
• Otvori novi notepad i izaberi opciju Paste da bi kopirao sadrzaj loga u notepad.
  

Sada mozes zatvoriti program.

 Okaci notepad sa sadrzajem loga u sledecu poruku.

System Information (local)
--------------------------------------------------------------------------------

computer name: DJORDJE-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X4 965 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 8587350016 total
VM: 2147352576, free: 1987690496




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 13-Jan-13 18:52:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011413-22604-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x5FFA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88007D34FA0, 0xFFFFF8800A9C70F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 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 13-Jan-13 18:52:20 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (0xFFFFF88007D34FA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88007D34FA0, 0xFFFFF8800A9C70F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 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 09-Jan-13 05:44:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010913-21496-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x79E0)
Bugcheck code: 0x116 (0xFFFFFA80070C1010, 0xFFFFF8800695D9E0, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR



On Tue 08-Jan-13 18:36:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010813-21886-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFFA800B52D000, 0x0, 0xFFFFF80002ED0F7A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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
--------------------------------------------------------------------------------

4 crash dumps have been found and analyzed. A third party driver has 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:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

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.

Note that it's not always possible to state with certainty whether a reported driver is actually 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.

Zeza te drajver za grafiku ATI.

Preuzmi najnoviji drajver sa sajta proizvodjaca.
Prvo deinstaliraj stari, pa onda instaliraj drajver koji si preuzeo.

Takodje azuriraj DirectX
http://www.microsoft.com/en-us/download/details.aspx?id=35

izgleda da je to bio problem,mada mi nije jasno sto bi pravio problem drajver samo 2 verzije stariji i koji sam dobio uz graficku na disku,ali nema veze...bitno je da sad radi...u svakom slucaju hvala puno

izgleda da ipak nije to problem...opet mi je izbacio bsod i sa najnovijim drajverima...cak sam i izvadio graficku i povezao na integrisanu i opet mi je izbacio bsod...

Postavi ponovo izvestaj da vidimo sta je prouzrokovalo zadnji BSOD.

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 16-Jan-13 00:55:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-14211-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Wed 16-Jan-13 00:55:56 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 15-Jan-13 21:27:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011513-18033-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x90FD4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800030ADFD4, 0xFFFFF880009A9968, 0xFFFFF880009A91D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HA NDLED_M
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 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.
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 13-Jan-13 18:52:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011413-22604-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x5FFA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88007D34FA0, 0xFFFFF8800A9C70F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 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 09-Jan-13 05:44:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010913-21496-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x79E0)
Bugcheck code: 0x116 (0xFFFFFA80070C1010, 0xFFFFF8800695D9E0, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR



On Tue 08-Jan-13 18:36:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010813-21886-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFFA800B52D000, 0x0, 0xFFFFF80002ED0F7A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. A third party driver has 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:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

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.

Note that it's not always possible to state with certainty whether a reported driver is actually 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.

file path: C:\Windows\system32\ntoskrnl.exe

Hmm ovo moze da znaci svasta, najverovatnije hardverski problem. Ako je racunar u garanciji nosi pod hitno.

Mozes da testiras ram module. na Hirensu imas Memtest, pa probaj. Ili ako imas dva modula, da probas da izvadis jedan pa da vidis kako se ponasa, pa drugi (ako imas dva).

Sve to ako nije zalepljena nalepnica na kucistu pozadi. Ako ima nalepnica onda ne smes da ga otvaras.

sad vec pocinjem da ludim,jer sam vec jednom nosio da mi zamene ram jer nije valjao i bio sam bez kompa 20 dana... a jel mozes da mi kazes na koju komponentu sumnjas da stvara probleme?