Nvidia 8800GTX 768Mb

Hi everyone, I am planning to order a new Mac Pro to replace my recently acquired PC (which already had a lot of nice stuff in it, such as a GC Nvidia 8800GTX Overclocked, 10,000 RPM hard drives, etc.)
I 'm wondering if I could use my own Graphic Card in this new Mac Pro.
I saw that the Mac Pro could be delivered with a 8800GT Graphic Card but mine is more demanding regarding the power supply, and I can't find any reliable information about the power delivered by the Mac.
If anyone already tried the 8800GTX on a mac or knows about the power supplied, please let me know.
thank you in advance.
MF

KEEP YOUR CURRENT HI-END PC!
The new MacPro graphics are lemons...actually the drivers are very, very poor.
Wait for next generation Intel Nehalem CPUs, in 3rdQ. The next MacPro may be worth if Apple decides to make it right, dedicating some resources to IT instead of iPhones and ICrappies.
Next generation willvery likely include a newer generation GPU w/HDMI ports (9xxx series is out now) and Blue Ray. Contrary to most people opinions and hopes Apple has kept MacPros very poorly upgradable and that is simply unethical for such hi end pro tools.
Keep your money! No worth at the moment.
I

Similar Messages

MSI Geforce 8800GTX 768mb OC Edition memory bus

In the nvidia control panel the memory bus (Factory shipped clock frequencies setting) is set to 1000 instead of 2000! Core bus is normal to 610. I also realized that if i increase the memory speed it goes only up to 1200? Remember, this is the OC Edition! Any suggestions? (Drivers installed: 162.22 vista 64bit)

Quote from: flobelix on 20-July-07, 03:32:33
Well... NO! control panel shows real clock 1000mhz, that's 2000mhz effective ( 1000mhz DoubleDataRate = 1000 x 2 = 2000!). So don't worry everything's ok.
Thanks man!

RE: GPU disabled with NVidia 8800GTX, 2 weeks and no fix yet!

Hi folks
My hard drive crashed while back...had to reinstall everything. Now, for some reason Photoshop refuses to enable OpenGL access even though before I was able to use Photoshop with my video cards. I have reinstalled the app multiple times, reset prefs many times, installed various versions of my video card drivers (including the latest from NVidia) but no luck. I checked Adobe and NVidia site and my cards are listed as supported. I talked to Alienware and they couldn't figure out the problem, I talked to NVidia and they said my cards are ok and it's Photoshop's end. I posted the problem originally and someone from Adobe said it is NVidia's problem.
Someone please help! I keep getting passed from one company to another and no one seems to know what is going on. As I said before, Photoshop CS5 was working fine with my video cards before (with GPU enabled). After I had to swap my HD's, Photoshop refuses to enable GPU access.
Here are my specs:
Alienware m17x R1 laptop
Intel GM965 motherboard
Windows Vista 32
2x NVidia Geforce 8800 GTX (have a gig memory each, not running SLI)
4 Gigs of RAM
2x 500 Gig WD drives (RAID 0)
Wacom Cintiq as second display
I know my OpenGL works because I am able to run Modo fine. I checked in Device Manager and all seems ok.
Currently I am running version 12.1 of Photoshop. I have work piling up but can't seem to enable Photoshop's GPU features as I do 3D work.
This is what shows in my System Information in Photoshop:
Adobe Photoshop Version: 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch]) x32
Operating System: Windows Vista 32-bit
Version: 6.0 Service Pack 2
System architecture: Intel CPU Family:6, Model:7, Stepping:6 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1
Physical processor count: 2
Processor speed: 2793 MHz
Built-in memory: 2046 MB
Free memory: 729 MB
Memory available to Photoshop: 1646 MB
Memory used by Photoshop: 70 %
Image tile size: 128K
Image cache levels: 4
Display: 2
Display Bounds:= top: 0, left: -1600, bottom: 1200, right: 0
Display: 1
Display Bounds:= top: 0, left: 0, bottom: 1200, right: 1920
Video Card Number: 1
Video Card: NVIDIA GeForce 8800M GTX
Driver Version: 7.15.11.7482
Driver Date: 20080329113400.000000-000
Video Card Driver: nvd3dum.dll,nvwgf2um.dll
Video Mode: 1920 x 1200 x 4294967296 colors
Video Card Caption: NVIDIA GeForce 8800M GTX
Video Card Memory: 0 MB
Video Card Number: 1
Video Card: NVIDIA GeForce 8800M GTX
Driver Version: 7.15.11.7482
Driver Date: 20080329113400.000000-000
Video Card Driver: nvd3dum.dll,nvwgf2um.dll
Video Mode: 1920 x 1200 x 4294967296 colors
Video Card Caption: NVIDIA GeForce 8800M GTX
Video Card Memory: 0 MB
Serial number: 95458707258873191941
Application folder: C:\Program Files\Adobe\Adobe Photoshop CS5.1\
Temporary file path: C:\Users\Arash\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
C:\, 931.5G, 766.1G free
Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS5.1\Plug-ins\
Additional Plug-ins folder: not set
I am at my wit's end!

