BSOD 0x1000007e for ntoskrnl.exe after Sys Recovery Disks reinstall

Please remove BitDefender and use MSE in its place.

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability
compared to other antivirus or internet security software. It is free and lightweight:-

• Microsoft Security Essentials - Free Antivirus for Windows
• Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer
• Good and Free system security combination.
• How to Scan Your Computer With Multiple Antivirus Programs - How-To Geek

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Free up the start-up, nothing except the antivirus is usually needed.

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

Check for heating issues using Speccy or HWMonitor. Upload a screen shot with either of the tools:

• Speccy - System Information - Free Download
• HWMonitor CPUID - System & hardware benchmark, monitoring, reporting
• Screenshots and Files - Upload and Post in Seven Forums

Run Disk Check on your Hard Drive for file system errors and bad sectors on it:

• How to Run Disk Check in Windows 7

Upload a screenshot of your hard disk using Crystal Disk Info:

• CrystalDiskInfo - Software - Crystal Dew World
• Screenshots and Files - Upload and Post in Seven Forums

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

Test your Hard Drive with SeaTools:

• How to Use SeaTools for DOS and Windows Disk Check Utility

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Memtest should be done overnight.

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\zarathud\SF_07-07-2014\070714-14133-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 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02c4c000 PsLoadedModuleList = 0xfffff800`02e8f890
Debug session time: Tue Jul  8 06:55:13.520 2014 (UTC + 6:00)
System Uptime: 0 days 0:00:27.551
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002ce7150, fffff880030be5c8, fffff880030bde20}

Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+9b )

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: fffff80002ce7150, The address that the exception occurred at
Arg3: fffff880030be5c8, Exception Record Address
Arg4: fffff880030bde20, 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: 
nt!MiReplenishPageSlist+c0
fffff800`02ce7150 f00fba6b1000    lock bts dword ptr [rbx+10h],0

EXCEPTION_RECORD:  fffff880030be5c8 -- (.exr 0xfffff880030be5c8)
ExceptionAddress: fffff80002ce7150 (nt!MiReplenishPageSlist+0x00000000000000c0)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880030bde20 -- (.cxr 0xfffff880030bde20)
rax=fffffa8009d43740 rbx=fffef281d7ca5c00 rcx=0000058000000000
rdx=0000000000000050 rsi=0000000000000002 rdi=000000000000000e
rip=fffff80002ce7150 rsp=fffff880030be800 rbp=fffffa80088404f0
 r8=fffff80002efc500  r9=fffffa8009c00000 r10=000000000033ffff
r11=0000000000000000 r12=fffff80002efc500 r13=2aaaaaaaaaaaaaab
r14=fdffffffffffffff r15=0000058000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!MiReplenishPageSlist+0xc0:
fffff800`02ce7150 f00fba6b1000    lock bts dword ptr [rbx+10h],0 ds:002b:fffef281`d7ca5c10=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

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 fffff80002ef9100
GetUlongFromAddress: unable to read from fffff80002ef91c0
 ffffffffffffffff 

FOLLOWUP_IP: 
rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+9b
fffff880`013bbfd3 488be8          mov     rbp,rax

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002de44fc to fffff80002ce7150

STACK_TEXT:  
fffff880`030be800 fffff800`02de44fc : fffffa80`09c00aa0 00000000`00000010 00000000`00000044 00000000`00000044 : nt!MiReplenishPageSlist+0xc0
fffff880`030be870 fffff800`02de4d11 : 00000000`00000080 00000000`00000020 00000000`00000000 00000000`0033ffff : nt!MiAllocateMdlPagesByLists+0x60c
fffff880`030be9a0 fffff800`02de5619 : 00000000`00000001 fffffa80`0ae7a000 00000000`00000474 00000000`00000001 : nt!MiAllocatePagesForMdl+0x451
fffff880`030bea90 fffff880`013bbfd3 : fffffa80`0ae78118 fffff880`013c9519 00000000`00000001 fffff880`056ef000 : nt!MmAllocatePagesForMdlEx+0x89
fffff880`030bead0 fffff880`013c93da : fffffa80`0ae78118 fffffa80`0ae78118 fffff880`030bc3e0 fffffa80`0ae78118 : rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+0x9b
fffff880`030beb30 fffff880`013c759e : fffffa80`0ae78118 00000000`00000010 00000000`00000010 00000000`00000001 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageFindSpace+0x4a
fffff880`030beb60 fffff880`013c6773 : fffffa80`0c47d150 fffffa80`0cf06170 00000000`00000000 fffffa80`0ae78118 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageAdd+0x2e
fffff880`030bec20 fffff880`013c662e : fffffa80`0c47d150 00000000`00010000 00000000`00000080 fffffa80`0ae780b0 : rdyboost!ST_STORE<SMD_TRAITS>::StDmPageAdd+0xe3
fffff880`030bec80 fffff880`013c541a : fffffa80`0c47d150 00000000`00000080 00000000`00000080 fffffa80`0ae78f88 : rdyboost!ST_STORE<SMD_TRAITS>::StWorkItemProcess+0x23a
fffff880`030bece0 fffff800`02f5d73a : 00000000`00000000 fffff800`00000000 fffffa80`0ad50b50 fffffa80`09d43740 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStWorker+0x152
fffff880`030bed40 fffff800`02cb28e6 : fffff800`02e3ce80 fffffa80`0ad50b50 fffff800`02e4acc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`030bed80 00000000`00000000 : fffff880`030bf000 fffff880`030b9000 fffff880`030be810 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+9b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rdyboost

IMAGE_NAME:  rdyboost.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7982e

STACK_COMMAND:  .cxr 0xfffff880030bde20 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_rdyboost!ST_STORE_SMD_TRAITS_::StDmCurrentRegionSet+9b

BUCKET_ID:  X64_0x7E_rdyboost!ST_STORE_SMD_TRAITS_::StDmCurrentRegionSet+9b

Followup: MachineOwner
---------

Interesting KK as I asked for the memtest, HDD test and chkdsk stuff in the other thread but it wasn't followed up.
I also suggested a clean install using Greg's tutorial as it seemed to me the disks being used were somehow "off".
I wish I could read the dump files properly as I am sure there must be stuff in there.

ICit2lol said:

Interesting KK as I asked for the memtest, HDD test and chkdsk stuff in the other thread but it wasn't followed up.
I also suggested a clean install using Greg's tutorial as it seemed to me the disks being used were somehow "off".
I wish I could read the dump files properly as I am sure there must be stuff in there.

My apologies/

koolkat77 said:

ICit2lol said:

Interesting KK as I asked for the memtest, HDD test and chkdsk stuff in the other thread but it wasn't followed up.
I also suggested a clean install using Greg's tutorial as it seemed to me the disks being used were somehow "off".
I wish I could read the dump files properly as I am sure there must be stuff in there.

My apologies/

No worries and Zarathud mate the volts look ok but the temps on the cores seem to be a little on the high side for my liking although I suppose it does depend on the ambient temperature of where you are.

As suggested by Kool Kat that memtest will be interesting to see the results.

After looking at the memtest and the HW Info readout I still think the cores are a little on the high side I know the memtest is probably not that accurate but if you take the mid way point between the HW and memtest results you are getting around 78C.
That would have me changing the compound at the very least. Volts still ok so having a rethink.