0x0000001a & 0x00000050 - New Install/Build

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Benetration, Aug 19, 2012.

  1. Benetration

    Benetration New Member

    Joined:
    Nov 22, 2011
    Messages:
    10
    Likes Received:
    0
    System Spec:
    Intel Core i5-3570k
    Asus P8Z77-Pro M/b
    16GB DDR3 1600MHz RAM (2x8)
    2x2TB 7200RPM, 64MB cache HDD's
    1x500GB 7200RPM HDD
    nVidia GeForce 8800GTS
    Creative SoundBlaster Xtreme Gamer sound card
    Linksys WMP600N wireless PCI card
    Corsair HX650 PSU
    1x Blu-Ray optical drive
    1x DVD optical drive

    This is a new computer build that I finished a few days ago. I've updated the BIOS, set up a RAID 1 configuration through Intel Rapid Storage Technology/through the BIOS on my 2x2TB HDDs.

    I installed Windows 7 x64 Ultimate and have begun to migrate my programs and data over from my previous machine. This process has been paused because I am experiencing BSOD issues. There are two which have occured:

    0x0000001a - MEMORY_MANAGEMENT
    0x00000050 - PAGE_FAULT_IN_NON_PAGED_AREA

    I ran a Windows Memory Diagnostic test overnight - no problems were found. I've updated all my drivers.

    I have followed the BSOD posting instructions and also googled effortlessly regarding these Stop codes. I just can't make sense of it I'm afraid.

    SFDiag.zip and Screens & HTML Report.zip attached, should contain requested/required files and data. If you need any more information I'll be happy to help!

    Thanks in advance - your help is greatly appreciated!

    Ben :)
     

    Attached Files:

  2. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Take some time and clear up your network stack. True you are getting BSODs that might suggest memory issues but these can be related to drivers misbehaving.
    First uninstall LogMeIn and Remote Anywhere
    LMIRfsDriver.sys 7/14/2008
    lmimirr.sys 4/10/2007
    and
    RaInfo.sys 1/4/2008
    Then check here C:\Windows\System32\Drivers and confirm that those three files are no longer present. If they are simply rename them so that the file extension is changed from .sys to .OLD to break them and prevent them from loading for the time being.
    Next update this driver
    netr28x.sys 2/25/2009 I suspect it's the RT2860 driver from here Ralink-A MEDIATEK COMPANY
    If Blue Screens persist attach any new dump files here.
    If not see what LogMeIn and Remote Anywhere have in the way of something recent. So as not to add drivers that are four or five years old to your system.
    DUMP:
    Code:
    BugCheck 1A, {41287, 0, 0, 0}
    Probably caused by : NETIO.SYS ( NETIO!NsiEnumerateObjectsAllParametersEx+6df )
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041287, The subtype of the bugcheck.
    Arg2: 0000000000000000
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x1a_41287
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  NetSvcHelp.exe
    CURRENT_IRQL:  0
    TRAP_FRAME:  fffff88009c24a60 -- (.trap 0xfffff88009c24a60)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000fffffffff
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002b2500d rsp=fffff88009c24bf0 rbp=fffff88009c24c70
     r8=0000058000000000  r9=00000000ffffffff r10=0000000000000000
    r11=fffff88003500180 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up di pl zr na po nc
    nt!KiDpcInterrupt+0x7d:
    fffff800`02b2500d fc              cld
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002a6a3be to fffff80002ada1c0
    STACK_TEXT:  
    fffff880`09c248f8 fffff800`02a6a3be : 00000000`0000001a 00000000`00041287 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    fffff880`09c24900 fffff800`02ad82ee : 00000000`00000001 00000000`00000000 fffff880`01a78100 fffffa80`000bea10 : nt! ?? ::FNODOBFM::`string'+0x45a45
    fffff880`09c24a60 fffff800`02b2500d : fffffa80`000bea40 fffff880`09c24c70 fffff6fc`4000d618 ffffffff`ffffffff : nt!KiPageFault+0x16e
    fffff880`09c24bf0 fffff800`02aacfca : fffffa80`11879010 fffff880`01a9d438 fffffa80`0ffe0df0 fffff800`02c05fbd : nt!KiDpcInterrupt+0x7d
    fffff880`09c24d80 fffff800`02d90426 : 00000000`c0000000 fffff880`01a14300 00000000`00000000 fffff800`02d0c540 : nt!MiLockCode+0x12a
    fffff880`09c24eb0 fffff880`01a1a71e : fffffa80`115f21a0 fffffa80`11f5d4c0 fffffa80`115f21a0 00000000`00000000 : nt!MmLockPagableSectionByHandle+0x10e
    fffff880`09c24f00 fffff880`01a1acbc : fffffa80`15409b00 fffffa80`115f21a0 fffffa80`11f5d4c0 fffffa80`15409bf8 : ndis!ndisQuerySetMiniportEx+0x6e
    fffff880`09c24f70 fffff880`01a19409 : 006f0051`002d0036 00610050`00200053 00740065`006b0063 fffff880`09c253e8 : ndis!ndisIfGetMiniportStatistics+0x3bd
    fffff880`09c251a0 fffff880`01a19807 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisIfQueryObject+0x389
    fffff880`09c25330 fffff880`01a18cad : fffffa80`11f61870 fffffa80`11f61870 fffff880`09c25410 00060000`00000000 : ndis!ndisNsiGetInterfaceRodInformation+0x207
    fffff880`09c253d0 fffff880`01b0af36 : fffff880`01a79a50 fffffa80`15409000 00000000`00000001 fffffa80`13eccb00 : ndis!ndisNsiGetAllInterfaceInformation+0x42e
    fffff880`09c25490 fffff880`01616e29 : fffffa80`15409000 fffff8a0`00000070 fffffa80`0d7b1da0 fffff880`09c257d0 : NETIO!NsiEnumerateObjectsAllParametersEx+0x6df
    fffff880`09c25670 fffff880`016188e8 : fffffa80`0d7b1da0 fffffa80`0d7b1cd0 00000000`00000000 fffffa80`0d7b1d08 : nsiproxy!NsippEnumerateObjectsAllParameters+0x305
    fffff880`09c25860 fffff880`016189db : fffffa80`113007f0 00000000`00000000 00000000`00000001 00000000`00000003 : nsiproxy!NsippDispatchDeviceControl+0x70
    fffff880`09c258a0 fffff800`02df0717 : fffffa80`140d1a70 fffffa80`140d1a70 fffffa80`0d7b1de8 fffffa80`0d7b1cd0 : nsiproxy!NsippDispatch+0x4b
    fffff880`09c258d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    NETIO!NsiEnumerateObjectsAllParametersEx+6df
    fffff880`01b0af36 3d1a000080      cmp     eax,8000001Ah
    SYMBOL_STACK_INDEX:  b
    SYMBOL_NAME:  NETIO!NsiEnumerateObjectsAllParametersEx+6df
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: NETIO
    IMAGE_NAME:  NETIO.SYS
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79381
    FAILURE_BUCKET_ID:  X64_0x1a_41287_NETIO!NsiEnumerateObjectsAllParametersEx+6df
    BUCKET_ID:  X64_0x1a_41287_NETIO!NsiEnumerateObjectsAllParametersEx+6df
     
  3. Benetration

    Benetration New Member

    Joined:
    Nov 22, 2011
    Messages:
    10
    Likes Received:
    0
    Thanks for your reply Trouble.

    I shall follow your instructions.

    Why would this have happened on the new system? I've had LogMeIn installed on all my machines for years and never had any problems.

    Also, would it be better after I've obtained the updated driver files to do another clean installation again, to kind of, wipe the slate clean and start over? Then just apply the updated drives on the new install? If that makes sense. Just so the OS isn't buggy for the rest of its lifetime. Or am I talking jibberish? :confused:
     
  4. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Why don't you try updating the driver for your Network adapter with the RaLink Chipset that is using the RaInfo.sys 1/4/2008 that I referenced above from the link I included and uninstall all things LogMeIn including Remote Anywhere and see if the machine runs more dependably, with respect to the Blue Screen Issues.

    Your problem for now seems to be related to your network, see if you can resolve that before resorting to anything more drastic.

    Again, once you have taken care of the problem device and software along with the associated drivers that I have enumerated above. Then we can see if there is anything else we may be missing. If the machine is stable then look for something more recent from LogMeIn. Surely they have updated some of their drivers since 2007 / 2008 or at least I would hope so.
    Regards
    Randy
     
  5. Benetration

    Benetration New Member

    Joined:
    Nov 22, 2011
    Messages:
    10
    Likes Received:
    0
    I've updated the network drivers as requested, and removed all LogMeIn software. No BSOD's thus far.

    LogMeIn does not have a more updated driver unfortunately, which is pretty bad for them. I have done extensive searching on the Internet.
     
  6. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Alright lets just be patient for a while. I'm not sure at what rate you were experiencing BSODs previously but you might want to give it a few days just to see if it remains stable or starts to exhibit new symptoms.
    In the mean time hold off installing any new or old for that matter, software that might impact your network stack for now.
    Regards
    Randy
     

Share This Page

Loading...