Aced the Intel Burn test on Standard, High and Very High x 5, All threads.
I think we're at the point where we have to examine my computers behavior.. I mean, it hasn't been like this (not wanting to boot, bluescreen every day while idle) a very long time.. I'm not sure what to make of this.. Might need to run memtest again or run a while with only 2 sticks
Yes, I have. I will try sfc again though, for the helluvit.
Insufficient space should be of no concern, 40gb + free on main disk and space in the TB range on other disks. RAM should be fine as far as I know, rolling with 16Gb..
Did you buy the RAM in sets or matched pairs, have you checked the motherboard's documentation? Some motherboards require the RAM to be installed in certain slots, and are only compatible with certain types of RAM.
uh yeah, they were 2 x 4Gb or so, the RAMs should work with the motherboard, I have to doublecheck that..
SFC, I forgot to pull up a cmd windows so after it was done it just threw the terminal, rendering me unable to read. I found the logs for it and there's indications that stuff has been fixed although I might be reading it wrong. I am currently running a verifyonly to see if there are any (more) problems..
EDIT;
ACTUALLY, the EXACT type of memory i have wasn't listed in the specs.
Disable verifier now. The last crash dump, with verifier enabled, have not caught any device driver, and indicated to Memory corruption, as Harry pointed out. Rather the immediate earlier crash dump is highly interesting.
It is either out and out memory corruption (so we need to know how many passes you have run the memtest, and at what stick - dimm combination; better you explain it) or something bad, say a virus. As another test, scan the system for possible virus infection.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c000001d, fffff880016318ad, fffff88003fd0c50, 0} Probably caused by : memory_corruption Followup: memory_corruption --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c000001d, Exception code that caused the bugcheck Arg2: fffff880016318ad, Address of the instruction which caused the bugcheck Arg3: fffff88003fd0c50, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction. FAULTING_IP: Ntfs!NtfsGetIoAtEof+1d fffff880`016318ad ff ??? CONTEXT: fffff88003fd0c50 -- (.cxr 0xfffff88003fd0c50) rax=fffff88003fd16b0 rbx=fffff8a00161f690 rcx=fffff88003fd16b0 rdx=0000000000000000 rsi=fffffa80128535c0 rdi=fffff8a00161f690 rip=fffff880016318ad rsp=fffff88003fd1630 rbp=fffff88003fd1a00 r8=0000000000031000 r9=0000000000010000 r10=fffffa800f6ef030 r11=fffff88003fd16b0 r12=fffff88003fd16b0 r13=0000000000010000 r14=fffffa801370a520 r15=0000000000000702 iopl=0 nv up ei pl nz na po cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010207 Ntfs!NtfsGetIoAtEof+0x1d: fffff880`016318ad ff ??? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x3B PROCESS_NAME: svchost.exe CURRENT_IRQL: 1 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880016318ad STACK_TEXT: fffff880`03fd1630 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsGetIoAtEof+0x1d CHKIMG_EXTENSION: !chkimg -lo 50 -db !Ntfs 5 errors : !Ntfs (fffff880016310ba-fffff88001631c0a) fffff880016310b0 ff 0f 84 96 00 00 00 41 3b cb *2f 84 8d 00 00 00 .......A;./..... ... fffff88001631600 5e 01 00 41 8a 8b 88 01 00 00 *cc 8b 4c 24 70 49 ^..A........L$pI ... fffff880016318a0 da 48 8b 50 28 48 3b 53 70 0f *94 58 c3 ff ff 48 .H.P(H;Sp..X...H ... fffff88001631900 c1 48 8b cb e8 3b 8f 07 00 84 *e0 75 be e9 ee c2 .H...;.....u.... ... fffff88001631c00 33 c0 33 d2 48 8b c8 ff 15 c3 *c2 03 00 48 85 f6 3.3.H........H.. MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: STRIDE STACK_COMMAND: .cxr 0xfffff88003fd0c50 ; kb FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE Followup: memory_corruption ---------
Let us know the results of the scans, and the details of memtest.
I just want to say again, thanks for your perserverance, I'm humbled by your will to help!
The memtest ran for 7-10 passes on each stick, about 4 hrs or something. However, since the modules arent supported by the motherboard, and i use 2 different (8Gb Corsair vengeance low profile, 8Gb regular corsair vengeance, same timings) in dual channel mode, it might have to do with that aswell?
I will conduct a more indepth memory check overnight to ensure they are ok.
Kaspersky's tool came back clean..
The incompatible RAM may be the problem, have you got warranty for the RAM or any returns policy still remaining?
Well from what I've read, the vengeance and mobo should workfine, iit's just that the modules arent certified with the mobo because it wasn't out at the time the mobo was introduced. So I guess the memory is ok. I'm running my first pass now with a single module in.. Still weird boots at times, it's like the computer starts but no peripherals are recognized.. It stays on for like 5 seconds then reboots. Sometimes it boots sometimes it doesn't.. I don't know what to make of this. .
Quote