Šta je novo?

PLavi ekran

sasa prvulovic

Poštovan
Učlanjen(a)
24.04.2017
Poruke
8
Poena
51
Pozdrav drugari pocecu ovako sa specifikacijama racunara;

Ploca 760 PI-AM3RS760G2

Procesor Phenom II x4 960 T

Hdd Hitachi HDS721010DLE630-MSK5215H00LR2G-SMART

Gpu Zotac Gtx 650 amp

Ram exceleram ERS303A 2x 4 Gb

Nakon zamene predhodne ploce koja je crkla i sveze instalacije windowsa(Win7)

Dobijam plavi ekran (BSOD) nasumicno nakon nekog vremena nekada nakon 5 minunta a ponekad nakon 1h vremena

Windows memory diagnostic zavrsio bez gresaka


https://1drv.ms/u/s!AlW9_QSvzwDdhiwetIk_C8Mf8vH9
 
On Mon 6/18/2018 9:01:29 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061818-21621-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0xF400000180, 0x2, 0x0, 0xFFFFF80002A3B138)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 6/18/2018 8:59:14 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061818-26223-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF880012AE348)
Bugcheck code: 0x50 (0xFFFFF8000AD149C0, 0x0, 0xFFFFF880012AE348, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Mon 6/18/2018 8:45:49 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061818-58484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0x7800000000, 0x2, 0x1, 0xFFFFF80002CC05A2)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 6/18/2018 8:45:49 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!KeSynchronizeExecution+0x3D39)
Bugcheck code: 0xA (0x7800000000, 0x2, 0x1, 0xFFFFF80002CC05A2)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 6/18/2018 7:36:27 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061818-21013-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0xFFFFFA2A09BB6100, 0x2, 0x1, 0xFFFFF80002CF070F)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 6/18/2018 5:55:56 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061818-22230-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x5E1C)
Bugcheck code: 0x50 (0xFFFFFA00040C0E50, 0x1, 0xFFFFF80002BE2D21, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Mon 6/18/2018 4:30:58 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061818-32183-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF88015335136)
Bugcheck code: 0x50 (0xFFFFFAB10741E0F8, 0x0, 0xFFFFF88015335136, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 361.75
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 361.75
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 361.75 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA



On Mon 6/18/2018 3:45:35 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061818-17752-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF80002614502)
Bugcheck code: 0xA (0xFFFFFAB107589F28, 0x2, 0x0, 0xFFFFF80002614502)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





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

8 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:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 361.75 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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.
 
On Mon 6/18/2018 9:01:29 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061818-21621-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0xF400000180, 0x2, 0x0, 0xFFFFF80002A3B138)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 6/18/2018 8:59:14 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061818-26223-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF880012AE348)
Bugcheck code: 0x50 (0xFFFFF8000AD149C0, 0x0, 0xFFFFF880012AE348, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Mon 6/18/2018 8:45:49 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061818-58484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0x7800000000, 0x2, 0x1, 0xFFFFF80002CC05A2)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 6/18/2018 8:45:49 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!KeSynchronizeExecution+0x3D39)
Bugcheck code: 0xA (0x7800000000, 0x2, 0x1, 0xFFFFF80002CC05A2)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 6/18/2018 7:36:27 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061818-21013-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0xFFFFFA2A09BB6100, 0x2, 0x1, 0xFFFFF80002CF070F)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 6/18/2018 5:55:56 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061818-22230-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x5E1C)
Bugcheck code: 0x50 (0xFFFFFA00040C0E50, 0x1, 0xFFFFF80002BE2D21, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Mon 6/18/2018 4:30:58 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061818-32183-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF88015335136)
Bugcheck code: 0x50 (0xFFFFFAB10741E0F8, 0x0, 0xFFFFF88015335136, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 361.75
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 361.75
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 361.75 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA



On Mon 6/18/2018 3:45:35 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061818-17752-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF80002614502)
Bugcheck code: 0xA (0xFFFFFAB107589F28, 0x2, 0x0, 0xFFFFF80002614502)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





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

8 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:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 361.75 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
 
Pa brate, jesi video u onom linku? Lik je zaustavio BSOD kad je izbacio Nvidia GeForce Experience aplikaciju, probaj bez nje, kao i ostale stvari sa linka.
 
epa *mjau**mjau**mjau* taj link je los
Oh oh, something's wrong
Not Found - Error 404

a i nemam ja taj expirience to *mjau**mjau**mjau**mjau**mjau**mjau* odmah brisem.
 
A pa da, treba obrisati ono na kraju ´http://´
 
Kako da se resim ovog plavetnila?
Najcesce se javlja kad skinem film i prevod sa interneta pa pustim da vidim da li ogovara, a ponekad se desava kad otvorim par tab-ova u mozili.
Uradio sam test ram memorije i nema greske. Probao sam vise instalacija win10.
Uvek mi izbaci drugi error.
0bf2101b3df1390f927912877ecf66a7.jpg
 
Nazad
Vrh Dno