Ok folks...I solved the problem. I basically reinstalled from scratch: wipe the drive, reinstall OS and driver. Now, at first I installed the OEM driver for my video cards and that again didn't work. So, I again installed the latest driver right on top of the old (yup, didn't bother to uninstall the older one) and that still didn't work. Then I started to mess around with PhysX and GPU setting in the driver controls. Under PhysX menu it has an option of allowing me to force one of my video cards to run PhyX or allow the driver to decide what to use. I had fiddled around with this option before, but for some reason didn't seem to work before. Anyhow, I decided to pick one of my cards from the drop down menu (I think the first one...am not am my machine now). Surprise...Photoshop enables the GPU options. I couldn't believe it.
Still a mystery to me: why did my OEM driver work on my old HD but not on my new one? Why couldn't the old drive figure out how to use the GPU so Photoshop is able to see it, even before my HD crash all worked fine? I don't know why the NVidia tech person couldn't point me to the menu that controls PhyX.
Anyhow, suffice to say I got it working and installed all my apps and will be using Acronis to back up my system onto another drive: a clone of my HD.
Thanks for suggestions folks. I wish it hadn't taked so long to solve it.....but at the end of the day the solution was: Reinstall everything again.

Recording problem with SoundBlaster X

Hello everyone,
I am running a X-FI sound card which is on my motherboard (MSI P6N Platinium).
I always had MSI boards with integrated soundblaster cards, and I used to plug my guitar directly in the microphone input and record.
Since I got this new board with the X-FI card, I have latency when I play my guitar. The sound has around half a second delay before it gets to the speakers.
I never had such a problem with my other motherboards/soundblasters.
I tried with the front panel mic, and also with the back panel one. The problem with the back panel is that when I plug my guitar in, it doesn't allow me to output to the normal 5. speakers, I have just the option to should Digital output...
Does anyone have an idea on something I should look for in the setup?
I am running a:
Intel Dual Core 6600
MSI P6N Platinium with integrated SoundBlaster X-FI Xtreme Audio
2GB Geil sync RAM
Nvidia 8800GTX 768Mb Video Ram
Thanks a lot in advance for your help!

Hmm.. IIRC, X-Fi Xtreme Audio?doesn't have nati've ASIO?drivers so, if you like to?use lower latency (less delayed), you'll need to either?- install asio4all dri've and use asio compatible software for to input the signal?or?- use WDM/KS capable software for to input the signal?ASIO4ALL driver http://www.asio4all.com?ASIO capable Host? software:VSTHost - http://www.hermannseib.com/english/default.htm?(you need to add least one effect plugin to get signal out ... effevts can be found from KVR http://www.kvraudio.com/get.php)?Reaper?- http://www.cockos.com/reaper/?(support for WDM/KS and ASIO, use WDM/KS with settings 4 buffers x?256 - 52 samples)?jutapa

P35 Platinum R-G-R-R (Persistent)

First - the Moan guide stats:
CPU brand, model and speed (eg AMD Athlon64 3000+ 'Venice' core): Intel Core 2 Quad 6600 Kentsfield 2.4 GHz
# Motherboard model (eg K7N2 Delta2 Platinum, NOT just MS-6570!!): MSI P35 Platinum
# Memory brand, type/speed, size, number of sticks (eg 2x Crucial 512mb DDR400): 2 Sticks Crucial 2GB DDR2, 5-3-3, CL4 (also tested using 4 sticks Samsung 512MB 4-4-4 in varous combinations)
# Video card brand, chipset type, memory size (eg Gainward Geforce 6800GS 512mb AGP): BFG nVidia 8800GTX 768MB
# Hard drive(s) brand, size, type, speed (eg 2x Seagate 200gb SATA150) : 1x Seagate 250gb SATA2 7200rpm
# Operating system and version (eg Microsoft Windows XP Home Edition SP2): Windows Vista Ultimate
# Power Supply Unit brand and output in watts and DC output (amps): BFG 650w Split Rail (20A per rail)
New install, I have not tweaked any settings. Basically, when I power on the system, I get the D-LED R'G'R'R - which the manuka says it is stuck on memory. I have tried many different combinations with no luck. I also get no video output. Looking for any advice or help.
Also of note, LED3 is lit red- pressing the BIOS reset button does not clear it. The manual says that this means the system is in a standby state - but not how it got there or how to recover it.
Thanks in advance

