Witam może ktoś wie co może być przyczyną?
Ściągnij:
i włącz analizę
On Sun 2020-04-19 19:43:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041920-6921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0xFFFFDC8939F58000, 0x2, 0x1, 0xFFFFF800533D5512)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](http://www.google.com/search?q=Microsoft® Windows® Operating System)
company: [Microsoft Corporation](http://www.google.com/search?q=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 Sun 2020-04-19 19:42:17 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041920-7187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0xFFFF8900C8B15278, 0xFF, 0x0, 0xFFFFF80017FCFDBC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](http://www.google.com/search?q=Microsoft® Windows® Operating System)
company: [Microsoft Corporation](http://www.google.com/search?q=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 Sun 2020-04-19 19:33:26 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041920-6906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFBD, 0xFF, 0x0, 0xFFFFF805797CDC15)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](http://www.google.com/search?q=Microsoft® Windows® Operating System)
company: [Microsoft Corporation](http://www.google.com/search?q=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 Sun 2020-04-19 17:25:50 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041920-7062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x189 (0xFFFF83033B1D28D0, 0x0, 0x0, 0x0)
Error: BAD_OBJECT_HEADER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](http://www.google.com/search?q=Microsoft® Windows® Operating System)
company: [Microsoft Corporation](http://www.google.com/search?q=Microsoft Corporation)
description: NT Kernel & System
Bug check description: This indicates that The OBJECT_HEADER of a kernel object has been corrupted.
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 2020-04-19 17:24:07 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041920-7109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0x1C, 0x2, 0x0, 0xFFFFF8020B89C41B)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](http://www.google.com/search?q=Microsoft® Windows® Operating System)
company: [Microsoft Corporation](http://www.google.com/search?q=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 Sat 2020-04-18 21:10:03 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041820-7109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C971F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80352FC971F, 0xFFFFEF03DB2952E8, 0xFFFFD7015393B930)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](http://www.google.com/search?q=Microsoft® Windows® Operating System)
company: [Microsoft Corporation](http://www.google.com/search?q=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.
On Fri 2020-04-17 23:18:47 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041720-8937-01.dmp
This was probably caused by the following module: win32kbase.sys (0xFFFF810AAA1BFDB4)
Bugcheck code: 0x50 (0xFFFF810AAE37CCA0, 0x0, 0xFFFF810AAA1BFDB4, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\win32kbase.sys
product: [System operacyjny Microsoft® Windows®](http://www.google.com/search?q=System operacyjny Microsoft® Windows®)
company: [Microsoft Corporation](http://www.google.com/search?q=Microsoft Corporation)
description: Podstawowy sterownik jądra Win32k
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 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 Wed 2020-04-15 23:00:10 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041520-6859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0x41049, 0xFF, 0x0, 0xFFFFF80240E3ECB4)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](http://www.google.com/search?q=Microsoft® Windows® Operating System)
company: [Microsoft Corporation](http://www.google.com/search?q=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.
Conclusion
On your computer a total of 50 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.
No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.