Insufficient Resources/Access Denied error - Plenty resources available

Maverickbcp

Member
Nov 7, 2013
145
0
76
As the title says I've been getting this error lately after the PC has been on for a few days straight running one Handbrake job after another. Right before I get this error I'll get signs like not being able to navigate in a folder I already had opened or when I try to launch an item on my Quick Launch bar it acts as if that program is no longer installed. When I go to launch task manager I'll get the system resources error.

I'll close any of my open programs apparently "freeing" up enough resources to allow me to launch Task Manager. When I do I'll plainly see I have over 10gb's of free ram and my cpu barely topping 60%. My hard drive isn't anywhere near full and I can find my system errors/faults in the system viewer.

I'm running Win 7 i7 4770k, 16gb ram, & a 250gb ssd with Windows managed page file size. This is a relatively new system. I used this hard drive/OS on my last system without this issue but never tried such lengthy Handbrake jobs either. I did a fresh reinstall of the OS when I built my new system. I can't seem to figure out what resource I could possibly be taking up to cause the error.

I'm running Win 7 64bit.
 
Last edited:

Virgorising

Diamond Member
Apr 9, 2013
4,470
0
0
Does this sound like a bad driver issue to anyone else? Cause it does to me.

Do you see odd or redundant or excessive things listed in Task Manger eating things up?
 
Last edited:

VirtualLarry

No Lifer
Aug 25, 2001
56,552
10,171
126
System resources are not RAM. It's an internal list of "tokens" used as handles to Windows' objects.

There is a global system-wide limit of 65535 of them, no matter how much RAM you have.

Actually, I think that there is two pools, one for GDI handles, and one for System handles. Still, the principle is the same.
 

Maverickbcp

Member
Nov 7, 2013
145
0
76
System resources are not RAM. It's an internal list of "tokens" used as handles to Windows' objects.

There is a global system-wide limit of 65535 of them, no matter how much RAM you have.

Actually, I think that there is two pools, one for GDI handles, and one for System handles. Still, the principle is the same.

True but usually whenever you see this message it's normally due to lack of ram, cpu, or most commonly hard drive space. None of which fit my issue. What would you suggest? I've been in IT for years and obviously haven't looked everywhere yet but have checked quite a lot with nothing becoming apparent to me.

Nothing seems astray in task manager. My normal top 3-4 processes taking up the most while still leaving over 40-50% remaining. I've found no faults anywhere or system reported messages. It is weird the effect this has on the quick launch items and the "Access denied" errors when trying to launch things like task manager or the start menu. So far it would seem it obviously has something to do with the PC processing hundreds of Handbrake jobs before reporting this error forcing me to reboot the PC as that's really all I've been doing. I've just never seen something like this before where I can't seem to find what resource the system is claiming to be running out of.
 

chubbyfatazn

Golden Member
Oct 14, 2006
1,617
35
91
I'm with VirtualLarry on this one.

I leave my computer on for days on end as well (the Intel one in my sig) and after a few days Explorer will crash and then I get the out-of-resources popup. I usually wrap up what I'm doing and restart at that point.
 

Maverickbcp

Member
Nov 7, 2013
145
0
76
I'm with VirtualLarry on this one.

I leave my computer on for days on end as well (the Intel one in my sig) and after a few days Explorer will crash and then I get the out-of-resources popup. I usually wrap up what I'm doing and restart at that point.

That definitely makes sense but before I upgraded to this new system I was running the same OS on a i7 920, Evga x58 mb, 6 gb's ram, same hd, etc and left the PC on for months without ever getting this error. I think it has to do with the hundreds of handbrake jobs as that's the only change in my system/daily activities that's changed that would make sense as the hardware change doesn't.
 

Fardringle

Diamond Member
Oct 23, 2000
9,197
763
126
Have you tried removing and reinstalling Handbrake? It sounds like the program isn't releasing resources when it finishes an encoding job, so your "hundreds of jobs" are using up all available resources.
 

Maverickbcp

Member
Nov 7, 2013
145
0
76
I haven't yet but I can. The thing I'm wondering is what resources is it retaining? I've looked everywhere but can't seem to locate it. The usual resources a program takes up(ram, cpu, hd) all show plenty remaining whenever this issue occurs. I expected to open task manager to see it using up all my ram, throttling my cpu, or possibly I slipped up and let it fill my HD but none have been the case. I can try and just leave the PC on for a week without doing any handbrake jobs to see if the error appears anyways but I'll save that till the end of my Handbrake jobs. I will have it encoding files non-stop for the next couple weeks at least. Then begins ripping thousands of DVD/Blu-ray/HD-DVD to .mp4. Yay me...lol.
 

