עזרה בפיענוח קריסה BSOD ב WINDOWS 10 - תמיכה טכנית למחשבים - HWzone פורומים
עבור לתוכן
  • צור חשבון

עזרה בפיענוח קריסה BSOD ב WINDOWS 10


benyben

Recommended Posts

שלום לכם. 

אני מקבל קריסת מערכת. חלון כחול של 10 (על כל המסך - עם הסמיילי העצוב), וכתוב באנגלית - please wait while we... משהו כזה. 

האם יש דרך לאתר את הפיגוע?

(:

הבנתי שיש דרך לגלות דרך המסך הכחול את העניין הזה. 

אשמח לקבל עצה. 

תודה

 

עדכון: 

הורדתי את WHOCRASHED

הנה הדוח: 

 

 

Crash Dump Analysis



Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 23-03-2017 6:53:18 PM your computer crashed
crash dump file: C:\Windows\Minidump\032317-4953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x139 (0x3, 0xFFFFC481130E8830, 0xFFFFC481130E8788, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




On Tue 21-03-2017 11:16:28 AM your computer crashed
crash dump file: C:\Windows\Minidump\032117-3984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x139 (0x3, 0xFFFFDA8173945830, 0xFFFFDA8173945788, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




On Wed 08-03-2017 4:55:52 PM your computer crashed
crash dump file: C:\Windows\Minidump\030817-5109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xC2 (0x7, 0x5246704E, 0x40B0006, 0xFFFFA70DC6BF42C0)
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 kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




On Thu 23-02-2017 9:06:51 PM your computer crashed
crash dump file: C:\Windows\Minidump\022317-13515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x139 (0x3, 0xFFFFAC00EEFB4ED0, 0xFFFFAC00EEFB4E28, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 11-02-2017 10:01:40 PM your computer crashed
crash dump file: C:\Windows\Minidump\021117-3687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xC2 (0x7, 0x44696457, 0x40B0001, 0xFFFF8F891D187890)
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



5 crash dumps have been found and analyzed. 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 on the bug check errors together with the model name and brand of your computer may help you investigate this further.


 

קישור לתוכן
שתף באתרים אחרים

ארכיון

דיון זה הועבר לארכיון ולא ניתן להוסיף בו תגובות חדשות.

×
  • צור חדש...