Bluescreen reset

[Ajjjc]

Witam
Byłabym wdzięczna za pomoc , pojawia się Bluescreen.
Sciągnęłam program WinDbg - Microsoft Debugging Tools wrzuciłam do niego te pliki MINIDUMP
Odczytałam , poszukałam w necie kodów błędów i znalazłam co nie co, bo wychodzi ze to bug check 0xD1, ale przyznam że kompletnie się na tym nie znam , więc abym głupoty jakiejś nie zrobiła , proszę WAS o pomoc.



Poniżej ważniejsze rzeczy:


BugCheck D1, {8c43c490, 2, 8, 8c43c490}
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+2d490 )

A po analizie:

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: 83402000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4d11d0b7

READ_ADDRESS: 8c43c490

CURRENT_IRQL: 0

FAULTING_IP:
dtsoftbus01+2d490
8c43c490 ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 8c43c490 to 8344ff99

FAILED_INSTRUCTION_ADDRESS:
dtsoftbus01+2d490
8c43c490 ?? ???

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8059dd14 8c43c490 badb0d00 902bf2e8 85b4d528 nt+0x4df99
8059dd9c 877aa7f2 9024e0e8 902cf450 9024e030 dtsoftbus01+0x2d490
8059ddb0 877aa850 9024e0e8 902cf468 00000000 CLASSPNP+0x47f2
8059ddc8 877aac11 9024e0e8 902932bc 83536ce0 CLASSPNP+0x4850
8059dde8 8343704d 9024e030 00000000 8059de34 CLASSPNP+0x4c11
8059de08 834ac26b 83536cc0 02536c64 1c3a86a6 nt+0x3504d
8059df28 834abea1 8059df70 8059df02 8059df78 nt+0xaa26b
8059df88 834ac595 00000000 00000000 001fbc22 nt+0xa9ea1
8059dff4 834aa235 8818faa8 00000000 00000000 nt+0xaa595
8059dff8 8818faa8 00000000 00000000 00000000 nt+0xa8235
834aa235 00000000 00000000 00000000 00000000 0x8818faa8


STACK_COMMAND: kb

FOLLOWUP_IP:
dtsoftbus01+2d490
8c43c490 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: dtsoftbus01+2d490

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dtsoftbus01

IMAGE_NAME: dtsoftbus01.sys

BUCKET_ID: WRONG_SYMBOLS

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

[djkamil09061991]

Problemem jest sterownik programu deamon tools, tak więc odinstaluj go i sprawdz czy bedzie lepiej.

[Ajjjc]

Odinstalowany, zaraz sprawdzę czy pomogło, bo przeważnie działo się to po podłączeniu BitCometa



a wiec, po usunięciu DT zrobiłam restart , oczyściłam i podłączyłam Bita, dzieje sie to samo, ale chyba juz chodzi o cos innego , bo kody inne, ale proszę sprawdzić, bo ja się nie znam tym.

prosze to całosc:


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini122812-02.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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x82e4a000 PsLoadedModuleList = 0x82f61c70
Debug session time: Fri Dec 28 13:47:04.112 2012 (GMT+1)
System Uptime: 0 days 0:16:00.005
*********************************************************************
* 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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 77, {1, 0, 0, a299d8c0}

***** 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 : ntkrnlpa.exe ( nt+cdabf )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: 00000001, (page was retrieved from disk)
Arg2: 00000000, value found in stack where signature should be
Arg3: 00000000, 0
Arg4: a299d8c0, address of signature on kernel stack

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: 82e4a000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5037809b

ERROR_CODE: (NTSTATUS) 0x1 - STATUS_WAIT_1

BUGCHECK_STR: 0x77_1

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 82ec0c38 to 82f17abf

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
88193cb4 82ec0c38 00000077 00000001 00000000 nt+0xcdabf
88193d38 82e7e4e8 917c0ac0 88193d58 00000000 nt+0x76c38
88193d6c 82e7f2dc 917c0b30 00000000 88193dc0 nt+0x344e8
88193d7c 8301ffe6 00000000 bc9e4e4b 00000000 nt+0x352dc
88193dc0 82e88f0e 82e7f259 00000000 00000000 nt+0x1d5fe6
00000000 00000000 00000000 00000000 00000000 nt+0x3ef0e


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+cdabf
82f17abf 8be5 mov esp,ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+cdabf

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlpa.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

[djkamil09061991]

Przeinstaluj jeszcze sterownik do karty sieciowej, jeśli nie wiesz na jaki to podaj nazwę płyty głównej z programu cpu-z zakładka mainboard.

[Ajjjc]

Dostępne tylko dla zarejestrowanych użytkowników
Powyzej płyta


Dodam tylko , ze przejrzałam wszystkie MINIDUMP i wnioskuje ze są 3 rózne błedy

[seba86mu]

Na screenie nic nie widać.

[Ajjjc]

Na screenie nic nie widać.

zerknij teraz

[djkamil09061991]

Nie mowiłas ze to laptop podaj dokładny model, powinno byc napisane od spodu.

[Ajjjc]

:) Acer Aspire 5710
Vista

[djkamil09061991]

Zainstaluj dla pewności chipset:
Dostępne tylko dla zarejestrowanych użytkowników

następnie siec:
Dostępne tylko dla zarejestrowanych użytkowników

[Ajjjc]

Zainstaluj dla pewności chipset:
Dostępne tylko dla zarejestrowanych użytkowników

następnie siec:
Dostępne tylko dla zarejestrowanych użytkowników

Ok , działam juz:) a rozpoznałes juz jakos ten problem?

[djkamil09061991]

Ok , działam juz:) a rozpoznałes juz jakos ten problem?

Przyczyn moze byc wiele, krąg sie zawęza bo mowisz iz problem występuje przy włączaniu programu którym pobierasz, tak więc na poczatek stery do sieciówki tak jak podałem wyżej, jeśli to nic nie da to problemem może być zapora, antywirus lub sam program.

[Ajjjc]

chipset juz mam, ale podpowiedz jak z z lan'em sobie poradzic, bo sie pogubilam

[djkamil09061991]

No tak bo z tego co widze sterownik ten nie ma instalatora a wiec wypakuj go gdzies, wejdz w menedzer urządzen rozwin plusik przy karty sieciowe, następnie daj aktualizuj sterownik i wskaż folder ze sterownikiem który wczesniej wypakowałas.

[Ajjjc]

odmawia mi aktualizacji
tak to wyglada


Dostępne tylko dla zarejestrowanych użytkowników