Memory management error

ncncore · 19 Jan 2014 at 16:35

I keep getting this message on a BSOD while playing games.

System config :-

CPU- i5 3570k
Mobo- gigabyte Z77X-UP5
Ram- corsair vengeance 4x4Gb 1866Mhz (Bios correctly set)
Os- windows 8.1

This error only started today and the system has been running fine now for 14 months with no sign of this previously.

I am just running memtest86 now but so far no errors have been reported. I still have all 4 sticks in place at present.

What's my next step if this passes with no errors or if I do get errors how do I pinpoint the exact fault.

Nick

ncncore · 19 Jan 2014 at 16:58

Not sure will check once I have got through this memtest. Currently sat at 56%, still no errors.

Just seems strange that it has been fine for so long and then today it's binning me out.

ncncore · 19 Jan 2014 at 17:20

Ok so it passed fine and my profile vtt voltage is sat at 1.05v but I can't change it.

ncncore · 19 Jan 2014 at 17:23

Scrap that last I have upped it to 1.10v

ncncore · 19 Jan 2014 at 17:47

So it didn't quite BSOD this time with the new voltage setting but it did kick me from the game and mouse movements kept sticking and nothing would really open once I got booted from the game.

Just done a restart and everything seems fine again.

Really quite annoying to say the least.

ncncore · 19 Jan 2014 at 18:00

I' running my CPU at 4.2 so nothing crazy.

I kept Alt Tabbing and checking Task manager memory tab and it all looked fine then it seems all of a sudden it all goes wrong.

ncncore · 19 Jan 2014 at 18:03

Cpu Vcore is at 1.255v

I have just stuck the Vtt to 1.12v now so I will see if that changes anything.

Thanks for the help so far

ncncore · 19 Jan 2014 at 18:15

Ok so it binned me again but this time the desktop is fine just the game has binned out.

Also there are a lot of critical errors- source - Kernal-power event id - 41 task category- (63)

I think there may be another issue other than memory?

ncncore · 19 Jan 2014 at 18:30

There are quite few WHEA-Logger warnings. This is the details -

- System

- Provider

[ Name] Microsoft-Windows-WHEA-Logger

EventID 19

Version 0

Level 3

Task 0

Opcode 0

Keywords 0x8000000000000000

- TimeCreated

[ SystemTime] 2014-01-19T14:08:15.443050100Z

EventRecordID 19099

- Correlation

[ ActivityID] {8F3F8D5B-FF93-4C23-BA73-F05C30FD8E2C}

- Execution

[ ProcessID] 1732
[ ThreadID] 2932

Channel System

Computer nickPC

- Security

[ UserID] S-1-5-19

- EventData

ErrorSource 1
ApicId 0
MCABank 0
MciStat 0x9000004000010005
MciAddr 0x0
MciMisc 0x0
ErrorType 12
TransactionType 256
Participation 256
RequestType 256
MemorIO 256
MemHierarchyLvl 256
Timeout 256
OperationType 256
Channel 256
Length 864
RawData 435045521002FFFFFFFF03000200000002000000600300000F080E0013010E140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B18BCE2DD7BD0E45B9AD9CF4EBD4F890BFF366241F15CF0100000000000000000000000000000000000000000000000058010000C00000000102000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000400000000102000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000058020000080100000102000000000000011D1E8AF94257459C33565E5CC3F7E80000000000000000000000000000000002000000000000000000000000000000000000000000000057010000000000000002080000000000A90603000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000A906030000081000BFE39A7FFFFBEBBF0000000000000000000000000000000000000000000000000000000000000000010000000100000086E850E51F15CF010000000000000000000000000000000000000000000000000500010040000090000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

ncncore · 19 Jan 2014 at 19:03

Ok, I wonder if somewhere along the lines the voltage setting dropped down. I will stick it up a touch and see.

ncncore · 19 Jan 2014 at 19:18

Fixed I think, just set 1.255v on the vcore bios setting.

ncncore · 19 Jan 2014 at 19:27

Ok there's a new level of info to take in haha!

I will try my best to set that up and see how i get on

ncncore · 19 Jan 2014 at 20:02

All settings as per your last post but during stres core v is sitting at 1.32v.

Also not sure what the accuracy is but in task manager CPU speed is reading 5.17Ghz

ncncore · 19 Jan 2014 at 20:24

Cool just managed a game there for about 20 mins without issue. I will try knocking it down a bit and see.

Once again many thanks!

Also is there a reason that this has only just started playing up when it has been fine for so long?

ncncore · 19 Jan 2014 at 20:34

Ok so I dropped the LLC down to medium and dvid back to 0.005v and it was sat at 1.308v

I have just noticed though you said negative 0.005v!

ncncore · 19 Jan 2014 at 20:38

1.296v now so it's getting better, is it a case of just dropping it down bit by bit till I reach 1.255v

Edit*****

-0.015v is giving me 1.284v, should I keep dropping it or just roll with that?

Edit 2****

-0.025v and it stays at 1.284v under load

ncncore · 19 Jan 2014 at 21:06

Well I will leave it as it is as everything seems to be fine at the moment, I will try llc to low and see how it goes.

Many Thanks for the info!