KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: 82a26d34, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for aswSnx.sys
*** WARNING: Unable to verify timestamp for klif.sys
*** WARNING: Unable to verify timestamp for klhk.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 1
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-HH6FM2D
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 5
Key : Analysis.Memory.CommitPeak.Mb
Value: 66
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 8e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: 0
BUGCHECK_P3: ffffffff82a26d34
BUGCHECK_P4: 0
TRAP_FRAME: 82a26d34 -- (.trap 0xffffffff82a26d34)
ErrCode = 00000010
eax=00000000 ebx=00000000 ecx=82e99d84 edx=00000073 esi=000007a0 edi=00000b18
eip=00000000 esp=82a26da8 ebp=865288f8 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
00000000 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: svchost.exe
IP_IN_FREE_BLOCK: 0
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
82a26da4 91f5639f 865288f8 865288f8 82f931c8 0x0
82a26dc4 830ba719 00000b18 000007a8 00000001 FortiShield+0x539f
82a26e7c 830a08f1 865288f8 0000003e 82a27088 nt!PspInsertThread+0x65c
82a27040 830c48fa 82a2799c 001fffff 82a27974 nt!PspCreateThread+0x244
82a27474 91ea1d89 82a2799c 001fffff 82a27974 nt!NtCreateThreadEx+0x20b
82a274e8 926926ac 82a2799c 001fffff 82a27974 aswSnx+0x29d89
82a27820 8cfce40a 82a2799c 001fffff 82a27974 klif+0x886ac
82a2785c 8cfcf4d8 926924d8 82a27898 0000002c klhk+0x140a
82a27878 8cfce3cf 85f22a50 82a27898 82a2788c klhk+0x24d8
82a27890 82e8ca16 82a2799c 001fffff 82a27974 klhk+0x13cf
82a27890 82e8a669 82a2799c 001fffff 82a27974 nt!KiSystemServicePostCall
82a27934 830d4aa5 82a2799c 001fffff 82a27974 nt!ZwCreateThreadEx+0x11
82a279cc 83031b8a 00000001 00000000 00000000 nt!RtlpCreateUserThreadEx+0xa4
82a279fc 830392af 800055c8 b213c4fb 00000000 nt!EtwpInjectThread+0x47
82a27a4c 830394fd 88a0c950 c632c008 88aec660 nt!EtwpQueueNotification+0x1d4
82a27ac8 830315a1 88aec660 00000000 82a27ba0 nt!EtwpSendDataBlock+0x16b
82a27b4c 8300a865 00000000 8dfbb840 8dfbb810 nt!EtwpEnableGuid+0x363
82a27be8 8300a7ac 8dfbb770 00000000 0000000c nt!EtwEnableTrace+0xb0
82a27c1c 8300b293 0000000c 8dfbb770 00000004 nt!WdipSemEnableDisableTrace+0x3c
82a27c4c 8300b1e9 00000000 8dfc8490 00000000 nt!WdipSemDisableContextProvider+0x8d
82a27c68 8300ae01 00000030 a400d5f8 a400d5f8 nt!WdipSemDisableContextProviders+0x2f
82a27c84 83009ddd 82a27cac 0000138a a400d610 nt!WdipSemDisableScenario+0xf0
82a27c98 82fef48f 82a27cac 0000000b 00000030 nt!WdipStartEndScenario+0x89
82a27cc4 830a384e b213c3a3 0000000d 0088fac4 nt!WdiDispatchControl+0x47
82a27d14 82e8ca16 0000000d 0088fad8 00000030 nt!NtTraceControl+0x171
82a27d34 00000000 badb0d00 0088faac 00000000 nt!KiSystemServicePostCall
SYMBOL_NAME: FortiShield+539f
MODULE_NAME: FortiShield
IMAGE_NAME: FortiShield.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x8E_FortiShield+539f
OS_VERSION: 7.1.7601.19160
BUILDLAB_STR: win7sp1_gdr
OSPLATFORM_TYPE: x86
OSNAME: Windows 7
FAILURE_ID_HASH: {9c8351a9-cc4e-112c-fc87-101f109523b1}
Followup: MachineOwner
---------
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: 9dbd8d34, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for aswSnx.sys
*** WARNING: Unable to verify timestamp for klif.sys
*** WARNING: Unable to verify timestamp for klhk.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 1
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-HH6FM2D
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 7
Key : Analysis.Memory.CommitPeak.Mb
Value: 66
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 8e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: 0
BUGCHECK_P3: ffffffff9dbd8d34
BUGCHECK_P4: 0
TRAP_FRAME: 9dbd8d34 -- (.trap 0xffffffff9dbd8d34)
ErrCode = 00000010
eax=00000000 ebx=00000000 ecx=82e84d84 edx=00000073 esi=000007d0 edi=0000122c
eip=00000000 esp=9dbd8da8 ebp=888b2a60 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
00000000 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: svchost.exe
IP_IN_FREE_BLOCK: 0
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
9dbd8da4 91f4139f 888b2a60 888b2a60 82f7e1c8 0x0
9dbd8dc4 830a5719 0000122c 00001c60 00000001 FortiShield+0x539f
9dbd8e7c 8308b8f1 888b2a60 0000003e 9dbd9088 nt!PspInsertThread+0x65c
9dbd9040 830af8fa 9dbd999c 001fffff 9dbd9974 nt!PspCreateThread+0x244
9dbd9474 91e8cd89 9dbd999c 001fffff 9dbd9974 nt!NtCreateThreadEx+0x20b
9dbd94e8 91fd86ac 9dbd999c 001fffff 9dbd9974 aswSnx+0x29d89
9dbd9820 8d40140a 9dbd999c 001fffff 9dbd9974 klif+0x886ac
9dbd985c 8d4024d8 91fd84d8 9dbd9898 0000002c klhk+0x140a
9dbd9878 8d4013cf 87649d18 9dbd9898 9dbd988c klhk+0x24d8
9dbd9890 82e77a16 9dbd999c 001fffff 9dbd9974 klhk+0x13cf
9dbd9890 82e75669 9dbd999c 001fffff 9dbd9974 nt!KiSystemServicePostCall
9dbd9934 830bfaa5 9dbd999c 001fffff 9dbd9974 nt!ZwCreateThreadEx+0x11
9dbd99cc 8301cb8a 00000001 00000000 00000000 nt!RtlpCreateUserThreadEx+0xa4
9dbd99fc 830242af 80005a50 ad035450 00000000 nt!EtwpInjectThread+0x47
9dbd9a4c 830244fd 87e62d28 9c7b51c8 87ef0138 nt!EtwpQueueNotification+0x1d4
9dbd9ac8 8301c5a1 87ef0138 00000000 9dbd9ba0 nt!EtwpSendDataBlock+0x16b
9dbd9b4c 82ff5865 00000000 8dfbb840 8dfbb810 nt!EtwpEnableGuid+0x363
9dbd9be8 82ff57ac 8dfbb770 00000000 0000000c nt!EtwEnableTrace+0xb0
9dbd9c1c 82ff6293 0000000c 8dfbb770 00000004 nt!WdipSemEnableDisableTrace+0x3c
9dbd9c4c 82ff61e9 00000000 8dfc8490 00000000 nt!WdipSemDisableContextProvider+0x8d
9dbd9c68 82ff5e01 00000030 b2d33598 b2d33598 nt!WdipSemDisableContextProviders+0x2f
9dbd9c84 82ff4ddd 9dbd9cac 0000138a b2d335b0 nt!WdipSemDisableScenario+0xf0
9dbd9c98 82fda48f 9dbd9cac 0000000b 00000030 nt!WdipStartEndScenario+0x89
9dbd9cc4 8308e84e ad035308 0000000d 001ef814 nt!WdiDispatchControl+0x47
9dbd9d14 82e77a16 0000000d 001ef828 00000030 nt!NtTraceControl+0x171
9dbd9d34 00000000 badb0d00 001ef7fc 00000000 nt!KiSystemServicePostCall
SYMBOL_NAME: FortiShield+539f
MODULE_NAME: FortiShield
IMAGE_NAME: FortiShield.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x8E_FortiShield+539f
OS_VERSION: 7.1.7601.19160
BUILDLAB_STR: win7sp1_gdr
OSPLATFORM_TYPE: x86
OSNAME: Windows 7
FAILURE_ID_HASH: {9c8351a9-cc4e-112c-fc87-101f109523b1}
Followup: MachineOwner
---------
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: 82a26d34, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for aswSnx.sys
*** WARNING: Unable to verify timestamp for klif.sys
*** WARNING: Unable to verify timestamp for klhk.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 1
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-HH6FM2D
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 5
Key : Analysis.Memory.CommitPeak.Mb
Value: 66
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 8e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: 0
BUGCHECK_P3: ffffffff82a26d34
BUGCHECK_P4: 0
TRAP_FRAME: 82a26d34 -- (.trap 0xffffffff82a26d34)
ErrCode = 00000010
eax=00000000 ebx=00000000 ecx=82e99d84 edx=00000073 esi=000007a0 edi=00000b18
eip=00000000 esp=82a26da8 ebp=865288f8 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
00000000 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: svchost.exe
IP_IN_FREE_BLOCK: 0
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
82a26da4 91f5639f 865288f8 865288f8 82f931c8 0x0
82a26dc4 830ba719 00000b18 000007a8 00000001 FortiShield+0x539f
82a26e7c 830a08f1 865288f8 0000003e 82a27088 nt!PspInsertThread+0x65c
82a27040 830c48fa 82a2799c 001fffff 82a27974 nt!PspCreateThread+0x244
82a27474 91ea1d89 82a2799c 001fffff 82a27974 nt!NtCreateThreadEx+0x20b
82a274e8 926926ac 82a2799c 001fffff 82a27974 aswSnx+0x29d89
82a27820 8cfce40a 82a2799c 001fffff 82a27974 klif+0x886ac
82a2785c 8cfcf4d8 926924d8 82a27898 0000002c klhk+0x140a
82a27878 8cfce3cf 85f22a50 82a27898 82a2788c klhk+0x24d8
82a27890 82e8ca16 82a2799c 001fffff 82a27974 klhk+0x13cf
82a27890 82e8a669 82a2799c 001fffff 82a27974 nt!KiSystemServicePostCall
82a27934 830d4aa5 82a2799c 001fffff 82a27974 nt!ZwCreateThreadEx+0x11
82a279cc 83031b8a 00000001 00000000 00000000 nt!RtlpCreateUserThreadEx+0xa4
82a279fc 830392af 800055c8 b213c4fb 00000000 nt!EtwpInjectThread+0x47
82a27a4c 830394fd 88a0c950 c632c008 88aec660 nt!EtwpQueueNotification+0x1d4
82a27ac8 830315a1 88aec660 00000000 82a27ba0 nt!EtwpSendDataBlock+0x16b
82a27b4c 8300a865 00000000 8dfbb840 8dfbb810 nt!EtwpEnableGuid+0x363
82a27be8 8300a7ac 8dfbb770 00000000 0000000c nt!EtwEnableTrace+0xb0
82a27c1c 8300b293 0000000c 8dfbb770 00000004 nt!WdipSemEnableDisableTrace+0x3c
82a27c4c 8300b1e9 00000000 8dfc8490 00000000 nt!WdipSemDisableContextProvider+0x8d
82a27c68 8300ae01 00000030 a400d5f8 a400d5f8 nt!WdipSemDisableContextProviders+0x2f
82a27c84 83009ddd 82a27cac 0000138a a400d610 nt!WdipSemDisableScenario+0xf0
82a27c98 82fef48f 82a27cac 0000000b 00000030 nt!WdipStartEndScenario+0x89
82a27cc4 830a384e b213c3a3 0000000d 0088fac4 nt!WdiDispatchControl+0x47
82a27d14 82e8ca16 0000000d 0088fad8 00000030 nt!NtTraceControl+0x171
82a27d34 00000000 badb0d00 0088faac 00000000 nt!KiSystemServicePostCall
SYMBOL_NAME: FortiShield+539f
MODULE_NAME: FortiShield
IMAGE_NAME: FortiShield.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x8E_FortiShield+539f
OS_VERSION: 7.1.7601.19160
BUILDLAB_STR: win7sp1_gdr
OSPLATFORM_TYPE: x86
OSNAME: Windows 7
FAILURE_ID_HASH: {9c8351a9-cc4e-112c-fc87-101f109523b1}
Followup: MachineOwner
---------
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: 9dbd8d34, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for aswSnx.sys
*** WARNING: Unable to verify timestamp for klif.sys
*** WARNING: Unable to verify timestamp for klhk.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 1
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-HH6FM2D
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 7
Key : Analysis.Memory.CommitPeak.Mb
Value: 66
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 8e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: 0
BUGCHECK_P3: ffffffff9dbd8d34
BUGCHECK_P4: 0
TRAP_FRAME: 9dbd8d34 -- (.trap 0xffffffff9dbd8d34)
ErrCode = 00000010
eax=00000000 ebx=00000000 ecx=82e84d84 edx=00000073 esi=000007d0 edi=0000122c
eip=00000000 esp=9dbd8da8 ebp=888b2a60 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
00000000 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: svchost.exe
IP_IN_FREE_BLOCK: 0
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
9dbd8da4 91f4139f 888b2a60 888b2a60 82f7e1c8 0x0
9dbd8dc4 830a5719 0000122c 00001c60 00000001 FortiShield+0x539f
9dbd8e7c 8308b8f1 888b2a60 0000003e 9dbd9088 nt!PspInsertThread+0x65c
9dbd9040 830af8fa 9dbd999c 001fffff 9dbd9974 nt!PspCreateThread+0x244
9dbd9474 91e8cd89 9dbd999c 001fffff 9dbd9974 nt!NtCreateThreadEx+0x20b
9dbd94e8 91fd86ac 9dbd999c 001fffff 9dbd9974 aswSnx+0x29d89
9dbd9820 8d40140a 9dbd999c 001fffff 9dbd9974 klif+0x886ac
9dbd985c 8d4024d8 91fd84d8 9dbd9898 0000002c klhk+0x140a
9dbd9878 8d4013cf 87649d18 9dbd9898 9dbd988c klhk+0x24d8
9dbd9890 82e77a16 9dbd999c 001fffff 9dbd9974 klhk+0x13cf
9dbd9890 82e75669 9dbd999c 001fffff 9dbd9974 nt!KiSystemServicePostCall
9dbd9934 830bfaa5 9dbd999c 001fffff 9dbd9974 nt!ZwCreateThreadEx+0x11
9dbd99cc 8301cb8a 00000001 00000000 00000000 nt!RtlpCreateUserThreadEx+0xa4
9dbd99fc 830242af 80005a50 ad035450 00000000 nt!EtwpInjectThread+0x47
9dbd9a4c 830244fd 87e62d28 9c7b51c8 87ef0138 nt!EtwpQueueNotification+0x1d4
9dbd9ac8 8301c5a1 87ef0138 00000000 9dbd9ba0 nt!EtwpSendDataBlock+0x16b
9dbd9b4c 82ff5865 00000000 8dfbb840 8dfbb810 nt!EtwpEnableGuid+0x363
9dbd9be8 82ff57ac 8dfbb770 00000000 0000000c nt!EtwEnableTrace+0xb0
9dbd9c1c 82ff6293 0000000c 8dfbb770 00000004 nt!WdipSemEnableDisableTrace+0x3c
9dbd9c4c 82ff61e9 00000000 8dfc8490 00000000 nt!WdipSemDisableContextProvider+0x8d
9dbd9c68 82ff5e01 00000030 b2d33598 b2d33598 nt!WdipSemDisableContextProviders+0x2f
9dbd9c84 82ff4ddd 9dbd9cac 0000138a b2d335b0 nt!WdipSemDisableScenario+0xf0
9dbd9c98 82fda48f 9dbd9cac 0000000b 00000030 nt!WdipStartEndScenario+0x89
9dbd9cc4 8308e84e ad035308 0000000d 001ef814 nt!WdiDispatchControl+0x47
9dbd9d14 82e77a16 0000000d 001ef828 00000030 nt!NtTraceControl+0x171
9dbd9d34 00000000 badb0d00 001ef7fc 00000000 nt!KiSystemServicePostCall
SYMBOL_NAME: FortiShield+539f
MODULE_NAME: FortiShield
IMAGE_NAME: FortiShield.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x8E_FortiShield+539f
OS_VERSION: 7.1.7601.19160
BUILDLAB_STR: win7sp1_gdr
OSPLATFORM_TYPE: x86
OSNAME: Windows 7
FAILURE_ID_HASH: {9c8351a9-cc4e-112c-fc87-101f109523b1}
Followup: MachineOwner
---------