That is not necessarely the only correct answer. Your CPU operates at 266 MHz FSB-frequency. That means at least in theory 533 MHz modules should work if the BIOS is able to detect them and if it sets FSB/DRAM ratio to 1:1.
However, try officially supported modules first. If you have a spare 667 MHz standard RAM module or if you can borrow one, use those for testing.
In a worst case scenario, your board came with BIOS v1.3, which seems to have major compatibility issues. With generic 667 Mhz RAM, it is in most cases possible to work around these problems. This may not be the case, I am just providing an alternative explanation to your problem. Try with different RAM first.
Also, the board has two jumpers that allow you to pre-set certain default FSB-clock speeds (200, 266 and 333 MHz). Have a look at your mainboard manual to compare jumper settings.

Crashes, slow graphics, nvidia updates.

I've been experiencing the wierdest set of hardware (I think) problems recently. I've tried hard to find a solution, but I'm just lost. It's a bit long, but there's a lot of info.
First, it takes a few tries for my computer to start. The VGA won't post, it'll try to start, but it'll shut down and try again. Sometimes it'll continue without VGA, but not often. It does this with any amount of hardware attached to it -- even with just the CPU and motherboard with the onboard graphics chip, and with two PSUs. After it gets a successful VGA post, the computer continues to work fine.
Until recently. A kernel update from 3.2 to 3.3 brought crashes into the picture. Could be completely unrelated to the kernel update, but it consistantly started happening after rebooting to 3.3. One of three things would happen: X would crash and restart, everything would freeze and require a cold restart, or it would take a few seconds to recover. I noticed that the more video I was watching (ex higher res, full screen vs low res in a window) would trigger crashes. A 1080p flash video would bring the system down in 5 minutes, as would any HD video in mplayer or VLC. VirtualBox also triggered eed crashes pretty often while working with Autodesk Inventor inside XP.
Now, here's where things get real bad. Last night I ran a -Syu and nervously updated my nvidia drivers. After rebooting, my system is unusable. My KDE desktop takes about 40 seconds to load, and then I can't even close any windows, open anything. Black boxes show up around / in windows, graphics are fragmented, things don't load. Totally unusable. Switching to TTY's gives a blank screen.
Upon rebooting to windows (which isn't a good assessment of the situation because it's installed on a really slow old IDE HDD) it worked for a bit at a much slower speed than normal, eventually bluescreening and rebooting. I'm working on burning a liveCD with an X interface now to see if I can trigger crashes from there.
I rebooted to an arch liveCD last night and ran a long test ith smartmonctl on my main HDD that Arch resides on. No problems.
Another interesting thing: upon taking out my Nvidia 8800GTX to see if the onboard graphics chipset (Nvidia 8200) would fare any better, I couldn't get any picture at all. The top 1/3rd or so had a picture, but the rest simply flickered with both DVI and VGA outputs on the mobo.
I'll check the logs to see if I can find anything interesting when I get that liveCD up.

I suspect:
overheating - check the cooling fan on the CPU or graphics card, clean the dust with a vacuum cleaner, put some machine oil in it if possible, or replace it
faulty (swollen) electrolytic capacitors on graphics card or motherboard - replace them with the same farrad values, if you know electronics
bad/corrupt BIOS (CMOS) settings - reset them by turning off PC, removing battery, wait one minute, put it back on, start PC. enter BIOS, set all values as you need, save and reboot, see if it works as it should
faulty RAM - remove one of the sticks, boot PC, check if it works, swap the memory sticks, repeat until you've tried them all; test memory with memtest afterwards
faulty VGA/DVI/HDMI cable - reconnect them if loose; if an VGA cable, keep it away from power cables, speakers or any other device that creates magnetic fields (cellphones too); replace the cable with a new one, if possible
faulty monitor - try with another one that works
buggy drivers/kernel - update the system or search the forums for anything similar to your problem
Did you find the culprit?
Last edited by bjornoslav (2012-04-16 19:23:51)

