[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death

Thu, 25 Sep 2014 14:45:38 -0700

We've been running into this issue since at least March 2013. One out of our 5 nodes seems to blue screen every few days. I always figured it was something in Java or driver issue since I didn't think it was possible for a userspace program to crash the whole machine, so I just worked around it.

We're currently running Jenkins LTS 1.565.2 on a Linux master with Windows 7 64-bit slaves.

I have a complete crash dump (8.3 GB) from a BSOD today. Here's it's bugcheck analysis. I'm not familiar enough with Windows internals to really dig much deeper, but let me know if I can help debug further.

Kernel Complete Dump File: Full address space is available

Symbol search path is: srv*D:\MSSymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xfffff800`03049000 PsLoadedModuleList = 0xfffff800`0328c6d0
Debug session time: Thu Sep 25 13:58:37.568 2014 (UTC - 5:00)
System Uptime: 2 days 1:04:26.686
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
.......................................................
Loading unloaded module list
........Unable to enumerate user-mode unloaded modules, NTSTATUS 0xC0000147
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800aa49060, fffffa800aa49340, fffff800033c50d0}

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for winp.x64.FEF9CB80B43534DCA303AC36686258E8.dll - 
Probably caused by : _

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800aa49060, Terminating object
Arg3: fffffa800aa49340, Process image file name
Arg4: fffff800033c50d0, Explanatory message (ascii)

Debugging Details:
------------------


PROCESS_OBJECT: fffffa800aa49060

IMAGE_NAME:  _

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: _

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  java.exe

BUGCHECK_STR:  0xF4_java.exe

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000344cd92 to fffff800030beb80

STACK_TEXT:  
fffff880`072b89c8 fffff800`0344cd92 : 00000000`000000f4 00000000`00000003 fffffa80`0aa49060 fffffa80`0aa49340 : nt!KeBugCheckEx
fffff880`072b89d0 fffff800`033f91db : ffffffff`ffffffff fffffa80`10987b50 fffffa80`0aa49060 fffffa80`0a3ccb30 : nt!PspCatchCriticalBreak+0x92
fffff880`072b8a10 fffff800`03378ec4 : ffffffff`ffffffff 00000000`00000001 fffffa80`0aa49060 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17476
fffff880`072b8a60 fffff800`030bde13 : fffffa80`0aa49060 00000000`ffffffff fffffa80`10987b50 00000000`00000000 : nt!NtTerminateProcess+0xf4
fffff880`072b8ae0 00000000`770c157a : 000007fe`fd35402f 00000000`00000000 00000000`00000000 00000000`12c2ec30 : nt!KiSystemServiceCopyEnd+0x13
00000000`12c2e998 000007fe`fd35402f : 00000000`00000000 00000000`00000000 00000000`12c2ec30 00000000`00000ab0 : ntdll!NtTerminateProcess+0xa
00000000`12c2e9a0 000007fe`fa3c193c : 00000000`0000075c 00000000`00000001 00000000`00000000 00000000`0000075c : KERNELBASE!TerminateProcess+0x2f
00000000`12c2e9d0 00000000`0000075c : 00000000`00000001 00000000`00000000 00000000`0000075c 00000000`0052c290 : winp_x64_FEF9CB80B43534DCA303AC36686258E8!Java_org_jvnet_winp_Native_noop+0x178
00000000`12c2e9d8 00000000`00000001 : 00000000`00000000 00000000`0000075c 00000000`0052c290 000007fe`fa3c1a40 : 0x75c
00000000`12c2e9e0 00000000`00000000 : 00000000`0000075c 00000000`0052c290 000007fe`fa3c1a40 00000000`000007f0 : 0x1


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_java.exe_IMAGE__

BUCKET_ID:  X64_0xF4_java.exe_IMAGE__

Followup: MachineOwner
---------
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to