Code:
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\ossi\012112-23946-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0341d000 PsLoadedModuleList = 0xfffff800`03662670
Debug session time: Sat Jan 21 03:51:02.869 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:15.570
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a00497b000, 0, fffff88004204c02, 0}
Unable to load image \??\C:\Windows\system32\drivers\acedrv09.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for acedrv09.sys
*** ERROR: Module load completed but symbols could not be loaded for acedrv09.sys
Could not read faulting driver name
Probably caused by : acedrv09.sys ( acedrv09+4c02 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a00497b000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88004204c02, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036cc100
fffff8a00497b000
FAULTING_IP:
acedrv09+4c02
fffff880`04204c02 450fb70452 movzx r8d,word ptr [r10+rdx*2]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: smss.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88006d84620 -- (.trap 0xfffff88006d84620)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000a85b rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000020 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004204c02 rsp=fffff88006d847b0 rbp=fffffa80080fc908
r8=000000000000a810 r9=000000000000003a r10=fffff8a00497afc0
r11=0000000000007b80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe cy
acedrv09+0x4c02:
fffff880`04204c02 450fb70452 movzx r8d,word ptr [r10+rdx*2] ds:c908:fffff8a0`0497b000=????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800034459fc to fffff80003499c40
STACK_TEXT:
fffff880`06d844b8 fffff800`034459fc : 00000000`00000050 fffff8a0`0497b000 00000000`00000000 fffff880`06d84620 : nt!KeBugCheckEx
fffff880`06d844c0 fffff800`03497d6e : 00000000`00000000 fffff8a0`0497b000 fffff880`06d84700 00000000`000004fc : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`06d84620 fffff880`04204c02 : 004e0052`0045004b 00320033`004c0045 004c004c`0044002e 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`06d847b0 004e0052`0045004b : 00320033`004c0045 004c004c`0044002e 00000000`00000000 ffff0000`02f9b30f : acedrv09+0x4c02
fffff880`06d847b8 00320033`004c0045 : 004c004c`0044002e 00000000`00000000 ffff0000`02f9b30f 00000000`0015a000 : 0x4e0052`0045004b
fffff880`06d847c0 004c004c`0044002e : 00000000`00000000 ffff0000`02f9b30f 00000000`0015a000 0015d9dc`00000144 : 0x320033`004c0045
fffff880`06d847c8 00000000`00000000 : ffff0000`02f9b30f 00000000`0015a000 0015d9dc`00000144 fffff880`04204e18 : 0x4c004c`0044002e
STACK_COMMAND: kb
FOLLOWUP_IP:
acedrv09+4c02
fffff880`04204c02 450fb70452 movzx r8d,word ptr [r10+rdx*2]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: acedrv09+4c02
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: acedrv09
IMAGE_NAME: acedrv09.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45cc7c68
FAILURE_BUCKET_ID: X64_0x50_acedrv09+4c02
BUCKET_ID: X64_0x50_acedrv09+4c02
Followup: MachineOwner
---------
2: kd> lmvm acedrv09
start end module name
fffff880`04200000 fffff880`04224000 acedrv09 T (no symbols)
Loaded symbol image file: acedrv09.sys
Image path: \??\C:\Windows\system32\drivers\acedrv09.sys
Image name: acedrv09.sys
Timestamp: Fri Feb 09 06:51:36 2007 (45CC7C68)
CheckSum: 0002AAEE
ImageSize: 00024000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Remove acedrv09.sys as it is quite old and blamed for the crash. The best method to remove the offending driver (from my Google research of the file) is to go into C:\Windows\System32\Drivers and rename acedrv09.sys to acedrv09.sys.bak to create a backup of it and prevent the system from loading the driver.
You will also want to find acedrv09.dll and rename it to acedrv09.dll.bak to prevent it from causing conflicts. To find acedrv09.dll, open an Elevated Command Prompt and type the following lines.
cd ..
cd ..
dir /s /b *acedrv09.dll*
That will tell you which directory the .dll file is in and you can navigate to that directory through (Start Menu -> My Computer/Computer -> Double click C:) and then navigating the folders based on the path found by the command prompt.
If you need help or get stuck with the above process, let us know.