[SOLVED] Page Fault in NONPAGED Area BSOD on startup. Safe mode is working. FIX: I removed an old gigabyte driver.

[plath]

Hi everybody,

Well I have a problem I hope someone can please help me with. I just spent about 11 hours empting my PC from it's midtower and changing the motherboard, cpu cooler, ram and CPU and adding a M2 drive. I kept a GPU, case, soundcard and two SSDs and switched a case fan also. After that ordeal it turned on, but sadly i have not yet been able to boot properly into my desktop. Every time, I get a "Page Fault in NONPAGED Area" BSOD, right before I enter the Desktop.

I had an Intel 4670k on a Z97 Mobo and DDR3. I switched my storage, PSU and GPU (Nvidia GTX 1070) into a new system. The new CPU is a Ryzen 7 5700X on a Gigabyte AORUS Elite B550 motherboard and 16gb of Kingston Fury Beast 3600mhz CL17 RAM. PSU is EVGA Supernova G2 750W. I am using the same OS installation for over 10 years although it has been upgraded at some point from Windows 8.1 to Windows 10, I have never formatted in that time. I believe it was originally a retail version, but it is now a license.

I've tried to do some troubleshooting, but I can't get rid of it. I have:

• Disabled "Automatically Manage Paging File Size for All Drives"
• Ran DISM and SFC repair
• Ran Windows Memory Diagnostic Tool, it did not find anything wrong.
• Tried to test all combinations of RAM and slots to isolate the cause, but it did not.
• Checked my SSDs in CrystalDisk

I've also attached my SysnativeBSODCollectionApp zip. I'm posting this right now in safe mode, where it boots fine. Maybe it's a driver conflict perhaps from some old hardware?

 

[axe0]

Hi Plath,

A Gigabyte driver looks to be causing problems which make sense with the driver being close to 15 years old. I would suggest removing the Gigabyte software.

Bugcheck code 00000050
Arguments ffffa600`00000000 00000000`00000000 00000000`00000000 00000000`00000006
Debug session time: Mon Feb  6 21:17:50.971 2023 (UTC + 1:00)
System Uptime: 0 days 0:00:08.553
0: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffce08`4b05f0f8 fffff803`4ea308e6 nt!KeBugCheckEx
01 ffffce08`4b05f100 fffff803`4e842d3d nt!MiZeroFault+0x1f0bb6
02 ffffce08`4b05f1f0 fffff803`4e841fba nt!MiUserFault+0x80d
03 ffffce08`4b05f280 fffff803`4ea09cd8 nt!MmAccessFault+0x16a
04 ffffce08`4b05f420 fffff803`4e8d3b3f nt!KiPageFault+0x358
05 ffffce08`4b05f5b0 fffff803`4e91bdd5 nt!MiMappingHasIoTracker+0x3f
06 ffffce08`4b05f5e0 fffff803`69751552 nt!MmUnmapIoSpace+0x65
07 ffffce08`4b05f720 00000000`c0000002 gdrv+0x1552
08 ffffce08`4b05f728 ffffa706`9e0f4680 0xc0000002
09 ffffce08`4b05f730 00000000`00000000 0xffffa706`9e0f4680

0: kd> lmvm gdrv
Browse full module list
start             end                 module name
fffff803`98620000 fffff803`98629000   gdrv     T (no symbols)           
    Loaded symbol image file: gdrv.sys
    Image path: \??\C:\Windows\gdrv.sys
    Image name: gdrv.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Mar 13 04:22:29 2009 (49B9D175)
    CheckSum:         000105CE
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

 

[plath]

Hi Plath,

A Gigabyte driver looks to be causing problems which make sense with the driver being close to 15 years old. I would suggest removing the Gigabyte software.

Bugcheck code 00000050
Arguments ffffa600`00000000 00000000`00000000 00000000`00000000 00000000`00000006
Debug session time: Mon Feb  6 21:17:50.971 2023 (UTC + 1:00)
System Uptime: 0 days 0:00:08.553
0: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffce08`4b05f0f8 fffff803`4ea308e6 nt!KeBugCheckEx
01 ffffce08`4b05f100 fffff803`4e842d3d nt!MiZeroFault+0x1f0bb6
02 ffffce08`4b05f1f0 fffff803`4e841fba nt!MiUserFault+0x80d
03 ffffce08`4b05f280 fffff803`4ea09cd8 nt!MmAccessFault+0x16a
04 ffffce08`4b05f420 fffff803`4e8d3b3f nt!KiPageFault+0x358
05 ffffce08`4b05f5b0 fffff803`4e91bdd5 nt!MiMappingHasIoTracker+0x3f
06 ffffce08`4b05f5e0 fffff803`69751552 nt!MmUnmapIoSpace+0x65
07 ffffce08`4b05f720 00000000`c0000002 gdrv+0x1552
08 ffffce08`4b05f728 ffffa706`9e0f4680 0xc0000002
09 ffffce08`4b05f730 00000000`00000000 0xffffa706`9e0f4680

0: kd> lmvm gdrv
Browse full module list
start             end                 module name
fffff803`98620000 fffff803`98629000   gdrv     T (no symbols)          
    Loaded symbol image file: gdrv.sys
    Image path: \??\C:\Windows\gdrv.sys
    Image name: gdrv.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Mar 13 04:22:29 2009 (49B9D175)
    CheckSum:         000105CE
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

That's interesting. I just moved from a Gigabyte SOC-Force to an Aorus Elite. Did it before as well. the SOC-Force was from an Asus Z87-K mobo.

Thanks for your sleuthing. I'll try to delete it.

 

[plath]

damn you're a genius. actually booted properly after i deleted all trace of gigabyte from my system. thanks for saving my hide!