Severe sound crackling noise with SB X-Fi ExtremGamer and 680i m

My computer suddenly (~3 weeks+ after my new build) started making extremely loud crackling noises anytime I have sound on. I remember hearing some crackling noise before on one occasion, but not nearly at this level and it seemed to "magically" disappeared so I forgot about it.
I swapped the speakers to another computer and verified that they are not the source. Unfortunately, I do not have another sound card to swap and check. I updated all of my mobo and sound card drivers, and tried my sound card on both PCI slots on the 680i, all to no avail. EDIT:Happens even with no applications and speakers on, just having Windows running has a slight crackle.No overclocking on my system.
On-board sound is disabled on BIOS.
It still makes ths sound with speaker wires touching absolutely nothing (and also stretched out as to not be wound up).
No microphone on my system.
() Is anyone aware of any issues similar to this?
(2) Should I just RMA my sound card?
My system:
CPU - Intel Core 2 Duo E6600
Motherboard - eVGA 22-CK-NF68-AR (Nvidia Nforce 680i)
RAM - Corsair XMS2 2GB (2xGB) DDR2-800 with EPP
Video Card - eVGA Geforce 8800GTX (768MB)
Sound Card - Creative X-Fi XtremeGamer
Hard Dri've - Seagate Barracuda 7200.0 (SATA 3GB/s, 6MB cache, 320GB)
Case - Antec Nine Hundred
Power Supply - OCZ GamerXstream 600W
DVD Burner - Lite-On 6x DVD burner
Speakers - Logitech X-540 70 watts 5.Message Edited by jblack on 0-22-200707:33 PM

hey could you add me to msn? I have the same sound card and Mobo.--- [email protected]

P6N Diamond Freezes...

System Information
Time of this report: 11/3/2007, 01:01:23
Machine name: ?
Operating System: Windows XP Professional x64 Edition (5.2, Build 3790) Service Pack 2 (3790.srv03_sp2_gdr.070321-2337)
Language: English (Regional Setting: English)
System Manufacturer: MSI
System Model: MS-7320
BIOS: Default System BIOS
Processor: Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz (2 CPUs), ~3.0GHz
Memory: 4096MB RAM
Page File: 686MB used, 5206MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.3790.3959 32bit Unicode
Ok i've been having this issue mainly with FPS games. Also running a 8800 GTX card with the system. When i'm in the middle of playing Teamfortress 2 and some other graphic intensive games it will just do a system dump or freeze going into the blue screen of death or just sit there till i alt tab and it takes about 4 or 5 minutes to get it going. Then having to reboot so that the computer will play games again or it will just freeze again apon entry into it. Anyone have any idea what going on? I'm not sure where to start. Thx

"The blue dump screen that restarts the computer it didn't get the chance to screenshot it went so fast"
disable "automatic restart on system failure", from "startup and recovery" tab. or "F8" just after BIOS post, and choice it from there.
"Ok, I'm using a PC Power & Cooling Silencer 750 Quad - Copper EPS12V 750W Continuous @ 40°C (825W Peak) Power Supply.sing CORSAIR Dominator 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 1066 (PC2 8500) Dual Channel Kit Desktop Memory Model TWIN2X2048-8500C5D - 4 gigs in total. This is the wish list from newegg specifying everything. http://secure.newegg.com/NewVersion/WishList/PublicWishDetail.asp?Source=MSWD&WishListNumber=5152651 . Thanks for your help, and sorry for lack of info was last when i thought about posting on the boards."
Grab Orthos and test for stability:
https://forum-en.msi.com/index.php?topic=99013.msg716696#msg716696
//* Use "Large in-place FFT's leave it for at least 8 hours, make sure that no error(s) will comes during testing, observe CPU temp during testing too. Make sure that no overheating issue occur. *//
"EVGA 768-P2-N835-AR GeForce 8800GTX 768MB 384-bit GDDR3 PCI Express x16 HDCP Ready SLI Supported Video Card"
Have you tested with different games too?
If yes BSOD comes there too or?
What OS you are running?
That VGA model is Factory OC version? Try decrease GD/SD/MEM to Nvidia reference clock speed & re-test.

