8 odpowiedzi w tym temacie

[zohandv1r]

Witam serdecznie, mam problem z wyskakującymi bluscreenami i nie wiem jak sobie poradzić. Screenshot:

 

http://speedy.sh/x25h8/IMG-1651.JPG

 

Problem pojawia się najczęściej podczas grania.

 

[Miodek]

Upewnij się, że wszystkie możliwe sterowniki do podzespołów są najnowsze.

[zohandv1r]

Sterowniki aktualne; wszystko pobierane ze stron producentów, wyskakuje mi rownież taki blue screen


Wysłane z iPhone za pomocą Tapatalk

[zohandv1r]

Wysłane z iPhone za pomocą Tapatalk

[Miodek]

Od jak dawna występuje problem? Czy było coś robione z systemem / sprzętem zanim pojawił się problem?

Jeśli to nie wina sterowników to stawiam na jakiś podzespół, ewentualnie jakaś usterka w systemie. Z diagnozą poczekam na odpowiedź.

[zohandv1r]

Driver irql not less or uqual występuje kilkunastu mcy. System przeinstalowany pol roku temu


Wysłane z iPhone za pomocą Tapatalk

[zohandv1r]

Ten pierwszy teraz niedawno


Wysłane z iPhone za pomocą Tapatalk

[hhenryk88]

Tutaj http://www.mamkomput...kranie-windows/ masz poradnik jak poradzić sobie z błędami BSOD, czyli z niebieskim ekranem - w skrócie musisz zainstalować odpowiedni program (WhoCrashed), który zidentyfikuje źródło problemu, co umożliwi jego naprawienie.

[zohandv1r]

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 2016-04-03 16:50:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040316-16614-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1898C0)
Bugcheck code: 0xD1 (0xFFFFF8000259706E, 0x2, 0x8, 0xFFFFF8000259706E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Sterownik TCP/IP
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 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 2016-04-03 16:50:02 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 (0xFFFFF8000259706E, 0x2, 0x8, 0xFFFFF8000259706E)
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 Sat 2016-04-02 14:10:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040216-16364-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x85066)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Sterownik TCP/IP
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 2016-04-02 13:20:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040216-17409-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 

 

 

Ktoś pomoże w rozszyfrowaniu genezy problemu?