Iam facing the same problem. System Freeze while working on 3DS Max .

 

Processor : 3930 K

Motherboard: DX79TO

Graphics : Quadro 2000 D

Ram : Corsair Vengeance 16 GB

 

I have tried many driver versions from nvidia site . 295 , 301.24 and also the drivers from the cd i got with the quadro card . Also Tried testing Asus 210 Card . But stil freezes. Rendering is fine but as soon as i start working on the viewport of Max , the system freezes totally . I have to press the restart button .

 

Also tried setting openGL as the display driver . but no use . It happens only with 3DS max . Having installed max 2009 , 2011 , 2011 design .. but same results . I work even on Autodesk Maya , and it works just fine .

 

Its a brand new PC . Please help me out .

I have tried many driver versions from nvidia site . 295 , 301.24 and also the drivers from the cd i got with the quadro card .

 

It is not your video card or the display drivers. You are running out of memory. Make sure your virtual memory (page file) setting is set to 'System Managed Size'. Run your Event Viewer and look for an "event" for the freeze as Windows 7 normally records these events. In FSX I would also be telling you to lower your sliders as they are set too high. Graphics rendering requires a very, very powerful computer. I see your Graphics card meets specifications and is approved specifically for AutoCAD though. Your CPU is extremely powerful too. You may also try lowering display settings for your video card. If changing the page file setting doesn't fix it for you, then I would seek support from 3DS Max. Don't know how many projects you are working on at one time with 3DS Max but you might need to adjust the number of objects being rendered at one time.

 

Best regards,

Jim

Thank you . I set the virtual memory to System managed Size .But that didnt solve the problem.stil freezes my PC.

 

i havent even started working on 3DS Max on this new system .Just installed it recently. before I can do anything , even a simple zoomin or zoomout operation in the viewport , freezes everything . today it happened twice while working on photoshop too .

 

I believe you can really help me out with this one .

even a simple zoomin or zoomout operation in the viewport , freezes everything

 

Make sure your display driver settings are not set too high. Return them to the default and see if that improves things. Here are some 'Tips and Tricks on how to speed up rendering' in 3DS Max for an individual who had similar problems with his computer as yours - http://www.max-realms.com/modules/newbb/viewpost.php?uid=52667 and I checked out your Motherboard and here are some guidelines that might help you - http://www.tomshardware.com/forum/307820-30-dx79to. Is your system overclocked? Did you build it yourself?

 

