Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_080310-14093-01.zip\080310-12187-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e05000 PsLoadedModuleList = 0xfffff800`03042e50
Debug session time: Tue Aug 3 17:27:21.453 2010 (GMT-4)
System Uptime: 0 days 0:00:15.578
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88001050090, fffff8800437b8d8, fffff8800437b140}
Probably caused by : rdyboost.sys ( rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+94 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88001050090, The address that the exception occurred at
Arg3: fffff8800437b8d8, Exception Record Address
Arg4: fffff8800437b140, 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:
rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+94
fffff880`01050090 440fb702 movzx r8d,word ptr [rdx]
EXCEPTION_RECORD: fffff8800437b8d8 -- (.exr 0xfffff8800437b8d8)
ExceptionAddress: fffff88001050090 (rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+0x0000000000000094)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
CONTEXT: fffff8800437b140 -- (.cxr 0xfffff8800437b140)
rax=000000000019d370 rbx=0000000000000000 rcx=00000000000183fc
rdx=0000000000000000 rsi=fffffa800bed2178 rdi=fffffa800bbc29a0
rip=fffff88001050090 rsp=fffff8800437bb10 rbp=0000000000000001
r8=0000000000000000 r9=00000000ffffffff r10=000000000011aa87
r11=0000000000000001 r12=fffffa800bed2160 r13=000000000018ae60
r14=0000000000001000 r15=fffff880009b7140
iopl=0 nv up ei ng nz ac pe cy
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010293
rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+0x94:
fffff880`01050090 440fb702 movzx r8d,word ptr [rdx] ds:002b:00000000`00000000=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: NULL_DEREFERENCE
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ad0e0
0000000000000000
FOLLOWUP_IP:
rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+94
fffff880`01050090 440fb702 movzx r8d,word ptr [rdx]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88001052894 to fffff88001050090
STACK_TEXT:
fffff880`0437bb10 fffff880`01052894 : 00000000`00000000 fffffa80`0ca38060 fffffa80`0dbd0900 fffffa80`0ca38000 : rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+0x94
fffff880`0437bb50 fffff880`0105b607 : 00000000`0000000a 00000000`00000001 fffffa80`0dbd0900 fffffa80`0bed20b0 : rdyboost!ST_STORE<SMD_TRAITS>::StDmPageRemove+0x30c
fffff880`0437bc80 fffff880`0105a3fe : fffffa80`0dbd0900 00000000`00000080 00000000`00000080 fffffa80`0bed2f88 : rdyboost!ST_STORE<SMD_TRAITS>::StWorkItemProcess+0x22f
fffff880`0437bce0 fffff800`0311aa86 : 00000000`00000000 fffff880`00000000 fffffa80`0bba4b60 fffffa80`09cfb9e0 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStWorker+0x152
fffff880`0437bd40 fffff800`02e53b06 : fffff880`009b2180 fffffa80`0bba4b60 fffff880`009bd1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0437bd80 00000000`00000000 : fffff880`0437c000 fffff880`04376000 fffff880`0437b820 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+94
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: rdyboost
IMAGE_NAME: rdyboost.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc48a
STACK_COMMAND: .cxr 0xfffff8800437b140 ; kb
FAILURE_BUCKET_ID: X64_0x7E_VRF_rdyboost!B_TREE_unsigned_long,ST_STORE_SMD_TRAITS_::_ST_REGION_ENTRY,4096,NP_CONTEXT_::BTreeSearchKey+94
BUCKET_ID: X64_0x7E_VRF_rdyboost!B_TREE_unsigned_long,ST_STORE_SMD_TRAITS_::_ST_REGION_ENTRY,4096,NP_CONTEXT_::BTreeSearchKey+94
Followup: MachineOwner
---------
This dump blames rdyboost.sys Which is a Microsoft driver. How ever, if you do not use ReadyBoost, you can turn it off. For more information, read this thread: