bloidas

Zrobiłem ten test i wyświetliło się: "no fails detected, push f2 to end" czy coś takiego, więc chyba jest ok. Usunąłem wszystkie myszki - było ich z 15. Do tej pory nie ma problemów, a mam cały dzień włączonego lapka, więc wydaję mi się, że problem zniknął, ale zobaczymy w perpektywie czasu W każdym razie bardzo dziękuję za pomoc

Wydaje mi się, że problem zaczął się pojawiać od czasu kiedy kupiłem nową myszkę do komputera. Nie ważne czy jest podłączona czy nie problem od tego czasu się pojawia. Wersji tych memtestów jest dużo. Który pownienem wybrać?

Jeszcze coś takiego z Framework.NET windbg:

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\032214-19375-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Users\Wojtek\Desktop\Nowy folder (2)*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0xfffff800`03a4e000 PsLoadedModuleList = 0xfffff800`03c8ae70
Debug session time: Sat Mar 22 16:39:43.894 2014 (UTC + 1:00)
System Uptime: 0 days 2:44:46.081
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
..............................
ERROR: FindPlugIns 800700a1
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {8, 6, 5, fffffa8006928b20}

*************************************************************************
*** ***
*** ***
*** 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!UsbhHubProcessChangeWorker+ec )

Followup: MachineOwner
---------

2: kd> !analyze -v
ERROR: FindPlugIns 800700a1
*******************************************************************************
* *
* 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: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent
Arg4: fffffa8006928b20, 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 fffff8800a6609ec to fffff80003abd880

STACK_TEXT:
fffff880`033a8c18 fffff880`0a6609ec : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx
fffff880`033a8c20 fffff800`03db4243 : fffffa80`068a5050 fffffa80`06d83320 ffffffff`dc3a58a0 fffff800`03c625f8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`033a8c80 fffff800`03acab21 : fffff800`03c62500 fffff800`03db4220 fffffa80`03574680 fffffa80`03574680 : nt!IopProcessWorkItem+0x23
fffff880`033a8cb0 fffff800`03d5c47a : 895e148d`4424448b fffffa80`03574680 00000000`00000080 fffffa80`0355b040 : nt!ExpWorkerThread+0x111
fffff880`033a8d40 fffff800`03a9bda6 : fffff880`031d3180 fffffa80`03574680 fffff880`031ddfc0 f8d1c22b`99011044 : nt!PspSystemThreadStartup+0x5a
fffff880`033a8d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`0a6609ec cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: usbhub!UsbhHubProcessChangeWorker+ec

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbhub

IMAGE_NAME: usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0aaa

FAILURE_BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

Followup: MachineOwner

Z przed chwili mam jeszcze to: 

Podpis problemu:
Nazwa zdarzenia problemu: BlueScreen
Wersja systemu operacyjnego: 6.1.7600.2.0.0.768.3
Identyfikator ustawień regionalnych: 1045

Dodatkowe informacje o problemie:
BCCode: fe
BCP1: 0000000000000008
BCP2: 0000000000000006
BCP3: 0000000000000005
BCP4: FFFFFA8006928B20
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Pliki pomagające opisać problem:
C:\Windows\Minidump\032214-19375-01.dmp
C:\Users\Wojtek\AppData\Local\Temp\WER-54803-0.sysdata.xml (gdy owtorzę wyświtla się przeglądarka internetowa i to:

Błąd składni XML

Błąd składni XML: błąd składni (Wiersz: 1, Znak: 0)

Potraktuj dokument jako HTML
Błąd:
missing root element
Specyfikacja:
http://www.w3.org/TR/REC-xml/)

Przeczytaj w trybie online nasze zasady zachowania poufności informacji:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0415

Jeśli zasady zachowania poufności informacji w trybie online nie są dostępne, przeczytaj nasze zasady zachowania poufności informacji w trybie offline:
C:\Windows\system32\pl-PL\erofflps.txt

Załączam zdjecie bluescreena.  Mam nadzieję, że to pomoże.

Witam!

Z góry przepraszam, jeżeli źle wybiorę temat, ale jestem nowy i nie do końca rozumiem komputery "od środka". Od pewnego czasu, ostatnio intensywniej, na ekrania pojawia się czarny ekran, a zaraz potem bluescreen bug code usb driver z tego co pamiętam. Gdy się zrestartuje na tapecie wyświetla się, że system odzyskał sprawność po nieoczekiwanym zamknięciu jednak gdy klikam rozwiąż problem, nic się nie dzieje.Wiem ze muszę wrzucić ten folder minidump, ale gdy już go skompresuję i próbuje tu wrzucić to wyświetla się ze nie mam uprawnień do wysyłania tego typu plików. Z vaio care informacje o systemie jakby się przydały. Jestem w stanie współpracować, zamieścić wszystko, tylko muszę wiedzieć co. Proszę o pomoc w rozwiązaniu problemu!