Jump to content

BSOD loop on Windows 11

Brandon Mathijssen
By Brandon Mathijssen
in Troubleshooting
 Share
Posted (edited)

I'm having a problem where windows will boot and i can log in but after a 2-5 minutes the the pc crashes with one of a few different BSOD's

I have tried a couple of different solutions but so far nothing has worked

 

The bsod's I'm getting are:

 

irql_not_less_or_equal

page fault in nonpaged area

system thread exception not handled

system_service_exception

dpc watchdog violation (only 2 or 3 times)

 

I have tried:

 

Sfc/scannow

Dism scanhealth and restorehealth 

DDU and fresh drivers for the gpu

All drvers up to date (as far as i can tell)

Restored windows 

Reset windows

Tried ram sticks 1 by 1 (tried with one stick at a time) XMP on & off

Memory diagnostic didn't work (Sat on the blue screen saying _%complete then restarted like it had never run)

Ran memtest86 (passed)

Chkdsk /c

Turning off XMP

 

I7 13700k

Gigabyte B760 aorus elite ax 

32gb corsair vengeance ddr5 5600mhz

Gtx 1080ti fe

Samsung 980 pro 1tb

 

Dumps.zip

Edited by Brandon Mathijssen
Link to comment
https://linustechtips.com/topic/1511914-bsod-loop-on-windows-11/
Share on other sites
Link to post
Share on other sites
Posted

Your memory is throwing errors.

 

Is this a new build? Did it ever work right?

 

Try down clocking the ram to 4800 and run it at the XMP voltage. 
 

If that works, either live with it or get a different set of ram. Make sure it’s in the QVL list.

Link to post
Share on other sites
Posted

I've had irql when oc my ddr4 ram, given reputation of intel 13th gen and ddr5, its probably that.

you can use latencyMon to check latency of various drivers, to rule out any anomolies thats not memory related. But its probably the memory. try some memory stability tests, you'll probably bsod.

you can give memory controller more/less power, the memory itself more/less power to see how it goes, but i don't like that i'm telling people to mess around with those type of stuff, xmp "should just work". start by feeding the ram a little bit more power, see if it becomes stable. usually xmp profile raises the default vdimm anyways.

 

you should google "13th gen ddr5 issues" in various forums and reddit, see if someone else has a fix or if it is universally a lottery.

Link to post
Share on other sites
Posted

Can you reset your bios to stock, and see if that helps?  Also with bios stock, try the 1 stick then the other.

 

Also when I look up your "Gigabyte B760 aorus elite ax" it looks to support only DDR4:

https://download.gigabyte.com/FileList/Manual/mb_manual_b760-aorus-elite_1101_e_230420.pdf?v=dbae1bad340007913911492441209bfc

 

Is it a different revision or is the model sightly different?  I just wanted to look to see if there was a clear CMOS button on it you could also try vs. having to pull the battery and wait + hold down the power button for few min with the computer unplugged and no battery.  The holding the power button while the computer is unplugged drains the caps.

 

 

P.S. also a major Mass Effect fan here, love your pic.

Current build

https://pcpartpicker.com/b/pcY9TW

Link to post
Share on other sites
Posted
  • Author
26 minutes ago, DarkWaterSong said:

Can you reset your bios to stock, and see if that helps?  Also with bios stock, try the 1 stick then the other.

 

Also when I look up your "Gigabyte B760 aorus elite ax" it looks to support only DDR4:

https://download.gigabyte.com/FileList/Manual/mb_manual_b760-aorus-elite_1101_e_230420.pdf?v=dbae1bad340007913911492441209bfc

 

Is it a different revision or is the model sightly different?  I just wanted to look to see if there was a clear CMOS button on it you could also try vs. having to pull the battery and wait + hold down the power button for few min with the computer unplugged and no battery.  The holding the power button while the computer is unplugged drains the caps.

 

 

P.S. also a major Mass Effect fan here, love your pic.