How about E8500?

Greetings! Everybody seems to be in business of overclocking Q6600. Does anyone have tried overclocking wolfdale E8500?
My E8500 runs smoothly with my P35 Platinum @ 4.2 but with P7N Diamond it's a disaster. With the same components except for the board I can't imagine it being a failure.

I just set up my Xeon E3110 (same as a E8400). So far I've overclocked it from 3 GHz to 3.6 GHz. This is with BIOS v1.0 on the P7N Diamond 780i motherboard. I thought I might wait until the next official BIOS release before going higher.
CASE: Antec Nine Hundred Black Steel ATX Mid Tower Computer Case $59.99 + $9.99 shipping
MOTHERBOARD: MSI P7N Diamond LGA 775 NVIDIA nForce 780i SLI ATX $229.99 + $6.33 shipping
CPU: Intel BX80570E3110 Xeon E3110 3.00GHz 1333MHz FSB 6MB L2 Cache LGA775 $229.00 + $11.88 shipping
CPU COOLING: Scythe SCNJ-1100P 120mm Sleeve $34.99 +$6.33 shipping
CPU GREASE: Arctic Silver CMQ-22G $9.99 +$4.99 shipping
VIDEO CARD: EVGA 768-P2-N831-AR GeForce 8800GTX 768MB 384-bit GDDR3 PCI Express x16 HDCP Ready SLI $339.99 +$7.15 shipping
MEMORY: Patriot Viper 4GB(2 x 2GB) 240-Pin DDR2 SDRAM DDR2 1066 (PC2 8500) $104.99 + FREE shipping
POWER SUPPLY: CORSAIR CMPSU-750TX ATX12V / EPS12V 750W $144.99 FREE shipping
HARD DRIVE (MOSTLY OS):
Western Digital Raptor WD1500ADFD 150GB 10,000 RPM SATA 1.5Gb/s Hard Drive - OEM $169.99 + FREE shipping
HARD DRIVE (STORAGE): Seagate Barracuda 7200.11 ST3750330AS 750GB 7200 RPM SATA-300 $194.99 FREE shipping
OS: Microsoft Windows Vista 64-Bit Ultimate for System Builders Single Pack DVD $189.99 FREE shipping
DVD BURNER: HP Black 2MB Cache SATA 20X DVD±R DVD Burner with LightScribe $34.99 +$5.58 shipping
DVD DRIVE: ASUS Black SATA DVD-ROM Drive Model DVD-E616A3T $18.99 +$5.84 shipping
http://usera.imagecave.com/Vroshnak/overclock.jpg

Mac Pro + X1900 XT crashing after boot (Leopard) - please read...

I have a Mac Pro quad 3GHz w/ ATI X1900 XT videocard. It's one of the first models released.
For the past 4-5 months I've noticed a few pixels on in random places - looks like stuck pixels on an LCD, but they're not as they move around from time to time and sometimes aren't there at all. It progressed to horizontal lines across the screen in places - following window boundaries, etc.
A few weeks ago I de-dusted the X1900 (there was much), applied latest Mac Pro firmware update and applied that recent X1900 XT firmware update. All in the same hour. The dots went nearly totally away, but the lines did not.
In the past 4-5 days, my Mac Pro basically freezes up within five minutes of boot. Can be running different apps. UT2K4 or just activating Expose or doing nothing. Right now it's still up amazingly after 30 mins.
I've got some screenshots and I found some crash log entries that correspond. Please have a look:
http://www.blakespot.com/macproleopardcrash/
I also took a 10 min HD video of the crashing I will put on a DVD and take to the Genius Bar to show the problem, if I need to send in hardware to Apple for repair.
I would love to think it's the X1900 and it overheated or something and became damaged so that would be all I need to send in. Note that NONE of these problems were at all present in the first 6 months of life or so. And yes, the crashing is post-Leopard install.
Very troubling. Is anyone else having issues like this? Any input appreciated.
Thanks much.
blakespot

I have had nothing but trouble with ATI cards on all of my macs, I really wish Apple would drop the ATI card altogether and replace it with an nvidia 8800gtx,
its the only thing still stopping me from buying a mac pro,
the nvidia cards are either 256mb £99 or £1,000 quadro (old technology and overpriced), they need a card in the middle ground that's not an ATI

