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: BSOD - during docking

13 May 2015   #1
labrat

Windows 7 64 bit
 
 
BSOD - during docking

Hi,
I got the BSOD screen a couple of times yesterday. I managed to replicate the issue multiple times - happens when the laptop isn't docked properly. Maybe graphics card related, but not sure. I think there may be dump files from previous blue screen crashes - that might be a separate issue - don't think it's related.

I've attached the zip file - hope you guys can help with the recent/ past crashes. Thanks


My System SpecsSystem Spec
.
15 May 2015   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Hi labrat.

Try to update the driver to your HD Pro Webcam C920 from here.

Report us for any further BSOD after doing it.
_________________________________________________
Code:
BugCheck 3B, {c0000005, fffff88004d167b3, fffff8801f54d250, 0}

*** WARNING: Unable to verify timestamp for lvrs64.sys
*** ERROR: Module load completed but symbols could not be loaded for lvrs64.sys
Probably caused by : ks.sys ( ks!KsDispatchIrp+d3 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88004d167b3, Address of the instruction which caused the bugcheck
Arg3: fffff8801f54d250, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP: 
ks!KsDispatchIrp+d3
fffff880`04d167b3 488b02          mov     rax,qword ptr [rdx]

CONTEXT:  fffff8801f54d250 -- (.cxr 0xfffff8801f54d250;r)
rax=fffffa800e181cd8 rbx=fffffa800e0f5bc0 rcx=fffffa800c3b0850
rdx=4d7d674deae3b483 rsi=fffffa800c3b0850 rdi=fffffa800e181740
rip=fffff88004d167b3 rsp=fffff8801f54dc30 rbp=fffff8801f54ddc0
 r8=fffffa800c3b0850  r9=fffffa800e181740 r10=0000000000000000
r11=fffff8801f54d990 r12=000000000000000c r13=0000000000000001
r14=0000000000000001 r15=fffffa800dfb59d0
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
ks!KsDispatchIrp+0xd3:
fffff880`04d167b3 488b02          mov     rax,qword ptr [rdx] ds:002b:4d7d674d`eae3b483=????????????????
Last set context:
rax=fffffa800e181cd8 rbx=fffffa800e0f5bc0 rcx=fffffa800c3b0850
rdx=4d7d674deae3b483 rsi=fffffa800c3b0850 rdi=fffffa800e181740
rip=fffff88004d167b3 rsp=fffff8801f54dc30 rbp=fffff8801f54ddc0
 r8=fffffa800c3b0850  r9=fffffa800e181740 r10=0000000000000000
r11=fffff8801f54d990 r12=000000000000000c r13=0000000000000001
r14=0000000000000001 r15=fffffa800dfb59d0
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
ks!KsDispatchIrp+0xd3:
fffff880`04d167b3 488b02          mov     rax,qword ptr [rdx] ds:002b:4d7d674d`eae3b483=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Unity.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff88004cfd560 to fffff88004d167b3

STACK_TEXT:  
fffff880`1f54dc30 fffff880`04cfd560 : fffffa80`0e181740 fffff880`0c557070 fffff880`00000003 fffff880`0c559170 : ks!KsDispatchIrp+0xd3
fffff880`1f54dc60 fffff880`0c52d2a4 : fffffa80`0e181740 fffffa80`0e181cd8 fffff880`0c554f41 00000000`ffffffff : ks!CKsDevice::PassThroughIrp+0xc0
fffff880`1f54dca0 fffffa80`0e181740 : fffffa80`0e181cd8 fffff880`0c554f41 00000000`ffffffff 00000000`00000000 : lvrs64+0x152a4
fffff880`1f54dca8 fffffa80`0e181cd8 : fffff880`0c554f41 00000000`ffffffff 00000000`00000000 00000000`00000001 : 0xfffffa80`0e181740
fffff880`1f54dcb0 fffff880`0c554f41 : 00000000`ffffffff 00000000`00000000 00000000`00000001 fffff880`0c554f40 : 0xfffffa80`0e181cd8
fffff880`1f54dcb8 00000000`ffffffff : 00000000`00000000 00000000`00000001 fffff880`0c554f40 00000000`00000000 : lvrs64+0x3cf41
fffff880`1f54dcc0 00000000`00000000 : 00000000`00000001 fffff880`0c554f40 00000000`00000000 fffff880`0c554f41 : 0xffffffff


FOLLOWUP_IP: 
ks!KsDispatchIrp+d3
fffff880`04d167b3 488b02          mov     rax,qword ptr [rdx]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ks!KsDispatchIrp+d3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ks

IMAGE_NAME:  ks.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a3f3

IMAGE_VERSION:  6.1.7601.17514

STACK_COMMAND:  .cxr 0xfffff8801f54d250 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_ks!KsDispatchIrp+d3

BUCKET_ID:  X64_0x3B_ks!KsDispatchIrp+d3

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_ks!ksdispatchirp+d3

FAILURE_ID_HASH:  {43fe7e33-d99e-1b31-8127-54e240a9ec27}

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

1: kd> lmvm ks
start             end                 module name
fffff880`04cfc000 fffff880`04d3f000   ks         (pdb symbols)          c:\symbols\ks.pdb\55180135F005455BB845BEE938E68ECC2\ks.pdb
    Loaded symbol image file: ks.sys
    Mapped memory image file: c:\symbols\ks.sys\4CE7A3F343000\ks.sys
    Image path: \SystemRoot\system32\DRIVERS\ks.sys
    Image name: ks.sys
    Timestamp:        Sat Nov 20 16:03:23 2010 (4CE7A3F3)
    CheckSum:         00045588
    ImageSize:        00043000
    File version:     6.1.7601.17514
    Product version:  6.1.7601.17514
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.0 Driver
    File date:        00000000.00000000
    Translations:     0000.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ks.sys
    OriginalFilename: ks.sys
    ProductVersion:   6.1.7601.17514
    FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
    FileDescription:  Kernel CSA Library
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
1: kd> lmvm lvrs64
start             end                 module name
fffff880`0c518000 fffff880`0c56bb80   lvrs64   T (no symbols)           
    Loaded symbol image file: lvrs64.sys
    Image path: \SystemRoot\system32\DRIVERS\lvrs64.sys
    Image name: lvrs64.sys
    Timestamp:        Thu Dec 15 10:43:30 2011 (4EE981FA)
    CheckSum:         00065895
    ImageSize:        00053B80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
19 May 2015   #3
labrat

Windows 7 64 bit
 
 

Thanks Arc for looking into this. I have updated the C920 drivers. I will come back with an update in a week and let you know if I see any more blue screens.
My System SpecsSystem Spec
.

19 May 2015   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

OK, take your time.
My System SpecsSystem Spec
Reply

 BSOD - during docking




Thread Tools




Similar help and support threads
Thread Forum
BSOD when mounting to docking station
Good morning, User came in to weird error today - they think it might have been "LogMeIn". They started to get BSODs when placing the laptop, Lenovo T450s, onto docking station. Anything obvious in dumps? I uninstalled/reinstalled LogMeIn as a first step. Thanks!
BSOD Help and Support
HP Laptop BSOD on removal from docking station
(Post has been edited - 8/20/14) Hi guys, Got a user with an HP EliteBook 850 G1 laptop. Sometimes when he goes to remove the laptop from its docking station while still running, it'll BSOD. Quick google search didn't turn up anything specific. His laptop appears to have been...
BSOD Help and Support
HDD > 2 TB and docking stations
Jumanji discovered an interesting bit and I thought others should be aware. This might be old news to some. I found one article to exemplify the issue, but there are sure to be more. While this article refers to 3TB drives, the same caution applies to 4TB and greater drives. Basically older...
Hardware & Devices
BSOD on Lenovo W530 after ejecting from Docking Station
Hi, I am experiencing BSOD around a minute or so after ejecting from my docking station. Would love any pointers on where to start troubleshooting. Please find the dump file attached. Thanks, David.
BSOD Help and Support
BSOD On Laptop With Docking Station.
Getting a random blue screen on an HP Elitebook 8470p. I believe it is caused by the docking station. Thanks for any help Yoseph
BSOD Help and Support
Docking WMP
Have MS removed the ability to dock wmp into the taskbar like you could with vista? I thought that was rather nice feature.
Music, Pictures & Video


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 15:26.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App