1. Define 'Crashing'. Is it the 'non-responding' message, is it frozen and does the mouse cursor not move anymore, does it quit PR and checking for a solution, is it turning off your machine, is it a BSOD?
2. Are you using the latest video drivers from nVidia? Current version is 296.10
Have you already tuned your system a bit? Removing games, MSN and similar crap, disabling the sidebar permanently, turning off indexing and compression of both drives, setup a fixed pagefile on the D: drive, etc.?
It could be a compatibility issue between the i7-3930K and the RAM. Read posts from Scott Chichelli about the i7-3930K and you'll find that that CPU really needs 1.35V-rated RAM to work correctly, and that there is a major issue between the 3930K's memory controller and the Micron chips that are used on most RAM modules these days.
The even more expensive i7-3960X's memory controller does not suffer from the same issue.
1. I probably should have said "freezing". The on screen image is frozen...I cant move the mouse, work the keyboard, CNTL+ALT+DEL is no use. I have to shut the PC down manually (hold PWR button on case down for 3-5 secs).
2. Nvidia drivers are up to date, I downloaded the driver about 2 weeks ago. I'll double check this when I get home.
3. The only "tuning" I've done, is disabling windows indexing. As far as the the other suggestions go, "removing games, MSN and similar crap, disabling the sidebar permanently, setup a fixed pagefile on the D: drive, ect"...I had no idea that these would help. Do you have a link or a list of programs/operations that need to be addressed? I don't even know what a "fixed page file on the D:" is
Thanks for the info so far!
To find out how to move your page/swap file to a different drive, search at Microsoft
Here Win7 Tuning Help & Tips & Utilities
Free System Optimizer http://www.iobit.com/advancedsystemcareper.html
Registry Cleaners http://windowssecrets.com/newsletter/putting-registry-system-
Be sure you have the default hard drive indexing OFF for all drives and folders!!!
Temp/Cookie Cleaner http://www.mixesoft.com/
Win7 Toolbar http://WindowsSecrets.com/comp/110210
More Win7 Tips http://windowssecrets.com/comp/110127
Utilities http://windowssecrets.com/comp/110106 (Startup Solutions)
Win7 Help http://social.technet.microsoft.com/Forums/en-US/category/w7itpro/
Win7 Configuration Article http://windowssecrets.com:80/comp/100218
Win7 Monitor http://windowssecrets.com:80/comp/100304
Win7 Optimizing http://www.blackviper.com/Windows_7/servicecfg.htm
Win7 Virtual XP http://www.microsoft.com/windows/virtual-pc/
More on Virtual XP http://blogs.zdnet.com/microsoft/?p=5607&tag=col1;post-5607
Win7 Adobe Notes http://kb2.adobe.com/cps/508/cpsid_50853.html#tech
Win7 Adobe Update Server Problem http://forums.adobe.com/thread/586346
An Adobe Win7 FAQ http://forums.adobe.com/thread/511916
More Win7 Tips/FAQ http://forums.adobe.com/thread/513640
Win7 God Mode http://forums.adobe.com/thread/595255
CS5 Install Error http://forums.adobe.com/thread/629281
CS5 Help Problem http://kb2.adobe.com/cps/842/cpsid_84215.html
Win7 and Firewire http://forums.adobe.com/thread/521842
Win7 64bit Crashing and "a" fix http://forums.adobe.com/thread/580435
Harm's Tools http://forums.adobe.com/thread/504907
Optimizing Hard Drive http://www.video2brain.com/en/videos-5353.htm
Win7 Reinstall http://windowssecrets.com/newsletter/win7s-no-reformat-nondestructive-
Anti-Malware Tools http://windowssecrets.com/newsletter/the-advanced-system-recover-
Repair AVI http://forums.adobe.com/thread/888268
Tune Vista & Win7 64bit http://forums.adobe.com/thread/436139
GPU Monitor http://www.techpowerup.com/downloads/2092/TechPowerUp_GPU-Z_v0.5.8.html
What am I looking for in Memtest? Is there a particular temp or error message I should keep an eye out for? Sorry, I've never had the need to use these types of programs before .
Also, I've done some research on the 1.35v memory...these should do the trick...correct? Thinking 32Gb this time around (going to get 2 packs of 16Gb 4x4).
Thanks for all the links J. Smith!
That memory is for 1155 mobos, not for X79 mobos.The type you selected I would not touch. Samsung finally released their low voltage ram http://www.newegg.com/Product/Product.aspx?Item=N82E16820147096
Like Scott said, download and run Memtest86+ from here: http://www.memtest.org/
Let it run a decent time and if no errors show up, it may be something else. What does the event viewer show in terms of errors? For tuning tips, look at Adobe Forums: Guide for installing and tuning a Vista...
This also applies to Win7.
This "freezing" that you describe occurs with both Gigabyte and Asus boards with early versions of the BIOS. Update your BIOS to the latest version - the problem was solved in BIOS releases in early March.
This cured the problem on my Gigabyte motherboard, and I know of one other user with an Asus board who took this advice and solved the problem.
Ok, I ran the memtest86+ for 3 1/2 hours...NO errors.
I updated my BIOS to the latest version, 1010.
While the computer hasn't crashed yet, its still behaving the same (choppy video scrubbing, ghosting text boxes).
I'm going to go through Harm's tuning tips and see if this helps.
Of course, any other suggestions or comments whilst I'm doing this are welcome.
It sounds as though the BIOS update may well have solved your freezing problem - your description of the problem sounded just like my very similar system with the original BIOS.
I have built a system very like yours, except that I am using a Gigabyte GA-X79-UD5 motherboard and two RAID0 arrays, plus two single drives for storage.
As for memory being the problem, I am using 32 GB of Corsair XMS3 PC£-12800 at 1.5V and since the BIOS update my system has been 100% stable. So unless the problem that Scott alleges exists is confined to Asus motherboards, I doubt that your problem lies with memory.
So I've done a fair amount of "tuning". Went through and turned off some of the windows features I wont be using. Also went over to Black Viper and adjusted my setting based on his "safe" configuration.
The problem with the ghosting text boxes was solved with: Control Panel-->System-->Advanced system settings-->Visual Effects-->Adjust for best performance! Looks a bit bland, but I'll get use to it.
No crashing or freezing yet!
I am, however, still having trouble with scrubing video (when I grab the little blue triangle in PP and move it back and forth). It does it when the footage has a YELLOW bar over the top. With a GREEN bar, everything scrubs smoothly. Any suggestions or something I'mmissing?
Screen shots of Logs/System and Logs/Application
Thanks for the link John.
I'm still a bit concerned becasue I've seen people scrub through yellow render bars with no problems (with a quad core processor).
After watching some videos, I've realized that AVCHD (the files I'll be editing) use the processer rather than the HDD to preivew. Could it be that my processor is causing the slow playback?
Thanks for all the replies and patient answers so far. Hope I'm not being to dense.
Well I decided to shoot some footage today and do a quick edit..just to see how things are working.
I'm noticing HORIZONTAL LINES moving from the the bottom of the frame to the top during playback. Any ideas what this is?
Footage is AVCHD.
I import the footage and drag it to the new sequence icon.
My monitor is at the correct resolution and 60Hz.
You might want to read what the bios update is for before you assume that is the blanket fix by itself btw.
F10 3.37 MB 2012/03/23 Asia China America Europe Europe(Russia) : FTP / Http
- Improve compatibility
Incase your wondering that is a ram compatibility update
P9X79 PRO BIOS 1010
1. Improve system stability.
2. Improve memory compatibility.
3..Enhance compatibility with some USB devices.
4.Fix PCIEx16 VGA card HD 7970 cannot be detected when the temperature of VGA less than -40.
There is a reason the turning off the Aero seemed to solve your ghosting and other video anomalies. When the Aero is on then Windows controls the Memory managment for the video/display. This also means there is allot more caching to ram to handle the frame buffer isolation. When people have pointed you to ram they were not incorrect on this. The MPE engine uses the system ram for the grand central station of data transiting between the CPU, video cards, and storage. If the timings on the ram are not syncing correctly to the ram controller in the cpu then your going to have random anomalies including drawing out on the screen because all of that data is transiting through ram as well. Think of it this way. If the memory controller sends a read request to a page on the ram that was prematurely wiped or not refreshed in time, then that data is garbage regardless of the rest of the data. You can manually set bios settings to try and get that ram to work or you can look at ram meant for that platform. BTW so everyone is aware, It seems Samsung has transitioned to 1.35V ram for their modules available in retail atleast from what I can see available in stock. That is tvery telling if they have done that since 1.35V requires better grade chips which raises the price of production.
Thanks for the info! I grasped some of what you explained (I'm not a computer guy....although, this build has tought me alot!).
I tried the Samsung memory linked above, but it did nothing for the ghosting text. Turing off some of the features in windows fixed that, but brought about another problem....the horizontal lines in video playback. I turned Aero ON (in a limited capacity) and it seemed to have solved the horizontal line issue...weird .
Could you recommend any other 1.35V memory that is meant for this platform?
Concerns about sluggishness on the time-line, involving scrubbing and random brief playback and trims, have been raised here before by newer users..... What kind of responsiveness is to be expected, with a x79-based system like this one?
For <50mbs GOP codecs ; for AVC intra 100-150mbs; for intermediate codecs 100-220mbs? More or less instantaneous? Tolerable tedium? Outright insufferable?
We have not had the Samsung 1.35V ram in stock here to test yet. I am still trying to get 8 modules here so we can verify compatibility and settings. However based on the rated timings I expect they should work fine if the bios is setup correctly. I need to know your current bios settings with those in. You can email me directly at firstname.lastname@example.org or call at your convenience. Number is on the website.
Eric, in reply to your post (#10), what makes you assume that I did not discover this information for my Gigabyte motherboard before upgrading my BIOS? I admit that it was an assumption on my part that Asus motherboards would have the same solution, but I know of another user who solved this probem with his Asus motherboard by upgrading the BIOS to 1010.
The rest of your response to me is irrelevant - my system functions correctly and does not, and has not in the past suffered from these problems.
The post was to reference why it worked for you and possibly other users. I did not assume anything beyond what you stated to the original post which was that memory was likely not the issue. I was pointing out the bios update was based around memory comparability. Now what you set your ram and bios settings to after the update I dont know. If those settings are default since most of the bios updates default the CMOS then that would also explain why it's working as well. The importance of the post was to get the original person back on track to what is causing the issue they are having and why. In that process I had to explain why a bios update might fix something similar to their issue and the reason for that. The rest of the response was toward the original person.
In post 14, I said that the problem was not his memory because he had updated the BIOS by then (as I suggested in post 11), and that solved the memory compatibility problem.
The rest of your post 27 was directed at me too, it was headed as a response to a post of mine. If you wish to respond to two posts at the same time, it would make sense to use separate responses to avoid confusion.
I am using the 3930K processor, which had this memory compatibility problem, which as I said originally, was solved by Gigabyte and Asus in BIOS releases in early March.
The processor is not overclocked.
Please do not think that I am attacking either ADK, or its personnel.
I was simply trying to correct the misconception contained in this thread that this memory incompatibility is a current problem. It is no longer a problem, at least for a non-overclocked 3930K, provided the BIOS is updated. This is evidenced by the OP stating that once he had updated the BIOS, the freezing ceased.
I apologize for the confusion with posting to 2 posts in the same post. I normally try to avoid double posting unless it's a follow up thought.
Actually the blanket memory compatibility fix is another point I was trying to dispel. Just because the fix worked for your modules does not mean it's going to work for everyone else. The changes alone between Corsair XMS modules between batches and runs is significant depending on what their building with when and binning. Now multiply that by each model/series and then each manufacturer. There is no way Gigabyte or Asus can update timing detection and round trip latency adjustments for every one of those in a single update. It likely may have just fixed a few batches of any one manufacturer and only at certain speeds if that much. Once again there are to many variables to assume it's a blanket fix for memory compatibility and I dont want people lead down the wrong path in troubleshooting these because of that.
The system not freezing is not the only symptom the poster stated that is a sign of ram issues nor is that the only symptom of the ram issues. Ghosting is a frame buffer corruption issue. Now the question is where the frame buffer corruption is occurring. Is it on the video card or the system ram. Considering the Ghosting went away when the client turned off the aero then the answer is the system ram. When the Aero is turned off, then the video driver alone handles the memory management which uses less ram. Also the anomalies on preview with lines with the MPE engine is also due to a corrupted frame buffer. So yes the memory is still an issue and the assumption it's not is completely incorrect.