timja / jenkins-gh-issues-poc-06-18

0 stars 0 forks source link

[JENKINS-24453] Jenkins server got blue screen to death #5432

Closed timja closed 7 years ago

timja commented 10 years ago

Jenkins Server get blue screen to death crash about twice a day. After sending the dump to microsoft, it turns out there The Java related binary D:\Jenkins_CI\war\WEB-INF\lib\winp.x64.35A3F35D2ED629A6CEC5B41DD1D280C3.dll has called to Terminate the csrss.exe and csrss.exe is a critical process since it was called to Terminate this process the machine Bug Checked.
What is CSRSS.EXE?
This is the user-mode portion of the Win32 subsystem (with Win32.sys being the kernel-mode portion). Csrss stands for client/server run-time subsystem and is an essential subsystem that must be running at all times. Csrss is responsible for console windows, creating and/or deleting threads, and some parts of the 16-bit virtual MS-DOS environment


Originally reported by sharon_xia, imported from: Jenkins server got blue screen to death
  • status: Resolved
  • priority: Major
  • resolution: Fixed
  • resolved: 2017-03-08T13:59:17+00:00
  • imported: 2022/01/10
timja commented 10 years ago

sharon_xia:

System Properties
Name ↓ Value
awt.toolkit sun.awt.windows.WToolkit
executable-war D:\Jenkins_CI\jenkins.war
file.encoding Cp1252
file.encoding.pkg sun.io
file.separator \
hudson.diyChunking true
hudson.lifecycle hudson.lifecycle.WindowsServiceLifecycle
java.awt.graphicsenv sun.awt.Win32GraphicsEnvironment
java.awt.headless true
java.awt.printerjob sun.awt.windows.WPrinterJob
java.class.path D:\Jenkins_CI\jenkins.war
java.class.version 51.0
java.endorsed.dirs C:\Program Files\Java\jre7\lib\endorsed
java.ext.dirs C:\Program Files\Java\jre7\lib\ext;C:\Windows\Sun\Java\lib\ext
java.home C:\Program Files\Java\jre7
java.io.tmpdir C:\Users\ADMINI~1\AppData\Local\Temp\
java.library.path C:\Program Files\Java\jre7\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Java\jre7\bin;C:\Python27;C:\Program Files (x86)\Git\bin;.
java.runtime.name Java(TM) SE Runtime Environment
java.runtime.version 1.7.0_60-b19
java.specification.name Java Platform API Specification
java.specification.vendor Oracle Corporation
java.specification.version 1.7
java.vendor Oracle Corporation
java.vendor.url http://java.oracle.com/
java.vendor.url.bug http://bugreport.sun.com/bugreport/
java.version 1.7.0_60
java.vm.info mixed mode
java.vm.name Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.name Java Virtual Machine Specification
java.vm.specification.vendor Oracle Corporation
java.vm.specification.version 1.7
java.vm.vendor Oracle Corporation
java.vm.version 24.60-b09
javamelody.analytics-id UA-1335263-7
javamelody.gzip-compression-disabled true
javamelody.http-transform-pattern /\d+/|/site/.|avadoc/.|/ws/.|obertura/.|estReport/.|iolations/file/.|/user/.|/static/\w/
javamelody.no-database true
javamelody.storage-directory /D:\Jenkins_CI\monitoring
javamelody.system-actions-enabled true
line.separator
mail.smtp.sendpartial true
mail.smtps.sendpartial true
os.arch amd64
os.name Windows Server 2008 R2
os.version 6.1
path.separator ;
pid 1340
sun.arch.data.model 64
sun.awt.enableExtraMouseButtons true
sun.boot.class.path C:\Program Files\Java\jre7\lib\resources.jar;C:\Program Files\Java\jre7\lib\rt.jar;C:\Program Files\Java\jre7\lib\sunrsasign.jar;C:\Program Files\Java\jre7\lib\jsse.jar;C:\Program Files\Java\jre7\lib\jce.jar;C:\Program Files\Java\jre7\lib\charsets.jar;C:\Program Files\Java\jre7\lib\jfr.jar;C:\Program Files\Java\jre7\classes
sun.boot.library.path C:\Program Files\Java\jre7\bin
sun.cpu.endian little
sun.cpu.isalist amd64
sun.desktop windows
sun.io.unicode.encoding UnicodeLittle
sun.java.command D:\Jenkins_CI\jenkins.war --httpPort=8080 --httpsPort=443 --httpsKeyStore=D:\Jenkins_CI\jre\bin\jenkins.jks --httpsKeyStorePassword=******
sun.java.launcher SUN_STANDARD
sun.jnu.encoding Cp1252
sun.management.compiler HotSpot 64-Bit Tiered Compilers
sun.os.patch.level Service Pack 1
svnkit.http.methods Digest,Basic,NTLM,Negotiate
svnkit.ssh2.persistent false
svnkit.symlinks false
user.country US
user.dir D:\Jenkins_CI
user.home C:\Users\Administrator
user.language en
user.name Administrator
user.script
user.timezone America/New_York
user.variant
Environment Variables
Name ↓ Value
ALLUSERSPROFILE C:\ProgramData
APPDATA C:\Users\Administrator\AppData\Roaming
BASE D:\Jenkins_CI
CommonProgramFiles C:\Program Files\Common Files
CommonProgramFiles(x86) C:\Program Files (x86)\Common Files
CommonProgramW6432 C:\Program Files\Common Files
COMPUTERNAME WIN2K8-R2-0
ComSpec C:\Windows\system32\cmd.exe
FP_NO_HOST_CHECK NO
JAVA_HOME C:\Program Files (x86)\Java\jre7\bin
JENKINS_HOME D:\Jenkins_CI
LOCALAPPDATA C:\Users\Administrator\AppData\Local
NUMBER_OF_PROCESSORS 12
OS Windows_NT
Path C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Java\jre7\bin;C:\Python27;C:\Program Files (x86)\Git\bin
PATHEXT .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PROCESSOR_ARCHITECTURE AMD64
PROCESSOR_IDENTIFIER Intel64 Family 6 Model 44 Stepping 2, GenuineIntel
PROCESSOR_LEVEL 6
PROCESSOR_REVISION 2c02
ProgramData C:\ProgramData
ProgramFiles C:\Program Files
ProgramFiles(x86) C:\Program Files (x86)
ProgramW6432 C:\Program Files
PSModulePath C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
PUBLIC C:\Users\Public
SystemDrive C:
SystemRoot C:\Windows
TEMP C:\Users\ADMINI~1\AppData\Local\Temp
TMP C:\Users\ADMINI~1\AppData\Local\Temp
USERDOMAIN WIN2K8-R2-0
USERNAME Administrator
USERPROFILE C:\Users\Administrator
windir C:\Windows
windows_tracing_flags 3
windows_tracing_logfile C:\BVTBin\Tests\installpackage\csilogfile.log
Plugins
Name ↓ Version Enabled Pinned
active-directory 1.22 true false
ant 1.2 true false
antisamy-markup-formatter 1.0 true false
artifactory 1.1.0 false false
async-http-client 1.7.8 true false
backup 1.6 true false
build-name-setter 1.0 true false
build-timeout 1.12.2 true false
buildgraph-view 1.1 true false
cloudbees-credentials 3.2 false false
cloudbees-deployer-plugin 4.3 false false
cloudbees-plugin-gateway 4.1 false false
cloudbees-registration 3.11 false false
cloudbees-wasted-minutes-tracker 3.5 false false
clover 3.0.2 false false
cobertura 1.9.3 true false
conditional-buildstep 1.3.3 true false
copy-to-slave 1.2.1 true false
copyartifact 1.14 true false
coverity 1.2.7 true false
cppcheck 1.14 true false
credentials 1.14 true true
cron_column 1.003 true false
cvs 2.11 true false
dashboard-view 2.0 true false
dependencyanalyzer 0.6 true false
deployed-on-column 1.7 true false
disk-usage 0.21 true false
downstream-buildview 1.8 true false
downstream-ext 1.6 true false
doxygen 0.6 true false
email-ext 2.38.1 true false
emotional-hudson 1.2 false false
envinject 1.89 true false
extended-choice-parameter 0.4 true false
external-monitor-job 1.2 true false
files-found-trigger 1.1.3 true false
flow 1.2 true false
gallio 1.6 true false
gcal 0.3 false false
git 2.2.1 true false
git-client 1.9.1 true false
greenballs 1.10 true false
groovy 1.4 true false
htmlpublisher 1.3 true false
javadoc 1.1 true false
jenkins-multijob-plugin 1.10 true false
jenkinswalldisplay 0.5.9 true false
job-dsl 1.16 true false
jobConfigHistory 1.5 true false
jobtype-column 1.0 false false
join 1.9 true false
ldap 1.10.2 true true
locks-and-latches 0.6 true false
log-parser 1.0.4 false false
mailer 1.6 true false
matrix-auth 1.1 true false
maven-plugin 2.1 true false
monitoring 1.43.0 true false
multiple-scms 0.3 true false
nodenamecolumn 1.1 true false
nunit 0.15 true false
pam-auth 1.1 true false
parameterized-trigger 2.12 true false
platformlabeler 1.1 true false
plot 1.7 true false
postbuild-task 1.8 true false
PrioritySorter 1.1 true false
rebuild 1.14 true false
regexemail 0.3 true false
regression-report-plugin 1.1 true false
run-condition 1.0 true false
scm-api 0.2 true false
screenshot 1.1 true false
sectioned-view 1.12 true false
sidebar-link 1.5 true false
sonar 2.1 true false
sonargraph-plugin 1.2 true false
sounds 0.2 false false
speaks 0.1.1 false false
ssh-credentials 1.7.1 true true
ssh-slaves 0.14 true true
status-view 1.0 true false
statusmonitor 1.2 true false
subversion 1.23 true true
svn-release-mgr 1.2 true false
svn-tag 1.14 true false
test-stability 1.0 true false
testInProgress 1.1 true false
testlink 2.3.1 true false
timestamper 1.2.2 true false
token-macro 1.10 true false
trac 1.10 true false
translation 1.10 true false
valgrind 0.20 true false
violations 0.7.15-SNAPSHOT (private-01/22/2014 20:25-tanakd1) true false
vsphere-cloud 1.1.10 false false
windows-slaves 1.0 true false
xunit 1.80 false false
Thread Dumps

