Ta przeglądarka nie jest już obsługiwana.
Przejdź na przeglądarkę Microsoft Edge, aby korzystać z najnowszych funkcji, aktualizacji zabezpieczeń i pomocy technicznej.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Podczas normalnego korzystania z komputera dostaję blue screen lub częściowej czarny ekran, który nie znika i trzeba restartować laptopa z przycisku.
minidump nr.1
Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`48000000 PsLoadedModuleList = 0xfffff805`48c2a290
Debug session time: Wed Sep 21 20:28:55.457 2022 (UTC + 2:00)
System Uptime: 0 days 0:00:32.135
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`483f8fa0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9e00`0d3e7160=000000000000001e
10: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff805482d660b, The address that the exception occurred at
Arg3: ffff9e000d3d2340, Parameter 0 of the exception
Arg4: ffff9e000d3c7180, 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: 4999
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 5043
Key : Analysis.Init.CPU.mSec
Value: 1280
Key : Analysis.Init.Elapsed.mSec
Value: 16214
Key : Analysis.Memory.CommitPeak.Mb
Value: 96
Key : Bugcheck.Code.DumpHeader
Value: 0x1e
Key : Bugcheck.Code.KiBugCheckData
Value: 0x1e
Key : Bugcheck.Code.Register
Value: 0x1e
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: MEMORY.DMP
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc000001d
BUGCHECK_P2: fffff805482d660b
BUGCHECK_P3: ffff9e000d3d2340
BUGCHECK_P4: ffff9e000d3c7180
EXCEPTION_PARAMETER1: ffff9e000d3d2340
EXCEPTION_PARAMETER2: ffff9e000d3c7180
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
FAILED_INSTRUCTION_ADDRESS:
nt!KiGetNextTimerExpirationDueTime+2ab
fffff805`482d660b ff ???
STACK_TEXT:
ffff9e00`0d3e7158 fffff805`484f5e5e : 00000000`0000001e ffffffff`c000001d fffff805`482d660b ffff9e00`0d3d2340 : nt!KeBugCheckEx
ffff9e00`0d3e7160 fffff805`48401e92 : fffff805`484f5e3c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
ffff9e00`0d3e71a0 fffff805`48277a77 : ffff9e00`0d3e7710 00000000`00000000 ffffee83`c02a7c60 fffff805`483fcaf4 : nt!RtlpExecuteHandlerForException+0x12
ffff9e00`0d3e71d0 fffff805`48276676 : ffffee83`c02a7288 ffff9e00`0d3e7e20 ffffee83`c02a7288 ffff9e00`0d3c7180 : nt!RtlDispatchException+0x297
ffff9e00`0d3e78f0 fffff805`483f9e32 : 00000000`099080f7 74c985ca`440f1000 00000228`808b4915 e8118b48`f84f8d48 : nt!KiDispatchException+0x186
ffff9e00`0d3e7fb0 fffff805`483f9e00 : fffff805`4840b0a5 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffee83`c02a7148 fffff805`4840b0a5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
ffffee83`c02a7150 fffff805`484055e9 : 524f5453`202d2030 ffffc48d`ecb756b8 ffffc48d`ecaf2c00 fffff805`48346428 : nt!KiExceptionDispatch+0x125
ffffee83`c02a7330 fffff805`482d660b : ffff9e00`0d3c7180 00000000`13277e00 00000000`00000000 ffffee83`c02a7520 : nt!KiInvalidOpcodeFault+0x329
ffffee83`c02a74c0 fffff805`4850ed2d : ffffffff`ffffffff ffffc48d`ecb75600 00000000`13277e00 00000000`00000000 : nt!KiGetNextTimerExpirationDueTime+0x2ab
ffffee83`c02a7520 fffff805`48560b5d : 00000000`00000002 ffff9e00`0d3c7100 fffff805`46589ac0 ffff9e00`0d3c7180 : nt!KeEstimateClockTickDuration+0xbd
ffffee83`c02a7580 fffff805`4849a345 : ffffffff`ffffffff ffff9e00`0d3c7180 00000000`00000000 00000000`00000000 : nt!PpmEstimateIdleDuration+0xd9
ffffee83`c02a76f0 fffff805`482d31b5 : 00000000`00000000 00001f80`00000000 00000000`009bb63e 00000000`00000002 : nt!PpmIdleSelectStates+0x1068b5
ffffee83`c02a7af0 fffff805`483fcaf4 : ffffffff`00000000 ffff9e00`0d3d2340 ffffc48d`fc7170c0 00000000`000008ca : nt!PoIdle+0x405
ffffee83`c02a7c60 00000000`00000000 : ffffee83`c02a8000 ffffee83`c02a2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54
SYMBOL_NAME: nt!KiGetNextTimerExpirationDueTime+2ab
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 2ab
FAILURE_BUCKET_ID: 0x1E_C000001D_BAD_IP_nt!KiGetNextTimerExpirationDueTime
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {3cf0bafd-83ed-8cf5-43a1-56778933476d}
Followup: MachineOwner
---------
minidump nr.2
Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\092122-8015-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`4d000000 PsLoadedModuleList = 0xfffff800`4dc2a290
Debug session time: Wed Sep 21 20:28:04.573 2022 (UTC + 2:00)
System Uptime: 0 days 0:04:36.251
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`4d3f8fa0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9c81`665f5d30=000000000000007f
Loading Dump File [C:\Windows\Minidump\092122-8015-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Can't set dump file contexts
MachineInfo::SetContext failed - Thread: 000002510619D360 Handle: b Id: b - Error == 0x8000FFFF
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`4d000000 PsLoadedModuleList = 0xfffff800`4dc2a290
Debug session time: Wed Sep 21 20:28:04.573 2022 (UTC + 2:00)
System Uptime: 0 days 0:04:36.251
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.........
nt!KeBugCheckEx:
fffff800`4d3f8fa0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9c81`665f5d30=000000000000007f
Loading Dump File [C:\Windows\Minidump\092122-8015-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Can't set dump file contexts
MachineInfo::SetContext failed - Thread: 0000025109399760 Handle: b Id: b - Error == 0x8000FFFF
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`4d000000 PsLoadedModuleList = 0xfffff800`4dc2a290
Debug session time: Wed Sep 21 20:28:04.573 2022 (UTC + 2:00)
System Uptime: 0 days 0:04:36.251
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.........
nt!KeBugCheckEx:
fffff800`4d3f8fa0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9c81`665f5d30=000000000000007f
||2:10: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
BugCheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffff9c81665f5e70
Arg3: 0000001db33fbee8
Arg4: 00007ffe5eb8d8cc
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3983
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 17608
Key : Analysis.Init.CPU.mSec
Value: 968
Key : Analysis.Init.Elapsed.mSec
Value: 18570
Key : Analysis.Memory.CommitPeak.Mb
Value: 156
Key : Bugcheck.Code.DumpHeader
Value: 0x7f
Key : Bugcheck.Code.Register
Value: 0x7f
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 092122-8015-01.dmp
BUGCHECK_CODE: 7f
BUGCHECK_P1: 8
BUGCHECK_P2: ffff9c81665f5e70
BUGCHECK_P3: 1db33fbee8
BUGCHECK_P4: 7ffe5eb8d8cc
TRAP_FRAME: ffff9c81665f5e70 -- (.trap 0xffff9c81665f5e70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000046 rbx=0000000000000000 rcx=00007ffe5eb8d8c4
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=00007ffe5eb8d8cc rsp=0000001db33fbee8 rbp=0000000000000000
r8=0000001dafec4000 r9=0000000000000000 r10=0000001db33fbf20
r11=0000000000000246 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
00007ffe`5eb8d8cc ?? ???
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: FortniteClient-Win64-Shipping.exe
STACK_TEXT:
ffff9c81`665f5d28 fffff800`4d40af69 : 00000000`0000007f 00000000`00000008 ffff9c81`665f5e70 0000001d`b33fbee8 : nt!KeBugCheckEx
ffff9c81`665f5d30 fffff800`4d405d83 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff9c81`665f5e70 00007ffe`5eb8d8cc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x2c3
0000001d`b33fbee8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`5eb8d8cc
SYMBOL_NAME: nt!KiDoubleFaultAbort+2c3
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.2006
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 2c3
FAILURE_BUCKET_ID: 0x7f_8_nt!KiDoubleFaultAbort
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {d1f8395a-8c58-45da-6ebf-e8bb4aad2fc5}
Followup: MachineOwner
---------
minidump nr.3
Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\092122-8375-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`51400000 PsLoadedModuleList = 0xfffff805`5202a290
Debug session time: Wed Sep 21 19:01:48.614 2022 (UTC + 2:00)
System Uptime: 0 days 0:00:38.292
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`517f8fa0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc685`8f3a3020=000000000000001e
10: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff80551633902, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000000, 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 ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4515
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 13973
Key : Analysis.Init.CPU.mSec
Value: 390
Key : Analysis.Init.Elapsed.mSec
Value: 29159
Key : Analysis.Memory.CommitPeak.Mb
Value: 92
Key : Bugcheck.Code.DumpHeader
Value: 0x1e
Key : Bugcheck.Code.Register
Value: 0x1e
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 092122-8375-01.dmp
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80551633902
BUGCHECK_P3: 1
BUGCHECK_P4: 0
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000000
WRITE_ADDRESS: fffff805520fb390: 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
0000000000000000
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: MsMpEng.exe
TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000
STACK_TEXT:
ffffc685`8f3a3018 fffff805`5183cd15 : 00000000`0000001e ffffffff`c0000005 fffff805`51633902 00000000`00000001 : nt!KeBugCheckEx
ffffc685`8f3a3020 fffff805`5180b0ac : 00000000`00001000 ffffc685`8f3a38c0 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x1c6825
ffffc685`8f3a36e0 fffff805`51807243 : 00000000`00000000 ffff848e`ce30ad30 ffffc685`8f3a39f8 00000000`00001368 : nt!KiExceptionDispatch+0x12c
ffffc685`8f3a38c0 fffff805`51633902 : 00000000`00000001 ffff848e`ddd88080 ffff848e`ddd88080 ffff848e`e0a99080 : nt!KiPageFault+0x443
ffffc685`8f3a3a50 00000000`00000001 : ffff848e`ddd88080 ffff848e`ddd88080 ffff848e`e0a99080 ffffde8e`3acfada0 : nt!PsGetCurrentSilo+0x22
ffffc685`8f3a3a58 ffff848e`ddd88080 : ffff848e`ddd88080 ffff848e`e0a99080 ffffde8e`3acfada0 00000000`00001368 : 0x1
ffffc685`8f3a3a60 ffff848e`ddd88080 : ffff848e`e0a99080 ffffde8e`3acfada0 00000000`00001368 00000000`00000000 : 0xffff848e`ddd88080
ffffc685`8f3a3a68 ffff848e`e0a99080 : ffffde8e`3acfada0 00000000`00001368 00000000`00000000 ffffc685`8f3a3ae0 : 0xffff848e`ddd88080
ffffc685`8f3a3a70 ffffde8e`3acfada0 : 00000000`00001368 00000000`00000000 ffffc685`8f3a3ae0 00000000`00000000 : 0xffff848e`e0a99080
ffffc685`8f3a3a78 00000000`00001368 : 00000000`00000000 ffff
Pytanie zablokowane. To pytanie zostało zmigrowane ze społeczności pomocy technicznej firmy Microsoft. Możesz zagłosować, czy pytanie jest pomocne, ale nie możesz dodawać komentarzy ani odpowiedzi, ani też śledzić pytania.
Zauważeyłem, że gdy laptop przełącza się z integrowanej karty graficznej na dedykowaną laptop zaczyna dostawać błędy oraz blue screeny takie jak IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION, 0x0000007F (UNEXPECTED KERNEL MODE TRAP).
Najnowsze sterowniki są zainstalowane. Wszystkie aktualizacje windowsa też.
Przepraszam za późną odpowiedź. Wykonywałem kroki z tego poradnika niestety nie przyniosły poprawy. Około 2 tygodnie temu nie mogłem nawet się zalogować, ponieważ od razu gdy otwierałem komputer wyskakiwał blue screen. Zrobiłem factory reset i zainstalowałem Windowsa 10 od nowa z usunięciem wszystkich danych z bootowalnego pendriva. Po instalacji po około 30 min wyskoczył 1 czarny ekran i od teraz znowu zwiększa sie ich częstotliwość. Najczęściej występują przy uruchomieniu jakiejś gry z minimalnie wyższymi wymaganiami np. 7 days to die, Call of duty warzone. podejrzewałem, że może jest to brak ramu lub jego wadliwość wymieniłem RAM z 8gb na 32gb, ale nic nie pomogło. Blue screeny i czarne ekrany występują również podczas normalnego korzystania z laptopa, nap przeglądanie internetu, word, itp. Cieszył bym się, jeżeli udałoby się to naprawić, ponieważ gdy wysłałem laptopa na gwarancję, napisali, że reinstalacja systemu go naprawiła, lecz od razu po uruchomieniu wyskoczył błąd.
Ta odpowiedź została przetłumaczona automatycznie. W związku z tym mogą występować błędy gramatyczne lub dziwne sformułowania.
Witaj fkrolik
Nie otrzymaliśmy od Ciebie wiadomości od 72 godzin, więc rozważymy rozwiązanie Twojego problemu. Jeśli potrzebujesz dalszej pomocy, utwórz nowy wątek, aby omówić te obawy, ponieważ nie będziemy monitorować tego wątku w przyszłości.
Dziękujemy za zrozumienie.
Pozdrawiam
Jason Guer
Moderator społeczności firmy Microsoft
Ta odpowiedź została przetłumaczona automatycznie. W związku z tym mogą występować błędy gramatyczne lub dziwne sformułowania.
Witaj fkrolik
Dziękujemy za opublikowanie wpisu w witrynie Microsoft Community. Chętnie pomożemy.
Rozumiem, że masz problem w odniesieniu do BSOD, w którym zaobserwowałeś kilka plików minidump na swoim komputerze. Pracujmy razem nad znalezieniem najlepszego rozwiązania tego problemu.
Aby lepiej zrozumieć problem, chciałbym zadać kilka pytań:
Zrobiłem badanie jakiejś poprawki BSOD i znalazłem ten artykuł Microsoft, który moim zdaniem może rozwiązać problem. W każdej szansie, że już wykonałeś kroki, daj mi znać.
Kliknij tutaj: Rozwiązywanie problemów z błędami niebieskiego ekranu (microsoft.com)
Mam nadzieję, że to działa dla Ciebie.
Pozdrawiam
Jason Guer
Moderator społeczności firmy Microsoft