Did you see anything in the Event Viewer (click on the Start Button, type Event Viewer in the Search bar then look up and click on Event Viewer. Once open, click on Event Viewer (Local), then Custom Views, then Administrative Events. See if there are any critical or major errors being reported by your system. Those items should be fixed, especially the critical errors.

 

Start up your computer in Safe Mode and see if the problem persists. A system driver or network connection can cause system freezes too. You might check out the following program I use occasionally to check for driver updates or to make sure all my drivers are up-to-date - http://performersoft.com/driver-performer.php. It's freeware to download, install, and run. It will search your harddrive and look for problems then make recommendations for driver updates. If you want them to download and install the updates for you, then you'll have to purchase a license. At least it will give you an idea if your system is up-to-date. I'm constantly updating my drivers on my own but decided to download and try this program. It found over 100 drivers out of date!! And my system was a little more than one year old! Needless to say, I bought a license and got things fixed.

 

You might also download and install a free registry cleaner and system cleaner like CCleaner. It does a very good job of safely cleaning your registry and deleting things not needed on your harddrive like temporary files that could still be running in the background. Here's the link: http://www.piriform.com/CCLEANER. You won't believe how systems can be brought down to their knees without an occasional cleaning of the registry and removing temporary or useless files.

 

Another thing that could be slowing down your system is malware. Super Anti-Spyware does an excellent job and it's free - http://www.superantispyware.com/.

 

Hope this helps.

 

Best regards,

Jim

Hi , Its been a while since I posted here . I was busy troubleshooting the freezing problem. Here are the updates :

 

1.I disabled the Graphics card driver in the device manager .and my system started working widout any freezing after that . as soon as i reanabled the driver , problem started again.

 

2.I tried installing the Quadro card on my dual core system , and it worked like a gem. no freezing at all.

 

3.I even approached my computer dealer from where I got the system . He replaced each component one after the other infront of me with new ones. including RAM , Graphics Card , SMPS etc . but no use .

 

While I appreciate the solutions given by you , like registry cleaning , event viewer etc .. theres definitely no justification for such serious errors especially when its a brand new PC . When my good old dual core CPU has not given me any problems till date when i run the same apps. like 3ds max , photoshop , maya . and what not .

This beast is giving me sleepless nights .

 

 

Is it possible that it might be the motherboard problem? because I have seen a couple of posts on other forums , ppl using the same DX79TO Boards facing the same freezing issue.

I but Just Flight Traffic X in everything was great,Had some problems with FSX had to take it out but it back in.Try to put Traffic X in about 1/3 in to retracting files the whole computer freezes up.I got a disk from PC Pilot same thing happens.Wrote Just Flight twice nothing from them!! here is my error:- System

 

- Provider

 

[ Name] Microsoft-Windows-Kernel-EventTracing

[ Guid] {B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}

 

EventID 3

 

Version 0

 

Level 2

 

Task 2

 

Opcode 14

 

Keywords 0x8000000000000010

 

- TimeCreated

 

[ SystemTime] 2012-06-08T01:13:32.050890200Z

 

EventRecordID 497

 

Correlation

 

- Execution

 

[ ProcessID] 4

[ ThreadID] 196

 

Channel Microsoft-Windows-Kernel-EventTracing/Admin

 

Computer SCOTT-PC

 

- Security

 

[ UserID] S-1-5-18

 

 

- EventData

 

SessionName ReadyBoot

FileName C:\Windows\Prefetch\ReadyBoot\ReadyBoot.etl

ErrorCode 3221225864

LoggingMode 0 Thanks for the help....Scott

Try this:

 

* Open the Performance Monitor management console, e.g., "Administrative Tools" -> "Performance Monitor", or,"perfmon.msc /s" from the Run Command.

 

 

* Under the management console sub-folder "Data Collector Sets" -> "Startup Event Trace Sessions", Right click "ReadyBoot", Select "Properties"

* Select the "Stop Condition" Tab.

* Increase the "Maximum Size" value as needed, I would say 60.

* Press OK, and exit.

 

Best regards,

Jim

- System

 

- Provider

 

[ Name] Application Error

 

- EventID 1000

 

[ Qualifiers] 0

 

Level 2

 

Task 100

 

Keywords 0x80000000000000

 

- TimeCreated

 

[ SystemTime] 2012-06-07T20:42:55.000000000Z

 

EventRecordID 63428

 

Channel Application

 

Computer SCOTT-PC

 

Security

 

 

- EventData

 

fsx.exe

10.0.61637.0

46fadb14

ai_player.dll

10.0.61637.0

46fadb57

c0000005

00037489

12c8

01cd44ec986e82c5

C:\FSX SIM X\fsx.exe

C:\FSX SIM X\ai_player.dll

5b831f59-b0e1-11e1-bae6-c0cb38bb1ddd Sorry I think this is the correct error I should have sent....

Sorry I think this is the correct error I should have sent....

 

This is a common module error. There is no known solution. However, the ai_player.dll error will occur 100% of the time when you have FTX/Orbx software installed and active and when you close down FSX but it does not cause FSX to crash to desktop. It just happens when you close FSX and an error message will state FSX did not close properly. If you go into the FTX's Configuration program and return scenery to the default, the problem will go away. FTX/Orbx can't pinpoint the problem. I think it's a problem with FSX rendering a scenery object that does not exist or in another location. You have the Exception Error c0000005 which indicates too that you had a Memory_Access_Violation. In other words, ai_player.dll was being called by FSX and a memory access violation caused FSX to CTD. It could be a problem with Just Flight's Traffic X but then everyone who owns Just Flight's Traffic X would be having the same problem. You can go into your FSX settings and turn off Aircraft AI, then run FSX and see if the problem still occurs. I think your problem is with system memory configurations. As I recall I discussed this with you in another post. You might also try returning your sliders to the default (in FSX display settings you can click on reset defaults for each page) and then see if this fixed the problem. If so, a slider was too high causing FSX's inability to render or perform an action in time. I did some Googling too and some others attributed the problem to the video card drivers. If you just updated them, this might be the cause.

 

Since this is a whole new problem not associated with the OP, you should start a new post. This is confusing having several different errors in one post. Thanks.

 

Best regards,

Jim

System Freezing DX79TO Problem solved :

Updated the BIOS on the advice of Intel Customer Care . My system never Froze after that . Finally the End of Frustrating troubleshoots !!

 

Special thanks to Firehawk too for his insights .

Thanks for your kind comments and for posting information on how you fixed your problem. Resetting the BIOS back to the default or, in your case, upgrading to the latest BIOS, will fix a lot of things. Sometimes we accidently set the wrong settings and they will work for a while but sooner or later take your system down. Good to hear you are back to flying instead of troubleshooting.

 

Best regards,

Jim