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 2 mo. old PC

29 Nov 2010   #1
Sirfapalot

Windows 7 Professional 64bit
 
 
BSOD on 2 mo. old PC

- x86 (32-bit) or x64 ? Its x64
- the original installed OS on the system? Yes
- an OEM or full retail version? OEM


- What is the age of system (hardware)? Got my PC probably early-mid Oct, so it should be about 2 mo old
- What is the age of OS installation (have you re-installed the OS?)? Same age as PC, no reinstallation

I'm just being really cautious, since I got a BSOD so soon which is why I posted here. I lost my old PC to hard drive failure (due to Power surge prbly) and lost all my data, so now I'm very paranoid.


My System SpecsSystem Spec
.
30 Nov 2010   #2
wish

Windows 7 Ultimate x64 SP1
 
 

Hello,
I'm pretty sure Zone Alarm that causing your problem.
Uninstall Zone ALarm completely or use this tools if you have problem uninstalling ZA → http://download.zonealarm.com/bin/fr...cpes_clean.exe

After that turn on your Windows Firewall.

Also remove Alcohol or Daemon software because they use sptd.sys which is notorious for causing BSOD in windows 7.
Uninstall sptd.sys with this tools --> DuplexSecure - Downloads
Then for alternative software, you may use MagicIso.

Then we'll see how it goes.

Log
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff80002ecf1df}

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

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

0: 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: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002ecf1df

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 fffff80002ec8ca9 to fffff80002ec9740

STACK_TEXT:  
fffff800`00ba4d28 fffff800`02ec8ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`02ec7172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff800`02ecf1df : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`091f3000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SepAccessCheck+0x1cf


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`02ec7172 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 System SpecsSystem Spec
30 Nov 2010   #3
Sirfapalot

Windows 7 Professional 64bit
 
 

Thanks.

I'll uninstall Zone alarm.

Though I'm not sure about Daemon tools. For rare Jap Eroges I usually need to "acquire" them and they usually need Daemon tools to work. Though I do use MagicISO (which is quite convenient since the images stay mounted on the next time to you start windows )

Also, I'm running Windows 7 in jap locale. Could that be the reason zone alarm caused the problem?
My System SpecsSystem Spec
.

30 Nov 2010   #4
wish

Windows 7 Ultimate x64 SP1
 
 

Nope, Zone Alarm is also well known as BSOD maker with different Locale id.
Just uninstall it then we'll see if the problem persist
My System SpecsSystem Spec
Reply

 BSOD on 2 mo. old PC




Thread Tools



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 11:27.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App