Lenovo Y50-70 po pádu BSOD
Zdravím všechny,
upadl mi NTB ze stolu, rozbil se displej. Nechal jsem ho vyměnit a od té doby mám nepravidelně BSOD. Udělal jsem čistej reinstal a pořád. Poznáte něco z prohlížeče událostí?? Díky všem.
Název protokolu:System
Zdroj: Microsoft-Windows-Kernel-Power
Datum: 3/10/2019 1:01:38 PM
ID události: 41
Kategorie úlohy:(63)
Úroveň: Kritická
Klíčová slova: (2)
Uživatel: SYSTEM
Počítač: win7-PC
Popis:
Systém se znovu restartoval, aniž by se předtím zcela vypnul. Tato chyba mohla být způsobena tím, že systém přestal reagovat, selhal nebo že došlo k neočekávané ztrátě napájení.
Kód XML události:
41
2
1
63
0
0x8000000000000002
4977
System
win7-PC
59
0xc0000005
0xfffff80002f09050
0xfffff88002761970
0x0
false
0
upadl mi NTB ze stolu, rozbil se displej. Nechal jsem ho vyměnit a od té doby mám nepravidelně BSOD. Udělal jsem čistej reinstal a pořád. Poznáte něco z prohlížeče událostí?? Díky všem.
Název protokolu:System
Zdroj: Microsoft-Windows-Kernel-Power
Datum: 3/10/2019 1:01:38 PM
ID události: 41
Kategorie úlohy:(63)
Úroveň: Kritická
Klíčová slova: (2)
Uživatel: SYSTEM
Počítač: win7-PC
Popis:
Systém se znovu restartoval, aniž by se předtím zcela vypnul. Tato chyba mohla být způsobena tím, že systém přestal reagovat, selhal nebo že došlo k neočekávané ztrátě napájení.
Kód XML události:
59
0xc0000005
0xfffff80002f09050
0xfffff88002761970
0x0
false
0
Z toho asi moc ne. Můžeš zkusit aplikaci WhoCrashed:
http://www.servispckupka.cz/stop_modra_obrazovka_windows_whocrashed.php
nebo WinDBG:
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools
S tím nemám zkušenost ...
http://www.servispckupka.cz/stop_modra_obrazovka_windows_whocrashed.php
nebo WinDBG:
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools
S tím nemám zkušenost ...
On Mon 3/11/2019 9:40:00 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031119-7129-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x93BA0)
Bugcheck code: 0xA (0x800000, 0x2, 0x0, 0xFFFFF80002C908B2)
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 3/11/2019 9:33:23 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031119-9516-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8800125DEA0)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88006BF81F8, 0xFFFFF88006BF7A60, 0xFFFFF8800125DEA0)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Sun 3/10/2019 11:47:25 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031019-8548-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x93BA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F09050, 0xFFFFF88002761970, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 3/6/2019 3:10:04 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\030619-6364-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0x50 (0xFFFFF8E0009CF9BC, 0x1, 0xFFFFF80002DBAFB2, 0x5)
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.
On Wed 3/6/2019 1:23:10 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\030619-6396-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0x50 (0xFFFFF88009034A68, 0x1, 0xFFFFF80002F649A9, 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.
crash dump file: C:\Windows\Minidump\031119-7129-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x93BA0)
Bugcheck code: 0xA (0x800000, 0x2, 0x0, 0xFFFFF80002C908B2)
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 3/11/2019 9:33:23 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031119-9516-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8800125DEA0)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88006BF81F8, 0xFFFFF88006BF7A60, 0xFFFFF8800125DEA0)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Sun 3/10/2019 11:47:25 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031019-8548-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x93BA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F09050, 0xFFFFF88002761970, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 3/6/2019 3:10:04 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\030619-6364-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0x50 (0xFFFFF8E0009CF9BC, 0x1, 0xFFFFF80002DBAFB2, 0x5)
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.
On Wed 3/6/2019 1:23:10 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\030619-6396-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0x50 (0xFFFFF88009034A68, 0x1, 0xFFFFF80002F649A9, 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.
Jen takový malý dotaz, pokud nemáš ssd verzi, zkoušel jsi surface test povrchu disku?
Bug check description: This indicates a problem occurred in the NTFS file system.
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.
Bug check description: This indicates a problem occurred in the NTFS file system.
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.
@dzandra Mám SSD.
Udělal jsem včera ješte jednou čistej reinstal a zas to spadlo.
https://ufile.io/f4ndd
Udělal jsem včera ješte jednou čistej reinstal a zas to spadlo.
https://ufile.io/f4ndd
Reinstall systému Ti nepomůže, neboť Bug Check 0x124 poukazuje na kritickou hardwarovou chybu. S největší pravděpodobností se jedná o chybu procesoru/základní desky.
Doporučuji notebook rozebrat a zkontrolovat řádné uchycení procesoru v patici a systému chlazení. Dále bych prošel veškeré konektory. V neposlední řadě proveď test operační paměti pomocí MemTest86 nebo MemTest+.
Po čisté instalaci systému nainstaloval jsi všechny ovladače pro Win7 správně?
EDIT: Zkontroluj i pevný disk utilitou výrobce.
Doporučuji notebook rozebrat a zkontrolovat řádné uchycení procesoru v patici a systému chlazení. Dále bych prošel veškeré konektory. V neposlední řadě proveď test operační paměti pomocí MemTest86 nebo MemTest+.
Po čisté instalaci systému nainstaloval jsi všechny ovladače pro Win7 správně?
EDIT: Zkontroluj i pevný disk utilitou výrobce.
