Random BSOD occurances

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

  1. mikbor

    mikbor New Member

    Joined:
    Jun 13, 2011
    Messages:
    2
    Likes Received:
    0
    I have just bought a refurbished laptop and I began getting BSOD when setting up.
    At first it only occurred when I was transferring large files. After some work I fixed that, but I am also getting more or less random BSODs as well.
    I ran the windows hard drive check and memtest86+ and both passed.
    I have attached the DxDiag and 2 minidumps (33431 is the most recent crash).

    Please help.

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.768.3
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 7f
    BCP1: 0000000000000010
    BCP2: 0000000080050033
    BCP3: 00000000000006F8
    BCP4: 00000000693D6007
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1
     

    Attached Files:

  2. Captain Jack

    Captain Jack Extraordinary Member

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

    Seems like the causes of crashes are random so more likely it could be some Hardware that's causing the system to crash. Go follow this link Hardware Diagnostic | Captain Debugger and run a complete Hardware Diagnostic

    If your Overclocking please reset to default settings. Uninstall Avast and run the removal tool. (IMP)

    Code:
    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000010, EXCEPTION_NPX_ERROR
    Arg2: 0000000080050033
    Arg3: 00000000000006f8
    Arg4: 000000006953f4b2
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x7f_10
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  iTunes.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002cc2c69 to fffff80002cc3700
    
    STACK_TEXT:  
    fffff880`0857ead8 fffff800`02cc2c69 : 00000000`0000007f 00000000`00000010 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
    fffff880`0857eae0 fffff800`02cc1baa : fffffa80`049a1b60 00000000`0000074c 00000000`00000000 fffffa80`08f38320 : nt!KiBugCheckDispatch+0x69
    fffff880`0857ec20 00000000`6953f4b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiFloatingErrorFault+0x16a
    00000000`0df7f90c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6953f4b2
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiFloatingErrorFault+16a
    fffff800`02cc1baa 90              nop
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!KiFloatingErrorFault+16a
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34
    
    FAILURE_BUCKET_ID:  X64_0x7f_10_nt!KiFloatingErrorFault+16a
    
    BUCKET_ID:  X64_0x7f_10_nt!KiFloatingErrorFault+16a
    
    Followup: MachineOwner
     

Share This Page

Loading...