Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD on brand new HP w/ W7 64 bit

27 Nov 2010   #1

Windows 7 Home Premium 64-bit
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.
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:

Read our privacy statement online:

If the online privacy statement is not available, please read our privacy statement offline:

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 System SpecsSystem Spec
28 Nov 2010   #2

Windows 7 Ultimate x64 SP1

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 ->

Also update your Realtek NIC driver -> Realtek

Then we'll see if the problem persist.

*                                                                             *
*                        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                                    *
*                                                                             *

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
        .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)
kb will then show the corrected stack.
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000006f8
Arg4: fffff80002c4fec0

Debugging Details:






LAST_CONTROL_TRANSFER:  from fffff80002c86ca9 to fffff80002c87740

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


fffff800`02c85172 90              nop


SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  ntkrnlmp.exe


FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

Followup: MachineOwner
My System SpecsSystem Spec
28 Nov 2010   #3

Windows 7 Home Premium 64-bit

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 System SpecsSystem Spec


 BSOD on brand new HP w/ W7 64 bit

Thread Tools

Similar help and support threads
Thread Forum
BSOD on brand new pc!!
Howdy, I've just assembled a pc for a friend of mine, installed Windows 7 Ultimate, installed everything neccesary, and then when I was defragmenting the C drive with Deffraggler I got a stop screen and had to reboot. I attach here the minidump and a xml with all the info for this system (captured...
BSOD Help and Support
Brand New PC, keep getting BSOD :(
I'll try and make this quick. Bought a new Dell Inspiron not long ago. In the span of a week or two i literally got over 10 BSODs, it's usually when I'm moving chunks of music of movies from one hardrive to another. So Dell told me there must be a hardware failure, they came round and...
BSOD Help and Support
Brand new pc _ bsod
Is Windows 7 . . . x64 ? windows 7 home premiuim 64 bit was installed originally and came preinstalled - all bought 5 days ago i reinstalled windows 7 about 2 hours ago. Hi all.
BSOD Help and Support
Source Windows Summary Shut down unexpectedly Date ‎31/‎07/‎2010 8:34 PM Status
BSOD Help and Support
Brand new computer, Brand new windows 7.. no wireless?
I just unpacked my custom build and got it turned on.. went to try and get the internet working, and for the life of me.. i can't figure it out. I don't even have a little wireless bar down in the right hand corner. when i try to connect to a network in network and sharing center, it wants me to...
Network & Sharing

Our Sites

Site Links

About Us

Find 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 17:16.
Twitter Facebook Google+