[SOLVED] Cant figure out why I'm getting BSOD on a game

[roorffxi23]

So I am getting BSOD only when I am playing certain games. The two ive noticed are FIFA 23 and Battlefield 5. I have played RDR2, Facry, GTA and have had no issues.

My CPU and GPU temps are 70-80cs when playing these games.

Getting BSOD DRIVER_OVERRAN_STACK_BUFFER and IRQL_NOT_LESS_OR_EQUAL

I have freshly installed Windows twice now.
Checked RAM and passed 11 tests overnight with memtest86
I've run sfc scans
I've tested my hard drive with the built-in windows hard drive checker
I have tried updating all my drivers
I have no overclocking



Those temps are about the same in RDR2 and I play for hours with no issues. With Fifa/Battlefield I BSOD in 20mins

PC Specs: i9-10850K
MasterLiquid Lite 120mm (I think it may be an overheating problem)
1TB WD Blue SN550 Series
16GB (8GBx2) DDR4/3200MHz
Asus Z590 ATX
Windows 11
Monitor is LG 27GL83A-B"

some BSODS here: https://www.dropbox.com/scl/fo/mu7a7sae6oo9g8kpk0l6m/h?dl=0&rlkey=m36tomi534yqxmxpi8e3xlze2

Not sure what to do anymore.

 

[johnbl]

bugcheck was a bad cpu instruction pointer running your game.
generally I see this with heating problems, overclock problems, and electrical problems.

the sata controller driver gets updated via windows update if you use the microsoft provided version.

you might disable these drivers:
AsIO2.sys Mon May 31 18:42:16 2021
AsIO3.sys Wed May 18 19:51:01 2022

they might tweak gpu speeds. they are a interface to the hardware for the asus software.

used to check ram temps and gpu . not sure what other functions they might have.

 

[roorffxi23]

Not sure where
AsIO2.sys Mon May 31 18:42:16 2021
AsIO3.sys Wed May 18 19:51:01 2022

are or under to disable under my device manager

When i google it says this

AsIO2.sys and AsIO3.sys are drivers for Asmedia USB 3.0 Host Controller. They are used to control the USB 3.0 ports on your computer. The drivers are installed by default on Windows computers.
If you are experiencing problems with your USB 3.0 ports, you can try disabling or uninstalling the drivers. However, this may cause problems with other USB devices, such as your mouse and keyboard.
If you are unsure whether or not to disable or uninstall the drivers, you should contact the manufacturer of your computer or Asmedia for further assistance.

 

[roorffxi23]

Would higher temps to CPU be an issue? It doesn't run any hotter than RDR2 does at mid-70s C

 

[roorffxi23]

I left the game running in the training mode and when i came back after about 40min it had BSOD. Didn't do too much since the last test wanted to see if it would BSOD if i just left it idle.

This time it was a

PAGE_FAULT_IN_NONPAGED_AREA

If i read it right the process that caused it was MsMpEng.exe which is Windows defender.

https://www.dropbox.com/s/hrc3b86m4xpsbmx/032723-5687-01.dmp?dl=0


Update: I disabled Windows Defender and still BSOD. This time i got a

INTERRUPT_EXCEPTION_NOT_HANDLED

DMP:

https://www.dropbox.com/s/1co9lvg36bmt15l/032723-5765-01.dmp?dl=0

 

[johnbl]

bugcheck was in
nt!HalpApicConvertToRte

i think this has to do with advanced peripheral interrupt controller
this is something low level in the hardware. Something that should be set up by the BIOS or chipset drivers. like a usb 3 interface, SPI, it could be some sensors on the motherboard, it could be GPIO

generally, you update the bios, or go into bios make any setting change and set it back and save the configuration.
boot into windows, go into control panel, device manager and check for any setup failure. (yellow icon)

if you moved windows drive from another machine and with out reinstalling you would have to reinstall or maybe find the device and delete it from device manager to get plug and play to reinstall the device.

note: asmedia usb 3 host controllers might have firmware updates that have to be installed
(at least in the old versions I had on my motherboard during the early usb 3 days)

note: I expectes that
asio2.sys and asio3.sys were part of asus input output probe
for controlling asus hardware. installed via armory crate but not removed when it is disabled. i think they have asus armory crate cleaner utility to clean up the drivers.
I do not run armory crate. I do not like the idea of the bios putting files directly on my drive

 

