[RESOLVED]Not Enough Storage is Available to Process this Command - Error

[jmine]

A new issue has developed in my build. While in Attract Mode I keep getting the following error "Not Enough Storage is Available to Process this command". I have seen this error on the back glass with the error box header "PinballX Back Glass" and on the playfield with the same error with the error box titled simply PinballX. I was able to capture the full error code from the back glass attached as Not Enough Storage Error. I have also attached my config, log, and plugin logger file. I found a recommendation on Microsoft TechWeb to add and increase IRPStackSize in the registry, I did this, it is now set at decimal 45 (Max is 50). I do not see where this helped. It seems to take place after attract mode has been running 10 to 20 min.

I know it is not a HDD issue, I have a 500GB SSD with 400GB free. I have 16GM RAM in the system, so should not be an issue there. The GTX-760 GPU should have plenty, and the Intel Internal GPU is set at the maximum so it should be OK.

Any one ever experienced this before? Any ideas I can try to fix it?

log.txt

Not Enough Storage Error.txt

PinballX.ini

Logger.txt

[Draco1962]

Moving this thread to the correct forum for the right attention. Please be aware of where you are posting! Thanks!

[jmine]

As a test I removed all back glass and table videos leaving only the images for each of the 30 games in the cabinet. The system ran all night in attract mode with no problems. So now I know the "Not enough Space to Process this Command" error is being caused by PBX playing the videos. In addition to increasing the IRPStackSize in the registry to 49 I have also doubled the available swap file space, but doing this had no effect on the problem. If anyone has any ideas on what else I might try to fix this please let me know. Thanks.

[Draco1962]

You may want to disable plugins for right now and see if that remedies the issue. Per your log.txt you have the Function Logger plugin enabled.

[Adultery]

Function Logger isn't the issue, I believe that's a generic display issue error. Do you happen to know what table caused this? Or more specifically can you recreate it using specific tables or do some work one time and not the next? I feel like it may be a corrupted video or something.

[Draco1962]

I suggested that to take it out of the equation and bring his settings to more of a baseline settup. You are likely correct.

[jmine]

Actually it was doing this before I turned on the function logger. I turned it on hoping it would provide a clue to the problem. As far as being caused by a specific table or back glass video, I do not think so. I just put all the videos back in the folders and ran some more tests. I discovered I can create the error by manually cycling between games, (so system need not be in attract mode). I started cycling from game to game every three or four seconds and after five or ten minutes the first indication of a problem was the system started showing the wrong playfield video, or not changing the playfield video, it would start to stall (not react to right left commands), then start working again (like the system was catching up) and after a few more cycles the error appears, and things stop! I did this three times and each time the error appeared it was a different table.

[jmine]

Troubleshooting continues: I updated the bios, made sure all Windows updates were installed, changed the main monitor from 3840X1080 HDMI to 1920X1080 VGA, to see it that would make a difference; but still throwing the same "Not Enough Storage to Process this Command" error after about 10-15 min in attract mode with the table and back glass videos in place. I also tested with any other programs such as anti-virus, UltraMon, dual screen management, and VirtuMVP 2.0, disabled, but still the same. I'm running out of ideas!!

[tthurman]

I'm betting this will be one of those "something really bizarre" being the culprit cases.

So it just started doing this all of the sudden?

Have you tried an over the top re-install of PBX?

Possibly consider backing up your config, uninstall, run a registry cleaner, such as ccleaner, and re-install.

[jmine]

tthurman, thanks for the tips, First time I have tried CCleaner, it looks like a quality utility to have in the tool pouch

I did an over the top install of PBX and I ran the registry cleaner, it sure found a lot of issues, I re-installed the .Net Framework 4.5.2,

Sadly, I am still having the same problem.... None of the stress test software I have run (Intel, or EVGA) have shown any problems, and I can play all the Pinball tables for hours with no problems. It just seems to be the table and back glass videos in PBX that trigger the error.

[jmine]

So I tried running attract mode with only the backglass videos in place and no Table videos and it through the error in about 10 minutes. I then reversed the process and had only the table videos and no backglass videos and it ran for over 45 min with no error! So I'm going to let it run this way all night and see if it stay's stable, if it does that points to the backgless videos as the cause. That would be good at least it narrows down the search. I will follow-up tomorrow.

[jmine]

Well it ran all night with only the table videos. So this morning I took the backglass monitor and moved it to the GTX760 and turned off the internal Intel Graphics, thinking the internal graphics may be the problem. But not so, as soon as I put the backglass videos back in the system it through the error again, even with the backglass monitor on the GTX and with the internal graphics set to off in the bios. So that eliminates that as the suspect! One other odd thing, the last time it through the error, it was leaving "Line Drive" and bringing up "Abra Ca Dabra" nether has a backglass video! Grrrr....

[Carny_Priest]

Where did you get the backglass videos?

Are you running the Shark codec pack found on the PinballX home page? It is what is recommended.

[jmine]

Carny_Priest, The backgless videos come from the PinballX FTP service. I was running the Shark codec pack, but had the same issue so uninstalled it. I eliminated half of the videos today and only tried running with eight of them in place, and it still was causing the error, I took them all out and all was fine!! Next step is to try adding them back one at a time to see what happens with one or two or three etc...

[Carny_Priest]

Could just be that a video got corrupted on download. Redownloading may be the fix.

Or the file on the FTP is corrupt. I count vouch for any of that table video media. I don't use them.

My experience is that the Shark codec pack on the PBX home page is what works the best. YMMV

[jmine]

I have a work around, but do not consider the issue resolved, but I also am not going to spend any more time on it so will mark the thread resolved. I have found that I can have video backglass or video tables in the menu, just not both for the same table. The only time the system seems to through the error is if both table and backglass videos run at the same time. So I will pick one, and simply avoid having both. Sorry to anyone else who might have this issue but I just cant spend any more time on it and will live with the work around. Thanks.