Windows 10: TwinCAT 3.0 crash when going from run mode to config mode Blue screen

NavinRai1 · Mar 24, 2019

Hi All,

I'm running TwinCAT 3 integrated in visual studio 2013. It crashes as soon I activate the configuration ans put it to to 'RUN' mode. I have searched online and seen that 'TwinCAT 3.0 and “spectre/meltdown”-OS' patch could sove the issue, if so, how do I run the patch. Any other suggestions would be helpful.

Regards,

...

:)

markoanton · Mar 24, 2019

TwinCAT crash when going from run mode to config mode Blue screen - APC_INDEX_MISMATCH

Hi All,

I'm running TwinCAT 3 integrated in visual studio 2013. When going from run mode to config I get blue screen. Following is the dump file.

Loading Dump File [C:\Windows\Minidump\041618-6562-01.dmp]

Loading Dump File [C:\Windows\Minidump\041618-6562-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************

************* Path validation summary **************

Response Time (ms) Location

Response Time (ms) Location

Deferred Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsSRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Symbol search path is: Symbol search path is: SRV*c:\symbols*Symbol information

SRV*c:\symbols*Symbol information

Executable search path is:

Executable search path is:

Windows 10 Kernel Windows 10 Kernel Version 16299Version 16299 MP MP (2 procs) (2 procs) Free x64

Free x64

Product: Product: WinNtWinNt, suite:, suite: TerminalServer TerminalServer SingleUserTS SingleUserTS

Built by: 16299.15.amd64fre.rs3_release.170928-1534

Built by: 16299.15.amd64fre.rs3_release.170928-1534

Machine Name:Machine Name:

Kernel base = 0xfffff802`1dc99000 PsLoadedModuleList = 0xfffff802`1dfff070

Kernel base = 0xfffff802`1dc99000 PsLoadedModuleList = 0xfffff802`1dfff070

Debug session time: Mon Apr 16 09:46:23.116 2018 (UTC + 2:00)

Debug session time: Mon Apr 16 09:46:23.116 2018 (UTC + 2:00)

System Uptime: 0 days 0:08:49.719System Uptime: 0 days 0:08:49.719

Loading Kernel Symbols

Loading Kernel Symbols

..............................................................................................................................

................................................................................................................................

................................................................................................................................

................................

Loading User Symbols

Loading User Symbols

Loading unloaded module list

.Loading unloaded module list

...............................

Unable to deliver callback, Unable to deliver callback, 3131

*******************************************************************************

*******************************************************************************

* *

* *

* Bugcheck Analysis *

* Bugcheck Analysis *

* *

* *

*******************************************************************************

*******************************************************************************

Use Use !analyze -v !analyze -v to get detailed debugging information.

to get detailed debugging information.

BugCheck BugCheck 11, {, {6a101e5c6a101e5c, , 00, , ffffffff, , fffffe0cd702fa80fffffe0cd702fa80}

}

Probably caused by : Probably caused by : ntkrnlmp.exentkrnlmp.exe ( ( nt!KiSystemServiceExitPico+242nt!KiSystemServiceExitPico+242 )

)

Followup:

Followup: MachineOwnerMachineOwner

---------

---------

0: kd> !analyze -v

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

APC_INDEX_MISMATCH (1)

This is a kernel internal error. The most common reason to see this

bugcheck is when a filesystem or a driver has a mismatched number of

calls to disable and re-enable APCs. The key data item is the

Thread->CombinedApcDisable field. This consists of two separate 16-bit

fields, the SpecialApcDisable and the KernelApcDisable. A negative value

of either indicates that a driver has disabled special or normal APCs

(respectively) without re-enabling them; a positive value indicates that

a driver has enabled special or normal APCs (respectively) too many times.

Arguments:

Arg1: 000000006a101e5c, *******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

APC_INDEX_MISMATCH (1)

This is a kernel internal error. The most common reason to see this

bugcheck is when a filesystem or a driver has a mismatched number of

calls to disable and re-enable APCs. The key data item is the

Thread->CombinedApcDisable field. This consists of two separate 16-bit

fields, the SpecialApcDisable and the KernelApcDisable. A negative value

of either indicates that a driver has disabled special or normal APCs

(respectively) without re-enabling them; a positive value indicates that

a driver has enabled special or normal APCs (respectively) too many times.

Arguments:

Arg1: 000000006a101e5c, Address of system call function or worker routine

Arg2: 0000000000000000, Thread->ApcStateIndex

Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable

Arg4: fffffe0cd702fa80, Call type (0 - system call, 1 - worker routine)

Debugging Details:

------------------

Address of system call function or worker routine

Arg2: 0000000000000000, Thread->ApcStateIndex

Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable

Arg4: fffffe0cd702fa80, Call type (0 - system call, 1 - worker routine)

Debugging Details:

------------------

DUMP_CLASS:

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.371 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: HP

SYSTEM_PRODUCT_NAME: HP ProDesk 400 G4 MT

SYSTEM_SKU: Y3A10AV

BIOS_VENDOR: HP

BIOS_VERSION: P03 Ver. 02.15

BIOS_DATE: 01/30/2018

BASEBOARD_MANUFACTURER: HP

BASEBOARD_PRODUCT: 82A1

BASEBOARD_VERSION: KBC Version 06.21

DUMP_TYPE: 2

BUGCHECK_P1: 6a101e5c

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: fffffe0cd702fa80

FAULTING_IP:

+01

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.371 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: HP

SYSTEM_PRODUCT_NAME: HP ProDesk 400 G4 MT

SYSTEM_SKU: Y3A10AV

BIOS_VENDOR: HP

BIOS_VERSION: P03 Ver. 02.15

BIOS_DATE: 01/30/2018

BASEBOARD_MANUFACTURER: HP

BASEBOARD_PRODUCT: 82A1

BASEBOARD_VERSION: KBC Version 06.21

DUMP_TYPE: 2

BUGCHECK_P1: 6a101e5c

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: fffffe0cd702fa80

FAULTING_IP:

+0

00000000`6a101e5c ?? ???

00000000`6a101e5c ?? ???

CPU_COUNT: 2

CPU_MHZ: d50

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x1

PROCESS_NAME: TCATSysSrv.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: MARKOA

ANALYSIS_SESSION_TIME: 04-16-2018 14:35:26.0533

ANALYSIS_VERSION: 10.0.16299.91 amd64fre

LAST_CONTROL_TRANSFER: from fffff8021de20ae9 to fffff8021de0e930

STACK_TEXT:

CPU_COUNT: 2

CPU_MHZ: d50

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x1

PROCESS_NAME: TCATSysSrv.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: MARKOA

ANALYSIS_SESSION_TIME: 04-16-2018 14:35:26.0533

ANALYSIS_VERSION: 10.0.16299.91 amd64fre

LAST_CONTROL_TRANSFER: from fffff8021de20ae9 to fffff8021de0e930

STACK_TEXT:

fffffe0c`d702f848 fffff802`1de20ae9 : 00000000`00000001 00000000`6a101e5c 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx

fffffe0c`d702f850 fffff802`1de20a0e : ffff9e0e`fb35b340 fffffe0c`d702fa80 00000000`02edea68 fffffe0c`d702f9a8 : nt!KiBugCheckDispatch+0x69

fffffe0c`d702f990 00000000`6a101e5c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x242

00000000`02edf368 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6a101e5c

THREAD_SHA1_HASH_MOD_FUNC: 1b1fd012b2a510c586295e696f84a9476c8f91e5

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 79ccfec657f280658f4ce8dad86665e296622bc0

THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b

FOLLOWUP_IP:

nt!KiSystemServiceExitPico+242

fffffe0c`d702f848 fffff802`1de20ae9 : 00000000`00000001 00000000`6a101e5c 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx

fffffe0c`d702f850 fffff802`1de20a0e : ffff9e0e`fb35b340 fffffe0c`d702fa80 00000000`02edea68 fffffe0c`d702f9a8 : nt!KiBugCheckDispatch+0x69

fffffe0c`d702f990 00000000`6a101e5c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x242

00000000`02edf368 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6a101e5c

THREAD_SHA1_HASH_MOD_FUNC: 1b1fd012b2a510c586295e696f84a9476c8f91e5

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 79ccfec657f280658f4ce8dad86665e296622bc0

THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b

FOLLOWUP_IP:

nt!KiSystemServiceExitPico+242

fffff802`1de20a0e 4883ec50 sub rsp,50h

fffff802`1de20a0e 4883ec50 sub rsp,50h

FAULT_INSTR_CODE: 50ec8348

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiSystemServiceExitPico+242

FOLLOWUP_NAME: MachineOwner

MODULE_NAME:

FAULT_INSTR_CODE: 50ec8348

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiSystemServiceExitPico+242

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5abdad89

IMAGE_VERSION: 10.0.16299.371

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 242

FAILURE_BUCKET_ID: 0x1_SysCallNum_1b0007_nt!KiSystemServiceExitPico

BUCKET_ID: 0x1_SysCallNum_1b0007_nt!KiSystemServiceExitPico

PRIMARY_PROBLEM_CLASS: 0x1_SysCallNum_1b0007_nt!KiSystemServiceExitPico

TARGET_TIME: 2018-04-16T07:46:23.000Z

OSBUILD: 16299

OSSERVICEPACK: 371

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-03-30 05:22:49

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.16299.371

ANALYSIS_SESSION_ELAPSED_TIME: cc3

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1_syscallnum_1b0007_nt!kisystemserviceexitpico

FAILURE_ID_HASH: {1d25e8fe-40eb-1b84-9166-c3af30bbaf7e}

Followup: MachineOwner

---------

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5abdad89

IMAGE_VERSION: 10.0.16299.371

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 242

FAILURE_BUCKET_ID: 0x1_SysCallNum_1b0007_nt!KiSystemServiceExitPico

BUCKET_ID: 0x1_SysCallNum_1b0007_nt!KiSystemServiceExitPico

PRIMARY_PROBLEM_CLASS: 0x1_SysCallNum_1b0007_nt!KiSystemServiceExitPico

TARGET_TIME: 2018-04-16T07:46:23.000Z

OSBUILD: 16299

OSSERVICEPACK: 371

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-03-30 05:22:49

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.16299.371

ANALYSIS_SESSION_ELAPSED_TIME: cc3

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1_syscallnum_1b0007_nt!kisystemserviceexitpico

FAILURE_ID_HASH: {1d25e8fe-40eb-1b84-9166-c3af30bbaf7e}

Followup: MachineOwner

---------

Junaid_A · Mar 24, 2019

Blue Screen - Unexpected Kernal mode trap

Hi Anne,

Thank you for writing to Microsoft Community forum.

This issue may occur when your computer lacks sufficient kernel space to process kernel-mode drivers

To have a better clarity on the issue and guide you accordingly, respond to the questions listed below.

What is the make and model of the PC?

Were there any changes made on the computer prior to this issue?

Meanwhile, you may try the troubleshooting steps suggested in the articles listed below and check if it works:

Troubleshoot blue screen errors.

Troubleshoot UNEXPECTED_KERNEL_MODE_TRAP

Bug check: UNEXPECTED_ KERNEL_ MODE_ TRAP

Regards,

Sachin Venkatesh · Mar 24, 2019

Password not accepted in Safe mode

Hi,

Thank you for posting your query on Microsoft Community forum.

Have you tried all the above steps suggested by Sangeeta Sarkar on September 13, 2015.

I would suggest you to provide some information to help you better.

Are you trying to login the Microsoft account or the Local account in safe mode?

Did you try with only safe mode or safe mode with networking?

What is the critical error you are getting?

If you are using Windows 10. To go to safe mode you have to follow the below steps.

If you are able to go to login screen in normal mode try the below steps to go to safe mode with networking.

At the login screen click on the power symbol.

Hold SHIFT + Click Restart.

After restarting your system, select the Troubleshoot option.

Select advanced options under
Troubleshoot screen.

Click on Startup Settings.

Click Restart and follow the onscreen steps to go to
Safe Mode with networking and check if you are able to login.

[*]

Please get back with more information, we will be glad to help you further.

Windows 10: TwinCAT 3.0 crash when going from run mode to config mode Blue screen

TwinCAT 3.0 crash when going from run mode to config mode Blue screen

TwinCAT 3.0 crash when going from run mode to config mode Blue screen

TwinCAT 3.0 crash when going from run mode to config mode Blue screen

TwinCAT 3.0 crash when going from run mode to config mode Blue screen - Similar Threads - TwinCAT crash going

Blue screen when going to sleep mode ntoskrnl.exe+375129

Blue screen when going to sleep mode ntoskrnl.exe+375129

Blank screen when going on safe mode

Blank screen when going on safe mode

Blank screen when going on safe mode

Blue screen trying to run the Bitlocker recovery mode

Blue screen trying to run the Bitlocker recovery mode

Blue screen trying to run the Bitlocker recovery mode

Laptop randomly runs into issues when going into sleep mode

Users found this page by searching for:

twincat 3 windows 10 blue screen

twincat 3 freeze run mode

twincat 3 crashed