[SOLVED] BSOD during Overclocking getting 0x1A Memory_Management

H

HyeVltg3

Member
Joined
Jan 26, 2015
Posts
6
Mods close topic if this is against any rules to ask for BSOD help when trying to over clock, but I'm getting an Error code thats not...common during OC-ing.
Been trying to overclock just my CPU, i5-3570K, since Thursday and the 0x1A error stumps me every time.
Intel Core i5-3570K, PNY GeForce GTX 670, Enermax ECA3212-BL - 170912 - HyeVltg3's Saved Part List - PCPartPicker Canada
I've run Memtest86+ for 2 passes and no errors were found. running ram at stock so I dont understand why the BSOD happens.
I built this setup way back in Sept.2012. has been running perfectly since then, havent even seen a single BSOD since I built it, and I'm a heavy user, just never had an interest in overclocking till this week.

Can I continue to request help or ?
Just need to know if I have hardware limitation (bad HW causing BSOD when CPU is at a higher frequency)
Been ripping out my hair (figuratively) since Thursday night.
Thank you.
 
Mods close topic if this is against any rules to ask for BSOD help when trying to over clock
Click to expand...

It's not against the rules, but we don't really "help" overclocking unfortunately. It's not like we don't want to, it's just not something we really do provided there's no "fix" for an unstable overclock other than understanding what the adjustments you're making in the BIOS actually do, and what to raise/lower/change if you crash when booting Windows/initiating a benchmark or stress test.

I'm getting an Error code thats not...common during OC-ing.
Click to expand...

0x1A is actually not uncommon at all, especially if you're just raising core voltage for example and that's it. On SB> generation CPUs, it got easier to OC as you'd generally only have to touch core voltage to bump up a few notches, but if you want to go any higher then you need to mess with a lot of stuff like FSB, etc. This leads to...

I've run Memtest86+ for 2 passes and no errors were found. running ram at stock so I dont understand why the BSOD happens.
Click to expand...

Because your RAM is not the issue, you just have an unstable CPU overclock. This is especially true if on complete stock settings your system runs without any issues. 0x1A is just a generic bug check for a severe memory error. Your video card has memory, your CPU has memory, etc. If a bug check is in relation to memory, it doesn't automatically imply RAM is the culprit.

IMO: Read a lot more into overclocking across various benchmarking communities as it's not something you can be taught how to do in a thread by a sole person. It's a hobby that needs a lot of patience and technical understanding, as you need to understand pretty much every piece of hardware. If you don't know what you're doing and you just randomly change BIOS values then you just end up with an unstable overclock, way too much energy consumption, and too much unnecessary heat (kills hardware way faster).

Also, I could take a look at the crash dump for you anyway if you want just for curiosity's sake. You can find it in C:\Windows named MEMORY.DMP. Upload that to OneDrive or something similar and paste the link.
 
Patrick said:
Also, I could take a look at the crash dump for you anyway if you want just for curiosity's sake. You can find it in C:\Windows named MEMORY.DMP. Upload that to OneDrive or something similar and paste the link.
Click to expand...

Assumed as such for the other things you mentioned, I'm the one tampering with values obviously would lead to unstable BSODs, just going from 3.9 to 4.5 I can make it up to 1.32v before I get hit with 0x1A.
My main reason for asking for help here, is on the OC boards, its hard to get direct help, usually get the ol' "increase vcore" "increase vtt" indirect tips, been running 3-8hr tests since thursday all according to maybes.
Saw that this board was about helping read and solve BSOD dump files so was just making sure I could ask for help here or would be shoo'd away haha.

Problem, my .dmp file is 1.2GB ! ... is that normal or is there any way to trim it down to 1-3 days of logged info?
 
My main reason for asking for help here, is on the OC boards, its hard to get direct help, usually get the ol' "increase vcore" "increase vtt" indirect tips
Click to expand...

It's because most people have no idea what they're doing themselves, unfortunately. The bad thing about the OC community is people confuse a personal fix for a permanent solution to all different hardware. For awhile on an OC forum, there was a thread devoted to what bug checks you'd get if you had "x" wrong with your overclock, and what to do to fix it. For example, an 0x124 automatically implies low vcore, so bump it up and voila.. solved :roll eyes (sarcasti

Problem, my .dmp file is 1.2GB ! ... is that normal or is there any way to trim it down to 1-3 days of logged info?
Click to expand...

Normal, it's an entire snapshot of kernel memory space. Very helpful in these type of bug checks. You can just zip it to compress it and then I can download it without issue so long as you won't have any bandwidth restrictions yourself.

Bottom line, I can look at the dump and tell you what went wrong, but I can't tell you how to fix it. Overclocking is lots of trial and error.
 
Thanks.

MEMORY_MANAGEMENT (1a)

This indicates that a severe memory management error occurred.

Code: 
0: kd> .bugcheck
Bugcheck code 0000001A
Arguments 00000000`00041287 00000000`000001c6 00000000`00000000 00000000`00000000

