various BSOD - need input please

[tasev1]

Hi. Many posters on this forum helped me overclock my CPU earlier this year - thanks!. I am having an issue that keeps relating to ram, and I can't pinpoint the source.

Base specs to start:
Intel I7-950 on Sabertooth X58 mobo 3.06Ghz
8Gb "Hyper Xtreme" Ram rated for 1600 9-9-9-27.
Windows 7-64
GeForce GTX660GC.

Ok. I have a stable overclock at 3.8 Ghz all on stock voltages and a slight OC on RAM - I have NEVER had any issues at these settings thus far. I fiddled with going to 4.2 Ghz months ago but had occasional (1 in 2 weeks for example) memory BSOD's so I gave up. I just went back to that past setting recently and I had to raise voltages just to get my system to boot (those voltages worked previously, and now they're not good enough?)!

Now, under my 4.2 Ghz overclock my RAM frequency runs lower than the rated 1600 (at 14xx) and timings at 9-9-9-27. My Prime95 blend tested no problems for 24 hours (no HT), and my RAM on Memtest86+ passed after some dozen passes (2 channel and single channel tested).

I have played around with RAM timings, voltages of ram, core and uncore, and I still have the occasional BSOD. Various codes, but all somehow related to ram. Currently, I have my page file set to 3GB. I will play around with that and see what happens, since one of the errors was "...non paged area..."

BSOD errors I recall getting:

0x50
0x7F
0x0BE
0x0A
0X1A

Any input from the pros?

 

[Wraith]

Have you checked your minidump file for accurate detailed reasons for the BSOD? Just giving us ID Codes are very vague and could be a multitude of things.
Download a copy of Blue screen viewer so you can access the full crash details.

 

[tasev1]

==================================================
Dump File : 021214-15724-01.dmp
Crash Time : 12/02/2014 7:30:42 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041287
Parameter 2 : 00000000`00000008
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : nvlddmkm.sys
Caused By Address : nvlddmkm.sys+1eb1bd
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021214-15724-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,720
Dump File Time : 12/02/2014 7:32:51 PM
==================================================

==================================================
Dump File : 021214-16270-01.dmp
Crash Time : 12/02/2014 6:03:13 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffa500`00021ef3
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`03318cec
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021214-16270-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,712
Dump File Time : 12/02/2014 6:05:34 PM
==================================================

==================================================
Dump File : 020614-19531-01.dmp
Crash Time : 05/02/2014 9:14:10 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041284
Parameter 2 : fffff700`01081001
Parameter 3 : 00000000`00000ad9
Parameter 4 : fffff700`01080000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\020614-19531-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,736
Dump File Time : 06/02/2014 12:16:06 AM
==================================================

==================================================
Dump File : 020514-21278-01.dmp
Crash Time : 05/02/2014 9:04:55 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffff680`0005a880
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`033a13b6
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\020514-21278-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,712
Dump File Time : 05/02/2014 9:07:03 PM
==================================================

==================================================
Dump File : 020514-20779-01.dmp
Crash Time : 05/02/2014 7:04:18 PM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`80050033
Parameter 3 : 00000000`000006f8
Parameter 4 : fffff880`0441c66f
Caused By Driver : RapportCerberus64_59849.sys
Caused By Address : RapportCerberus64_59849.sys+1c66f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\020514-20779-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,712
Dump File Time : 05/02/2014 7:05:48 PM
==================================================

==================================================
Dump File : 020414-16364-01.dmp
Crash Time : 04/02/2014 9:41:31 PM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`80050033
Parameter 3 : 00000000`000006f8
Parameter 4 : fffff880`044622a2
Caused By Driver : RapportCerberus64_59849.sys
Caused By Address : RapportCerberus64_59849.sys+622a2
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\020414-16364-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,720
Dump File Time : 04/02/2014 9:43:35 PM
==================================================

==================================================
Dump File : 012914-23727-01.dmp
Crash Time : 29/01/2014 9:42:39 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffff680`000573e0
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`033fd3b6
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+9c607
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012914-23727-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,736
Dump File Time : 29/01/2014 9:45:09 PM
==================================================

==================================================
Dump File : 012914-46113-01.dmp
Crash Time : 29/01/2014 8:43:54 PM
Bug Check String : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code : 0x000000be
Parameter 1 : 00000000`03bfe300
Parameter 2 : aa400001`d282b025
Parameter 3 : fffff880`03d11bb0
Parameter 4 : 00000000`0000000a
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012914-46113-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,736
Dump File Time : 29/01/2014 8:47:16 PM
==================================================

