هذا هو تقرير عن جهازي ببرنامج WhoCrashed ارجوا وضع حل لتلك الشاشة اللعينه
System Information (local)
Computer name: DESKTOP-E4NDHOA
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., B150M PRO GAMING
CPU: GenuineIntel Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8467849216 bytes total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Tue 01/08/2017 02:35:09 م your computer crashed
crash dump file: C:\WINDOWS\Minidump\080117-23203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0xC2 (0x7, 0xFFFF9882, 0x94D5D4B0, 0xFFFF98829621C13
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 Mon 31/07/2017 12:39:39 ص your computer crashed
crash dump file: C:\WINDOWS\Minidump\073117-19593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0xC2 (0x7, 0xFFFF9F01, 0x553DF118, 0xFFFFC90D0DBC2BE
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 30/07/2017 10:55:34 م your computer crashed
crash dump file: C:\WINDOWS\Minidump\073017-21734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0xC2 (0x7, 0x182D6650, 0x182D6650, 0xFFFFAA0547C860F
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 30/07/2017 01:46:44 م your computer crashed
crash dump file: C:\WINDOWS\Minidump\073017-16875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0xC2 (0x7, 0x477061AE, 0x50EE2E25, 0xFFFF8985D125A8F
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 29/07/2017 03:41:13 م your computer crashed
crash dump file: C:\WINDOWS\Minidump\072917-15234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0xC2 (0x7, 0x65, 0x780065, 0xFFFFB1809264554
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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.
Conclusion
7 crash dumps have been found and analyzed. Only 5 are included in this report. 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.
ما هو حل الشاشة الزرقاء في windows 10 creator update
رد مع اقتباس
المشاركة الأصلية كتبت بواسطة ironfighter
المفضلات