Jump to content











Photo
- - - - -

Multiple volumes created on startup

imdisk memory problems

  • Please log in to reply
3 replies to this topic

#1 WonkyPenguin

WonkyPenguin
  • Members
  • 2 posts
  •  
    United Kingdom

Posted 03 March 2016 - 11:21 AM

(ImDisk 2.0.5/2.0.9 Windows 7 64-bit w/ 32Gb RAM)

 

I've been happily using ImDisk for a couple of years, but in the last couple of weeks I've been hitting out of memory errors when I've not had much running.  Immediately after a reboot, my "system" process was running with ~31Gb committed (despite only having a ~15Mb working set).

 

I use one 2Gb volume mounted to "E:".  Upon investigation, the ImDisk control panel app shows that ImDisk had allocated 14/15 2Gb volumes, of which one was mapped to a letter.  When I remove these, the committed memory goes down, but the volumes re-appear every time I reboot.  I uninstalled ImDisk and then reinstalled (originally 2.0.5, and again with 2.0.9), but it is still happening so I've had to remove it again.

 

Anyone else encountered this issue and/or have any idea how to resolve it?

 

Thanks in advance!

 

:dubbio:



#2 Olof Lagerkvist

Olof Lagerkvist

    Gold Member

  • Developer
  • 1339 posts
  • Location:Borås, Sweden
  •  
    Sweden

Posted 03 March 2016 - 12:46 PM

What method did you use to auto-create the ImDisk drive at system startup? Could there be something duplicated there?



#3 WonkyPenguin

WonkyPenguin
  • Members
  • 2 posts
  •  
    United Kingdom

Posted 03 March 2016 - 02:23 PM

Hi Olof, thanks for the reply.

 

It was created by the task scheduler at system startup (as per the FAQ @ http://reboot.pro/to...s-and-how-tos/)

 

imdisk -a -t vm -p  "/fs:ntfs /q /y" -m E: -s 2G

 

 

Doubt it's related, but one thing had noticed (quite a while ago) when I moved to Windows 7 (previously XP) was that the auto-formatting stopped working.  I'd always put that down to a Windows 7 quirk.



#4 Olof Lagerkvist

Olof Lagerkvist

    Gold Member

  • Developer
  • 1339 posts
  • Location:Borås, Sweden
  •  
    Sweden

Posted 03 March 2016 - 04:56 PM

Does this task run at system startup only, or could there be multiple triggers defined for this task? Or could there be more than one scheduled task? Have you by any chance tried the -P (capital P) switch to save settings and thereby got both registry settings and scheduled tasks defined? No scripts in startup folder/group policy settings or similar?

 

Just a few possible scenarios I could imagine, I'm not sure how else this could happen.







Also tagged with one or more of these keywords: imdisk, memory, problems

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users