@Ted Kaczynski Dün gece bilgisayarı kapattıktan sonra HDD'nin SATA kablosunu sökmüştüm. Sabah bilgisayarı açarken "an operating System wasnt found press CTRL alt delete to restart" yazısı aldım. Yeniden başlattım yine aynı yazı geldi. Sonra HDD'nin SATA kablosunu taktım Memory management ve kernel data in page error mavi ekranlarını aldım arka arkaya.
DMP dosyaları
drive.google.com
drive.google.com
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
C:\Users\burak\Desktop\Minidump
On Sun 13.12.2020 14:24:46 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!memset+0xFDB8)
Bugcheck code: 0x7A (0x1, 0xFFFFFFFFC0000005, 0xFFFFCA0B3C3B5340, 0xFFFF843FFA828000)
Error:
KERNEL_DATA_INPAGE_ERROR
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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.12.2020 14:24:46 your computer crashed or a problem was reported
crash dump file: C:\Users\burak\Desktop\Minidump\121320-5968-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x7A (0x1, 0xFFFFFFFFC0000005, 0xFFFFCA0B3C3B5340, 0xFFFF843FFA828000)
Error:
KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 12.12.2020 17:17:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121220-6671-01.dmp
This was probably caused by the following module:
fltmgr.sys (0xFFFFF80310604A1E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80310604A1E, 0xFFFF950E51BEF8E0, 0x0)
Error:
SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® İşletim Sistemi
company: Microsoft Corporation
description: Microsoft Dosya Sistemi Filtre Yöneticisi
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 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 Fri 11.12.2020 11:50:50 your computer crashed or a problem was reported
crash dump file: C:\Users\burak\Desktop\Minidump\121120-5734-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8035AFEDB9F, 0xFFFFFA86173E6050, 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 Fri 11.12.2020 11:50:04 your computer crashed or a problem was reported
crash dump file: C:\Users\burak\Desktop\Minidump\121120-6375-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xA (0xE900000000, 0x2, 0x1, 0xFFFFF8036D665892)
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 Thu 10.12.2020 14:00:12 your computer crashed or a problem was reported
crash dump file: C:\Users\burak\Desktop\Minidump\MEMORY.DMP
This was probably caused by the following module:
hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFF43FFF0D6380, 0x2000000000, 0x0)
Error:
MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
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: hardware.sys .
Google query:
hardware.sys MEMORY_MANAGEMENT
On Thu 10.12.2020 14:00:12 your computer crashed or a problem was reported
crash dump file: C:\Users\burak\Desktop\Minidump\121020-5578-01.dmp
This was probably caused by the following module:
hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFF43FFF0D6380, 0x2000000000, 0x0)
Error:
MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
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: hardware.sys .
Google query:
hardware.sys MEMORY_MANAGEMENT
On Thu 10.12.2020 13:58:31 your computer crashed or a problem was reported
crash dump file: C:\Users\burak\Desktop\Minidump\121020-8390-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x50 (0xFFFFF3DDC0602FE0, 0x0, 0xFFFFF8021AC4D0D4, 0x2)
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 9.12.2020 13:50:32 your computer crashed or a problem was reported
crash dump file: C:\Users\burak\Desktop\Minidump\120920-9453-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801290E55C4, 0xFFFFFB0FCE101E38, 0xFFFFFB0FCE101670)
Error:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_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.
The following dump files were found but could not be read. These files may be corrupted:
C:\Users\burak\Desktop\Minidump\121320-6687-01.dmp
Conclusion
On your computer a total of 12 crash dumps have been found. Only 10 have been analyzed. Only 9 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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:
hardware.sys
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.
drive.google.com
Ve windows update 2OH2 güncellemesi yüklerken hep bu hatayı alıyorum.
