Blue screen

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

  1. ohadb

    ohadb New Member

    Joined:
    Jul 4, 2011
    Messages:
    8
    Likes Received:
    0
    Hi, I just got new windows 7 professional 64 bit on Lenovo W520 laptop
    I'm getting these blue screens.
    Can anyone help?

    Thanks,
     

    Attached Files:

  2. nmsuk

    nmsuk Windows Forum Admin
    Staff Member Premium Supporter

    Joined:
    Sep 7, 2009
    Messages:
    2,694
    Likes Received:
    194
    Hi sorry it's taken so long to get back to you. The latest BSOD you've received was caused by deamon tools. Can you uninstall it and see if that solves the problem. If you need DT to mount ISO images may I suggest virtualclonedrive as I've been using that for awhile with no problems whatsoever.
     
  3. kaos

    kaos Senior Member

    Joined:
    May 9, 2011
    Messages:
    1,747
    Likes Received:
    33
    virtual drives can be a pain, also you need to remove SPTD.Sys, This driver is a known issue,

    if you dont know how to remove this then i can help you or if your comfortable removing this properly then im cool :)
     
  4. zigzag3143

    zigzag3143 Honorable Member
    Microsoft MVP

    Joined:
    Jun 2, 2009
    Messages:
    812
    Likes Received:
    115
    As previously stated sptd.sys needs to be updated. You can do that here

    Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.

    They use a driver, found in your dmp,sptd.sys, that is notorious for causing BSODs.

    Use this SPTD uninstaller DuplexSecure - Downloads

    when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.


    Let us know if you need further assistance/.


    Ken J
     
  5. ohadb

    ohadb New Member

    Joined:
    Jul 4, 2011
    Messages:
    8
    Likes Received:
    0
    Thank you very much for the replays
    I uninstalled the deamon tool but after a day I got another blue screen :-(
    Attched is the dump, Is it the same problem?

    I Just used the DuplexSecure but I still don't know if it helps.

    Thanks,
    Ohad
     

    Attached Files:

  6. nmsuk

    nmsuk Windows Forum Admin
    Staff Member Premium Supporter

    Joined:
    Sep 7, 2009
    Messages:
    2,694
    Likes Received:
    194
    Could you supply your memory settings in the bios please.
     
  7. Captain Jack

    Captain Jack Extraordinary Member

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

    Seems like the crash has caused by driver cbfs3.sys which belongs to Jungledisk for cloudbased storage and Jungledisk uses the Eldos Callback system for something in Jungledisk. I found this support article Blue Screen in Windows : Jungle Disk Support that will help you in resolving it. If that fails I would recommend to contact their support Jungle Disk Support


    Code:
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 000000000000014c, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002e8ee88, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030af100
     000000000000014c 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KiTryUnwaitThread+28
    fffff800`02e8ee88 f0480fba6b4000  lock bts qword ptr [rbx+40h],0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  QTAgent32.exe
    
    TRAP_FRAME:  fffff8800ea84480 -- (.trap 0xfffff8800ea84480)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000600508 rbx=0000000000000000 rcx=fffff88003389180
    rdx=fffffa80071a6ab0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002e8ee88 rsp=fffff8800ea84610 rbp=0000000000000000
     r8=0000000000000100  r9=0000000000000000 r10=fffffa80071a6ab0
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!KiTryUnwaitThread+0x28:
    fffff800`02e8ee88 f0480fba6b4000  lock bts qword ptr [rbx+40h],0 ds:02b0:00000000`00000040=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002e7f2a9 to fffff80002e7fd00
    
    STACK_TEXT:  
    fffff880`0ea84338 fffff800`02e7f2a9 : 00000000`0000000a 00000000`0000014c 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`0ea84340 fffff800`02e7df20 : 00000000`0663fd01 00000000`0663ee10 ffffffff`ffffffff 00000000`0000010c : nt!KiBugCheckDispatch+0x69
    fffff880`0ea84480 fffff800`02e8ee88 : fffffa80`06e1d3a0 00000000`00000001 fffffa80`096f5800 00000000`00000001 : nt!KiPageFault+0x260
    fffff880`0ea84610 fffff800`02e84038 : fffff880`0ea846f8 00000000`00000000 00000000`00000000 fffff880`03389180 : nt!KiTryUnwaitThread+0x28
    fffff880`0ea84670 fffff880`04adb4b7 : fffff880`00000000 fffff880`00000001 00000000`00000000 00000001`00060080 : nt!KeSetEvent+0x446
    fffff880`0ea846e0 fffff880`00000000 : fffff880`00000001 00000000`00000000 00000001`00060080 fffffa80`071a6ab0 : cbfs3+0x14b7
    fffff880`0ea846e8 fffff880`00000001 : 00000000`00000000 00000001`00060080 fffffa80`071a6ab0 fffff880`04afae5b : 0xfffff880`00000000
    fffff880`0ea846f0 00000000`00000000 : 00000001`00060080 fffffa80`071a6ab0 fffff880`04afae5b 00000000`c0000022 : 0xfffff880`00000001
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    cbfs3+14b7
    fffff880`04adb4b7 ??              ???
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  cbfs3+14b7
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: cbfs3
    
    IMAGE_NAME:  cbfs3.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d99c5a2
    
    FAILURE_BUCKET_ID:  X64_0xA_cbfs3+14b7
    
    BUCKET_ID:  X64_0xA_cbfs3+14b7
    
    Followup: MachineOwner
    ---------
    
    7: kd> lmvm cbfs3
    start             end                 module name
    fffff880`04ada000 fffff880`04b2d000   cbfs3    T (no symbols)           
        Loaded symbol image file: cbfs3.sys
        Image path: \??\C:\Windows\system32\drivers\cbfs3.sys
        Image name: cbfs3.sys
        Timestamp:        Mon Apr 04 18:50:34 2011 (4D99C5A2)
        CheckSum:         0005DCD9
        ImageSize:        00053000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    
     
     
    2 people like this.
  8. ohadb

    ohadb New Member

    Joined:
    Jul 4, 2011
    Messages:
    8
    Likes Received:
    0
    Hi,
    What do you mean BIOS memory configuration?

    this is my BIOS and systemInformation?
    What else do you need?

    Thanks,
     

    Attached Files:

Share This Page

Loading...