Now that I know how to bypass the repair option and get to safe mode, here is the attached dump file as requested. I cannot do a system health report, keeps producing an error.
The newest BSOD was from NOv 16, 2010. Is this the newest one?
It was caused by rdyboost. sys. I would disable it. the specific function btw is a memory exception caused by the BB security cookie check.
If this is the latest BSOD you should be ok after disabling it.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\111610-34023-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols;srv*e:\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 Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c65000 PsLoadedModuleList = 0xfffff800`02ea2e50
Debug session time: Tue Nov 16 19:29:19.216 2010 (GMT-5)
System Uptime: 0 days 0:01:08.057
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800194c7b4, fffff88002ec9798, fffff88002ec9000}
Probably caused by : rdyboost.sys ( rdyboost!_security_check_cookie+14 )
Followup: MachineOwner
---------
0: 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: fffff8800194c7b4, The address that the exception occurred at
Arg3: fffff88002ec9798, Exception Record Address
Arg4: fffff88002ec9000, 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!_security_check_cookie+14
fffff880`0194c7b4 c20000 ret 0
EXCEPTION_RECORD: fffff88002ec9798 -- (.exr 0xfffff88002ec9798)
ExceptionAddress: fffff8800194c7b4 (rdyboost!_security_check_cookie+0x0000000000000014)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88002ec9000 -- (.cxr 0xfffff88002ec9000)
rax=0000000000000004 rbx=fffffa8005ccb118 rcx=f880019510180000
rdx=00000000000003ff rsi=fffffa8005ccb130 rdi=0000057ffa334ee8
rip=fffff8800194c7b4 rsp=fffff88002ec99d8 rbp=fffff88002ec9a00
r8=fffffa8008cc4000 r9=fffff88002ec9b70 r10=0000000000000000
r11=0000000000000001 r12=0000000000000000 r13=fffff88002ec9b70
r14=fffffa8009163270 r15=fffffa8005ccb118
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
rdyboost!_security_check_cookie+0x14:
fffff880`0194c7b4 c20000 ret 0
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
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: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0d0e0
ffffffffffffffff
FOLLOWUP_IP:
rdyboost!_security_check_cookie+14
fffff880`0194c7b4 c20000 ret 0
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88001931a9d to fffff8800194c7b4
STACK_TEXT:
fffff880`02ec99d8 fffff880`01931a9d : fffffa80`05ccb118 fffffa80`05ccb130 00000000`00000001 00000000`00000020 : rdyboost!_security_check_cookie+0x14
fffff880`02ec99e0 fffff880`01930b2e : fffffa80`05ccb118 fffffa80`05ccb130 fffffa80`09163270 fffffa80`080bacf0 : rdyboost!B_TREE<_SMD_STORE_KEY,ST_STORE<SMD_TRAITS>::_ST_PAGE_ENTRY,4096,NP_CONTEXT>::BTreeSearchResultDeref+0x14d
fffff880`02ec9a50 fffff880`0193d7df : fffffa80`05ccb118 00000000`0401c507 fffff880`02ec9ba0 00000000`00000000 : rdyboost!B_TREE<_SMD_STORE_KEY,ST_STORE<SMD_TRAITS>::_ST_PAGE_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+0x2e
fffff880`02ec9aa0 fffff880`0193c9b7 : fffffa80`0000051f fffff880`000000c0 fffffa80`09163270 fffff880`02ec9b70 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageRetrieve+0x4f
fffff880`02ec9b40 fffff880`0193c5fc : 00000000`00000009 00000000`040df2e2 fffffa80`09163270 fffffa80`05ccb0b0 : rdyboost!ST_STORE<SMD_TRAITS>::StDmPageRetrieve+0x153
fffff880`02ec9c80 fffff880`0193b3fe : fffffa80`09163270 00000000`00000080 00000000`00000080 fffffa80`05ccbf88 : rdyboost!ST_STORE<SMD_TRAITS>::StWorkItemProcess+0x224
fffff880`02ec9ce0 fffff800`02f79c06 : 00000000`00000000 fffff880`00000000 fffffa80`05cc20a0 fffffa80`05205040 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStWorker+0x152
fffff880`02ec9d40 fffff800`02cb3c26 : fffff880`009e6180 fffffa80`05cc20a0 fffff880`009f0f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02ec9d80 00000000`00000000 : fffff880`02eca000 fffff880`02ec4000 fffff880`02ec9820 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: rdyboost!_security_check_cookie+14
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: rdyboost
IMAGE_NAME: rdyboost.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc48a
STACK_COMMAND: .cxr 0xfffff88002ec9000 ; kb
FAILURE_BUCKET_ID: X64_0x7E_rdyboost!_security_check_cookie+14
BUCKET_ID: X64_0x7E_rdyboost!_security_check_cookie+14
Followup: MachineOwner
---------
Old drivers needing updating. Your video driver is over 3 years old.
Code:
c6501.sys 2/7/2007 5:18:04 0x45c9a75c fffff880`06e70000 fffff880`06fc6000 0x00156000
nvmfdx64.sys 8/1/2008 13:38:28 0x48935824 fffff880`04272000 fffff880`043de180 0x0016c180
nvstor64.sys 8/18/2008 20:53:39 0x48aa27a3 fffff880`00dc2000 fffff880`00dee000 0x0002c000
dump_nvstor64.sys 8/18/2008 20:53:39 0x48aa27a3 fffff880`0586f000 fffff880`0589b000 0x0002c000