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

16 May 2011   #1

windows 7 x64
 
 
Bluescreen

System windows 7 64 bit

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\051711-19422-01.dmp
C:\Users\animal\AppData\Local\Temp\WER-248587-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

My System SpecsSystem Spec
.

16 May 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by gimley View Post
System windows 7 64 bit

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\051711-19422-01.dmp
C:\Users\animal\AppData\Local\Temp\WER-248587-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
Virtually identical and Related to BdfNdisf6.sysFirewall NDIS6 Filter Driver from BitDefender LLC


Of course I would remove it ans replace with win 7 firewall

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\051711-20872-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03413000 PsLoadedModuleList = 0xfffff800`03658650
Debug session time: Mon May 16 16:32:10.837 2011 (GMT-4)
System Uptime: 0 days 4:07:18.148
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\BdfNdisf6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for BdfNdisf6.sys
*** ERROR: Module load completed but symbols could not be loaded for BdfNdisf6.sys
Probably caused by : BdfNdisf6.sys ( BdfNdisf6+2003 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+6b5952f038fda90
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff8800318b218 -- (.exr 0xfffff8800318b218)
ExceptionAddress: fffff88004db4002 (BdfNdisf6+0x0000000000002002)
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 1
   Parameter[0]: 0000000000000000

TRAP_FRAME:  fffff8800318b2c0 -- (.trap 0xfffff8800318b2c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000103 rbx=0000000000000000 rcx=f88004dc43360000
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004db4003 rsp=fffff8800318b450 rbp=fffffa8008712d00
 r8=fffffa8009350400  r9=ffffffffffffffff r10=fffffa80093504f0
r11=fffff8800318b380 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
BdfNdisf6+0x2003:
fffff880`04db4003 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000348a6be to fffff80003492cd0

STACK_TEXT:  
fffff880`0318a2f8 fffff800`0348a6be : fffff880`0318a350 fffff880`0318a310 fffff880`0318aa70 fffff800`034be890 : nt!KeBugCheck
fffff880`0318a300 fffff800`034be55d : fffff800`03699968 fffff800`035d6cbc fffff800`03413000 fffff880`0318b218 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`0318a330 fffff800`034bd335 : fffff800`035da0fc fffff880`0318a3a8 fffff880`0318b218 fffff800`03413000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0318a360 fffff800`034ce3b1 : fffff880`0318b218 fffff880`0318aa70 fffff880`00000000 00000000`00000001 : nt!RtlDispatchException+0x415
fffff880`0318aa40 fffff800`03492382 : fffff880`0318b218 fffffa80`08949aa0 fffff880`0318b2c0 fffffa80`08b02950 : nt!KiDispatchException+0x135
fffff880`0318b0e0 fffff800`034901b4 : fffffa80`05148024 fffffa80`05148024 fffffa80`04548570 fffff880`04f74fba : nt!KiExceptionDispatch+0xc2
fffff880`0318b2c0 fffff880`04db4003 : fffffa80`08949aa0 fffff880`04dbbec0 fffffa80`00000000 fffffa80`00000000 : nt!KiBreakpointTrap+0xf4
fffff880`0318b450 fffffa80`08949aa0 : fffff880`04dbbec0 fffffa80`00000000 fffffa80`00000000 00000000`00000000 : BdfNdisf6+0x2003
fffff880`0318b458 fffff880`04dbbec0 : fffffa80`00000000 fffffa80`00000000 00000000`00000000 fffffa80`08b02950 : 0xfffffa80`08949aa0
fffff880`0318b460 fffffa80`00000000 : fffffa80`00000000 00000000`00000000 fffffa80`08b02950 fffff880`0318b490 : BdfNdisf6+0x9ec0
fffff880`0318b468 fffffa80`00000000 : 00000000`00000000 fffffa80`08b02950 fffff880`0318b490 fffffa80`08712d40 : 0xfffffa80`00000000
fffff880`0318b470 00000000`00000000 : fffffa80`08b02950 fffff880`0318b490 fffffa80`08712d40 00000000`00000000 : 0xfffffa80`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
BdfNdisf6+2003
fffff880`04db4003 ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  BdfNdisf6+2003

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: BdfNdisf6

IMAGE_NAME:  BdfNdisf6.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a92aa1a

FAILURE_BUCKET_ID:  X64_0x1E_BdfNdisf6+2003

BUCKET_ID:  X64_0x1E_BdfNdisf6+2003

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

2: kd> lmvm BdfNdisf6
start             end                 module name
fffff880`04db2000 fffff880`04ddd000   BdfNdisf6 T (no symbols)           
    Loaded symbol image file: BdfNdisf6.sys
    Image path: \SystemRoot\system32\DRIVERS\BdfNdisf6.sys
    Image name: BdfNdisf6.sys
    Timestamp:        Mon Aug 24 10:56:26 2009 (4A92AA1A)
    CheckSum:         00020615
    ImageSize:        0002B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
Reply

 Bluescreen




Thread Tools



Similar help and support threads for2: Bluescreen
Thread Forum
BlueScreen BSOD Help and Support
When a bluescreen isnt a bluescreen Performance & Maintenance
Getting Bluescreen lately BSOD Help and Support
BlueScreen BSOD Help and Support
Bluescreen BSOD Help and Support
HELP! HELP! Bluescreen! BSOD Help and Support
BlueScreen 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 01:17 PM.
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