New
#11
Well I already rebooted. But so far after two reboots there is no bluetooth devices loaded in Device Manager. We are feeling a little more optimistic now. I'll just use it and abuse a day or two and see how it goes.
Well I already rebooted. But so far after two reboots there is no bluetooth devices loaded in Device Manager. We are feeling a little more optimistic now. I'll just use it and abuse a day or two and see how it goes.
Alright, best of luck! Post back in a few days how the system responds. :)
So far so good. Still keeping an eye on it though for a day or so before marking this as resolved.
Had a couple of BSOD's last night. Both when happened after putting in the password to TruCrypt for mounting.
Before that the worse thing that was happening was the plug in for adobe was crashing in the web browser.
Attached is the BSOD reports.
Thank you for your analysis in advance.
Caused by ESET. Remove ESET and install the latest version (even if you already have the latest version). Your version could be out of date or corrupted. Use the ESET uninstall tool to remove the software. Make sure to get the Windows 7 uninstaller...Code:Loading Dump File [D:\Kingston\BSODDmpFiles\jbPanama\Windows_NT6_BSOD_jcgriff2\032112-24788-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`0324a000 PsLoadedModuleList = 0xfffff800`0348e650 Debug session time: Wed Mar 21 19:55:26.790 2012 (UTC - 6:00) System Uptime: 0 days 0:43:44.414 Loading Kernel Symbols ............................................................... ................................................................ ..................................................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff88002108745, fffff88009a91130, 0} Unable to load image \SystemRoot\system32\DRIVERS\eamonm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for eamonm.sys *** ERROR: Module load completed but symbols could not be loaded for eamonm.sys Probably caused by : eamonm.sys ( eamonm+7745 ) Followup: MachineOwner --------- 2: 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: fffff88002108745, Address of the instruction which caused the bugcheck Arg3: fffff88009a91130, 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%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: eamonm+7745 fffff880`02108745 483933 cmp qword ptr [rbx],rsi CONTEXT: fffff88009a91130 -- (.cxr 0xfffff88009a91130) rax=0000000000000000 rbx=fffde5830f2c433b rcx=fffff88002186778 rdx=fffff88009a91c88 rsi=0000000000000718 rdi=0000000000000000 rip=fffff88002108745 rsp=fffff88009a91b10 rbp=fffffa800bcb53b0 r8=fffff88009a91c60 r9=0000000000000000 r10=fffffa800bba6010 r11=fffff88009a91c08 r12=0000000000000000 r13=fffff88009a91c88 r14=0000000000000001 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 eamonm+0x7745: fffff880`02108745 483933 cmp qword ptr [rbx],rsi ds:002b:fffde583`0f2c433b=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: TrueCrypt.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 0000000000000718 to fffff88002108745 STACK_TEXT: fffff880`09a91b10 00000000`00000718 : 00000000`00000000 00000000`00000000 fffffa80`0bcb5450 fffffa80`0a5eb680 : eamonm+0x7745 fffff880`09a91b18 00000000`00000000 : 00000000`00000000 fffffa80`0bcb5450 fffffa80`0a5eb680 00000000`00000000 : 0x718 FOLLOWUP_IP: eamonm+7745 fffff880`02108745 483933 cmp qword ptr [rbx],rsi SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: eamonm+7745 FOLLOWUP_NAME: MachineOwner MODULE_NAME: eamonm IMAGE_NAME: eamonm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4baa6584 STACK_COMMAND: .cxr 0xfffff88009a91130 ; kb FAILURE_BUCKET_ID: X64_0x3B_eamonm+7745 BUCKET_ID: X64_0x3B_eamonm+7745 Followup: MachineOwner ---------
Thank you. I will do that as soon as I return home from work.
The BSOD usually happens 90% of the time.
I finally got ESET v4 uninstalled and v5 installed.
My first attempt to mount the drive was successful.
I have to go to work now to meet deadlines.
I will do a series of mounts and dismounts to try and break it. I will report back tomorrow. Thanks again Ziden!!
Last edited by jbPanama; 23 Mar 2012 at 11:32.
No problem. Best of luck!
writhziden, you rock!
Thanks so much!!
Everything continues to work great!
You have solved the issues!
That is excellent news! Thank you for posting back. I am very happy I was able to help.