BSoD references missing file?
- From: thynke <thynke@xxxxxxxxx>
- Date: 28 May 2007 20:22:29 -0700
Hi all,
for the past couple of weeks, I've been getting BSoDs a couple times
a
day on my Dell Inspiron 5100 notebook.
Some system details:
Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 2 Build 2600
OS Manufacturer Microsoft Corporation
System Name NOTEBOOK
System Manufacturer Dell Computer Corporation
System Model Inspiron 5100
System Type X86-based PC
Processor x86 Family 15 Model 2 Stepping 9 GenuineIntel ~2392
Mhz
BIOS Version/Date Dell Computer Corporation A32, 10/18/2004
SMBIOS Version 2.3
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.2180
(xpsp_sp2_rtm.
040803-2158)"
Total Physical Memory 1,024.00 MB
Available Physical Memory 642.52 MB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB
Page File Space 3.41 GB
Page File C:\pagefile.sys
The error indicates that a file, mmig46.sys, is responsible for the
crash. However, a search for the file on my system (along with
searching *.* for files that contain the text "mmig46"), turn up
nothing.
Additionally, a Google search for mmig46.sys turns up zilch.
No such file?
But, I do see a few registry keys on my system which contain
references to the file, namely:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_MMIG46
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_MMIG46\0000
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root
\LEGACY_MMIG46\0000\Control
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root
\LEGACY_MMIG46\0000\LogConf
I tried backing up the registry and removing these keys, but upon
reboot, the keys are back where they were.
Here's a kernel dump from the most recent crash:
// begin dump
**************************************************************
Microsoft (R) Windows Debugger Version 6.7.0005.0
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Dumpfiles\Memory.dmp]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Mon May 28 16:52:53.336 2007 (GMT-4)
System Uptime: 0 days 6:55:49.908
Loading Kernel Symbols
...........................................................................................
...............................................
Loading User Symbols
Loading unloaded module list
.................
***************************************************************************
****
*
*
* Bugcheck
Analysis *
*
*
***************************************************************************
****
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {c0000005, b216ecb8, b22a2c50, b22a294c}
*** ERROR: Module load completed but symbols could not be loaded for
Mmig46.sys
Probably caused by : Mmig46.sys ( Mmig46+ecb8 )
Followup: MachineOwner
---------
kd> !analyze -v
***************************************************************************
****
*
*
* Bugcheck
Analysis *
*
*
***************************************************************************
****
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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: c0000005, The exception code that was not handled
Arg2: b216ecb8, The address that the exception occurred at
Arg3: b22a2c50, Exception Record Address
Arg4: b22a294c, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at
"0x%08lx". The memory could not be "%s".
FAULTING_IP:
Mmig46+ecb8
b216ecb8 668908 mov word ptr [eax],cx
EXCEPTION_RECORD: b22a2c50 -- (.exr 0xffffffffb22a2c50)
ExceptionAddress: b216ecb8 (Mmig46+0x0000ecb8)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000023
Attempt to write to address 00000023
CONTEXT: b22a294c -- (.cxr 0xffffffffb22a294c)
eax=00000023 ebx=00000000 ecx=000044e8 edx=00000004 esi=00000003
edi=00000008
eip=b216ecb8 esp=b22a2d18 ebp=b22a2d6c iopl=0 nv up ei pl nz
na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010202
Mmig46+0xecb8:
b216ecb8 668908 mov word ptr [eax],cx ds:
0023:00000023=????
Resetting default scope
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at
"0x%08lx". The memory could not be "%s".
WRITE_ADDRESS: 00000023
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 9b180000 to b216ecb8
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may
be wrong.
b22a2d6c 9b180000 ffff0000 00000023 00000003 Mmig46+0xecb8
b22a2dac 8057d0f1 00000000 00000000 00000000 0x9b180000
b22a2ddc 804f827a b216736c 00000000 00000000 nt!
PspSystemThreadStartup
+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
Mmig46+ecb8
b216ecb8 668908 mov word ptr [eax],cx
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Mmig46
IMAGE_NAME: Mmig46.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4649d195
SYMBOL_NAME: Mmig46+ecb8
STACK_COMMAND: .cxr 0xffffffffb22a294c ; kb
FAILURE_BUCKET_ID: 0x7E_Mmig46+ecb8
BUCKET_ID: 0x7E_Mmig46+ecb8
Followup: MachineOwner
----------------------------------------
// end dump
Also...
Event Viewer reports an error by the Service Control Manager
category: none
Event ID: 7028
"The Mmig46 Registry key denied access to SYSTEM account programs so
the Service Control Manager took ownership of the Registry key."
Any ideas? - TIA
.
- Follow-Ups:
- Re: BSoD references missing file?
- From: Holz
- Re: BSoD references missing file?
- Prev by Date: Help: When booting chkdsk dosen't see problem. After boot it does
- Next by Date: RE: Stop Error: 0x000000CF
- Previous by thread: Help: When booting chkdsk dosen't see problem. After boot it does
- Next by thread: Re: BSoD references missing file?
- Index(es):
Relevant Pages
|
