Shut down activates BSOD

[kaisterkai]

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

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000046
BCP2: FFFFF80002CB0EF8
BCP3: FFFFF880085070B0
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\060910-28142-01.dmp
C:\Users\L Rusaki\AppData\Local\Temp\WER-35459-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

I have the dump mini thing, but I don't know how to upload it.. I can email it to you..

Sigh, this BSOD comes when it's shutting down, restarting or logging off..

Very annoying indeed...

My email is: Removed by Dwarf

Thanks

 

[kaisterkai]

I saw the attachment file thingy... Here is the BSOD error dump thingy:

 

[Jonathan_King]

Welcome to SF!

It's a bad idea to post your email address here. Spiders run through and will pick up such things, and spam you. See here: http://www.sevenforums.com/general-discussion/8-forum-rules.html#post23230

You dmp is pretty straightforward. You Bluetooth drivers are causing the issue. Pleae update them.

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_060910-28142-01.zip\060910-28142-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c12000 PsLoadedModuleList = 0xfffff800`02e4fe50
Debug session time: Wed Jun  9 09:31:39.327 2010 (GMT-4)
System Uptime: 0 days 2:36:23.794
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000046, fffff80002cb0ef8, fffff880085070b0, 0}

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

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

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

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

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000046 - An attempt to release a mutant object was made by a thread that was not the owner of the mutant object.

FAULTING_IP: 
nt!RtlRaiseStatus+18
fffff800`02cb0ef8 488b8424b8010000 mov     rax,qword ptr [rsp+1B8h]

CONTEXT:  fffff880085070b0 -- (.cxr 0xfffff880085070b0)
rax=0000000000000000 rbx=00000000c0000046 rcx=fffff880085070b0
rdx=0000000000000001 rsi=0000000000000001 rdi=fffff80002dfce80
rip=fffff80002cb0ef8 rsp=fffff88008506ff0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=fffff80002dfd820
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=fffffa80042f3b60 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000286
nt!RtlRaiseStatus+0x18:
fffff800`02cb0ef8 488b8424b8010000 mov     rax,qword ptr [rsp+1B8h] ss:0018:fffff880`085071a8=fffff80002cb0ef8
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  NclIVTBTSrv.ex

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002c8b520 to fffff80002cb0ef8

STACK_TEXT:  
fffff880`08506ff0 fffff800`02c8b520 : 00000000`00000010 fffff800`02dfce80 fffffa80`03c3e401 fffff8a0`02a65f01 : nt!RtlRaiseStatus+0x18
fffff880`08507590 fffff880`051de68e : fffff8a0`00000001 fffff8a0`00000001 fffffa80`04233700 fffffa80`02bbad00 : nt!KeReleaseMutant+0x260
fffff880`08507640 fffff8a0`00000001 : fffff8a0`00000001 fffffa80`04233700 fffffa80`02bbad00 00000000`00000000 : VComm+0x368e
fffff880`08507648 fffff8a0`00000001 : fffffa80`04233700 fffffa80`02bbad00 00000000`00000000 fffff8a0`08865f00 : 0xfffff8a0`00000001
fffff880`08507650 fffffa80`04233700 : fffffa80`02bbad00 00000000`00000000 fffff8a0`08865f00 fffffa80`04233600 : 0xfffff8a0`00000001
fffff880`08507658 fffffa80`02bbad00 : 00000000`00000000 fffff8a0`08865f00 fffffa80`04233600 00000000`00000000 : 0xfffffa80`04233700
fffff880`08507660 00000000`00000000 : fffff8a0`08865f00 fffffa80`04233600 00000000`00000000 00000000`00000000 : 0xfffffa80`02bbad00


FOLLOWUP_IP: 
VComm+368e
fffff880`051de68e ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  VComm+368e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: VComm

IMAGE_NAME:  VComm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45ec0a58

STACK_COMMAND:  .cxr 0xfffff880085070b0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_VComm+368e

BUCKET_ID:  X64_0x3B_VComm+368e

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

0: kd> lmvm VComm
start             end                 module name
fffff880`051db000 fffff880`051e4d00   VComm    T (no symbols)           
    Loaded symbol image file: VComm.sys
    Image path: \SystemRoot\system32\DRIVERS\VComm.sys
    Image name: VComm.sys
    Timestamp:        Mon Mar 05 07:17:28 2007 (45EC0A58)
    CheckSum:         0000F4FA
    ImageSize:        00009D00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

If the BSODs continue, please upload all the dmps you have. Just put them in one zip folder.

 

[kaisterkai]

I tried updating the drivers for my Blue tooth, but it seems that it's all up to date?

How else could I install them?

Should I uninstall it then?

 

[Jonathan_King]

Check on the computer manufacturer's site. The drivers you are using now are from 2007, so it's pretty likely there's an update.

If you can't find an update, remove the drivers completely, and see if the problem goes away.

 

[kaisterkai]

Sigh, on their website, it said that their Blue tooth device isn't compatible with win 7...

So what should I do? Leave the drivers out?

 

[Jonathan_King]

I suggest just leaving your computer without BT for a while, until we're sure that's what was causing the BSODs.

If we determine that is the case, I recommend buying a BT card that is compatible with Windows 7.

 

[kaisterkai]

I see..

But could it be that it was the drivers? Because window 7 can use the BT without me installing the drivers, but I installed it anyway just in case.. So could it be that the drivers that was giving to me by the product causing the problem?

 

[Jonathan_King]

If you don't install the drivers from the manufacture's website, Windows will use its own generic drivers, dated July 13, 2009. Try those and see if it works how you like.

 

[kaisterkai]

Yeah, I think I'm going to try that hey..

Thanks for the help, I just restarted my PC, and everything seems to be fine.. It really does seem to be the BT Drivers.. Thanks alot!