agent_smith Δημοσ. 12 Οκτωβρίου 2009 Δημοσ. 12 Οκτωβρίου 2009 Γεια χαρά. Έχω ένα περίεργο πρόβλημα με το wireless receiver του Logitech mx revolution mouse. Κάθε φορά που κάνω boot με το receiver έχω Blue Screen με μήνυμα Internal_Power_Error. Σε όποια θύρα το συνδέσω και ας έχω αφαιρέσει όλα τα usb περιφερικά ακόμα και στο usb hub με εξωτερική τροφοδοσία. Αν αφήσω το Pc να bootare χωρίς το receiver ανοίγει κανονικά και έπειτα αν το συνδέσω σε usb θύρα δουλεύει κανονικά. Καμία ιδέα;
Moderators Gi0 Δημοσ. 12 Οκτωβρίου 2009 Moderators Δημοσ. 12 Οκτωβρίου 2009 Απο τα debugging tools Bug Check 0xA0: INTERNAL_POWER_ERRORdd {margin-bottom:0em; margin-left:1.9em; }.divclass {behavior:url(#default#savehistory);}The INTERNAL_POWER_ERROR bug check has a value of 0x000000A0. This bug check indicates that the power policy manager experienced a fatal error. Θα ξεκινησουμε με ενα update των drivers οπως αναφερεται κ πανω και μετα το ψαχνεις παραπερα.Εμπειρικα παντως οι drivers της logitech ειναι ο κυριος υποπτος.
agent_smith Δημοσ. 12 Οκτωβρίου 2009 Μέλος Δημοσ. 12 Οκτωβρίου 2009 τα εκανα ολα update mouse-keyboard αλλα δεν...
Moderators Gi0 Δημοσ. 12 Οκτωβρίου 2009 Moderators Δημοσ. 12 Οκτωβρίου 2009 τα εκανα ολα update mouse-keyboard αλλα δεν... Κανε τον κοπο να ανεβασεις τα dumps καπου για να τα δω.Καντα ενα rar πριν τα ανεβασεις. Τι windows εχεις?Αν δεν εχει vista/7 ενεργοποιησε τα full kernel dump,για να παρεις περισσοτερες πληροφοριες στο επομενο bsod.
agent_smith Δημοσ. 12 Οκτωβρίου 2009 Μέλος Δημοσ. 12 Οκτωβρίου 2009 Κανε τον κοπο να ανεβασεις τα dumps καπου για να τα δω.Καντα ενα rar πριν τα ανεβασεις.Τι windows εχεις?Αν δεν εχει vista/7 ενεργοποιησε τα full kernel dump,για να παρεις περισσοτερες πληροφοριες στο επομενο bsod. οκ θα το κοιταξω και εγω αν δε βρω ακρη θα στα ανεβασω. ευχαριστω
agent_smith Δημοσ. 13 Οκτωβρίου 2009 Μέλος Δημοσ. 13 Οκτωβρίου 2009 Σου δινω το dump γιατι δεν εβγαλα ακρη... Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Smith\Desktop\Mini101309-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff800`03c16000 PsLoadedModuleList = 0xfffff800`03ddadd0 Debug session time: Tue Oct 13 10:01:54.705 2009 (GMT+3) System Uptime: 0 days 0:00:18.501 ********************************************************************* * 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 A0, {101, 7, fffffa6001be6b20, 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 *** *** *** ************************************************************************* ********************************************************************* * 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+ * ********************************************************************* ********************************************************************* * 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+ * ********************************************************************* Probably caused by : ntoskrnl.exe ( nt+5a450 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* INTERNAL_POWER_ERROR (a0) The power policy manager experienced a fatal error. Arguments: Arg1: 0000000000000101, Unhandled exception occured while processing a system power event. Arg2: 0000000000000007 Arg3: fffffa6001be6b20, ExceptionPointer. To debug this, in the debugger type: 'dt nt!_EXCEPTION_POINTERS <argument>'. Then type: '.cxr <value of context record from the previous command>'. All subsequent debugger commands will show you the actual source of the error. Start with a stack trace by typing 'kb'. Arg4: 0000000000000000 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 *** *** *** ************************************************************************* ********************************************************************* * 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+ * ********************************************************************* ********************************************************************* * 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+ * ********************************************************************* 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: nt FAULTING_MODULE: fffff80003c16000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 49e0237f BUGCHECK_STR: 0xA0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80003cff05a to fffff80003c70450 STACK_TEXT: fffffa60`01be6a78 fffff800`03cff05a : 00000000`000000a0 00000000`00000101 00000000`00000007 fffffa60`01be6b20 : nt+0x5a450 fffffa60`01be6a80 00000000`000000a0 : 00000000`00000101 00000000`00000007 fffffa60`01be6b20 00000000`00000000 : nt+0xe905a fffffa60`01be6a88 00000000`00000101 : 00000000`00000007 fffffa60`01be6b20 00000000`00000000 fffff980`01980328 : 0xa0 fffffa60`01be6a90 00000000`00000007 : fffffa60`01be6b20 00000000`00000000 fffff980`01980328 fffff800`03d61bb4 : 0x101 fffffa60`01be6a98 fffffa60`01be6b20 : 00000000`00000000 fffff980`01980328 fffff800`03d61bb4 fffff800`03cbbe2f : 0x7 fffffa60`01be6aa0 00000000`00000000 : fffff980`01980328 fffff800`03d61bb4 fffff800`03cbbe2f fffff980`01980460 : 0xfffffa60`01be6b20 STACK_COMMAND: kb FOLLOWUP_IP: nt+5a450 fffff800`03c70450 48894c2408 mov qword ptr [rsp+8],rcx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt+5a450 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ntoskrnl.exe BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- 0: kd> lmvm nt start end module name fffff800`03c16000 fffff800`0412e000 nt T (no symbols) Loaded symbol image file: ntoskrnl.exe Image path: \SystemRoot\system32\ntoskrnl.exe Image name: ntoskrnl.exe Timestamp: Sat Apr 11 07:58:39 2009 (49E0237F) CheckSum: 00487B94 ImageSize: 00518000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 0: kd> lmvm nt start end module name fffff800`03c16000 fffff800`0412e000 nt T (no symbols) Loaded symbol image file: ntoskrnl.exe Image path: \SystemRoot\system32\ntoskrnl.exe Image name: ntoskrnl.exe Timestamp: Sat Apr 11 07:58:39 2009 (49E0237F) CheckSum: 00487B94 ImageSize: 00518000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Moderators Gi0 Δημοσ. 13 Οκτωβρίου 2009 Moderators Δημοσ. 13 Οκτωβρίου 2009 Λογικο να μην μπορεις να βγαλεις ακρη μια και δεν εχεις τα σωστα symbols στον debugger.
Προτεινόμενες αναρτήσεις
Αρχειοθετημένο
Αυτό το θέμα έχει αρχειοθετηθεί και είναι κλειστό για περαιτέρω απαντήσεις.