Visit this page for master and slave thread dumps.
Help us localize this page

timja commented 10 years ago

danielbeck:

Please specify your Jenkins version.

timja commented 10 years ago

danielbeck:

Also, it helps if you're not running Jenkins as Local System or a similarly privileged user.

timja commented 10 years ago

sharon_xia:

Jenkins Version: Jenkins ver. 1.554.3

timja commented 10 years ago

sharon_xia:

Actually we are running Jenkins as Local System account "Administrator", does it matter? Will this trigger this issue?

timja commented 10 years ago

sharon_xia:

Do you mean if we do not run it as Local System then we can get more debugging information or it will trigger this issue? For now I have to move the winp.x64.35A3F35D2ED629A6CEC5B41DD1D280C3.dll out of the WEN-INF/lib folder, however I am not sure what plugin or what function of jenkins will rely on it

timja commented 10 years ago

danielbeck:

If you run Jenkins as an unprivileged user it doesn't get to kill csrss, so yes, that should be a workaround.

winp is used as a process killer, usually however only for processes that are started in your builds. This is designed as regular "clean up" after a build finishes.

timja commented 10 years ago

sharon_xia:

However when I installed the newest LTS version of jenkins it does not have this dll in it. Do you know which plugin/version might use it?
Does it work if I upgrade my jenkins to the latest one 1.556.1?

