Constant BSOD Issues

Anonymous
2019-07-31T23:05:50+00:00

I have a custom built PC and since Day 1 I have had issues with BSOD's.  Usually this happens while playing a game, but has happened just sitting idle.  I am not a PC technical guy but I need some help to fix this issue.  I never get a specific fault in the Bluescreen, but the Bluescreen Viewer point to ntoskrnl.exe as the culprit but in my research its never the actual fault.

The Following are the BSOD's I am getting:

Security Kernel Check Failure (Most Frequent)

System Service Exemption

IQRL not Less or Equal

The Build Is as Follows:

Asus Prime Z390-A

Intel I7-8700

32 GB Corsair Ram

Nvidia GeForce RTX 2070

Corsair MP510 SSD

Windows 10 Pro 1903

Following has already been done:

Reinstalled Win 10 multiple times

Uninstalled and reinstalled Graphics Drivers

Updated all drivers that needed updated (done by going thru device manager one at a time)

chkdsk, memtest, sfc, to name a few

Tried different ram, both amount and brand

3 Different HD's, both brand and SSHD, SSD, and Standard HD

Im not 100% sure what info is needed but ask and Ill do my best.  Please HELP!

Windows for home | Windows 10 | Performance and system failures

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

43 answers

Sort by: Newest
  1. Anonymous
    2019-08-02T11:23:23+00:00

    A. Analysis Results

    File Name: 073019-12953-01.dmp

    SYSTEM_SERVICE_EXCEPTION (3b)

    IMAGE_NAME: ntkrnlmp.exe

    File Name: 073119-12375-01.dmp

    IRQL_NOT_LESS_OR_EQUAL (a)

    IMAGE_NAME: ntkrnlmp.exe

    File Name: 073019-12921-01.dmp

    KERNEL_SECURITY_CHECK_FAILURE (139)

    IMAGE_NAME: ntkrnlmp.exe'

    File Name: 073019-12421-01.dmp

    KERNEL_SECURITY_CHECK_FAILURE (139)

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

    IMAGE_NAME: GLCKIO2.sys

    B. Third Party Drivers

    GLCKIO2.sys - ???

    Driver date - Mon Apr 22 06:44:46 2019

    C. Recommendations

    A. Create a system restore point so that if something wrong happens you can revert.

    Type restore point in Cortana Search > Create a Restore point > Check whether against your drive, Protection is ON or not. If not ON, click Configure button below to Make it ON > Now press Create to create a restore point

    B.Go to C:\windows\system32\drivers\

    Right click on GLCKIO2.sys > Properties > Details tab > Post the screenshot

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-08-02T00:44:07+00:00

    Had almost 3 hrs with no issues then it BSOD on me again.

    https://1drv.ms/u/s!AhoUalcrbFFVjzH1X0c3EgegsA0u?e=7RABva

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-08-01T11:14:16+00:00

    Sure keep us updated :)

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-08-01T02:32:05+00:00

    ok that's done but no time left tonight for testing.  I will do more testing tomorrow after I get off of work and will report back any issues if there are any.  Thank you for your help either way.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2019-08-01T02:11:07+00:00

    No real help here as well :(

    First, create a Restore point:

    https://www.tenforums.com/tutorials/4571-create...

    Second, Boot to Safe mode and rename GLCKIO2.sys in C:/Windows/System32/drivers to GLCKIO2.sys.old

    https://www.tenforums.com/tutorials/2304-boot-i...

    If the PC fails to boot which it should not, we would restore the system using Restore point.

    Wait until the next BSOD happens.

    Disclaimer:

    This is a non-Microsoft website which would provide accurate and safe information. Watch out for ads on the site which are frequently classified as a PUP (Potentially Unwanted Products). There is no need to buy paid products to fix your computers as they do more harm than good sometimes.

    Was this answer helpful?

    0 comments No comments