בזמן האחרון, לפעמים שאני משאיר את המשחב בלילה המחשב פשוט קופא, ואני צריך לעשות לו ריסט ידנית.

איך אני יכול לבדוק ממה זה נגרם?

תן יותר פרטים? המחשב קופא הבנתי.

מתי זה התחיל לקרוא? משהו שיעזור לאתר את מקור הבעיה? אני ממליץ לך לאפס את הביוס דבר ראשון.

זה התחיל לפני שבועים.

ומאז הוא קפא איזה 5 פעמים בלילה ללא סיבה.

מבחינת טמפרטורה הכל בסדר.

בביוס לא נגעתי כבר שנה, לכן לא חשבתי על לאפס אותו.

אבל אני יעשה את זה.

[br]פורסם בתאריך: 4.02.2011 בשעה 00:03:35

---

היום היה לי מסך כחול, ואז ריסט.

פעלתי על פי המדריך בנעוץ לבדוק מה גרם לזה.

הורדתי את חבילת הסמלית אבל שאני מנסה לפענח את הקובץ הוא רושם לי "Your debugger is not using the correct symbols ".

מה כדאי לעשות?

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Alex\Desktop\BLUE\020411-16859-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.      *
* Use .symfix to have the debugger choose a symbol path.          *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                  *
* The Symbol Path can be set by:                  *
*  using the _NT_SYMBOL_PATH environment variable.         *
*  using the -y <symbol_path> argument when starting the debugger. *
*  using .sympath and .sympath+                  *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c17000 PsLoadedModuleList = 0x82d5f810
Debug session time: Fri Feb 4 15:12:45.336 2011 (UTC + 2:00)
System Uptime: 0 days 13:30:29.961
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                  *
* The Symbol Path can be set by:                  *
*  using the _NT_SYMBOL_PATH environment variable.         *
*  using the -y <symbol_path> argument when starting the debugger. *
*  using .sympath and .sympath+                  *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                       *
*            Bugcheck Analysis                  *
*                                       *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4A, {82e74510, 2, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                  ***
***                                  ***
***  Your debugger is not using the correct symbols         ***
***                                  ***
***  In order for this command to work properly, your symbol path  ***
***  must point to .pdb files that have full type information.   ***
***                                  ***
***  Certain .pdb files (such as the public OS symbols) do not   ***
***  contain the required information. Contact the group that   ***
***  provided you with these symbols if you need this command to  ***
***  work.                             ***
***                                  ***
***  Type referenced: nt!_KPRCB                   ***
***                                  ***
*************************************************************************
*************************************************************************
***                                  ***
***                                  ***
***  Your debugger is not using the correct symbols         ***
***                                  ***
***  In order for this command to work properly, your symbol path  ***
***  must point to .pdb files that have full type information.   ***
***                                  ***
***  Certain .pdb files (such as the public OS symbols) do not   ***
***  contain the required information. Contact the group that   ***
***  provided you with these symbols if you need this command to  ***
***  work.                             ***
***                                  ***
***  Type referenced: nt!KPRCB                   ***
***                                  ***
*************************************************************************
*************************************************************************
***                                  ***
***                                  ***
***  Your debugger is not using the correct symbols         ***
***                                  ***
***  In order for this command to work properly, your symbol path  ***
***  must point to .pdb files that have full type information.   ***
***                                  ***
***  Certain .pdb files (such as the public OS symbols) do not   ***
***  contain the required information. Contact the group that   ***
***  provided you with these symbols if you need this command to  ***
***  work.                             ***
***                                  ***
***  Type referenced: nt!_KPRCB                   ***
***                                  ***
*************************************************************************
*************************************************************************
***                                  ***
***                                  ***
***  Your debugger is not using the correct symbols         ***
***                                  ***
***  In order for this command to work properly, your symbol path  ***
***  must point to .pdb files that have full type information.   ***
***                                  ***
***  Certain .pdb files (such as the public OS symbols) do not   ***
***  contain the required information. Contact the group that   ***
***  provided you with these symbols if you need this command to  ***
***  work.                             ***
***                                  ***
***  Type referenced: nt!KPRCB                   ***
***                                  ***
*************************************************************************
*************************************************************************
***                                  ***
***                                  ***
***  Your debugger is not using the correct symbols         ***
***                                  ***
***  In order for this command to work properly, your symbol path  ***
***  must point to .pdb files that have full type information.   ***
***                                  ***
***  Certain .pdb files (such as the public OS symbols) do not   ***
***  contain the required information. Contact the group that   ***
***  provided you with these symbols if you need this command to  ***
***  work.                             ***
***                                  ***
***  Type referenced: nt!_KPRCB                   ***
***                                  ***
*************************************************************************
*************************************************************************
***                                  ***
***                                  ***
***  Your debugger is not using the correct symbols         ***
***                                  ***
***  In order for this command to work properly, your symbol path  ***
***  must point to .pdb files that have full type information.   ***
***                                  ***
***  Certain .pdb files (such as the public OS symbols) do not   ***
***  contain the required information. Contact the group that   ***
***  provided you with these symbols if you need this command to  ***
***  work.                             ***
***                                  ***
***  Type referenced: nt!_KPRCB                   ***
***                                  ***
*************************************************************************
*************************************************************************
***                                  ***
***                                  ***
***  Your debugger is not using the correct symbols         ***
***                                  ***
***  In order for this command to work properly, your symbol path  ***
***  must point to .pdb files that have full type information.   ***
***                                  ***
***  Certain .pdb files (such as the public OS symbols) do not   ***
***  contain the required information. Contact the group that   ***
***  provided you with these symbols if you need this command to  ***
***  work.                             ***
***                                  ***
***  Type referenced: nt!_KPRCB                   ***
***                                  ***
*************************************************************************
*************************************************************************
***                                  ***
***                                  ***
***  Your debugger is not using the correct symbols         ***
***                                  ***
***  In order for this command to work properly, your symbol path  ***
***  must point to .pdb files that have full type information.   ***
***                                  ***
***  Certain .pdb files (such as the public OS symbols) do not   ***
***  contain the required information. Contact the group that   ***
***  provided you with these symbols if you need this command to  ***
***  work.                             ***
***                                  ***
***  Type referenced: nt!_KPRCB                   ***
***                                  ***
*************************************************************************
Probably caused by : ntkrnlpa.exe ( nt+25d510 )

Followup: MachineOwner
---------

משהו?

תבדוק אם זה עוזר לך:

http://www.pchelpforum.com/blue-screen-errors/59519-blue-screen-death-ntkrnlpa-exe-causing-blue-screen-death.html

רשום לך בסוף הדאמפ ממה נגרם המסך הכחול , פשוט הרצתי חיפוש בגוגל על זה....

הרצתי גם, ולפי הנאמר הבנתי שזה כתוצאה מדרייברים.

השאלה איך אני מברר איזה מהם בלי להתחיל להסיר את כולם ואז להתקין