Ahoj,
tak můj repasovaný zbook g6 dělá další problémy občas.
Jedná se mi o samovolné restartování - vyhodí se modrá obrazovka a napíše to něco s tím, že je pc nutno restartovat, takže se sám restartue.
Teď se mi to asi stalo po 2 dnech, kdy jsem PC používal a dával jsem jej jen do režimu spánku přes noc - nebyl problém s tím, že by se pc zaseknul v černé obrazovce a musel by se natvrdo vypnout...
Ty dva dny kdy to jelo normálně jsem neměl zaplou školní VPN. Dnes jsem ji zapl a bych si něco nainstaloval a po chvilce modrá obrazovka, myslím že ty problémy se zaseknutím PC v režimu spánku jsou taktéž když mám zaplou školní VPN/ nějaký soft který jede přes školní VPN.
Nedá se toto nějak diagnostikovat co se s čím stalo, když vznikne problém?
dík
Občasné problémy s PC
Re: Občasné problémy s PC
Tu diagnostiku jsi mel udelat pred tim, nez jsi vlozil prispevek do sekce BSOD - chybi vsechny body dle navodu.
HP ZBOOK G6 lze s primhourenim obou oci povazovat za splneni bodu C>
HP ZBOOK G6 lze s primhourenim obou oci povazovat za splneni bodu C>
Re: Občasné problémy s PC
Tak jsem se zase rychleji dotazoval než hledal:
našel jsem složku MiniDump a stáhl WinDbg a vyhodilo mi to text, který je níže. Jste z toho schopni něco rychle detekovat? já ne ale zkusil jsem chatGpt a odpoveď:
KMODE_EXCEPTION_NOT_HANDLED (1e). Tato chyba obvykle znamená, že došlo k neošetřené výjimce v jádru systému Windows. Důležité informace z výpisu jsou:
Kód chyby: 0x1e
Výjimkový kód: 0xc0000005 (přístupová chyba)
Adresa výjimky: 0xfffff804240488f2
Název modulu: acsock64.sys
Chyba byla specifikována jako přístupová chyba (Access Violation), která se obvykle vyskytuje, když program pokusí přistupovat k paměti, ke které nemá oprávnění.
Důležitým vodítkem je název modulu acsock64.sys, což je ovladač sítě pravděpodobně spojený s nějakým bezpečnostním softwarem, jako je antivirus nebo firewall.
Takže možná to je opravdu něco se sítí a VPN a nějakým softem.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff804240488f2, The address that the exception occurred at
Arg3: ffffee0175bdbf08, Parameter 0 of the exception
Arg4: ffffb4819ffb2900, Parameter 1 of the exception
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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: ContextRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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: ContextRecord ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4593
Key : Analysis.Elapsed.mSec
Value: 23713
Key : Analysis.IO.Other.Mb
Value: 18
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 28
Key : Analysis.Init.CPU.mSec
Value: 499
Key : Analysis.Init.Elapsed.mSec
Value: 76305
Key : Analysis.Memory.CommitPeak.Mb
Value: 96
Key : Bugcheck.Code.LegacyAPI
Value: 0x1e
Key : Bugcheck.Code.TargetModel
Value: 0x1e
Key : Dump.Attributes.AsUlong
Value: 1808
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: AV_acsock64!unknown_function
Key : Failure.Hash
Value: {0e906a44-0355-22fb-3f6f-e0fdb167414b}
Key : Hypervisor.Enlightenments.ValueHex
Value: 1417cf94
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 1
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 4853999
Key : Hypervisor.Flags.ValueHex
Value: 4a10ef
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 1
Key : Hypervisor.RootFlags.AccessStats
Value: 1
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 1
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key : Hypervisor.RootFlags.MceEnlightened
Value: 1
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key : Hypervisor.RootFlags.Value
Value: 1015
Key : Hypervisor.RootFlags.ValueHex
Value: 3f7
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff804240488f2
BUGCHECK_P3: ffffee0175bdbf08
BUGCHECK_P4: ffffb4819ffb2900
FILE_IN_CAB: 072124-22265-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump
EXCEPTION_PARAMETER1: ffffee0175bdbf08
EXCEPTION_PARAMETER2: ffffb4819ffb2900
WRITE_ADDRESS: fffff80407f1c4a8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffb4819ffb2900
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: instup.exe
TRAP_FRAME: 8e118a8a767ff6ab -- (.trap 0x8e118a8a767ff6ab)
Unable to read trap frame at 8e118a8a`767ff6ab
STACK_TEXT:
ffffb481`9ffb2038 fffff804`0776a91f : 00000000`0000001e ffffffff`c0000005 fffff804`240488f2 ffffee01`75bdbf08 : nt!KeBugCheckEx
ffffb481`9ffb2040 fffff804`07637b26 : ffffb481`9ffb2900 fffff804`07468ec5 ffffee01`75bdc148 fffff804`240488f2 : nt!KiFatalFilter+0x1f
ffffb481`9ffb2080 fffff804`075d24f1 : ffffb481`00000002 ffffee01`75bdbf08 ffffee01`75bd7000 ffffee01`75bde000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16
ffffb481`9ffb20c0 fffff804`0762148f : ffffee01`75bdbf08 ffffb481`9ffb26c0 ffffee01`75bdbf00 fffff804`074c4aba : nt!_C_specific_handler+0xa1
ffffb481`9ffb2130 fffff804`0755fc73 : ffffee01`75bdd1a0 ffffee01`75bdbf08 fffff804`074c4aba fffff804`072dc91c : nt!RtlpExecuteHandlerForException+0xf
ffffb481`9ffb2160 fffff804`074b0aee : ffffffff`ffffffff ffffee01`75bdbfb0 ffffee01`75bdbfb0 ffffb481`9ffb2900 : nt!RtlDispatchException+0x2f3
ffffb481`9ffb28d0 fffff804`07617012 : d2254242`06cffc03 7ae867da`de7b752f 8e118a8a`767ff6ab b2d90989`72bdfcf3 : nt!KiDispatchException+0x1ae
ffffb481`9ffb2fb0 fffff804`07616fe0 : fffff804`0762be75 00000000`00000002 fffff804`07843c32 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffee01`75bdbdc8 fffff804`0762be75 : 00000000`00000002 fffff804`07843c32 00000000`00000000 ffffddad`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
ffffee01`75bdbdd0 fffff804`07627163 : 00000000`00000000 ffffc585`4c202000 fffff804`07200000 ffffc585`6a4f8510 : nt!KiExceptionDispatch+0x135
ffffee01`75bdbfb0 fffff804`240488f2 : fffff804`24048895 ffffc585`612dfb28 ffffc585`6d0b82d0 00000000`00000001 : nt!KiPageFault+0x463
ffffee01`75bdc148 fffff804`24048895 : ffffc585`612dfb28 ffffc585`6d0b82d0 00000000`00000001 fffff804`24046e53 : acsock64+0x88f2
ffffee01`75bdc150 ffffc585`612dfb28 : ffffc585`6d0b82d0 00000000`00000001 fffff804`24046e53 fffff804`2409d460 : acsock64+0x8895
ffffee01`75bdc158 ffffc585`6d0b82d0 : 00000000`00000001 fffff804`24046e53 fffff804`2409d460 00000000`00000000 : 0xffffc585`612dfb28
ffffee01`75bdc160 00000000`00000001 : fffff804`24046e53 fffff804`2409d460 00000000`00000000 00000000`00000000 : 0xffffc585`6d0b82d0
ffffee01`75bdc168 fffff804`24046e53 : fffff804`2409d460 00000000`00000000 00000000`00000000 fffff804`0cb781f6 : 0x1
ffffee01`75bdc170 fffff804`2409d460 : 00000000`00000000 00000000`00000000 fffff804`0cb781f6 ffffc585`612dfb20 : acsock64+0x6e53
ffffee01`75bdc178 00000000`00000000 : 00000000`00000000 fffff804`0cb781f6 ffffc585`612dfb20 fffff804`240484eb : acsock64+0x5d460
SYMBOL_NAME: acsock64+88f2
MODULE_NAME: acsock64
IMAGE_NAME: acsock64.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 88f2
FAILURE_BUCKET_ID: AV_acsock64!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {0e906a44-0355-22fb-3f6f-e0fdb167414b}
Followup: MachineOwner
---------
našel jsem složku MiniDump a stáhl WinDbg a vyhodilo mi to text, který je níže. Jste z toho schopni něco rychle detekovat? já ne ale zkusil jsem chatGpt a odpoveď:
KMODE_EXCEPTION_NOT_HANDLED (1e). Tato chyba obvykle znamená, že došlo k neošetřené výjimce v jádru systému Windows. Důležité informace z výpisu jsou:
Kód chyby: 0x1e
Výjimkový kód: 0xc0000005 (přístupová chyba)
Adresa výjimky: 0xfffff804240488f2
Název modulu: acsock64.sys
Chyba byla specifikována jako přístupová chyba (Access Violation), která se obvykle vyskytuje, když program pokusí přistupovat k paměti, ke které nemá oprávnění.
Důležitým vodítkem je název modulu acsock64.sys, což je ovladač sítě pravděpodobně spojený s nějakým bezpečnostním softwarem, jako je antivirus nebo firewall.
Takže možná to je opravdu něco se sítí a VPN a nějakým softem.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff804240488f2, The address that the exception occurred at
Arg3: ffffee0175bdbf08, Parameter 0 of the exception
Arg4: ffffb4819ffb2900, Parameter 1 of the exception
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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: ContextRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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: ContextRecord ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4593
Key : Analysis.Elapsed.mSec
Value: 23713
Key : Analysis.IO.Other.Mb
Value: 18
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 28
Key : Analysis.Init.CPU.mSec
Value: 499
Key : Analysis.Init.Elapsed.mSec
Value: 76305
Key : Analysis.Memory.CommitPeak.Mb
Value: 96
Key : Bugcheck.Code.LegacyAPI
Value: 0x1e
Key : Bugcheck.Code.TargetModel
Value: 0x1e
Key : Dump.Attributes.AsUlong
Value: 1808
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: AV_acsock64!unknown_function
Key : Failure.Hash
Value: {0e906a44-0355-22fb-3f6f-e0fdb167414b}
Key : Hypervisor.Enlightenments.ValueHex
Value: 1417cf94
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 1
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 4853999
Key : Hypervisor.Flags.ValueHex
Value: 4a10ef
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 1
Key : Hypervisor.RootFlags.AccessStats
Value: 1
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 1
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key : Hypervisor.RootFlags.MceEnlightened
Value: 1
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key : Hypervisor.RootFlags.Value
Value: 1015
Key : Hypervisor.RootFlags.ValueHex
Value: 3f7
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff804240488f2
BUGCHECK_P3: ffffee0175bdbf08
BUGCHECK_P4: ffffb4819ffb2900
FILE_IN_CAB: 072124-22265-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump
EXCEPTION_PARAMETER1: ffffee0175bdbf08
EXCEPTION_PARAMETER2: ffffb4819ffb2900
WRITE_ADDRESS: fffff80407f1c4a8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffb4819ffb2900
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: instup.exe
TRAP_FRAME: 8e118a8a767ff6ab -- (.trap 0x8e118a8a767ff6ab)
Unable to read trap frame at 8e118a8a`767ff6ab
STACK_TEXT:
ffffb481`9ffb2038 fffff804`0776a91f : 00000000`0000001e ffffffff`c0000005 fffff804`240488f2 ffffee01`75bdbf08 : nt!KeBugCheckEx
ffffb481`9ffb2040 fffff804`07637b26 : ffffb481`9ffb2900 fffff804`07468ec5 ffffee01`75bdc148 fffff804`240488f2 : nt!KiFatalFilter+0x1f
ffffb481`9ffb2080 fffff804`075d24f1 : ffffb481`00000002 ffffee01`75bdbf08 ffffee01`75bd7000 ffffee01`75bde000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16
ffffb481`9ffb20c0 fffff804`0762148f : ffffee01`75bdbf08 ffffb481`9ffb26c0 ffffee01`75bdbf00 fffff804`074c4aba : nt!_C_specific_handler+0xa1
ffffb481`9ffb2130 fffff804`0755fc73 : ffffee01`75bdd1a0 ffffee01`75bdbf08 fffff804`074c4aba fffff804`072dc91c : nt!RtlpExecuteHandlerForException+0xf
ffffb481`9ffb2160 fffff804`074b0aee : ffffffff`ffffffff ffffee01`75bdbfb0 ffffee01`75bdbfb0 ffffb481`9ffb2900 : nt!RtlDispatchException+0x2f3
ffffb481`9ffb28d0 fffff804`07617012 : d2254242`06cffc03 7ae867da`de7b752f 8e118a8a`767ff6ab b2d90989`72bdfcf3 : nt!KiDispatchException+0x1ae
ffffb481`9ffb2fb0 fffff804`07616fe0 : fffff804`0762be75 00000000`00000002 fffff804`07843c32 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffee01`75bdbdc8 fffff804`0762be75 : 00000000`00000002 fffff804`07843c32 00000000`00000000 ffffddad`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
ffffee01`75bdbdd0 fffff804`07627163 : 00000000`00000000 ffffc585`4c202000 fffff804`07200000 ffffc585`6a4f8510 : nt!KiExceptionDispatch+0x135
ffffee01`75bdbfb0 fffff804`240488f2 : fffff804`24048895 ffffc585`612dfb28 ffffc585`6d0b82d0 00000000`00000001 : nt!KiPageFault+0x463
ffffee01`75bdc148 fffff804`24048895 : ffffc585`612dfb28 ffffc585`6d0b82d0 00000000`00000001 fffff804`24046e53 : acsock64+0x88f2
ffffee01`75bdc150 ffffc585`612dfb28 : ffffc585`6d0b82d0 00000000`00000001 fffff804`24046e53 fffff804`2409d460 : acsock64+0x8895
ffffee01`75bdc158 ffffc585`6d0b82d0 : 00000000`00000001 fffff804`24046e53 fffff804`2409d460 00000000`00000000 : 0xffffc585`612dfb28
ffffee01`75bdc160 00000000`00000001 : fffff804`24046e53 fffff804`2409d460 00000000`00000000 00000000`00000000 : 0xffffc585`6d0b82d0
ffffee01`75bdc168 fffff804`24046e53 : fffff804`2409d460 00000000`00000000 00000000`00000000 fffff804`0cb781f6 : 0x1
ffffee01`75bdc170 fffff804`2409d460 : 00000000`00000000 00000000`00000000 fffff804`0cb781f6 ffffc585`612dfb20 : acsock64+0x6e53
ffffee01`75bdc178 00000000`00000000 : 00000000`00000000 fffff804`0cb781f6 ffffc585`612dfb20 fffff804`240484eb : acsock64+0x5d460
SYMBOL_NAME: acsock64+88f2
MODULE_NAME: acsock64
IMAGE_NAME: acsock64.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 88f2
FAILURE_BUCKET_ID: AV_acsock64!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {0e906a44-0355-22fb-3f6f-e0fdb167414b}
Followup: MachineOwner
---------
Re: Občasné problémy s PC
acsock64.sys je ovladac od Cisco Anyconnect VPN.
Nemas nainstalovanou nejakou prastarou verzi VPN klienta ?
Nemas nainstalovanou nejakou prastarou verzi VPN klienta ?
Re: Občasné problémy s PC
Mě se právě zdá že to je ta nejaktuálnější - když se podívám na PC tak mi to ukazuje verzi 5.1.4.74 a na internetu je taktéž tato verze jako aktuální.
Re: Občasné problémy s PC
Dej tam 4.10 nejvyssi build.
U nas nebyla jeste 5.1 uvolnena, bude k tomu nejaky duvod (ani pro W10, an pro W11).
U nas nebyla jeste 5.1 uvolnena, bude k tomu nejaky duvod (ani pro W10, an pro W11).
Re: Občasné problémy s PC
Aha jak vidím tak to lze stáhnout jedině s nějakou objednávkou a když se přihlásím přes školu, tak se dostanu na nějakou stránku kde můžu stáhnout jen ten 5.1.4.74
Re: Občasné problémy s PC
Stahni jakykoliv instalator, co najdes na netu, je to vsechno jedno a to same
Nazev souboru
anyconnect-win-4.10.06090-core-vpn-predeploy-k9.msi
Nazev souboru
anyconnect-win-4.10.06090-core-vpn-predeploy-k9.msi
Re: Občasné problémy s PC
Stáhl jsem nějaký OpenConnect a vypadá že to funguje taky, tak to tak zatím nechám.
Děkuji moc za pomoc vážím si toho
Děkuji moc za pomoc vážím si toho
-
- Mohlo by vás zajímat
- Odpovědi
- Zobrazení
- Poslední příspěvek
-
- 1
- 1970
-
od X
Zobrazit poslední příspěvek
05 lis 2023 03:58
-
- 2
- 3383
-
od petr22
Zobrazit poslední příspěvek
08 led 2024 21:47
-
- 4
- 2251
-
od Bayani
Zobrazit poslední příspěvek
23 úno 2024 07:44
-
- 19
- 6016
-
od petr22
Zobrazit poslední příspěvek
11 kvě 2024 17:24
-
- 6
- 1077
-
od kecalek
Zobrazit poslední příspěvek
12 zář 2024 10:53
Zpět na “BSOD (Blue Screen Of Death)”
Kdo je online
Uživatelé prohlížející si toto fórum: Žádní registrovaní uživatelé a 1 host