BSOD 7f on Win 7 Home Premium 64bit.

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

  1. Petroc

    Petroc New Member

    Joined:
    Jul 3, 2011
    Messages:
    4
    Likes Received:
    0
    Hi all, I'd appreciate any and all help i can get.
    I just purchased a new Fujitsu P770 i3-330, running Win 7 Home Premium 64bit. Its installed with SP1.
    I keep getting BSOD Bcode 7f out of the blue :p

    Cant figure it out and its driving me nuts.
    I'm attaching info about the memory im using, just in case thats an issue.
    Also attached are the dmp files.

    Please help!! Im at my wits end and cant get work done.
    :(
    CPU-Z.
    CPU-Z2.

    Cheers all and god bless.

    Petroc.
     

    Attached Files:

    #1 Petroc, Jul 3, 2011
    Last edited: Jul 3, 2011
  2. kaos

    kaos Senior Member

    Joined:
    May 9, 2011
    Messages:
    1,747
    Likes Received:
    33
    Hi,

    This is the bug check analysis

    Code:
    
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    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: 0000000080050031
    Arg3: 00000000000006f8
    Arg4: 0000000001802e6f
    Debugging Details:
    ------------------
    
    BUGCHECK_STR:  0x7f_10
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  Picasa3.exe
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff80002e8a2a9 to fffff80002e8ad00
    STACK_TEXT:  
    fffff880`02c0dad8 fffff800`02e8a2a9 : 00000000`0000007f 00000000`00000010 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
    fffff880`02c0dae0 fffff800`02e891ea : 00000000`08ca99e8 fffff880`02c0dca0 00000000`08ca9a30 00000000`05cb2318 : nt!KiBugCheckDispatch+0x69
    fffff880`02c0dc20 00000000`01802e6f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiFloatingErrorFault+0x16a
    00000000`08ca96e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1802e6f
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!KiFloatingErrorFault+16a
    fffff800`02e891ea 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:  4d9fdd5b
    FAILURE_BUCKET_ID:  X64_0x7f_10_nt!KiFloatingErrorFault+16a
    BUCKET_ID:  X64_0x7f_10_nt!KiFloatingErrorFault+16a
    Followup: MachineOwner
    ---------
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    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: 0000000080050031
    Arg3: 00000000000006f8
    Arg4: 0000000001802e6f
    Debugging Details:
    ------------------
    
    BUGCHECK_STR:  0x7f_10
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  Picasa3.exe
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff80002e8a2a9 to fffff80002e8ad00
    STACK_TEXT:  
    fffff880`02c0dad8 fffff800`02e8a2a9 : 00000000`0000007f 00000000`00000010 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
    fffff880`02c0dae0 fffff800`02e891ea : 00000000`08ca99e8 fffff880`02c0dca0 00000000`08ca9a30 00000000`05cb2318 : nt!KiBugCheckDispatch+0x69
    fffff880`02c0dc20 00000000`01802e6f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiFloatingErrorFault+0x16a
    00000000`08ca96e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1802e6f
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!KiFloatingErrorFault+16a
    fffff800`02e891ea 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:  4d9fdd5b
    FAILURE_BUCKET_ID:  X64_0x7f_10_nt!KiFloatingErrorFault+16a
    BUCKET_ID:  X64_0x7f_10_nt!KiFloatingErrorFault+16a
    Followup: MachineOwner
    ---------
    
    
    Code:
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    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: 0000000080050031
    Arg3: 00000000000006f8
    Arg4: 000000005cc5e914
    Debugging Details:
    ------------------
    
    BUGCHECK_STR:  0x7f_10
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  iexplore.exe
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff80002e8f2a9 to fffff80002e8fd00
    STACK_TEXT:  
    fffff880`086a7358 fffff800`02e8f2a9 : 00000000`0000007f 00000000`00000010 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
    fffff880`086a7360 fffff800`02e8e1ea : 00000000`00000067 fffff880`086a7520 fffff960`0010a31c 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`086a74a0 00000000`5cc5e914 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiFloatingErrorFault+0x16a
    00000000`02fc561c fffff800`02e872d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5cc5e914
    fffff880`086a7880 fffff900`00000003 : 00000000`00000000 00000000`00000000 fffff880`00000700 fffffa80`08263060 : nt!KiCallUserMode
    fffff880`086a7888 00000000`00000000 : 00000000`00000000 fffff880`00000700 fffffa80`08263060 fffff880`086a7db0 : 0xfffff900`00000003
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!KiFloatingErrorFault+16a
    fffff800`02e8e1ea 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:  4d9fdd5b
    FAILURE_BUCKET_ID:  X64_0x7f_10_nt!KiFloatingErrorFault+16a
    BUCKET_ID:  X64_0x7f_10_nt!KiFloatingErrorFault+16a
    Followup: MachineOwner
    ---------
     
    
    

    This bugcheck comes from hardware issues, mainly memory if its miss matched

    If you have different types of RAM / brands make sure you take them all out and only put the same,m branded ram back in, test the pc,

    MAE SURE, you have all drivers are updated, service packs, internet explorer etc.,
    thenj

    download a program called Memtest86+, take all sticks of ram out, Test one by 1 in the first slot, Let the program run for 7 passes ( the pass count in the middle ) or untill it errors, If you get any errors , take it out to the side for the time being and test the next stick
     
  3. Petroc

    Petroc New Member

    Joined:
    Jul 3, 2011
    Messages:
    4
    Likes Received:
    0
    Hi Kaos thanks for responding.

    I'd also looked for advice elsewhere, and what ive done so far seems to have worked. So im going to share with everyone here. These are what have helped me.

    The first problem was that i assumed the BCCode 7f pointed to just one problem. However i've since learnt that its just a general indication of where things go wrong, not what caused it.

    1) First, it appears that my additional RAM was giving me problems. I took it out, cleaned it carefully with a soft brush, as well as the RAM slot. Although i couldn't see any dust, something must have been clogging up the contact points. After i had done this and reinserted the RAM, there was a HUGE decrease in number of crashes.

    2) Second, I had assumed that the vendor had provided me with all the appropriate drivers installed. Not so. I had to go to fujitsu website and carefully go through the list of drivers provided by them. Although my notebook came with an intel video accelerator, i couldnt use the driver from the intel website. Fujitsu had a customised driver for my notebook. I updated this driver.

    These 2 steps have solved almost all my BSODs.

    The others appear to be caused by specific applications. I think the problem lies with compatibility of 64 bit apps.

    For example Picasa 3.8 which some have said on other forums should work seamlessly with win 7 64bit, i find not to be the case. Many others also face similar problems as me so i know im not alone. As a workaround, i use Picasa with the compatibility feature provided with win 7. I get a bunch of error messges before i can use the app, but the app is usable.

    For video editing software, there was a problem with the codec apps. I have a workaround for this too, from another forum.

    All in all, im now zipping along.

    Hope others can learn from my experience.

    Cheers.

    Petroc
     

Share This Page

Loading...