Anybody else see this?
Windows Server 2008 RS SP1
SP 2013 Enterprise
ASPI 3.85
Comments: ** Comment from web user: jvossers **
I did some more troubleshooting on this and have some more info.
I removed most of the processing ASPI does from the main ps1 file. I ran it and noticed that the BSOD would not occur when opening the RTF file at the end. I gradually started adding things back in until it started giving me the BSOD. My conclusion is that at least the function InstallSharePoint must have run to get the machine into the state where it can produce these BSOD's. Anything happening before that is not enough to get it into this "please don't open WordPad" state.
Next, I experimented a little with what actions could trigger the actual BSOD.
* Copy RTF file to new file and open with WordPad __crashes__
* Copy RTF file to new file and edit in notepad, remove all contents, save, open with WordPad __crashes__
* Run > "wordpad" __crashes__
* Open Control Panel > Appearance > Fonts __crashes__
Opening the Fonts folder from Control Panel is something I tried after googling around, where I found information suggesting a bad font could be the cause of the BSOD. I wonder if in our case the SP2013 binary install is dropping a naughty font in the fonts folder.
http://www.sevenforums.com/bsod-help-support/36757-firefox-wordpad-cause-bsods-win32-sys.html