No audio device installed (Big iss

Hello all,?I have Vista Ultimate and am using an Audixy 4. After installing the new drivers today (SBAXVSD_PCDRV_LB_2_2_0002) I lost my sound. At the device manager i see that "This device is working properly."?When I go to Controle panel/Sound I see the device but I almost none of the commands work (Disable, Test, Configure) only the Properties work but there I cannot do anything useful. When I right click on the Sound icon at the bottom right of the screen and go to Open Volume Mixer, it says "No audio device installed"?Yersterday I also had this issue and reinstalled Vista with a fresh install which fixed the problem. Today I had the same thing again and decided to use my onboard sound card (RealTek, 623_Vista_APO), and nothing changed! I am still getting the same errors as with the Audixy 4. Is there any sollution to this Vista bug? :angry:?Thanks for reading

I am not sure why anyone is not replying with a resolution but I am having a similar problem. I am having a computer custom built and the Technician building it claims that Windows Vista will not recognize both the Soundblaster Xi Fi Extreme Music sound card and the MSI 8800GTX 768MB video card that I have chosen for the configuration. This is due to some conflict. The Technician claims the problem is the sound card and Creative needs to update drivers before this configuration can be done. Is this true? Can anyone explain why? I know Creative has Windows Vista drivers but apparently for this situation it does not resolve the conflict.

Problem installing vista/xp on a mac pro, installers don't see bootcamp

hello there!
recently, a video post production studio i work for purchased a new penryn-based mac pro (2x3.0 ghz, 6gb ram, nvidia 8800gtx).
yesterday i wanted to install vista onto it to be able to help other windows machines in the studio with 3d studio max rendering jobs (8 cores should do wonders for that), but i ran into a weird obstacle.
this mac has 5 internal sata drives - one (320gb) for the system, and 4 disks (750gb each) in raid0 set (just a temporary setup until the studio purchases a fiber optic card with external disks). the DVD drive is an IDE one.
this is the first time i'm setting up windows on a mac, so i could be doing something wrong, even though i doubt it - it seems very straightforward.
so i created a 32gb partition on the system disk (the only one that's not in raid) using boot camp assistant, and started vista sp1 x64 install (boot camp recognized the install dvd).
after a reboot, vista started it's setup routine. everything was fine until it reached the part where i should select the destination partition for vista. this is the weird part: vista installer sees all 4 750gig drives from the raid, but it doesn't see my system drive (320gig) which has Macintosh HD and BOOTCAMP partitions on it. vista even sees any usb drives connected.
doesn't seem logical, as all sata drives are on the same controller (at least that's what leopard system profiler says).
i thought it had something to do with the fact i'm trying to install 64bit vista, so i tried with windows xp sp2 (x86), but the same thing happened.
i searched all over, but couldn't find anyone with the same problem.
any thoughts?
Message was edited by: recircle_admin

This thread says it all - and then some
http://discussions.apple.com/thread.jspa?messageID=7150748&#7150748
I would pull all the drives except your boot drive. Makes it easier.
32GB is pretty small actually for Vista x64. And the SP1 patch process can temporarily use another 10GB. Also, you are running off the slow inner tracks of your drive, which is half performance of outer tracks.
Most people opt for stock 2.8GHz Penryn - not a huge benefit from going with 3GHz, but that is beside the point.
Always good to disconnect any device during the install except what you have to use (keyboard, mouse) which can interfere.
You MUST reformat the 32GB from FAT to NTFS before you can install. That is where most people stop. You have to DELETE and then CREATE that BOOTCAMP 32GB (Advanced Options) before you can proceed with installation.
You don't want 32-bit version if you want to access more than 1.9GB RAM.
Lots of threads here in BootCamp, in Mac Pro Discussion, and MacRumors Windows on Mac.
http://forums.macrumors.com/forumdisplay.php?f=86

Dual Monitors Windows 7 Problems

Ok, this problem is getting really annoying and I think its a problem with windows 7 itself and not my computer.
Basically I have a dual monitor setup with the left hand monitor as my secondary and right hand monitor as my primary. Whenever I have an application with any graphics on it at all such as a progress bar on my left hand monitor moving windows around becomes laggy and juddery, yet this doesn't happen when the graphical app is on my primary monitor!
My system Specs:
ASUS Striker Extreme MOBO
OCZ 850W gameXtreme
Core 2 Duo 2.4GHz CPU
4GB (4x1GB) OCZ DDR2 1066MHz RAM
Nvidia 8800GTX
Sound blaster x-fi Xtreme Gamer (older PCI version)
3 x 80GB HD for system drive in RAID 0
1 x 500GB and 1 x 250GB drives for storage
Monitors are 1680 x 1050 res
Windows 7 Exp Index:
CPU: 5.9
Memory: 5.9
Graphics: 6.8
Gaming Graphics: 6.8
Primary HD: 5.9
What iv tried:
Updating to latest drivers
Upgraded system memory from 2GB to 4GB
Installing 64-bit version
removing sound card and re-installing windows from scratch
upgraded my PSU
Thanks for your help!

(Latest update) This is the best I can do to alleviate the problem, and does reduce its severity immensely, but I found myself still noticing some slight playback glitches in videos on my second monitor which probably also translate to anything else with movement. I have tested with a panning scene in one of my videos and there is a subtle micro-stutter on my second monitor which I can find no way to fix. This doesn't occur if outputting to a single display, one or the other, nor does it occur when playing the video on my primary monitor in a dual-monitor configuration. Note that when I say "primary monitor", I am not referring to the monitor Windows has marked as primary, but my actual monitor rather than TV. In a dual-monitor configuration, this micro-stutter will only occur when playing video on my right monitor (TV), regardless of settings or which ports the monitors are connected to on the GPU. The micro-stutter occurs with no relation to the activity on the other screen, as it can be completely still. I can confirm the micro-stutter does not occur at all with Desktop Window Manager (Aero) disabled. In short, this is a nightmare.
(Note that this micro-stutter is equally replicable in the 182.50 (WDDM1.1-less) driver, meaning there is no way to solve it other than disabling Aero or outputting to a single monitor.)
I think I've solved the problem.. for me, anyway. I've divided this into short answer and "long answer", which is closer to a stream of consciousness in some ways, as I found out about Force10Level9 as I was writing.
The short version:
I've found some registry keys which seem to have fixed the problem for me. I haven't experienced any side effects, but use the tweaks at your own risk!
I don't know exactly what they do. This comes from a lot of.. experimentation. I believe FrameRateMin tells the Desktop Window Manager that it's crucial to try to keep the framerate at or above the value specified (more details below), and Force10Level9 sounds like it forces DWM to use DirectX 9. I'm fairly certain about the former, not as certain about the latter, but together they do wonders.
You can view the fix below. You can then save it as a .reg file and import it into your registry. Restart the Desktop Window Manager service or reboot to see the changes.
Fix: http://pastebin.com/FFDbubw9
Undo: http://pastebin.com/zA8CJY06
(P.S. Just ran a FurMark test between fix applied and no fix. No difference in performance, with an inactive secondary monitor. I also noticed no difference in Physical Memory usage as reported by Task Manager. YMMV, let me know if you have any side effects.)
(P.P.S. The screen fade that happens when you log in/out is just as choppy as before (or if it wasn't choppy for you, that shouldn't have changed). Oh well, how often do we see that thing, anyway? :))
By the way, it appears 10Level9 is Windows 7's emulation platform for running DX10 on DX9 hardware. It's reported to be at least a 0.5x performance hit, so it's surprising that it actually makes Aero run better. If this article is anything to go by, Force10Level9 makes Aero run exactly the same as it does with older WDDM 1.0-only drivers like 182.50: http://www.techarp.com/showarticle.aspx?artno=637&pgno=1
The long version:
Well... I was able to do one more thing.
There is an undocumented registry key which allows you to fine-tune the Desktop Window Manager's scheduling. Unfortunately, all of its values seem to be defunct in the final version of Windows 7 we all use today... except one: FrameRateMin.
From what I gather, the Desktop Window Manager (Aero) carefully monitors the framerate it is able to achieve, and when it can't measure up to its own expectations, it will perform a "step down", or framerate reduction, and maintain this lower framerate for a given period of time (at one time specifiable with a registry value) before trying again at maximum speed.
I presume it does all this to keep things looking "smooth".
The problem is, in most cases, it doesn't help, and actually prolongs the stuttering duration. By "in most cases", I mean in every case it's happened in my personal usage of my Windows 7 computers.
So what helped me was setting this FrameRateMin value to 60. That way, the Desktop Window Manager considers anything under 60fps to be unacceptable and will not remain at a lower framerate for purposes of perceived smoothness. Thus, the stuttering will take up as little time as possible, making it nearly unnoticeable most of the time.
Keep in mind DWM shouldn't be having performance problems to begin with, but apparently in some cases, like with my particular hardware (desktop and laptop) and the latest NVIDIA drivers, it does.
Down to brass tacks. The registry key is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\DWM\Schedule. The value is FrameRateMin, a DWORD representing the minimum framerate DWM will consider as acceptable. I set it to 60, but you can set it to whatever you want.
To repeat, this WILL NOT prevent Aero from ever getting below the framerate you specify; it simply prevents Aero from retaining a lower framerate after a stutter in order to give the illusion of smoothness (an illusion which fails).
I imagine the main reason it fails so spectacularly in my usage is because I watch a lot of videos which play back at 24fps. Such a framerate plays back terribly with a 30Hz refresh rate, which is what Aero would reduce itself to for extended lengths of time. Now, performance hiccups are minimal, but sadly still existent.
So this isn't a solution, but it does help. I am still uncertain of where the problem lies, considering GPU-Z shows graphics card loads to be as low as always when it's happening.
Oh, and I found one more registry value. This one is far more important. :) It solves the problem for me entirely, from what I can tell.
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics
add the DWORD value Force10Level9 with a value of 1.
I haven't noticed any side effects, just smooth performance.
Apply these tweaks at your own risk!

