[Rozwiązany] - System się zawiesza, występują BSOD-y, resetowanie

Zaloguj się Zarejestruj się

Całe forum

Przeszukaj

Całe forum

Użytkownicy

Wątek zamknięty

Tryb drzewa \| Tryb normalny [Rozwiązany] System się zawiesza, występują BSOD-y, resetowanie
tutusik Wdrażany Liczba postów: 15	Post: #1 System się zawiesza, występują BSOD-y, resetowanie Witam, Od 2 tyg mam problem z moim kompem. Zawiesza się, parę razy było blue screen, teraz od 3-4 dni nie było blue screen ale zawiesza się i resetuje się samo ;/ Dane komputera : Kod: Nazwa systemu operacyjnego Microsoft Windows 7 Professional Wersja 6.1.7601 Service Pack 1 Kompilacja 7601 Dodatkowy opis systemu operacyjnego Niedostępne Producent systemu operacyjnego Microsoft Corporation Nazwa systemu TUTKOWSKI-PC Producent systemu To Be Filled By O.E.M. Model systemu To Be Filled By O.E.M. Typ systemu x64-based PC Procesor AMD Athlon™ II X2 250 Processor, 3000 MHz, Rdzenie: 2, Procesory logiczne: 2 Wersja/data systemu BIOS American Megatrends Inc. P1.40, 2011-02-18 Wersja SMBIOS 2.6 Katalog systemu Windows C: \Windows Katalog systemowy C: \Windows\system32 Urządzenie rozruchowe \Device\HarddiskVolume2 Ustawienia regionalne Polska Warstwa abstrakcji sprzętu Wersja = "6.1.7601.17514" Nazwa użytkownika tutkowski-PC\tutkowski Strefa czasowa Środkowoeuropejski czas letni Zainstalowana pamięć fizyczna (RAM) 4,00 GB Całkowita pamięć fizyczna 3,75 GB Dostępna pamięć fizyczna 1,85 GB Całkowity rozmiar pamięci wirtualnej 7,50 GB Dostępna pamięć wirtualna 5,30 GB Obszar pliku stronicowania 3,75 GB Plik stronicowania C: \pagefile.sys Blue screen: 21.06.2012 18:23
Podziękowania od:

thermalfake Ostatni Mohikanin Liczba postów: 13.580	Post: #2 RE: Zawieszka + restart + blue screen Napiszę to kolejny raz do bólu - podrzuć do analizy pliki *.dmp z folderu c:\windows\minidump To co możesz zrobić na już - przeczyścić sprzęt z kurzu, przesmarować procesor, gpu, zrobić "poprawę montażu" podzespołów - sprawdzić w biosie poprawność pracy procesora i pamieci ram czyli podawane napięcia i timingi ram - pomierzyć napięcia zasilacza miernikiem pod obciążeniem - wykonać testy obciążeniowe furmark, orthos na kilka godzin monitorując temperatury dowolnym programem - puścić długo czasowy test pamięci memtest86 - wykonać diagnostykę dysku: odczyt smart i test powierzchni - hd tune a jak nie odczyta smart'a to crystal disk info Cytat:UNEXPECTED_KERNEL_MODE_TRAP - Błędy sprzętowe lub programowe jądra systemu (awaria sprzętu, problemy z oprogramowaniem lub problemy z uzyskaniem przerwania) Najczęstszą przyczyną tego błędu jest awaria sprzętu. Jest wielce prawdopodobne, że ujrzysz ten komunikat o błędzie Stop, jeżeli masz wadliwe kości pamięci, niedopasowane moduły pamięci, wadliwie działający procesor albo awarię wentylatora lub zasilania, która powoduje przegrzanie. Pojawienie się tego błędu jest szczególnie prawdopodobne w wypadku systemów, w których procesor został przestawiony na pracę z szybkością przekraczającą szybkość nominalną - czyli po overclockingu. Rozwiązanie: -Przywróć ustawienia Biosu. -Wykonaj gruntowne testy całego sprzętu. -Uaktualnij wszystkie sterowniki. -Przywróć rejestr. Źródło: h-o-t-f-i-x.pl W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu. Jak mądrze zadawać pytania? - przejrzyj poradnik na forum. Nie udzielam porad via PW. (Ten post był ostatnio modyfikowany: 21.06.2012 20:31 przez thermalfake.) 21.06.2012 20:26
Podziękowania od:

