שלום.

המחשב לפתע הציג מסך כחול.

הנה הדו"ח:

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional information about the problem:

BCCode: 7f

BCP1: 0000000000000008

BCP2: 0000000080050031

BCP3: 00000000000006F8

BCP4: FFFFF80002F02BDB

OS Version: 6_1_7601

Service Pack: 1_0

Product: 256_1

Files that help describe the problem:

C:\Windows\Minidump\050211-28610-01.dmp

C:\Users\Black965\AppData\Local\Temp\WER-36239-0.sysdata.xml

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

מה פשר העניין ???

אם יש לך קובץ DMP (דמפ) (כמו שנראה שכן יש לך: C:\Windows\Minidump\050211-28610-01.dmp)

תעלה אותו ותשלח קישור או שתצרף את הקובץ

בכל מקרה אתה יכול לנתח את הקובץ בעצמך בעזרת המדריך הבא:

http://hwzone.co.il/community/index.php?topic=124642.msg1014561#msg1014561

תודה רבה!!!

מצאתי את הקובץ.

אבל - איך פותחים אותו? עם תכונת הטקסט?

ואם אפשר להעלות - איך מעלים? לאן?

תודה

Loading Dump File [C:\Windows\Minidump\050211-28610-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\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850

Machine Name:

Kernel base = 0xfffff800`02e62000 PsLoadedModuleList = 0xfffff800`030a7e90

Debug session time: Mon May 2 14:24:56.775 2011 (UTC - 7:00)

System Uptime: 4 days 3:55:39.938

*********************************************************************

* 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\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Loading Kernel Symbols

...............................................................

................................................................

...........................

Loading User Symbols

Loading unloaded module list

..................................................

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff80002f02bdb}

***** 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 ***

*** ***

*************************************************************************

Probably caused by : ntoskrnl.exe ( nt+80640 )

Followup: MachineOwner

---------

אם מדובר על Windows XP אז תנסה:

http://www.computerhope.com/issues/ch000646.htm

http://www.google.co.il/search?q=ntoskrnl.exe&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:he:official&client=firefox-a

עם 7 אז תבדוק:

http://www.google.co.il/search?hl=iw&client=firefox-a&hs=j7D&rls=org.mozilla%3Ahe%3Aofficial&q=ntoskrnl.exe+win7&aq=0s&aqi=g-s1g3&aql=&oq=ntoskrnl.exe+w

http://windows7forums.com/blue-screen-death-bsod/43572-windows-7-blue-screen-ntoskrnl-exe.html

מוטי, קראת בכלל מה שהוא הדביק?

***  Your debugger is not using the correct symbols         ***

פותח הדיון, תשתמי בלי יותר פשוט כמו זה. לא חיבים באמת התקין את כל הסט של WinDbg כדי לנתח קבצי memory dump.

פדיחה!! לא סמתי לב לזה..

תגיד, בקשר לפוסט הראשון שלי...

איך ידעת שזה ה NETLIMITER

עכשיו שאני חוזר לבדוק את הדאמפ אני רואה את זה:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini040511-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: D:\Symbols\
Executable search path is: 

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to load image nt, Win32 error 0n2
Unable to add module at 00000000
Debugger can not determine kernel base address
Windows Server 2003 Kernel Version 3790 (Service Pack 2) UP Free x86 compatible
Product: LanManNt, suite: Enterprise TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a8e48
Debug session time: Tue Apr 5 16:58:08.937 2011 (UTC + 2:00)
System Uptime: 0 days 0:12:43.546

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to load image nt, Win32 error 0n2
Unable to add module at 00000000
Debugger can not determine kernel base address
Loading Kernel Symbols

Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                       *
*            Bugcheck Analysis                  *
*                                       *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, f65cbad4, f51cb898, 0}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image ( Unknown_Module_c7b3cc47>+2ea8ee8d )

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

אין פה זכר ל NETLIMITER...

משום מה הקובץ DUMP נעלם!!!!!

אתה ממשיך להתעלם מתוכן הטקסט?

סליחה אני באמת לא מתכוון להיות נודניק. אבל אני מבולבל. איזה תוכן טקסט?

כל שהבנתי זה שיש להוריד את התכונה WhoCrahsed.

הורדתי אותה.

אבל לא רק שאני לא מבין כל כך איך להפנות אותה אל הקובץ, אלא שהקובץ משום מה לא נמצא שם יותר.

זה הכל.