BSOD On Dell XPS 410

  1. Hi all I have been having some major problems with this Dell XPS 410. I bought new RAM for it and its still giving me some odd issues. I have included a mini dump. Sometimes it boots up fine, sometimes it says I need to insert the CD and do a repair, sometimes I get to the windows screen and it restarts right away, sometimes it turns on and just stays with an Orange Screen.

    I had bought new RAM for the unit that has made it work better but I am still having some issues with it.

    0x0000008E-ks.sys
    &
    0x0000007E-atapi.sys

    I hope someone can help me out. I am running Windows XP SP 3. I was thinking I might need a new power supply. I have also tried installing the OS on another hard drive still have issues.

    Attached Files:

  2. Malnutrition

    Malnutrition Newcomer, in training

    Code:
     
    [SIZE=11px][COLOR=#000000]Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp3_qfe.130503-0418
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Wed Jul  3 18:04:24.781 2013 (UTC - 4:00)
    System Uptime: 0 days 0:00:43.522
    *******************************************************************************
    *																			 *
    *						Bugcheck Analysis									*
    *																			 *
    *******************************************************************************
    
    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    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: f6e1f04f, The address that the exception occurred at
    Arg3: b8b83644, Trap Frame
    Arg4: 00000000
    
    Debugging Details:
    ------------------
    
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
    
    FAULTING_IP: 
    ks!FindAndReferenceCreateItem+1a
    f6e1f04f 833800		  cmp	 dword ptr [eax],0
    
    TRAP_FRAME:  b8b83644 -- (.trap 0xffffffffb8b83644)
    ErrCode = 00000000
    eax=00000000 ebx=86923008 ecx=e2acc77a edx=869fb488 esi=e22c83b8 edi=00000000
    eip=f6e1f04f esp=b8b836b8 ebp=b8b836c8 iopl=0		 nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000			 efl=00010202
    ks!FindAndReferenceCreateItem+0x1a:
    f6e1f04f 833800		  cmp	 dword ptr [eax],0	ds:0023:00000000=????????
    Resetting default scope
    
    DEFAULT_BUCKET_ID:  DRIVER_FAULT
    
    BUGCHECK_STR:  0x8E
    
    PROCESS_NAME:  stsystra.exe
    
    LAST_CONTROL_TRANSFER:  from f6e1ef9f to f6e1f04f
    
    STACK_TEXT:  
    b8b836c8 f6e1ef9f e2acc77a 0000004c 86923008 ks!FindAndReferenceCreateItem+0x1a
    b8b836f0 804ef1f9 86efa748 869fb488 869fb488 ks!DispatchCreate+0x7d
    b8b83700 80583232 8695dac8 86969fd4 b8b83898 nt!IopfCallDriver+0x31
    b8b837e0 805bf4bc 8695dae0 00000000 86969f30 nt!IopParseDevice+0xa12
    b8b83858 805bba48 00000000 b8b83898 00000240 nt!ObpLookupObjectName+0x53c
    b8b838ac 80576051 00000000 00000000 00005800 nt!ObOpenObjectByName+0xea
    b8b83928 805769c8 b8b83a34 c0100200 b8b839cc nt!IopCreateFile+0x407
    b8b83984 b911c80a b8b83a34 c0100200 b8b839cc nt!IoCreateFile+0x8e
    b8b839f4 b911c721 e380c568 b8b83a34 00000000 wdmaud!OpenDevice+0x66
    b8b83a1c b9122a19 b8b83a34 b8b83a38 00000000 wdmaud!OpenSysAudio+0x39
    b8b83a3c b911dd72 86e93760 86638300 86ab5a70 wdmaud!kmxlOpenSysAudio+0x1e
    b8b83a5c 804ef1f9 869e09c0 86e93750 86e93750 wdmaud!SoundDispatchCreate+0x86
    b8b83a6c 80583232 86ec1c00 8665c9dc b8b83c04 nt!IopfCallDriver+0x31
    b8b83b4c 805bf4bc 86ec1c18 00000000 8665c938 nt!IopParseDevice+0xa12
    b8b83bc4 805bba48 00000000 b8b83c04 00000040 nt!ObpLookupObjectName+0x53c
    b8b83c18 80576051 00000000 00000000 632d1801 nt!ObOpenObjectByName+0xea
    b8b83c94 805769c8 013ee750 c0100080 013ee6f0 nt!IopCreateFile+0x407
    b8b83cf0 805790d2 013ee750 c0100080 013ee6f0 nt!IoCreateFile+0x8e
    b8b83d30 805417e8 013ee750 c0100080 013ee6f0 nt!NtCreateFile+0x30
    b8b83d30 7c90e514 013ee750 c0100080 013ee6f0 nt!KiSystemServicePostCall
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    013ee748 00000000 00000000 00000000 00000000 0x7c90e514
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    ks!FindAndReferenceCreateItem+1a
    f6e1f04f 833800		  cmp	 dword ptr [eax],0
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  ks!FindAndReferenceCreateItem+1a
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: ks
    
    IMAGE_NAME:  ks.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  48025c12
    
    FAILURE_BUCKET_ID:  0x8E_ks!FindAndReferenceCreateItem+1a
    
    BUCKET_ID:  0x8E_ks!FindAndReferenceCreateItem+1a
    
    Followup: MachineOwner
    ---------
    [/COLOR][/SIZE]
    








    Possible Causes to your crashes.

    Code:
    afd.sys Ancillary Function Driver for WinSock
    aswSP.SYS avast! Self Protection Driver
    ks.sys Kernel CSA Library 
    At this point it looks like Avast may be at fault here.

    So go ahead and do a clean install of Avast for me please.
    http://www.avast.com/uninstall-utility

    Also Can I see the logs below from your machine.



    Download Security Check by screen317 from here.
    • Save it to your Desktop.
    • Double click SecurityCheck.exe and follow the onscreen instructions inside of the black box.
    • A Notepad document should open automatically called checkup.txt; please post the contents of that document.

    Please download MINITOOLBOX and run it.

    Checkmark following boxes:



    Flush DNS
    Reset FF proxy Settings
    Reset Ie Proxy Settings
    Report IE Proxy Settings
    Report FF Proxy Settings
    List content of Hosts
    List IP configuration
    List Winsock Entries
    List last 10 Event Viewer log
    List Installed Programs
    List Users, Partitions and Memory size
    List Devices (problems only)



    Click Go and post the result.
  3. Malnutrition

    Malnutrition Newcomer, in training

    Any luck with the issue?


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.