Hi Abhimanyu11,
Here is the analysis result for reference:
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, 81a5fc73}
Unable to load image \SystemRoot\system32\DRIVERS\wsimd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for wsimd.sys
*** ERROR: Module load completed but symbols could not be loaded for wsimd.sys
Probably caused by : wsimd.sys ( wsimd+8bee )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 81a5fc73, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 81c476f4
Unable to read MiSystemVaType memory at 81c17300
00000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeSetEvent+253
81a5fc73 8b09 mov ecx,dword ptr [ecx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: System
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
TRAP_FRAME: 82d07a58 -- (.trap 0xffffffff82d07a58)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=b851d640 edi=82c20120
eip=81a5fc73 esp=82d07acc ebp=82d07b04 iopl=0 nv up ei pl nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010217
nt!KeSetEvent+0x253:
81a5fc73 8b09 mov ecx,dword ptr [ecx] ds:0023:00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 81b33ca3 to 81b1f5f0
STACK_TEXT:
82d079b0 81b33ca3 0000000a 00000000 00000002 nt!KiBugCheck2
82d079b0 81a5fc73 0000000a 00000000 00000002 nt!KiTrap0E+0x1cf
82d07b04 824229ba b851d640 00000000 82c20120 nt!KeSetEvent+0x253
82d07b18 b8519bee b851d640 82d07b78 8510e008 ndis!NdisSetEvent+0x12
WARNING: Stack unwind information not available. Following frames may be wrong.
82d07b4c 8246ffd0 82d07b78 8247000e 843ec040 wsimd+0x8bee
82d07bdc 82470023 82d07c30 81aab611 8510e1ec ndis!_NDIS_PROTOCOL_BLOCK::NotifyBindComplete+0x6d
82d07be4 81aab611 8510e1ec 00000000 843ec040 ndis!KWorkItemBase<_NDIS_PROTOCOL_BLOCK,KCoalescingWorkItem<_NDIS_PROTOCOL_BLOCK> >::CallbackThunk+0x15
82d07c30 81ab977a 00000000 4be33bb7 00000000 nt!ExpWorkerThread+0xff
82d07c70 81b34fe1 81aab512 00000000 00000000 nt!PspSystemThreadStartup+0x58
82d07c7c 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x15
STACK_COMMAND: kb
FOLLOWUP_IP:
wsimd+8bee
b8519bee ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: wsimd+8bee
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: wsimd
IMAGE_NAME: wsimd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49bf40fe
FAILURE_BUCKET_ID: AV_wsimd+8bee
BUCKET_ID: AV_wsimd+8bee
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_wsimd+8bee
FAILURE_ID_HASH: {57fd296c-b544-408c-48af-24bcd99ca5f6}
Followup: MachineOwner
---------
"This is usually caused by drivers using improper addresses."
What is the type of the wireless adapter ?Have you checked whether the driver is compatible with Windows 8.1 ?
I would suggest you to run "netsh wlan show drivers" to check whether "Hosted network supported " is "Yes"before we try to create the hosted network with the command line.
If the Hosted network is supported,we can try to download the wireless driver from the manufacturer website and manually install the driver for the deivce to have a check .Please pay attention to the system requirements of the driver.
Best regards
-
Edited by
MeipoXuMicrosoft contingent staff
Friday, May 08, 2015 8:54 AM
-
Proposed as answer by
ZigZag3143xMVP, Moderator
Friday, May 08, 2015 10:11 AM