New
#1
They are getting fewer - But bsod
Could someone look at the dumpfile attached - please
Not sure what happened.
at least this is not as common as it was several months ago
Thanks
Could someone look at the dumpfile attached - please
Not sure what happened.
at least this is not as common as it was several months ago
Thanks
Did you do what John suggested here? https://www.sevenforums.com/crashes-d...tml#post476735
I still see PC Tools in this dmp.
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\Desktop\033110-68266-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 Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e8ee50 Debug session time: Wed Mar 31 19:04:16.752 2010 (GMT-4) System Uptime: 0 days 1:18:53.295 Loading Kernel Symbols ............................................................... ................................................................ ............................................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {fffffa800c63d000, 2, 0, fffff8800854a8eb} Unable to load image \??\C:\Windows\system32\drivers\pctNdis-PacketFilter64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for pctNdis-PacketFilter64.sys *** ERROR: Module load completed but symbols could not be loaded for pctNdis-PacketFilter64.sys Probably caused by : pctNdis-PacketFilter64.sys ( pctNdis_PacketFilter64+e8eb ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: fffffa800c63d000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff8800854a8eb, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef90e0 fffffa800c63d000 CURRENT_IRQL: 2 FAULTING_IP: pctNdis_PacketFilter64+e8eb fffff880`0854a8eb 807d00fa cmp byte ptr [rbp],0FAh CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: pctsSvc.exe TRAP_FRAME: fffff88008217ba0 -- (.trap 0xfffff88008217ba0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8006449918 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800854a8eb rsp=fffff88008217d30 rbp=fffffa800c63d000 r8=0000000000000000 r9=0000000000000000 r10=fffffa8006a9af11 r11=fffff88008217d98 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc pctNdis_PacketFilter64+0xe8eb: fffff880`0854a8eb 807d00fa cmp byte ptr [rbp],0FAh ss:0018:fffffa80`0c63d000=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002cc2469 to fffff80002cc2f00 STACK_TEXT: fffff880`08217a58 fffff800`02cc2469 : 00000000`0000000a fffffa80`0c63d000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`08217a60 fffff800`02cc10e0 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff880`08217f18 : nt!KiBugCheckDispatch+0x69 fffff880`08217ba0 fffff880`0854a8eb : fffffa80`06449918 fffffa80`05226018 fffffa80`06449908 00000000`00000000 : nt!KiPageFault+0x260 fffff880`08217d30 fffffa80`06449918 : fffffa80`05226018 fffffa80`06449908 00000000`00000000 fffffa80`06449918 : pctNdis_PacketFilter64+0xe8eb fffff880`08217d38 fffffa80`05226018 : fffffa80`06449908 00000000`00000000 fffffa80`06449918 fffff880`08210218 : 0xfffffa80`06449918 fffff880`08217d40 fffffa80`06449908 : 00000000`00000000 fffffa80`06449918 fffff880`08210218 fffff880`08550070 : 0xfffffa80`05226018 fffff880`08217d48 00000000`00000000 : fffffa80`06449918 fffff880`08210218 fffff880`08550070 00000000`00000001 : 0xfffffa80`06449908 STACK_COMMAND: kb FOLLOWUP_IP: pctNdis_PacketFilter64+e8eb fffff880`0854a8eb 807d00fa cmp byte ptr [rbp],0FAh SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: pctNdis_PacketFilter64+e8eb FOLLOWUP_NAME: MachineOwner MODULE_NAME: pctNdis_PacketFilter64 IMAGE_NAME: pctNdis-PacketFilter64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ab01663 FAILURE_BUCKET_ID: X64_0xD1_pctNdis_PacketFilter64+e8eb BUCKET_ID: X64_0xD1_pctNdis_PacketFilter64+e8eb Followup: MachineOwner ---------