Welcome to SF.
Dump files point towards hardware issues.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050033, 6f8, fffff80003abd527}
Probably caused by : hardware ( nt!KiDoubleFaultAbort+b2 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000006f8
Arg4: fffff80003abd527
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: ccsvchst.exe
CURRENT_IRQL: 0
EXCEPTION_RECORD: fffff8800c8ed318 -- (.exr 0xfffff8800c8ed318)
ExceptionAddress: fffff80003a59c01 (nt!_GSHandlerCheckCommon+0x0000000000000035)
ExceptionCode: 10000004
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 00000000000000eb
TRAP_FRAME: fffff8800c8ed3c0 -- (.trap 0xfffff8800c8ed3c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000160 rbx=0000000000000000 rcx=fffff8800c8ef340
rdx=000004e8fffffb30 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003a59c01 rsp=fffff8800c8ed550 rbp=fffff8800c8ee498
r8=fffff80003bd0028 r9=fffff8800c8ef340 r10=fffff8800c8ef340
r11=0000000000000160 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!_GSHandlerCheckCommon+0x35:
fffff800`03a59c01 10488b adc byte ptr [rax-75h],cl ds:00000000`000000eb=??
Resetting default scope
MISALIGNED_IP:
nt!_GSHandlerCheckCommon+35
fffff800`03a59c01 10488b adc byte ptr [rax-75h],cl
LAST_CONTROL_TRANSFER: from fffff80003a821e9 to fffff80003a82c40
STACK_TEXT:
fffff880`009b8de8 fffff800`03a821e9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009b8df0 fffff800`03a806b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009b8f30 fffff800`03abd527 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0c8ecb40 fffff800`03a822c2 : fffff880`0c8ed318 fffff880`0c8ed670 fffff880`0c8ed3c0 fffff880`0c8ef340 : nt!KiDispatchException+0xab
fffff880`0c8ed1e0 fffff800`03a80e3a : 00000000`00000001 00000000`000000eb 145a86a4`008b2200 fffff880`0c8ed670 : nt!KiExceptionDispatch+0xc2
fffff880`0c8ed3c0 fffff800`03a59c01 : 4626ea33`8427988a 65337496`90c133ae 6ab6bc85`33d74d52 fffff800`03aad92b : nt!KiPageFault+0x23a
fffff880`0c8ed550 fffff800`03a59c7a : 7202e7cb`ab43335c 419d4b17`00ac17d4 fffff880`0c8edcf0 fffff800`03aadb80 : nt!_GSHandlerCheckCommon+0x35
fffff880`0c8ed580 fffff800`03aad84d : fffff800`03bd0014 00000000`00000000 fffff800`03a0d000 00000000`00000000 : nt!_GSHandlerCheck_SEH+0x42
fffff880`0c8ed5b0 fffff800`03aac625 : fffff800`03bd0014 fffff880`0c8ed628 fffff880`0c8ee498 fffff800`03a0d000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0c8ed5e0 fffff800`03abd5b1 : fffff880`0c8ee498 fffff880`0c8edcf0 fffff880`00000010 fffff880`0c8ee7f0 : nt!RtlDispatchException+0x415
fffff880`0c8edcc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x135
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`03a806b2 90 nop
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiDoubleFaultAbort+b2
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
Code:
STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Usual causes: Memory corruption, Hardware (memory in particular), Overclocking
failure, Installing a faulty or mismatched hardware (especially memory) or a
failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS
updates needed, Improperly seated cards, Incompatible storage devices,
Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack
If you are overclocking any hardware, STOP. Reset any changed values back to default.
Code:
Start Menu\Programs\Norton Internet Security Public:Start Menu\Programs\Norton Internet Security Public
Norton tends to cause BSOD-s. Recommend uninstalling it with the Norton Removal Tool and replace with Microsoft Security Essentials. See if this stops the BSOD-s.
Microsoft Security Essentials.
Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-
Warning
:ar: Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.
Run a full scan with both (separately) once downloaded, installed and updated.
Perform a System File Check to check the integrity of all protected
Windows 7 :
- Click on the start
rb:
- Type CMD on Search
- Left click and Run as Administrator
- Type
Full tutorial here:
Disk Check on your hard drive for file system errors and bad sectors on it.
Reduce items at start-up. Nothing except anti-virus is required plus improves the time for logging in windows.
For monitoring the heat/celsius of the system, use Speccy or HWMonitor:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff800030b04f0, fffff880032be5c8, fffff880032bde20}
Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+9b )
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: fffff800030b04f0, The address that the exception occurred at
Arg3: fffff880032be5c8, Exception Record Address
Arg4: fffff880032bde20, 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`030b04f0 f00fba6b1000 lock bts dword ptr [rbx+10h],0
EXCEPTION_RECORD: fffff880032be5c8 -- (.exr 0xfffff880032be5c8)
ExceptionAddress: fffff800030b04f0 (nt!MiReplenishPageSlist+0x00000000000000c0)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880032bde20 -- (.cxr 0xfffff880032bde20)
rax=fffffa80087ff0f0 rbx=fffef28197fd2d00 rcx=0000058000000000
rdx=0000000000000050 rsi=0000000000000004 rdi=000000000000000c
rip=fffff800030b04f0 rsp=fffff880032be800 rbp=fffffa80088008f0
r8=fffff800032bd500 r9=fffffa8009c00000 r10=000000000033ffff
r11=0000000000000000 r12=fffff800032bd500 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`030b04f0 f00fba6b1000 lock bts dword ptr [rbx+10h],0 ds:002b:fffef281`97fd2d10=????????
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 fffff800032ba100
GetUlongFromAddress: unable to read from fffff800032ba1c0
ffffffffffffffff
FOLLOWUP_IP:
rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+9b
fffff880`01cf6fd3 488be8 mov rbp,rax
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff800031a4bac to fffff800030b04f0
STACK_TEXT:
fffff880`032be800 fffff800`031a4bac : fffffa80`09c000c8 00000000`00000004 00000000`00000005 00000000`00000005 : nt!MiReplenishPageSlist+0xc0
fffff880`032be870 fffff800`031a53c1 : 00000000`00000080 00000000`00000020 00000000`00000000 00000000`0033ffff : nt!MiAllocateMdlPagesByLists+0x60c
fffff880`032be9a0 fffff800`031a5cc9 : 00000000`00000001 fffffa80`0ae50000 00000000`0000027d 00000000`00000001 : nt!MiAllocatePagesForMdl+0x451
fffff880`032bea90 fffff880`01cf6fd3 : fffffa80`0ae4f118 fffff880`01d04519 00000000`00000001 fffff880`031a0000 : nt!MmAllocatePagesForMdlEx+0x89
fffff880`032bead0 fffff880`01d043da : fffffa80`0ae4f118 fffffa80`0ae4f118 fffff880`032bc3e0 fffffa80`0ae4f118 : rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+0x9b
fffff880`032beb30 fffff880`01d0259e : fffffa80`0ae4f118 00000000`00000010 00000000`00000010 00000000`00000001 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageFindSpace+0x4a
fffff880`032beb60 fffff880`01d01773 : fffffa80`0c451230 fffffa80`0ad7fa90 00000000`00000000 fffffa80`0ae4f118 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageAdd+0x2e
fffff880`032bec20 fffff880`01d0162e : fffffa80`0c451230 00000000`00010000 00000000`00000080 fffffa80`0ae4f0b0 : rdyboost!ST_STORE<SMD_TRAITS>::StDmPageAdd+0xe3
fffff880`032bec80 fffff880`01d0041a : fffffa80`0c451230 00000000`00000080 00000000`00000080 fffffa80`0ae4ff88 : rdyboost!ST_STORE<SMD_TRAITS>::StWorkItemProcess+0x23a
fffff880`032bece0 fffff800`03321e5a : 00000000`00000000 fffff880`00000000 fffffa80`0ad27b50 fffffa80`09d5b040 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStWorker+0x152
fffff880`032bed40 fffff800`0307bd26 : fffff880`009b2180 fffffa80`0ad27b50 fffff880`009bd0c0 1eb81eb8`0d370d37 : nt!PspSystemThreadStartup+0x5a
fffff880`032bed80 00000000`00000000 : fffff880`032bf000 fffff880`032b9000 fffff880`032be810 00000000`00000000 : nt!KiStartSystemThread+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 0xfffff880032bde20 ; 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
---------
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Note
Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.
Information
Errors are sometimes found after 8 passes.
Tip
Do this test overnight, before going to bed.
If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial:
Upload a screenshot of your hard disk using CrystalDiskInfo:
Make a hard drive test from the hard drive manufacturers website:
Let us know the results.
