Boxee on x64

I'm getting build errors trying to compile AUR boxee source on x64. The common-all-garden -fPIC variety, but I can't track them down...
/usr/bin/ccache gcc -o ../../../../system/players/dvdplayer/avutil-50-x86_64-linux.so -shared -fPIC -rdynamic --soname,../../../../system/players/dvdplayer/avutil-50-x86_64-linux.so ffmpeg/libavutil/*.o \
`cat ../../DllLoader/exports/wrapper.def` ../../DllLoader/exports/wrapper.o
/usr/bin/ccache gcc -o ../../../../system/players/dvdplayer/avcodec-52-x86_64-linux.so -shared -fPIC -rdynamic --soname,../../../../system/players/dvdplayer/avcodec-52-x86_64-linux.so ffmpeg/libavcodec/*.o \
ffmpeg/libavcodec/x86/*.o `cat ../../DllLoader/exports/wrapper.def` ../../DllLoader/exports/wrapper.o
/usr/bin/ld: ffmpeg/libavcodec/x86/fft_mmx.o: relocation R_X86_64_PC32 against symbol `ff_cos_16' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: ld returned 1 exit status
make[1]: *** [../../../../system/players/dvdplayer/avcodec-52-x86_64-linux.so] Error 1
make[1]: Leaving directory `/tmp/yaourt-tmp-root/aur-boxee-source/boxee-source/src/src/boxee-sources-0.9.20.10711/xbmc/cores/dvdplayer/Codecs'
make: *** [dvdpcodecs] Error
Has anyone come across the same issue? Does anyone have a precompiled 64 bit Boxee package? I'd be happy to provide hosting for a repo if someone else is successful in compiling the package!

I had the same error -- do you have Yasm installed? I was able to compile boxee-source successfully once I removed it. I assume it may just need the right flags or an alignment patch to fft_mmx.asm and/or others, but I was annoyed enough by the time I succeeded without yasm that I didn't dig any further.

Similar Messages

X201 Tablet: Drivers not working for Network controller on Windows 7 Pro x64

Hello,
After downloading and installing all LAN and WLAN drivers for X201 Tablet, I couldn't find one that works on Windows 7 x64.
How can I proceed?
Thank you in advance
Solved!
Go to Solution.

I fixed it by downloading this drivers:
https://downloadcenter.intel.com/download/18713/Network-Adapter-Driver-for-Windows-7-
And after installing them and restarting, searching for them manually from the Device Manager.
Cheers

Error while installing SQL Server 2012 X64 SP2,

Error while installing SQL Server 2012 X64 SP2,
When I installed the SQL Server 2012 X64 SP1, I got the attached error.
What might be the issue here?
Thank you
Best
Jamal

Hello,
Are you trying to install SQL Server on a compressed or encrypted drive? SQL Server won’t install on a drive/folder with these attributes.
Are you trying to install SQL Server on a ReFS file system? It is not supported on SQL Server 2012.
Disable any security/antivirus software and download the media again. Mount the media (.ISO file) and try to install again.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Error while deploying web role - Invalid application runtime - a runtime component is missing:/base/x64/IISConfigurator.exe

I have Azure SDK 2.5 installed and when I try and publish my web role from VS 2013, it fails. When I manually upload the package and config through the Azure Portal I get the error: "Invalid application runtime - a runtime component
is missing:/base/x64/IISConfigurator.exe".
I have tried uninstalling and re-installing the Azure SDK with no change in the error.
Any ideas how I can troubleshoot this?

I uninstalled the SDK, and tried to create a new cloud servce using the WCF service project template. The new project still gives me the same error:
The file provided is not a valid service package. Detailed error code: WCFServiceWebRole1 Invalid application runtime - a runtime component is missing:/base/x64/IISConfigurator.exe.

IPhone 3gs will no longer sync to iTunes on Windows 7 x64

My iPhone 3gs worked fine up until the last 2 updates. Ever since then, the iphone is not even recognized by iTunes. When I go under "devices" in the advanced settings I can see the backup for my phone. Why can't it recognize a phone that it's already recognized? I installed the latest 10.4 and still it's not recognized. I know the computer sees it as it's listed as "started" and "automatic" under services in the admin tools. I've pretty much tried every work around I can think of or seen online and nothing has worked at all. Really have no idea what to do next.
If anyone has any idea how to resolve this issue, I would greatly appreciate it! My setup is below:
Windows 7 pro x64
iTunes 10.4
iphone 3gs
Thanks in advance for any assistance!

Ok! So I just came across this randomly in another thread from user Kempas (thanks a lot!). It totally fixed the problem so I thought I'd repost it!
https://discussions.apple.com/message/10644045#10644045
Ok, I'm assuming everyone who is having trouble with Windows 7 (64-bit? mine is) has tried the following solution I found over at en.kioskea.net posted by a guy called Steve78545 (hey, you got to give a dude his due).
It's maybe because Windows 7 uses a MTP driver instead of the USBAAPL by default, and what you need is an 'Apple Mobile Device USB Driver' which you might not have in 'Universal Serial Bus Controllers' (check it and see). If you haven't got it, as good ol' Steve78545 suggested:
Update the driver by expanding 'Portable Devices' from the list, right click Apple iPhone/iPhone and select 'Update Driver Software'. Then select 'Browse My computer...'
Copy the following path and paste it in - C:\Program Files\Common Files\Apple\Mobile Device Support\Drivers - then hit 'Next'.
Let the thing do it's...thing an it should work. At least it did for me, so I hope it helps a few people out!
K

IPod and Windows Vista beta 2 X64

Hi..
I've just installed the vista beta X64.. and iTunes don't work with it..
here's the solution:
Buy Anapod explorer..
First download the latest update (now 28-06-06)..
install it..
then install anapod..
Then it's working..

As I recall, it will not install in the current version of Parallels. There are some changes that need to be made to the bios code that Parallels uses. The company posted on its forums at one point that this ability will come in the next release.
Check this link for more information:
http://forums.parallels.com/showthread.php?t=2689&highlight=vista
If this message is helpful or solves your problem, please be sure to hit the helpful or solved buttons at the top of this response.

Windows 7 x64 can't read/install any printer drivers from Windows Server 2003 x64 (AMD64 folder and HP Deskjet 855c)

I read the thread Widows 7 printer
HP deskjet 855c driver about possible installation of HP855c drivers onto Windows 7 x64 from "Windows Server 2003 x64" CD but I didn't have enough luck to succeed with doing it on my laptop. That thread appears to be dead now
as it is marked "Answered", so I'm asking for help here. I have Toshiba Satellite P500 with Windows 7 Home Premium 64-bit (http://i55.tinypic.com/2zgth6v.jpg).
Let me tell you first that I don't have access to Windows Server 2003 x64 or XP Pro 64 CD's. However I did some research online, which eventually forced me to learn about the "file sharing". After extensive search I was able to get the copies
of AMD64 folders from Windows Server 2003 R2 Standard x64 with SP2 and
XP Pro 64. The reason that I went also after XP Pro was because I thought that the extra wording "R2 Standard x64 with SP2" in description of "Windows Server 2003" did not reflect the exact name provided by poster
Alan. I couldn't find just "Windows Server 2003 x64" (does it matter?).
Anyway, I followed first the drill with running "printui /s /t2" and disabling UAC, and then in both cases I was able to locate the
NTPRINT.INF file (http://oi51.tinypic.com/9qwvt2.jpg - this image is from XP Pro AMD64 folder) but each time when I
attempted to install the driver, I got the same message stating:
"The folder you specified doesn't contain a compatible software drive for your device. If the folder contains the driver, make sure it's designed to work with Windows for x64-based systems." (http://oi53.tinypic.com/27yveiw.jpg)
Why aren't there x64 drivers?
During several installation attempts I had the printer connected to or disconnected from my laptop. It didn't make any difference. I must add that for this purpose I had to use different cable than the original one designated only for the
Parallel port in my old desktop with Windows XP. My new laptop with Windows 7 x64 came only with 3 USB ports (plus 1 HDMI and 1 Serial). Because of that situation I bought in advance a new printer cable called “USB to 36-pin Parallel Port Adapter
Cable” (http://www.amazon.com/gp/product/B003A8I75E). I'm not sure, if it will work until I can install the printer.
Besides, nobody talked about this issue yet. I was also playing with the port choices in "Add printer" step; changing from default LPT1 to USB001 with the same negative results.
I don't know what I'm doing wrong. I was very hopeful after reading positive "case closed" notes there.
Can anyone help me here, maybe by making the necessary files available for download? I'm willing to pay for such assistance or make a donation, if necessary. Seriously. Judging by the large number of views of the original
thread, one could assume that there is a potential demand for such service. It would be more human to pay few bucks for a few driver files than $900 for the whole Windows Server 2003 x64 CD, no? Can Microsoft accomodate me/us, please? :)
Andrew*
P.S. I was advised to come for help here from
http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/windows-7-x64-cant-readinstall-any-printer-drivers/4e7d06e1-33a5-4597-be70-4fdc087a63a7?msgId=9a045994-0d31-4d40-b17d-dba372393ee4

I have my HP 855c/driver working on Win 7 Ultimate x64. I used the 'printui /s' procedure and 4 files described above with some minor changes.
I pulled WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU.exe down from the Microsoft website. Running the file causes the exe to unpack into a temp folder at the root drive. A 'Setup Error' message box is displayed once the file is run. I left this
message box up until I copied ntprint.inf, ntprint.cat, and sp2.cab from the temp folder.
I copied driver.cab from a Windows XP Pro disc. I also needed amd64\stdnames.gpd which was already in my Windows 7 c:\windows\system32\spool\drivers\x64\3 folder.
I created a folder with the 5 files (ntprint.inf, ntprint.cat, sp2.cab, driver.cab, and amd64\stdnames.gpd). This is my 'Have Disc' folder.
I followed the 'printui /s' instructions, first changing the permissions mentioned above and then installing the driver. Next I followed the instructions to add a printer from Control Panel 'Devices and Printers' - 'Add Printer', choosing to 'use an existing
driver' when installing the HP 855c.
I used a slightly different ntprint.inf, size 1570418. The readable contents of ntprint.inf is as follows. Notice the line 'CatalogFile=ntprint.cat' is not included. I tried using the 1570468 version of ntprint.inf; when I did I received an incompatibility
message (probably the same one mentioned above).
; NTPRINT.INF (for Windows Server 2003 family)
; List of supported printers, manufacturers
[Version]
Signature="$Windows NT$"
Provider=%MS%
; LayoutFile=layout.inf
ClassGUID={4D36E979-E325-11CE-BFC1-08002BE10318}
Class=Printer
DriverVer=10/01/2002,5.2.3790.4533
[ClassInstall32.NT]
AddReg=printer_class_addreg
[printer_class_addreg]
HKR,,,,%PrinterClassName%
HKR,,Icon,,"-4"
HKR,,Installer32,,"ntprint.dll,ClassInstall32"
HKR,,NoDisplayClass,,1
HKR,,EnumPropPages32,,"printui.dll,PrinterPropPageProvider"
Good luck

Windows 7 x64 on 2009 MB, step-by-step instructions and solutions

ok, after spending days on this with about 10+ clean installs on 2 different machines and searching forums about various problems, i'm going to go step by step in a flow-chart like manner to describe the steps and various pitfalls in getting windows 7 ultimate 64 bit installed correctly on a macbook (late 2009)...most of this i didn't figure out on my own, this is a compilation of solutions found by others. i'll try and link or credit anyone i can, but honestly can't remember where i saw all of this. part of this is to share my days of frustration to try and save someone some time. also, in case i have to do this again, i want a record of it so i don't have to start from scratch next time.
i don't have everything working perfectly, but i have wireless and sound, but not sure if all the drivers are up to date. i'm still working on the headphone issue, i don't have sound yet with headphones, but i got the speakers to work.
i'm going to preface this by saying that windows 7 is a horrible piece of software, i'm only helping a friend do it because she's an architect and needs autocad, but she wants a mac for daily use. also, i'm doing this from a spanish install of windows 7 (here in south america), so it's a pain to translate this cruddy convoluted OS into english as i'm not familiar with windows 7 anyway, so i'll do my best. i'm not a pc expert. also going to say that the windows 7 x86 and x64 installs i've done on a couple macbook pro 15's seems to work much better (full trackpad functionality, expose works) and without as many problems...i don't know why it doesn't seem to work as well in x64 on the macbook, i'm still investigating.
also, i want to say that a fresh (first-time) bootcamp partition with windows install after a clean mac os x install seems to produce the best results. i say this because i wasn't happy with all the hacks in my first couple attemtps, so i erased the bootcamp partitions and re-created them to re-install windows 7 again. but i started experiencing some peculiarities that never happened in the first install after a clean Mac OS X install. it's as if the computer leaves artifacts from previous installs and acts funny. also, reboots and start-up times seem to be slower now than when it was a first-time fresh install. anyway, i'll try and outline all the weirdness here, indicated by asterisks *
SO, HERE GOES:
1) Go to Bootcamp Utility > Create Bootcamp partition
2) Afterwards, this should take you to a restart into the windows install dvd....if install dvd boots fine, skip to step 3
** if you get a gray screen (happened to me after subsequent re-install attempts), you have to power off and reboot holding down "C" key to boot from the dvd...or you can hold down alt/opt key to get the icons of bootable volumes, at this point it should be mac os x and the windows dvd. the point is, force it to boot from the dvd if it hangs on re-start.
3) Windows install should start. Select language, etc....You should then get to a screen listing all the partitions (should be 3 of them). Choose the Bootcamp partition and format (erase) it to proceed with the install.
4) Windows should start installing all the files and will reboot a couple times, here's where things get weird possibly. On the first attempt at installing Windows 7, the install went smoothly on restart.
** some of you might get a blinking cursor and a black screen that goes on forever. Supposedly this is a bug in Windows 7, having to do with video drivers or something. I don't understand because my first install attempt, it rebooted just fine and the installation continued.
anyway, what you have to do here if you get the forever-black screen is power down the machine with the power button and restart holding the alt/option key. this time when you get the bootable volumes on the gray screen, choose the Windows partition, which will now appear. DON'T boot up from the DVD. upon restart into Windows, you should be back in the installation process and it will attempt to finish the install here.
it might be my imagination, but once i had to reboot into the dvd here to actually finish the install. technically Windows is not finished installing at this step, you just have to figure out how to get past the black screen to finish the install. try both.
5) Windows should go back to where it left off before the restart, then finish the install.....and restart AGAIN. On my first attempt, the restart went smoothly and started the "first time user" process...
** some of you will get the black screen YET AGAIN, this happened to me on my subsequent attempts at re-installing Windows. again, you need to power off and start up holding the alt/option key, choose the Windows partition and it should take you to the "first time user configuration" process....since at this point, windows is indeed installed.
6) Here you will fill out all your information, product key, etc...and get into Windows. Here you will have some other problems.
Problem #1: you have no drivers to run Windows on your Mac, so you will need to install Bootcamp in windows from your Mac OS X install dvd
Problem #2: you have no "right click", because you don't have drivers, so you might not be able to eject the Windows dvd to put in the Mac dvd
Solutions: you can't control-click or right click, BUT YOU CAN hover over the DVD drive ( "D:" in your computer, my PC or whatever it's called in english) and see if there's an "eject disc" option.
for some reason, my Windows dvd was spinning and not being recognized, so i just rebooted (alt/option) into Mac OS X and ejected the disc there. the point is, you need to eject the Windows disc and put in the Mac OS X install disc to access Bootcamp for Windows.
7) Reboot into Windows (if you had to boot into Mac to eject the disc). Insert Mac OS X install disc. Navigate to BootCamp setup.exe and run it.
** the first time i did this, it ran no problem. but in subsequent attempts, it gave me the "x64 not supported by this computer" message that everyone seems to encounter. there is a bypass for this outlined here:
http://www.techulous.com/hardware/how-to-apple-boot-camp-64-bit-for-windows-7-on -unsupported-macs.html
8) Ok, so now you should have Bootcamp 3.0 installed. Now you need to update it with Bootcamp 3.1 update. Download it here and run it. This is required for 64 bit support, I believe this is the link:
http://support.apple.com/kb/dl979
** hopefully you don't have problems, i didn't, so you might have to search the forums since i can't anticipate what might happen here, it worked for me every time.
9) Ok, i think it might reboot after the update install. Now you have Bootcamp installed and most of the drivers you need, however not everything works. Some of the drivers will be out of date.
Problem #1: you may or may not have updated nvidia drivers. mine are ok, but check nvidia website if you have doubts. most of their drivers are for PC hardware, however, so the ones on the bootcamp disk and update should be fine.
Problem #2: almost everyone has wi-fi connectivity problems. it has to do with the wrong/outdated broadcom drivers from bootcamp. i will outline how i got it to work (based on someone else's solution i found in some forum or other).
Problem #3: almost everyone is having sound issues. i'll explain what i did. i still have no sound coming out of the headphone jack, i'm working on that next. but i have speaker sound and no red light coming out of the headphone jack.
** first of all, you should probably download firefox from internet explorer in windows, then update adobe flash, it's a pain....i used another computer to download the drivers, then transfered them by USB drive, but you can do it however u want.
Solution to wi-fi: ok, not sure where i got this information, but i downloaded HP drivers in a file called "sp45524.exe"....here's the link:
http://www.wireless-driver.com/download/hp/hp-broadcom-wireless-lan-windows7-dri ver-v560188.htm
apparently the broadcom drivers in Bootcamp 3.0 and 3.1 update won't install on Windows 7 x64 for some reason, lot of people are getting "code 10".
what i did is this:
9a) run the .exe file, it will create a folder called SWSetup\SP45524 that will house the drivers. there's a setup file in that folder, i didn't try it. perhaps it will install from there, but everything i read suggested a different step. ** if you run the set up file, you may have to run as administrator, or use the "troubleshoot compatibility" trick to get it to work.
9b) Go to Control Panel > Hardware and Sound > Device Manager > Network adapters
you should uninstall or deactivate any drivers you have. if it's not showing any wi-fi adapter, right click and "check for new hardware" (not sure how it's translated into english from spanish)....you should have an unknown device pop up with the yellow icon and exclamation mark. double click on that, assign it as a network adapter.
when you get to the driver tabs, you can install it from there. this is where it gets tricky. click "install driver", "check drivers on this computer", "choose from a list of drivers on this computer", "use disc", and in the dialogue box ("install from disc" that says "copy manufacturers files from", navigate to the C: SWSetup|SP45524 folder and click until you can accept. this will load up a different list of drivers.
(sorry, i'm translating the Windows from spanish to english, and i'm not familiar with exactly what they say in english, so you'll just have to use your imagination)
you should now have a small list of drivers. personally, i chose the first one on the list "Wi-Fi adapter Broadcom 43224AG 802.11a/b/g/draft-n", but the second one worked also. again, i'm doing this on a late 2009 white macbook (6.1) and it works. according to the date of the driver, it seems like it might not even be the most current and might be older than the one that's on the MAC OS X install disc, but none of the ones on the disc work. this one does. (thanks to whoever found this out, i can't find the original link of the post with this driver reference).
Solutions to sound: ok, there are multiple posts on this, everything from updating realtek to sigmatel...personally what worked for me was to download the most current Cirrus Logic drivers.
everyone has been pointing to this post:
http://www.stuffedcow.net/macbook_audio
it doesn't really tell you what to do exactly. i'm not even sure what to do, but here's what i did. actually, i downloaded what was supposed to be the CS4207 driver here:
http://www.cirrus.com/en/products/pro/detail/P1233.html
then i followed the same procedure as before with the network adapter driver...."install driver", "check drivers on this computer", "choose from a list of drivers on this computer", "use disc", and in the dialogue box ("install from disc" that says "copy manufacturers files from", navigate to the folder you just downloaded from the above link.
you should have an updated list of drivers. what i don't understand is that the Cirrus site lists the most current driver as CS4207, but the only thing that has 4207 in it starts with CDB. in any case, i chose the last one on the list, CS4206A (AB 99).
i have no idea why i chose that, it just seemed to be the most current. in any case, sound works now.
Ok, i tested all this stuff in skype. wifi, microphone and speakers work, isight works. however, still no headphone sound. so if anyone knows how to fix that, please let me know. i haven't gotten to that part yet. but i've spent like over a week trying to figure this out. windows 7 is so horrible that there seems to be so many steps to getting it just right, and i just found myself starting all over (i didn't mention the nightmare with license breaks with AutoCad due to windows reading the clock differently...that's another hack that i had to deal with...and failure meant re-installing everything).
ok, off to bed now....

Windows 7 x64 all updates
Just doublechecking. Does that include the recent chkdsk hotfixes?
[The Chkdsk.exe program does not start correctly on a Windows 7-based computer|http://support.microsoft.com/kb/975778]

How to install win 8.1 pro x64 on MBA mid 2013 (core i7)

Please help me how to install win 8.1 pro x64 on MBA mid 2013 (core i7).
Thank you very much for your help.
Best regards.

Everything you need to help you is located here: http://www.apple.com/support/bootcamp/

Error trying to install Win 8.1 x64 Enterprise

Brand new iMac 27", fully loaded, 1 TB SSD, 32 GB RAM, running Mavericks 10.9.3. Trying to install Win 8.1 x64 Enterprise (from MSDN).
Downloaded the ISO file and license and used Boot Camp to install the files and Apple Support files to a 16 GB USB 3.0 thumbdrive.
Used Boot Camp to repartition the 1 TB SSD to set a Windows partion of 256 GB, then the computer rebooted into Windows Setup.
Came to the drives listing, selected the BOOTCAMP parition (Drive 0, Partition 4, 239 GB) and formated it, then clicked on NEXT.
Thought for a while, then it came up with this error message: "We couldn't install Windows in the location you chose. Please check your media drive. Here's more info about what happened: 0x80300002"
Got some hits on Google about issues with VISTA, or with Intel processors, but, nothing specific.
Checked USB thumb drive with Norton, no issues, CHKDSK, no issues.
Have repeated the entire process twice, including restoring the patition and recreating it, and rebuilding the USB Thumbdrive.
Any ideas on what to do?
Thanks!

More sadness. I finally started getting the BSOD as soon as Windows booted, and, I could not restart or shutdown the computer...had to power off. That, after a few times, corrupted my BootCamp partition. I messed around with trying to fix, but, no joy.
Redid the partition, checked all drives for errors (fixed permissions on the Mac HD...LOT of errors), and created a new partition.
Used USB 2.0 (VERY SLOW) thumbdrive and had all external drives removed, and installed Win 8.1 Pro, not Enterprise this time.
Got it back up, patched it, configured it, put Norton 360 on it (have on all my computers and iOS devices) shut down, and hooked up the external drives. Booted up and...got the BSOD.
This time I had Windows Debugger loaded, and after the BSOD could reboot, go back intoWindows, and Debug.
Culprit seems to be Norton--in particular a Norton Storage driver. Will be contacting vendor to fix.
Here's dump:
Probably caused by : SYMDS64.SYS ( SYMDS64+71be6 )
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Dump\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff802`0f87e000 PsLoadedModuleList = 0xfffff802`0fb482d0
Debug session time: Tue Jun 17 00:48:52.131 2014 (UTC - 6:00)
System Uptime: 0 days 0:03:09.864
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                        Bugcheck Analysis                                    *
Use !analyze -v to get detailed debugging information.
BugCheck 139, {3, ffffd0002852d3e0, ffffd0002852d338, 0}
*** ERROR: Module load completed but symbols could not be loaded for SYMDS64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS
Probably caused by : SYMDS64.SYS ( SYMDS64+71be6 )
Followup: MachineOwner
6: kd> !analyze -v
*                        Bugcheck Analysis                                    *
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd0002852d3e0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd0002852d338, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
Debugging Details:
TRAP_FRAME: ffffd0002852d3e0 -- (.trap 0xffffd0002852d3e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe00059c129f0 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffe0005718d2a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8020f9e8cdb rsp=ffffd0002852d570 rbp=0000000000000000
r8=0000000000005aa0 r9=00000000000007ff r10=ffffd00066cc8000
r11=ffffe00059963040 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
nt! ?? ::FNODOBFM::`string'+0x682b:
fffff802`0f9e8cdb cd29            int     29h
Resetting default scope
EXCEPTION_RECORD: ffffd0002852d338 -- (.exr 0xffffd0002852d338)
ExceptionAddress: fffff8020f9e8cdb (nt! ?? ::FNODOBFM::`string'+0x000000000000682b)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT
BUGCHECK_STR: 0x139
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
EXCEPTION_PARAMETER1: 0000000000000003
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff8020f9ddae9 to fffff8020f9d1fa0
STACK_TEXT:
ffffd000`2852d0b8 fffff802`0f9ddae9 : 00000000`00000139 00000000`00000003 ffffd000`2852d3e0 ffffd000`2852d338 : nt!KeBugCheckEx
ffffd000`2852d0c0 fffff802`0f9dde10 : ffffe000`59c8cc40 00000000`00000000 ffffe000`54b71040 fffff800`1d6d40b6 : nt!KiBugCheckDispatch+0x69
ffffd000`2852d200 fffff802`0f9dd034 : 00000000`00000000 00000000`00000000 ffff6d2d`50094127 fffff802`0f81458f : nt!KiFastFailDispatch+0xd0
ffffd000`2852d3e0 fffff802`0f9e8cdb : ffffc000`061df4e0 ffffc000`061df4e0 ffffc000`061dfbf8 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0xf4
ffffd000`2852d570 fffff800`1d7a0be6 : ffffe000`59e10120 fffff800`1d794388 ffffe000`54dfe9c8 fffff800`1d735f7c : nt! ?? ::FNODOBFM::`string'+0x682b
ffffd000`2852d5a0 fffff800`1d7a54e2 : ffffc000`061df4e0 ffffc000`061dfbf8 ffffc000`061df550 fffff800`1d7367ea : SYMDS64+0x71be6
ffffd000`2852d5d0 fffff800`1d737f20 : ffffc000`061df378 ffffc000`061dfbf8 00000000`00000000 ffffc000`05a9bf18 : SYMDS64+0x764e2
ffffd000`2852d620 fffff800`1d73e171 : ffffc000`051e6a88 ffffc000`05a9bf18 ffffc000`05a9bf18 ffffe000`5988cb00 : SYMDS64+0x8f20
ffffd000`2852d650 fffff800`1d782027 : ffffc000`061ea018 00000000`00000000 ffffe000`58409008 fffff800`1d794388 : SYMDS64+0xf171
ffffd000`2852d680 fffff800`1d79af21 : ffffc000`061ea018 ffffd000`2852d8c9 ffffe000`58409008 00000000`10000004 : SYMDS64+0x53027
ffffd000`2852d6c0 fffff800`1d9a3bb3 : ffffe000`58409078 fffff800`1d98b3e8 ffffe000`58409008 ffffd000`2852d8c9 : SYMDS64+0x6bf21
ffffd000`2852d6f0 fffff800`1d9a91fa : ffffe000`5840a1a8 ffffe000`58409008 00000000`00000000 ffffe000`00000000 : SYMEFA64+0xe9bb3
ffffd000`2852d720 fffff800`1d9ae015 : 00000000`00000000 00000000`00000000 ffffd000`2852d8c9 ffffe000`58a10e60 : SYMEFA64+0xef1fa
ffffd000`2852d760 fffff800`1d9adf4c : 00000000`01820201 ffffe000`58a10e60 ffffe000`58a10e60 ffffe000`58a10be0 : SYMEFA64+0xf4015
ffffd000`2852d790 fffff800`1d9b294c : ffffe000`59e0a150 ffffe000`58a10e60 ffffe000`5988ca80 ffffe000`58a10e60 : SYMEFA64+0xf3f4c
ffffd000`2852d7c0 fffff800`1d9a2435 : ffffd000`2852d8a0 ffffe000`599a4010 ffffd000`00000000 ffffe000`59e0a010 : SYMEFA64+0xf894c
ffffd000`2852d7f0 fffff800`1d6d528a : 00000000`00000000 ffffe000`59e0a070 ffffe000`5604e300 ffffe000`58a10e60 : SYMEFA64+0xe8435
ffffd000`2852d820 fffff800`1d71bf76 : ffffd000`2852d960 00000000`00000000 ffffe000`5604f900 ffffe000`571dab10 : fltmgr!FltpPerformPreCallbacks+0x31a
ffffd000`2852d930 fffff800`1d6d413a : ffffe000`57170dd0 ffffe000`571dabd0 ffffe000`59cf18c0 fffff802`0fd411a7 : fltmgr!FltpProcessShutdownRequest+0x122
ffffd000`2852d9b0 fffff802`0fbf7518 : ffffe000`57170dd0 00000000`00000001 ffffe000`571dabd0 fffff802`0fb54a90 : fltmgr!FltpDispatch+0x13a
ffffd000`2852da10 fffff802`0fbf7273 : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000000 : nt!IopShutdownBaseFileSystems+0xb8
ffffd000`2852da90 fffff802`0fbfb722 : fffff802`0fbfb4b0 00000000`00000000 ffffe000`59963040 ffffe000`59963040 : nt!IoShutdownSystem+0x127
ffffd000`2852db10 fffff802`0f8d1adb : fffff802`0fbfb4b0 ffffd000`2852dbd0 00000000`00000000 ffffe000`59963040 : nt!PopGracefulShutdown+0x272
ffffd000`2852db50 fffff802`0f94d794 : ffffe000`59965800 ffffe000`59963040 ffffe000`59963040 ffffe000`54b71040 : nt!ExpWorkerThread+0x293
ffffd000`2852dc00 fffff802`0f9d85c6 : ffffd000`66c40180 ffffe000`59963040 ffffe000`59965800 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`2852dc60 00000000`00000000 : ffffd000`2852e000 ffffd000`28528000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
SYMDS64+71be6
fffff800`1d7a0be6 33d2            xor     edx,edx
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: SYMDS64+71be6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SYMDS64
IMAGE_NAME: SYMDS64.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 51f84c44
FAILURE_BUCKET_ID: 0x139_3_SYMDS64+71be6
BUCKET_ID: 0x139_3_SYMDS64+71be6
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x139_3_symds64+71be6
FAILURE_ID_HASH: {bf9be68b-5f04-08d4-3152-3d420dc362f6}
Followup: MachineOwner

Will the late 2013 Mac Pro boot from an external drive (4Tb, USB 3) with a cloned Win7 x64 partition on it?

Hello all,
I ordered a CTO Mac Pro for heavy rendering and animating work, and I am planning on using bootcamp to install a windows partition (for 3DsMax). As I am now using a HP Elitebook 8770W that has several valuable files and projects on it, I have bought a Seagate 4Tb external Desktop Drive that uses USB 3.0 to use as a backup drive. Now, as I saw that Bootcamp Assistant only supports installing a x64 version of Windows 8, my question is:
Will a late 2013 Mac Pro using bootcamp assistant boot from an external USB drive with a cloned partition running x64 win7? Or do I really have to buy Windows 8 and install that to my internal SSD, and then use the migration assistant to copy over my projects?
Thanks!

Posted? or found in new builds?
BCA should really just pull whatever the latest drivers are when run.
If it is with how it partitions and sets up nMP and its partition for Windows that is another matter and makes sense.
Some people want UEFI native booting in Windows, and my experieince with that on PCs has been that it boots faster and runs well, but has different partitions that it wants. For one thing, there is now a backup "system reserved" partition, just as Apple GUID has some volume information blocks and backup and areas that were once optional (and if format erase was not able to, it would not create one) are now mandatory.
Windows 8.1 is req'd, reason a backup should be a big must - is it might overwrite and use another OS's partition table entries. Especially when doing UEFI install.
There was something about which linux OS was safe and how they would each add entries in the table, but one would not place nice. That one had to be done first or not at all.

HT3986 Hi, i have a macbook pro version 10.6.8 with boot camp version 3.0.4. I managed to install windows 7 professional x64, however when i insert my OS CD to install the drivers using the boot camp method, it says unsupported to this computer model

Hi, i have a macbook pro version 10.6.8 with boot camp version 3.0.4. I managed to install windows 7 professional x64 bits but however when i tried to install the drivers using the OSX MAC CD using boot camp, it prompt me boot camp x 64 is unsupported with this computer model. Then i tried the method by right click the bootcamp x64 and managed to install the drivers. However, i still couldnt manage access the internet and it prompts me no networking hardware detected...Any idea how can i solve it?
P.S i tried updating my bootcamp version 3.0.4 in mac os with bootcamp x64 version 3.1 exe but it shows me weird wording..
my bootcamp version in windows 7 is 2.1..

Uninstall 2.x totally
Use CCleaner Registry tool
Do whatever you need to to nuke the existing Apple programs and folders hidden here and there also.
BC 2.2 was XP and Vista only

Adobe Photoshop CS4 (x64) problem on Windows7

Hi, everyone. I have a problem with Photoshop CS4 (x64) running on Windows7 (x64). When I try to launch x64 version I get message "Adobe Photoshop CS4 has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." It was working fine before and only today it have broken. By the way, Photoshop CS4 (x86) works perfect, I can't launch only x64 version. Have you any idea how to solve this problem?
(re-installing Photoshop don't fix it)

Hi - Have you tried disabling Aero - it worked for me when it was crashing my Win 7 64 in th evanishing filter
http://www.howtogeek.com/howto/windows-vista/disable-aero-on-windows-vista/

Instalei o Windows7 x64 num computador limpo. Quando sincronizei o iPhone, perdi todos os meus contatos. Como resolver esse problema?

Tenho o iTunes versão 10.4 para windows x64. Tudo instalado corretamente e estou tendo muita dificuldade para sincronizar o iPhone4. Numa primeira vez, o programa fez um monte de atualizações e depois de terminada a "sincronização" verifiquei que tinha perdido todos os contatos gravados no iPhone!?!
Como resolver isso?
Essas dificuldades também estão acontecendo na sincronização do iPad (!!?!!)
Nada disso acontecia quando o sistema instalado era o velho Windows XP x86. Não digo bom e velho porque não é. O novo Win7 é bastante superior e melhor que o velho WinXP. O problema começou a acontecer quando instalei a versão nova do iTunes (a tal 10.4 instalada de acordo com os requisitos da Apple e feita sem nenhum problema e sem relatar nenhum erro durante nem depois da insatalação), que aliás é o único programa que está dando problema na nova instalação.
Como resolver isso?

Tenho o iTunes versão 10.4 para windows x64. Tudo instalado corretamente e estou tendo muita dificuldade para sincronizar o iPhone4. Numa primeira vez, o programa fez um monte de atualizações e depois de terminada a "sincronização" verifiquei que tinha perdido todos os contatos gravados no iPhone!?!
Como resolver isso?
Essas dificuldades também estão acontecendo na sincronização do iPad (!!?!!)
Nada disso acontecia quando o sistema instalado era o velho Windows XP x86. Não digo bom e velho porque não é. O novo Win7 é bastante superior e melhor que o velho WinXP. O problema começou a acontecer quando instalei a versão nova do iTunes (a tal 10.4 instalada de acordo com os requisitos da Apple e feita sem nenhum problema e sem relatar nenhum erro durante nem depois da insatalação), que aliás é o único programa que está dando problema na nova instalação.
Como resolver isso?

Unable to share library on Vista x64

I am running a new installation of Vista Enterprise SP1 x64 w/ iTunes 7.6.2.9. After enabling sharing, I cannot see any other libraries on the same subnet. Other's who see my library get an error when connecting: "The shared library 'my library' is not responding (-3259). Check that any firewall software running on either the shared computer or this computer has been set to allow communication on port 3689"
I get the same issues with the Vista firewall turned off. Not running any other firewalls. I have allowed iTunes on the firewall rules when prompted and have verified it is allowed.

yes. The file I installed from was itunes64setup.exe

Boxee on x64

Similar Messages

Maybe you are looking for