TechSpot

Bsod Error, Please Help Meeee!!!

By CRAZYBONE
Oct 8, 2005
  1. Every time I receive a blue bosd, this is the analysys of my memory.dmp. I need your help. My pc is new. What happens????


    Microsoft (R) Windows Debugger Version 6.5.0003.7
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\MEMORY.DMP]
    Kernel Complete Dump File: Full address space is available

    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
    Debug session time: Sat Oct 8 10:27:09.875 2005 (GMT+2)
    System Uptime: 0 days 0:39:49.458
    Loading Kernel Symbols
    ..........................................................................................................................................
    Loading unloaded module list
    ............
    Loading User Symbols
    ........................................................................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 8E, {c0000005, 80576b43, edbb5770, 0}

    *** WARNING: Unable to verify checksum for pavlsp.dll
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for pavlsp.dll -
    *** WARNING: Unable to verify checksum for emule.exe
    *** ERROR: Module load completed but symbols could not be loaded for emule.exe
    Probably caused by : hardware ( afd!AfdBind+2dc )

    Followup: MachineOwner
    ---------

    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
    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.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 80576b43, The address that the exception occurred at
    Arg3: edbb5770, Trap Frame
    Arg4: 00000000

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en "0x%08lx" hace referencia a la memoria en "0x%08lx". La memoria no se puede "%s".

    FAULTING_IP:
    nt!IopParseDevice+1e7
    80576b43 d021 shl byte ptr [ecx],1

    TRAP_FRAME: edbb5770 -- (.trap ffffffffedbb5770)
    ErrCode = 00000002
    eax=001f01ff ebx=84b579e8 ecx=0000bb40 edx=0000790a esi=84dd0548 edi=84fda9a0
    eip=80576b43 esp=edbb57e4 ebp=edbb58bc iopl=0 nv up ei pl nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
    nt!IopParseDevice+0x1e7:
    80576b43 d021 shl byte ptr [ecx],1 ds:0023:0000bb40=??
    Resetting default scope

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    MISALIGNED_IP:
    nt!IopParseDevice+1e7
    80576b43 d021 shl byte ptr [ecx],1

    LAST_CONTROL_TRANSFER: from 805b3642 to 80576b43

    STACK_TEXT:
    edbb58bc 805b3642 84e4b928 00000000 84dd0548 nt!IopParseDevice+0x1e7
    edbb5944 805afb23 00000000 edbb5984 00000240 nt!ObpLookupObjectName+0x56a
    edbb5998 8056a11d 00000000 00000000 bb5a3400 nt!ObOpenObjectByName+0xeb
    edbb5a14 8056aa94 842eeb78 02000000 edbb5bb8 nt!IopCreateFile+0x407
    edbb5a70 efb67483 842eeb78 02000000 edbb5bb8 nt!IoCreateFile+0x8e
    edbb5c24 efb6e2c7 8424de38 84d6d030 edbb5c58 afd!AfdBind+0x2dc
    edbb5c34 804eddf9 84f42030 842b2c18 806d02d0 afd!AfdDispatchDeviceControl+0x53
    edbb5c44 80573b3a 842b2cf4 84296798 842b2c18 nt!IopfCallDriver+0x31
    edbb5c58 805749c9 84f42030 842b2c18 84296798 nt!IopSynchronousServiceTail+0x60
    edbb5d00 8056d326 00000950 0000024c 00000000 nt!IopXxxControlFile+0x5e7
    edbb5d34 8053c808 00000950 0000024c 00000000 nt!NtDeviceIoControlFile+0x2a
    edbb5d34 7c91eb94 00000950 0000024c 00000000 nt!KiFastCallEntry+0xf8
    0012dc34 7c91d8ef 719d4f04 00000950 0000024c ntdll!KiFastSystemCallRet
    0012dc38 719d4f04 00000950 0000024c 00000000 ntdll!ZwDeviceIoControlFile+0xc
    0012dcf0 016b5434 00000950 0012dd58 00000010 mswsock!WSPBind+0x1ab
    WARNING: Stack unwind information not available. Following frames may be wrong.
    0012dd6c 004094e6 033f93e8 00000000 033ad660 pavlsp+0x5434
    0012dd84 00411b66 00000000 00000000 00000000 emule+0x94e6
    7c8092ac f7028b7f ac0f0462 90c318d0 90909090 emule+0x11b66
    7c8092b0 ac0f0462 90c318d0 90909090 8b55ff8b 0xf7028b7f
    7c8092b4 90c318d0 90909090 8b55ff8b 645756ec 0xac0f0462
    7c8092b8 90909090 8b55ff8b 645756ec 000018a1 0x90c318d0
    7c8092bc 8b55ff8b 645756ec 000018a1 08758b00 0x90909090
    7c8092c0 645756ec 000018a1 08758b00 c4a1f88b 0x8b55ff8b
    7c8092c4 00000000 08758b00 c4a1f88b 857c8836 0x645756ec


    FOLLOWUP_IP:
    afd!AfdBind+2dc
    efb67483 8945e4 mov [ebp-0x1c],eax

    SYMBOL_STACK_INDEX: 5

    FOLLOWUP_NAME: MachineOwner

    SYMBOL_NAME: afd!AfdBind+2dc

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    STACK_COMMAND: .trap ffffffffedbb5770 ; kb

    MODULE_NAME: hardware

    IMAGE_NAME: hardware

    FAILURE_BUCKET_ID: IP_MISALIGNED

    BUCKET_ID: IP_MISALIGNED

    Followup: MachineOwner
    ---------
     
  2. cpc2004

    cpc2004 TS Evangelist Posts: 2,044

    Hi,

    This is hardware problem. IP_Misaligned (Instruction Misaligned) is usually caused by faulty memory.

    Suggestion
    1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
    2. Reseat the memory stick to another memory slot
    3. Downclock the ram
    4. Clean the dust inside the computer case
    5. Make sure that the ram is compatible to the motherboard
    If it still crashes, diagnostic which memory stick is faulty
    1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
    2. If you have only one memory stick, replace the ram
     
  3. CRAZYBONE

    CRAZYBONE TS Rookie Topic Starter

    I have diagnostics with memtest the memory and its ok, i donĀ“t know what to do.
     
  4. cpc2004

    cpc2004 TS Evangelist Posts: 2,044

    Some faulty ram can pass memtest and this is the reason why I don't recommend to use memtest. Do you follow any of my instruction at my previous post?
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.