BSOD:( pls help

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

  1. acydburn

    acydburn New Member

    Joined:
    Aug 20, 2012
    Messages:
    20
    Likes Received:
    0
    Geting crashes 2-3 times a day .. included all specs and the dump file .. if anybody can give a look.. thank you .. and sorry for the first post!
     

    Attached Files:

  2. acydburn

    acydburn New Member

    Joined:
    Aug 20, 2012
    Messages:
    20
    Likes Received:
    0
    nobody haves an opinion?
     
  3. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,838
    Likes Received:
    1,566
    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:  VISTA_DRIVER_FAULT
    [COLOR=#ff0000]BUGCHECK_STR:  0x1E[/COLOR]
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    EXCEPTION_RECORD:  fffff88002f1b4c8 -- (.exr 0xfffff88002f1b4c8)
    ExceptionAddress: fffff88003da045a (wanarp!WanNdisSendComplete+0x000000000000007a)
       [COLOR=#ff0000]ExceptionCode: c0000005 (Access violation)[/COLOR]
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    TRAP_FRAME:  fffff88002f1b570 -- (.trap 0xfffff88002f1b570)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa80070107a0 rbx=0000000000000000 rcx=00000000000005ad
    rdx=fffffa80070106c0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88003da045a rsp=fffff88002f1b700 rbp=0000000000000000
     r8=000000000000d1b0  r9=0000000000000030 r10=fffff80002c12000
    r11=000000000000053e r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    wanarp!WanNdisSendComplete+0x7a:
    fffff880`03da045a 488b4608        mov     rax,qword ptr [rsi+8] ds:0590:00000000`00000008=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002c88bbe to fffff80002c91190
    
    STACK_TEXT:  
    fffff880`02f1a5a8 fffff800`02c88bbe : 00000000`00000028 00000000`00000008 fffff880`02f1ad20 fffff800`02cbc160 : nt!KeBugCheck
    fffff880`02f1a5b0 fffff800`02cbbe2d : fffff800`02e97770 fffff800`02dd42f0 fffff800`02c12000 fffff880`02f1b4c8 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff880`02f1a5e0 fffff800`02cbac05 : fffff800`02dd7fac fffff880`02f1a658 fffff880`02f1b4c8 fffff800`02c12000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`02f1a610 fffff800`02ccbb81 : fffff880`02f1b4c8 fffff880`02f1ad20 fffff880`00000000 00000000`00000007 : nt!RtlDispatchException+0x415
    fffff880`02f1acf0 fffff800`02c90842 : fffff880`02f1b4c8 fffffa80`07010590 fffff880`02f1b570 69436d4d`021e0003 : nt!KiDispatchException+0x135
    fffff880`02f1b390 fffff800`02c8f14a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
    fffff880`02f1b570 fffff880`03da045a : fffffa80`07010590 69436d4d`021e0003 00000000`00000000 fffff880`0f28a37d : nt!KiGeneralProtectionFault+0x10a
    fffff880`02f1b700 fffff880`014cd36f : fffffa80`06f4f010 00000000`00000000 fffffa80`04d611a0 00000000`00000000 : wanarp!WanNdisSendComplete+0x7a
    fffff880`02f1b730 fffff880`03d4f5f4 : fffffa80`00000000 fffffa80`07010590 fffff880`00000000 00000000`00000000 : ndis!ndisMSendCompleteNetBufferListsInternal+0x10f
    fffff880`02f1b7d0 fffff880`014ce128 : fffffa80`04d611a0 00000000`00000000 00000000`00000000 fffffa80`03b013b0 : pacer! ?? ::FNODOBFM::`string'+0x144
    fffff880`02f1b830 fffff880`0445cebc : fffff880`04458580 00000000`00000000 fffffa80`079e3010 fffff880`04458110 : ndis!ndisMSendCompleteX+0x188
    fffff880`02f1b880 fffff880`0445d337 : fffffa80`00000000 fffffa80`043c02a0 00000000`00000000 fffffa80`0795fd30 : ndiswan!CompleteSendDesc+0x21c
    fffff880`02f1b8e0 fffff880`01418aea : fffffa80`0795fd30 fffffa80`05281e00 fffffa80`049c8b80 fffffa80`07960810 : ndiswan!ProtoCoSendComplete+0x77
    fffff880`02f1b930 fffff880`04484e9d : fffffa80`05281e00 fffffa80`0795fd30 00000000`00000000 fffff880`0447d2f0 : ndis!ndisMCoSendCompleteToNdisPacket+0x11a
    fffff880`02f1b980 fffff880`04488f93 : 00000000`00000000 fffffa80`049c8b80 fffffa80`0795fd30 fffffa80`04c281a0 : raspppoe!DereferencePacket+0x191
    fffff880`02f1b9b0 fffff880`014d264e : fffffa80`04bfae00 fffffa80`079ce6c0 fffffa80`079ce6c0 fffff880`014102f7 : raspppoe!PrSendComplete+0x6b
    fffff880`02f1b9f0 fffff880`014d251d : 00000000`00000000 fffffa80`04bfae20 00000000`00000000 fffffa80`077cbe20 : ndis!ndisSendCompleteWithPause+0xde
    fffff880`02f1ba40 fffff880`014cd36f : fffffa80`00000000 fffffa80`0795fd30 fffffa80`04c281a0 fffff880`0418ef5d : ndis!ndisMSendNetBufferListsCompleteToNdisPackets+0x9d
    fffff880`02f1ba90 fffff880`014cd21d : fffffa80`00000000 fffffa80`07c08e20 00000000`00000001 fffffa80`00000000 : ndis!ndisMSendCompleteNetBufferListsInternal+0x10f
    fffff880`02f1bb30 fffff880`0417cc38 : fffffa80`050a4000 fffff880`041b7400 fffff880`0488a000 fffff880`041b7400 : ndis!NdisMSendNetBufferListsComplete+0x6d
    fffff880`02f1bb70 fffffa80`050a4000 : fffff880`041b7400 fffff880`0488a000 fffff880`041b7400 fffffa80`053b3310 : nvmf6264+0x5c38
    fffff880`02f1bb78 fffff880`041b7400 : fffff880`0488a000 fffff880`041b7400 fffffa80`053b3310 fffff880`041a15be : 0xfffffa80`050a4000
    fffff880`02f1bb80 fffff880`0488a000 : fffff880`041b7400 fffffa80`053b3310 fffff880`041a15be fffffa80`053b32f0 : nvmf6264+0x40400
    fffff880`02f1bb88 fffff880`041b7400 : fffffa80`053b3310 fffff880`041a15be fffffa80`053b32f0 fffff880`041b7400 : 0xfffff880`0488a000
    fffff880`02f1bb90 fffffa80`053b3310 : fffff880`041a15be fffffa80`053b32f0 fffff880`041b7400 fffff880`0488a000 : nvmf6264+0x40400
    fffff880`02f1bb98 fffff880`041a15be : fffffa80`053b32f0 fffff880`041b7400 fffff880`0488a000 00000000`00000000 : 0xfffffa80`053b3310
    fffff880`02f1bba0 fffffa80`053b32f0 : fffff880`041b7400 fffff880`0488a000 00000000`00000000 00000000`00000000 : nvmf6264+0x2a5be
    fffff880`02f1bba8 fffff880`041b7400 : fffff880`0488a000 00000000`00000000 00000000`00000000 fffff880`041b7400 : 0xfffffa80`053b32f0
    fffff880`02f1bbb0 fffff880`0488a000 : 00000000`00000000 00000000`00000000 fffff880`041b7400 00000000`00000000 : nvmf6264+0x40400
    fffff880`02f1bbb8 00000000`00000000 : 00000000`00000000 fffff880`041b7400 00000000`00000000 00000000`00000000 : 0xfffff880`0488a000
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    wanarp!WanNdisSendComplete+7a
    fffff880`03da045a 488b4608        mov     rax,qword ptr [rsi+8]
    
    SYMBOL_STACK_INDEX:  7
    
    SYMBOL_NAME:  wanarp!WanNdisSendComplete+7a
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: wanarp
    
    IMAGE_NAME:  wanarp.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a874
    
    FAILURE_BUCKET_ID:  X64_0x1E_wanarp!WanNdisSendComplete+7a
    
    BUCKET_ID:  X64_0x1E_wanarp!WanNdisSendComplete+7a
    
    Followup: MachineOwner
    The KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.


    • The reason for the above could be down to a number of issues:

    Your Bios is out of date:

    BiosVendor = American Megatrends Inc.
    BiosVersion = 0803
    BiosReleaseDate = 06/09/2009
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    SystemFamily = To Be Filled By O.E.M.
    SystemVersion = System Version
    SystemSKU = To Be Filled By O.E.M.
    BaseBoardManufacturer = ASUSTeK Computer INC.
    BaseBoardProduct = M4N78
    BaseBoardVersion = Rev X.0x

    Please update: http://uk.asus.com/Motherboards/AMD_AM2Plus/M4N78/#download

    You have also a couple suspect drivers:

    AVerA706_x64.sys Wed Jun 10 11:21:54 2009 : Please update:http://www.avermedia.com/Support/FAQ.aspx?type=2

    SNCAMD.SYS Thu Jan 25 10:48:38 2007: USB 2.0 PC Camera (SN9C201) driver Please update

    snp2sxp.sys Mon Apr 09 04:37:15 2007: USB2.0 PC Camera (SNP2STD) Update: http://www.rosewill.com/products/d_1083/productDetail.htm


    Could you also run a scan with Malwarebytes: http://www.malwarebytes.org/lp/malware_lp/?gclid=COSEwIvB-LECFSsntAodPD0AYg
    Also to rule any disk errors please run a chkdsk too.
     
    #3 kemical, Aug 21, 2012
    Last edited: Aug 21, 2012
  4. acydburn

    acydburn New Member

    Joined:
    Aug 20, 2012
    Messages:
    20
    Likes Received:
    0
    should I understand that the memory is the problem ?
     
  5. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,838
    Likes Received:
    1,566
    Sorry this editor can be a nightmare at times.. If the above doesn't help then try running memtest on individual sticks (the reason for this is two fold, this is so you know which module is the bad one and testing multiple sticks can mean that errors are not picked up) for at least 7/8 passes.

    http://www.memtest.org/
     
    #5 kemical, Aug 21, 2012
    Last edited: Aug 21, 2012
  6. acydburn

    acydburn New Member

    Joined:
    Aug 20, 2012
    Messages:
    20
    Likes Received:
    0
    After researching bios update on m4n78 found out that it`s not recomended..lots of users rolled back to old drivers because new one`s are problematic ... ran malware .. clean .. ran mem test .. clean , avermedia drivers updated and the usb cam chkdsk done and no erors.. hope it`s ok now .. I`ll post a reply if something ..Thank you very much kemical!
     
  7. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,838
    Likes Received:
    1,566
    Hmm... I'm pretty sure you won't have run a proper memtest in the time allotted but if you error out again I'd seriously consider using the method outline above.

    Oh and if you could post the link to the bios update information you mentioned that would be a great help for our bsod team, thanks.
     
  8. acydburn

    acydburn New Member

    Joined:
    Aug 20, 2012
    Messages:
    20
    Likes Received:
    0
  9. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,838
    Likes Received:
    1,566
    Thanks and yes I did see that but as it's only a few out of what must be millions of boards sold then it's not what I would consider a major issue. Still,l it is one that's undesirable so why not at least update the bios to the version prior? See how you go anyway.
     
  10. acydburn

    acydburn New Member

    Joined:
    Aug 20, 2012
    Messages:
    20
    Likes Received:
    0
    testing a thing..I know the bios is old .. but wanted to see how things are going with a dif version for chipset drivers..so far so good.. if another blue screen apears.. i`m gona flash the bios..btw for the mem test I used Prime it was all ok ..
     
  11. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,838
    Likes Received:
    1,566
    Prime? Isn't that for testing cpu's?
     
  12. bassfisher6522

    bassfisher6522 Essential Member

    Joined:
    Aug 27, 2008
    Messages:
    4,884
    Likes Received:
    317
    Dude: Prime95 test the CPU and Memtest+ test the memory....you are running the wrong test. If you follow Ross's instructions to the letter you will find out that your memory (one of the sticks or all of them) are bad.

    Note: Memtest+ takes hours and hours to run not minutes...
     
  13. bassfisher6522

    bassfisher6522 Essential Member

    Joined:
    Aug 27, 2008
    Messages:
    4,884
    Likes Received:
    317
    Although I do like your screen name....reference to the 1995 movie hackers...acid burn played by Angelina Jolie. Not a bad movie either.
     
  14. acydburn

    acydburn New Member

    Joined:
    Aug 20, 2012
    Messages:
    20
    Likes Received:
    0
    ok that bsod was back,and I observed that it comes everytime when the mem is in full load(game on utorrent on music on copy extract etc)...tested the mem with memtest86_4.0 , the weird thing is that the first time was with erors.. removed one stick .. was clean .. the other one alone was clean .. both of them again erors .. and then moved both of them to the next 2 slots and was clean .. I left them only 1 run over .. I`m planing tonight to leave the pc on and do the full test..should I buy another mems?
     
  15. acydburn

    acydburn New Member

    Joined:
    Aug 20, 2012
    Messages:
    20
    Likes Received:
    0
    Ok did the overnight memtest .. again I got errors.. and observed in the same "place" in diferent test ..it`s the memory sticks or the motherboard? .. i`m gonna be at work today.. any reply I`ll get tonight..many thanks guys!
     
  16. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,838
    Likes Received:
    1,566
    How long did you run memtest on the sticks individually? Sometimes it can take forever for a error to show. The fact that your getting errors with both sticks shows your on the right track. I'd try testing overnight on single sticks.
     
  17. acydburn

    acydburn New Member

    Joined:
    Aug 20, 2012
    Messages:
    20
    Likes Received:
    0
    with just one stick I ran it 2 pass,this night stick nr 1 all night :) curious with 2 stick not even 1 pass and showing errors..
     
  18. bassfisher6522

    bassfisher6522 Essential Member

    Joined:
    Aug 27, 2008
    Messages:
    4,884
    Likes Received:
    317
    There you go...bad ram...it needs replacing. It happens to all of us at one time on another, ram going bad. I've even ordered ram and when it came in and installed the brand new ram...bam BSOD....had to RMA the one stick because of bad ram on a brand new stick. It happens.
     
  19. bassfisher6522

    bassfisher6522 Essential Member

    Joined:
    Aug 27, 2008
    Messages:
    4,884
    Likes Received:
    317
    Note....the minimum recommended passes for MemTest86+ is 4 passes.
     
  20. nmsuk

    nmsuk Windows Forum Admin
    Staff Member Premium Supporter

    Joined:
    Sep 7, 2009
    Messages:
    2,709
    Likes Received:
    195
    Isn't necessarily bad ram. Could just be badly configured which is usually the case if the sticks pass on their own.
     

Share This Page

Loading...