Problems after overclocking

Liam123 · 15 Oct 2011 at 17:00

So i was overclocking my 1090t abit to around 3.8ghz with 2.6ghz NB i wasnt using any vcore higher than 1.45 and NB 1.23. I bluescreen on 2.6ghz NB and backed it down to 2.4ghz, ran prime for 2 hours and all seemed fine.

Then randomly when waiting for a download i blue screened and the system powered on but no beeps or display. I managed to get it to boot and took the overclock off but windows memory diagnostic found hardware errors. I looked inside and swapped the corsair vengance for 4gb of ocz gold, that did nothing so it probably wasnt ram related. I then reset the CMOS and that seemed to have worked but im still getting BSOD sometimes for reasons like IRQL, memory management and PEF LIST CORRUPT. Ive posted my dumps etc. on seven forums for someone to look at.

Do you think the overclocking could have done this or may it be a program or driver causing it?

Liam123 · 15 Oct 2011 at 17:04

Voltages and temps are fine @ fully stock settings and ram only on 1333mhz, CPU idles at 25 and NB is at 35-45

Blue160 · 15 Oct 2011 at 17:07

If the RAM isn't the problem then it could be the memory controller in the CPU

Did you monitor temperatures whilst overclocking?

Liam123 · 15 Oct 2011 at 17:09

ye im running antec 620 push pull the cpu core never went over 51 but i saw the NB go as high as 61 was that too much? in my case i have a 120mm fan attached to the HDD cage and it blows cool air right across my motherboards heatsink

Liam123 · 15 Oct 2011 at 17:10

do you think its my motherboard? its an old M4A78LT-M AM3 M-ATX which is a bit weak for ocing

Blue160 · 15 Oct 2011 at 17:17

Impossible to say without swapping bits in and out unfortunately. Motherboard would be a strong contender for the faulty component.

Deception · 15 Oct 2011 at 17:27

What code does the BSOD generate (the 0x one)

Liam123 · 15 Oct 2011 at 17:28

ill get you it now

Liam123 · 15 Oct 2011 at 17:30

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 15/10/2011 16:32:16
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: GOLTYS-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000005003, 0xfffff70001080000, 0x000000000000298f, 0x000042130000511e). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101511-25006-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-10-15T15:32:16.000000000Z" />
<EventRecordID>127691</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>GOLTYS-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x0000001a (0x0000000000005003, 0xfffff70001080000, 0x000000000000298f, 0x000042130000511e)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">101511-25006-01</Data>
</EventData>
</Event>

Liam123 · 15 Oct 2011 at 17:30

the error was memory_management

Liam123 · 15 Oct 2011 at 17:42

i think that is the right 0x numbers

Deception · 15 Oct 2011 at 17:43

what voltage is the RAM running at?

Liam123 · 15 Oct 2011 at 17:46

stock 1.5v, ive triud both my 8gb of corsair vengance @ stock 1.5v and my ocz gold @ stock 1.65v still the same problems so probably not memory related

Liam123 · 15 Oct 2011 at 18:05

........

Deception · 15 Oct 2011 at 18:08

Liam123 said:
stock 1.5v, ive triud both my 8gb of corsair vengance @ stock 1.5v and my ocz gold @ stock 1.65v still the same problems so probably not memory related

Tried it with only 1 stick and ram memtest? Might not be the RAM itself, but it could be the slot. Sorry, only reason im going on about the RAM is that everything is pointing towards it

Liam123 · 15 Oct 2011 at 18:13

ill try with one stick tommorow, i havnt bsod for a while and ive set the ram to ddr 1600

Liam123 · 15 Oct 2011 at 18:13

weird thing is my mobo doesnt allow me to set 2t command rates