HELP! Having a BSOD and sudden restart in my newly laptop!

[eantham]

Hello, I just bought my HP g4-1025tx 3 weeks back and since the initial week after i bought. It keep restart and i personally thought this is something normal but the more frequent it happen, the more weird it is.

I have no idea of how to solve it. This is what has been shown in the report:


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

Additional information about the problem:
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050033
BCP3: 00000000000406F8
BCP4: FFFFF80002E48EB0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\052011-24897-01.dmp
C:\Users\Tham nyap Fu\AppData\Local\Temp\WER-52556-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

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


I wish someone can help me on this.May I know what are those further detailed information or steps required in order to solve it? your work is greatly appreciated.

http://cid-21d9c51ea280f5d4.office.live.com/self.aspx/.Public/Posting -eantham.zip

Thanks you!

 

[yowanvista]

Please post the full report
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[eantham]

Thanks yowanvista, Im done and waiting for the helps, thanks~

 

[yowanvista]

A Zone Alarm software probably Zone Alarm Firewall is the cause, please remove it from your system
Use the Removal Tool

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050033, 406f8, fffff80002e9feb0}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )


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: 00000000000406f8
Arg4: fffff80002e9feb0

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 fffff80002ed6ca9 to fffff80002ed7740

STACK_TEXT:  
fffff800`00ba4d28 fffff800`02ed6ca9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`02ed5172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff800`02e9feb0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0bedcb10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`02ed5172 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:  4cc791bd

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

Followup: MachineOwner
---------

 

[eantham]

Thanks yowanvista, hopefully it won't appear again. Is there any other way to trigger the blue screen or just wait for it to happen again?

 

[yowanvista]

Thanks yowanvista, hopefully it won't appear again. Is there any other way to trigger the blue screen or just wait for it to happen again?

Wait for it to occur again if it does

 

[eantham]

Alright, really thanks and appreciate for the helps. Till now it havent appear, hehe