• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

IMC Voltage (VTT)

Rroff said:
I'd reccomend 1.15 max on non-exotic cooling, 1.2 if your using sub-ambient cooling. Some guides will say 1.2 max on air but I've seen a few incidents that leaves me convinced <1.2 is a better idea if you want the CPU to last.
Click to expand...

Going a bit off topic here but I am rather confused, I recently replaced my PSU for a corsair RM 750 & increased my memory from 1600mhz to 2133mhz (2133mhz is stock). I have had one GPU driver crash and my game will randomly shut off sometimes but with know error...

Is this just me needing more GPU voltage because its a new PSU or do I need more VTT because of the memory speed increase?
 
Rroff said:
Only way to know for sure really is to put RAM back to 1600 and see if the problem goes away.

Have you tried running memtest to see if your RAM is stable with those settings?
Click to expand...

Funnily enough I have not ran memtest at 2133mhz yet so ill get on that tonight, is it better to do it in DOS or within windows?
 
Rroff said:
DOS version is better - it can't test memory currently in use by Windows, etc.

If you have a UEFI BIOS, etc. you can just stick it on a USB disc and select it from the boot over-ride menu in the BIOS without messing about now.
Click to expand...

Yeah I normally just use a USB stick because it makes life simple. :)
 
wazza300 said:
how much memory are you running?

vtt is usually fine on stock 1.05v unless your using more than 8gb of ram
Click to expand...

I am using 16gb and VTT is set to auto (1.141v). But I will note for some reason I had VTT on 1.104v and when I set to auto it is now 1.141v.
 
Last edited:
@wazza300

One question, I have noticed when i enable the XMP Profile the only thing it changes is the voltage from 1.5v to 1.65v, I have to change from 1600mhz to 2133mhz and the timings manually. There is also a option that is called Dram Reference clock that is set to auto all the time, what I am wondering is am I meant to change this? (has two options 100mhz/133mhz)

Another thing is if I set Dram Voltage to Auto it sets 1.665v instead of 1.650v, is this telling me it needs more voltage to run?

*Note*

I always had to change the settings manually after selecting the XMP Profile but never really noticed the Dram Reference option until now.
 
Last edited:
No I only have one XMP profile & Auto. I ran memtest last night for 11 hours which resulted in 5 passes with no errors.
 
wazza300 said:
Yh if it does it through the bios,its safer
Click to expand...

Had a blue screen about 30 minutes ago and WhoCrashed couldn't find the dump... So no idea what happened there, updated my bios now though and the XMP profile seems to change everything correctly.
 
Last edited:
I am not sure what it means.

e9gs36.jpg


2ef0ox5.jpg
 
wazza300 said:
idk what that is without googling

it might be nothing but it might be the error that caused the crash idk,ill try n find what it is later on
Click to expand...

Ill have a look around as well, thanks for the help much appreciated. Always seems to be one problem after a another with this PC (but its still my baby).

--

Strange, that same problem seems to be happening everyday every few hours in the event log.
 
Last edited:
Just got another BSOD from the same error in Event Viewer.

But

On the actual Blue screen before my PC restarted I did see the code 0x0000001E.

(so I am not sure if its a combination of things or one is causing another)

---------------

Few hours later got another blue screen (0x0000003B)

I normally use this to trouble shoot BSOD's

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

BSOD Codes for SandyBridge
0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
0x101 = add more vcore
0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT
0x1E = add more vcore
0x3B = add more vcore
0xD1 = add QPI/VTT voltage
“0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances”
0X109 = add DDR3 voltage
0x0A = add QPI/VTT voltage
 
Last edited:
Another BSOD today 0x0000007E.

Probably just going to reinstall see if it helps had so many issues lately hard to point to the problem.
 
Last edited:
This was after a clean install.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF8800441F149
BCP3: FFFFF88009C86D30
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\013014-9328-01.dmp
C:\Users\Loxa\AppData\Local\Temp\WER-11637-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

------

On Thu 30/01/2014 21:10:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013014-9328-01.dmp
This was probably caused by the following module: npfs.sys (Npfs+0xB149)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800441F149, 0xFFFFF88009C86D30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 30/01/2014 21:10:05 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: npfs.sys (Npfs+0xB149)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800441F149, 0xFFFFF88009C86D30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom