[SOLVED] QUOTA_UNDERFLOW BSOD

[dralaamonirsrg]

Good evening folks,
Would like to ask as am getting this weird BSOD ‘sometimes not every time’ when restarting or shutting down pc. Am on win 10 pro latest build fully updated.
cpu ryzen 3600
Ram vengance pro 3600mhz
Power supply corsair rm 850x
Recently been tightning the ram timings
I assumed that it is the cause but the weird thing no ram errors at all, all disks showed no errors, I can game and do anything the only way to get that BSOD is when restarting or shutting down it appears right after the screen where it says restarting
And not all the time. CPU isn’t overclocked or anything. Thinking of just revert the timing to less agressive ones but really was happy to reach 66ns on latency test xD

What do you think guys?

 

[Colif]

if it only started after you played with settings, then relaxing them might remove error

one possible fix -
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC


Set up for minidumps
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

 

[dralaamonirsrg]

if it only started after you played with settings, then relaxing them might remove error

one possible fix -
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC


Set up for minidumps
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

Greetings,
found these dump files saved in the folder:
https://drive.google.com/file/d/1yGdh7SEoKZNb-KAEO4SV2DxbidBynjYt/view?usp=sharing
I have changed to small mini dumps but the bsod did not appear yet since last time I loosen ram timing abit
Will keep restarting to see if it happens xD

 

[Colif]

perhaps we wait and see if you get another one.

No need to try to crash

 

[gardenman]

Hopefully the change fixes the problem. If not, results from dump files are here: https://frutescentrich.htmlpasta.com/

 

[dralaamonirsrg]

Hopefully the change fixes the problem. If not, results from dump files are here: https://frutescentrich.htmlpasta.com/

It happened again unfortunately...
So memory corruption it is?
how should I fix it?
here is the dump file from today
https://drive.google.com/file/d/1QuQIb9gjHs7rIM5KCsd7xQ_g9wmpFYZR/view?usp=sharing
Running MemTest86 now booted from USB
Will see what i will get there not sure if it is testing each stick individually but it is taking long time I let it scan automatically changed nothing

Regards

 

[Colif]

well, i would blame 2 of those on the Nvidia drivers, rest aren't so obvious

Which GPU is it?

I would maybe run DDU and instead of running Geforce experience to get new drivers, try WIndows update instead as they have older drivers from Nvidia which are more stable than the latest from Nvidia - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

I see memory corruption on a lot of BSOD, and not all of them are RAM. Just wrong timings can do it, running ram at wrong speeds.. etc.

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://chariestyak.htmlpasta.com/

File information:	051820-10484-01.dmp (May 18 2020 - 02:03:14)
Bugcheck:	QUOTA_UNDERFLOW (21)
Probably caused by:	ntkrnlmp.exe (Process: SearchIndexer.)
Uptime:	0 Day(s), 14 Hour(s), 46 Min(s), and 20 Sec(s)

Comment: The overclocking driver "RTCore64.sys" was found on your system. (MSI Afterburner)

Possible Motherboard page: https://www.msi.com/Motherboard/b450-tomahawk
There is a BIOS update available for your system. You are using version 1.C and the latest is 1.D. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[dralaamonirsrg]

well, i would blame 2 of those on the Nvidia drivers, rest aren't so obvious

Which GPU is it?

I would maybe run DDU and instead of running Geforce experience to get new drivers, try WIndows update instead as they have older drivers from Nvidia which are more stable than the latest from Nvidia - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

I see memory corruption on a lot of BSOD, and not all of them are RAM. Just wrong timings can do it, running ram at wrong speeds.. etc.

Thanks for the response,
It's 1080ti fe . I do use DDU each time I update drivers and I don't include anything in installation except the drivers. Could it be really MSI afterburner?

I ran the dump file through the debugger and got the following information: https://chariestyak.htmlpasta.com/

File information:	051820-10484-01.dmp (May 18 2020 - 02:03:14)
Bugcheck:	QUOTA_UNDERFLOW (21)
Probably caused by:	ntkrnlmp.exe (Process: SearchIndexer.)
Uptime:	0 Day(s), 14 Hour(s), 46 Min(s), and 20 Sec(s)

Comment: The overclocking driver "RTCore64.sys" was found on your system. (MSI Afterburner)

Possible Motherboard page: https://www.msi.com/Motherboard/b450-tomahawk
There is a BIOS update available for your system. You are using version 1.C and the latest is 1.D. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

Yes sir. Indeed that is my motherboard. I actually was on the latest bios. But latest bios was kind of weird with higher voltages than before. I also couldn't run ram on previous timings I guess it's less tolerating to ram OC. So I downgraded the bios and it amazed me that I could reach nice timings with good bandwidth
but felts stupid when I started to see those BSOD on restart.

Like I can play any game for hours do anything even leave the game running the whole day. But if I restart it will BSOD. I think also it's some driver or device that is not shutting down correctly when the software signals that thing. But can't figure what that is.

I disconnected an old SATA hdd as I think it's abit noisy than before. Running scan by HD tune on other hard drives.

how to clean up drivers? Like deleting them and re-install?
can I go device manager like delete everything xD

I would re-install windows but the office key I have can be activated only once.

 

[Colif]

could update Realtek drivers although your current ones are from Feb - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

your ram -

CMW16GX4M2Z3600C18

is on motherboard website so that is 1 less theory.

But latest bios was kind of weird with higher voltages than before. I also couldn't run ram on previous timings I guess it's less tolerating to ram OC. So I downgraded the bios and it amazed me that I could reach nice timings with good bandwidth

Was ram bought as 2 seperate sticks or a set of 2? it shows as a single on https://www.msi.com/Motherboard/support/B450-TOMAHAWK#support-mem-19

ram speeds shouldn't reduce with a new bios, new bios updates meant to add features, not take them away.

 

[dralaamonirsrg]

could update Realtek drivers although your current ones are from Feb - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

your ram -

CMW16GX4M2Z3600C18

is on motherboard website so that is 1 less theory.



Was ram bought as 2 seperate sticks or a set of 2? it shows as a single on https://www.msi.com/Motherboard/support/B450-TOMAHAWK#support-mem-19

ram speeds shouldn't reduce with a new bios, new bios updates meant to add features, not take them away.

Yes sir, 2 sticks same set.
For the bios yea it shouldn't be like that but yea 1.0.03 abba I can push FCLK to 1867 fre1 3777mhz timings 16-19-14-16 34 56....1.4v
in 1.0.0.4 anything above 1800 fail to boot and I have to reset cmos even timings were unstable.

For the Lan driver actually even if it says package is from April the actual drivers are dated since February.

look also into system log found these errors

https://imgur.com/a/W7TaLoZ

View: https://imgur.com/a/W7TaLoZ


something is trying to start and error is like each second in the log...
what is this??
checked COM+ services both are running not disabled

 

[dralaamonirsrg]

Nevermind think I've fixed that now turning system event notification service from disabled to manual xD

 

[Colif]

event viewer always has errors, the only ones you need to look at are the Crtitical ones. A lot of the others might be 1 time errors and don't normally cause BSOD.

I think its still associated with the ram timings but I get another opinion.
ram speed is 3600, supported speed is 3600, you running it at 3777 is above its max, so could be reason for BSOD.

just handy for me, left is your BIOS, right is MSI website ram list

 

[dralaamonirsrg]

event viewer always has errors, the only ones you need to look at are the Crtitical ones. A lot of the others might be 1 time errors and don't normally cause BSOD.

I think its still associated with the ram timings but I get another opinion.
ram speed is 3600, supported speed is 3600, you running it at 3777 is above its max, so could be reason for BSOD.

just handy for me, left is your BIOS, right is MSI website ram list

Greetings,
Nice ultrawide resolution there 😉
Well, I might update again to latest bios.Today have spent the time on memtest64 from usb
No errors were found. Removed the old hdd scanned all hdd. Did repair the image from any corruption. Went with ram speed back to 3600 kept the timings at 16-19-16-16 36 58
1.42v
Played games for like 9 hours no issues. Decided to restart and I was greeted again with the BSOD with same data as the last one
Ntoskrnl.exe is the cause it says on dump file whocrashed app.

I think updating bios again...
Mabe change the antivirus app...
Ditch intelligent cleaner??
MSI afterburn is mabe another thing but I don’t think i can live without it xD
Ditch intelligent standby list cleaner ?
Ryzen master was installed. I dis also uninstall it before along with dragon center

what else should be done?

 

[Colif]

i have a 4k monitor but running at 2k, its wide enough for me but I see the true ultra wides and my neck aches just thinking about it.

ntoskrnl = victim. Its the brains of windows, without it windows cannot work.

I would run memory at XMP settings and see if you still get BSOD. We fix those and then you can go faster if you want, but if BSOD return its likely ram.
to go faster than 3600 you would need an X570 motherboard

If I were him, I'd stick to current platform and stay with the frequency and voltage or reduce the frequency and tighten timings with that voltage

from discord

 

[dralaamonirsrg]

i have a 4k monitor but running at 2k, its wide enough for me but I see the true ultra wides and my neck aches just thinking about it.

ntoskrnl = victim. Its the brains of windows, without it windows cannot work.

I would run memory at XMP settings and see if you still get BSOD. We fix those and then you can go faster if you want, but if BSOD return its likely ram.
to go faster than 3600 you would need an X570 motherboard


from discord

Alright boss,
Bios updated. left ram on 3600 on timings I've used the safe ones from ryzen calculator used the ram profile extracted by thaiphoon burner it's like 16-21-21-21 it added atleast 1gb/s read speed
filled down each value exactly as it says in the app
so far it's fine. You can't till till you restart and see and it doesn't happen after every single restart
here is ram test :

https://imgur.com/iO0rmsB

View: https://imgur.com/iO0rmsB

I wonder if the memtest86 from usb boot like it tests it against xmpo profile or my bios timings...

and yea am not trying to upgrade so am trying to keep everything maintained. Even the windows used all the dism repair thing ran sfc /scannow.
I'm sick of just formatting windows just because I can't solve the problem especially it coz be a hardware or a bad driver. Lets see how it goes.
Guess after some years we get to have the AI figuring out all of this without that much of an effort xD

 

[dralaamonirsrg]

Just an update...today morning it happened again and when booted to windows one of the hard drives was invisible and I went to check its SATA cable ,found it plugged but kindda bent moving it made the drive showing up again.
Changed the SATA cable and re-scanned the hard drive again. Came without errors.
Could that be the issue? will see if it BSOD again or not.

Regards

 

[Colif]

Quota underflow is such a rare error, that its possible the hdd cable was a cause. It crashed searchindexer so maybe the cable was creating strange results on that drive?

 

[dralaamonirsrg]

Guys...it's Victory!!! Turned out the SATA cable was the fault!!
24h without a BSOD....

Thanks for your support!!
Just incase anybody faces the problem should start with same steps I did with you and Physically check the cables and the hardware..

Much appreciated!!!
Mr@gardenman
Mr@Colif