==================================================
Dump File : 012914-17175-01.dmp
Crash Time : 29/01/2014 8:24:00 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffbc2`2a242660
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`032b2ea5
Parameter 4 : 00000000`00000007
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+1a82
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012914-17175-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,736
Dump File Time : 29/01/2014 8:28:22 PM
==================================================

==================================================
Dump File : 012814-15475-01.dmp
Crash Time : 28/01/2014 11:08:01 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`083f88f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4adb3c
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
Processor : x64
Crash Address : ntoskrnl.exe+4adb3c
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012814-15475-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
Dump File Time : 28/01/2014 11:08:05 PM
==================================================

==================================================
Dump File : 012814-18844-01.dmp
Crash Time : 28/01/2014 8:49:15 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`05592028
Parameter 3 : 00000000`fa000000
Parameter 4 : 00000000`00400405
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012814-18844-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,552
Dump File Time : 28/01/2014 8:53:45 PM
==================================================

==================================================
Dump File : 012214-16520-01.dmp
Crash Time : 22/01/2014 5:21:24 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`0549f028
Parameter 3 : 00000000`fa000000
Parameter 4 : 00000000`00400405
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012214-16520-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,376
Dump File Time : 22/01/2014 5:25:55 PM
==================================================

The Cerberus driver errors I know about and were fixed by removing Rapport....I think the other one is relating to NVidia drivers which I will clean install.....the system one i am clueless on however.

 

[Wraith]

Well the Hal.Dll is a link library that is loaded into the Kernel which handles requests between chipsets and buses (PCI & PCIe), fltmgr.sys is a file system filter allowing Windows to communicate with hardware, nvlddmkm.sys is as you thought a gForce driver, RapportCerberus is again what you thought and the same thing I always avoid installing damn supposed "Safe Banking" app.

The others are memory related... Namely dumps 2, 3, 4, 7 & 8 all refer to
MEMORY_MANAGMENT
PAGE_FAULT_IN_NONPAGED_AREA
IRQL_NOT_LESS_OR_EQUAL
ATTEMPTED_WRITE_TO_READONLY_MEMORY
All ntoskrnl.exe related which points to memory management, scheduler, Cache management....ect ect

I'd concentrate on your RAM voltages and frequencies.

 

[kilobravo]

In my opinion,your cpu and ram are degrading.
Here`s some common bsod codes.

BSOD codes for overclocking
0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
on i7 32nm SB, usually means too little vCore
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (Nb) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

 

[tasev1]

The RAM is less than a year old, the chip is 3 years old and only clocked since September / October. Doesn't common sense suggest that if it were memory alone, then I would have this issue at other clock speeds too? Though my chip has been sped up, my memory is running SLOWER than it's rated (at 3.8Ghz I run it slightly faster than rated without issue). I have tried memory voltages from the 1.5V at 11-11-11-30 to 1.65v at 9-9-9-27, as well as playing around with my core and uncore but it didn't help.

I have two theories - my QPI bridge can't handle the processor / voltage increases and nothing I can do will help, or reinstalling stable NVidia drivers will help (I already removed Rapport).

The other thing - from past tunings I have my page file set to 3gb. Could this have an effect? I want to consider either having windows manage it, or have no page file (for increased game performance....SUPPOSEDLY)

 

[kilobravo]

Win7 should manage pagefile.

If qpi/vtt or vcore voltages have been to high, even for a short time it could ruin your cpu and also if vcore temp has been to high it degrades faster.
Nearly all bsods you had are related to memory.If you have some other ramsticks i would try with them.

 

[tasev1]

I temporarily set it to my 4.2 Ghz clock and booted up. Just as I was reading responses on another forum I got a BSOD 0x124 (QPI/VTT or vcore). I haven't touched my QPI multiplier - should I? (its at 36x now I think).

When I did my initial clock months ago, I had my voltages at the lowest stable values and it 'worked'. This past month, I had to INCREASE my voltages just to get my system to boot - so I'm fairly certain my voltages SHOULD be ok, and my temps were acceptable.

I am going to do two steps now - update my BIOS for the first time (fixes indicate memory compatibility and system stability updates), and if that doesn't help, I will try my old sticks of RAM (which equate to only 6GB - kind of slow for performance gaming, but oh well).

If all else fails, then I will just have to settle at 3.8 Ghz. That runs flawlessly and I am happy with the performance.