Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Bsod

30 Jan 2011   #1
Tek86

Windows 7 Professional x64
 
 
delete

Plz delete this post. Thx


My System SpecsSystem Spec
.
30 Jan 2011   #2
TonyTiger2004

Windows 7 Ultimate x64
 
 

Hello Tek86, Welcome to Sevenforums.

Not a wise idea to overclock your laptop, as the cooling won't be that great. You typically add an aftermarket CPU Cooler on a desktop computer to compensate for your Overclock. I will go through your dump files, im sure you've probably got some old Drivers and things. Will Update your shortly.

- Tony

UPDATE: You Can Go into C:\Windows\System32\drivers and rename rdyboost.sys to rdyboost.bak to disable ready boost.

I Did not see any obvious Drivers needing to be updated. Your bugcheck is pointing to a couple things, one of which is hardware. That could just be from the overclock. as it just isn't advisable to overclock your laptop.

Bugcheck
HTML Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Tony\Desktop\012911-15522-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\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
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a56000 PsLoadedModuleList = 0xfffff800`02c93e50
Debug session time: Sat Jan 29 17:33:17.499 2011 (UTC - 6:00)
System Uptime: 0 days 0:00:11.606
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880011c44c1, fffff88003747858, fffff880037470b0}

Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+441 )

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: fffff880011c44c1, The address that the exception occurred at
Arg3: fffff88003747858, Exception Record Address
Arg4: fffff880037470b0, 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!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+441
fffff880`011c44c1 413bc1          cmp     eax,r9d

EXCEPTION_RECORD:  fffff88003747858 -- (.exr 0xfffff88003747858)
ExceptionAddress: fffff880011c44c1 (rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+0x0000000000000441)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 000000000000c531
Attempt to write to address 000000000000c531

CONTEXT:  fffff880037470b0 -- (.cxr 0xfffff880037470b0)
rax=0000000000000000 rbx=0000000000008532 rcx=0000000000000000
rdx=fffffa8008242448 rsi=0000000000003fff rdi=fffffa80082619cc
rip=fffff880011c44c1 rsp=fffff88003747a90 rbp=fffffa8007df2078
 r8=fffffa8008252a64  r9=0000000000000200 r10=fffffa8008242000
r11=000000000000fce6 r12=fffffa8009726000 r13=00000000ffffffff
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+0x441:
fffff880`011c44c1 413bc1          cmp     eax,r9d
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:  0000000000000001

EXCEPTION_PARAMETER2:  000000000000c531

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfe0e0
 000000000000c531 

FOLLOWUP_IP: 
rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+441
fffff880`011c44c1 413bc1          cmp     eax,r9d

BUGCHECK_STR:  0x7E

EXCEPTION_DOESNOT_MATCH_CODE:  This indicates a hardware error.
Instruction at fffff880011c44c1 does not read/write to 000000000000c531

LAST_CONTROL_TRANSFER:  from fffff880011c33a8 to fffff880011c44c1

STACK_TEXT:  
fffff880`03747a90 fffff880`011c33a8 : 00000000`00000000 fffff880`0d25e000 fffff880`037443e0 fffffa80`07df2078 : rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+0x441
fffff880`03747af0 fffff880`011c1582 : fffffa80`07df2078 00000000`00000010 00000000`00000010 00000000`00000070 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageFindSpace+0x34
fffff880`03747b20 fffff880`011c0757 : fffffa80`0890b320 fffffa80`092a1920 00000000`00000000 fffffa80`07df2078 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageAdd+0x2e
fffff880`03747be0 fffff880`011c0612 : fffffa80`0890b320 00000000`00010000 00000000`00000080 fffffa80`07df2010 : rdyboost!ST_STORE<SMD_TRAITS>::StDmPageAdd+0xe3
fffff880`03747c40 fffff880`011bf3fe : fffffa80`0890b320 00000000`00000080 00000000`00000080 fffffa80`07df2ee8 : rdyboost!ST_STORE<SMD_TRAITS>::StWorkItemProcess+0x23a
fffff880`03747ca0 fffff800`02d6b166 : 00000000`00000000 fffff800`00000000 fffffa80`07deba40 fffffa80`0730a9e0 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStWorker+0x152
fffff880`03747d00 fffff800`02aa6486 : fffff800`02c40e80 fffffa80`07deba40 fffffa80`07d44910 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03747d40 00000000`00000000 : fffff880`03748000 fffff880`03742000 fffff880`037477e0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+441

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rdyboost

IMAGE_NAME:  rdyboost.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc48a

STACK_COMMAND:  .cxr 0xfffff880037470b0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_CODE_ADDRESS_MISMATCH_rdyboost!ST_STORE_SMD_TRAITS_::StDmCurrentRegionFind+441

BUCKET_ID:  X64_0x7E_CODE_ADDRESS_MISMATCH_rdyboost!ST_STORE_SMD_TRAITS_::StDmCurrentRegionFind+441

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: fffff880011c44c1, The address that the exception occurred at
Arg3: fffff88003747858, Exception Record Address
Arg4: fffff880037470b0, 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!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+441
fffff880`011c44c1 413bc1          cmp     eax,r9d

