BSOD on brand new HP w/ W7 64 bit


  1. Posts : 2
    Windows 7 Home Premium 64-bit
       #1

    BSOD on brand new HP w/ W7 64 bit


    My two week old HP laptop is having issues. I have received the BSOD 2-3 times and a black screen, straight to restart once. Here is the most recent error and attached dmp files.

    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: 0000000000000008
    BCP2: 0000000080050033
    BCP3: 00000000000006F8
    BCP4: FFFFF80002C86EC0
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\112710-25724-01.dmp
    C:\Users\jcmontag\AppData\Local\Temp\WER-46347-0.sysdata.xml

    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt


    I just bought this computer and believe that it is still under warranty. So, if it is a hardware issue, I hopefully could get it replaced if I act quickly. Fingers crossed that it is nothing serious!

    Really appreciate the help! Thanks
      My Computer


  2. Posts : 507
    Windows 7 Ultimate x64 SP1
       #2

    Hello,
    By looking at debugger pattern, It seems the crash was caused by Zone Alarm.
    Try to uninstall Zone ALarm completely or use this tools if you have problem uninstalling ZA -> http://download.zonealarm.com/bin/fr...cpes_clean.exe

    Also update your Realtek NIC driver -> Realtek

    Then we'll see if the problem persist.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {8, 80050033, 6f8, fffff80002c4fec0}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    
    Followup: MachineOwner
    ---------
    
    3: 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: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050033
    Arg3: 00000000000006f8
    Arg4: fffff80002c4fec0
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x7f_8
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002c86ca9 to fffff80002c87740
    
    STACK_TEXT:  
    fffff880`02fd9ce8 fffff800`02c86ca9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
    fffff880`02fd9cf0 fffff800`02c85172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`02fd9e30 fffff800`02c4fec0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff880`02ff5ee0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiDoubleFaultAbort+b2
    fffff800`02c85172 90              nop
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    
    BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    
    Followup: MachineOwner
      My Computer


  3. Posts : 2
    Windows 7 Home Premium 64-bit
    Thread Starter
       #3

    Thanks! I uninstalled Zonealarm and updated the drivers. The crashes have been sporadic as to when they occur, but i will monitor the situation and post any further crashes.

    Thank you again for the help!
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:27.
Find Us