Odpowiedz

Windows 7 Enterprise (64) zacinanie oraz bluescreen'y o treści: invalid_kernel_handle

 
thermalfake
Ostatni Mohikanin

Liczba postów: 13.580
Post: #8

RE: bluescreen invalid_kernel_handle


Z żadnego przeciążenia ram'u no i to jest zupełnie inny błąd jak ten z fotki. Niemniej tego też nie wolno bagatelizować.

Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [G: \Downloads\030613-76674-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 (4 procs) Free x64
Product:  WinNt, suite:  TerminalServer SingleUserTS
Built by:  7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`03605000 PsLoadedModuleList = 0xfffff800`03849670
Debug session time:  Wed Mar  6 09: 57: 37.596 2013 (UTC + 1: 00)
System Uptime:  0 days 0: 00: 10.126
Loading Kernel Symbols
....................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800457c8f8, 0, 0}

Probably caused by :  hardware

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

0:  kd> !analyze -v;r;kv;lmtn;.bugcheck;!sysinfo cpuinfo;!sysinfo machineid; !sysinfo cpuspeed; !sysinfo smbios
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1:  0000000000000000, Machine Check Exception
Arg2:  fffffa800457c8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3:  0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4:  0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:   0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

PROCESS_NAME:   System

CURRENT_IRQL:   0

STACK_TEXT:  
fffff880`0318e6f0 fffff800`038c6ca9 :  fffffa80`0457c8d0 fffffa80`0303fb50 00000000`00000016 00000000`00000000 :  nt!WheapCreateLiveTriageDump+0x6c
fffff880`0318ec10 fffff800`037a7557 :  fffffa80`0457c8d0 fffff800`038212d8 fffffa80`0303fb50 00000000`00000000 :  nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0318ec40 fffff800`0370e935 :  fffff800`03882ae0 00000000`00000001 fffffa80`0409da90 fffffa80`0303fb50 :  nt!WheapProcessWorkQueueItem+0x57
fffff880`0318ec80 fffff800`0368d641 :  fffff880`010dce00 fffff800`0370e910 fffffa80`0303fb00 fffffa80`0000055a :  nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0318ecb0 fffff800`0391ae5a :  00000000`00000000 fffffa80`0303fb50 00000000`00000080 fffffa80`0277cb30 :  nt!ExpWorkerThread+0x111
fffff880`0318ed40 fffff800`03674d26 :  fffff880`02f64180 fffffa80`0303fb50 fffff880`02f6efc0 00000000`00000000 :  nt!PspSystemThreadStartup+0x5a
fffff880`0318ed80 00000000`00000000 :  fffff880`0318f000 fffff880`03189000 fffff880`0318e260 00000000`00000000 :  nt!KxStartSystemThread+0x16


STACK_COMMAND:   kb

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  hardware

IMAGE_NAME:   hardware

DEBUG_FLR_IMAGE_TIMESTAMP:   0

FAILURE_BUCKET_ID:   X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:   X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