VirtualLarry

No Lifer
Aug 25, 2001
56,552
10,171
126
I haven't yet but I can. The thing I'm wondering is what resources is it retaining? I've looked everywhere but can't seem to locate it. The usual resources a program takes up(ram, cpu, hd) all show plenty remaining whenever this issue occurs.

I already explained what Resources mean. They don't mean "resources" (CPU/disk/RAM), they specifically mean (Windows) Resources, which are basically little imaginary bit of information in Windows, which are limited in number, and have NOTHING to do with CPU/disk/RAM.

Look up a book on the Windows architecture and GDI for more info.
 

Maverickbcp

Member
Nov 7, 2013
145
0
76
I already explained what Resources mean. They don't mean "resources" (CPU/disk/RAM), they specifically mean (Windows) Resources, which are basically little imaginary bit of information in Windows, which are limited in number, and have NOTHING to do with CPU/disk/RAM.

Look up a book on the Windows architecture and GDI for more info.

Yes and I already said I perfectly understand what it is you're saying but I inquired as to whether or not there was any way to monitor them? I've been looking to see if there's a way to tell if they're filling up. I know it's not referring to cpu/ram/hd as they're not being filled up.

Also resources can mean cpu/disk/ram. My team and I troubleshoot various error reports every day from various applications as well as Windows and constantly receive resource error reports pointing to cpu/ram/hd/pagefile/etc. Not necessarily saying that's what this error is referring to but the term "resource" is ambiguous and doesn't always necessarily specify which "resource" it's referring to.

Thank you anyways for your assistance. This isn't the first time I've done such tasks on my PC and never once ran into an issue such as this so I will broaden my research. As I said before I'm almost certain it's going to be tied to Handbrake specifically as I've done similar tasks with different applications without an issue such as this. Possibly Handbrake not releasing the resources after each job as it's supposed to or something. I'll figure it out.
 
Last edited:

Steltek

Diamond Member
Mar 29, 2001
3,222
991
136
Nirsoft has a GDI handle monitor program here and a heap memory view utility here which can be used to trace object and memory leaks (either may flag with antivirus as being infected due to the toolkit used to create them, but both are in fact legitimate applications). You can also get the number of GDI handles by each process in task manager. Launch Task Manager. Click the Processes tab. Hit the View menu, the choose 'Select Columns'. Go down the menu and put a check in next to the 'User Objects' and 'GDI Objects' options. You may have to resize the column display in task manager to be able to see the totals as displayed by each process.

Don't know if it will help, but here are a few older articles on User and GDI objects by Mark Russinovich:

Pushing the Limits of Windows: USER and GDI Objects - Part 1, Part 2
 

Maverickbcp

Member
Nov 7, 2013
145
0
76
Nirsoft has a GDI handle monitor program here and a heap memory view utility here which can be used to trace object and memory leaks (either may flag with antivirus as being infected due to the toolkit used to create them, but both are in fact legitimate applications). You can also get the number of GDI handles by each process in task manager. Launch Task Manager. Click the Processes tab. Hit the View menu, the choose 'Select Columns'. Go down the menu and put a check in next to the 'User Objects' and 'GDI Objects' options. You may have to resize the column display in task manager to be able to see the totals as displayed by each process.

Don't know if it will help, but here are a few older articles on User and GDI objects by Mark Russinovich:

Pushing the Limits of Windows: USER and GDI Objects - Part 1, Part 2

That sounds like what I could be looking for thank you. During the week I'm pretty tied up at work so am unable to do much researching into this. Those may save me a good deal of time.
 

Steltek

Diamond Member
Mar 29, 2001
3,222
991
136
Any time.

I suspect, like VirtualLarry and Fardringle, that it will turn out that Handbrake is simply choking on the volume of what you are throwing at it due to coding and/or design issues.

Being a cross-platform application, it runs on Windows but I'm sure (like many cross platform applications I've used) it simply isn't optimized for Windows and no serious effort was made by the coders to do anything else but ensure it works as advertised. At least, as you've found, until you throw hundreds of consecutive jobs at it and it suffers a meltdown.
 

Maverickbcp

Member
Nov 7, 2013
145
0
76
Any time.

I suspect, like VirtualLarry and Fardringle, that it will turn out that Handbrake is simply choking on the volume of what you are throwing at it due to coding and/or design issues.

Being a cross-platform application, it runs on Windows but I'm sure (like many cross platform applications I've used) it simply isn't optimized for Windows and no serious effort was made by the coders to do anything else but ensure it works as advertised. At least, as you've found, until you throw hundreds of consecutive jobs at it and it suffers a meltdown.

Ya it probably just isn't releasing the resources after each job.