BSOD When IGD is Enabled.

[Bryce]

Hey there,

I recently picked up a new motherboard, and have been having issues with BSOD. Normally, on my PC I use a Gigabyte 3080 Vision OC for my main screen GPU (the one I game on), then I have 2 screens running on IGD just for google, discord, whatever. Lightweight stuff.

Prior to this new motherboard, this setup worked flawlessly. I've since upgraded to an I7-11700K, and a Gigabyte Z590 Vision D Motherboard. Now, when I am either playing games, or just working, I will get BSOD sometimes several times a day. The errors love to change too!

Errors I've gotten:
SYSTEM_SERVICE_EXCEPTION
MEMORY_MANAGMENT
UNEXPECTED_KERNEL_MODE_TRAP
KERNEL_MODE_HEAP_CORRUPTION
PAGE_FAULT_IN_NONPAGED_AREA
IRQL_NOT_LESS_OR_EQUAL

I currently have 32GB @ 3000Mhz ram. Running XMP Profile 1, I double checked the timings and voltage with the manufacture website, all bang on.

These BSOD's happened both on Windows 10, and now Windows 11. Windows 11 gave me a bit more information, pointing at DirectX for some reason and my IGD driver, so this gave me the idea to try to disable my IGD and see if it still happens. Sure enough, my PC stopped crashing, my games stopped crashing, and it works perfectly fine. What would the cause be of this??

My old motherboard only had 2 BIOS settings for IGD
Enable/Disable IGD/PEG
Amount of Ram (max was 64MB on that mobo for some reason).

and IGD worked fine back then.

The new mobo I have has 4 settings now:

Enabled/Disable IGD
DVMT Pre-Allocated (Default 64MB)
DVMT Total Gfx Mem (Default 256MB)
Aperture Size (Default 256MB)

Not sure what these new settings should be set too, my old motherboard made it so much easier

I'd like to get IGD turned back on without crashing, but this problem has been consistent all over the place. I will be updating my IGD drivers, but I wanted to make sure what to set my BIOS settings to incase those were the cause.

Thanks guys!

 

[TheoneandonlyMrK]

Sounds like a memory issue try running at 2666 see if the errors go away.

 

[eidairaman1]

Sounds like a memory issue try running at 2666 see if the errors go away.

Memtest 64 may or may not detect a problem. Might try to reseat the ram and check lga pins (never had this problem on zif pga)

 

[Bryce]

Memtest 64 may or may not detect a problem. Might try to reseat the ram and check lga pins (never had this problem on zif pga)

I ran Memtest 64 before, and it said my ram was totally fine. With my last mobo, I never had BSOD. Just this new motherboard. I suspected the Ram, but I took 2 chips out, and left 2 in, no change. The only thing that has prevented these crashes is disabling IGD completely.

Sounds like a memory issue try running at 2666 see if the errors go away.

I'll have to figure out how to do this, currently my motherboard just lets me choose a profile which brings it to 3000mhz, correct timing and voltage. If I disable this profile, they default to 2133 for some reason.

 

[tabascosauz]

Memory management, page fault in nonpaged area, and irql not less or equal are all classic memory instability BSODs. All 3 are honestly difficult to achieve with anything other than memory instability.

The memory being run at "spec" has nothing to do with whether it's stable. XMP is not a guarantee of stability.

MT64 is an ancient program. Run one of the reputed memtests - HCI Memtest, Testmem5, or Karhu, all of which tax memory heavily as well as the memory controller. For someone new to the mem game I recommend grabbing TM5 from overclock.net, the zip comes with various different .cfg custom tests. Instructions in the thread.

Memory Testing with TestMem5 TM5 with custom configs

Hello everybody I am just making a very light tutorial with a collection of custom config files and a DOWNLOAD LINK for TM5 v0.12 anta777 absolut config Official Intel DDR4 24/7 Memory Stability Thread None of the work is mine but it seems like a pretty good and fast testing app Update...

