selmanns
Centipat
- Katılım
- 18 Eylül 2021
- Mesajlar
- 11
Daha fazla
- Cinsiyet
- Erkek
Microsoft (R) Windows Debugger Version 10.0.22415.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\091821-12765-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`7b200000 PsLoadedModuleList = 0xfffff800`7be2a230
Debug session time: Sat Sep 18 01:46:20.815 2021 (UTC + 3:00)
System Uptime: 0 days 15:11:24.641
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
................................
For analysis of this file, run !analyze -v
storport!StorpAllocateHostMemoryBuffer+0x2fe:
fffff800`7f899ece 48892f mov qword ptr [rdi],rbp ds:002b:00000000`00000000=????????????????
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8007f899ece, The address that the exception occurred at
Arg3: ffff8a0fa0ff6dc8, Exception Record Address
Arg4: ffff8a0fa0ff6600, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullPtr
Key : AV.Fault
Value: Write
Key : Analysis.CPU.mSec
Value: 3468
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 40233
Key : Analysis.Init.CPU.mSec
Value: 468
Key : Analysis.Init.Elapsed.mSec
Value: 75584
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8007f899ece
BUGCHECK_P3: ffff8a0fa0ff6dc8
BUGCHECK_P4: ffff8a0fa0ff6600
EXCEPTION_RECORD: ffff8a0fa0ff6dc8 -- (.exr 0xffff8a0fa0ff6dc8)
ExceptionAddress: fffff8007f899ece (storport!StorpAllocateHostMemoryBuffer+0x00000000000002fe)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000
CONTEXT: ffff8a0fa0ff6600 -- (.cxr 0xffff8a0fa0ff6600)
rax=0000000463000000 rbx=ffffd2821a9d1950 rcx=0000000000000002
rdx=0000000001460000 rsi=ffff8a0fa0ff72a0 rdi=0000000000000000
rip=fffff8007f899ece rsp=ffff8a0fa0ff7000 rbp=ffffd2821a9d1b10
r8=0000000000000ac0 r9=ffffd2821a9d1b50 r10=ffffd28204607fc0
r11=ffff8a0fa0ff6f70 r12=ffffd282120b48d0 r13=0000000003ff0000
r14=0000000001460000 r15=0000000000000002
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
storport!StorpAllocateHostMemoryBuffer+0x2fe:
fffff800`7f899ece 48892f mov qword ptr [rdi],rbp ds:002b:00000000`00000000=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
WRITE_ADDRESS: fffff8007befa390: 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
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000000
EXCEPTION_STR: 0xc0000005
LOCK_ADDRESS: fffff8007be44a60 -- (!locks fffff8007be44a60)
Cannot get _ERESOURCE type
Resource @ nt!PiEngineLock (0xfffff8007be44a60) Available
1 total locks
PNP_TRIAGE_DATA:
Lock address : 0xfffff8007be44a60
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0
STACK_TEXT:
ffff8a0f`a0ff7000 fffff800`7f86f1e0 : 00000000`00000000 00000000`00337000 00000000`0c800000 ffff8a0f`a0ff72a0 : storport!StorpAllocateHostMemoryBuffer+0x2fe
ffff8a0f`a0ff70e0 fffff800`7f83d7de : 00000000`c1000002 ffffd282`1752f020 00000000`00337000 00000000`0c800000 : storport!StorPortExtendedFunction+0x13e0
ffff8a0f`a0ff71b0 fffff800`7f83caa6 : 0000007f`51face52 ffff8a0f`a0ff73c0 00000000`00000001 ffff8a0f`a0ff73c0 : stornvme!NVMeInitHostMemoryBuffer+0x116
ffff8a0f`a0ff7360 fffff800`7f8399e6 : ffffd282`1752f020 ffffd282`1752f020 00000000`00000000 fffff800`7f84e578 : stornvme!NVMeControllerInitPart2+0x1b6
ffff8a0f`a0ff73e0 fffff800`7f88f270 : ffffd282`00000000 ffffd282`11a031a0 00000000`00000000 00000000`00000040 : stornvme!NVMeHwPassiveInitialize+0x66
ffff8a0f`a0ff7420 fffff800`7f88eb5f : 00000000`00000002 00000000`00000040 ffffd282`11a031a0 ffffd282`11a031a0 : storport!RaidAdapterStartMiniport+0x1bc
ffff8a0f`a0ff7480 fffff800`7f88f086 : fffff800`7b21e150 00000000`00000000 00000000`00000000 00000000`00000000 : storport!RaidAdapterStartDevice+0x193
ffff8a0f`a0ff7520 fffff800`7f8871a7 : ffffd282`160ad8a0 00000000`00000000 ffffd282`11a031a0 00000000`00000000 : storport!RaidAdapterStartDeviceIrp+0x11a
ffff8a0f`a0ff7550 fffff800`7f8683af : 00000000`00000010 00000000`00000000 ffffd282`160ad8a0 ffffd282`1a467c00 : storport!RaidAdapterPnpIrp+0x11883
ffff8a0f`a0ff75f0 fffff800`7b48f865 : ffffd282`160ad8a0 ffff8a0f`a0ff7750 ffffd282`11a03050 00000000`69706e04 : storport!RaDriverPnpIrp+0x8f
ffff8a0f`a0ff7630 fffff800`7b9566fe : ffffd282`106e90a0 ffffd282`1a467c00 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55
ffff8a0f`a0ff7670 fffff800`7b4717fe : ffffd282`106e90a0 00000000`00000000 ffffd282`1a467c00 fffff800`7b925e5b : nt!PnpAsynchronousCall+0xea
ffff8a0f`a0ff76b0 fffff800`7b56bae0 : 00000000`00000000 ffffd282`106e90a0 fffff800`7b56b190 fffff800`7b56b190 : nt!PnpSendIrp+0x9e
ffff8a0f`a0ff7720 fffff800`7b92be58 : ffffd282`040188a0 00000000`00000000 ffffd282`1a467c00 00000000`00000000 : nt!PnpStartDevice+0x88
ffff8a0f`a0ff77b0 fffff800`7b92c1bf : ffffd282`040188a0 00000000`00000000 00000000`00000000 fffff800`7b56b632 : nt!PnpStartDeviceNode+0xec
ffff8a0f`a0ff7840 fffff800`7b926b69 : ffffd282`040188a0 ffff8a0f`a0ff7911 00000000`00000000 00000000`00000001 : nt!PipProcessStartPhase1+0x73
ffff8a0f`a0ff7890 fffff800`7b937678 : ffffd282`16f9fd00 fffff800`7b407b01 ffff8a0f`a0ff79b0 fffff800`00000002 : nt!PipProcessDevNodeTree+0x319
ffff8a0f`a0ff7960 fffff800`7b56dfe6 : 00000001`00000003 ffffd281`fbac8ca0 ffffd282`16f9fdf0 ffffd282`16f9fdf0 : nt!PiProcessReenumeration+0x88
ffff8a0f`a0ff79b0 fffff800`7b4b8515 : ffffd282`1a014040 ffffd281`f60e8c50 fffff800`7be433a0 00000000`00000000 : nt!PnpDeviceActionWorker+0x206
ffff8a0f`a0ff7a70 fffff800`7b555855 : ffffd282`1a014040 00000000`00000080 ffffd281`f60df140 00000000`00000000 : nt!ExpWorkerThread+0x105
ffff8a0f`a0ff7b10 fffff800`7b5fe818 : ffffbd01`2a188180 ffffd282`1a014040 fffff800`7b555800 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8a0f`a0ff7b60 00000000`00000000 : ffff8a0f`a0ff8000 ffff8a0f`a0ff1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: stornvme!NVMeInitHostMemoryBuffer+116
MODULE_NAME: stornvme
IMAGE_NAME: stornvme.sys
IMAGE_VERSION: 10.0.19041.1165
STACK_COMMAND: .cxr 0xffff8a0fa0ff6600 ; kb
BUCKET_ID_FUNC_OFFSET: 116
FAILURE_BUCKET_ID: AV_stornvme!NVMeInitHostMemoryBuffer
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9c2f831b-7f7d-973f-3544-4f5fec43c170}
Followup: MachineOwner
---------
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\091821-12765-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`7b200000 PsLoadedModuleList = 0xfffff800`7be2a230
Debug session time: Sat Sep 18 01:46:20.815 2021 (UTC + 3:00)
System Uptime: 0 days 15:11:24.641
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
................................
For analysis of this file, run !analyze -v
storport!StorpAllocateHostMemoryBuffer+0x2fe:
fffff800`7f899ece 48892f mov qword ptr [rdi],rbp ds:002b:00000000`00000000=????????????????
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8007f899ece, The address that the exception occurred at
Arg3: ffff8a0fa0ff6dc8, Exception Record Address
Arg4: ffff8a0fa0ff6600, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullPtr
Key : AV.Fault
Value: Write
Key : Analysis.CPU.mSec
Value: 3468
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 40233
Key : Analysis.Init.CPU.mSec
Value: 468
Key : Analysis.Init.Elapsed.mSec
Value: 75584
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8007f899ece
BUGCHECK_P3: ffff8a0fa0ff6dc8
BUGCHECK_P4: ffff8a0fa0ff6600
EXCEPTION_RECORD: ffff8a0fa0ff6dc8 -- (.exr 0xffff8a0fa0ff6dc8)
ExceptionAddress: fffff8007f899ece (storport!StorpAllocateHostMemoryBuffer+0x00000000000002fe)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000
CONTEXT: ffff8a0fa0ff6600 -- (.cxr 0xffff8a0fa0ff6600)
rax=0000000463000000 rbx=ffffd2821a9d1950 rcx=0000000000000002
rdx=0000000001460000 rsi=ffff8a0fa0ff72a0 rdi=0000000000000000
rip=fffff8007f899ece rsp=ffff8a0fa0ff7000 rbp=ffffd2821a9d1b10
r8=0000000000000ac0 r9=ffffd2821a9d1b50 r10=ffffd28204607fc0
r11=ffff8a0fa0ff6f70 r12=ffffd282120b48d0 r13=0000000003ff0000
r14=0000000001460000 r15=0000000000000002
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
storport!StorpAllocateHostMemoryBuffer+0x2fe:
fffff800`7f899ece 48892f mov qword ptr [rdi],rbp ds:002b:00000000`00000000=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
WRITE_ADDRESS: fffff8007befa390: 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
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000000
EXCEPTION_STR: 0xc0000005
LOCK_ADDRESS: fffff8007be44a60 -- (!locks fffff8007be44a60)
Cannot get _ERESOURCE type
Resource @ nt!PiEngineLock (0xfffff8007be44a60) Available
1 total locks
PNP_TRIAGE_DATA:
Lock address : 0xfffff8007be44a60
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0
STACK_TEXT:
ffff8a0f`a0ff7000 fffff800`7f86f1e0 : 00000000`00000000 00000000`00337000 00000000`0c800000 ffff8a0f`a0ff72a0 : storport!StorpAllocateHostMemoryBuffer+0x2fe
ffff8a0f`a0ff70e0 fffff800`7f83d7de : 00000000`c1000002 ffffd282`1752f020 00000000`00337000 00000000`0c800000 : storport!StorPortExtendedFunction+0x13e0
ffff8a0f`a0ff71b0 fffff800`7f83caa6 : 0000007f`51face52 ffff8a0f`a0ff73c0 00000000`00000001 ffff8a0f`a0ff73c0 : stornvme!NVMeInitHostMemoryBuffer+0x116
ffff8a0f`a0ff7360 fffff800`7f8399e6 : ffffd282`1752f020 ffffd282`1752f020 00000000`00000000 fffff800`7f84e578 : stornvme!NVMeControllerInitPart2+0x1b6
ffff8a0f`a0ff73e0 fffff800`7f88f270 : ffffd282`00000000 ffffd282`11a031a0 00000000`00000000 00000000`00000040 : stornvme!NVMeHwPassiveInitialize+0x66
ffff8a0f`a0ff7420 fffff800`7f88eb5f : 00000000`00000002 00000000`00000040 ffffd282`11a031a0 ffffd282`11a031a0 : storport!RaidAdapterStartMiniport+0x1bc
ffff8a0f`a0ff7480 fffff800`7f88f086 : fffff800`7b21e150 00000000`00000000 00000000`00000000 00000000`00000000 : storport!RaidAdapterStartDevice+0x193
ffff8a0f`a0ff7520 fffff800`7f8871a7 : ffffd282`160ad8a0 00000000`00000000 ffffd282`11a031a0 00000000`00000000 : storport!RaidAdapterStartDeviceIrp+0x11a
ffff8a0f`a0ff7550 fffff800`7f8683af : 00000000`00000010 00000000`00000000 ffffd282`160ad8a0 ffffd282`1a467c00 : storport!RaidAdapterPnpIrp+0x11883
ffff8a0f`a0ff75f0 fffff800`7b48f865 : ffffd282`160ad8a0 ffff8a0f`a0ff7750 ffffd282`11a03050 00000000`69706e04 : storport!RaDriverPnpIrp+0x8f
ffff8a0f`a0ff7630 fffff800`7b9566fe : ffffd282`106e90a0 ffffd282`1a467c00 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55
ffff8a0f`a0ff7670 fffff800`7b4717fe : ffffd282`106e90a0 00000000`00000000 ffffd282`1a467c00 fffff800`7b925e5b : nt!PnpAsynchronousCall+0xea
ffff8a0f`a0ff76b0 fffff800`7b56bae0 : 00000000`00000000 ffffd282`106e90a0 fffff800`7b56b190 fffff800`7b56b190 : nt!PnpSendIrp+0x9e
ffff8a0f`a0ff7720 fffff800`7b92be58 : ffffd282`040188a0 00000000`00000000 ffffd282`1a467c00 00000000`00000000 : nt!PnpStartDevice+0x88
ffff8a0f`a0ff77b0 fffff800`7b92c1bf : ffffd282`040188a0 00000000`00000000 00000000`00000000 fffff800`7b56b632 : nt!PnpStartDeviceNode+0xec
ffff8a0f`a0ff7840 fffff800`7b926b69 : ffffd282`040188a0 ffff8a0f`a0ff7911 00000000`00000000 00000000`00000001 : nt!PipProcessStartPhase1+0x73
ffff8a0f`a0ff7890 fffff800`7b937678 : ffffd282`16f9fd00 fffff800`7b407b01 ffff8a0f`a0ff79b0 fffff800`00000002 : nt!PipProcessDevNodeTree+0x319
ffff8a0f`a0ff7960 fffff800`7b56dfe6 : 00000001`00000003 ffffd281`fbac8ca0 ffffd282`16f9fdf0 ffffd282`16f9fdf0 : nt!PiProcessReenumeration+0x88
ffff8a0f`a0ff79b0 fffff800`7b4b8515 : ffffd282`1a014040 ffffd281`f60e8c50 fffff800`7be433a0 00000000`00000000 : nt!PnpDeviceActionWorker+0x206
ffff8a0f`a0ff7a70 fffff800`7b555855 : ffffd282`1a014040 00000000`00000080 ffffd281`f60df140 00000000`00000000 : nt!ExpWorkerThread+0x105
ffff8a0f`a0ff7b10 fffff800`7b5fe818 : ffffbd01`2a188180 ffffd282`1a014040 fffff800`7b555800 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8a0f`a0ff7b60 00000000`00000000 : ffff8a0f`a0ff8000 ffff8a0f`a0ff1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: stornvme!NVMeInitHostMemoryBuffer+116
MODULE_NAME: stornvme
IMAGE_NAME: stornvme.sys
IMAGE_VERSION: 10.0.19041.1165
STACK_COMMAND: .cxr 0xffff8a0fa0ff6600 ; kb
BUCKET_ID_FUNC_OFFSET: 116
FAILURE_BUCKET_ID: AV_stornvme!NVMeInitHostMemoryBuffer
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9c2f831b-7f7d-973f-3544-4f5fec43c170}
Followup: MachineOwner
---------
Son düzenleyen: Moderatör:
