Custom built Desktop pc running into bsod errors.

Aidan C · 07 Jul 2020

Hi I have built this desktop personal computer around a couple months ago and I have been running into blue screen of death errors, I am getting the error code "Irql_not_less_or_equal" or something like that,
I also have received "KERNEL_SECURITY_CHECK_FAILURE" before but not in a little while since I reinstalled windows (I only did that a day and a half ago though.)

I am only every running into the bsod's when playing games ran in the game engine "Unity" I have noticed so far.
I have tried a ram test aswell as reinstalling windows multiple times and also tried to update drivers including my graphical one but still they continue, I have no idea what it could be as of this moment I have been working on it continuously over the course of the 2 months so if someone can guide me to fixing this I will be extremely grateful.

My specs are as including:
Cpu - Intel Core i9 9900k
MotherBoard - MPG Z390 GAMING EDGE AC (MS-7B17)
Ram - Patriot Viper Steel 16GB (2 x 8GB) 288-Pin DDR4 Speed = 4133mhz & Voltage of 1.35V
Graphics Card - NVIDIA Geforce GTX 1060 6GB from EVGA Corp.
Windows Version # = 10.0.18363 Build 18363

Here is the required Zip :

Attachment 287031

Please let me know if I can do anything to help you help me, I sincerely hope we can fix the issue..

Ztruker · 07 Jul 2020

Warning

Attention:

Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions

If you need to add new information, please make a new post in your initial BSOD thread. Please do not make an extra new thread.

Please do not post anything other than Windows 10 Blue Screen Of Death problems in this section.

Aidan C · 07 Jul 2020

I'm sorry, did I not follow the requirements?

Ztruker · 07 Jul 2020

No problem. Do it now and post the resulting zip file so we can look at the data.

Ztruker · 07 Jul 2020

Not sure what you did but this is what I get:

Attachment 287061

See here: How to Upload and Post Screenshots and Files at Ten Forums

Aidan C · 07 Jul 2020

For some reason it will no longer let me edit the post to fix the link, can you see if this one worked? I have uploaded it to onedrive as the download will not work for you.

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Ztruker · 07 Jul 2020

That's good, got it.
07/03 dumps shows:

Code:

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 000000000000001e, Type of memory safety violation
Arg2: ffff810fd9756a10, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffff810fd9756968, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

Debugging Details:
------------------

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

bedaisy = BattleEye anti-cheat driver.

Update your Battle-eye software or delete it, see if that helps.

07/06 17:56 and 07/07 00:05 dumps are both WHEA 124:

Code:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe28656b3f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

Code:

4: kd> !errrec ffffe28656b3f028
===============================================================================
Common Platform Error Record @ ffffe28656b3f028
-------------------------------------------------------------------------------
Record Id     : 01d653ea2922dc53
Severity      : Fatal (1)
Length        : 936
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/7/2020 4:03:42 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe28656b3f0a8
Section       @ ffffe28656b3f180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000906ed
Processor ID  : 0x0000000000000004

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffe28656b3f0f0
Section       @ ffffe28656b3f240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000004
CPU Id        : ed 06 09 00 00 08 10 04 - ff fb fa 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ ffffe28656b3f240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffe28656b3f138
Section       @ ffffe28656b3f2c0
Offset        : 664
Length        : 272
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 4 Bank 4)
  Status      : 0xbe00000000800400
  Address     : 0x00007ff9e36842e2
  Misc.       : 0x00007ff9e36842e2

Code:

2: kd> !errrec ffffdd871d5db028
===============================================================================
Common Platform Error Record @ ffffdd871d5db028
-------------------------------------------------------------------------------
Record Id     : 01d6518e391135ff
Severity      : Fatal (1)
Length        : 872
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/6/2020 21:55:22 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffdd871d5db0a8
Section       @ ffffdd871d5db180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000906ed
Processor ID  : 0x0000000000000002

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffdd871d5db0f0
Section       @ ffffdd871d5db240
Offset        : 536
Length        : 64
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000002
CPU Id        : ed 06 09 00 00 08 10 02 - ff fb fa 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffdd871d5db138
Section       @ ffffdd871d5db280
Offset        : 600
Length        : 272
Flags         : 0x00000000
Severity      : Fatal

Error         : Unknown (Proc 2 Bank 0)
  Status      : 0xb200000000030005

These can be caused by a defective CPU or driver.

The other two dumps are identical:

Code:

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000064, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80054ca3c6e, address which referenced memory

Code:

CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  AV
PROCESS_NAME:  Gunfire Reborn.exe

Nothing else in the dump give me any useful info though.

To see if this is a driver problem, enable Driver Verifier:

Run Driver Verifier

Driver Verifier-- tracking down a mis-behaving driver.

Following the instructions in the above link will check for problems in all non-Microsoft drivers.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it.

If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file.
Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

To check if verifier is active, open a Command Prompt and enter:

verifier /query

If not active it will respond with

No drivers are currently verified.

If you have questions, see this additional tutorial which may help to clear things up.

Enable and Disable Driver Verifier in Windows 10