tutusik Wdrażany Liczba postów: 15	Post: #3 RE: Zawieszka + restart + blue screen http://www.speedyshare.com/5nxMq/Minidump.rar - pliki z minidump a sprzęt mam na gwarancji jeszcze więc jest tam plomba, wolę nie rozbierać. a sprawdzić w biosie itp nie wiem jak :< jestem zieloniutki w te rzeczy ;( 21.06.2012 20:38
Podziękowania od:

thermalfake Ostatni Mohikanin Liczba postów: 13.580	Post: #4 RE: Zawieszka + restart + blue screen No to robisz tylko to co nie wymaga otwierania obudowy. Jeśli nie był czyszczony od nowości i tym bardziej jeśli stoi na podłodze to czas najwyższy zanieść do serwisu - po gwarancji może być już za późno. Ostatni Kod: Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C: \Users\user\Desktop\bsody\dmp21\061512-20092-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: symsrvsymsrv.dllc: \symbhttp: //msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030 Machine Name: Kernel base = 0xfffff800`02e13000 PsLoadedModuleList = 0xfffff800`03057670 Debug session time: Fri Jun 15 19: 55: 43.961 2012 (UTC + 2: 00) System Uptime: 0 days 6: 58: 11.016 Loading Kernel Symbols ...............................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2 WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Unable to add module at 00000000`00000000 Loading User Symbols Loading unloaded module list ..Missing image name, possible paged-out or corrupt data. ..Missing image name, possible paged-out or corrupt data. ..Missing image name, possible paged-out or corrupt data. ...........Missing image name, possible paged-out or corrupt data. ..Missing image name, possible paged-out or corrupt data. . ***************************************************************************** * * * Bugcheck Analysis * * * ***************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 80050031, 6f8, fffff80002eccaf7} Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 ) Followup: MachineOwner --------- 0: kd> !analyze -v ***************************************************************************** * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a portion of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000006f8 Arg4: fffff80002eccaf7 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: d EXCEPTION_RECORD: fffff80000b9c798 -- (.exr 0xfffff80000b9c798) ExceptionAddress: fffff80002e9bbd4 (nt!KeUpdateSystemTime+0x0000000000000274) ExceptionCode: 10000001 ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000000 TRAP_FRAME: fffff80000b9c840 -- (.trap 0xfffff80000b9c840) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002e9bbd4 rsp=fffff80000b9c9d0 rbp=fffff78000000320 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=fffff80000b9ca20 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!KeUpdateSystemTime+0x274: fffff800`02e9bbd4 ff150e451200 call qword ptr [<Unloaded_Unknown_Module_00000000`00000000>+0x12450e (00000000`0012450e)] ds: cad0: fffff800`02fc00e8=00000000005add76 Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002e91769 to fffff80002e921c0 STACK_TEXT: fffff800`00ba4d28 fffff800`02e91769 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx fffff800`00ba4d30 fffff800`02e8fc32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff800`00ba4e70 fffff800`02eccaf7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 fffff800`00934040 fffff800`02e91842 : fffff800`00b9c798 00000000`00000000 fffff800`00b9c840 fffff800`03004e80 : nt!KiDispatchException+0xab fffff800`00b9c660 fffff800`02e9014a : fffffa80`0548d000 fffff880`075c8d35 00000007`00000050 00000000`00000000 : nt!KiExceptionDispatch+0xc2 fffff800`00b9c840 fffff800`02e9bbd4 : fffffa80`00000000 fffff800`03004e80 00000000`00002711 fffff880`00040024 : nt!KiGeneralProtectionFault+0x10a fffff800`00b9c9d0 fffff800`03405895 : fffff800`0342b460 fffff800`00b9cb80 fffff800`0342b460 00000000`00000000 : nt!KeUpdateSystemTime+0x274 fffff800`00b9cad0 fffff800`02e8e713 : 00000000`00000000 fffff800`00040004 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d fffff800`00b9cb00 fffff880`02cd87f2 : fffff800`02e9ace9 00000000`ffffffed fffffa80`04d45468 fffff800`03012cc0 : nt!KiInterruptDispatchNoLock+0x163 fffff800`00b9cc98 fffff800`02e9ace9 : 00000000`ffffffed fffffa80`04d45468 fffff800`03012cc0 00000000`00000001 : 0xfffff880`02cd87f2 fffff800`00b9cca0 fffff800`02e89e9c : fffff800`03004e80 fffff800`00000000 00000000`00000000 fffff880`014fba00 : nt!PoIdle+0x52a fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x2c STACK_COMMAND: kb FOLLOWUP_IP: nt!KiDoubleFaultAbort+b2 fffff800`02e8fc32 90 nop SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiDoubleFaultAbort+b2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4fa390f3 FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 Followup: MachineOwner --------- Tu już jest prościej - jak pisałem dysk twardy do solidnego sprawdzenia ERROR_CODE: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR DISK_HARDWARE_ERROR: There was error with disk hardware Kod: Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C: \Users\user\Desktop\bsody\dmp21\041712-19250-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: symsrvsymsrv.dllc: \symbhttp: //msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505 Machine Name: Kernel base = 0xfffff800`02e06000 PsLoadedModuleList = 0xfffff800`0304a650 Debug session time: Tue Apr 17 13: 20: 21.352 2012 (UTC + 2: 00) System Uptime: 0 days 4: 00: 07.710 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ........ ****************************************************************************** * * * Bugcheck Analysis * * * ***************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck 7A, {fffff6fc50036158, ffffffffc000009c, b52e2820, fffff8a006c2bf66} Probably caused by : ntkrnlmp.exe ( nt! ? : FNODOBFM: `string'+3716a ) Followup: MachineOwner --------- 0: kd> !analyze -v ***************************************************************************** * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_DATA_INPAGE_ERROR (7a) The requested page of kernel data could not be read in. Typically caused by a bad block in the paging file or disk controller error. Also see KERNEL_STACK_INPAGE_ERROR. If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185, it means the disk subsystem has experienced a failure. If the error status is 0xC000009A, then it means the request failed because a filesystem failed to make forward progress. Arguments: Arg1: fffff6fc50036158, lock type that was held (value 1,2,3, or PTE address) Arg2: ffffffffc000009c, error status (normally i/o status code) Arg3: 00000000b52e2820, current process (virtual address for lock type 3, or PTE) Arg4: fffff8a006c2bf66, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address) Debugging Details: ------------------ ERROR_CODE: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR DISK_HARDWARE_ERROR: There was error with disk hardware BUGCHECK_STR: 0x7a_c000009c CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: rundll32.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88002be8730 -- (.trap 0xfffff88002be8730) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000120 rbx=0000000000000000 rcx=fffff8a000876010 rdx=fffff8a006c2bf64 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80003121a7a rsp=fffff88002be88c0 rbp=fffff88002be8ca0 r8=0000000000000000 r9=00000000000ed920 r10=0000000000000005 r11=fffff88002be8910 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!CmpQueryKeyDataFromNode+0xa: fffff800`03121a7a f6420220 test byte ptr [rdx+2],20h ds: 0003: fffff8a0`06c2bf66=20 Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ef2f12 to fffff80002e82c80 STACK_TEXT: fffff880`02be8418 fffff800`02ef2f12 : 00000000`0000007a fffff6fc`50036158 ffffffff`c000009c 00000000`b52e2820 : nt!KeBugCheckEx fffff880`02be8420 fffff800`02ea9b0f : fffffa80`041bee90 fffff880`02be8590 fffff800`030b7600 fffffa80`041bee90 : nt! ? : FNODOBFM: `string'+0x3716a fffff880`02be8500 fffff800`02e902a9 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff780`00000320 : nt!MiIssueHardFault+0x28b fffff880`02be85d0 fffff800`02e80dae : 00000000`00000000 fffff8a0`06c2bf66 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x1399 fffff880`02be8730 fffff800`03121a7a : 00000000`00000000 fffff880`02be8a70 fffff8a0`05e0fd64 fffff8a0`00876010 : nt!KiPageFault+0x16e fffff880`02be88c0 fffff800`03137fb9 : 00000000`00000000 fffff880`02be8ca0 fffff8a0`04e47cc0 00000000`00e31f60 : nt!CmpQueryKeyDataFromNode+0xa fffff880`02be8940 fffff800`03138333 : fffff880`00e31f60 fffff880`02be8a00 fffffa80`00000000 fffff800`00000000 : nt!CmEnumerateKey+0x219 fffff880`02be8a70 fffff800`02e81f13 : fffffa80`03e2f7b0 00000000`00000855 00000000`00000000 00000000`000ed920 : nt!NtEnumerateKey+0x261 fffff880`02be8bb0 00000000`7732163a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`000ed8c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7732163a STACK_COMMAND: kb FOLLOWUP_IP: nt! ? : FNODOBFM: `string'+3716a fffff800`02ef2f12 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ? : FNODOBFM: `string'+3716a FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4f558b55 FAILURE_BUCKET_ID: X64_0x7a_c000009c_nt!_??_: FNODOBFM: _string_+3716a BUCKET_ID: X64_0x7a_c000009c_nt!_??_: FNODOBFM: _string_+3716a Followup: MachineOwner --------- Tego nie jestem dokładniej odczytać ale co mogę powiedzieć - zaktualizuj sterowniki chipsetu najlepiej w trybie awaryjnym - nie zainstalują się te same - odłącz urzadzenia z portów usb - wyłącz/odinstaluj wszelkie oprogramowanie antywirusowe Kod: Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C: \Users\user\Desktop\bsody\dmp21\041312-15693-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: symsrvsymsrv.dllc: \symbhttp: //msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505 Machine Name: Kernel base = 0xfffff800`02e1a000 PsLoadedModuleList = 0xfffff800`0305e650 Debug session time: Fri Apr 13 16: 27: 11.271 2012 (UTC + 2: 00) System Uptime: 0 days 0: 20: 30.629 Loading Kernel Symbols ............................................................... ................................................................ .................... Loading User Symbols Loading unloaded module list ..... ****************************************************************************** * * * Bugcheck Analysis * * * ***************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck FE, {8, 6, 6, fffffa8004c57b20} ********************************************************************* * * * * * 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: usbport!_DEVICE_EXTENSION * * * ********************************************************************* ********************************************************************* * * * * * 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: usbhub!_DEVICE_EXTENSION_HUB * * * ********************************************************************* ********************************************************************* * * * * * 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: usbhub!_DEVICE_EXTENSION_HUB * * * ********************************************************************* ********************************************************************* * * * * * 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: usbhub!_DEVICE_EXTENSION_HUB * * * ********************************************************************* Probably caused by : usbhub.sys ( usbhub!UsbhWaitEventWithTimeoutEx+3aa ) Followup: MachineOwner --------- 0: kd> !analyze -v ***************************************************************************** * * * Bugcheck Analysis * * * ***************************************************************************** BUGCODE_USB_DRIVER (fe) USB Driver bugcheck, first parameter is USB bugcheck code. Arguments: Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT Arg3: 0000000000000006, TimeoutCode: Timeout_PCE_Disable_Action - PortData->PortChangeListDone - Timeout trying to set Disable bit Arg4: fffffa8004c57b20, TimeoutContext - PortData Debugging Details: ------------------ ********************************************************************* * * * * * 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: usbport!_DEVICE_EXTENSION * * * ********************************************************************* ********************************************************************* * * * * * 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: usbhub!_DEVICE_EXTENSION_HUB * * * ********************************************************************* ********************************************************************* * * * * * 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: usbhub!_DEVICE_EXTENSION_HUB * * * ********************************************************************* ********************************************************************* * * * * * 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: usbhub!_DEVICE_EXTENSION_HUB * * * *********************************************************************** CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xFE PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff88006cd47fa to fffff80002e96c80 STACK_TEXT: fffff880`089fa868 fffff880`06cd47fa : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000006 : nt!KeBugCheckEx fffff880`089fa870 fffff880`06cdf5c1 : fffffa80`04c57b20 fffffa80`04c57cf8 fffffa80`04c57b20 fffffa80`04e73050 : usbhub!UsbhWaitEventWithTimeoutEx+0x3aa fffff880`089fa920 fffff880`06cdebdc : 00000000`00000000 fffffa80`50447100 fffffa80`04c57b20 00000000`00080000 : usbhub!Usbh_PCE_Disable_Action+0x4f1 fffff880`089fa980 fffff880`06ce3ff0 : fffffa80`04e73050 00000000`00000002 00000000`00000002 fffffa80`04e73708 : usbhub!UsbhDispatch_PortChangeQueueEventEx+0x110 fffff880`089fa9c0 fffff880`06cdc744 : fffffa80`04e73050 fffffa80`04c57b20 fffffa80`04c57b20 00000000`00000000 : usbhub!UsbhPCE_Disable+0xb4 fffff880`089faa10 fffff880`06cdba3c : 00000000`00000007 00000000`00000003 fffffa80`04e73050 fffffa80`04e73708 : usbhub!UsbhBusPause_Action+0x184 fffff880`089faa60 fffff880`06cdbeb6 : fffffa80`04e731a0 00000000`00000007 fffffa80`04e73050 00000000`00000000 : usbhub!Usbh_BS_BusRun+0x94 fffff880`089faaa0 fffff880`06cdc92b : 00000000`00000003 fffffa80`04e73708 fffffa80`04e73050 00000000`00000000 : usbhub!UsbhDispatch_BusEvent+0x20e fffff880`089faaf0 fffff880`06cf143e : fffffa80`046a11b8 fffffa80`06736e60 fffffa80`06736e60 fffffa80`046a11b8 : usbhub!UsbhSyncBusPause+0x4f fffff880`089fab30 fffff880`06cefb4e : fffffa80`04e73050 fffffa80`04e73708 fffffa80`04e73708 00000000`00000004 : usbhub!UsbhFdoSetPowerDx_Action+0x9a fffff880`089fab90 fffff880`06cee77f : fffffa80`046a11b8 fffffa80`04e731a0 fffffa80`04e73050 fffffa80`046a1010 : usbhub!UsbhFdoDevicePowerState+0x206 fffff880`089fabe0 fffff880`06ceda3b : fffffa80`046a1010 00000000`00000000 fffffa80`04e73050 fffff880`089fad40 : usbhub!UsbhFdoPower_SetPower+0x93 fffff880`089fac20 fffff880`06cd4fdf : 00000000`00000001 fffffa80`04e73050 fffff880`089fad40 fffffa80`04cda010 : usbhub!UsbhFdoPower+0xaf fffff880`089fac60 fffff800`02fac585 : 00000000`00000000 00000000`00000002 00000000`00000001 fffffa80`046a10b8 : usbhub!UsbhGenDispatch+0x7f fffff880`089fac90 fffff800`03130fda : ffffffff`fa0a1f00 fffffa80`04322b60 00000000`00000080 fffff880`019390d9 : nt!PopIrpWorker+0x3c5 fffff880`089fad40 fffff800`02e879c6 : fffff880`009ea180 fffffa80`04322b60 fffffa80`06669760 00000000`0014a000 : nt!PspSystemThreadStartup+0x5a fffff880`089fad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: usbhub!UsbhWaitEventWithTimeoutEx+3aa fffff880`06cd47fa cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: usbhub!UsbhWaitEventWithTimeoutEx+3aa FOLLOWUP_NAME: MachineOwner MODULE_NAME: usbhub IMAGE_NAME: usbhub.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c15 FAILURE_BUCKET_ID: X64_0xFE_usbhub!UsbhWaitEventWithTimeoutEx+3aa BUCKET_ID: X64_0xFE_usbhub!UsbhWaitEventWithTimeoutEx+3aa Followup: MachineOwner --------- W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu. Jak mądrze zadawać pytania? - przejrzyj poradnik na forum. Nie udzielam porad via PW. (Ten post był ostatnio modyfikowany: 21.06.2012 21:04 przez thermalfake.) 21.06.2012 20:43
Podziękowania od:	tutusik

Wątek zamknięty

Podobne wątki
Wątek:	Autor	Odpowiedzi:	Wyświetleń:	Ostatni post
BSOD	Moloch4	0	831	05.07.2019 11:29 Ostatni post: Moloch4
BSOD Windows 7	luzbluzoner	0	1.329	17.12.2016 20:25 Ostatni post: luzbluzoner
Częsty ekrad BSOD	kubajed	0	1.288	03.10.2016 17:46 Ostatni post: kubajed
System zawiesza się przy zamykaniu	Delwin	25	6.489	29.01.2016 00:46 Ostatni post: Illidan
Usuwanie opcji startu systemu: napraw system, przywróć system, uruchom normalnie	metronomus	1	2.481	01.01.2016 16:15 Ostatni post: thermalfake
Nowa instalacja, 3 BSOD	avocado	0	1.343	20.11.2015 09:46 Ostatni post: avocado

« Starszy wątek | Nowszy wątek »

Autor: tutusik
Temat został oceniony na 0 w skali 1-5 gwiazdek.
Zebrano 1 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