BSOD, would like to know why?

[Kari]

After almost a year with 7 on several computers, I finally got my first BSOD. I don't count the one I had earlier because it was caused by an application I knew to be incompatible when I installed it.

This one puzzles me. Computer was working alone doing some prescheduled tasks when I was not at home. When I came back, I found BSOD.

Dump file attached, any information really appreciated.

Kari

 

[zigzag3143]

After almost a year with 7 on several computers, I finally got my first BSOD. I don't count the one I had earlier because it was caused by an application I knew to be incompatible when I installed it.

This one puzzles me. Computer was working alone doing some prescheduled tasks when I was not at home. When I came back, I found BSOD.

Dump file attached, any information really appreciated.

Kari

Hey Kari
this crash was probably caused by emOEM64.sys \. Not much info available on it but it has been used by virii to hide.

I would run your av for a thorough check
run a sytem file check to verify and repair your system files
typr cmd in search>right click and run as admin>sfc /scannow

I am sure you know all of the above but just in case

Ken J+

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


Loading Dump File [C:\Users\K\Desktop\121509-34725-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`03056e50
Debug session time: Tue Dec 15 13:18:03.510 2009 (GMT-5)
System Uptime: 1 days 22:59:58.171
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800f5afb57, fffff8800dc24960, 0}

Probably caused by : emOEM64.sys ( emOEM64+12b57 )

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

0: 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: fffff8800f5afb57, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800dc24960, 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: 
emOEM64+12b57
fffff880`0f5afb57 83784c00        cmp     dword ptr [rax+4Ch],0

CONTEXT:  fffff8800dc24960 -- (.cxr 0xfffff8800dc24960)
rax=e56c694602150003 rbx=0000000000000004 rcx=fffffa8008bc0b50
rdx=0000000000000004 rsi=fffff8800dc25400 rdi=fffffa8008bc0b50
rip=fffff8800f5afb57 rsp=fffff8800dc25340 rbp=fffffa80087630d8
 r8=fffff8800dc25400  r9=0500000000000501 r10=fffff80003004a60
r11=0000000000000000 r12=0000000000000004 r13=0000000000000000
r14=0000000000000007 r15=0000000000000028
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
emOEM64+0x12b57:
fffff880`0f5afb57 83784c00        cmp     dword ptr [rax+4Ch],0 ds:002b:e56c6946`0215004f=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  ehrecvr.exe

CURRENT_IRQL:  1

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800f5afb57

STACK_TEXT:  
fffff880`0dc25340 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : emOEM64+0x12b57


FOLLOWUP_IP: 
emOEM64+12b57
fffff880`0f5afb57 83784c00        cmp     dword ptr [rax+4Ch],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  emOEM64+12b57

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: emOEM64

IMAGE_NAME:  emOEM64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  486987d7

STACK_COMMAND:  .cxr 0xfffff8800dc24960 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_emOEM64+12b57

BUCKET_ID:  X64_0x3B_emOEM64+12b57

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

 

[Kari]

Thanks, Ken. I know that file belongs to my Cinergy HTC XS HD TV-receiver, so at least I know where to look for the problem.

Kari