1st argument tells us that a page fault occurred during the synchronization of virtual address space residing in physical memory (working set).

2nd argument is the actual virtual address:

Code: 
0: kd> !pte 00000000000001c6
                                           VA 00000000000001c6
PXE at FFFFF6FB7DBED000    PPE at FFFFF6FB7DA00000    PDE at FFFFF6FB40000000    PTE at FFFFF68000000000
contains 0070000620ECA867  contains 05900006200CE867  contains 0E700006211D3867  contains 0000000000000000
pfn 620eca    ---DA--UWEV  pfn 6200ce    ---DA--UWEV  pfn 6211d3    ---DA--UWEV  not valid // It's invalid, of course

Code: 
0: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0e1675c8 fffff800`06628062 : 00000000`0000001a 00000000`00041287 00000000`000001c6 00000000`00000000 : nt!KeBugCheckEx
fffff880`0e1675d0 fffff800`0668cfae : 00000000`00000001 00000000`000001c6 fffff700`01080000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x454f5
fffff880`0e167730 fffff800`06659dc8 : 00000000`00060000 00000000`00000000 00000000`00000000 fffffa80`272b7b50 : nt!KiPageFault+0x16e (TrapFrame @ fffff880`0e167730)
fffff880`0e1678c0 fffff800`06659b0a : fffffa80`272b7b50 fffffa80`29d54620 fffffa80`29d54620 00000000`76fa5000 : nt!MiQueryAddressState+0x208
fffff880`0e167910 fffff800`06967f94 : 00000000`00000020 00000000`76fa6000 fffffa80`272b7b50 fffff680`00004d28 : nt!MiQueryAddressSpan+0xaa
fffff880`0e167980 fffff800`0668e113 : ffffffff`ffffffff fffffa80`29ca7b50 fffff880`00000000 00000000`0265e2f8 : nt!NtQueryVirtualMemory+0x382
fffff880`0e167a70 00000000`772d14ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0e167ae0)
00000000`0265e2d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772d14ea

Code: 
0: kd> .trap fffff880`0e167730
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff680003b7d28
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80006659dc8 rsp=fffff8800e1678c0 rbp=0000000000000001
 r8=fffff800067cc060  r9=fffffa8029d54620 r10=0000000000000000
r11=fffff70001080000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiQueryAddressState+0x208:
fffff800`06659dc8 66ff8bc6010000  dec     word ptr [rbx+1C6h] ds:00000000`000001c6=????

The instruction at the time of the crash (pagefault) was subtracting to the 16-bit integer stored at the rbx register + 1C6. rbx is null as it's volatile, i.e contents are just trashed and not saved across calls.

So basically as you have an unstable overclock, your CPU is failing at "basic" arithmetic (the dec instruction - subtraction). That's really it : )

To fix it, I'd either just go back to stock and slowly move up with core voltage for now until you hit a wall, and then read and find out what to do next. Either that or just stay at stack if overclocking isn't that big of a deal to you. Remember that not every CPU is the same, so just because one 3xxx series CPU can get 4.5 (random example) doesn't mean yours can.
 
Patrick said:
So basically as you have an unstable overclock, your CPU is failing at "basic" arithmetic (the dec instruction - subtraction). That's really it : )

To fix it, I'd either just go back to stock and slowly move up with core voltage for now until you hit a wall, and then read and find out what to do next. Either that or just stay at stack if overclocking isn't that big of a deal to you. Remember that not every CPU is the same, so just because one 3xxx series CPU can get 4.5 (random example) doesn't mean yours can.
Click to expand...

Well thats actually good news, was really scared that it may be a hardware issue (excluding cpu) and that with the over-clocking it made it prominent, more noticeable.
I have to thank you for even taking the time to look at it, greatly appreciated. Think I'll just go with Asus OC Tuner built in to the mobo, that "safe" clock it set me to was 4.1 but I thought I could do better manually, hence the hunt for the extra 400Mhz, if its not really going to work I can rest easy knowing that I left leave well enough alone =)

Thank You Patrick.
 
Glad to help.

The auto-OC built into motherboards is actually pretty terrible, unfortunately. They for the most part do achieve stable overclocks, yes, but we'll use this as a random example:

4.1 auto-OC vCore @ 1.5.

whereas if you did 4.1 manually, you'd get it a lot lower... maybe @ 1.2/3 for example.

It wayyyy over-values, and that's why a lot of overclockers frown upon using it as it causes more heat, etc.

Anyway, it's entirely up to you!
 
Actually wanted to write back last night but pc was busy running prime95 at 90% ram, too laggy to type.
I set up the oc tuner and it bumped me to 1.42v @41!! =_=
i bumped it down to 1.12v and was just testing worked fine this morning, 0 workers stopped.
thanks for the help Pat, going to undervolt a bit to see how low I can go then just up one notch. =)
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top