BSOD 4 times tonight.

[sastusbulbas]

i all, not had a BSOD for some time, LGA775 I think.

Anyway, had four in a row tonight.

I was overclocked to 4.4GHz at 1.29v using an air cooler, in sig below. I have not been gaming much, added 16gb of memory recently, but not done much at all since simply using the motherboards overclock facility on auto everywhere for the 4.4 overclock.

Today was unusual, as I had World Of Tanks running all day, playing on and off, and during a heavy session this evening thats when the system shut down and restarted with a BSOD.
I restarted and it looped, dropped to 4.2GHz and it wold not post, and rebooted again at 4.4Ghz with a BSOD, then again into windows at 4.4GHz.

I noticed my temps were in the low 40's idle, previous it was mid/high 30's idle. So I reset my CPU fan profile and dropped to default configs.

I am hoping for some direction in a more stable overclock, clearly need to disale some auto functions and tune that voltage, but I am hoping someone can give me some pointers on the BSOD info I post below?

==================================================
Dump File : 101016-12807-01.dmp
Crash Time : 10/10/2016 20:29:02
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`0cd398f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4ad53c
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.23539 (win7sp1_ldr.160902-0600)
Processor : x64
Crash Address : ntoskrnl.exe+4ad53c
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101016-12807-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
Dump File Time : 10/10/2016 20:29:05
==================================================
Dump File : 101016-12979-01.dmp
Crash Time : 10/10/2016 20:29:46
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000020
Parameter 2 : fffffa80`152d0730
Parameter 3 : fffffa80`152d0d40
Parameter 4 : 00000000`0461ba10
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+22e60
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70180
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101016-12979-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 364,584
Dump File Time : 10/10/2016 20:36:12
==================================================

Dump File : 101016-12168-01.dmp
Crash Time : 10/10/2016 20:36:53
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`11235028
Parameter 3 : 00000000`bf800000
Parameter 4 : 00000000`00000124
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70180
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101016-12168-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 405,680
Dump File Time : 10/10/2016 20:39:35
==================================================
Dump File : 101016-12214-01.dmp
Crash Time : 10/10/2016 20:56:51
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000019
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`03502180
Parameter 4 : 00000000`00000006
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70180
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.23539 (win7sp1_ldr.160902-0600)
Processor : x64
Crash Address : ntoskrnl.exe+70180
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101016-12214-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 405,064
Dump File Time : 10/10/2016 21:00:06
==================================================

 

[zipp0r]

101 is usually vcore and 124 can be either vcore or vccio (memory controller)

dont use automatic overclocking !

 

[doyll]

What's been said.

How long has cooler been mounted? If more than a year a good clean and new TIM often fixes things.

 

[SirJinks]

added 16gb of memory recently

Are all your memory slots now filled? I understand this can stress your IMC and affect overclocking.

 

[sastusbulbas]

What's been said.

How long has cooler been mounted? If more than a year a good clean and new TIM often fixes things.

You have a point with the cooler, it's never been off since purchase, though there is little in the way of dust ingress here.
That said I had intended to put a water cooled loop in place, but have hit financial difficulties due to redundancy so buying a Gsync monitor and EK360 system is on hold.
I would rather replace the cooler with a water loop or AIO, I felt it should have been cooler even with a 4.4GHz OC and 1.29v. From what I have read 4.4GHz to 4.6GHz (where I hope to get to) requires better cooling, my system cannot take a bigger air cooler, my current cooler was bought because my bigger Noctua hit the GPU.

Hopefully a few others will chip in about the BSOD data I provided, I need to start afresh with overclocking, and am also tempted to do a re-instal of the OS to get rid of the bloat that may have accumulated.

Are all your memory slots now filled? I understand this can stress your IMC and affect overclocking.

No, it's just the 2x8GB Corsair Vengeance 2400MHz kit I have. Previous it was 2x4GB lower latency 2400Mhz Patriot Viper.