This project has moved and is read-only. For the latest updates, please go here.

BSOD when process loads log in Wordpad


I have a reproducible scenario whereby when the ASPI process completes and I press "any key" to complete the process, the logging transcript is loaded into Wordpad. For me (connected over RDP) everytime that happens the system crashes with the blue screen of death and a core dump.

Anybody else see this?

Windows Server 2008 RS SP1
SP 2013 Enterprise
ASPI 3.85

file attachments


brianlala wrote Mar 20, 2013 at 7:05 PM

Dude you are having no luck :-| Can't really be the script though - all it's doing is opening an RTF in Wordpad which I've done tens if not hundreds of times...

Wondering, what's the code displayed in the BSOD?


wrote Mar 21, 2013 at 12:29 AM

csyvenky wrote Mar 21, 2013 at 12:29 AM

Crazy - it happened again. From the looks of the screen-grab its a memory problem.

Very strange that it happens every time the script finishes and Wordpad is called.

ZachMillis wrote Mar 21, 2013 at 1:02 AM

I've had that happen on a few machines as well, using ASPI 3.2 with SP 2013 (I know that script is beta for 2013). Both machines were Server 2008 R2 SP1 with SP 2013 Enterprise. There wasn't anything useful in the event log when it happened to me, but I'm glad to hear I'm not the only one. :)

brianlala wrote Mar 27, 2013 at 3:20 AM

Wow - I just reproduced this. Same platform (Win2008 R2 SP1, SP2013) and nearly the same details on the BSOD. Interesting is that I'm using Hyper-V on Windows 8, while you appear to be using VMware.

Now I wonder if anyone can reproduce this on physical hardware...?


codeplex_anykey wrote Apr 4, 2013 at 10:09 AM

I had the same problem on a server of a client. Also Win2008R2SP1, SP2013 with CU March2013 overlay. Server is running on some VMware server (out of our control). After the black out it comes back with a PING, and it goes down once more and when it comes back it finally works. I have no control over the hypervisor so I cannot get the error on the screen as RDP doesn't give me the error.

Also did some test runs on a private Windows Server 2012 with HyperV with also Windows 2008R2sp1 as SP2013 server, no issues so far. This using the same binary set and similar XML input file.

Hope someone finds the cause!


brianlala wrote Apr 5, 2013 at 12:27 PM

This gets weirder. I actually reproduced the issue after the script was all done. Instead of pressing a key upon script completion to automatically open the log .rtf in Wordpad (as I wanted to avoid a BSOD!) I just closed the PowerShell windows. Then, a few minutes later, I decided I wanted to view the log after all, so I double-clicked the AutoSPInstaller*.rtf file and whammo - BSOD.

So this tells me this likely has nothing to do with the script, and everything to do with Wordpad and opening .rtf files (maybe too large, maybe some formatting it doesn't like?)


csyvenky wrote Apr 5, 2013 at 6:08 PM

It's funny because I have built a new farm on new infrastructure in Australia and have the same issue.

I nearly came to the same conclusion - I was going to look thru the script to see if I could disable Wordpad entirely. Or change the output format to TXT.

wrote Apr 18, 2013 at 4:32 AM

brianteare wrote May 1, 2013 at 4:30 PM

Hi Guys,

Same here, hyper-v hosted Windows 2008 R2. Ran AutoSPInstaller on Dev1, copied the rtf file to another server, opened it there, server rebooted :-)

So this is a word pad issue, imho.

I don't see this on windows server 2012 though.

wuwu wrote May 2, 2013 at 12:34 PM

I have also the problem as Stefan.

CraigHumphrey wrote Jun 18, 2013 at 3:59 AM

Hey Guys,
I'm seeing the same thing with the output from v3.87. Opened the RTF file on my OWA server (so similar patch level, but not exactly the same) Srv2008R2SP1 on VMWare:
Opened the RTF on my desktop (Win7sp1 x86) no problem.
Created a test RTF on my desktop, opened it on the OWA server - no problem.
Copied the content (using WordPad) of the AutoSPInstaller into a new (WordPad) RTF - opened just fine.
Note: the new RTF was 42KB, compared to 73KB for the original AutoSPInstaller generated one. All formatting was lost in the copy&paste.
Opened it in Word on my desktop, saved it out as a new RTF (77K, more formattin added) - opened just fine.

Google not revealing much...


rdcpro wrote Jul 26, 2013 at 12:55 AM

I'm experiencing the same issue. I also get the same BSOD when opening the RTF file, both after an error, and also after a successful installation. But it's not just the RTF file, because after rebooting, I can open the RTF with no problem.

So maybe it has something to do with the way the file was closed or not closed when AutoSPInstaller terminates or completes.

rdcpro wrote Jul 26, 2013 at 12:58 AM

By the way, my VM was originally built on VMWare, then converted to a VHD and is running on HyperV.

Mike Sharp

brianteare wrote Jul 26, 2013 at 8:04 AM

I think it is fairly clear this is an operating system (server 2008) / application issue. Copy the rtf to your desktop, open it there and all is well I suspect :-)

jvossers wrote Aug 15, 2013 at 8:35 PM

I was getting the BSOD too. Before running ASPI, I did a string replace for ".rtf" with ".txt" in the ASPI ps1 file which contains all the functions (which replaces 2 instances). Visually, the log output does not look great in the txt file, but at least it seems to work around the BSOD problem.

jvossers wrote Aug 16, 2013 at 9:34 AM

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.

wrote Aug 16, 2013 at 9:41 AM

jvossers wrote Aug 19, 2013 at 12:14 AM

I have narrowed it down to a specific font.

Delete or move the following file with Powershell or CMD.EXE before opening Wordpad and you will see that you will not get the BSOD.


Move it back to its original location and when you open Wordpad next you will get the BSOD.

At least, this is the behaviour I am seeing on my machine. It would be useful if someone could reproduce this.

wrote Jan 14, 2014 at 3:17 PM

Associated with changeset 106186: Changes in this release:
  • Workaround for issue 19491 (BSOD when log file auto-opens in Wordpad)
  • Better detection of SharePoint 2010 with Service Pack 2 integrated, to allow installation on Windows Server 2012
  • Check for SP2013 before attempting to install Project Server 2013; give warning instead of erroring out if Project Server was requested but no bits were found
  • Improvements to InstallUpdates function for SP2010 SP2 etc., handle language packs and Project 2013 updates better
  • Slight rewrite of AssignCert function for improved handling of different domain name scenarios
  • CreateWebApp now checks for AccessServices provisioning to see if it should grants rights
  • Fixed issue 20474 (always running AddToHosts regardless of true or false)
  • CreateUserProfileServiceApplication now correctly detects all content access accounts (in case of multiple search service apps); also enhanced the granting of rights to the UPSA
  • Fixed hashtable parsing in CreateUPSAsAdmin by changing it to an empty string
  • Added checks for dependent service apps in CreateStateServiceApp and CreateSecureStoreServiceApp functions to make sure they gets provisioned if any service apps that requires them are also being provisioned
  • Improved check for search service account credentials in CreateEnterpriseSearchServiceApp
  • Fixed single quote in CheckForSP1 function
  • AddToHOSTS now adds comment with each entry added for tracking purposes
  • Fixed Add-LocalIntranetURL function per issue 20486
  • Pretty minor syntax updates throughout

wrote Nov 27 at 6:36 PM