Media encoder crashing when exporting h.264

I have a short 1:30 project I'd like to export using the h.264 codec. The project is made up of [email protected] h.264 quicktimes shot on a Canon 1DmkIV. If I export to h.264 using either the 720p or 1080p presets the Media Encoder will do two render passes then crash with an "Unknown Error". This will happen if I export h.264 or as a quicktime using the h.264. Strangely if I export as h.264 bluray it works fine but then the audio and video are seperate and not what I need if I intend to upload to Vimeo. I can successfuly export to other codecs.
I've clicked through premierepro.wikia.com but couldn't seem to find any answers. Anyone have a suggestion?
Thanks in advance,
FYI
Adobe Premiere Pro CS3 v.3.2.0 (374)
Windows XP SP3
Intel E6850 Duo Core @3Ghz
4Gb RAM
nVidia 8800GTX
Soundblaster X-Fi

Ok, that worked but Media Encoder wouldn't render out with TS checked using PCM audio, I had to change to Dolby Digital. Once rendered and uploaded to Vimeo the image was displayed as 4:3 but with the anamorphic vertical squeeze even though I was using the 1080p24 preset. <shrug>
I'm wondering if it is the Mainconcept codec that's buggy. Is there an alternative h.264 codec to use with Premiere CS3?

PSE 7 Editors Hang Badly in Windows 7RC x64

