win7 蓝屏 貌似和e1e6032.sys有关

• 问题

• 

  

  0

  登录进行投票

  Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
  Copyright (c) Microsoft Corporation. All rights reserved.
  
  
  Loading Dump File [C:\Users\_alonso\Desktop\052610-15522-01.dmp]
  Mini Kernel Dump File: Only registers and stack trace are available
  
  Symbol search path is: SRV*c:\temp*http://msdl.microsoft.com/download/symbols
  Executable search path is:
  Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
  Product: WinNt, suite: TerminalServer SingleUserTS
  Built by: 7600.16539.x86fre.win7_gdr.100226-1909
  Machine Name:
  Kernel base = 0x83e0d000 PsLoadedModuleList = 0x83f55810
  Debug session time: Wed May 26 11:39:33.730 2010 (GMT+8)
  System Uptime: 0 days 1:10:15.570
  Loading Kernel Symbols
  ...............................................................
  ................................................................
  .....................
  Loading User Symbols
  Loading unloaded module list
  ........
  Unable to load image \SystemRoot\system32\DRIVERS\e1e6032.sys, Win32 error 0n2
  *** WARNING: Unable to verify timestamp for e1e6032.sys
  *** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
  *******************************************************************************
  *                                                                             *
  *                        Bugcheck Analysis                                    *
  *                                                                             *
  *******************************************************************************
  
  Use !analyze -v to get detailed debugging information.
  
  BugCheck 1000007E, {c0000005, 83eb37fb, 9031b7a0, 9031b380}
  
  Probably caused by : e1e6032.sys ( e1e6032+55b1 )
  
  Followup: MachineOwner
  ---------
  
  0: kd> !analyze -v
  *******************************************************************************
  *                                                                             *
  *                        Bugcheck Analysis                                    *
  *                                                                             *
  *******************************************************************************
  
  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
  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: 83eb37fb, The address that the exception occurred at
  Arg3: 9031b7a0, Exception Record Address
  Arg4: 9031b380, Context Record Address
  
  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!IoFreeMdl+9
  83eb37fb f6460620        test    byte ptr [esi+6],20h
  
  EXCEPTION_RECORD:  9031b7a0 -- (.exr 0xffffffff9031b7a0)
  ExceptionAddress: 83eb37fb (nt!IoFreeMdl+0x00000009)
     ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
  NumberParameters: 2
     Parameter[0]: 00000000
     Parameter[1]: 3fb7c5f1
  Attempt to read from address 3fb7c5f1
  
  CONTEXT:  9031b380 -- (.cxr 0xffffffff9031b380)
  eax=3fb7c5eb ebx=86dea000 ecx=86cad000 edx=b862b42d esi=3fb7c5eb edi=86dea000
  eip=83eb37fb esp=9031b868 ebp=9031b86c iopl=0         nv up ei pl nz na pe nc
  cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
  nt!IoFreeMdl+0x9:
  83eb37fb f6460620        test    byte ptr [esi+6],20h       ds:0023:3fb7c5f1=??
  Resetting default scope
  
  CUSTOMER_CRASH_COUNT:  1
  
  DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
  
  PROCESS_NAME:  System
  
  CURRENT_IRQL:  0
  
  ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
  
  EXCEPTION_PARAMETER1:  00000000
  
  EXCEPTION_PARAMETER2:  3fb7c5f1
  
  READ_ADDRESS: GetPointerFromAddress: unable to read from 83f75718
  Unable to read MiSystemVaType memory at 83f55160
   3fb7c5f1
  
  FOLLOWUP_IP:
  e1e6032+55b1
  9efb75b1 ??              ???
  
  BUGCHECK_STR:  0x7E
  
  LAST_CONTROL_TRANSFER:  from 9efb75b1 to 83eb37fb
  
  STACK_TEXT: 
  9031b86c 9efb75b1 3fb7c5eb 86cad000 87842b48 nt!IoFreeMdl+0x9
  WARNING: Stack unwind information not available. Following frames may be wrong.
  9031b884 9efb79c4 86cad000 b862b42d b862b42d e1e6032+0x55b1
  9031b8a4 9efc059e 86cad000 00000000 00000001 e1e6032+0x59c4
  9031b8c8 9efc0631 86caf208 00000001 86cad000 e1e6032+0xe59e
  9031b8e0 9efbcd9b 86cad000 00000000 86c5f0e0 e1e6032+0xe631
  9031b8f4 8ce98f0b 000004d2 00000000 8ce55338 e1e6032+0xad9b
  9031b930 8ce9b9c9 00c5f0e0 0000007e 86c5f3ec ndis!ndisMCommonHaltMiniport+0x54f
  9031b94c 8ce9d701 86c5f0e0 86c5f028 86c5f0e0 ndis!ndisMHaltMiniport+0x5a
  9031ba7c 8ce4ca5d 86c5f028 87059688 86c5f0e0 ndis!ndisPnPRemoveDevice+0x33a
  9031baac 8ce8cfe7 86c5f028 87059688 87059764 ndis!ndisPnPRemoveDeviceEx+0xaa
  9031baf0 83e494bc 86c5f028 87059688 9031bb8c ndis!ndisPnPDispatch+0x3cf
  9031bb08 83fe9eeb 86e27690 864fa008 86e27690 nt!IofCallDriver+0x63
  9031bb38 83fc0b3d 86e27690 00000000 864fa008 nt!IopSynchronousCall+0xc2
  9031bb90 83e21c3e 86e27690 00000002 ac9ecac0 nt!IopRemoveDevice+0xd4
  9031bbbc 83fc0951 00000016 ac9ecac0 00000000 nt!PnpRemoveLockedDeviceNode+0x16c
  9031bbd0 83fc08b7 00000002 00000016 00000000 nt!PnpDeleteLockedDeviceNode+0x2d
  9031bc04 83fc0238 86e27690 ac9ecac0 00000002 nt!PnpDeleteLockedDeviceNodes+0x4c
  9031bcc4 83fc2210 9031bcf4 00000000 8c375ce8 nt!PnpProcessQueryRemoveAndEject+0x946
  9031bcdc 83fc3d58 00000000 8837d2b8 8659ba70 nt!PnpProcessTargetDeviceEvent+0x38
  9031bd00 83e7af3b 8837d2b8 00000000 8659ba70 nt!PnpDeviceEventWorker+0x216
  9031bd50 8401b6bb 00000001 bdcaf64b 00000000 nt!ExpWorkerThread+0x10d
  9031bd90 83ecd0f9 83e7ae2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
  00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
  
  
  SYMBOL_STACK_INDEX:  1
  
  SYMBOL_NAME:  e1e6032+55b1
  
  FOLLOWUP_NAME:  MachineOwner
  
  MODULE_NAME: e1e6032
  
  IMAGE_NAME:  e1e6032.sys
  
  DEBUG_FLR_IMAGE_TIMESTAMP:  49c9236b
  
  STACK_COMMAND:  .cxr 0xffffffff9031b380 ; kb
  
  FAILURE_BUCKET_ID:  0x7E_e1e6032+55b1
  
  BUCKET_ID:  0x7E_e1e6032+55b1
  
  Followup: MachineOwner
  ---------
  
  请大家给点提示，非常感谢！

  ---

  在IT的路上，You'll never walk alone

  2010年5月26日 5:13

  回复

  |

  引用