BlueScreen Raport z WinDbg co robić?

Zaloguj się Zarejestruj się

Całe forum

Przeszukaj

Całe forum

Użytkownicy

Odpowiedz

Tryb drzewa \| Tryb normalny BlueScreen Raport z WinDbg co robić?
kotletowygrajek Wdrażany Liczba postów: 10	Post: #1 BlueScreen Raport z WinDbg co robić? Kod: Mam częsty problem z BlueScreen -em oto raport co robić? Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C: \Windows\Minidump\010610-20467-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 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03088e50 Debug session time: Wed Jan 6 12: 02: 49.240 2010 (UTC + 1: 00) System Uptime: 0 days 2: 02: 51.676 ******************************************************************* * 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 D1, {28, b, 1, fffff880064f3a2e} Unable to load image \SystemRoot\system32\drivers\ha10kx2k.sys, Win32 error 0n2 * WARNING: Unable to verify timestamp for ha10kx2k.sys * ERROR: Module load completed but symbols could not be loaded for ha10kx2k.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 : ha10kx2k.sys ( ha10kx2k+9ba2e ) Followup: MachineOwner --------- 3: 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: 0000000000000028, memory referenced Arg2: 000000000000000b, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff880064f3a2e, 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. FAULTING_MODULE: fffff80002e4b000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 47e21dbe WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd 0000000000000028 CURRENT_IRQL: 0 FAULTING_IP: ha10kx2k+9ba2e fffff880`064f3a2e 83672800 and dword ptr [rdi+28h],0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 LAST_CONTROL_TRANSFER: from fffff80002ebc469 to fffff80002ebcf00 STACK_TEXT: fffff880`02ffb5f8 fffff800`02ebc469 : 00000000`0000000a 00000000`00000028 00000000`0000000b 00000000`00000001 : nt+0x71f00 fffff880`02ffb600 00000000`0000000a : 00000000`00000028 00000000`0000000b 00000000`00000001 fffff880`064f3a2e : nt+0x71469 fffff880`02ffb608 00000000`00000028 : 00000000`0000000b 00000000`00000001 fffff880`064f3a2e fffffa80`04a52050 : 0xa fffff880`02ffb610 00000000`0000000b : 00000000`00000001 fffff880`064f3a2e fffffa80`04a52050 00000000`0000ffc0 : 0x28 fffff880`02ffb618 00000000`00000001 : fffff880`064f3a2e fffffa80`04a52050 00000000`0000ffc0 00000000`0000ffc0 : 0xb fffff880`02ffb620 fffff880`064f3a2e : fffffa80`04a52050 00000000`0000ffc0 00000000`0000ffc0 00000000`00000000 : 0x1 fffff880`02ffb628 fffffa80`04a52050 : 00000000`0000ffc0 00000000`0000ffc0 00000000`00000000 00000000`00000000 : ha10kx2k+0x9ba2e fffff880`02ffb630 00000000`0000ffc0 : 00000000`0000ffc0 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`04a52050 fffff880`02ffb638 00000000`0000ffc0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffc0 fffff880`02ffb640 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffc0 STACK_COMMAND: kb FOLLOWUP_IP: ha10kx2k+9ba2e fffff880`064f3a2e 83672800 and dword ptr [rdi+28h],0 SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: ha10kx2k+9ba2e FOLLOWUP_NAME: MachineOwner MODULE_NAME: ha10kx2k IMAGE_NAME: ha10kx2k.sys BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner Notatka została dodana nie znane. Ostatnia edycja dokonana 08.03.2010 20:44 przez** FiFU: Kilometrowa wypowiedź, niepoprawny tytuł. Duże partie tekstu umieszczamy na wklej.org, bądź w znaczniki [code]. 05.03.2010 15:30
Podziękowania od:

Odpowiedz

Podobne wątki
Wątek:	Autor	Odpowiedzi:	Wyświetleń:	Ostatni post
W koszu Błąd BCCode:3b i bluescreen	mazo88	1	443	03.03.2016 18:01 Ostatni post: thermalfake
W koszu Bluescreen 0x00000124 Win7 64bit po formacie	Xylos	1	478	27.01.2016 02:06 Ostatni post: thermalfake
W koszu Bluescreen 0x0000004a	lokikoki14	0	573	18.01.2016 13:58 Ostatni post: lokikoki14
W koszu Bluescreen	Bluescreeny	1	756	01.01.2016 02:32 Ostatni post: thermalfake
W koszu Format Win 7 bluescreen	koxig	2	594	29.11.2015 20:06 Ostatni post: thermalfake
W koszu BAD_SYSTEM_CONFIG_INFO 0x00000074 Bluescreen podczas uruchamiania Win7.	koxig	0	414	02.10.2015 19:09 Ostatni post: koxig

« Starszy wątek | Nowszy wątek »

Autor: kotletowygrajek
Temat został oceniony na 0 w skali 1-5 gwiazdek.
Zebrano 0 głosów.

Regulamin for | Polityka Prywatności | Oznacz wszystkie działy jako przeczytane | Ekipa forum | Statystyki | Wersja mobilna | Użytkownicy | Wersja Lo-Fi | Mapa strony |

Copyright © Windows 7 Forum