- #SOUNDFLOWER FOR WINDOWS REW FULL#
- #SOUNDFLOWER FOR WINDOWS REW SOFTWARE#
- #SOUNDFLOWER FOR WINDOWS REW ZIP#
- #SOUNDFLOWER FOR WINDOWS REW FREE#
- #SOUNDFLOWER FOR WINDOWS REW MAC#
It's actually *not* a migrated setup from an older machine.I just noticed that - I must've accidentally chosen VHD for some reason. I don't mind uninstalling it for this though.
#SOUNDFLOWER FOR WINDOWS REW SOFTWARE#
I do know I have a firewall, but I don't believe it stops software from calling *out*. I actually need SoundFlower to do my online recordings (I don't use a physical amp, so I need a way to route the sound from Logic to my online recording app), but I could uninstall it for the time being - I won't be recording until these CCNA classes are over in May. Bryan Attachments VBOX_Windows 10 (22.53 KiB) Downloaded 402 times fs_usage_-204219_ (12.38 KiB) Downloaded 398 times Buayaguy Posts: 10 Joined: 10. Thanks for your reply, very much appreciated.
#SOUNDFLOWER FOR WINDOWS REW ZIP#
If there are any log files there that you think may be helpful, please let me know and I'll be happy to zip them and put them in an attachment.Ĭode: Select all Expand view Collapse view iKho:DiagnosticReports root# ls -al | grep "$(date 1 _analyticsd _analyticsusers 996 Feb 2 18:00 1 root _analyticsusers 3693 Feb 2 20:28 1 root _analyticsusers 3010 Feb 2 20:22 1 root _analyticsusers 134995 Feb 2 20:44 1 root _analyticsusers 19343 Feb 2 16:28 1 root _analyticsusers 24972 Feb 2 16:29 1 root _analyticsusers 2445 Feb 2 20:23 trustd_-202300_mory_resource.diag Here is a list of the files in /Library/Logs/DiagnosticReports that were written between when I left and got back home today (there aren't many.) The second file I attached is that first vbox logfile you wanted. Notice the time stamp is 20:42 - that's when I actually ran sysdiagnose, not when the crash happened (I still don't know exactly when that happened.) I looked online and it suggested running sysdiagnose to find the most recent crash, which I ran, and it gave me this first logfile: It said to look in /Library/Logs/DiagnosticReports, but I didn't see anything that obviously said "crash" or "freeze" or even "panic". When I got home about 5 hours later (20:20), the computer was rebooted, waiting for me to login.
#SOUNDFLOWER FOR WINDOWS REW FULL#
Surprisingly, the VM stayed working well for the entire 15 minutes I was using it, but then I was leaving for class around 3:30pm (15:30), and I left it running full screen. Bryan Attachments Screen Shot at 1.54.14 PM copy.jpg (100.43 KiB) Viewed 6694 times Buayaguy Posts: 10 Joined: 10. I'll try to get a recent crash report when it happens again. Is there any known issue for this, or better yet, any kind of fix or at least workaround? When it locks up, the mouse freezes and the system reboots within a couple of seconds. So the problem is that it just locks up the machine randomly - it usually never goes much past.30-40 minutes, unless I have it minimized, but if I'm actively using it, it tends to lock up within 10-15 minutes at the latest, and recently it locked within the first couple of minutes I had it open.
#SOUNDFLOWER FOR WINDOWS REW MAC#
I'm running it in fullscreen mode, because I need the screen space (running Cisco Packet Tracer, since they don't offer a native Mac version, and don't want to constantly reboot into a bootcamp-type situation.) I'm also running the latest version of Virtualbox with extension pack: 5.2.6 r120293
#SOUNDFLOWER FOR WINDOWS REW FREE#
I typically still have at least 10-12 gigs free while the VM is running. I have the VM settings attached, but basically there shouldn't be an issue with over-provisioning. My machine is a year old iMac, 4Ghz i7 (8 processor cores), 32 gigs of RAM, AMD Radeon 2 GB video card, running High Sierra. I've been looking through the forums seeing if I could find an answer to this, but pretty much everything I found related to computer crashing or freezing up was related to the user over-provisioning the guest OS.