rax=fffffa8004817000 rbx=fffffa800457c8f8 rcx=fffff8800318e730
rdx=fffffa800271a000 rsi=0000000000000000 rdi=fffffa8004817000
rip=fffff80003ab594c rsp=fffff8800318e6f0 rbp=0000000000000001
r8=000000000000f1e0  r9=00000000000007ff r10=000000000000060c
r11=0000000000000000 r12=fffff80003882b40 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000286
nt!WheapCreateLiveTriageDump+0x6c:
fffff800`03ab594c 48897c2438      mov     qword ptr [rsp+38h],rdi ss: 0018: fffff880`0318e728=fffffa8000000910
Child-SP          RetAddr           :  Args to Child                                                           :  Call Site
fffff880`0318e6f0 fffff800`038c6ca9 :  fffffa80`0457c8d0 fffffa80`0303fb50 00000000`00000016 00000000`00000000 :  nt!WheapCreateLiveTriageDump+0x6c
fffff880`0318ec10 fffff800`037a7557 :  fffffa80`0457c8d0 fffff800`038212d8 fffffa80`0303fb50 00000000`00000000 :  nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0318ec40 fffff800`0370e935 :  fffff800`03882ae0 00000000`00000001 fffffa80`0409da90 fffffa80`0303fb50 :  nt!WheapProcessWorkQueueItem+0x57
fffff880`0318ec80 fffff800`0368d641 :  fffff880`010dce00 fffff800`0370e910 fffffa80`0303fb00 fffffa80`0000055a :  nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0318ecb0 fffff800`0391ae5a :  00000000`00000000 fffffa80`0303fb50 00000000`00000080 fffffa80`0277cb30 :  nt!ExpWorkerThread+0x111
fffff880`0318ed40 fffff800`03674d26 :  fffff880`02f64180 fffffa80`0303fb50 fffff880`02f6efc0 00000000`00000000 :  nt!PspSystemThreadStartup+0x5a
fffff880`0318ed80 00000000`00000000 :  fffff880`0318f000 fffff880`03189000 fffff880`0318e260 00000000`00000000 :  nt!KxStartSystemThread+0x16
start             end                 module name
fffff800`00ba0000 fffff800`00baa000   kdcom    kdcom.dll    Sat Feb 05 17: 52: 49 2011 (4D4D8061)
fffff800`03605000 fffff800`03bed000   nt       ntkrnlmp.exe Thu Aug 30 17: 11: 58 2012 (503F82BE)
fffff800`03bed000 fffff800`03c36000   hal      hal.dll      Sat Nov 20 14: 00: 25 2010 (4CE7C669)
fffff880`00c18000 fffff880`00c25000   mcupdate mcupdate.dll Tue Jul 14 03: 29: 09 2009 (4A5BDF65)
fffff880`00c25000 fffff880`00c39000   PSHED    PSHED.dll    Tue Jul 14 03: 32: 23 2009 (4A5BE027)
fffff880`00c39000 fffff880`00c97000   CLFS     CLFS.SYS     Tue Jul 14 01: 19: 57 2009 (4A5BC11D)
fffff880`00c97000 fffff880`00d57000   CI       CI.dll       Sat Nov 20 14: 12: 36 2010 (4CE7C944)
fffff880`00d57000 fffff880`00db3000   volmgrx  volmgrx.sys  Sat Nov 20 10: 20: 43 2010 (4CE792EB)
fffff880`00db3000 fffff880`00def000   vmbus    vmbus.sys    Sat Nov 20 10: 57: 29 2010 (4CE79B89)
fffff880`00e00000 fffff880`00e09000   WMILIB   WMILIB.SYS   Tue Jul 14 01: 19: 51 2009 (4A5BC117)
fffff880`00e09000 fffff880`00e13000   msisadrv msisadrv.sys Tue Jul 14 01: 19: 26 2009 (4A5BC0FE)
fffff880`00e13000 fffff880`00e46000   pci      pci.sys      Sat Nov 20 10: 19: 11 2010 (4CE7928F)
fffff880`00e46000 fffff880`00e53000   vdrvroot vdrvroot.sys Tue Jul 14 02: 01: 31 2009 (4A5BCADB)
fffff880`00e53000 fffff880`00e68000   partmgr  partmgr.sys  Sat Mar 17 06: 06: 09 2012 (4F641BC1)
fffff880`00e68000 fffff880`00e7d000   volmgr   volmgr.sys   Sat Nov 20 10: 19: 28 2010 (4CE792A0)
fffff880`00e7d000 fffff880`00e84000   pciide   pciide.sys   Tue Jul 14 01: 19: 49 2009 (4A5BC115)
fffff880`00e84000 fffff880`00e94000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 01: 19: 48 2009 (4A5BC114)
fffff880`00e94000 fffff880`00eae000   mountmgr mountmgr.sys Sat Nov 20 10: 19: 21 2010 (4CE79299)
fffff880`00eae000 fffff880`00ec2000   winhv    winhv.sys    Sat Nov 20 10: 20: 02 2010 (4CE792C2)
fffff880`00ec2000 fffff880`00ecb000   atapi    atapi.sys    Tue Jul 14 01: 19: 47 2009 (4A5BC113)
fffff880`00ed0000 fffff880`00f92000   Wdf01000 Wdf01000.sys Thu Jul 26 04: 25: 13 2012 (5010AA89)
fffff880`00f92000 fffff880`00fa2000   WDFLDR   WDFLDR.SYS   Thu Jul 26 04: 29: 04 2012 (5010AB70)
fffff880`00fa2000 fffff880`00ff9000   ACPI     ACPI.sys     Sat Nov 20 10: 19: 16 2010 (4CE79294)
fffff880`01077000 fffff880`010a1000   ataport  ataport.SYS  Sat Nov 20 10: 19: 15 2010 (4CE79293)
fffff880`010a1000 fffff880`010ac000   amdxata  amdxata.sys  Fri Mar 19 17: 18: 18 2010 (4BA3A3CA)
fffff880`010ac000 fffff880`010f8000   fltmgr   fltmgr.sys   Sat Nov 20 10: 19: 24 2010 (4CE7929C)
fffff880`010f8000 fffff880`0110c000   fileinfo fileinfo.sys Tue Jul 14 01: 34: 25 2009 (4A5BC481)
fffff880`0110c000 fffff880`011181a0   PxHlpa64 PxHlpa64.sys Mon Oct 17 16: 29: 34 2011 (4E9C3BCE)
fffff880`01119000 fffff880`01177000   msrpc    msrpc.sys    Sat Nov 20 10: 21: 56 2010 (4CE79334)
fffff880`01177000 fffff880`011e9000   cng      cng.sys      Fri Aug 24 17: 47: 16 2012 (5037A204)
fffff880`01201000 fffff880`013a4000   Ntfs     Ntfs.sys     Fri Aug 31 17: 14: 14 2012 (5040D4C6)
fffff880`013a4000 fffff880`013bf000   ksecdd   ksecdd.sys   Sat Jun 02 04: 50: 23 2012 (4FC97F6F)
fffff880`013bf000 fffff880`013d0000   pcw      pcw.sys      Tue Jul 14 01: 19: 27 2009 (4A5BC0FF)
fffff880`013d0000 fffff880`013da000   Fs_Rec   Fs_Rec.sys   Thu Mar 01 04: 41: 06 2012 (4F4EEFD2)
fffff880`01400000 fffff880`0142b000   ksecpkg  ksecpkg.sys  Fri Aug 24 17: 48: 29 2012 (5037A24D)
fffff880`0149d000 fffff880`0158f000   ndis     ndis.sys     Wed Aug 22 17: 11: 46 2012 (5034F6B2)
fffff880`0158f000 fffff880`015ef000   NETIO    NETIO.SYS    Wed Aug 22 17: 11: 28 2012 (5034F6A0)
fffff880`01640000 fffff880`01841000   tcpip    tcpip.sys    Wed Oct 03 17: 09: 34 2012 (506C552E)
fffff880`01841000 fffff880`0188b000   fwpkclnt fwpkclnt.sys Wed Aug 22 17: 10: 49 2012 (5034F679)
fffff880`0188b000 fffff880`0189b000   vmstorfl vmstorfl.sys Sat Nov 20 10: 57: 30 2010 (4CE79B8A)
fffff880`0189b000 fffff880`018e7000   volsnap  volsnap.sys  Sat Nov 20 10: 20: 08 2010 (4CE792C8)
fffff880`018e7000 fffff880`018ef000   spldr    spldr.sys    Mon May 11 18: 56: 27 2009 (4A0858BB)
fffff880`018ef000 fffff880`01929000   rdyboost rdyboost.sys Sat Nov 20 10: 43: 10 2010 (4CE7982E)
fffff880`01929000 fffff880`0193b000   mup      mup.sys      Tue Jul 14 01: 23: 45 2009 (4A5BC201)
fffff880`0193b000 fffff880`01944000   hwpolicy hwpolicy.sys Sat Nov 20 10: 18: 54 2010 (4CE7927E)
fffff880`01944000 fffff880`0197e000   fvevol   fvevol.sys   Sat Nov 20 10: 24: 06 2010 (4CE793B6)
fffff880`0197e000 fffff880`01994000   disk     disk.sys     Tue Jul 14 01: 19: 57 2009 (4A5BC11D)
fffff880`01994000 fffff880`019c4000   CLASSPNP CLASSPNP.SYS Sat Nov 20 10: 19: 23 2010 (4CE7929B)
fffff880`019c4000 fffff880`019c8380   BtHidBus BtHidBus.sys Tue Apr 06 12: 31: 30 2010 (4BBB0D82)
fffff880`019c9000 fffff880`019d7000   crashdmp crashdmp.sys Tue Jul 14 02: 01: 01 2009 (4A5BCABD)
fffff880`019d7000 fffff880`019e3000   dump_ataport dump_ataport.sys Tue Jul 14 01: 19: 47 2009 (4A5BC113)
fffff880`019e3000 fffff880`019ec000   dump_atapi dump_atapi.sys Tue Jul 14 01: 19: 47 2009 (4A5BC113)
fffff880`019ec000 fffff880`019ff000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 01: 21: 51 2009 (4A5BC18F)
Mini Kernel Dump does not contain unloaded driver list
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`0457c8f8 00000000`00000000 00000000`00000000
sysinfo:  could not find necessary interfaces.
sysinfo:  note that mssmbios.sys must be loaded (XPSP2+).
sysinfo:  could not find necessary interfaces.
sysinfo:  note that mssmbios.sys must be loaded (XPSP2+).
sysinfo:  could not find necessary interfaces.
sysinfo:  note that mssmbios.sys must be loaded (XPSP2+).
sysinfo:  could not find necessary interfaces.
sysinfo:  note that mssmbios.sys must be loaded (XPSP2+).

Po dalszej analizie

Kod:
===============================================================================
Common Platform Error Record @ fffffa800457c8f8
-------------------------------------------------------------------------------
Record Id     :  01ce1a48a21dbb2e
Severity      :  Fatal (1)
Length        :  928
Creator       :  Microsoft
Notify Type   :  Machine Check Exception
Timestamp     :  3/6/2013 8: 57: 37
Flags         :  0x00000002 PreviousError

===============================================================================
Section 0     :  Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800457c978
Section       @ fffffa800457ca50
Offset        :  344
Length        :  192
Flags         :  0x00000001 Primary
Severity      :  Fatal

Proc. Type    :  x86/x64
Instr. Set    :  x64
Error Type    :  BUS error
Operation     :  Generic
Flags         :  0x00
Level         :  3
CPU Version   :  0x0000000000100f23
Processor ID  :  0x0000000000000000

===============================================================================
Section 1     :  x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800457c9c0
Section       @ fffffa800457cb10
Offset        :  536
Length        :  128
Flags         :  0x00000000
Severity      :  Fatal

Local APIC Id :  0x0000000000000000
CPU Id        :  23 0f 10 00 00 08 04 00 - 09 20 80 00 ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa800457cb10

===============================================================================
Section 2     :  x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800457ca08
Section       @ fffffa800457cb90
Offset        :  664
Length        :  264
Flags         :  0x00000000
Severity      :  Fatal

Error         :  BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)
  Status      :  0xa200001000010c0f

Stwierdzam, że problem jest identyczny jak tu
http://windows7forum.pl/problem-z-bsod-c...#pid154773

Jeśli chodzi o pierwotny błąd to tu jest opis
http://msdn.microsoft.com/en-us/library/...85%29.aspx
Z niego można się tylko tyle dowiedzieć, że jakaś część kodu jądra kernel próbuje przekazać chroniony lub nieistniejący już wskaźnik (odwołanie do zasobu/obiektu coś w rodzaju powiązania) do funkcji NtClose (zamknięcia/zniszczenia). Ten wskaźnik prawdopodobnie gdzieś jest dalej używany skoro wywala błąd. Bez analizy nic więcej nie poradzę.

[Obrazek: 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.

06.03.2013 22:12

Znajdź wszystkie posty użytkownika
Odpowiedz cytując ten post
Odpowiedz


Wiadomości w tym wątku
RE: bluescreen invalid_kernel_handle - thermalfake - 06.03.2013 22:12
Podobne wątki
Wątek: Autor Odpowiedzi: Wyświetleń: Ostatni post
Lsass.exe oraz svchost.exe 50% zużycia procesora. gadula700 3 2.414 15.09.2016 21:46
Ostatni post: gadula700
Windows 7 x64 Bluescreen przy grach skailer213 1 1.238 04.08.2016 14:46
Ostatni post: thermalfake
Windows 7 64-bit Problem z bluescreen'ami soho90 4 2.061 13.02.2016 12:37
Ostatni post: soho90
Problemy z Aero, Windows Update oraz programem Teamspeak ignaccy 0 1.577 05.02.2016 23:08
Ostatni post: ignaccy
Rozwiązany -Windows 7 64-bit Problem z bluescreen'ami (BSOD) jacob776 6 3.619 04.12.2015 17:45
Ostatni post: jacob776
bluescreen -czego wina ? ftcrev 2 1.778 01.11.2015 11:37
Ostatni post: thermalfake
« Starszy wątek | Nowszy wątek »

Temat został oceniony na 0 w skali 1-5 gwiazdek.
Zebrano 1 głosów.