Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000000000000
STACK_TEXT:
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: INVALID_KERNEL_CONTEXT
Followup: MachineOwner
---------
Please run driver verifier
Driver Verifier - Enable and Disable
Have you updated all your drivers with the latest ones?
Also found this
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002f4535f, Address of the instruction which caused the bugcheck
Arg3: fffff88006363b50, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!MiIdentifyPfn+26f
fffff800`02f4535f f0410fba6e481f lock bts dword ptr [r14+48h],1Fh
CONTEXT: fffff88006363b50 -- (.cxr 0xfffff88006363b50)
rax=0000000000000001 rbx=02000000001209dc rcx=0a00000000000020
rdx=00000000000142cd rsi=0000000000000000 rdi=fffffa800a00cac0
rip=fffff80002f4535f rsp=fffff88006364530 rbp=fffffa8006d81090
r8=000000000001cb4e r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=fffff880031d7180 r13=0000000000000000
r14=8afffa8006d81010 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!MiIdentifyPfn+0x26f:
fffff800`02f4535f f0410fba6e481f lock bts dword ptr [r14+48h],1Fh ds:002b:8afffa80`06d81058=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002f4600b to fffff80002f4535f
STACK_TEXT:
fffff880`06364530 fffff800`02f4600b : 00000000`00000000 00000000`00000004 fffffa80`0a00cac0 fffffa80`0a00c000 : nt!MiIdentifyPfn+0x26f
fffff880`063645d0 fffff800`032aaa25 : fffffa80`0a00c000 fffff880`06364b60 fffff880`063646a8 00000000`00000000 : nt!MmQueryPfnList+0xbb
fffff880`06364610 fffff800`031eda68 : 00000000`00000006 00000000`00000000 fffffa80`0a00c000 00000000`00000001 : nt!PfpPfnPrioRequest+0x115
fffff880`06364660 fffff800`031a27b3 : 00000000`00000000 00000000`00000000 00000000`64496d4d fffffa80`64496d01 : nt! ?? ::NNGAKEGL::`string'+0x47c0d
fffff880`063646f0 fffff800`031a3029 : 00000000`0137b628 fffff880`031d7180 00000000`0137b680 00000000`0137b648 : nt!ExpQuerySystemInformation+0x1193
fffff880`06364aa0 fffff800`02e9c253 : fffffa80`097b2b50 00000000`03193a30 00000000`090a3c58 00000000`03194610 : nt!NtQuerySystemInformation+0x4d
fffff880`06364ae0 00000000`770c167a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0137b548 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770c167a
FOLLOWUP_IP:
nt!MiIdentifyPfn+26f
fffff800`02f4535f f0410fba6e481f lock bts dword ptr [r14+48h],1Fh
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiIdentifyPfn+26f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be
STACK_COMMAND: .cxr 0xfffff88006363b50 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x3B_nt!MiIdentifyPfn+26f
BUCKET_ID: X64_0x3B_nt!MiIdentifyPfn+26f
Followup: MachineOwner
---------
Please run memtest overnight post back the results
Memtest86.com - Memory Diagnostic
Also update your Broadcom 802.11 Network Adapter wireless drive