Share via

BSOD crashes

Anonymous
2017-12-06T22:28:47+00:00

Hello,

In the past week I had a lot of BSOD crashes. I tried to catch some of them in the last few days and here are they.

IRLQ not less or equal

error Page Fault In Nonpaged Area

CRITICAL STRUCTURE CORRUPTION

Here is the logs off the Event Viewer from the last 3 BSOD that I got

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID 

{22279AF5-03AE-4CAF-989D-2530918B2F1C}

 and APPID 

{0773CCD6-59A2-4D26-B235-19247767E645}

 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID 

{22279AF5-03AE-4CAF-989D-2530918B2F1C}

 and APPID 

{0773CCD6-59A2-4D26-B235-19247767E645}

 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

My PC specs are the following:

CPU: Intel Core i7-4790k overlocked up to 4.5GHz

CPU Cooler: Noctua NH-D15

Motherboard: Asus Z97 Deluxe

Memory: G.Skill Sniper Series 16GB 2 x 8GB DDR3

GPU: Asus Strix 980Ti

HDD: Western Digital Caviar Blue 1TB

SSD: 240GB Corsair Force LE

PSU: Cooler Master 650W 80+ Gold Certified

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

10 answers

Sort by: Most helpful
  1. Sumit 43,796 Reputation points Volunteer Moderator
    2017-12-08T10:51:45+00:00

    The dump stack blames BEDaisy.sys for the crash:

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

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

    BEDaisy+0x1e287c

    The driver stands for BattleEye anti-cheat driver. Uninstalling that should resolve this issue.(You might try a reinstall, but I recommend Uninstalling and watching it for few days to observe how things go)

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-12-07T23:53:59+00:00

    Hello,

    After I had a couple of crashes with this BSOD problem, I googled it and I came across to this website https://shauncassells.wordpress.com/2015/09/28/windows-10-event-10016-fix-the-application-specific-permission-settings-do-not-grant-local-activation-permission-for-the-com-server-application-with-clsid-d63b10c5-bb46-4990-a94f-e40b9d520160-and-a/

    I was following the steps, did everything the same as it's shown there and today while I was gaming I did not get any blue screen of death compared to what I was getting before like insane amount of BSODs. So after I went afk, like after 10-12 hours of leaving the PC turned on with the game running, the PC just crashed with this BSOD  and this message pops up in the Event Viewer

    "The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x0000000000000048, 0x0000000000000002, 0x0000000000000001, 0xfffff801b7609417). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 86ea8bf4-4a43-4d4c-a1ff-6edfd3048fc3."

    MEMORY.DMP is 1GB. Also I found a Minidump which is 1.6MB and I will upload this one

    http://www.mediafire.com/file/h7f9bauiieqnzs2/120817-6203-01.dmp

    Please let me know if the link doesn't work so I can upload on onedrive as last option.

    Also I did mem test & stress test they were both good. Stress test was running for 1 hr and temperatures of cores were between 77 - 80C which is totally fine for overclocked and properly cooled CPU.

    Was this answer helpful?

    0 comments No comments
  3. Sumit 43,796 Reputation points Volunteer Moderator
    2017-12-07T03:07:19+00:00

    Please share the minidumps for a better analysis of the problem. Instructions can be found here:

    http://answers.microsoft.com/en-us/windows/wiki...

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-12-07T00:21:11+00:00

    We are volunteers willing to help you try to resolve this issue.

    Troubleshoot blue screen errors <-- read this link

    http://windows.microsoft.com/en-us/windows-10/t...

    We can analyze the minidumps if you make them available from the OneDrive or other file sharing sites (such as MediaFire). If you have problems uploading the minidumps copy them to the Desktop or the Documents folder and upload them from there.

    One-Drive - Share files and folders and change permissions

    http://windows.microsoft.com/en-us/onedrive/sha...

    Upload photos and files

    http://windows.microsoft.com/en-us/onedrive/add...

    Zip or upload the contents of C:\Windows\minidump

    Use OneDrive to upload collected files

    http://social.technet.microsoft.com/Forums/en-U...

    Please let us know the results and if you need further assistance.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2017-12-06T22:41:25+00:00

    Usually BSODs are caused by hardware/driver issues.

    I would first start by disconnecting any non-essential hardware, only keeping mouse and keyboard attached.

    It could suggest you need to update your chipset drivers and BIOS.

    I recommend you update the most critical ones: BIOS, Chipset, Display Driver, Network adapters.

    http://answers.microsoft.com/en-us/insider/wiki...

    Another option is to check your hardware.

    You can open the system unit to make sure all components are fitted and secured properly.

    I would also try swapping out memory modules to see if one of them might defective. You can also try scanning for errors:

    https://www.groovypost.com/howto/use-the-memory...

    Was this answer helpful?

    0 comments No comments