Also, By default the jenkins will run as Local System and we didn't have this issue before for several years. Why it turns out only recently?

timja commented 10 years ago

danielbeck:

winp is used by Jenkins core, only indirectly by plugins.

There have been a few changes to winp/process killing recently. As I don't use Windows I cannot say for sure what the current status is, generally, killing processes has always been a bit brittle/prone to error. In this case, the fix for JENKINS-22685 comes to mind as a potential candidate.

timja commented 10 years ago

sharon_xia:

Does that mean the latest 1.556.1 still has this issue? Is it OK if I remove winp.x64.35A3F35D2ED629A6CEC5B41DD1D280C3.dll from the WEB-INF/lib folder?

timja commented 10 years ago

oleg_nenashev:

@sharon

> Does that mean the latest 1.556.1 still has this issue?

Most probably, the answer is yes.
BTW, I cannot find any similar issues in Jenkins JIRA, hence I suppose that the issue does not appear on every Windows installation.
Probably, it is somehow related to your system configurations or jobs running on the master node (they have Administrator privileges as well)

> Is it OK if I remove winp.x64.35A3F35D2ED629A6CEC5B41DD1D280C3.dll from the WEB-INF/lib folder?

No. You'll just corrupt the Jenkins installation with the unpredictable further behavior

timja commented 10 years ago

sharon_xia:

No we did almost all of the tasks on slave jobs and the only job on master does not even run when this issue happen and does not have progress killing related command.

