Random BSOD 0x000000E1


  1. Posts : 3
    Windows 7 Ultimate x64
       #1

    Random BSOD 0x000000E1


    Hi!

    I got BSOD randomly after I installed windows 7 ultimatium x64 and SP1. Its typically when I open bittorrent or use a lot of CPU/RAM capacity, but also randomy. I tried to remove one RAM-stick (tought it was broken), and downloaded memtest, but this didnt solve the problem.

    I still got randomly BSOD (many per day) and have to restart. Can anyone help me out? I have uploaded the files (all in one .rar-file) the crashes direct to, see attchment.

    All help will appreciate!
      My Computer


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

    Your Ralink 802.11 Wireless Adapter driver caused the BSODs
    Update the driver, newer versions are available here: Ralink-A MEDIATEK COMPANY

    Note that this device is old and wasn't listed as being Windows 7 Certified.
    If no drivers are found that device should be removed

    ASACPI.sys the 2005 version is a huge cause of BSODs
       Information
    Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
    Scroll down to the Utilities category, then scroll down to the "
    ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
    Download and install it.
    Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005)



    Your Nvidia Driver is outdated, update it, http://www.nvidia.com/object/win7-wi...ql-driver.html
    Turn Off driver Verifier is you're using it.
    Code:
    nvlddmkm.sys        fffff880`0f0d1000    fffff880`0fd62e00    0x00c91e00    0x4c37918e    10/07/2010 01:15:58
    Code:
    ASACPI.sys        fffff880`03df4000    fffff880`03dfc000    0x00008000    0x42476c4c    28/03/2005 06:30:36
    Code:
    *******************************************************************************
    *                                                                             *
    *                        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:
    ------------------
    
    
    EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
    
    FAULTING_IP: 
    +0
    00000000`00000000 ??              ???
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    BUGCHECK_STR:  0x1E
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    EXCEPTION_RECORD:  fffff80000b9c468 -- (.exr 0xfffff80000b9c468)
    ExceptionAddress: fffff880043577cf (netr7064+0x000000000002d7cf)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    TRAP_FRAME:  fffff80000b9c510 -- (.trap 0xfffff80000b9c510)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=d7111b00d6902034 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000005 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880043577cf rsp=fffff80000b9c6a0 rbp=0000000000000000
     r8=0000000000000177  r9=fffff88000f15ce0 r10=fffff80000b9c820
    r11=0000000000000005 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    netr7064+0x2d7cf:
    fffff880`043577cf ??              ???
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800028cc5fe to fffff800028d4c10
    
    STACK_TEXT:  
    fffff800`00b9b548 fffff800`028cc5fe : fffffa80`0429f240 fffff880`016d104b fffff800`00b9bcc0 fffff800`02900830 : nt!KeBugCheck
    fffff800`00b9b550 fffff800`029004fd : fffff800`02ade71c fffff800`02a1bc30 fffff800`02858000 fffff800`00b9c468 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff800`00b9b580 fffff800`028ff2d5 : fffff800`02a1f0fc fffff800`00b9b5f8 fffff800`00b9c468 fffff800`02858000 : nt!RtlpExecuteHandlerForException+0xd
    fffff800`00b9b5b0 fffff800`02910361 : fffff800`00b9c468 fffff800`00b9bcc0 fffff800`00000000 fffffa80`03909a80 : nt!RtlDispatchException+0x415
    fffff800`00b9bc90 fffff800`028d42c2 : fffff800`00b9c468 fffffa80`03e1d320 fffff800`00b9c510 fffffa80`03dff530 : nt!KiDispatchException+0x135
    fffff800`00b9c330 fffff800`028d2bca : fffffa80`03df9ff0 00000000`00000000 00000000`00000003 00000000`0000000b : nt!KiExceptionDispatch+0xc2
    fffff800`00b9c510 fffff880`043577cf : fffffa80`03dfa000 fffffa80`03e1d320 00000000`00000000 fffffa80`03dff530 : nt!KiGeneralProtectionFault+0x10a
    fffff800`00b9c6a0 fffffa80`03dfa000 : fffffa80`03e1d320 00000000`00000000 fffffa80`03dff530 fffffa80`03dfa000 : netr7064+0x2d7cf
    fffff800`00b9c6a8 fffffa80`03e1d320 : 00000000`00000000 fffffa80`03dff530 fffffa80`03dfa000 00000000`00000000 : 0xfffffa80`03dfa000
    fffff800`00b9c6b0 00000000`00000000 : fffffa80`03dff530 fffffa80`03dfa000 00000000`00000000 00000000`00000000 : 0xfffffa80`03e1d320
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    netr7064+2d7cf
    fffff880`043577cf ??              ???
    
    SYMBOL_STACK_INDEX:  7
    
    SYMBOL_NAME:  netr7064+2d7cf
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: netr7064
    
    IMAGE_NAME:  netr7064.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  45923fcb
    
    FAILURE_BUCKET_ID:  X64_0x1E_VRF_netr7064+2d7cf
    
    BUCKET_ID:  X64_0x1E_VRF_netr7064+2d7cf
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 3
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Thank you so much! I have now removed the wireless stick (no driver for win 7), and my computer has not crashed for 1 day! I think its so much better to buy new usb-wirless lan card compared to reinstall win XP!

    THANKS!
      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 08:14.
Find Us