פורסם 2009 בנובמבר 1416 שנים עבדתי לפי המדריך שבסטיקי ובמקום מה שצריך להופיע לי, זה מה שמופיע לי:Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64Copyright © Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\110809-20638-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: ואין את הסיבה לבעיה כמו במדריך, מה אני עושה?
פורסם 2009 בנובמבר 1516 שנים זה מה שזה נתן לי:Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64Copyright © Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\110809-21715-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: D:\SymbolsExecutable 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.exeWindows 7 Kernel Version 7600 MP (2 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7600.16385.amd64fre.win7_rtm.090713-1255Machine Name:Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50Debug session time: Sun Nov 8 08:17:17.061 2009 (GMT+2)System Uptime: 0 days 15:40:18.653Unable 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.exeLoading Kernel Symbols......................................................................................................................................................Loading User SymbolsLoading 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 aninterrupt request level (IRQL) that is too high. This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: 0000000080000028, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000000, value 0 = read operation, 1 = write operationArg4: fffff88001624b1c, address which referenced memoryDebugging 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: ndisFAULTING_MODULE: fffff80002a5f000 ntDEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc184READ_ADDRESS: unable to get nt!MmSpecialPoolStartunable to get nt!MmSpecialPoolEndunable to get nt!MmPoolCodeStartunable to get nt!MmPoolCodeEnd 0000000080000028 CURRENT_IRQL: 0FAULTING_IP: ndis!NdisMQueueDpcEx+4bfffff880`01624b1c 8b4828 mov ecx,dword ptr [rax+28h]CUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULTBUGCHECK_STR: 0xD1LAST_CONTROL_TRANSFER: from fffff80002ad0469 to fffff80002ad0f00STACK_TEXT: fffff880`0af0bab8 fffff800`02ad0469 : 00000000`0000000a 00000000`80000028 00000000`00000002 00000000`00000000 : nt+0x71f00fffff880`0af0bac0 00000000`0000000a : 00000000`80000028 00000000`00000002 00000000`00000000 fffff880`01624b1c : nt+0x71469fffff880`0af0bac8 00000000`80000028 : 00000000`00000002 00000000`00000000 fffff880`01624b1c fffffa80`0528d800 : 0xafffff880`0af0bad0 00000000`00000002 : 00000000`00000000 fffff880`01624b1c fffffa80`0528d800 00000000`00000000 : 0x80000028fffff880`0af0bad8 00000000`00000000 : fffff880`01624b1c fffffa80`0528d800 00000000`00000000 00000000`00000000 : 0x2STACK_COMMAND: .bugcheck ; kbFOLLOWUP_IP: ndis!NdisMQueueDpcEx+4bfffff880`01624b1c 8b4828 mov ecx,dword ptr [rax+28h]SYMBOL_NAME: ndis!NdisMQueueDpcEx+4bFOLLOWUP_NAME: MachineOwnerIMAGE_NAME: ndis.sysBUCKET_ID: WRONG_SYMBOLSFollowup: MachineOwner---------[br]פורסם בתאריך: 15.11.2009 בשעה 17:47:35והשני:Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64Copyright © Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\110809-20638-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: D:\SymbolsExecutable 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.exeWindows 7 Kernel Version 7600 MP (2 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7600.16385.amd64fre.win7_rtm.090713-1255Machine Name:Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c5ae50Debug session time: Sun Nov 8 09:07:17.300 2009 (GMT+2)System Uptime: 0 days 0:48:27.496Unable 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.exeLoading Kernel Symbols...................................................................................................................................................Loading User SymbolsLoading 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---------
פורסם 2009 בנובמבר 1516 שנים Your debugger is not using the correct symbolsבאמת שלא חחיב להדביק את כל זה. ניסית בכלל לקרוא מה כתוב לך שם קודם?
פורסם 2009 בנובמבר 1616 שנים אוקיי מצטער לא שמתי לב, הנה:CRASH 1:A problem has been detected and Windows has been shut down to prevent damageto your computer.The problem seems to be caused by the following file: dxgkrnl.sysIf this is the first time you've seen this stop error screen,restart your computer. If this screen appears again, followthese steps:Check to make sure any new hardware or software is properly installed.If this is a new installation, ask your hardware or software manufacturerfor any Windows updates you might need.If problems continue, disable or remove any newly installed hardwareor software. Disable BIOS memory options such as caching or shadowing.If you need to use safe mode to remove or disable components, restartyour computer, press F8 to select Advanced Startup Options, and thenselect Safe Mode.Technical Information:*** STOP: 0x00000116 (0xfffffa8003c1a160, 0xfffff880048ef220, 0x0000000000000000, 0x0000000000000002)*** dxgkrnl.sys - Address 0xfffff8800532aef8 base at 0xfffff880052ce000 DateStamp 0x4ac5509eCRASH2:A problem has been detected and Windows has been shut down to prevent damageto your computer.The problem seems to be caused by the following file: ndis.sysDRIVER_IRQL_NOT_LESS_OR_EQUALIf this is the first time you've seen this stop error screen,restart your computer. If this screen appears again, followthese steps:Check to make sure any new hardware or software is properly installed.If this is a new installation, ask your hardware or software manufacturerfor any Windows updates you might need.If problems continue, disable or remove any newly installed hardwareor software. Disable BIOS memory options such as caching or shadowing.If you need to use safe mode to remove or disable components, restartyour computer, press F8 to select Advanced Startup Options, and thenselect Safe Mode.Technical Information:*** STOP: 0x000000d1 (0x0000000080000028, 0x0000000000000002, 0x0000000000000000, 0xfffff88001624b1c)*** ndis.sys - Address 0xfffff88001624b1c base at 0xfffff88001623000 DateStamp 0x4a5bc184וכמעט כל יום קורה שכשאני משחק במשחק, זה פשוט יוצא מהמשחק ורושם את זה:DescriptionA problem with your video hardware caused Windows to stop working correctly.Problem signatureProblem Event Name: LiveKernelEventOS Version: 6.1.7600.2.0.0.256.1Locale ID: 1037Files that help describe the problemWD-20091108-0907.dmpsysdata.xmlWERInternalMetadata.xml View a temporary copy of these filesWarning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.Extra information about the problemBCCode: 117BCP1: FFFFFA8003C1A160BCP2: FFFFF880048EF220BCP3: 0000000000000000BCP4: 0000000000000000OS Version: 6_1_7600Service Pack: 0_0Product: 256_1BlueScreenView v1.15Copyright © 2009 Nir SoferWeb site: http://www.nirsoft.netהדרייברים לכרטיס מסך מעודכנים!E84004GIGA GSKILL260GTX
פורסם 2009 בנובמבר 1616 שנים dxgkrnl.sysבעייה של DirectX שיצא לך לה תיקון לפני שלושה ימים. מתי עשית Windows Update לאחרונה?ndis.sysבעייה של כרטיס רשת. תראה אם יש עדכון לדרייבר שלו וכמובן להציץ בWU כמו שהולץ מקודם.Files that help describe the problemWD-20091108-0907.dmpנוצר לך קובץ dump גם פה.
פורסם 2009 בנובמבר 1616 שנים תודה על העזרה!!! הקראשים גם כללו:ntoskrnl.exedxgmms1.sysnvlddmkm.sysובקשר לקראש של הכרטיס מסך, הקובץ DUMP הזה לא קיים.
ארכיון
דיון זה הועבר לארכיון ולא ניתן להוסיף בו תגובות חדשות.