Share via

Error UNEXPECTED_KERNEL_MODE_TRAP ntoskrnl.exe

Anonymous
2018-04-14T14:59:42+00:00

Hello, can anyone help me?

At least once a week at least my notebook stops and shows the blue screen with the UNEXPECTED_KERNEL_MODE_TRAP error . I've turned the internet around for help and I do not know what else to do. It is absolutely everything updated, I use SSD and HD and they are also ok.

My specs:

   ASUS K45A

Microsoft Windows 10 Professional (x64) Build 16299.371 (1709/RS3) 

Processor Name: Intel Core i5-3210M 

Original Processor Frequency [MHz]:

2500 

SSD

Serial ATA 6Gb/s @ 6Gb/s 

Drive Controller:

Serial ATA 3Gb/s @ 3Gb/s 

Drive Model:

Hitachi HTS547575A9E384 

DUMP:

https://1drv.ms/u/s!AlW5hYm1QrK3g5VpSl0VwRJttJiqpQ

This is the resume of the DUMP:

041418-7046-01.dmp 14/04/2018 08:32:00 UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 0000000000000008 fffff80203867e50 ffff938c4cf81fa0 fffff802016ca771 ntoskrnl.exe ntoskrnl.exe+175930 x64 ntoskrnl.exe+175930

And this is with a red line:

ntoskrnl.exe ntoskrnl.exe+bb771 fffff8020160f000 fffff80201ee4000 0x008d5000 0x5abdad89 30/03/2018 00:22:49

Thanks a LOT if anyone can help me :(

Windows for home | Windows 10 | Settings

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2018-04-14T15:48:46+00:00

The driver that appears to cause the crash is the wsddin64.sys :

BugCheck 7F, {8, fffff80203867e50, ffff938c4cf81fa0, fffff802016ca771}

*** WARNING: Unable to verify timestamp for wsddin64.sys

*** ERROR: Module load completed but symbols could not be loaded for wsddin64.sys

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+2f4 )

The wsddin64.sys appears to be a component of Diebold Warsaw which may be a security plugin from a bank.

To stop the error you could try updating Diebold Warsaw but you may have to uninstall the program.

You could contact the bank on this issue.

Was this answer helpful?

2 people found this answer helpful.
0 comments No comments

Answer accepted by question author

Anonymous
2018-04-17T19:07:20+00:00

You're welcome.

I use WinDbg (Windows Debugger) - there is a good tutorial in the following link:

https://www.tenforums.com/tutorials/5558-windbg-basics-debugging-crash-dumps-windows-10-a.html 

The WinDbg Preview from the Microsoft Store is also very good:

https://www.microsoft.com/en-us/store/p/windbg-preview/9pgjgd53tn86

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

3 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-04-17T22:17:59+00:00

    You're welcome.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-04-17T22:12:50+00:00

    Great!

    Thanks a lot auggy! :D

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-04-17T10:21:46+00:00

    Thanks a lot for the tip :)

    I've updated some drivers (sound, keyboard) and nothing of the blue screen yet.

    BTW: how did you discovered that? hehe

    Thanks a lot :)

    Was this answer helpful?

    0 comments No comments