Windows 8 and 8.1 Forums

Windows 8.1 KERNEL_SECURITY_CHECK_FAILURE - Schwonkey668

  1. #1

    Posts : 4
    Windows 8.1

    Windows 8.1 KERNEL_SECURITY_CHECK_FAILURE - Schwonkey668

    Hi! This is my first post and my first time posting a BSOD to a website so please bare with me. I really have no idea what I am doing.

    I have been getting the BSOD KERNEL_SECURITY_CHECK_FAILURE off and on for about a month now. I know it started a month ago but I have only suspected it happening sometimes at night because my system would be rebooted in the morning and I know windows was not doing udpates EVERY night. I finally caught it in the act today just as I sat down so I know it is still going on.

    This is the BSOD zip file as done by instructions from another thread. I hope I did it right. Please let me know what else I should do. Thank you for your help!!! (I hope its even ok to ask but it felt like the right thing to do.)

      My System SpecsSystem Spec

  2. #2

    Posts : 660
    windows 8.1

    All your 9 Dumpfiles are aBugCheck 139, {3, ffffd00021db5400, ffffd00021db5358, 0} Probably caused by : xtouch.sys ( xtouch+4d86 ).

    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck 139, {3, ffffd00021db5400, ffffd00021db5358, 0}
    *** WARNING: Unable to verify timestamp for xtouch.sys
    *** ERROR: Module load completed but symbols could not be loaded for xtouch.sys
    Probably caused by : xtouch.sys ( xtouch+4d86 )
    Followup: MachineOwner
    2: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    A kernel component has corrupted a critical data structure.  The corruption
    could potentially allow a malicious user to gain control of this machine.
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: ffffd00021db5400, Address of the trap frame for the exception that caused the bugcheck
    Arg3: ffffd00021db5358, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    Debugging Details:
    TRAP_FRAME:  ffffd00021db5400 -- (.trap 0xffffd00021db5400)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffe0000316b8e8 rbx=0000000000000000 rcx=0000000000000003
    rdx=ffffe00003154a20 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff803f9013c5b rsp=ffffd00021db5590 rbp=0000000000000000
     r8=ffffe0000316b8e8  r9=0000000000000001 r10=ffffe00003154880
    r11=fffff78000000008 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe cy
    nt! ?? ::FNODOBFM::`string'+0x2aabb:
    fffff803`f9013c5b cd29            int     29h
    Resetting default scope
    EXCEPTION_RECORD:  ffffd00021db5358 -- (.exr 0xffffd00021db5358)
    ExceptionAddress: fffff803f9013c5b (nt! ?? ::FNODOBFM::`string'+0x000000000002aabb)
       ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
      ExceptionFlags: 00000001
    NumberParameters: 1
       Parameter[0]: 0000000000000003
    BUGCHECK_STR:  0x139
    PROCESS_NAME:  System
    ERROR_CODE: (NTSTATUS) 0xc0000409 - Er is een bufferoverschrijdingsfout opgetreden voor stack-buffer in deze toepassing. Via deze overschrijdingsfout kan een kwaadwillige gebruiker de controle over deze toepassing verkrijgen.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - Er is een bufferoverschrijdingsfout opgetreden voor stack-buffer in deze toepassing. Via deze overschrijdingsfout kan een kwaadwillige gebruiker de controle over deze toepassing verkrijgen.
    EXCEPTION_PARAMETER1:  0000000000000003
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER:  from fffff803f8fe47e9 to fffff803f8fd8ca0
    ffffd000`21db50d8 fffff803`f8fe47e9 : 00000000`00000139 00000000`00000003 ffffd000`21db5400 ffffd000`21db5358 : nt!KeBugCheckEx
    ffffd000`21db50e0 fffff803`f8fe4b10 : ffffd000`21db5380 fffff800`00353feb 00000000`00000000 fffff800`003158bb : nt!KiBugCheckDispatch+0x69
    ffffd000`21db5220 fffff803`f8fe3d34 : fffff800`02b51d01 ffffd000`21db5ae0 ffffd000`21db0000 ffffe000`09b325b0 : nt!KiFastFailDispatch+0xd0
    ffffd000`21db5400 fffff803`f9013c5b : ffffd000`201e6180 00000000`00000000 ffffd000`201e6180 fffff803`f8fdbbaf : nt!KiRaiseSecurityCheckFailure+0xf4
    ffffd000`21db5590 fffff800`04514d86 : ffffe000`00000000 ffffe000`00000000 00000000`00000000 ffffe000`03154880 : nt! ?? ::FNODOBFM::`string'+0x2aabb
    ffffd000`21db5630 ffffe000`00000000 : ffffe000`00000000 00000000`00000000 ffffe000`03154880 ffffc000`05b6b050 : xtouch+0x4d86
    ffffd000`21db5638 ffffe000`00000000 : 00000000`00000000 ffffe000`03154880 ffffc000`05b6b050 fffff800`04519419 : 0xffffe000`00000000
    ffffd000`21db5640 00000000`00000000 : ffffe000`03154880 ffffc000`05b6b050 fffff800`04519419 ffffd000`21db5936 : 0xffffe000`00000000
    fffff800`04514d86 ??              ???
    SYMBOL_NAME:  xtouch+4d86
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: xtouch
    IMAGE_NAME:  xtouch.sys
    FAILURE_BUCKET_ID:  0x139_3_xtouch+4d86
    BUCKET_ID:  0x139_3_xtouch+4d86
    FAILURE_ID_HASH_STRING:  km:0x139_3_xtouch+4d86
    FAILURE_ID_HASH:  {88dea76d-e1e8-4afa-02e2-cdbe3e8bbc57}
    Followup: MachineOwner
    Xtouch.sys is the driver for your USB Touchscreen Device, your driver is from Wed Oct 27 05:19:31 2010.
    This driver is not compatible with windows 8.1, please upload to a windows 8.1 compatible version.

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

    Advice: Look for the drivers first at driverpage of your OEM (HP)

    LVPr2M64 Wed Oct 07 10:26:50 2009 (4acc50ca) 0000d45c LVPr2M64.sys
    Driver Description: Logitech QuickCam Express/Go driver
    Driver Update Site: Logitech Support - Downloads, Manuals, FAQs & More

    lvpopf64 Wed Oct 07 10:27:20 2009 (4acc50e8) 000450ff lvpopf64.sys
    Driver Description: Logitech POP Suppression Filter
    Driver Update Site: Logitech Support - Downloads, Manuals, FAQs & More

    lvrs64 Wed Oct 07 10:27:59 2009 (4acc510f) 00058d78 lvrs64.sys
    Driver Description: Logitech Camera driver
    Driver Update Site: Logitech Support - Downloads, Manuals, FAQs & More

    lvuvc64 Wed Oct 07 10:28:44 2009 (4acc513c) 00616f6a lvuvc64.sys
    Driver Description: Logitech USB Video Class Driver (WebCam)
    Driver Update Site: Logitech Support - Downloads, Manuals, FAQs & More

    ICCWDT Wed Aug 18 10:27:45 2010 (4c6b9981) 0001100b ICCWDT.sys
    Driver Description: IIntel(R) Watchdog Timer Driver
    Driver Update Site:

    xtouch Wed Oct 27 05:19:31 2010 (4cc79a43) 0003307d None xtouch.sys
    (see above)

    clwvd Fri Aug 03 12:49:32 2012 (501bacbc) 0000ca2d clwvd.sys
    Driver Description: CyberLink WebCam Virtual Driver
    Driver Update Site: Customer Support | CyberLink

    WirelessButtonDriver64 Thu Aug 30 05:11:29 2012 (503ed9e1) 000082c4 WirelessButtonDriver64.sys
    Driver Description: HP wireless driver - 1st seen in Windows 8
    Apparently related to various keyboard functions and FN key
    Driver Update Site: OEM only - HP Support
    HP Support, Drivers, Contact and Help Forums | HP Support

    ISCTD64 Tue Nov 27 20:52:34 2012 (50b51a02) 00016374 ISCTD64.sys
    Driver Description: Intel Smart Connect Technology Driver
    Check w/OEM yours is HP
    Last edited by lifetec; 29 Mar 2014 at 13:55.
      My System SpecsSystem Spec

  3. #3

    Posts : 4
    Windows 8.1

    Ok not sure what to do about this. There is no listing for a "Touch Screen Device" of any kind in the Device Manager. And the HP website does not list a driver for updating one on its list of drivers for my machine.

    The irony is this is a brand new Windows 8.1 system, not an upgrade. So I have no idea why there is a non 8.1 driver on here. I bought the machine in January direct from HP.

    I have listed in Device Manager 4 generic "USB Input Device" but all four list the driver as 6/21/2006.

    I while ago I disabled the touch screen through a recommended website's instructions by going through those generic input device entries one by one disabling them until the touch screen disabled. There is still one disabled and the touch screen is disabled physically but even that one still lists the driver as 6/21/2006.

    Now I have a program called PerfectUpdater installed that updates drivers for me. At one point in time it 'updated' the eGalaxyTouch driver but it didnt update it fully (when I rebooted per instructions windows 'closed' a window that was the start of the install that was stuck behind other windows) but since I wasnt using the touch screen I wasnt worried at the time. I found the eGalaxTouch software installed in Control Panel so I have now removed it. (Its possible that reverted the drivers back to 2006 I guess).

    So I guess maybe I should just leave it alone and see if it BSODs more? Dont wanna waste your time though if there is more I could do before posting a new thread.

    With these other drivers I am going to contact PerfectUpdater and see what their problem is. They were recommended as #1 by PCMagazine so I thought they had their bleep together but I guess maybe not so much. Be a test of whether or not this software is worth ordering again next year or see if for some dumb reason its updating to old drivers. (yuck).

    Thanks for your help so far! Lets hope it stops!

    Oh. How do I clear the old logs so I can get new ones from new BSODs (just so we arent trying to debug BSODs from before the updates.)



    Just re ran the perfect updater to see what it would say and it wants to update a USB Input Device from 2006 to 10/27/2010 so apparently that was it. But now I am confused. If the 2010 isnt 8.1 compatible how the heck is the original 2006 compatible? Why would HP ship a 2014 Machine with a new touch screen with a 2006 driver from another operating system?

    Or am I crazy?
      My System SpecsSystem Spec

  4. #4

    Posts : 5,139
    Win8.1Pro - Finally!!!

    Just my 2 here.
    Driver updates are difficult to do properly. For example, a company may make a graphics chipset, but then another company may solder that chip to their graphics card (and add some stuff to the driver package), then another company will use this card in their system (adding some more stuff to it's driver package).

    Also, where do you get them from? In addition to the above example (where the drivers are available at the website of each of those who are involved) there's also some of them who upload different versions to Windows/Microsoft Update. FWIW - Microsoft doesn't certify these, so the different manufacturer's can upload what they want. I know of one instance w/Win7 where an older, BSOD causing driver was installed on systems through Windows Update (the company has since updated it - after a couple of years). Please remember that BSOD's are actually fairly rare events - so manufacturer's changes will come slowly.

    Also, what do you do if the driver manufacturer (or one/all of the other manufacturer's) doesn't offer a driver for download. Where do you download it from? Is it infected? Is it the proper driver? Will you get malware from the download process?

    Then there's the related software. Again using video as an example, the manufacturer will sometimes use 2 video cards, so each has their own unique requirements. And then there's the software and drivers that are needed to ensure that the cards work together properly (not to mention any other display stuff such as touchscreen or monitor drivers).

    Then you attempt to package a driver detection program that makes determinations based on what's installed. What if there's problems with a driver for a particular OS? What if the system isn't compatible with the driver for that particular device in that particular OS on that particular system?

    Next, most of these programs just look at individual drivers and then assign a name to them.
    This implies that you can find that name and then install just that driver.
    This just doesn't work - as most drivers come in installation packages that have several drivers - not just one.

    Also, there's driver versioning. As an easy method (in these forums) we use the dates of the files.
    But what date should we use? The date of the installation package? Or the date for the driver?
    And, are the dates accuarate, or are they just made up when the driver is compiled (and, as such, are the dates trustable)

    The same goes with versioning. Which version do you use? The version of the installation package, or the version of that particular driver? What happens when a manufacturer changes the version for their own installer? (Toshiba, HP, and Dell do this IMO - haven't looked at the others).

    And what about compatibility? What if the manufacturer says it's compatible and it actually isn't? What if you have an incompatible device and have a workaround installed? What about those devices that are installed and aren't compatible (and don't have a workaround)?

    Feel free to use a tool such as PerfectUpdater - but have a close look at what it's suggesting BEFORE attempting to update.
    If you have questions about what it suggests, feel free to post them here.

    Also, if you're going to let a program modify stuff in the bowels of your OS , then please:
    - make a complete backup of your system prior to starting
    - set a system restore point
    - have a bootable repair disk ready "just in case"

    FYI - the removal of some drivers, if not done properly, can render your system un-bootable. There is a way to safely remove them - but this involves a lot of work and isn't always 100% successful (but the method I use includes a step so that you can recover your system in case it doesn't work)

    In case you've been able to stay awake through the full rant here - thank you for reading it. :0)
      My System SpecsSystem Spec

  5. #5

    Posts : 5,139
    Win8.1Pro - Finally!!!

    One more thing - the date is not significant if:
    - the driver was designed properly (according to Microsoft specifications) and assuming that the Microsoft specifications were able to cope with updates/upgrades/newer versions of the OS
    - the driver developer takes the older driver and thoroughly tests it in the new OS (and finds that it's compatible). There are a few drivers out there like this - but then you have to wonder who's doing good testing and who isn't?

    You can see the dates on most of your drivers by going to C:\Windows\System32\drivers
    Some programs store the drivers in other places - but that's beyond the scope of this post

    As for your particular 2006 driver - which driver are they suggesting that you update? Look for the filename that ends in .sys
    The term "USB Input Device" is a generic term for anything that does input operations and plugs into a USB port (mouse, keyboard, webcam, fingerprint reader, SD card reader, etc)

    No need to clear the old logs. Just let them accumulate and we can tell which one's we've done and which we haven't.
      My System SpecsSystem Spec

  6. #6

    Posts : 4
    Windows 8.1

    The 2006 driver was the eGalaxyTouch I believe. For my touch screen that I have disabled lol. I uninstalled it from the control panel and it reverted the driver.

    The dumb thing is this: And it proves your point about dates and versions.

    I looked at the detailed info in PerfectUpdater of the driver that it scanned again after I reverted. The the date is 4 years later but the driver VERSION is back 1 and a mix number of minor versions so you really cant tell on that one whats going on. All I know is you found the error in that driver and I reverted it and I reverted it to a 'newer' version by version number so maybe there was a split in the development tree and PerfectUpdater has an older version of a branch or something.

    Anyway I'll just leave it alone for now and see how things go. I put that particular driver on ignore. All though it looks like PerfectUpdater is only doing (like you said to something else) it by name and not by file so I may never get a PerfectUpdater update for any USB Input Devices from here on out lol. Oh well. Its now named NotSoPerfectUpdater lol.

    Thanks for the help. See how things go.

    If I get more BSODs should I post to this thread or start new? I would assume keep the same thread going cuz they may be interacting with each other but some support websites like it fresh.



    Oh I forgot to ask.

    Should I go ahead and update the other items listed in the original response now that we think we have the specific problem? Just wasnt sure about that. Its startin to get a little more techie for me then I am used to so dont wanna fiddle with too much that I dont have to if things 'just work' ya know?

      My System SpecsSystem Spec

  7. #7

    Posts : 660
    windows 8.1

    The 2006 driver was the eGalaxyTouch I believe

    From your dxdiag.txt
    USB Touchscreen Controller(A120)
    | Vendor/Product ID: 0x0EEF, 0xA120
    | Location: Port_#0006.Hub_#0002
    | Matching Device ID: USB\VID_0EEF&PID_A120
    | Service: xtouch

    I did a google search on the VID & PID and also found Eeti E Galaxy Touch. On their website they have mentioned a windows 8/8.1 driver here EETI Driver1

    What is your exact model, i found HP ENVY TS 14 Sleekbook 103C_5335KV.
    But the HP U.S. site did not recognize this model.

    I would try to update the older drivers, because how more compatible windows 8.1. drivers how more stable your system will get.
      My System SpecsSystem Spec

  8. #8

    Posts : 4
    Windows 8.1

    Alright thank you on both. I will work on this. Will probably have to buy a usb key to do a backup first since this machine doesnt have an optical drive. I really should anyway. Ive been mostly relying on the idea that I have all of my important info in clouds or on one stick I use for documents/files individually.

    Any recommendations on the best way to get into the habbit of making backups? Like do I trust window's system of doing it? I know its different then a restore point. Ive had restore points fail.

    Guess I am looking for a good suggestion on how to make a image to a usb key so I can just go ahead and restore the whole darn thing should it eat itself or get so unstable I cant salvage it.

      My System SpecsSystem Spec

  9. #9

    Posts : 5,139
    Win8.1Pro - Finally!!!

    Stay with this topic until the problem is finished. If you get more BSOD's, zip them up and upload them so we can have a look at them.

    I won't post much of substance (about your particular problem) as lifetec has that well in hand - and I don't want to disturb their troubleshooting process.

    The best way to get in the habit of making backups is to use backup software. I have used SyncBackSE for years - there is a free version available. I currently use Acronis TrueImage as I want both the backup and the ability to image my hard drive (as I plan on switching to a faster drive and then to an SSD) - it runs about $40 (US) or less on Google Shopping. I alsu use the Windows Backup - but I haven't had good experiences with it.

    The most important thing is that it be able to notify you if there was a problem with the backup. SyncBackSE does that - but I'm not sure about the Acronis or the Windows Backup.

    Also, it's advisable to get an external hard drive to backup to. They run about $50 (US) or more, depending on the size that you want. Get as big as you can afford - as it's a pain having to switch multiple drives around (I have numerous 320 gB external drives and I can't keep track of what's on what. I just got a 1 tB drive and it's sweet!
      My System SpecsSystem Spec

  10. #10

    Posts : 660
    windows 8.1

    This tutorial System Image - Create in Windows 8[1]=Backup Restore should be a good starting point. It includes also links to free Image software.
      My System SpecsSystem Spec

Windows 8.1 KERNEL_SECURITY_CHECK_FAILURE - Schwonkey668

Similar Threads
Thread Forum
Last week my laptop suddenly displayed a BSOD with the error KERNEL_SECURITY_CHECK_FAILURE every time the 8.1 tried to load the startup applications (at the exact moment) after i log into my account. I tried uninstalling the RealTek Ethernet, WiFi, Bluetooth and Touchpad driver but to no avail. I...
BSOD Crashes and Debugging
Kernel_security_check_failure - bsod
Hey everyone, I'm having some problems after installing a new motherboard, I did a fresh install of Windows 8.1, updated it via windows update and installed the proper drivers. Everything runs fine except when I play games that I get this BSOD (KERNEL_SECURITY_CHECK_FAILURE) :cry: and I have to...
BSOD Crashes and Debugging
Kernel_Security_Check_Failure BSOD
Hi guys, i am getiing this failure on freshly reinstalled windows 8.1
BSOD Crashes and Debugging
Windows 8.1 - Kernel_Security_Check_Failure BSOD
Hi there, I just got a blue screen out of the blue (pun intended) and was hoping to get some help. I've attached the dump files. The error said "Kernel_Security_Check_Failure". I'm running Windows 8.1. If it helps at all, I had CPUID HWMonitor and OpenHardwareMonitor both open looking at...
BSOD Crashes and Debugging
Windows 8.1 - Kernel_Security_Check_Failure BSOD
This is maybe the 20th BSOD I have gotten in the last 20 days. They all happened immediately after an attempt to wake the computer from a longer hibernation. When system reboots after this BSOD, every time another BSOD "ATTEMPTED SWITCH FROM DPC" will appear right away. Then the system will...
BSOD Crashes and Debugging
Everything froze up and had this buzzing noise in my headset, this has happened 4 times before but not recently ( for about 2 months ) then it just randomly happened again, whocrashed had this to say : On Wed 11/27/2013 5:53:43 PM GMT your computer crashed crash dump file: ...
BSOD Crashes and Debugging
First time i got this error , i had other bsod (i ike to think that were solved), i was on youtube y an then ... bsod , here are my specs: cpu: i7 3635qm mb: Intel hm76 ram: 12 gb ram 1600 mhz (4gb + 8gb) gpu: intel hd 4000 + amd radeon 8870m hdd: liteon 512gb ssd s.o : windows 8 pro 64 bit
BSOD Crashes and Debugging

Eight Forums Android App Eight Forums IOS App Follow us on Facebook