3ds Max causes BSOD on launch

Become a member of the CGSociety

Connect, Share, and Learn with our Large Growing CG Art Community. It's Free!

Thread Tools Search this Thread Display Modes
Old 06 June 2012   #1
3ds Max causes BSOD on launch

This has been driving me up the wall for the past few days, I don't know what to do...and I'm usually very resourceful and know my way around the technical aspects of a computer.

2 days ago I was rendering out a 50 frame animation using 3ds Max 2012 and VRay 2.20. About 8 frames in, the computer bluescreens and restarts, from there on out, every single time I attempt to open 3ds Max, it bluescreens before the application can even fully launch.

Things I've tried so far:

Reinstalled 3ds Max onto not one, but two separate hard drives, both end in the same result.
Ran disk error checking on the hdd's.
Ran memtests, as well as manually pulled the ram out and checked each stick one at a time.
System restored at multiple points in time.
Ran registry error checkers (Boostspeed, Advanced System Care 5)
Reinstalled Windows completely, loaded all of the latest drivers for my hardware straight from the websites, installed the fresh version of 3ds Max, and STILL it bluescreens whenever I attempt to open it.

Note that it ONLY does this with 3ds Max, nothing else. I can open Photoshop, AfterEffects, ZBrush, and any other intensive program you can think of, but Max bluescreens instantly. Please help :(

PC Specs:

i7 2600k - not overclocked
16GB RAM - 1600mhz
Asus P8P67 Mobo
Windows 7 Ultimate
64gb SSD
1.5tb HDD
2 x GTX460 - not SLI

Last edited by darkshark : 06 June 2012 at 01:32 AM.
Old 06 June 2012   #2
Have you tried a different video card? Checked temperatures? Checked for physical signs of malfunction (burns and singes, burst capacitors, melted connectors, etc.)? Checked voltages from the power supply? Since it failed under load and the problem persists my guess is a component has failed or is failing.

Last edited by olson : 06 June 2012 at 12:56 PM.
Old 06 June 2012   #3
Where would I even begin to look for something like a burst capacitor?
Old 06 June 2012   #4
are you able to catch the stop code on the BSOD?

should have a bunch of register garbage and hex

then something like:
Stop Error 0x0000008E (0xC0000005, 0XF544B5B6, 0XBAC52AZ0, 0X00000000)
[color=blue !important][color=blue ! important]system32[/color][/color]
: lzx32.sys - Address F544B5B6 base at F5449000

if the system automatically reboots, disable "automatically restart" from the startup and recovery options panel in "advanced/ system properties"

google for the first byte range (0x0000008E in the example above) and/or even better you'll see what device driver is failing (Izx32.sys in above). my hunch is that it is your graphics card that is failing.. so you might see direct x driver or a manufacturer specific one listed.

good luck man, that is a horrible feeling to have to deal with.
Old 06 June 2012   #5
Originally Posted by darkshark: Where would I even begin to look for something like a burst capacitor?

They look like this.


That's just one of many things that could be an issue though. It sounds like hardware to me which is why I suggested looking for physical signs, proper voltages, fans are working, etc. If you're not comfortable working with the components and troubleshooting it might be better to take it to a good computer shop (i.e. not Geek Squad).
Old 06 June 2012   #6
No burst capacitors on the mobo.

Here's my update today

Used only 1 video card at a time, and then tried using NO video cards and running off of the mobo's onboard graphics.

(update today) Completely replaced the motherboard, which was an Asus P8p67 pro, with a P8z77 vpro, brand new. Still same outcome.

10 passes on memtest, 0 errors.

I'm seriously like.....out of things to test. Oh and the stop error is 0x50, which I know usually pertains to RAM, but I've tested it all multiple times, along with a brand new mobo .___.
Old 06 June 2012   #7
Maybe you can try to use on the bare minimum of memory (I don't know what the amount of installed memory is on your config). Let's say install 8GB of RAM (same manufacturer) and try to run the same Max-rendering again. Sometimes if you mix brands of memory or even batches of the same brand can cause strange things to happen in windows (even when memory tests indicate no errors).
So try to install the minimum of ram (preferably of the same batch) and see if you still get the BSOD.

Edit: Just saw you have 16GB, try 8GB or even 4GB to test. To see if its memory related.
Old 06 June 2012   #8
could be ram... but, not always.


maybe a rootkit? i dunno, i'm just grasping at straws now... seems like you did the painful hardware checks.

what about resetting the BIOS to default?

also found this:

no idea if your network drivers could be doing this... not a lot of info regarding it.

Last edited by tswalk : 06 June 2012 at 07:03 AM.
Old 06 June 2012   #9
Thread automatically closed

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.
CGTalk Policy/Legalities
Note that as CGTalk Members, you agree to the terms and conditions of using this website.
Thread Closed share thread

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Society of Digital Artists

Powered by vBulletin
Copyright 2000 - 2006,
Jelsoft Enterprises Ltd.
Minimize Ads
Forum Jump

All times are GMT. The time now is 04:07 PM.

Powered by vBulletin
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.