EXCEPTION_RECORD:  fffff88003747858 -- (.exr 0xfffff88003747858)
ExceptionAddress: fffff880011c44c1 (rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+0x0000000000000441)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 000000000000c531
Attempt to write to address 000000000000c531

CONTEXT:  fffff880037470b0 -- (.cxr 0xfffff880037470b0)
rax=0000000000000000 rbx=0000000000008532 rcx=0000000000000000
rdx=fffffa8008242448 rsi=0000000000003fff rdi=fffffa80082619cc
rip=fffff880011c44c1 rsp=fffff88003747a90 rbp=fffffa8007df2078
 r8=fffffa8008252a64  r9=0000000000000200 r10=fffffa8008242000
r11=000000000000fce6 r12=fffffa8009726000 r13=00000000ffffffff
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+0x441:
fffff880`011c44c1 413bc1          cmp     eax,r9d
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:  0000000000000001

EXCEPTION_PARAMETER2:  000000000000c531

WRITE_ADDRESS:  000000000000c531 

FOLLOWUP_IP: 
rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+441
fffff880`011c44c1 413bc1          cmp     eax,r9d

BUGCHECK_STR:  0x7E

EXCEPTION_DOESNOT_MATCH_CODE:  This indicates a hardware error.
Instruction at fffff880011c44c1 does not read/write to 000000000000c531

LAST_CONTROL_TRANSFER:  from fffff880011c33a8 to fffff880011c44c1

STACK_TEXT:  
fffff880`03747a90 fffff880`011c33a8 : 00000000`00000000 fffff880`0d25e000 fffff880`037443e0 fffffa80`07df2078 : rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+0x441
fffff880`03747af0 fffff880`011c1582 : fffffa80`07df2078 00000000`00000010 00000000`00000010 00000000`00000070 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageFindSpace+0x34
fffff880`03747b20 fffff880`011c0757 : fffffa80`0890b320 fffffa80`092a1920 00000000`00000000 fffffa80`07df2078 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageAdd+0x2e
fffff880`03747be0 fffff880`011c0612 : fffffa80`0890b320 00000000`00010000 00000000`00000080 fffffa80`07df2010 : rdyboost!ST_STORE<SMD_TRAITS>::StDmPageAdd+0xe3
fffff880`03747c40 fffff880`011bf3fe : fffffa80`0890b320 00000000`00000080 00000000`00000080 fffffa80`07df2ee8 : rdyboost!ST_STORE<SMD_TRAITS>::StWorkItemProcess+0x23a
fffff880`03747ca0 fffff800`02d6b166 : 00000000`00000000 fffff800`00000000 fffffa80`07deba40 fffffa80`0730a9e0 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStWorker+0x152
fffff880`03747d00 fffff800`02aa6486 : fffff800`02c40e80 fffffa80`07deba40 fffffa80`07d44910 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03747d40 00000000`00000000 : fffff880`03748000 fffff880`03742000 fffff880`037477e0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+441

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rdyboost

IMAGE_NAME:  rdyboost.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc48a

STACK_COMMAND:  .cxr 0xfffff880037470b0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_CODE_ADDRESS_MISMATCH_rdyboost!ST_STORE_SMD_TRAITS_::StDmCurrentRegionFind+441

BUCKET_ID:  X64_0x7E_CODE_ADDRESS_MISMATCH_rdyboost!ST_STORE_SMD_TRAITS_::StDmCurrentRegionFind+441

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: fffff880011c44c1, The address that the exception occurred at
Arg3: fffff88003747858, Exception Record Address
Arg4: fffff880037470b0, 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!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+441
fffff880`011c44c1 413bc1          cmp     eax,r9d

EXCEPTION_RECORD:  fffff88003747858 -- (.exr 0xfffff88003747858)
ExceptionAddress: fffff880011c44c1 (rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+0x0000000000000441)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 000000000000c531
Attempt to write to address 000000000000c531

