BSOD - error 0x00000001e - need help


  1. Posts : 2
    Window 7pro 64-bit
       #1

    BSOD - error 0x00000001e - need help


    hey everyone,

    i think i have tried everything i could think. Still nothing, so i am coming to yall for help. i have included the dump files as well.

    windows 7 64

    thanks for the help!!!!
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi Zero007.

    Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats including stop 0x3B BSOD.
    Code:
    Windows 7 Kernel Version 7600 MP (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

    Let us know for any further BSOD after installing Service Pack 1.
    ___________________________________________
    Code:
    BugCheck 3B, {c0000005, fffff80002b34dbf, fffff880028f2ee0, 0}
    
    Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+8f )
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 2
    Window 7pro 64-bit
    Thread Starter
       #3

    i downloaded SP1 and everything else for windows update. it is still BSOD when i start a download for a game. here is the new dump files.
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus.
    5. Apply > OK
    6. Accept then restart.

    Make it sure that utorrent is not in action. And then download another game. Does it still BSOD? Let us see.

    __________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff80002ca8ff0, 0, ffffffffffffffff}
    
    Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+150 )
    
    Followup: MachineOwner
    ---------
    
    2: 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: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002ca8ff0, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb2100
    GetUlongFromAddress: unable to read from fffff80002eb21c0
     0000000000000000 Nonpaged pool
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nt!MiReplenishPageSlist+150
    fffff800`02ca8ff0 48897308        mov     qword ptr [rbx+8],rsi
    
    BUGCHECK_STR:  0x1E_c0000005_R
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  Uplay.exe
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff80002cce5d8 to fffff80002c82d00
    
    STACK_TEXT:  
    fffff880`0963ef18 fffff800`02cce5d8 : 00000000`0000001e ffffffff`c0000005 fffff800`02ca8ff0 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0963ef20 fffff800`02c82382 : fffff880`0963f6f8 0002fa80`07685be0 fffff880`0963f7a0 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x4987d
    fffff880`0963f5c0 fffff800`02c80c8a : 00000000`00000000 00000000`00000000 00000000`00000068 00000000`00000001 : nt!KiExceptionDispatch+0xc2
    fffff880`0963f7a0 fffff800`02ca8ff0 : fffffa80`0ff82b30 fffffa80`0f4cb060 00000000`13f80000 fffff800`02ca321c : nt!KiGeneralProtectionFault+0x10a
    fffff880`0963f930 fffff800`02ca771f : fffffa80`0cc02490 00000000`000000ea fffffa80`076b5be0 00000000`000000ea : nt!MiReplenishPageSlist+0x150
    fffff880`0963f9a0 fffff800`02c90e34 : 00000000`00000000 00000000`00000002 00000000`00000000 ffffffff`ffffffff : nt!MiRemoveAnyPage+0x24f
    fffff880`0963fac0 fffff800`02c80e2e : 00000000`00000001 00000000`14016000 00000000`129e4a01 00000000`00000001 : nt!MmAccessFault+0x1224
    fffff880`0963fc20 00000000`77219b60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`0b00f3b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77219b60
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiReplenishPageSlist+150
    fffff800`02ca8ff0 48897308        mov     qword ptr [rbx+8],rsi
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  nt!MiReplenishPageSlist+150
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b
    
    IMAGE_VERSION:  6.1.7601.17592
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!MiReplenishPageSlist+150
    
    BUCKET_ID:  X64_0x1E_c0000005_R_nt!MiReplenishPageSlist+150
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x1e_c0000005_r_nt!mireplenishpageslist+150
    
    FAILURE_ID_HASH:  {07a04de5-bbfe-1adf-07f9-787bb73a882e}
    
    Followup: MachineOwner
    ---------
      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 21:35.
Find Us