• 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.

BSOD issue possibly caused by GPU?

trawetSluaP

trawetSluaP

trawetSluaP

Associate
Joined
9 Nov 2014
Posts
769
Hi guys, I'm getting an intermittent BSOD that displays the following error:

"PAGE FAULT IN NONPAGED AREA (NVLDDMKM)"

I think it may possibly be relayed to the GPU but I don't have other parts I can put into my machine to rule them out.

It seems to happen at random, when I open Spotify at times, or most recently when I changed my display settings from "PC Screen Only" to Extend".

I've had a look on various places on the web and can't really come to a conclusion and any help would be very appreciated!
 
Hey,

Thanks for the suggestion but I've already tried that and always use DDU when installing/updating drivers.

I've also tried a clean install of Windows and am currently running Memtest too.
 
setter said:
Id also download this.

http://www.resplendence.com/whocrashed

Run it and it will display the bsod info and the stop error code, often theese can be used to help determine the cause of blue screens.
Click to expand...

Memtest ran 2 full cycles and reported no errors, I'll run it overnight to make sure.

Here's what Whocrashed reports:

On Mon 18/01/2016 19:06:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011816-5531-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x6418C0)
Bugcheck code: 0x50 (0xFFFFC001DCB40FF0, 0x0, 0xFFFFF8002FE018C0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 361.43
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 361.43
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 361.43 , NVIDIA Corporation).
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA



On Mon 18/01/2016 19:06:38 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x6418C0)
Bugcheck code: 0x50 (0xFFFFC001DCB40FF0, 0x0, 0xFFFFF8002FE018C0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 361.43
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 361.43
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 361.43 , NVIDIA Corporation).
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA
 
0x50 can be ram related, often not enough on SA, IOA and IOD voltages on haswell.

Useful list of bsod codes for overclocking below.

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



Haswell, according to a source from the R.O.G forums these codes still very much apply, but where it says QPI/VTT this can also mean SA/IO for this particular architecture.


Haswell-E

101 initially add more vcore but also possibly SA that needs tuning try +/- in small steps, 0.05v at a time, going larger and you could miss a stability sweetspot
Click to expand...

What have you the voltage on theese set too? Iirc even with just 8gb of 2400mhz ram on the maximus 6 formula i needed around 1.200v on each.
 
setter said:
0x50 can be ram related, often not enough on SA, IOA and IOD voltages on haswell.

Useful list of bsod codes for overclocking below.



What have you the voltage on theese set too? Iirc even with just 8gb of 2400mhz ram on the maximus 6 formula i needed around 1.200v on each.
Click to expand...

My CPU isn't overclocked and I've got the ram set to XMP in the Maximus VII Formula BIOS so I think it runs at around 1.65 volts.
 
Yep, XMP will indeed set 1.65v automatically. But it doesnt adjust the chipset voltages above. Often with 16gb of ram theese require a bump in volts. Id suggest setting each of the above manually to 1.200v first to see if it helps.
 
setter said:
Yep, XMP will indeed set 1.65v automatically. But it doesnt adjust the chipset voltages above. Often with 16gb of ram theese require a bump in volts. Id suggest setting each of the above manually to 1.200v first to see if it helps.
Click to expand...

When you say set "each" manually do you mean each stick of RAM? I'm not sure how to do them individually!

EDIT: You mean the SA/IO voltages right? Haha! Sorry I'm not very experienced with OC'ing!

EDIT 2: I have a Digital and Analog IO, so up these AND the System Agent voltage to 1.2?
 
Last edited:
In bios under the ai overclocking section, if you scroll down to the voltage setting you will see the SA, IOA and IOD voltages ive listed above. You will need to adjust theese. No need to touch the memory timings/voltages as XMP takes care of theese. Below is an old pic of mine from the 6 formula that shows theese voltages. May look slightly different on the 7 formula bios screen.

cdXd9vU.png
 
setter said:
In bios under the ai overclocking section, if you scroll down to the voltage setting you will see the SA, IOA and IOD voltages ive listed above. You will need to adjust theese. No need to touch the memory timings/voltages as XMP takes care of theese. Below is an old pic of mine from the 6 formula that shows theese voltages. May look slightly different on the 7 formula bios screen.

cdXd9vU.png
Click to expand...

Sweet, got it! All set to 1.2v. Hope it works.

One other thing, I also have "Eventual SA, IOA and IOD Voltage". Should I leave those on auto?

Thanks for your help! Wrong section in the end though!
 
No probs, yep id just leave on auto. Mustve been a new feature on the Z97 formula as i cant recall seeing that option on the Z87 model.
 
You must log in or register to reply here.
Back
Top Bottom