CONTEXT:  fffff880037470b0 -- (.cxr 0xfffff880037470b0)
rax=0000000000000000 rbx=0000000000008532 rcx=0000000000000000
rdx=fffffa8008242448 rsi=0000000000003fff rdi=fffffa80082619cc
rip=fffff880011c44c1 rsp=fffff88003747a90 rbp=fffffa8007df2078
 r8=fffffa8008252a64  r9=0000000000000200 r10=fffffa8008242000
r11=000000000000fce6 r12=fffffa8009726000 r13=00000000ffffffff
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+0x441:
fffff880`011c44c1 413bc1          cmp     eax,r9d
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:  0000000000000001

EXCEPTION_PARAMETER2:  000000000000c531

WRITE_ADDRESS:  000000000000c531 

FOLLOWUP_IP: 
rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+441
fffff880`011c44c1 413bc1          cmp     eax,r9d

BUGCHECK_STR:  0x7E

EXCEPTION_DOESNOT_MATCH_CODE:  This indicates a hardware error.
Instruction at fffff880011c44c1 does not read/write to 000000000000c531

LAST_CONTROL_TRANSFER:  from fffff880011c33a8 to fffff880011c44c1

STACK_TEXT:  
fffff880`03747a90 fffff880`011c33a8 : 00000000`00000000 fffff880`0d25e000 fffff880`037443e0 fffffa80`07df2078 : rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+0x441
fffff880`03747af0 fffff880`011c1582 : fffffa80`07df2078 00000000`00000010 00000000`00000010 00000000`00000070 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageFindSpace+0x34
fffff880`03747b20 fffff880`011c0757 : fffffa80`0890b320 fffffa80`092a1920 00000000`00000000 fffffa80`07df2078 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageAdd+0x2e
fffff880`03747be0 fffff880`011c0612 : fffffa80`0890b320 00000000`00010000 00000000`00000080 fffffa80`07df2010 : rdyboost!ST_STORE<SMD_TRAITS>::StDmPageAdd+0xe3
fffff880`03747c40 fffff880`011bf3fe : fffffa80`0890b320 00000000`00000080 00000000`00000080 fffffa80`07df2ee8 : rdyboost!ST_STORE<SMD_TRAITS>::StWorkItemProcess+0x23a
fffff880`03747ca0 fffff800`02d6b166 : 00000000`00000000 fffff800`00000000 fffffa80`07deba40 fffffa80`0730a9e0 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStWorker+0x152
fffff880`03747d00 fffff800`02aa6486 : fffff800`02c40e80 fffffa80`07deba40 fffffa80`07d44910 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03747d40 00000000`00000000 : fffff880`03748000 fffff880`03742000 fffff880`037477e0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+441

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rdyboost

IMAGE_NAME:  rdyboost.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc48a

STACK_COMMAND:  .cxr 0xfffff880037470b0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_CODE_ADDRESS_MISMATCH_rdyboost!ST_STORE_SMD_TRAITS_::StDmCurrentRegionFind+441

BUCKET_ID:  X64_0x7E_CODE_ADDRESS_MISMATCH_rdyboost!ST_STORE_SMD_TRAITS_::StDmCurrentRegionFind+441

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: fffff880011c44c1, The address that the exception occurred at
Arg3: fffff88003747858, Exception Record Address
Arg4: fffff880037470b0, 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!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+441
fffff880`011c44c1 413bc1          cmp     eax,r9d

EXCEPTION_RECORD:  fffff88003747858 -- (.exr 0xfffff88003747858)
ExceptionAddress: fffff880011c44c1 (rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+0x0000000000000441)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 000000000000c531
Attempt to write to address 000000000000c531

CONTEXT:  fffff880037470b0 -- (.cxr 0xfffff880037470b0)
rax=0000000000000000 rbx=0000000000008532 rcx=0000000000000000
rdx=fffffa8008242448 rsi=0000000000003fff rdi=fffffa80082619cc
rip=fffff880011c44c1 rsp=fffff88003747a90 rbp=fffffa8007df2078
 r8=fffffa8008252a64  r9=0000000000000200 r10=fffffa8008242000
r11=000000000000fce6 r12=fffffa8009726000 r13=00000000ffffffff
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+0x441:
fffff880`011c44c1 413bc1          cmp     eax,r9d
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:  0000000000000001

EXCEPTION_PARAMETER2:  000000000000c531

WRITE_ADDRESS:  000000000000c531 

FOLLOWUP_IP: 
rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+441
fffff880`011c44c1 413bc1          cmp     eax,r9d

BUGCHECK_STR:  0x7E

EXCEPTION_DOESNOT_MATCH_CODE:  This indicates a hardware error.
Instruction at fffff880011c44c1 does not read/write to 000000000000c531