I believe this might problably related to the last two LFS version. We plan to do a downgrade to 1.532.3 next Monday(we stayed on this version for months and didn't see this issue) to check this issue will be gone or not. Currently even if I delete this dll, it will be generated again automatically. And I don't find a hint which job might trigger it yet.

timja commented 10 years ago

sharon_xia:

Still see this issue on Jenkins ver. 1.532.3

timja commented 10 years ago

sharon_xia:

Could you please let me know how to run a normal user(not administrator)run jenkins? I followed the guide but it failed: http://technet.microsoft.com/en-us/library/cc787533%28v=WS.10%29.aspx

Currently this crash issue happens more than once a day...

timja commented 10 years ago

sharon_xia:

I took a look at the windows dump file, the blue screen is caused by java.exe which called jenkins.

GetPointerFromAddress: unable to read from fffff800018be000
PROCESS fffffa804b96db30
SessionId: none Cid: 053c Peb: 7fffffd5000 ParentCid: 04f8
DirBase: 82c93e000 ObjectTable: fffff8a001823860 HandleCount:
Image: java.exe
VadRoot fffffa804bdb6680 Vads 972 Clone 0 Private 744164. Modified 258616. Locked 58.
DeviceMap fffff8a0019d4cc0
Token fffff8a001c0da30
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
fffff78000000000: Unable to get shared data
ElapsedTime 00:00:00.000
UserTime 00:00:00.000
KernelTime00:00:00.000
QuotaPoolUsage[PagedPool] 0
QuotaPoolUsage[NonPagedPool] 0
Working Set Sizes (now,min,max) (746794, 50, 345) (2987176KB, 200KB, 1380KB)
PeakWorkingSetSize747257
VirtualSize 20052 Mb
PeakVirtualSize 20075 Mb
PageFaultCount 1577231
MemoryPriority BACKGROUND
BasePriority 8
CommitCharge 1015778

timja commented 10 years ago

sharon_xia:

This issue is not seen after upgrade jenkins to 1.565.1.
But we are seeing download issue on 1.565.1. See https://issues.jenkins-ci.org/browse/JENKINS-23868?focusedCommentId=211163#comment-211163

timja commented 9 years ago

scm_issue_link:

Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
changelog.html
http://jenkins-ci.org/commit/jenkins/d000cd65a7b0152334532bc7abd148095d5cee09
Log:
[FIXED JENKINS-24453]

The actual fix is made in 040b7d4047b324f17c0971f2511f954eb173fa23
through winp.

timja commented 9 years ago

kohsuke:

csrss.exe wouldn't have the right environment variables, so it should never match the killing criteria.

In 1.583 we made a change to winp so that at least it won't terminate a critical process, but we'll likely still have to figure out why that process was selected as a target of killing.

timja commented 9 years ago

dogfood:

Integrated in jenkins_main_trunk #3700
[FIXED JENKINS-24453] (Revision d000cd65a7b0152334532bc7abd148095d5cee09)

Result = SUCCESS
kohsuke : d000cd65a7b0152334532bc7abd148095d5cee09
Files :

timja commented 9 years ago

vynce:

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
---------
timja commented 9 years ago

scm_issue_link:

Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
core/pom.xml
http://jenkins-ci.org/commit/jenkins/21fb398bfa7068f6f72154763bdbb09baddf313d
Log:
JENKINS-24453[ZD-20503] Incorporated a newer version of winp.

This version checks the critical flag of the process, as killing such a
process results in BSoD.

(cherry picked from commit 040b7d4047b324f17c0971f2511f954eb173fa23)

Conflicts:
changelog.html

Compare: https://github.com/jenkinsci/jenkins/compare/b105627b7357^...21fb398bfa70

timja commented 8 years ago

dogfood:

Integrated in jenkins_main_trunk #4292
JENKINS-24453[ZD-20503] Incorporated a newer version of winp. (Revision 21fb398bfa7068f6f72154763bdbb09baddf313d)

Result = UNSTABLE
ogondza : 21fb398bfa7068f6f72154763bdbb09baddf313d
Files :

timja commented 7 years ago

p55p:

Hello, we are facing similar issue as described in this thread. Based on comments I thought the issue was solved in version 1.580.1 but we are running version 2.19.1 and we got the strange behavior also there.
One of our Windows boxes resulted in BSOD. When we inspected memory dump we found following details.

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

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 7601.23572.amd64fre.win7sp1_ldr.161011-0600

SYSTEM_MANUFACTURER: VMware, Inc.

VIRTUAL_MACHINE: VMware

SYSTEM_PRODUCT_NAME: VMware Virtual Platform

SYSTEM_VERSION: None

BIOS_VENDOR: Phoenix Technologies LTD

BIOS_VERSION: 6.00

BIOS_DATE: 09/17/2015

BASEBOARD_MANUFACTURER: Intel Corporation

BASEBOARD_PRODUCT: 440BX Desktop Reference Platform

BASEBOARD_VERSION: None

DUMP_TYPE: 1

BUGCHECK_P1: 3

BUGCHECK_P2: fffffa8182e4c2a0

BUGCHECK_P3: fffffa8182e4c580

BUGCHECK_P4: fffff80001994b70

PROCESS_NAME: csrss.exe

CRITICAL_PROCESS: csrss.exe

IMAGE_NAME: csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000

EXCEPTION_CODE: (HRESULT) 0x855ee060 (2237587552) -

ERROR_CODE: (NTSTATUS) 0x855ee060 -

CPU_COUNT: 4

CPU_MHZ: 960

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: f

CPU_STEPPING: 1

CPU_MICROCODE: 6,f,1,0 (F,M,S,R) SIG: 428'00000000 (cache) 428'00000000 (init)

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xF4

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: NVPC100

ANALYSIS_SESSION_TIME: 03-01-2017 12:25:49.0246

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

STACK_TEXT:
fffff880`069abb18 fffff800`01a1e852 : 00000000`000000f4 00000000`00000003 fffffa81`82e4c2a0 fffffa81`82e4c580 : nt!KeBugCheckEx
fffff880`069abb20 fffff800`019dc09b : 00000000`00000001 fffffa81`855ee060 fffffa81`82e4c2a0 fffffa81`83d68b01 : nt!PspCatchCriticalBreak+0x92
fffff880`069abb60 fffff800`01945454 : 00000000`00000001 00000000`00000328 fffffa81`82e4c2a0 fffffa81`00000008 : nt! ?? ::NNGAKEGL::`string'+0x27296
fffff880`069abbb0 fffff800`01689693 : 00000000`00000328 fffffa81`855ee060 fffffa81`82e4c2a0 00000000`00000328 : nt!NtTerminateProcess+0x284
fffff880`069abc20 00000000`776cbffa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`1ac8e008 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776cbffa

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_TERMINATED_BY_jenkins-slave.exe_855ee060

BUCKET_ID: X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_TERMINATED_BY_jenkins-slave.exe_855ee060

PRIMARY_PROBLEM_CLASS: X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_TERMINATED_BY_jenkins-slave.exe_855ee060

TARGET_TIME: 2017-03-01T09:52:59.000Z

OSBUILD: 7601

OSSERVICEPACK: 1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 400

PRODUCT_TYPE: 3

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

OSEDITION: Windows 7 Server (Service Pack 1) TerminalServer DataCenter SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-10-11 16:57:55

BUILDDATESTAMP_STR: 161011-0600

BUILDLAB_STR: win7sp1_ldr

BUILDOSVER_STR: 6.1.7601.23572.amd64fre.win7sp1_ldr.161011-0600

ANALYSIS_SESSION_ELAPSED_TIME: 9e0

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0xf4_csrss.exe_bugcheck_critical_process_terminated_by_jenkins-slave.exe_855ee060

FAILURE_ID_HASH:

{795c17b0-7869-c608-f0a3-7708c7ee022c}

Followup: MachineOwner

timja commented 7 years ago

oleg_nenashev:

Yes, there is a known issue with WinP: https://github.com/kohsuke/winp/issues/22 . This fix has been released in winp-1.24 and then integrated into Jenkins 2.34: https://github.com/jenkinsci/jenkins/commit/63c2f6c5d7d154a3a0f58c54f04f9b1a25ea5385.

According to the code the fix has been also backported to Jenkins 2.32.1 though changelogs do not say it explicitly. I will make sure that changelogs get updated.

The recommendation is to update the core to the latest LTS

timja commented 7 years ago

p55p:

Thank you Oleg for your quick response. We will do the upgrade and will let you know if the issue reoccur.

timja commented 7 years ago

scm_issue_link:

Code changed in jenkins
User: Oleg Nenashev
Path:
content/_data/changelogs/lts.yml
content/_partials/changelog-weekly.html
http://jenkins-ci.org/commit/jenkins.io/1e74ef665f37621c5d7fda4c0f5a42e3e4462a59
Log:
JENKINS-24453 - Noting fix in Jenkins 2.34 and 2.32.1

It was a missing fix, since I didn't notice there is a Jenkins JIRA issue for it.
This PR updates the Weekly release entry and also adds the missing entry for the Stable release

timja commented 7 years ago

scm_issue_link:

Code changed in jenkins
User: R. Tyler Croy
Path:
content/_data/changelogs/lts.yml
content/_partials/changelog-weekly.html
http://jenkins-ci.org/commit/jenkins.io/89b2c800c392195aca397baac4ceb91af08ad7f4
Log:
Merge pull request #723 from oleg-nenashev/changelog/JENKINS-24453

JENKINS-24453 - Noting fix in Jenkins 2.34 and 2.32.1

Compare: https://github.com/jenkins-infra/jenkins.io/compare/c49bb48b33bc...89b2c800c392

timja commented 2 years ago

[Originally duplicated by: JENKINS-36378]