Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
- Copyright (c) Microsoft Corporation. All rights reserved.
- ========================================================================
- =================== Dump File: 071217-22781-01.dmp ====================
- ========================================================================
- Mini Kernel Dump File: Only registers and stack trace are available
- Windows 10 Kernel Version 14393 MP (4 procs) Free x64
- Product: WinNt, suite: TerminalServer SingleUserTS Personal
- Built by: 14393.1480.amd64fre.rs1_release.170706-2004
- Kernel base = 0xfffff803`09212000 PsLoadedModuleList = 0xfffff803`09511040
- Debug session time: Wed Jul 12 14:46:46.154 2017 (UTC - 4:00)
- System Uptime: 0 days 12:58:15.906
- BugCheck 133, {0, 501, 500, fffff803095b2540}
- *** ERROR: Symbol file could not be found. Defaulted to export symbols for hal.dll -
- *** WARNING: Unable to verify timestamp for rtwlane.sys
- *** ERROR: Module load completed but symbols could not be loaded for rtwlane.sys
- *************************************************************************
- *** ***
- *** ***
- *** 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: TickPeriods ***
- *** ***
- *************************************************************************
- Probably caused by : rtwlane.sys ( rtwlane+306c4 )
- Followup: MachineOwner
- DPC_WATCHDOG_VIOLATION (133)
- The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
- or above.
- Arguments:
- Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
- component can usually be identified with a stack trace.
- Arg2: 0000000000000501, The DPC time count (in ticks).
- Arg3: 0000000000000500, The DPC time allotment (in ticks).
- Arg4: fffff803095b2540
- 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: TickPeriods ***
- *** ***
- *************************************************************************
- DUMP_CLASS: 1
- DUMP_QUALIFIER: 400
- BUILD_VERSION_STRING: 10.0.14393.1480 (rs1_release.170706-2004)
- SYSTEM_MANUFACTURER: HP
- SYSTEM_PRODUCT_NAME: HP Pavilion Notebook
- SYSTEM_SKU: Y5U04EA#A2N
- SYSTEM_VERSION: Type1ProductConfigId
- BIOS_VENDOR: Insyde
- BIOS_VERSION: F.38
- BIOS_DATE: 05/24/2017
- BASEBOARD_MANUFACTURER: HP
- BASEBOARD_PRODUCT: 8216
- BASEBOARD_VERSION: 83.17
- DUMP_TYPE: 2
- DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
- CPU_COUNT: 4
- CPU_MHZ: b58
- CPU_VENDOR: GenuineIntel
- CPU_FAMILY: 6
- CPU_MODEL: 8e
- CPU_STEPPING: 9
- CPU_MICROCODE: 6,8e,9,0 (F,M,S,R) SIG: 5E'00000000 (cache) 5E'00000000 (init)
- CUSTOMER_CRASH_COUNT: 1
- DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
- BUGCHECK_STR: 0x133
- PROCESS_NAME: System
- CURRENT_IRQL: d
- ANALYSIS_SESSION_HOST: USERNAME-PC
- ANALYSIS_SESSION_TIME: 07-14-2017 23:55:37.0793
- ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
- LAST_CONTROL_TRANSFER: from fffff80309234fb7 to fffff80309361960
- STACK_COMMAND: kb
- THREAD_SHA1_HASH_MOD_FUNC: 1769e2d3ecb806245c507aa4173a59411e9d65e3
- THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f727a705b9d9affec5f46feeafa10207b9e8adbb
- THREAD_SHA1_HASH_MOD: bf9bdb83f395e7a60f8629cfdfd92da8ae929b05
- FOLLOWUP_IP:
- rtwlane+306c4
- fffff80f`c62306c4 4883eb01 sub rbx,1
- FAULT_INSTR_CODE: 1eb8348
- SYMBOL_STACK_INDEX: 8
- SYMBOL_NAME: rtwlane+306c4
- FOLLOWUP_NAME: MachineOwner
- MODULE_NAME: rtwlane
- IMAGE_NAME: rtwlane.sys
- DEBUG_FLR_IMAGE_TIMESTAMP: 59096e5b
- BUCKET_ID_FUNC_OFFSET: 306c4
- FAILURE_BUCKET_ID: 0x133_DPC_rtwlane!unknown_function
- BUCKET_ID: 0x133_DPC_rtwlane!unknown_function
- PRIMARY_PROBLEM_CLASS: 0x133_DPC_rtwlane!unknown_function
- TARGET_TIME: 2017-07-12T18:46:46.000Z
- OSBUILD: 14393
- OSSERVICEPACK: 1480
- SERVICEPACK_NUMBER: 0
- OS_REVISION: 0
- SUITE_MASK: 784
- PRODUCT_TYPE: 1
- OSPLATFORM_TYPE: x64
- OSNAME: Windows 10
- OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
- USER_LCID: 0
- OSBUILD_TIMESTAMP: 2017-07-07 02:26:09
- BUILDDATESTAMP_STR: 170706-2004
- BUILDLAB_STR: rs1_release
- BUILDOSVER_STR: 10.0.14393.1480
- ANALYSIS_SESSION_ELAPSED_TIME: 7dcb
- ANALYSIS_SOURCE: KM
- FAILURE_ID_HASH_STRING: km:0x133_dpc_rtwlane!unknown_function
- FAILURE_ID_HASH: {59e49550-247c-b883-d51a-d0d9f839f43f}
- Followup: MachineOwner
- ========================================================================
- =================== Dump File: 071317-24406-01.dmp ====================
- ========================================================================
- Mini Kernel Dump File: Only registers and stack trace are available
- Windows 10 Kernel Version 14393 MP (4 procs) Free x64
- Product: WinNt, suite: TerminalServer SingleUserTS Personal
- Built by: 14393.1480.amd64fre.rs1_release.170706-2004
- Kernel base = 0xfffff803`dc41d000 PsLoadedModuleList = 0xfffff803`dc71c040
- Debug session time: Thu Jul 13 04:59:45.263 2017 (UTC - 4:00)
- System Uptime: 0 days 9:09:08.015
- BugCheck 133, {0, 501, 500, fffff803dc7bd540}
- *** ERROR: Symbol file could not be found. Defaulted to export symbols for hal.dll -
- *** WARNING: Unable to verify timestamp for rtwlane.sys
- *** ERROR: Module load completed but symbols could not be loaded for rtwlane.sys
- *************************************************************************
- *** ***
- *** ***
- *** 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: TickPeriods ***
- *** ***
- *************************************************************************
- Probably caused by : rtwlane.sys ( rtwlane+306c4 )
- Followup: MachineOwner
- DPC_WATCHDOG_VIOLATION (133)
- The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
- or above.
- Arguments:
- Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
- component can usually be identified with a stack trace.
- Arg2: 0000000000000501, The DPC time count (in ticks).
- Arg3: 0000000000000500, The DPC time allotment (in ticks).
- Arg4: fffff803dc7bd540
- 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: TickPeriods ***
- *** ***
- *************************************************************************
- DUMP_CLASS: 1
- DUMP_QUALIFIER: 400
- BUILD_VERSION_STRING: 10.0.14393.1480 (rs1_release.170706-2004)
- SYSTEM_MANUFACTURER: HP
- SYSTEM_PRODUCT_NAME: HP Pavilion Notebook
- SYSTEM_SKU: Y5U04EA#A2N
- SYSTEM_VERSION: Type1ProductConfigId
- BIOS_VENDOR: Insyde
- BIOS_VERSION: F.38
- BIOS_DATE: 05/24/2017
- BASEBOARD_MANUFACTURER: HP
- BASEBOARD_PRODUCT: 8216
- BASEBOARD_VERSION: 83.17
- DUMP_TYPE: 2
- DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
- CPU_COUNT: 4
- CPU_MHZ: b58
- CPU_VENDOR: GenuineIntel
- CPU_FAMILY: 6
- CPU_MODEL: 8e
- CPU_STEPPING: 9
- CPU_MICROCODE: 6,8e,9,0 (F,M,S,R) SIG: 5E'00000000 (cache) 5E'00000000 (init)
- CUSTOMER_CRASH_COUNT: 1
- DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
- BUGCHECK_STR: 0x133
- PROCESS_NAME: System
- CURRENT_IRQL: d
- ANALYSIS_SESSION_HOST: USERNAME-PC
- ANALYSIS_SESSION_TIME: 07-14-2017 23:59:48.0326
- ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
- LAST_CONTROL_TRANSFER: from fffff803dc43ffb7 to fffff803dc56c960
- STACK_COMMAND: kb
- THREAD_SHA1_HASH_MOD_FUNC: 49f22de85a436d24af2c8987e7dcca04014e743d
- THREAD_SHA1_HASH_MOD_FUNC_OFFSET: dbf6a0c06a351e4d9efecea980df0e51b03a478b
- THREAD_SHA1_HASH_MOD: ed504dc32ca1d616d5212fc03ad543768968fa0f
- FOLLOWUP_IP:
- rtwlane+306c4
- fffff80f`9b3206c4 4883eb01 sub rbx,1
- FAULT_INSTR_CODE: 1eb8348
- SYMBOL_STACK_INDEX: 8
- SYMBOL_NAME: rtwlane+306c4
- FOLLOWUP_NAME: MachineOwner
- MODULE_NAME: rtwlane
- IMAGE_NAME: rtwlane.sys
- DEBUG_FLR_IMAGE_TIMESTAMP: 59096e5b
- BUCKET_ID_FUNC_OFFSET: 306c4
- FAILURE_BUCKET_ID: 0x133_DPC_rtwlane!unknown_function
- BUCKET_ID: 0x133_DPC_rtwlane!unknown_function
- PRIMARY_PROBLEM_CLASS: 0x133_DPC_rtwlane!unknown_function
- TARGET_TIME: 2017-07-13T08:59:45.000Z
- OSBUILD: 14393
- OSSERVICEPACK: 1480
- SERVICEPACK_NUMBER: 0
- OS_REVISION: 0
- SUITE_MASK: 784
- PRODUCT_TYPE: 1
- OSPLATFORM_TYPE: x64
- OSNAME: Windows 10
- OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
- USER_LCID: 0
- OSBUILD_TIMESTAMP: 2017-07-07 02:26:09
- BUILDDATESTAMP_STR: 170706-2004
- BUILDLAB_STR: rs1_release
- BUILDOSVER_STR: 10.0.14393.1480
- ANALYSIS_SESSION_ELAPSED_TIME: 1735c
- ANALYSIS_SOURCE: KM
- FAILURE_ID_HASH_STRING: km:0x133_dpc_rtwlane!unknown_function
- FAILURE_ID_HASH: {59e49550-247c-b883-d51a-d0d9f839f43f}
- Followup: MachineOwner
- ========================================================================
- =================== Dump File: 071317-26359-01.dmp ====================
- ========================================================================
- Mini Kernel Dump File: Only registers and stack trace are available
- Windows 10 Kernel Version 14393 MP (4 procs) Free x64
- Product: WinNt, suite: TerminalServer SingleUserTS Personal
- Built by: 14393.1480.amd64fre.rs1_release.170706-2004
- Kernel base = 0xfffff802`94e1c000 PsLoadedModuleList = 0xfffff802`9511b040
- Debug session time: Wed Jul 12 19:48:23.018 2017 (UTC - 4:00)
- System Uptime: 0 days 4:49:53.770
- BugCheck 1E, {ffffffffc0000005, fffff805b5c065da, ffffde81c93b5528, ffffde81c93b4d60}
- *** WARNING: Unable to verify timestamp for rtwlane.sys
- *** ERROR: Module load completed but symbols could not be loaded for rtwlane.sys
- *** WARNING: Unable to verify timestamp for win32k.sys
- *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
- Probably caused by : memory_corruption
- Followup: memory_corruption
- 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: fffff805b5c065da, The address that the exception occurred at
- Arg3: ffffde81c93b5528, Parameter 0 of the exception
- Arg4: ffffde81c93b4d60, Parameter 1 of the exception
- Debugging Details:
- DUMP_CLASS: 1
- DUMP_QUALIFIER: 400
- BUILD_VERSION_STRING: 10.0.14393.1480 (rs1_release.170706-2004)
- SYSTEM_MANUFACTURER: HP
- SYSTEM_PRODUCT_NAME: HP Pavilion Notebook
- SYSTEM_SKU: Y5U04EA#A2N
- SYSTEM_VERSION: Type1ProductConfigId
- BIOS_VENDOR: Insyde
- BIOS_VERSION: F.38
- BIOS_DATE: 05/24/2017
- BASEBOARD_MANUFACTURER: HP
- BASEBOARD_PRODUCT: 8216
- BASEBOARD_VERSION: 83.17
- DUMP_TYPE: 2
- WRITE_ADDRESS: ffffde81c93b4d60
- EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
- FAULTING_IP:
- rtwlane+465da
- fffff805`b5c065da 4d8baee8050000 mov r13,qword ptr [r14+5E8h]
- EXCEPTION_PARAMETER1: ffffde81c93b5528
- EXCEPTION_PARAMETER2: ffffde81c93b4d60
- BUGCHECK_STR: 0x1E_c0000005
- CPU_COUNT: 4
- CPU_MHZ: b58
- CPU_VENDOR: GenuineIntel
- CPU_FAMILY: 6
- CPU_MODEL: 8e
- CPU_STEPPING: 9
- CPU_MICROCODE: 6,8e,9,0 (F,M,S,R) SIG: 5E'00000000 (cache) 5E'00000000 (init)
- CUSTOMER_CRASH_COUNT: 1
- DEFAULT_BUCKET_ID: CODE_CORRUPTION
- PROCESS_NAME: System
- CURRENT_IRQL: 2
- ANALYSIS_SESSION_HOST: USERNAME-PC
- ANALYSIS_SESSION_TIME: 07-15-2017 00:03:32.0239
- ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
- LAST_CONTROL_TRANSFER: from fffff80294fe9cd3 to fffff80294f6b960
- STACK_COMMAND: kb
- CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
- fffff80294f5aca1 - nt!MmGetVirtualForPhysical+15
- [ fa:ef ]
- fffff80294f5acb3 - nt!MmGetVirtualForPhysical+27 (+0x12)
- [ f6:86 ]
- 2 errors : !nt (fffff80294f5aca1-fffff80294f5acb3)
- MODULE_NAME: memory_corruption
- IMAGE_NAME: memory_corruption
- FOLLOWUP_NAME: memory_corruption
- DEBUG_FLR_IMAGE_TIMESTAMP: 0
- MEMORY_CORRUPTOR: LARGE
- FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
- BUCKET_ID: MEMORY_CORRUPTION_LARGE
- PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE
- TARGET_TIME: 2017-07-12T23:48:23.000Z
- OSBUILD: 14393
- OSSERVICEPACK: 1480
- SERVICEPACK_NUMBER: 0
- OS_REVISION: 0
- SUITE_MASK: 784
- PRODUCT_TYPE: 1
- OSPLATFORM_TYPE: x64
- OSNAME: Windows 10
- OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
- USER_LCID: 0
- OSBUILD_TIMESTAMP: 2017-07-07 02:26:09
- BUILDDATESTAMP_STR: 170706-2004
- BUILDLAB_STR: rs1_release
- BUILDOSVER_STR: 10.0.14393.1480
- ANALYSIS_SESSION_ELAPSED_TIME: 1acc
- ANALYSIS_SOURCE: KM
- FAILURE_ID_HASH_STRING: km:memory_corruption_large
- FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}
- Followup: memory_corruption
- ========================================================================
- =================== Dump File: 071417-23750-01.dmp ====================
- ========================================================================
- Mini Kernel Dump File: Only registers and stack trace are available
- Windows 10 Kernel Version 14393 MP (4 procs) Free x64
- Product: WinNt, suite: TerminalServer SingleUserTS Personal
- Built by: 14393.1480.amd64fre.rs1_release.170706-2004
- Kernel base = 0xfffff801`f7882000 PsLoadedModuleList = 0xfffff801`f7b81040
- Debug session time: Thu Jul 13 23:43:49.838 2017 (UTC - 4:00)
- System Uptime: 0 days 2:13:48.598
- BugCheck 1E, {ffffffffc0000005, fffff801f78b5cc2, 0, ffffffffffffffff}
- *** WARNING: Unable to verify timestamp for igdkmd64.sys
- *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
- *** WARNING: Unable to verify timestamp for win32k.sys
- *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
- Probably caused by : memory_corruption
- Followup: memory_corruption
- 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: fffff801f78b5cc2, The address that the exception occurred at
- Arg3: 0000000000000000, Parameter 0 of the exception
- Arg4: ffffffffffffffff, Parameter 1 of the exception
- Debugging Details:
- DUMP_CLASS: 1
- DUMP_QUALIFIER: 400
- BUILD_VERSION_STRING: 10.0.14393.1480 (rs1_release.170706-2004)
- SYSTEM_MANUFACTURER: HP
- SYSTEM_PRODUCT_NAME: HP Pavilion Notebook
- SYSTEM_SKU: Y5U04EA#A2N
- SYSTEM_VERSION: Type1ProductConfigId
- BIOS_VENDOR: Insyde
- BIOS_VERSION: F.38
- BIOS_DATE: 05/24/2017
- BASEBOARD_MANUFACTURER: HP
- BASEBOARD_PRODUCT: 8216
- BASEBOARD_VERSION: 83.17
- DUMP_TYPE: 2
- READ_ADDRESS: ffffffffffffffff
- EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
- FAULTING_IP:
- nt!KeSetEvent+12
- fffff801`f78b5cc2 f6017f test byte ptr [rcx],7Fh
- EXCEPTION_PARAMETER2: ffffffffffffffff
- BUGCHECK_STR: 0x1E_c0000005_R
- CPU_COUNT: 4
- CPU_MHZ: b58
- CPU_VENDOR: GenuineIntel
- CPU_FAMILY: 6
- CPU_MODEL: 8e
- CPU_STEPPING: 9
- CPU_MICROCODE: 6,8e,9,0 (F,M,S,R) SIG: 5E'00000000 (cache) 5E'00000000 (init)
- CUSTOMER_CRASH_COUNT: 1
- DEFAULT_BUCKET_ID: CODE_CORRUPTION
- PROCESS_NAME: System
- CURRENT_IRQL: 2
- ANALYSIS_SESSION_HOST: USERNAME-PC
- ANALYSIS_SESSION_TIME: 07-15-2017 00:08:21.0111
- ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
- EXCEPTION_RECORD: ffff9b8f18b0c000 -- (.exr 0xffff9b8f18b0c000)
- ExceptionAddress: ffff9b8f18030bb0
- ExceptionCode: 46c39270
- ExceptionFlags: ffffc88c
- NumberParameters: 404230160
- Parameter[0]: 0000000000006003
- Parameter[1]: 000000000001418b
- Parameter[2]: 00000002ffffffff
- Parameter[3]: 0000000000000000
- Parameter[4]: 0000000000000000
- Parameter[5]: 0000000000000000
- Parameter[6]: 0000000000000000
- Parameter[7]: 0000000000000000
- Parameter[8]: 0000000000000000
- Parameter[9]: 0000000000000000
- Parameter[10]: 0001000000000000
- Parameter[11]: 0000000000000000
- Parameter[12]: 0000000000000000
- Parameter[13]: 0000000000000000
- Parameter[14]: 0000000000000000
- TRAP_FRAME: ffffc4e2713899b8 -- (.trap 0xffffc4e2713899b8)
- Unable to read trap frame at ffffc4e2`713899b8
- LAST_CONTROL_TRANSFER: from fffff801f7a4fcb2 to fffff801f79d1960
- STACK_COMMAND: kb
- CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
- fffff801f7892a6d - nt!MiInsertNonPagedPoolOnSlist+45d
- [ f6:c4 ]
- 1 error : !nt (fffff801f7892a6d)
- MODULE_NAME: memory_corruption
- IMAGE_NAME: memory_corruption
- FOLLOWUP_NAME: memory_corruption
- DEBUG_FLR_IMAGE_TIMESTAMP: 0
- MEMORY_CORRUPTOR: ONE_BYTE
- FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
- BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
- PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_ONE_BYTE
- TARGET_TIME: 2017-07-14T03:43:49.000Z
- OSBUILD: 14393
- OSSERVICEPACK: 1480
- SERVICEPACK_NUMBER: 0
- OS_REVISION: 0
- SUITE_MASK: 784
- PRODUCT_TYPE: 1
- OSPLATFORM_TYPE: x64
- OSNAME: Windows 10
- OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
- USER_LCID: 0
- OSBUILD_TIMESTAMP: 2017-07-07 02:26:09
- BUILDDATESTAMP_STR: 170706-2004
- BUILDLAB_STR: rs1_release
- BUILDOSVER_STR: 10.0.14393.1480
- ANALYSIS_SESSION_ELAPSED_TIME: da91
- ANALYSIS_SOURCE: KM
- FAILURE_ID_HASH_STRING: km:memory_corruption_one_byte
- FAILURE_ID_HASH: {ad110d6a-3b33-2c0a-c931-570eae1ba92d}
- Followup: memory_corruption
- ========================================================================
- =================== Dump File: 071517-24531-01.dmp ====================
- ========================================================================
- Mini Kernel Dump File: Only registers and stack trace are available
- Windows 10 Kernel Version 14393 MP (4 procs) Free x64
- Product: WinNt, suite: TerminalServer SingleUserTS Personal
- Built by: 14393.1480.amd64fre.rs1_release.170706-2004
- Kernel base = 0xfffff803`5ee0e000 PsLoadedModuleList = 0xfffff803`5f10d040
- Debug session time: Fri Jul 14 20:52:22.532 2017 (UTC - 4:00)
- System Uptime: 0 days 21:06:16.293
- BugCheck 3B, {c0000005, fffff8035ef634c7, ffffb58145c5e500, 0}
- *** WARNING: Unable to verify timestamp for aswSP.sys
- *** ERROR: Module load completed but symbols could not be loaded for aswSP.sys
- Probably caused by : memory_corruption
- Followup: memory_corruption
- SYSTEM_SERVICE_EXCEPTION (3b)
- An exception happened while executing a system service routine.
- Arguments:
- Arg1: 00000000c0000005, Exception code that caused the bugcheck
- Arg2: fffff8035ef634c7, Address of the instruction which caused the bugcheck
- Arg3: ffffb58145c5e500, Address of the context record for the exception that caused the bugcheck
- Arg4: 0000000000000000, zero.
- Debugging Details:
- DUMP_CLASS: 1
- DUMP_QUALIFIER: 400
- BUILD_VERSION_STRING: 10.0.14393.1480 (rs1_release.170706-2004)
- SYSTEM_MANUFACTURER: HP
- SYSTEM_PRODUCT_NAME: HP Pavilion Notebook
- SYSTEM_SKU: Y5U04EA#A2N
- SYSTEM_VERSION: Type1ProductConfigId
- BIOS_VENDOR: Insyde
- BIOS_VERSION: F.38
- BIOS_DATE: 05/24/2017
- BASEBOARD_MANUFACTURER: HP
- BASEBOARD_PRODUCT: 8216
- BASEBOARD_VERSION: 83.17
- DUMP_TYPE: 2
- EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
- FAULTING_IP:
- nt!ExpInterlockedPopEntrySListFault+0
- fffff803`5ef634c7 498b08 mov rcx,qword ptr [r8]
- CONTEXT: ffffb58145c5e500 -- (.cxr 0xffffb58145c5e500)
- rax=000000258b90000a rbx=00007ffc74280000 rcx=ffffc60bef871f80
- rdx=efffc60bfc763b70 rsi=ffffb5813c717180 rdi=ffffc60bef871f80
- rip=fffff8035ef634c7 rsp=ffffb58145c5ef00 rbp=0000000000000000
- r8=efffc60bfc763b70 r9=0000000000000000 r10=ffffc60bef871f80
- r11=ffffc60bfbf7c080 r12=00000000000000b8 r13=0000000000000000
- r14=0000000000000002 r15=0000000000000008
- iopl=0 nv up ei ng nz na pe nc
- cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
- nt!ExpInterlockedPopEntrySListFault:
- fffff803`5ef634c7 498b08 mov rcx,qword ptr [r8] ds:002b:efffc60b`fc763b70=????????????????
- Resetting default scope
- CPU_COUNT: 4
- CPU_MHZ: b58
- CPU_VENDOR: GenuineIntel
- CPU_FAMILY: 6
- CPU_MODEL: 8e
- CPU_STEPPING: 9
- CPU_MICROCODE: 6,8e,9,0 (F,M,S,R) SIG: 5E'00000000 (cache) 5E'00000000 (init)
- CUSTOMER_CRASH_COUNT: 1
- DEFAULT_BUCKET_ID: CODE_CORRUPTION
- BUGCHECK_STR: 0x3B
- PROCESS_NAME: explorer.exe
- CURRENT_IRQL: 0
- ANALYSIS_SESSION_HOST: USERNAME-PC
- ANALYSIS_SESSION_TIME: 07-15-2017 00:11:45.0333
- ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
- LAST_CONTROL_TRANSFER: from fffff8035ee4a093 to fffff8035ef634c7
- CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
- fffff8035ee4dc31-fffff8035ee4dc32 2 bytes - nt!MiIsAddressValid+c1
- [ ff f6:7f b5 ]
- fffff8035ee643a3-fffff8035ee643a4 2 bytes - nt!MiResolvePageTablePage+53 (+0x16772)
- [ 80 f6:00 b5 ]
- fffff8035ee67d85-fffff8035ee67d86 2 bytes - nt!MiGetNextPageTable+1a5 (+0x39e2)
- [ 80 f6:00 b5 ]
- fffff8035ee67db8-fffff8035ee67db9 2 bytes - nt!MiGetNextPageTable+1d8 (+0x33)
- [ 80 f6:00 b5 ]
- 8 errors : !nt (fffff8035ee4dc31-fffff8035ee67db9)
- MODULE_NAME: memory_corruption
- IMAGE_NAME: memory_corruption
- FOLLOWUP_NAME: memory_corruption
- DEBUG_FLR_IMAGE_TIMESTAMP: 0
- MEMORY_CORRUPTOR: LARGE
- STACK_COMMAND: .cxr 0xffffb58145c5e500 ; kb
- FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
- BUCKET_ID: MEMORY_CORRUPTION_LARGE
- PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE
- TARGET_TIME: 2017-07-15T00:52:22.000Z
- OSBUILD: 14393
- OSSERVICEPACK: 1480
- SERVICEPACK_NUMBER: 0
- OS_REVISION: 0
- SUITE_MASK: 784
- PRODUCT_TYPE: 1
- OSPLATFORM_TYPE: x64
- OSNAME: Windows 10
- OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
- USER_LCID: 0
- OSBUILD_TIMESTAMP: 2017-07-07 02:26:09
- BUILDDATESTAMP_STR: 170706-2004
- BUILDLAB_STR: rs1_release
- BUILDOSVER_STR: 10.0.14393.1480
- ANALYSIS_SESSION_ELAPSED_TIME: 1b6c
- ANALYSIS_SOURCE: KM
- FAILURE_ID_HASH_STRING: km:memory_corruption_large
- FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}
- Followup: memory_corruption
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement