BSOD - Possible Memory issues?

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Jasperrr, Jan 4, 2011.

  1. Jasperrr

    Jasperrr New Member

    Joined:
    Jan 4, 2011
    Messages:
    2
    Likes Received:
    0
    After opening some corrupt software two nights ago, my task manager got disabled and my computer started to lock up. I immediately rebooted in Safe Mode and ran HijackThis to remove any suspicious startup programs.
    After doing this, I rebooted into windows and logged in. However, shortly after logging in I received an IRQL_NOT_LESS_OR_EQUAL BSOD, I then rebooted into safe mode and once again got the BSOD. I then decided to remove one of my two RAM sticks but I still got the error, same thing happened when I tried using only the second RAM stick.

    I then decided to boot into repair mode and ran the hardware test which gave me no errors. Afterwards I logged in to windows again and this time I received a SYSTEM_SERVICE_EXCEPTION BSOD instead of the IRQL error. I decided to once again try safe mode and this time it worked and I was able to acces the dmp files.

    However, as we speak. My computer has broke down again thus I cannot attach any CPU-Z screenshots atm. I did attach my collection of dumpfiles.

    View attachment minidumps.zip
     
    #1 Jasperrr, Jan 4, 2011
    Last edited: Jan 4, 2011
  2. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Not exactly sure what your options might be if you can't even boot any longer even in safemode but your most recent dump files indicate that the problem is with ataport.sys which is probably being cause by the presence of Daemon Tools and it's driver sptd.sys. You would probably need to start there by uninstalling Daemon Tools and it's driver DuplexSecure - FAQ
    Additionally there are a couple old drivers
    hardlock.sys 11/20/2006
    and
    aksdf.sys 12/13/2006
    both associated with a Software Product called Alladin Knowledge Systems you may want to consider removing that as well.
    Also uninstall LogMeIn for the time being
    And see if Logitech has any updates for your mouse and keyboard
    L8042Kbd.sys and LMouFilt.sys both dated 6/17/2009, they may have something more current, if not don' worry about it for now.
     
  3. Captain Jack

    Captain Jack Extraordinary Member

    Joined:
    Mar 6, 2010
    Messages:
    1,952
    Likes Received:
    139
    Hello and Welcome !

    Seems like your Marvell Yukon Ethernet Controller i.e. yk62x64.sys is casung the crash. See if you could uninstall it completely and reboot the System download a fresh version Marvell: Support rest follow Trouble's excellent suggestions.

    Bugcheck:

    Code:
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa80047b4060, Physical Device Object of the stack
    Arg3: fffff8000453c4d8, Functional Device Object of the stack
    Arg4: fffffa8004f81990, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IRP_ADDRESS:  fffffa8004f81990
    
    DEVICE_OBJECT: fffffa8004f0f050
    
    DRIVER_OBJECT: fffffa8004ecb2e0
    
    IMAGE_NAME:  yk62x64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  49a2ba83
    
    MODULE_NAME: yk62x64
    
    FAULTING_MODULE: fffff88004f92000 yk62x64
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002f3fe23 to fffff80002ed0f00
    
    STACK_TEXT:  
    fffff800`0453c488 fffff800`02f3fe23 : 00000000`0000009f 00000000`00000003 fffffa80`047b4060 fffff800`0453c4d8 : nt!KeBugCheckEx
    fffff800`0453c490 fffff800`02edcfa6 : fffff800`0453c620 fffff800`0453c620 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
    fffff800`0453c530 fffff800`02edc326 : fffffa80`05834200 fffffa80`05834200 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`0453c5a0 fffff800`02edce7e : 000006bd`a6f2870a fffff800`0453cc18 00000000`02d4f23c fffff800`0304ca08 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`0453cbf0 fffff800`02edc697 : 000001fa`7bde2ec6 000001fa`02d4f23c 000001fa`7bde2e00 00000000`0000003c : nt!KiTimerExpiration+0x1be
    fffff800`0453cc90 fffff800`02ed96fa : fffff800`03049e80 fffff800`03057c40 00000000`00000000 fffffa80`039af0a0 : nt!KiRetireDpcList+0x277
    fffff800`0453cd40 00000000`00000000 : fffff800`0453d000 fffff800`04537000 fffff800`0453cd00 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_yk62x64.sys
    
    BUCKET_ID:  X64_0x9F_IMAGE_yk62x64.sys
    
    Followup: MachineOwner
    
     

Share This Page

Loading...