PLAVI EKRAN

[ALEKSA1999]

Jedan moj drugar je imao problem sa plavim ekranom. Doneo je njegov racunar kod mene kuci, ja ga nisam ni upalio prvo sam uzeo da mu ocistim prasinu posto je bio mnogo prljav.Meni se sada ne pojavljuje plavi ekran. Da li je moguce da se plavi ekran pojavljivao zbog prasine i vece temperature?

 

[Dexter013]

Zbog pregrevanja, da, moguce je ali ne mora da znaci.
Vidi u logovima detalje i baci ovde.

 

[ilbb]

Stavi WhoCrashed i klikni na Analyze pa će reći zašto

 

[ALEKSA1999]

Stavi WhoCrashed i klikni na Analyze pa će reći zašto

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 9/21/2015 7:30:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092215-15085-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467FB)
Bugcheck code: 0xA (0xFFFFFFFF824AEA20, 0x2, 0x0, 0xFFFFFFFF82AC0354)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 9/20/2015 4:49:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092015-10467-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0xFCC0)
Bugcheck code: 0x19 (0x22, 0xFFFFFFFF82132000, 0x1, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost 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 Sun 9/20/2015 2:01:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092015-10420-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xA06E5)
Bugcheck code: 0x1A (0x3452, 0x143A000, 0xFFFFFFFFC080EFCC, 0x0)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
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 Fri 9/18/2015 3:05:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091815-21871-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467FB)
Bugcheck code: 0xA (0x58, 0x2, 0x1, 0xFFFFFFFF82A500B9)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Fri 9/18/2015 3:03:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091815-9765-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467FB)
Bugcheck code: 0xA (0xFFFFFFFFC00140B8, 0x0, 0x0, 0xFFFFFFFF82AC86C9)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Fri 9/18/2015 2:37:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091815-12792-01.dmp
This was probably caused by the following module: hal.sys (hal+0x3829)
Bugcheck code: 0xA (0xFFFFFFFF821C2890, 0x2, 0x1, 0xFFFFFFFF82E19829)
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 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: hal.sys .
Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL



On Wed 9/16/2015 6:06:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091615-9921-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCE3C)
Bugcheck code: 0x1A (0x41289, 0x14F40001, 0x4701, 0x10F40045)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
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 9/15/2015 8:31:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091515-15912-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467FB)
Bugcheck code: 0xA (0xFFFFFFFFC0015ED0, 0x0, 0x0, 0xFFFFFFFF82A7A6C9)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Tue 9/15/2015 7:36:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091515-10873-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCE3C)
Bugcheck code: 0x1A (0x41284, 0x42EA001, 0x0, 0xFFFFFFFFC0802000)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
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 9/15/2015 7:30:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091515-11154-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xB3B2D)
Bugcheck code: 0x1A (0x5003, 0xFFFFFFFFC0802000, 0x60E1, 0x3A71049)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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.

OVO MI JE SVE IZBACIO DA NE ZNATE U CEMU JE PROBLEM???

 

[hedgehog]

Moze i BlueScreenView

EDIT: Pa po svemu sudeci neki drajveri su u pitanju.
I to izgleda ovaj za HAL, a posto kod tebe verovatno nema utaknutih njegovih dzidzabidza, verovatno zato ne baca BSOD.

EDIT2:Ja sam ovde misloi na na onaj HAL bankarski sistem

 

[ilbb]

Ažuriranje svih drajvera i čišćenje virusa.
Skeniranje diska, memorije i sistemskih fajlova.
Ako ne pomogne svež win.

Kako vidim da se koristi i ReadyBoost, tako da možda nešto oko tog usb uređaja, a sve u svemu nikakve koristi tj boljih performansi od njega nema.

 

[RogPlayer]

Imam i ja provlem sa plavim ekranom, cistio sam racunar i menjao termalnu pastu. Sve sam sastavio u normalno upalio racunar. Sledeci put kad sam upalio izaslo nesto marvel adapter no virtual disk, no psycic disk pa onda ponovo pocrni ekran i izadje no hard disc detected pa onda krene ucitavanje windowsa i iskoci plavi ekran. Kako da ovo rijesim??