• Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.

    Post 16 Update

    Post 17 Warning old domain name stealing credentials

  • Special Server Maintenance

    Just when you think you have everything running some what better...

    You get a message from the Hosting company. Short story they need to move us to a new server. I have been working with them to plan a good date for all concerned. Here is what we have come up with as a schedule.

    1. November 4th 17:00 -5UTC shut off the forums and start backup proceedures. During this time there will be no access to the forums or the Resource Section.
    2. November 5th Continue with Backups and download same until complete.
    3. November 6th 7:00 turn over server to hosting company to move system to new server
    4. November 7th - 8th restore backups and upgrade forum software.

    If all goes well we should be back online on November 8th.

    To keep you updated we will post updates on AVSIM forums.

    Thank you for your support.

Windows 10 Update and 3D Studio Max 2015 Train Wreck

Follow up.

After a few days and quite a few hours of thrashing and flogging through the various possible causes of the memory leak, I've probably isolated the cause.

When Max seizes up it becomes necessary to use Task Manager to shut down the program. I get a blue screen error message saying...

IRQL not less or equal.

It looks like a have a damaged driver...somewhere, even though I have taken the time to check and update all of my hardware and software drivers. So...looks like a complete re-install is going to be the only cure.

Hope this new data helps others avoid any problems on their systems. :encouragement:
 
Win 10 usually provides the faulty driver dll's name on the BSOD screen, so with a quick web search for the error message, driver dll filename and "Windows 10", you should be able to get to the bottom of it.

A complete reinstall should be the last resort. You don't disassemble your entire car because a flat tire either, do you?

I have a hunch that it's maybe the driver for your Intel (wireless) network chip (if you have one) as I had both my old Thinkpad and brand new HP notebook throw a BSOD on me after upgrading to Win 10's 1602 version whenever I've used WLAN for a prolonged time. According to a web search, it seems to be a fairly well known issue to boot. New drivers for the (W)LAN chip from your computer's manufacturer or Intel's website should fix this. They might have done for me, but I still need to test this some more.
 
Back
Top