windows10 Many unique BSOD errors on fresh windows install.

[weebuwu]

First ever install of windows so I could play a single game from steam. I've troubleshooted myself for hours yesterday and today to no avail.

It doesn't seem to matter whether I'm loading rust (the game) or not as the system crashes when doing nothing or when in game.

some stop code's I caught are as listed:

 

IRQL_NOT_LESS_OR_EQUAL

PAGE_FAULT_IN_NONPAGED_AREA what failed: dxgmms2.sys

SYSTEM_SERVICE_EXCEPTION

SYSTEM_SERVICE_EXCEPTION what failed: win32kfull.sys

 

I have tried using ddu to uninstall all drivers including the integrated gpu drivers, then reinstalling only nvidia drivers.

I have done 2 different fresh installs, both of which have been failing me.

My ram appears all good after leaving memtest to run for 5 hours completing multiple passes of 28gbs of my ram.  left with no errors (4 gigs left for OS to run)

I'm unsure what I am doing wrong and have no clue how to solve these issues, any help is greatly appreciated.

[TheGlenlivet]

Create a thumb drive with memtest on it, and remove all but 1 of your ram sticks, testing them individually.  You don't want your OS running in the background when you run memtest.

If you test all your sticks and they all pass then the next most likely issue with those bsod codes would be the drive the OS is installed on going bad..

[PDifolco]

17 minutes ago, weebuwu said:

First ever install of windows so I could play a single game from steam. I've troubleshooted myself for hours yesterday and today to no avail.

It doesn't seem to matter whether I'm loading rust (the game) or not as the system crashes when doing nothing or when in game.

some stop code's I caught are as listed:

 

IRQL_NOT_LESS_OR_EQUAL

PAGE_FAULT_IN_NONPAGED_AREA what failed: dxgmms2.sys

SYSTEM_SERVICE_EXCEPTION

SYSTEM_SERVICE_EXCEPTION what failed: win32kfull.sys

 

I have tried using ddu to uninstall all drivers including the integrated gpu drivers, then reinstalling only nvidia drivers.

I have done 2 different fresh installs, both of which have been failing me.

My ram appears all good after leaving memtest to run for 5 hours completing multiple passes of 28gbs of my ram.  left with no errors (4 gigs left for OS to run)

I'm unsure what I am doing wrong and have no clue how to solve these issues, any help is greatly appreciated.

Could be unstable/bad memory

What's your specs and RAM speeds ?

 

[weebuwu]

I assumed the first drive i installed this on was bad, which is why I have done a fresh install on a brand new ssd that had just arrived this morning. I am working on the memtest now I did not know best practice for memtest thank you for the information.

[weebuwu]

12 minutes ago, PDifolco said:

Could be unstable/bad memory

What's your specs and RAM speeds ?

 

ram in dual channel, 5200 megatransfer runs very stable on my linux distro so i did not touch it and have expo disabled.

crucial ddr5 pro

ryzen 7 7700x

gtx 1070

msi pro b650m-p mobo

linux on nvme ssd

windows on sata ssd

hyper 212 cooler

 

Edit: rm850x corsair psu

[weebuwu]

Okay, im writing memtest to a usb now. When im testing ram does it matter which stick i leave in?

Should i test one stick and then the other?

 

And again, thank you for your time.

[SpookyCitrus]

The BSODs you are getting are memory related. If the ram tests fine and it happens with EXPO enabled and disabled, I'd try a different kit. If it still has issues it could be the board or the CPU. If you haven't already you should update your bios to the latest version as that can fix ram issues. 

 

As for testing with memtest, you should be able to test with both modules installed. If it detects errors then you should test each stick individually. 

[Bjoolz]

51 minutes ago, weebuwu said:

Okay, im writing memtest to a usb now. When im testing ram does it matter which stick i leave in?

Should i test one stick and then the other?

 

And again, thank you for your time.

The random crash errors makes it likely a memory issue. Memory doesn't have to mean RAM, but it's usually the main suspect and the easiest to test. The other possibilities being the CPU because that has the memory controller and storage because of the page file. If you crash often you might as well just use the PC normally with one stick at a time. Memory testers aren't that reliable with DDR4 and newer. If it crashes with either stick, it's likely not RAM. Upload the dump files so we can look more directly at it, but the CPU would probably be the next suspect because none of these crash errors are directly storage related which you usually see at least a few of when it's storage.

 

Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

[weebuwu]

44 minutes ago, Bjoolz said:

The random crash errors makes it likely a memory issue. Memory doesn't have to mean RAM, but it's usually the main suspect and the easiest to test. The other possibilities being the CPU because that has the memory controller and storage because of the page file. If you crash often you might as well just use the PC normally with one stick at a time. Memory testers aren't that reliable with DDR4 and newer. If it crashes with either stick, it's likely not RAM. Upload the dump files so we can look more directly at it, but the CPU would probably be the next suspect because none of these crash errors are directly storage related which you usually see at least a few of when it's storage.

 

Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

It uhh.. it mught be the ram

 

Completely unrelated but jow to i go about rma'ing crucial ram

 

At 7037 errors now

[weebuwu]

Okay, with 7000 errors within the firsy coiple mimutes of testing, that is just bad ram right? Im testing the other stick now.

 

Should i mark as solved?

[Bjoolz]

48 minutes ago, weebuwu said:

It uhh.. it mught be the ram

 

Completely unrelated but jow to i go about rma'ing crucial ram

 

At 7037 errors now

Scroll down to where it shows a link for each region: https://www.crucial.com/company/warranty

[weebuwu]

RMA'ing right now, thank you much!