This is the MB I've got, it definitely ddr5.

https://www.gigabyte.com/Motherboard/B760-AORUS-ELITE-AX-rev-1x#kf

 

Cant remember if there a cmos button and im at work at the moment

Link to post
Share on other sites
Posted
5 minutes ago, Brandon Mathijssen said:

This is the MB I've got, it definitely ddr5.

https://www.gigabyte.com/Motherboard/B760-AORUS-ELITE-AX-rev-1x#kf

 

Cant remember if there a cmos button and im at work at the moment

See 18, and I figured it out.  They stuck several revisions of the board in the same manual 🤦‍♀️

Also what bios are you on?  Just this board may have a newer bios that plays nicer with your memory, also looked it up this is what you support:

mb_memory_B760-6L-L7-1-D5.pdf

image.png.f1f3e5e7d921f002d92a841866b2d996.png

Current build

https://pcpartpicker.com/b/pcY9TW

Link to post
Share on other sites
Posted
3 minutes ago, Brandon Mathijssen said:

Not sure what bios I have but i updated it when i built it about a month ago and it was the newest one at the time

I would just find the version, and google if there are any issues with that version.  I actually had a really bad on for my MB that caused my bluetooth and wifi to just disappear out of device manger.  Only way to fix was turn off the PC, unplug it, hold down the power button for 10 secs, and then it would be fixed for around 24 hours.

 

Problem is I could not roll back, because the previous version did not support my CPU but a newer version fixed the issue.  Also my issue was well documented for my board, and all over the Asus forums.

Current build

https://pcpartpicker.com/b/pcY9TW

Link to post
Share on other sites
Posted
  • Author

Looking at the page for my board there is a new bios from 10 days ago I'm just not sure if doing a bios update is a good idea with the pc crashing so often, or is that not an issue if its just in the bios?

 

Also this is the ram i have in at the moment

https://www.pbtech.co.nz/product/MEMCOR11502A/Corsair-VENGEANCE-RGB-32GB-DDR5-Desktop-RAM-Kit-2x

Link to post
Share on other sites
Posted
  • Author
6 hours ago, Whatisthis said:

Turn off XMP and see if it starts working. Check the voltage and give it a bump to the XMP voltage.

Nope still doing it with xmp disabled 

 

As the pc is still new and i dont have too much stuff on it yet and also i only use it for gaming would a clean install of windows fix this problem?

Link to post
Share on other sites
Posted
26 minutes ago, Brandon Mathijssen said:

Nope still doing it with xmp disabled 

 

As the pc is still new and i dont have too much stuff on it yet and also i only use it for gaming would a clean install of windows fix this problem?

Run the machine with one stick at a time and see if only one of them cause a crash. 

Link to post
Share on other sites
Posted
  • Author
17 minutes ago, Bjoolz said:

Run the machine with one stick at a time and see if only one of them cause a crash. 

Already tried that and they both did, but that was with xmp on, guess i could try it again with it off but that will have to wait till tomorrow 

Link to post
Share on other sites
Posted
17 hours ago, Brandon Mathijssen said:

Dump files above, hopefully i did it right.

Hmmmm.. RAM is definitely not off the table, but there are some things here that are a bit too consistent for RAM. You can get false patterns, let's say you have a 100 crashes and pick 5 dump files from those, you could see a pattern in those five that don't exist when you look at all 100. The pattern I think I am seeing is that on several of these it happens when allocating space in the memory pool. An Intel driver is often involved.

 

When it's RAM it's usually wildly random as it's random what uses the part of memory that corrupts data (EDIT: Same with memory controller which I touch on later). 

 

I don't know if you updated the BIOS after this issue started happening, but I see that you are running a beta BIOS. I would try version F2 (Versions that end in a letter are beta versions). Second I would try updating the Chipset driver. 

 

Quote

Also i tried the ram sticks 1 at a time with xmp off but it didnt make a difference 😔 