www.overclock.net

As for the memory allocation for the iGPU, it's commonly understood that changing those settings has nothing to do with performance, and may harm iGPU performance despite sounding seemingly better. If you're only using iGPU for screen output, best leave them alone.

Generally, one of the biggest factors in stability is VDIMM. Unfortunately, every board applies VDIMM differently, you cannot assume that XMP 1.35V being set in BIOS has the same result on different boards.

Also, isn't there a iGPU voltage for Intel?

 

[eidairaman1]

I ran Memtest 64 before, and it said my ram was totally fine. With my last mobo, I never had BSOD. Just this new motherboard. I suspected the Ram, but I took 2 chips out, and left 2 in, no change. The only thing that has prevented these crashes is disabling IGD completely.


I'll have to figure out how to do this, currently my motherboard just lets me choose a profile which brings it to 3000mhz, correct timing and voltage. If I disable this profile, they default to 2133 for some reason.

Have you thought of testing 1 module only in all 4 slots and then swapping to another module.

 

[TheoneandonlyMrK]

I ran Memtest 64 before, and it said my ram was totally fine. With my last mobo, I never had BSOD. Just this new motherboard. I suspected the Ram, but I took 2 chips out, and left 2 in, no change. The only thing that has prevented these crashes is disabling IGD completely.


I'll have to figure out how to do this, currently my motherboard just lets me choose a profile which brings it to 3000mhz, correct timing and voltage. If I disable this profile, they default to 2133 for some reason.

For just a trial 2133 is fine ,you only have to use that until it crashes , which it will if it is something else, you said you tested the memory that's why I suggested this, I believe you tested it to be stable, but sometimes I've found they were not long term, doing a particular task or something would trigger a bsd, odd but true.

 

[AlwaysHope]

...
Generally, one of the biggest factors in stability is VDIMM. Unfortunately, every board applies VDIMM differently, you cannot assume that XMP 1.35V being set in BIOS has the same result on different boards.
...

This is what I bet is the problem. Best to manually dial it in, also every board will not guarantee 1.35v precisely is delivered with XMP option in bios. Some droop a little, some over volt a little.

 

[Bryce]

For just a trial 2133 is fine ,you only have to use that until it crashes , which it will if it is something else, you said you tested the memory that's why I suggested this, I believe you tested it to be stable, but sometimes I've found they were not long term, doing a particular task or something would trigger a bsd, odd but true.

So I ran at 2133 for a while, with IGD. It still BSOD and game repeatedly crashed. If I run with IGD disabled on 2133, it works fine.

This is what I bet is the problem. Best to manually dial it in, also every board will not guarantee 1.35v precisely is delivered with XMP option in bios. Some droop a little, some over volt a little.

So does this mean it's something I'd need to manually tweak or something?

 

[AlwaysHope]

So does this mean it's something I'd need to manually tweak or something?

If I were you I would. Can't trust bios to always get Vdimm with XMP perfectly correct voltage applied. Run HWiNFO with auto settings for XMP & check Vdimm, bet its not exactly 1.35v
Btw, check that ALL drivers are up to date, especially the iGPU.

 

[eidairaman1]

So I ran at 2133 for a while, with IGD. It still BSOD and game repeatedly crashed. If I run with IGD disabled on 2133, it works fine.


So does this mean it's something I'd need to manually tweak or something?

Sounds like the igp driver is defective or the cpu itself is.

 

[Bryce]

Sounds like the igp driver is defective or the cpu itself is.

I've updated the driver to the latest one on Intel's website for Intel UHD 750, so far, not a single crash. I'll report back in a day or two to confirm these results.

 

[Bryce]

Update: It must've been the IGD drivers that were on my Motherboard Manufacturers website. After grabbing the latest drivers from Intel Directly, the game crashing, and BSOD have stopped entirely. Thanks for all your help everyone!