ASUS N53SN BSOD

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Batuhan Altun, Jun 13, 2011.

  1. Batuhan Altun

    Batuhan Altun New Member

    Joined:
    Jun 13, 2011
    Messages:
    6
    Likes Received:
    0
    Hi,
    My laptop is ASUS N53SN, it has 4gb RAM, but i have added 2x2gb, now it have 4x2gb=8gb memory,
    My problem is, i used my laptop 1 month with no problem, after it crashed and restart, screen frezed,
    after one week i have a BSOD,
    and after one week every two day i have a BSOD,
    and one week ago, it crashed 6 times a day,
    so first i make a memtest86
    no problem,
    them windows memory diog. no problem,
    then i format the system,
    but after format in 2 day i have 2 BSOD,
    as you see Crash Address are same, so is it a memory problem, but why test programs couldt find it,
    thanks a lot, sory about my english

    Untitled.
     

    Attached Files:

    #1 Batuhan Altun, Jun 13, 2011
    Last edited: Jun 13, 2011
  2. Batuhan Altun

    Batuhan Altun New Member

    Joined:
    Jun 13, 2011
    Messages:
    6
    Likes Received:
    0
    Today, screen freezed, after restart again BSOD
     

    Attached Files:

  3. Captain Jack

    Captain Jack Extraordinary Member

    Joined:
    Mar 6, 2010
    Messages:
    1,952
    Likes Received:
    139
    Hello there,

    It's some hardware that's causing the system to crash. We BSOD analyst don't recommend to Overclocking. I would recommend to reset all the settings to default values and see if then the system crashes. Go follow this link Hardware Diagnostic | Captain Debugger and run a complete Hardware Diagnostic.

    Here is article Stop 0x124 - what it means and what to try - Windows 7 Forums

    Code:
    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: fffff80000b9a010, 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: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
    
    FAULTING_IP: 
    +1a6952f009bdfdc
    fffff800`00b9a010 38afb90000f8    cmp     byte ptr [rdi-7FFFF47h],ch
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003111100
     0000000000000000 
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1E
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    EXCEPTION_RECORD:  fffff80000b9af38 -- (.exr 0xfffff80000b9af38)
    ExceptionAddress: fffff880018b84ac (tcpip!IppFragmentPackets+0x000000000000066c)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    TRAP_FRAME:  fffff80000b9afe0 -- (.trap 0xfffff80000b9afe0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=01750430fffffa80 rbx=0000000000000000 rcx=fffff8800167eec0
    rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880018b84ac rsp=fffff80000b9b170 rbp=000000000000000e
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    tcpip!IppFragmentPackets+0x66c:
    fffff880`018b84ac 83802001000001  add     dword ptr [rax+120h],1 ds:cf90:01750430`fffffba0=????????
    Resetting default scope
    
    MISALIGNED_IP: 
    tcpip!IppFragmentPackets+66c
    fffff880`018b84ac 83802001000001  add     dword ptr [rax+120h],1
    
    LAST_CONTROL_TRANSFER:  from fffff80002f6a4fb to fffff80002ee1d00
    
    STACK_TEXT:  
    fffff800`00b99f58 fffff800`02f6a4fb : 00000000`0000001e ffffffff`c0000005 fffff800`00b9a010 00000000`00000000 : nt!KeBugCheckEx
    fffff800`00b99f60 fffff800`02f35be4 : fffff800`00000000 fffffa80`0a02ce20 00000000`00000000 fffff800`00b9a000 : nt!KipFatalFilter+0x1b
    fffff800`00b99fa0 fffff800`02f0dadc : fffffa80`0a37f0f0 0000000d`00000018 fffff800`00b9a030 fffff800`00b9a800 : nt! ?? ::FNODOBFM::`string'+0x83d
    fffff800`00b99fe0 fffff800`02f0d55d : fffff800`03021d4c fffff800`00b9bf20 00000000`00000000 fffff800`02e62000 : nt!_C_specific_handler+0x8c
    fffff800`00b9a050 fffff800`02f0c335 : fffff800`03021d4c fffff800`00b9a0c8 fffff800`00b9af38 fffff800`02e62000 : nt!RtlpExecuteHandlerForException+0xd
    fffff800`00b9a080 fffff800`02f1d3b1 : fffff800`00b9af38 fffff800`00b9a790 fffff800`00000000 00000000`00000000 : nt!RtlDispatchException+0x415
    fffff800`00b9a760 fffff800`02ee1382 : fffff800`00b9af38 fffffa80`07ff48a8 fffff800`00b9afe0 fffffa80`0b47b3b0 : nt!KiDispatchException+0x135
    fffff800`00b9ae00 fffff800`02edfc8a : 00000000`00000000 00000000`00000000 fffffa80`0b401210 00000000`00000000 : nt!KiExceptionDispatch+0xc2
    fffff800`00b9afe0 fffff880`018b84ac : 00000000`00000000 00000000`0000000e fffffa80`09df0010 fffffa80`0b4ad080 : nt!KiGeneralProtectionFault+0x10a
    fffff800`00b9b170 fffff880`018b53b7 : fffff880`019c89a0 00000000`00000000 fffff880`019c0000 fffffa80`019c0800 : tcpip!IppFragmentPackets+0x66c
    fffff800`00b9b290 fffff880`018b7805 : 00000000`00000000 00000000`00000009 fffff800`00b9b3c8 fffff800`00000000 : tcpip!IppDispatchSendPacketHelper+0x87
    fffff800`00b9b350 fffff880`018b5f43 : 00000000`00000011 00000000`00000000 fffffa80`00000014 00000000`00000000 : tcpip!IppPacketizeDatagrams+0x2d5
    fffff800`00b9b470 fffff880`018b93ae : fffffa80`0a37f0f0 fffff880`0170cf04 fffff880`019c89a0 fffffa80`09f2c580 : tcpip!IppSendDatagramsCommon+0x753
    fffff800`00b9b740 fffff880`01894e38 : fffffa80`09f2c580 fffffa80`0b401210 fffffa80`0b401210 fffffa80`0a37f0f0 : tcpip!IpNlpSendDatagrams+0x3e
    fffff800`00b9b780 fffff880`0189508b : fffffa80`0b272280 fffff880`0198d450 fffff800`00b9c0d0 00000000`00000000 : tcpip!UdpSendMessagesOnPathCreation+0x688
    fffff800`00b9bb00 fffff880`018955d5 : fffff800`00b9c030 fffffa80`08118900 00000000`00000001 fffffa80`07ef82f0 : tcpip!UdpSendMessages+0x1db
    fffff800`00b9bef0 fffff800`02eee668 : fffffa80`07b4c3f0 fffff800`00b9c038 00000000`00000000 fffff880`0170c892 : tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x15
    fffff800`00b9bf20 fffff880`01895668 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff800`00b9c000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!UdpTlProviderSendMessages+0x78
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    tcpip!IppFragmentPackets+66c
    fffff880`018b84ac 83802001000001  add     dword ptr [rax+120h],1
    
    SYMBOL_STACK_INDEX:  9
    
    SYMBOL_NAME:  tcpip!IppFragmentPackets+66c
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: hardware
    
    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
    
    BUCKET_ID:  X64_IP_MISALIGNED
    
    Followup: MachineOwner
    ---------
    
    
     
  4. Batuhan Altun

    Batuhan Altun New Member

    Joined:
    Jun 13, 2011
    Messages:
    6
    Likes Received:
    0
    Thanks, I will try,
    After today BSOD, I removed ram that I have install,
    We have two same notebook,
    my notebook have 2x2gb original rams, and 2x2gb kingston rams
    i removed the ram that i have install, i take the orijinal rams from other n53sn
    i install that rams to my notebook, so i have 4x2gb original rams,
    i install 2x2gb kingston ram to other notebook, it has 2x2gb kingston
    after this no bsod, but nobody know, maybe one hour later :D
    so now all rams same brand

    if there is a problem between orginal rams and kingston ram, memtest86 should find it, but it didnt,
    am i false?

    Sory about very bad english :)
     

Share This Page

Loading...