-
👋 Witaj na MPCForum!
Przeglądasz forum jako gość, co oznacza, że wiele świetnych funkcji jest jeszcze przed Tobą! 😎
- ✅ Pełny dostęp do działów i ukrytych treści
- ✅ Możliwość pisania i odpowiadania w tematach
- ✅ System prywatnych wiadomości
- ✅ Zbieranie reputacji i rozwijanie swojego profilu
- ✅ Członkostwo w jednej z największych społeczności graczy
👉 Dołączenie zajmie Ci mniej niż minutę – a zyskasz znacznie więcej!
Zarejestruj się teraz
- 0
Pytanie
RychonKamikaze
RychonKamikaze
Witam, mam pewien problem z blue screenem. Niżej załączam treść DMP
Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini070415-03.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 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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Jul 4 18:54:14.203 2015 (GMT+2)
System Uptime: 0 days 0:23:30.930
*********************************************************************
* 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 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
...............
Unable to load image nvgts.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvgts.sys
*** ERROR: Module load completed but symbols could not be loaded for nvgts.sys
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c000001d, b7ef2d60, b84d3b94, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for SCSIPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SCSIPORT.SYS
*************************************************************************
*** ***
*** ***
*** 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 : hardware ( nvgts+dd60 )
Followup: MachineOwner
---------
1: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: b7ef2d60, The address that the exception occurred at
Arg3: b84d3b94, Trap Frame
Arg4: 00000000
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 ***
*** ***
*************************************************************************
*********************************************************************
* 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.
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {WYJ
FAULTING_IP:
nvgts+dd60
b7ef2d60 ff ???
TRAP_FRAME: b84d3b94 -- (.trap 0xffffffffb84d3b94)
ErrCode = 00000000
eax=00000000 ebx=8a57eb00 ecx=00000000 edx=b86a8440 esi=8a579004 edi=8a579004
eip=b7ef2d60 esp=b84d3c08 ebp=b84d3c28 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nvgts+0xdd60:
b7ef2d60 ff ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
MISALIGNED_IP:
nvgts+dd60
b7ef2d60 ff ???
LAST_CONTROL_TRANSFER: from b7efd6f1 to b7ef2d60
FAILED_INSTRUCTION_ADDRESS:
nvgts+dd60
b7ef2d60 ff ???
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b84d3c28 b7efd6f1 8a579004 8a556af0 8a57eb84 nvgts+0xdd60
b84d3c68 b7eef45f 8a579004 b84d3c8c b7ecfdd2 nvgts+0x186f1
b84d3c74 b7ecfdd2 8a579004 8a57eb84 8a57eb80 nvgts+0xa45f
b84d3c8c 8054555c 8a57eb80 8a556a38 804ffbac SCSIPORT+0x2dd2
00000000 00000000 00000000 00000000 00000000 nt+0x6e55c
STACK_COMMAND: kb
FOLLOWUP_IP:
nvgts+dd60
b7ef2d60 ff ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvgts+dd60
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED_nvgts.sys
BUCKET_ID: IP_MISALIGNED_nvgts.sys
Followup: MachineOwner
---------
Męczy mnie to odkąd odebrałem kompa od informatyka, ale żyłem z tym, bo to było średnio 2 razy dziennie. Zaobserwowałem, że prawie zawsze wywala jak oglądam filmik na YouTube w pełnym ekranie. Dzisiaj się zdenerowałem, bo wywaliło aż 4 razy w tym 2 razy w przeciągu 20 minut. Blue Screen pojawia się zwykle niezależnie od sytuacji i w niespodziewanych momentach. Z góry przepraszam jeśli temat utworzyłem w złym dziale. Pozdrawiam i proszę o pomoc
1 odpowiedź na to pytanie
Rekomendowane odpowiedzi
Zarchiwizowany
Ten temat przebywa obecnie w archiwum. Dodawanie nowych odpowiedzi zostało zablokowane.