בעיה בקריאת קבצי DUMP.

2009 בנובמבר 14

עבדתי לפי המדריך שבסטיקי ובמקום מה שצריך להופיע לי, זה מה שמופיע לי:

Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64

Loading Dump File [C:\Windows\Minidump\110809-20638-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

ואין את הסיבה לבעיה כמו במדריך, מה אני עושה?

multicore · 2009 בנובמבר 14

תוריד את ה symbol library למערכת ההפעלה שלך.

2009 בנובמבר 15

זה מה שזה נתן לי:

Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64

Loading Dump File [C:\Windows\Minidump\110809-21715-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: D:\Symbols

Executable search path is:

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 7600 MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Machine Name:

Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50

Debug session time: Sun Nov 8 08:17:17.061 2009 (GMT+2)

System Uptime: 0 days 15:40:18.653

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 D1, {80000028, 2, 0, fffff88001624b1c}

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

*** ***

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

*** WARNING: Unable to verify timestamp for ndis.sys

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

*** ***

*** 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 : ndis.sys ( ndis!NdisMQueueDpcEx+4b )

Followup: MachineOwner

---------

0: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: 0000000080000028, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

Arg4: fffff88001624b1c, address which referenced memory

Debugging Details:

------------------

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

*** ***

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

ADDITIONAL_DEBUG_TEXT:

Use '!findthebuild' command to search for the target build information.

If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: ndis

FAULTING_MODULE: fffff80002a5f000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc184

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

0000000080000028

CURRENT_IRQL: 0

FAULTING_IP:

ndis!NdisMQueueDpcEx+4b

fffff880`01624b1c 8b4828 mov ecx,dword ptr [rax+28h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from fffff80002ad0469 to fffff80002ad0f00

STACK_TEXT:

fffff880`0af0bab8 fffff800`02ad0469 : 00000000`0000000a 00000000`80000028 00000000`00000002 00000000`00000000 : nt+0x71f00

fffff880`0af0bac0 00000000`0000000a : 00000000`80000028 00000000`00000002 00000000`00000000 fffff880`01624b1c : nt+0x71469

fffff880`0af0bac8 00000000`80000028 : 00000000`00000002 00000000`00000000 fffff880`01624b1c fffffa80`0528d800 : 0xa

fffff880`0af0bad0 00000000`00000002 : 00000000`00000000 fffff880`01624b1c fffffa80`0528d800 00000000`00000000 : 0x80000028

fffff880`0af0bad8 00000000`00000000 : fffff880`01624b1c fffffa80`0528d800 00000000`00000000 00000000`00000000 : 0x2

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:

ndis!NdisMQueueDpcEx+4b

fffff880`01624b1c 8b4828 mov ecx,dword ptr [rax+28h]

SYMBOL_NAME: ndis!NdisMQueueDpcEx+4b

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ndis.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

---------

[br]פורסם בתאריך: 15.11.2009 בשעה 17:47:35

והשני:

Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64

Loading Dump File [C:\Windows\Minidump\110809-20638-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: D:\Symbols

Executable search path is:

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 7600 MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Machine Name:

Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c5ae50

Debug session time: Sun Nov 8 09:07:17.300 2009 (GMT+2)

System Uptime: 0 days 0:48:27.496

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

......

Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for dxgkrnl.sys

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8003c1a160, fffff880048ef220, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

***** 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 : nvlddmkm.sys ( nvlddmkm!DriverEntry+dc560 )

Followup: MachineOwner

---------

multicore · 2009 בנובמבר 15

Your debugger is not using the correct symbols

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

2009 בנובמבר 16

אוקיי מצטער לא שמתי לב, הנה:

CRASH 1:

A problem has been detected and Windows has been shut down to prevent damage

to your computer.

The problem seems to be caused by the following file: dxgkrnl.sys

If this is the first time you've seen this stop error screen,

restart your computer. If this screen appears again, follow

these steps:

Check to make sure any new hardware or software is properly installed.

If this is a new installation, ask your hardware or software manufacturer

for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware

or software. Disable BIOS memory options such as caching or shadowing.

If you need to use safe mode to remove or disable components, restart

your computer, press F8 to select Advanced Startup Options, and then

select Safe Mode.

Technical Information:

*** STOP: 0x00000116 (0xfffffa8003c1a160, 0xfffff880048ef220, 0x0000000000000000,

0x0000000000000002)

*** dxgkrnl.sys - Address 0xfffff8800532aef8 base at 0xfffff880052ce000 DateStamp

0x4ac5509e

CRASH2:

A problem has been detected and Windows has been shut down to prevent damage

to your computer.

The problem seems to be caused by the following file: ndis.sys

DRIVER_IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this stop error screen,

restart your computer. If this screen appears again, follow

these steps:

Check to make sure any new hardware or software is properly installed.

If this is a new installation, ask your hardware or software manufacturer

for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware

or software. Disable BIOS memory options such as caching or shadowing.

If you need to use safe mode to remove or disable components, restart

your computer, press F8 to select Advanced Startup Options, and then

select Safe Mode.

Technical Information:

*** STOP: 0x000000d1 (0x0000000080000028, 0x0000000000000002, 0x0000000000000000,

0xfffff88001624b1c)

*** ndis.sys - Address 0xfffff88001624b1c base at 0xfffff88001623000 DateStamp

0x4a5bc184

וכמעט כל יום קורה שכשאני משחק במשחק, זה פשוט יוצא מהמשחק ורושם את זה:

Description

A problem with your video hardware caused Windows to stop working correctly.

Problem signature

Problem Event Name: LiveKernelEvent

OS Version: 6.1.7600.2.0.0.256.1

Locale ID: 1037

Files that help describe the problem

WD-20091108-0907.dmp

sysdata.xml

WERInternalMetadata.xml

View a temporary copy of these files

Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem

BCCode: 117

BCP1: FFFFFA8003C1A160

BCP2: FFFFF880048EF220

BCP3: 0000000000000000

BCP4: 0000000000000000

OS Version: 6_1_7600

Service Pack: 0_0

Product: 256_1

BlueScreenView v1.15

Web site: http://www.nirsoft.net

הדרייברים לכרטיס מסך מעודכנים!

E8400

4GIGA GSKILL

260GTX

multicore · 2009 בנובמבר 16

dxgkrnl.sys

בעייה של DirectX שיצא לך לה תיקון לפני שלושה ימים. מתי עשית Windows Update לאחרונה?

ndis.sys

בעייה של כרטיס רשת. תראה אם יש עדכון לדרייבר שלו וכמובן להציץ בWU כמו שהולץ מקודם.

Files that help describe the problem
WD-20091108-0907.dmp

נוצר לך קובץ dump גם פה.

2009 בנובמבר 16

תודה על העזרה!!! הקראשים גם כללו:

ntoskrnl.exe

dxgmms1.sys

nvlddmkm.sys

ובקשר לקראש של הכרטיס מסך, הקובץ DUMP הזה לא קיים.

התחברות

בעיה בקריאת קבצי DUMP.

Recommended Posts

אורח

קישור לתוכן

שתף באתרים אחרים

קישור לתוכן

שתף באתרים אחרים

אורח

קישור לתוכן

שתף באתרים אחרים

קישור לתוכן

שתף באתרים אחרים

אורח

קישור לתוכן

שתף באתרים אחרים

קישור לתוכן

שתף באתרים אחרים

אורח

קישור לתוכן

שתף באתרים אחרים

ארכיון

דיונים חדשים

כתבות אחרונות

גנגסטרים אמיתיים עיצבו מחדש את הדיאלוגים ב-GTA San Andreas: כשהמציאות פוגשת את עולם המשחקים

2024-06-22

פרצת אבטחה חמורה במעבדי אינטל: עלולה להשפיע על מאות דגמי מחשבים

מהלך דרמטי בצרפת: גוגל, קלאודפלייר וסיסקו נאלצות לחסום גישה לאתרי פיראטיות

2024-06-18

פירצת אבטחה חמורה ב-Windows: האקרים יכולים לחדור למחשב שלכם דרך רשתות Wi-Fi

2024-06-17

לחיצות על בננה וירטואלית שהפכו לכסף אמיתי: הכירו את המשחק החדש שמשגע את Steam

2024-06-15

מתגעגעים לטמגוצ'י? תתכוננו לחיית מחמד וירטואלית בסטורי שלכם, שתגדל לפי כמות הלייקים שתקבלו

2024-06-14

מבצעים מרחבי הרשת

הכי נצפה