Posted 02 November 2010 - 09:32 AM
I have reports of VirtualBox crashes in Library\Logs\CrashReporter & Library\Logs\DiagnosticReports. I only know about them because I was reading and those logs were mentioned so I looked in the folders. There's been no noticeable problem using my programs in the VM. When I found the folders the last crash was days ago but there was another one yesterday. I have no idea how to troubleshoot the problem. Do I need to do anything? PaperPort and Word used to crash all the time on winxp despite [or because] of updating the os & both programs. The logs all list an EXC_BAD_ADDRESS & KERN-INVALID_ADDRESS [at different addresses each log]. There is a new version of virtualbox out, but I really don't want to have to reinstall right now unless letting virtualbox generate a crash report is a bad thing.
The mac also had a panic attack when I shut down last night. I got a message to power off via the power button and restart. I think the problem is the firewire hardware on my external hdd. It was giving me problems on the pc but I was suspecting the tablet's firewire pc card because the MyBook seemed to do ok w/ the mac. It's mostly formatted ntfs so I can just read from it to the mac. I write to it a lot from the pc. Maybe that's why I noticed problems w/ the pc and not w/ the mac.
The first line of the report said
"panic(cpu 0 caller 0x95169a1d): "ntfs_buf_iodone(): ni != vol->mft_ni\n"@/SourceCache/ntfs/ntfs-65.2/kext/ntfs_vnops.c:242"
The ntfs in there is what made me suspect the MyBook and further down the "backtrace" com.apple.iokit.firewire etc's are listed. It may be the drive itself has problems. The MyBook seemed to do OK using its usb connection on the pc, but the problem was intermittent, so I can't be sure.
The second line said there were 4 potential args on stack, whatever args are. Googling didn't help re "args" but I learned more about panic attacks.
"Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)"
I need to backup up the MyBook to dvd using the mac and I was going to try using its usb connection. If it is the drive itself that is the problem, the worst that will happen is a panic that is solved by rebooting w/out the ext hdd attached, correct? A bad ext hdd can't corrupt the mac os, can it?
mac 10.6 on macbook pro
WinXP sp2 on Dell 380 w/ 512 MB RAM- currently dead in the water
WinXP tab ed sp 3 on Thinkpad X41 w/ 1.5 GB RAM - lemony flavored
Win2K Sp4 on Sony VAIO GXR600 w/ 512 MB RAM - currently blue screening