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: Win 7 Intermittent Crashes

20 Jul 2011   #1

 
 
Win 7 Intermittent Crashes

Hey Guys,

**Files now attached per forum guidelines**

I have been having this issue for a while now and can not for the life of me figure it out. Basically my main PC lives in another room and I remote into it every day. Every night, however, the system bluescreens (or at least, that's what it tells me) and restarts. I have gone through my event viewer and everything actually seems ok (no reported system or application issues - hell, there isn't even a jump in time when it restarts), and in addition, I have removed all non-system-essential services from starting at all, but the issue persists. I have tested my memory and disks for any bad sectors. I had thought that the system may have been getting too hot, amongst the dinosaur power-sucking heat-generating *things* my roommates like to call servers, but it seems to be running at a steady 16 degrees C.

My basic system config is Corsair 16GB DDR3, 2TB 7200 seagate, Win 7 U x64, Asus P55A-UD3R mb, i7 860 @ 2.8, Bitlocker enabled.

This is the error I get when I log on:

Quote:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 3081

Additional information about the problem:
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000006F8
BCP4: FFFFF80003041E88
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\072011-47736-01.dmp
C:\Users\root\AppData\Local\Temp\WER-76305939-0.sysdata.xml
Any help would be greatly appreciated!!!

My System SpecsSystem Spec
20 Jul 2011   #2

Windows 8.1 Pro x64
 
 

My System SpecsSystem Spec
20 Jul 2011   #3

Windows 7 Ultimate x86
 
 

Well the error code gives me this:

STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Quote:
0x00000008, or Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault:
A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault. If you think this overview has occurred, use !thread to determine the stack limits, and then use kb (Display Stack Backtrace) with a large parameter (for example, kb 100) to display the full stack.
A hardware problem.
I'd say you follow these instructions so we get some more material to go on

http://www.sevenforums.com/crashes-d...tructions.html

-DG
My System SpecsSystem Spec
.


20 Jul 2011   #4

 
 

Hey Guys,

Please find these files attached in the first post. I have removed the hosts file as I prefer not to share my hosts and IP's with everyone on the planet.

Thanks!
My System SpecsSystem Spec
20 Jul 2011   #5

Windows 8.1 Pro x64
 
 

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

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

Use !analyze -v to get detailed debugging information.

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

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

Debugging Details:
------------------


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  avgcsrva.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003078c69 to fffff80003079700

STACK_TEXT:  
fffff880`009eede8 fffff800`03078c69 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009eedf0 fffff800`03077132 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009eef30 fffff800`03041e88 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`01e15a20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`03077132 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:  4d9fdd34

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

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

1: 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: fffff80003041e88

Debugging Details:
------------------


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  avgcsrva.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003078c69 to fffff80003079700

STACK_TEXT:  
fffff880`009eede8 fffff800`03078c69 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009eedf0 fffff800`03077132 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009eef30 fffff800`03041e88 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`01e15a20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`03077132 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:  4d9fdd34

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

Followup: MachineOwner
---------
My System SpecsSystem Spec
20 Jul 2011   #6

 
 

yowanvista,

Thanks for your reply. Interesting you should say that, and honestly it wasn't one of things I even thought about checking. We tend to use zonealarm all through the industry so I will check up on it. In the mean time I will get rid of it and see if the problem persists and let you know.

Thank you very much for your help regarding this issue.

Live long and prosper!
My System SpecsSystem Spec
Reply

 Win 7 Intermittent Crashes





Thread Tools



Similar help and support threads for2: Win 7 Intermittent Crashes
Thread Forum
Intermittent computer crashes with BSOD - Please help BSOD Help and Support
BSOD c000021a intermittent crashes BSOD Help and Support
Intermittent crashes *need opinions* General Discussion
Intermittent explorer.exe crashes (ntdll.dll) BSOD Help and Support
Intermittent Crashes & BSOD's BSOD Help and Support
Intermittent crashes - Windows 7 64 bit BSOD Help and Support
Intermittent crashes BSOD Help and Support

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 02:06 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33