STOP 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED
The Windows kernel detected an illegal or unknown processor instruction, often the result of invalid memory and access violations caused by faulty drivers or hardware devices. The error message often identifies the offending driver or device. If the error occurred immediately after installing a driver or service, try disabling or removing the new addition.
Code:
icrosoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp2_Windows_NT6_BSOD_jcgriff2[1].zip\Windows_NT6_BSOD_jcgriff2\082810-20888-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 Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03008000 PsLoadedModuleList = 0xfffff800`03245e50
Debug session time: Sat Aug 28 07:30:05.741 2010 (GMT-4)
System Uptime: 0 days 1:13:18.959
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000046, fffff800030a7034, 0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\btprot.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for btprot.sys
*** ERROR: Module load completed but symbols could not be loaded for btprot.sys
Probably caused by : btprot.sys ( btprot+361c7 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000046, The exception code that was not handled
Arg2: fffff800030a7034, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
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`030a7034 488b8424b8010000 mov rax,qword ptr [rsp+1B8h]
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
EXCEPTION_RECORD: fffff8800276b700 -- (.exr 0xfffff8800276b700)
ExceptionAddress: fffff800030a7034 (nt!RtlRaiseStatus+0x0000000000000018)
ExceptionCode: c0000046
ExceptionFlags: 00000001
NumberParameters: 0
TRAP_FRAME: fffff8800276b540 -- (.trap 0xfffff8800276b540)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8800276b7a0
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030a7034 rsp=fffff8800276b6e0 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=fffff80003008000
r11=00000000000000b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!RtlRaiseStatus+0x18:
fffff800`030a7034 488b8424b8010000 mov rax,qword ptr [rsp+1B8h] ss:0018:fffff880`0276b898=fffff800030a7034
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030b2a39 to fffff80003078740
STACK_TEXT:
fffff880`0276ac38 fffff800`030b2a39 : 00000000`0000001e ffffffff`c0000046 fffff800`030a7034 00000000`00000000 : nt!KeBugCheckEx
fffff880`0276ac40 fffff800`0317c459 : fffff880`0276b700 fffff880`0276b700 fffff880`0276b540 fffff880`0276b7a0 : nt!KiDispatchException+0x1b9
fffff880`0276b2d0 fffff800`0307a3fb : fffff880`0276b700 fffffa80`072fa0d0 00000000`00000000 00000008`00000004 : nt!KiRaiseException+0x1b9
fffff880`0276b400 fffff800`03077993 : fffffa80`082e3310 00000000`00000000 fffffa80`0821dc00 fffff800`030845b4 : nt!NtRaiseException+0x7b
fffff880`0276b540 fffff800`030a7034 : fffff880`0276b700 fffff880`0276b7a0 fffffa80`00000001 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0276b6e0 fffff800`03081610 : fffffa80`0712bc30 fffffa80`07110950 fffffa80`09af3e08 fffffa80`070fd900 : nt!RtlRaiseStatus+0x18
fffff880`0276bc80 fffff880`054361c7 : 00000000`00000000 fffffa80`00000001 fffffa80`08454d00 fffffa80`0712bc00 : nt!KeReleaseMutant+0x260
fffff880`0276bd30 00000000`00000000 : fffffa80`00000001 fffffa80`08454d00 fffffa80`0712bc00 fffffa80`09914c20 : btprot+0x361c7
STACK_COMMAND: kb
FOLLOWUP_IP:
btprot+361c7
fffff880`054361c7 ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: btprot+361c7
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: btprot
IMAGE_NAME: btprot.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4918b1c5
FAILURE_BUCKET_ID: X64_0x1E_btprot+361c7
BUCKET_ID: X64_0x1E_btprot+361c7
Followup: MachineOwner
---------
Install new driver
Btport.sys file description
Productname: Bluetooth Software 5.0.1.3200
Description: Bluetooth BTPORT Driver for Windows 2000
Company: Broadcom Corporation.
Your drivers are fairly current, except for bluetooth. Go to company website and update all BT drivers.
btiaa2dp.sys Fri Sep 05 17:52:34 2008
btiahid.sys Tue Jul 15 20:11:56 2008
btiapan.sys Fri Sep 05 17:51:33 2008
btiarcp.sys Tue Jul 15 20:11:57 2008
btiasco.sys Mon Jul 07 19:16:57 2008
btiaspp.sys Thu Sep 11 14:54:01 2008
btiausb.sys Mon Nov 10 17:12:25 2008
btprot.sys Mon Nov 10 17:12:21 2008
Quote