3ds Max causes BSOD on launch

[olson]

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.

[darkshark]

Where would I even begin to look for something like a burst capacitor?

[tswalk]

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)
system32 (http://www.techsupportforum.com/forums/#) : 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.

[olson]

Where would I even begin to look for something like a burst capacitor?

They look like this.

http://37prime.files.wordpress.com/2009/07/evga_nvidia_blown_capacitors_1080.jpg

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).

[darkshark]

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 .___.

[Raycat]

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.

[tswalk]

could be ram... but, not always.

http://msdn.microsoft.com/en-us/library/ff559023%28v=VS.85%29.aspx

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?

[edit]
also found this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;976527&sd=rss&spid=14498

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