-
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)
- Thread starter Loxa
- Start date
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:
Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D
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:
I found this regarding that error,
http://answers.microsoft.com/en-us/...pped-due/a1401dfa-d476-4f1a-81c2-f9c8a4781324
actually the errors appear due to the bsod
could try this as it cured it for the op in the post
Loacte the EppOobe.etl , delete it then reboot (sometimes it get corrupt) MSE then recreated the file automaically.
http://answers.microsoft.com/en-us/...pped-due/a1401dfa-d476-4f1a-81c2-f9c8a4781324
actually the errors appear due to the bsod
could try this as it cured it for the op in the post
Loacte the EppOobe.etl , delete it then reboot (sometimes it get corrupt) MSE then recreated the file automaically.
Thanks for looking into it, its really strange how such a thing caused a BSOD. I have done as the guide suggested.
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
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
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:
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.
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:
Memtest is not really a good test for unstable memory/controllers, it's only really useful for finding physical faults such as damaged areas of memory. You should use something like Prime95 blend test which will actually put your memory/controller under stress.
What speeds are you running the RAM at? it could simply be that the IMC can't handle the frequency with 16GB or possibly like my board I found that certain RAM straps had an issue with applying the correct voltage but could get stable by working around them.