i found this in the latest dump file. Mean anything?
MODULE_NAME: mfehidk
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 485162bc
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt+74950
8054b950 ab stos dword ptr es:[edi]
TRAP_FRAME: 9bb66bbc -- (.trap 0xffffffff9bb66bbc)
ErrCode = 00000002
eax=0000001c ebx=00000000 ecx=00000000 edx=e46615c8 esi=e46615d0
edi=00000000 eip=8054b950 esp=9bb66c30 ebp=9bb66c88 iopl=0 nv
up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030
gs=0000 efl=00010246 nt+0x74950:
8054b950 ab stos dword ptr es:[edi]
es:0023:00000000=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 9b578cc2 to 8054b950
also see this:
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Gerry said:
jgb555
These types of error can always be down to bad memory. Download and
run the test.
Do you have one or two memory modules? Page 58 of the User's Guide
deals with memory.
If you have bad memory you may have a warranty claim.
BTW this is not the same error as the earlier one but this is not
unusual.
Background information on Stop Error message 0x8E
http://msdn2.microsoft.com/en-us/library/ms794023.aspx
0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
A kernel mode program generated an exception which the error handler
didn't catch. These are nearly always hardware compatibility issues
(which sometimes means a driver issue or a need for a BIOS upgrade).
Source:
http://aumha.org/a/stop.htm
--
Hope this helps.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~