[johnbl]

bugcheck was in
nt!HalpApicConvertToRte

i think this has to do with advanced peripheral interrupt controller
this is something low level in the hardware. Something that should be set up by the BIOS or chipset drivers. like a usb 3 interface, SPI, it could be some sensors on the motherboard, it could be GPIO

generally, you update the bios, or go into bios make any setting change and set it back and save the configuration.
boot into windows, go into control panel, device manager and check for any setup failure. (yellow icon)

if you moved windows drive from another machine and with out reinstalling you would have to reinstall or maybe find the device and delete it from device manager to get plug and play to reinstall the device.

note: asmedia usb 3 host controllers might have firmware updates that have to be installed
(at least in the old versions I had on my motherboard during the early usb 3 days)

note: I expectes that
asio2.sys and asio3.sys were part of asus input output probe
for controlling asus hardware. installed via armory crate but not removed when it is disabled. i think they have asus armory crate cleaner utility to clean up the drivers.
I do not run armory crate. I do not like the idea of the bios putting files directly on my drive

you might keep asus armory create disabled in bios, then do a clean reinstall but do not install the asus utilities.
(if you are not willing to disable the two asus io drivers using microsoft autoruns)

I guess you could also just do a full install of asus armory crate tools so the interrupt works.

start cmd.exe as an admin and run
driverquery.exe
it should list the asio drivers and maybe what it is for

 

[johnbl]

a gpio controller would account for the interrupt bugcheck:
try the below instructions.

instructions for removing left over pieces of armory crate:
from this location:Error code 5: Access is denied - AsIO3.sys!! - Republic of Gamers Forum - 865939 (asus.com)

1. press WIN+R
2. input: REGEDIT
3. path to: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
4. find: "Asusgio2" and "Asusgio3" folder in the left tree window.
5. check the right window, remember the [ImagePath], just like mine is "C:\Windows\system32\drivers\AsIO3.sys"
6. delete these two folders "Asusgio2" and "Asusgio3" in the left tree window in regedit.
7. delete these two files "AsIO2.sys" and "AsIO3.sys" in the path "C:\Windows\system32\drivers"
8. reboot your computer, done!!

 

[roorffxi23]

I don't have any yellow marks in Device Manager. I am more than happy to disable the asi02 and 3 just wasn't sure how. I will try your last recommendation to remove them. Did you say re-install windows again but make sure disable armory crate is on before I boot? Also, I did re-update my BIOS drivers and I did notice Asus has AI Tweaking as auto, Ive read EA doesnt like OC at all. Think this could be it? Ill try disabling the asi02/3 tonight.

 

[roorffxi23]

a gpio controller would account for the interrupt bugcheck:
try the below instructions.

instructions for removing left over pieces of armory crate:
from this location:Error code 5: Access is denied - AsIO3.sys!! - Republic of Gamers Forum - 865939 (asus.com)

1. press WIN+R
2. input: REGEDIT
3. path to: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
4. find: "Asusgio2" and "Asusgio3" folder in the left tree window.
5. check the right window, remember the [ImagePath], just like mine is "C:\Windows\system32\drivers\AsIO3.sys"
6. delete these two folders "Asusgio2" and "Asusgio3" in the left tree window in regedit.
7. delete these two files "AsIO2.sys" and "AsIO3.sys" in the path "C:\Windows\system32\drivers"
8. reboot your computer, done!!

Well, I was able to play for 45mins I did it earlier and BSOD, but forgot to delete the drivers. So first BSOD is with drivers still on my pc and registry deleted. Second is with both deleted.

https://www.dropbox.com/scl/fo/u63ej5r68xk0hg7rz6ds0/h?dl=0&rlkey=8lguivvrqg1mp6lzm5klzzjtx


032823-5640-01 = first BSOD for tonight

 

[johnbl]

you only have one suspect driver left:
msio64.sys I think it is used to control lights on some device:
MsIo64.sys Windows process - What is it? (file.net)
I would use autoruns to disable the driver and reboot.

one of the three bugchecks indicated a problem from the USB susb system.
this could mean that some usb device might need to be updated, (firmware)

