BSOD on startup - Error 8E (Dumps included)


  1. Posts : 14
    Windows 7 Professional x64
       #1

    BSOD on startup - Error 8E (Dumps included)


    Hi,

    Any help on this issue would be much appreciated.

    On a PC used as a reception PC at work we're having issues with BSODs almost immediately after start up. The error (0x00000008E) occurs approximately 3 minutes after windows starts and has occurred repetitively today for the first time.

    No new software has recently been installed and no hardware changed. The system is a dell built system, is not and has never been overclocked.

    Any help would be much appreciated.
    I have attached the dump files to this post.

    Many thanks
    gcaster
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    Run a scan of Malwarebytes, you system is likely to be infected with malware
    You may need to run Malwarebytes in safemode with networking

    iaStor.sys is to be blamed, the most usual causes are Malware infection
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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: 8365dceb, The address that the exception occurred at
    Arg3: a4d8c74c, Trap Frame
    Arg4: 00000000
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    iaStor+41ceb
    8365dceb 8b4704          mov     eax,dword ptr [edi+4]
    
    TRAP_FRAME:  a4d8c74c -- (.trap 0xffffffffa4d8c74c)
    ErrCode = 00000000
    eax=855598e0 ebx=00000000 ecx=0000000e edx=85559870 esi=85559870 edi=00000000
    eip=8365dceb esp=a4d8c7c0 ebp=a4d8c7d0 iopl=0         nv up ei ng nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
    iaStor+0x41ceb:
    8365dceb 8b4704          mov     eax,dword ptr [edi+4] ds:0023:00000004=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x8E
    
    PROCESS_NAME:  WmiPrvSE.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 82c8f4bc to 8365dceb
    
    STACK_TEXT:  
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a4d8c7d0 82c8f4bc 87d4c240 855598e0 a1118218 iaStor+0x41ceb
    a4d8c7e8 89000bc7 89004290 a4656c08 87040000 nt!IofCallDriver+0x63
    a4d8c818 8900ddfd a4d8c8e8 2dd880b2 00000000 MpFilter+0xbc7
    a4d8c8ac 8900e560 87c5e378 a4d8c8e8 00000000 MpFilter+0xddfd
    a4d8c8c4 8356619a 87c5e378 00d8c8e8 a4d8c900 MpFilter+0xe560
    a4d8c930 8356b9ec 85782370 87c5e318 278ef025 fltmgr!FltpPerformPreMountCallbacks+0x1d0
    a4d8c998 8356bc5b 87fa8020 88969330 88969330 fltmgr!FltpFsControlMountVolume+0x116
    a4d8c9c8 82c8f4bc 87fa8020 88969330 82d89d80 fltmgr!FltpFsControl+0x5b
    a4d8c9e0 82e0b031 82c1f870 87d4c240 82c1f900 nt!IofCallDriver+0x63
    a4d8ca44 82cef56d 87d4c240 856e5701 00000000 nt!IopMountVolume+0x1d8
    a4d8ca7c 82e9347f 856e57e0 a4d8cba8 a4d8cb40 nt!IopCheckVpbMounted+0x64
    a4d8cb60 82e745f3 87d4c240 a5284ac8 856e4008 nt!IopParseDevice+0x7c9
    a4d8cbdc 82e9a7b9 00000000 a4d8cc30 00000040 nt!ObpLookupObjectName+0x4fa
    a4d8cc38 82e92b0b 00a4e5d4 85284ac8 00000001 nt!ObOpenObjectByName+0x165
    a4d8ccb4 82e9e422 00a4e630 80100080 00a4e5d4 nt!IopCreateFile+0x673
    a4d8cd00 82c963ea 00a4e630 80100080 00a4e5d4 nt!NtCreateFile+0x34
    a4d8cd00 775b6344 00a4e630 80100080 00a4e5d4 nt!KiFastCallEntry+0x12a
    00a4e638 00000000 00000000 00000000 00000000 0x775b6344
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    iaStor+41ceb
    8365dceb 8b4704          mov     eax,dword ptr [edi+4]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  iaStor+41ceb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: iaStor
    
    IMAGE_NAME:  iaStor.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b8f1b5b
    
    FAILURE_BUCKET_ID:  0x8E_iaStor+41ceb
    
    BUCKET_ID:  0x8E_iaStor+41ceb
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 14
    Windows 7 Professional x64
    Thread Starter
       #3

    Thank you very much, I'll get this done tomorrow morning and report back.

    Thanks again.
      My Computer


  4. Posts : 14
    Windows 7 Professional x64
    Thread Starter
       #4

    No luck I'm afraid.

    Plenty of malware cleaned off but still getting blue screens.

    Any other suggestions? I don't really want to get to a stage by which we have to format the PC!

    Thanks again
      My Computer


  5. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #5

    gcaster said:
    No luck I'm afraid.

    Plenty of malware cleaned off but still getting blue screens.

    Any other suggestions? I don't really want to get to a stage by which we have to format the PC!

    Thanks again
    Seems the Malware caused some system corruption, repair any corrupted files with SFC
    SFC /SCANNOW Command - System File Checker

    If that fails do a Repair Install
      My Computer


  6. Posts : 14
    Windows 7 Professional x64
    Thread Starter
       #6

    I've tried the SFC scan but that's reporting no errors. With this PC being an anytime upgrade am I right in believing it's not possible to do a repair install?
      My Computer


  7. Posts : 14
    Windows 7 Professional x64
    Thread Starter
       #7

    Well I've just re-ran Malwarebytes in safe mode which caused the system to crash (no BSOD just a full reset) and now the system will no longer boot.
    Looks like a full system restore is in order. Thank you for your help anyway.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:39.
Find Us