Window position causes Maxwell Render to Crash (Win7)
Posted: Fri May 07, 2010 7:18 pm
Using Windows 7 Pro 64-Bit with all the latest updates installed. Maxwell Version 2.0.3.0
I had several Instances of Maxwell Render opened, to compare images. While i was moving/resizing the Windows i had redraw errors (Window becoming white) and occasional crashes.
Then came the worst case scenario: Window position on the right side via Windows 7 Window Snapping caused Maxwell Render to crash - but it didnt´t stop here: everytime I restarted MW Render it would instanly crash again. I reinstalled Maxwell and updated to the latest ATI Driver (Version 10-4 on a ATI 4850), but this didn´t help. It would still crash withe the same window position on the right side.
Windows Bugreport (German)
Solution was to change registry entry for Maxwell Fullsize at startup to "true". I´m reporting this so it might help other users, who encounter similar errors.
I had several Instances of Maxwell Render opened, to compare images. While i was moving/resizing the Windows i had redraw errors (Window becoming white) and occasional crashes.
Then came the worst case scenario: Window position on the right side via Windows 7 Window Snapping caused Maxwell Render to crash - but it didnt´t stop here: everytime I restarted MW Render it would instanly crash again. I reinstalled Maxwell and updated to the latest ATI Driver (Version 10-4 on a ATI 4850), but this didn´t help. It would still crash withe the same window position on the right side.
Windows Bugreport (German)
Code: Select all
Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: maxwell.exe
Anwendungsversion: 0.0.0.0
Anwendungszeitstempel: 4bac9e54
Fehlermodulname: maxwell.exe
Fehlermodulversion: 0.0.0.0
Fehlermodulzeitstempel: 4bac9e54
Ausnahmecode: c0000094
Ausnahmeoffset: 00000000001b7120
Betriebsystemversion: 6.1.7600.2.0.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: 2d27
Zusatzinformation 2: 2d2734d8bc7ec10eadc0a210431fe04c
Zusatzinformation 3: ae86
Zusatzinformation 4: ae86d95fdbfaecaf562521cfc2f8a343Solution was to change registry entry for Maxwell Fullsize at startup to "true". I´m reporting this so it might help other users, who encounter similar errors.