LAST_CONTROL_TRANSFER:  from fffff880011c33a8 to fffff880011c44c1

STACK_TEXT:  
fffff880`03747a90 fffff880`011c33a8 : 00000000`00000000 fffff880`0d25e000 fffff880`037443e0 fffffa80`07df2078 : rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+0x441
fffff880`03747af0 fffff880`011c1582 : fffffa80`07df2078 00000000`00000010 00000000`00000010 00000000`00000070 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageFindSpace+0x34
fffff880`03747b20 fffff880`011c0757 : fffffa80`0890b320 fffffa80`092a1920 00000000`00000000 fffffa80`07df2078 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageAdd+0x2e
fffff880`03747be0 fffff880`011c0612 : fffffa80`0890b320 00000000`00010000 00000000`00000080 fffffa80`07df2010 : rdyboost!ST_STORE<SMD_TRAITS>::StDmPageAdd+0xe3
fffff880`03747c40 fffff880`011bf3fe : fffffa80`0890b320 00000000`00000080 00000000`00000080 fffffa80`07df2ee8 : rdyboost!ST_STORE<SMD_TRAITS>::StWorkItemProcess+0x23a
fffff880`03747ca0 fffff800`02d6b166 : 00000000`00000000 fffff800`00000000 fffffa80`07deba40 fffffa80`0730a9e0 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStWorker+0x152
fffff880`03747d00 fffff800`02aa6486 : fffff800`02c40e80 fffffa80`07deba40 fffffa80`07d44910 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03747d40 00000000`00000000 : fffff880`03748000 fffff880`03742000 fffff880`037477e0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionFind+441

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rdyboost

IMAGE_NAME:  rdyboost.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc48a

STACK_COMMAND:  .cxr 0xfffff880037470b0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_CODE_ADDRESS_MISMATCH_rdyboost!ST_STORE_SMD_TRAITS_::StDmCurrentRegionFind+441

BUCKET_ID:  X64_0x7E_CODE_ADDRESS_MISMATCH_rdyboost!ST_STORE_SMD_TRAITS_::StDmCurrentRegionFind+441

Followup: MachineOwner
---------
Drivers
HTML Code:
0: kd> lmtsmn
start             end                 module name
fffff880`04b64000 fffff880`04ba2000   1394ohci 1394ohci.sys Mon Jul 13 19:07:12 2009 (4A5BCC30)
fffff880`00f1a000 fffff880`00f71000   ACPI     ACPI.sys     Mon Jul 13 18:19:34 2009 (4A5BC106)
fffff880`02c9a000 fffff880`02d24000   afd      afd.sys      Mon Jul 13 18:21:40 2009 (4A5BC184)
fffff880`042dc000 fffff880`042f2000   AgileVpn AgileVpn.sys Mon Jul 13 19:10:24 2009 (4A5BCCF0)
fffff880`00deb000 fffff880`00df6000   amdxata  amdxata.sys  Tue May 19 12:56:59 2009 (4A12F2EB)
fffff880`00e2f000 fffff880`00e38000   atapi    atapi.sys    Mon Jul 13 18:19:47 2009 (4A5BC113)
fffff880`00e38000 fffff880`00e62000   ataport  ataport.SYS  Mon Jul 13 18:19:52 2009 (4A5BC118)
fffff880`00fe2000 fffff880`00fee000   BATTC    BATTC.SYS    Mon Jul 13 18:31:01 2009 (4A5BC3B5)
fffff880`03a6b000 fffff880`03a74000   bcmvwl64 bcmvwl64.sys Thu Jan 21 21:28:30 2010 (4B591B5E)
fffff880`04868000 fffff880`04b57000   bcmwl664 bcmwl664.sys Thu Jan 21 21:30:58 2010 (4B591BF2)
fffff880`01941000 fffff880`01948000   Beep     Beep.SYS     Mon Jul 13 19:00:13 2009 (4A5BCA8D)
fffff880`03b7d000 fffff880`03b8e000   blbdrive blbdrive.sys Mon Jul 13 18:35:59 2009 (4A5BC4DF)
fffff960`006c0000 fffff960`006e7000   cdd      cdd.dll      unavailable (00000000)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Mon Jul 13 20:32:13 2009 (4A5BE01D)
fffff880`0189f000 fffff880`018cf000   CLASSPNP CLASSPNP.SYS Mon Jul 13 18:19:58 2009 (4A5BC11E)
fffff880`00d21000 fffff880`00d7f000   CLFS     CLFS.SYS     Mon Jul 13 18:19:57 2009 (4A5BC11D)
fffff880`04bf8000 fffff880`04bfc500   CmBatt   CmBatt.sys   Mon Jul 13 18:31:03 2009 (4A5BC3B7)
fffff880`01000000 fffff880`01073000   cng      cng.sys      Mon Jul 13 18:49:40 2009 (4A5BC814)
fffff880`00fd9000 fffff880`00fe2000   compbatt compbatt.sys Mon Jul 13 18:31:02 2009 (4A5BC3B6)
fffff880`042cc000 fffff880`042dc000   CompositeBus CompositeBus.sys Mon Jul 13 19:00:33 2009 (4A5BCAA1)
fffff880`04f51000 fffff880`04f5f000   crashdmp crashdmp.sys Mon Jul 13 19:01:01 2009 (4A5BCABD)
fffff880`03adc000 fffff880`03b5f000   csc      csc.sys      Mon Jul 13 18:24:26 2009 (4A5BC22A)
fffff880`03b5f000 fffff880`03b7d000   dfsc     dfsc.sys     Mon Jul 13 18:23:44 2009 (4A5BC200)
fffff880`02c68000 fffff880`02c77000   discache discache.sys Mon Jul 13 18:37:18 2009 (4A5BC52E)
fffff880`01889000 fffff880`0189f000   disk     disk.sys     Mon Jul 13 18:19:57 2009 (4A5BC11D)
fffff880`04f29000 fffff880`04f4b000   drmk     drmk.sys     Mon Jul 13 20:01:25 2009 (4A5BD8E5)
fffff880`04f5f000 fffff880`04f6b000   dump_dumpata dump_dumpata.sys Mon Jul 13 18:19:47 2009 (4A5BC113)
fffff880`04f76000 fffff880`04f89000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 18:21:51 2009 (4A5BC18F)
fffff880`04f6b000 fffff880`04f76000   dump_msahci dump_msahci.sys Mon Jul 13 19:01:01 2009 (4A5BCABD)
fffff880`04f89000 fffff880`04f95000   Dxapi    Dxapi.sys    Mon Jul 13 18:38:28 2009 (4A5BC574)
fffff880`042f2000 fffff880`043e6000   dxgkrnl  dxgkrnl.sys  Mon Jul 13 18:38:56 2009 (4A5BC590)
fffff880`04200000 fffff880`04246000   dxgmms1  dxgmms1.sys  Mon Jul 13 18:38:32 2009 (4A5BC578)
fffff880`0113f000 fffff880`01153000   fileinfo fileinfo.sys Mon Jul 13 18:34:25 2009 (4A5BC481)
fffff880`010f3000 fffff880`0113f000   fltmgr   fltmgr.sys   Mon Jul 13 18:19:59 2009 (4A5BC11F)
fffff880`01200000 fffff880`0120a000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 18:19:45 2009 (4A5BC111)
fffff880`0184f000 fffff880`01889000   fvevol   fvevol.sys   Mon Jul 13 18:22:15 2009 (4A5BC1A7)
fffff880`0148b000 fffff880`014d5000   fwpkclnt fwpkclnt.sys Mon Jul 13 18:21:08 2009 (4A5BC164)
fffff800`02a0d000 fffff800`02a56000   hal      hal.dll      Mon Jul 13 20:27:36 2009 (4A5BDF08)
fffff880`03bc2000 fffff880`03be6000   HDAudBus HDAudBus.sys Mon Jul 13 19:06:13 2009 (4A5BCBF5)
fffff880`04e90000 fffff880`04eec000   HdAudio  HdAudio.sys  Mon Jul 13 19:06:59 2009 (4A5BCC23)
fffff880`04e00000 fffff880`04e19000   HIDCLASS HIDCLASS.SYS Mon Jul 13 19:06:21 2009 (4A5BCBFD)
fffff880`03be6000 fffff880`03bee080   HIDPARSE HIDPARSE.SYS Mon Jul 13 19:06:17 2009 (4A5BCBF9)
fffff880`04ff0000 fffff880`04ffe000   hidusb   hidusb.sys   Mon Jul 13 19:06:22 2009 (4A5BCBFE)
fffff880`015f1000 fffff880`015fa000   hwpolicy hwpolicy.sys Mon Jul 13 18:19:22 2009 (4A5BC0FA)
fffff880`04800000 fffff880`0481e000   i8042prt i8042prt.sys Mon Jul 13 18:19:57 2009 (4A5BC11D)
fffff880`03c27000 fffff880`041fa500   igdkmd64 igdkmd64.sys Wed May 06 13:22:19 2009 (4A01D55B)
fffff880`04845000 fffff880`0485b000   intelppm intelppm.sys Mon Jul 13 18:19:25 2009 (4A5BC0FD)
fffff880`04ba2000 fffff880`04bc9000   jmcr     jmcr.sys     Tue Aug 18 03:23:06 2009 (4A8A64EA)
fffff880`0481e000 fffff880`0482d000   kbdclass kbdclass.sys Mon Jul 13 18:19:50 2009 (4A5BC116)
fffff800`00b9e000 fffff800`00ba8000   kdcom    kdcom.dll    Mon Jul 13 20:31:07 2009 (4A5BDFDB)
fffff880`03a7f000 fffff880`03ac2000   ks       ks.sys       Mon Jul 13 19:00:31 2009 (4A5BCA9F)
fffff880`013ce000 fffff880`013e8000   ksecdd   ksecdd.sys   Mon Jul 13 18:20:54 2009 (4A5BC156)
fffff880`01460000 fffff880`0148b000   ksecpkg  ksecpkg.sys  Mon Jul 13 18:50:34 2009 (4A5BC84A)
fffff880`04f4b000 fffff880`04f50200   ksthunk  ksthunk.sys  Mon Jul 13 19:00:19 2009 (4A5BCA93)
fffff880`042ba000 fffff880`042cc000   L1C62x64 L1C62x64.sys Wed Apr 01 00:09:17 2009 (49D2F6FD)
fffff880`00cc9000 fffff880`00d0d000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 20:29:10 2009 (4A5BDF66)
fffff880`04f95000 fffff880`04fa3000   monitor  monitor.sys  Mon Jul 13 18:38:52 2009 (4A5BC58C)
fffff880`0482d000 fffff880`0483c000   mouclass mouclass.sys Mon Jul 13 18:19:50 2009 (4A5BC116)
fffff880`03bef000 fffff880`03bfc000   mouhid   mouhid.sys   Mon Jul 13 19:00:20 2009 (4A5BCA94)
fffff880`00e15000 fffff880`00e2f000   mountmgr mountmgr.sys Mon Jul 13 18:19:54 2009 (4A5BC11A)
fffff880`01907000 fffff880`01938000   MpFilter MpFilter.sys Tue Sep 14 19:19:28 2010 (4C901110)
fffff880`00fee000 fffff880`00ff9000   msahci   msahci.sys   Mon Jul 13 19:01:01 2009 (4A5BCABD)
fffff880`019a6000 fffff880`019b1000   Msfs     Msfs.SYS     Mon Jul 13 18:19:47 2009 (4A5BC113)
fffff880`00f7a000 fffff880`00f84000   msisadrv msisadrv.sys Mon Jul 13 18:19:26 2009 (4A5BC0FE)
fffff880`01153000 fffff880`011b1000   msrpc    msrpc.sys    Mon Jul 13 18:21:32 2009 (4A5BC17C)
fffff880`02c5d000 fffff880`02c68000   mssmbios mssmbios.sys Mon Jul 13 18:31:10 2009 (4A5BC3BE)
fffff880`014ed000 fffff880`014ff000   mup      mup.sys      Mon Jul 13 18:23:45 2009 (4A5BC201)
fffff880`014ff000 fffff880`015f1000   ndis     ndis.sys     Mon Jul 13 18:21:40 2009 (4A5BC184)
fffff880`0485b000 fffff880`04867000   ndistapi ndistapi.sys Mon Jul 13 19:10:00 2009 (4A5BCCD8)
fffff880`03a00000 fffff880`03a2f000   ndiswan  ndiswan.sys  Mon Jul 13 19:10:11 2009 (4A5BCCE3)
fffff880`04e7b000 fffff880`04e90000   NDProxy  NDProxy.SYS  Mon Jul 13 19:10:05 2009 (4A5BCCDD)
fffff880`02dae000 fffff880`02dbd000   netbios  netbios.sys  Mon Jul 13 19:09:26 2009 (4A5BCCB6)
fffff880`02d24000 fffff880`02d69000   netbt    netbt.sys    Mon Jul 13 18:21:28 2009 (4A5BC178)
fffff880`01400000 fffff880`01460000   NETIO    NETIO.SYS    Thu Apr 08 21:43:59 2010 (4BBE946F)
fffff880`019b1000 fffff880`019c2000   Npfs     Npfs.SYS     Mon Jul 13 18:19:48 2009 (4A5BC114)
fffff880`02c51000 fffff880`02c5d000   nsiproxy nsiproxy.sys Mon Jul 13 18:21:02 2009 (4A5BC15E)
fffff800`02a56000 fffff800`03033000   nt       ntkrnlmp.exe Mon Jul 13 18:40:48 2009 (4A5BC600)
fffff880`0122b000 fffff880`013ce000   Ntfs     Ntfs.sys     Mon Jul 13 18:20:47 2009 (4A5BC14F)
fffff880`01938000 fffff880`01941000   Null     Null.SYS     Mon Jul 13 18:19:37 2009 (4A5BC109)
fffff880`02d72000 fffff880`02d98000   pacer    pacer.sys    Mon Jul 13 19:09:41 2009 (4A5BCCC5)
fffff880`00fc4000 fffff880`00fd9000   partmgr  partmgr.sys  Mon Jul 13 18:19:58 2009 (4A5BC11E)
fffff880`00f84000 fffff880`00fb7000   pci      pci.sys      Mon Jul 13 18:19:51 2009 (4A5BC117)
fffff880`00ddb000 fffff880`00deb000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 18:19:48 2009 (4A5BC114)
fffff880`013e8000 fffff880`013f9000   pcw      pcw.sys      Mon Jul 13 18:19:27 2009 (4A5BC0FF)
fffff880`04eec000 fffff880`04f29000   portcls  portcls.sys  Mon Jul 13 19:06:27 2009 (4A5BCC03)
fffff880`00d0d000 fffff880`00d21000   PSHED    PSHED.dll    Mon Jul 13 20:32:23 2009 (4A5BE027)
fffff880`03c00000 fffff880`03c24000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:10:11 2009 (4A5BCCE3)
fffff880`03a2f000 fffff880`03a4a000   raspppoe raspppoe.sys Mon Jul 13 19:10:17 2009 (4A5BCCE9)
fffff880`03a4a000 fffff880`03a6b000   raspptp  raspptp.sys  Mon Jul 13 19:10:18 2009 (4A5BCCEA)
fffff880`043e6000 fffff880`04400000   rassstp  rassstp.sys  Mon Jul 13 19:10:25 2009 (4A5BCCF1)
fffff880`02c00000 fffff880`02c51000   rdbss    rdbss.sys    Mon Jul 13 18:24:09 2009 (4A5BC219)
fffff880`03a74000 fffff880`03a7f000   rdpbus   rdpbus.sys   Mon Jul 13 19:17:46 2009 (4A5BCEAA)
fffff880`0198b000 fffff880`01994000   RDPCDD   RDPCDD.sys   Mon Jul 13 19:16:34 2009 (4A5BCE62)
fffff880`01994000 fffff880`0199d000   rdpencdd rdpencdd.sys Mon Jul 13 19:16:34 2009 (4A5BCE62)
fffff880`0199d000 fffff880`019a6000   rdprefmp rdprefmp.sys Mon Jul 13 19:16:35 2009 (4A5BCE63)
fffff880`011b1000 fffff880`011eb000   rdyboost rdyboost.sys Mon Jul 13 18:34:34 2009 (4A5BC48A)
fffff880`04bc9000 fffff880`04bf8000   SCSIPORT SCSIPORT.SYS Mon Jul 13 19:01:04 2009 (4A5BCAC0)
fffff880`014e5000 fffff880`014ed000   spldr    spldr.sys    Mon May 11 11:56:27 2009 (4A0858BB)
fffff880`04bfd000 fffff880`04bfe480   swenum   swenum.sys   Mon Jul 13 19:00:18 2009 (4A5BCA92)
fffff880`01601000 fffff880`017fe000   tcpip    tcpip.sys    Thu Apr 08 21:45:54 2010 (4BBE94E2)
fffff880`019e0000 fffff880`019ed000   TDI      TDI.SYS      Mon Jul 13 18:21:18 2009 (4A5BC16E)
fffff880`019c2000 fffff880`019e0000   tdx      tdx.sys      Mon Jul 13 18:21:15 2009 (4A5BC16B)
fffff880`02dd8000 fffff880`02dec000   termdd   termdd.sys   Mon Jul 13 19:16:36 2009 (4A5BCE64)
fffff960`00510000 fffff960`0051a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`03b8e000 fffff880`03bb4000   tunnel   tunnel.sys   Mon Jul 13 19:09:37 2009 (4A5BCCC1)
fffff880`03ac2000 fffff880`03ad4000   umbus    umbus.sys    Mon Jul 13 19:06:56 2009 (4A5BCC20)
fffff880`04fa3000 fffff880`04fc0000   usbccgp  usbccgp.sys  Mon Jul 13 19:06:45 2009 (4A5BCC15)
fffff880`04fc0000 fffff880`04fc1f00   USBD     USBD.SYS     Mon Jul 13 19:06:23 2009 (4A5BCBFF)
fffff880`042a9000 fffff880`042ba000   usbehci  usbehci.sys  Mon Jul 13 19:06:30 2009 (4A5BCC06)
fffff880`04e21000 fffff880`04e7b000   usbhub   usbhub.sys   Mon Jul 13 19:07:09 2009 (4A5BCC2D)
fffff880`04253000 fffff880`042a9000   USBPORT  USBPORT.SYS  Mon Jul 13 19:06:31 2009 (4A5BCC07)
fffff880`04246000 fffff880`04253000   usbuhci  usbuhci.sys  Mon Jul 13 19:06:27 2009 (4A5BCC03)
fffff880`04fc2000 fffff880`04fef100   usbvideo usbvideo.sys Mon Jul 13 19:07:00 2009 (4A5BCC24)
fffff880`00fb7000 fffff880`00fc4000   vdrvroot vdrvroot.sys Mon Jul 13 19:01:31 2009 (4A5BCADB)
fffff880`01948000 fffff880`01956000   vga      vga.sys      Mon Jul 13 18:38:47 2009 (4A5BC587)
fffff880`03bb4000 fffff880`03bc2000   vgapnp   vgapnp.sys   Mon Jul 13 18:38:47 2009 (4A5BC587)
fffff880`01956000 fffff880`0197b000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 18:38:51 2009 (4A5BC58B)
fffff880`014d5000 fffff880`014e5000   vmstorfl vmstorfl.sys Mon Jul 13 18:42:54 2009 (4A5BC67E)
fffff880`00e00000 fffff880`00e15000   volmgr   volmgr.sys   Mon Jul 13 18:19:57 2009 (4A5BC11D)
fffff880`00d7f000 fffff880`00ddb000   volmgrx  volmgrx.sys  Mon Jul 13 18:20:33 2009 (4A5BC141)
fffff880`01073000 fffff880`010bf000   volsnap  volsnap.sys  Mon Jul 13 18:20:08 2009 (4A5BC128)
fffff880`04b57000 fffff880`04b64000   vwifibus vwifibus.sys Mon Jul 13 19:07:21 2009 (4A5BCC39)
fffff880`02d98000 fffff880`02dae000   vwififlt vwififlt.sys Mon Jul 13 19:07:22 2009 (4A5BCC3A)
fffff880`02dbd000 fffff880`02dd8000   wanarp   wanarp.sys   Mon Jul 13 19:10:21 2009 (4A5BCCED)
fffff880`0197b000 fffff880`0198b000   watchdog watchdog.sys Mon Jul 13 18:37:35 2009 (4A5BC53F)
fffff880`00e67000 fffff880`00f0b000   Wdf01000 Wdf01000.sys Mon Jul 13 18:22:07 2009 (4A5BC19F)
fffff880`00f0b000 fffff880`00f1a000   WDFLDR   WDFLDR.SYS   Mon Jul 13 18:19:54 2009 (4A5BC11A)
fffff880`02d69000 fffff880`02d72000   wfplwf   wfplwf.sys   Mon Jul 13 19:09:26 2009 (4A5BCCB6)
fffff960`00080000 fffff960`0038f000   win32k   win32k.sys   unavailable (00000000)
fffff880`0483c000 fffff880`04845000   wmiacpi  wmiacpi.sys  Mon Jul 13 18:31:02 2009 (4A5BC3B6)
fffff880`00f71000 fffff880`00f7a000   WMILIB   WMILIB.SYS   Mon Jul 13 18:19:51 2009 (4A5BC117)

Unloaded modules:
fffff880`018cf000 fffff880`018dd000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`018dd000 fffff880`018e9000   dump_pciidex
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`018e9000 fffff880`018f4000   dump_msahci.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000B000
fffff880`018f4000 fffff880`01907000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000
My System SpecsSystem Spec
30 Jan 2011   #3
Tek86

Windows 7 Professional x64
 
 

I renamed rdyboost.sys to rdyboost.bak using the takeown and cacls command. I then restarted laptop and it goes straight into startup repair. I also deleted rdyboost.sys using the same commands as above and got the same results, startup repair repairs the file to its original state.
My System SpecsSystem Spec
.

30 Jan 2011   #4
TonyTiger2004

Windows 7 Ultimate x64
 
 

Next step is to go into your drives and make sure that readyboost is disabled.

I just think the hardware of your laptop isn't going to let you overclock. I dont think readyboost is the actual issue here. But if it is and u make sure its turned off that should do the trick. Otherwise its Hardware related or so it seems.

- Tony
My System SpecsSystem Spec
Reply

 Bsod




Thread Tools



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 03:57.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App