That makes it way less likely that it's RAM, I see that you are running it on 4800MT/s so while it can be a compatibility issue I haven't seen much of that on Intel (Except 12th gen whose memory controller was a bit of dog) when running at low speeds. A faulty memory controller is quite rare, but possible as we are seeing Intel drivers involved. It could also be teething issues on the new motherboards that some edge case users are experiencing. Not many BIOS versions have been released yet for this board. 

Link to post
Share on other sites
Posted
  • Author
3 hours ago, Bjoolz said:

Hmmmm.. RAM is definitely not off the table, but there are some things here that are a bit too consistent for RAM. You can get false patterns, let's say you have a 100 crashes and pick 5 dump files from those, you could see a pattern in those five that don't exist when you look at all 100. The pattern I think I am seeing is that on several of these it happens when allocating space in the memory pool. An Intel driver is often involved.

 

When it's RAM it's usually wildly random as it's random what uses the part of memory that corrupts data (EDIT: Same with memory controller which I touch on later). 

 

I don't know if you updated the BIOS after this issue started happening, but I see that you are running a beta BIOS. I would try version F2 (Version that end in a letter are beta versions). Second I would try updating the Chipset driver. 

 

That makes it way less likely that it's RAM, I see that you are running it on 4800MT/s so while it can be a compatibility issue I haven't seen much of that on Intel (Except 12th gen whose memory controller was a bit of dog) when running at low speeds. A faulty memory controller is quite rare, but possible as we are seeing Intel drivers involved. It could also be teething issues on the new motherboards that some edge case users are experiencing. Not many BIOS versions have been released yet for this board. 

I updated the bios just after i got it running and installed windows, but yeah my bad, i didnt realize the ones with letters were beta versions so i'll go change that.

I dont know if it helps but i ran memtest86 and that passed, it was on 4800mh/xmp off at the time

 

Also after a bios and chipset driver update and assuming its not a hardware problem would a clean install of windows help or is something outside that?

Link to post
Share on other sites
Posted
2 minutes ago, Brandon Mathijssen said:

I updated the bios just after i got it running and installed windows, but yeah my bad, i didnt realize the ones with letters were beta versions so i'll go change that.

I dont know if it helps but i ran memtest86 and that passed, it was on 4800mh/xmp off at the time

 

Also after a bios and chipset driver update and assuming it’s not a hardware problem would a clean install of windows help or is something outside that?

It’s not a bad idea to clean install. There could be corruption due to the bsods you’ve had and a fresh install would eliminate issues as a result of that.

Link to post
Share on other sites
Posted
  • Author

So i tried the bios update and that went fine

The Chipset driver didn't make any difference 

I tried to clean install windows however it keeps blue screening during windows setup, but now its always the same bsod

 

irql_not_less_or_equal

 

So at this point i'm guessing it is the ram?

Do i go and buy some new ram or have i broken something else 🤣🤦‍♂️

 

And if your wondering, yes windows is dead, I can only get to the bios

giphy.gif

Link to post
Share on other sites
Posted
39 minutes ago, Brandon Mathijssen said:

So i tried the bios update and that went fine

The Chipset driver didn't make any difference 

I tried to clean install windows however it keeps blue screening during windows setup, but now its always the same bsod

 

irql_not_less_or_equal

 

So at this point i'm guessing it is the ram?

Do i go and buy some new ram or have i broken something else 🤣🤦‍♂️

 

And if your wondering, yes windows is dead, I can only get to the bios

giphy.gif

Run it with one stick at a time, the chance of both sticks being bad is exceedingly low. And as the other user mentioned, the OS can corrupt from all the crashes. 

Link to post
Share on other sites
Posted
  • Author
20 minutes ago, Bjoolz said:

Run it with one stick at a time, the chance of both sticks being bad is exceedingly low. And as the other user mentioned, the OS can corrupt from all the crashes. 

One stick seems to work a little better that the other but they both crash

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×