BSOD after windows loading screen

[Viperlx]

Hi All,

I have a computer which gives me a blue screen when I turn it on. Sometimes this will happen 4 times in a row and others I can't even get the blue screen. I didn't record the error code down but I am trying to replicate the issue and when I get the screen I will update this post.

- x86 (32-bit) or x64 ? x86
- the original installed OS on the system? Windows 7 Enterprise
- an OEM or full retail version? OEM
- What is the age of system (hardware)? 3 years
- What is the age of OS installation (have you re-installed the OS?) 2 months

I also attached a report and perfmon html file too.

Thanks for any help!

 

[ePeen]

Hi,

Your BSODs are caused / pointing to CipcCdp.sys which is the Cisco IP Communicator driver for CDP. Update the software using this driver or remove it by navigating to C:\windows\system32\drivers and changing CipcCdp.sys to CipcCdp.bak.

If you cannot get into Windows to do the following, boot into Safe Mode and do it there.

Drivers that need to be updated:

HpqKbFiltr.sys - HpqKbFiltr Mon Jun 18 18:12:03 2007 (HP Quick Launch Buttons HpqKbFiltr Keyboard Filter driver). Update here.

PBADRV.sys - PBADRV Mon Jan 07 13:52:14 2008 (PBA Support Driver from Dell). Update here.

dne2000.sys - dne2000 Mon Nov 10 19:59:21 2008 (Citrix Deterministic Network Enhancer Miniport or Cisco Systems VPN Client). Update here.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\Dumps\Windows_NT6_BSOD_jcgriff2\022712-20233-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16905.x86fre.win7_gdr.111025-1503
Machine Name:
Kernel base = 0x82c1d000 PsLoadedModuleList = 0x82d65810
Debug session time: Mon Feb 27 13:47:27.214 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:21.400
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {16, 2, 0, 82c59a5b}

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

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000016, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82c59a5b, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82d85718
Unable to read MiSystemVaType memory at 82d65160
 00000016 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiSignalNotificationObject+18
82c59a5b 807f1601        cmp     byte ptr [edi+16h],1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from 82c8489d to 82c59a5b

STACK_TEXT:  
807b6c5c 82c8489d 82d46d20 00000000 88f339c8 nt!KiSignalNotificationObject+0x18
807b6c84 8b222591 921edb78 00000000 00000000 nt!KeSetEvent+0x98
807b6c98 921ec324 921edb78 807b6d34 8b29050b ndis!NdisSetEvent+0x12
WARNING: Stack unwind information not available. Following frames may be wrong.
807b6ca4 8b29050b 00000000 807b6cc8 8b2594d0 CipcCdp+0x1324
807b6d34 8b2216da 00f339c8 00000000 876de720 ndis!ndisCheckProtocolBindings+0x219
807b6d50 82e2ba55 00000000 a4d47a48 00000000 ndis!ndisWorkerThread+0xa4
807b6d90 82cdd219 8b221636 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
CipcCdp+1324
921ec324 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  CipcCdp+1324

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CipcCdp

IMAGE_NAME:  CipcCdp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c478732

FAILURE_BUCKET_ID:  0xA_CipcCdp+1324

BUCKET_ID:  0xA_CipcCdp+1324

Followup: MachineOwner

 

[Viperlx]

Removing that driver seemed to fix the issue. Thank you for the help!!

 

[ePeen]

Great, my pleasure!

Have a great day