Plik ntoskrnl.exe powodujący bluescreeny
|
Jarek1993
Nowy
Liczba postów: 3
|
 Plik ntoskrnl.exe powodujący bluescreeny
Witam kupiłem nowy komputer i już pierwszego dnia restartuje mi się komputer. Proszę bardzo o pomoc.
Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Kod:
Loading Dump File [C: \Windows\Minidump\040912-21528-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
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c61000 PsLoadedModuleList = 0xfffff800`02ea5650
Debug session time: Mon Apr 9 21: 34: 28.326 2012 (UTC + 2: 00)
System Uptime: 0 days 7: 12: 05.762
*********************************************************************
* 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
*** 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 3B, {c0000005, fffff80002d0f269, fffff8800899dd60, 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+ae269 )
Followup: MachineOwner
---------
|
 Podziękowania od: |
|
|
|
peciaq
VIP
Liczba postów: 5.100
|
RE: Bluescreen Windows 7 Home promium 64 bit ntoskrnl.exe
Wrzuć pliki z Minidump na serwer hostingowy i daj nam tu linka.
|
| Podziękowania od: |
|
|
|
thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: Bluescreen Windows 7 Home promium 64 bit ntoskrnl.exe
Wstępnie po błędzie 0x0000003B SYSTEM_SERVICE_EXCEPTION może to być:
- błąd działania sterownika lub innego oprogramowania systemowego
- błąd pamięci RAM, pamięci gryzą się z płytą główną
- zła konfiguracja pamięci RAM (timingi, vdimm)
Ogólnie jesteś na dobrej drodze z rozprawieniem się z zrzutami pamięci lecz brakuje ścieżki do symboli stąd WinDbg nie jest w stanie dokładniej przeanalizować i zapisać wyniki w postaci symboli - ten obecny wydruk jest bezwartościowy.
![[Obrazek: 2089620800_1406976151.png]](http://obrazki.elektroda.pl/2089620800_1406976151.png)
W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
|
| Podziękowania od: |
|
|
|
Jarek1993
Nowy
Liczba postów: 3
|
RE: Bluescreen Windows 7 Home promium 64 bit ntoskrnl.exe
http://download.hellshare.pl/minidump-rar/6619230/ proszę, przepraszam że tak długo mi zajęło ale nie wiedziałem jak się wgrywa, musiałem trochę poczytać
|
| Podziękowania od: |
|
|
|
Jarek1993
Nowy
Liczba postów: 3
|
RE: Bluescreen Windows 7 Home promium 64 bit ntoskrnl.exe
sprawdzał może ktoś moje pliki , jest ktoś mi wstanie pomóc?
|
| Podziękowania od: |
|
|
|
thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: Bluescreen Windows 7 Home promium 64 bit ntoskrnl.exe
Sam po kolei testujesz pamięci RAM programem memtest 86 (opis w faq). Można je testować osobno, zmieniać slotami.
Odpal sobie CPU-Z, wejdź do zakładki Memory oraz SPD i porównaj z danym modelem kości czy masz prawidłowo ustawione przez płytę główną timingi/napięcie pamięci vdimm.
Mając nowy sprzęt na gwarancji nie mając o nim zielonego pojęcia poszedłbym po prostu reklamować.
Szersza analiza przykładowego minidumpa (wszystkie wypluwają ten sam błąd).
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\dmp15\040912-18610-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //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 Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c0b000 PsLoadedModuleList = 0xfffff800`02e4f650
Debug session time: Mon Apr 9 10: 19: 37.937 2012 (UTC + 2: 00)
System Uptime: 0 days 0: 12: 03.358
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002cb9269, fffff88008176e50, 0}
Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+551 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002cb9269, Address of the instruction which caused the bugcheck
Arg3: fffff88008176e50, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
nt!MiDeleteVirtualAddresses+551
fffff800`02cb9269 498b4510 mov rax,qword ptr [r13+10h]
CONTEXT: fffff88008176e50 -- (.cxr 0xfffff88008176e50)
rax=fffff80002ebc540 rbx=0000000006bc0049 rcx=0000058000000000
rdx=00000000ffffffff rsi=b8e00001070ff867 rdi=fffff68000035e00
rip=fffff80002cb9269 rsp=fffff88008177830 rbp=0000000006bc0000
r8=0000000fffffffff r9=000000000000938e r10=0000000006bc0000
r11=fffff70001080000 r12=fffffa8003ac4d68 r13=fffff70001080000
r14=0000000000000000 r15=000000000000938e
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210202
nt!MiDeleteVirtualAddresses+0x551:
fffff800`02cb9269 498b4510 mov rax,qword ptr [r13+10h] ds: 002b: fffff700`01080010=???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: firefox.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002cb9269
STACK_TEXT:
fffff880`08177830 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x551
FOLLOWUP_IP:
nt!MiDeleteVirtualAddresses+551
fffff800`02cb9269 498b4510 mov rax,qword ptr [r13+10h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiDeleteVirtualAddresses+551
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2
STACK_COMMAND: .cxr 0xfffff88008176e50 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x3B_nt!MiDeleteVirtualAddresses+551
BUCKET_ID: X64_0x3B_nt!MiDeleteVirtualAddresses+551
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.
|
| Podziękowania od: |
|
|
|
Post: #1
![[Obrazek: havensygn.jpg]](http://img33.imageshack.us/img33/2410/havensygn.jpg)
