Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Asuma1987

  1. I'm disable Emsisoft Internet Security and stopping process (Start-->Control Panel-->administ tools-->services-->Emsisoft Protection Service)
  2. hi. the same problem. the first blue screen this morning. Analyze minidump: Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\010115-4804-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144 Machine Name: Kernel base = 0xfffff800`02c55000 PsLoadedModuleList = 0xfffff800`02e98890 Debug session time: Thu Jan 1 10:36:47.437 2015 (UTC + 3:00) System Uptime: 0 days 0:15:39.280 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {fffffab8d1767c40, 2, 0, fffff880044066a2} Unable to load image fwndis64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for fwndis64.sys *** ERROR: Module load completed but symbols could not be loaded for fwndis64.sys *** ERROR: Symbol file could not be found. Defaulted to export symbols for ndis.sys - Probably caused by : fwndis64.sys ( fwndis64+36a2 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 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 kernel debugger is available get stack backtrace. Arguments: Arg1: fffffab8d1767c40, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff880044066a2, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f02100 fffffab8d1767c40 CURRENT_IRQL: 2 FAULTING_IP: fwndis64+36a2 fffff880`044066a2 8b4130 mov eax,dword ptr [rcx+30h] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff8800a2e4e20 -- (.trap 0xfffff8800a2e4e20) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff8800a2e4fe8 rbx=0000000000000000 rcx=fffffab8d1767c10 rdx=fffffa800dcb102c rsi=0000000000000000 rdi=0000000000000000 rip=fffff880044066a2 rsp=fffff8800a2e4fb0 rbp=fffffa800ef55020 r8=fffff8800a2e50d8 r9=fffff8800a2e50c8 r10=000000000000f070 r11=fffffa800ef55000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc fwndis64+0x36a2: fffff880`044066a2 8b4130 mov eax,dword ptr [rcx+30h] ds:d030:fffffab8`d1767c40=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002cca169 to fffff80002ccabc0 STACK_TEXT: fffff880`0a2e4cd8 fffff800`02cca169 : 00000000`0000000a fffffab8`d1767c40 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0a2e4ce0 fffff800`02cc8de0 : 00000000`00000000 00000000`00000000 fffff880`0150ed00 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`0a2e4e20 fffff880`044066a2 : 00000000`00000002 fffff880`014b427e fffffa80`0e5151a0 fffff880`014fab67 : nt!KiPageFault+0x260 fffff880`0a2e4fb0 00000000`00000002 : fffff880`014b427e fffffa80`0e5151a0 fffff880`014fab67 fffffa80`0ef558ec : fwndis64+0x36a2 fffff880`0a2e4fb8 fffff880`014b427e : fffffa80`0e5151a0 fffff880`014fab67 fffffa80`0ef558ec 00000000`00000400 : 0x2 fffff880`0a2e4fc0 00000000`0000000e : 00000000`00000000 fffffa80`0e519c60 00000000`00000004 fffffa80`0dcb1020 : ndis!NdisDprAllocatePacketNonInterlocked+0x76e fffff880`0a2e5050 00000000`00000000 : fffffa80`0e519c60 00000000`00000004 fffffa80`0dcb1020 00000000`00000048 : 0xe STACK_COMMAND: kb FOLLOWUP_IP: fwndis64+36a2 fffff880`044066a2 8b4130 mov eax,dword ptr [rcx+30h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: fwndis64+36a2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: fwndis64 IMAGE_NAME: fwndis64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 549f77ba FAILURE_BUCKET_ID: X64_0xD1_fwndis64+36a2 BUCKET_ID: X64_0xD1_fwndis64+36a2 Followup: MachineOwner --------- 0: kd> lmvm fwndis64 start end module name fffff880`04403000 fffff880`0447c000 fwndis64 T (no symbols) Loaded symbol image file: fwndis64.sys Image path: fwndis64.sys Image name: fwndis64.sys Timestamp: Sun Dec 28 06:23:38 2014 (549F77BA) CheckSum: 000862BB ImageSize: 00079000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
  • Create New...