Currently running Windows 7RC x64 on a Dell XPS-720-H2C o/c to 3.73 GHz with 6 GB of PC8500 DDR2 o/c to 1066 and a pair of NVidia 8800GTX display adapters in SLI. The machine runs Windows 7 like butter and is a joy to use. Purchased and downloaded PSE 7.0 andf the install was flawless. Ran the organizer and cataloged all my photos very quickly with no performance issues.
Opened the Editor and created a new file (500x503, 72dpi, 24 bit) and it took about 2.5 to 3 minutes for the image area to show up. PSE7 was totally locked the entire time but did NOT show as Not Responding in Task Manager. Once the image shows up, any changes to the file also take 2.5 to 3 minutes. Very frustrating. Every one of my other applications are running flawlessly in this Win 7 envoronment.
Uninstalled and reinstalled with the same result. Changed out RAM (I have quite a few spares lying around) and still no change. Enabled/disabled SLI which had zero affect. Ran the executables in a variety of comaptibility modes, still with no improvement. Not sure what else to try... maybe PSE 7.0 is not compatible with Windows 7.
I went through much of this forum and couldn't find anything substantive regarding performance problems with Vista x64 and essentially nothing regarding Windows 7RC x64. Any ideas out there?
Thanks in advance,
Doug

Others have reported PSE working with some versions of Windows 7, and many have reported PSE working with Vista 64. And many people have various problems getting PSE to run on Vista 32. So it's entirely possible your problems are not directly related to Windows 7 or 64-bit.
See this FAQ for troubleshooting PSE problems:
http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_Troubleshooting_Organiz er_crashes
and see this FAQ about PSE and Vista 64:
http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_PSE_and_Vista

Nvidia 8800GTX 768Mb

Similar Messages

Maybe you are looking for