Solved Just had a BSOD during boot

[lannyboy]

I am using
- Windows 7 SP1 Enterprise x64
- Laptop HP EliteBook 6930p
- Mobile Intel 4 Series Family Chipset built-in display
- 4GB memory

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000000, 0x0000000000000002, 0x0000000000000001, 0xfffff88002229ae6). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 112411-31168-01.

===

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

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF88002229AE6
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\112411-31168-01.dmp
C:\Users\leet\AppData\Local\Temp\WER-84115-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


Please help. Thanks.

PS: Please rename the zip extension to 7z extension because it didn't allow me to use 7z extension.

 

[JaidynM]

Is this the first time you've gotten this BSOD? If so, restart the computer and see if another BSOD occurs.

First of all, try running a Startup Repair.
http://www.sevenforums.com/tutorials/681-startup-repair.html

If it doesn't help, run an sfc/scannow command thrice in an elevated command prompt. Complete each command followed by a reboot.
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

This type of error is usually caused by a faulty device driver. However, to pinpoint the offending driver I need to read the dump file. Unfortunately, the program needed to read the .dmp file isn't working for me at the moment so I am in the process of downloading the 650mb file to reinstall.

Until then, just follow the instructions provided above. Although they are not directly related to the problem, the fixes may still prove useful.

EDIT: Jan (JMH), has beaten me to it. CipcCdp.sys is the faulty driver. The Cisco IP Communicator download center can be found below.
Download Software - Cisco Systems

 

[JMH]

Hello lannyboy,
Your crash was probably caused by CipcCdp.sys.
CipcCdp.sys appears to be a driver for Cisco IP Communicator.
Please reinstall using the newest version.

 

[lannyboy]

wow, very effective! thanks a lot guys.

well, it happened once only when after i joined a new domain. no more BSOD after trying to reboot many times.

by the way, what is the tool that you guys use to check the dmp file? i tried with visual studio but it said it is an old dmp type.

is it you guy using WINDBG for reading the memory?

===

just found one useful tool: BSOD Viewer

CipcCdp.sys CipcCdp.sys+1ae6 fffff880`02228000 fffff880`02234000 0x0000c000 0x4bc2b042 4/12/2010 1:31:46 PM
ntoskrnl.exe ntoskrnl.exe+26ee0 fffff800`02a0b000 fffff800`02ff4000 0x005e9000 0x4e02aaa3 6/23/2011 10:53:23 AM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17640 (win7sp1_gdr.110622-1506) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe

 

[JaidynM]

Yep, WinDbg is what I use.

 

[zigzag3143]

WinDbg is the gold standard when used in conjunction with other tools. A bit of a steep learning curve though.

 

[lannyboy]

Thanks guy Never really try on WINDBG.