you should remove the msio64 driver, then also change the memory dump to kernel, run your game and provide the kernel dump if/when you get the next bugcheck.
kernel dumps are the file memory.dmp and will contain the logs and info for what each cpu is running at the time of the crash.

you could also look into running verifier.exe to see if it catches some driver doing something wrong.

most of the failures have been when running the game, something could be wrong with the game or the syswow64 subsystem.

 

[roorffxi23]

you only have one suspect driver left:
msio64.sys I think it is used to control lights on some device:
MsIo64.sys Windows process - What is it? (file.net)
I would use autoruns to disable the driver and reboot.

one of the three bugchecks indicated a problem from the USB susb system.
this could mean that some usb device might need to be updated, (firmware)

you should remove the msio64 driver, then also change the memory dump to kernel, run your game and provide the kernel dump if/when you get the next bugcheck.
kernel dumps are the file memory.dmp and will contain the logs and info for what each cpu is running at the time of the crash.

you could also look into running verifier.exe to see if it catches some driver doing something wrong.

most of the failures have been when running the game, something could be wrong with the game or the syswow64 subsystem.

By autoruns you mean this:

https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

Correct? I uninstalled MSI afterburner, but I'm sure stuff stayed in the registry. I don't mind deleting it from the driver folder/registry if you think that is better.

Will change it to kernel tonight, isn't this file usually pretty big "memory.dmp"

Do you know what firmware I would need to update my USB?

 

[roorffxi23]

you only have one suspect driver left:
msio64.sys I think it is used to control lights on some device:
MsIo64.sys Windows process - What is it? (file.net)
I would use autoruns to disable the driver and reboot.

one of the three bugchecks indicated a problem from the USB susb system.
this could mean that some usb device might need to be updated, (firmware)

you should remove the msio64 driver, then also change the memory dump to kernel, run your game and provide the kernel dump if/when you get the next bugcheck.
kernel dumps are the file memory.dmp and will contain the logs and info for what each cpu is running at the time of the crash.

you could also look into running verifier.exe to see if it catches some driver doing something wrong.

most of the failures have been when running the game, something could be wrong with the game or the syswow64 subsystem.

Todays .DMP

https://www.dropbox.com/s/g73igu389cojdau/032923-5703-01.dmp?dl=0

i enabled complete but looked like a mini.

I couldnt delete Msi065 in the autorun but i did delete a driver that had .old in system32

I noticed this with autoruns

https://imgur.com/a/8DTLXKr

View: https://imgur.com/a/8DTLXKr

 

[roorffxi23]

Don't want to jinx it yet, but I was able to play a lot longer today than any other not. I played about 1.5 hours and NO BSOD!!

What I have done since a clean install:

1. Clean Windows install
2. Disabled Asus armoury crate from the bios
3. I downloaded all drivers (beforehand - GPU, Sound, Wifi, Chipset, BIOS, USB, Intel) and disconnected from the internet - Installed all drivers
4. Re-connected to the internet and allowed windows to install all updates/drivers I may have missed. Even did the optional Windows update setting.
5. Made anything that was associated with FIFA (steam, EA Play, EAanticheat, etc) installed with admin rights
6. Made sure all things associated with FIFA ran always as admin
7. Disabled all overlays (Steam, Discord, & Nvidia)
8. Made Windows clear the pagefile.sys on shutdown.
9. Disabled Fast Startup in the Power Options
10. Lastly, I did every step in THIS video, and THIS video that applied to me

I believe that is all I have done since the last install. I will try to play again during the weekend and post any BSOD if I do or if it's been a success.

 

[roorffxi23]

Rip maybe i talked too soon.

Looks like I may have been hopeful. Got two BSOD today in the first game about for both of these BSOD about 15 minutes in for both


https://www.dropbox.com/scl/fo/oysamy5ifxyi6uy946vo6/h?dl=0&rlkey=v45tzg00vo9oi4tx53kkqo6yf


At least these seem to be the same type of BSOD.

 

[roorffxi23]

Solution: Disable TURBO BOOST in your Bios settings. It is under Advanced > CPU Power Management. I guess for some reason EA Play doesnt like CPU Coreclock speeds to fluctuate with some boards/CPUS and causes it to crash.