1
Vote

BSOD when process loads log in Wordpad

description

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

comments

brianlala wrote Mar 20 at 6: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?

Brian

csyvenky wrote Mar 20 at 11:29 PM

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 at 12: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 at 2: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...?

Brian

codeplex_anykey wrote Apr 4 at 9: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!

Stefan

brianlala wrote Apr 5 at 11:27 AM

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

Brian

csyvenky wrote Apr 5 at 5: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.

brianteare wrote May 1 at 3: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 at 11:34 AM

Hello,
I have also the problem as Stefan.
Horst

CraigHumphrey wrote Tue at 2: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:
Image
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...

Later'ish
Craig

Sign in to add a comment or to set email notifications