Windows 10: Blue Screens while gaming.

So i play allot of Rust and i get a few bluescreens sometimes. Sometimes its the same one sometimes its another one.


The one that i the most get it IRQL_NOT_LESS_OR_EQUAL caused by driver hal.dll or DRIVER_IRQL_NOT_LESS_OR_EQUAL caused by driver tcpip.sys

This is the driver irql not less or equal what i found in microsoft debugging software but i have less knowlegde.

Can someone help me please?


Microsoft (R) Windows Debugger Version 10.0.18317.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\022519-6203-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff806`1d212000 PsLoadedModuleList = 0xfffff806`1d62dad0
Debug session time: Mon Feb 25 13:46:28.538 2019 (UTC + 1:00)
System Uptime: 0 days 0:11:26.285
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff****1`ccaceff0=000000000000000a
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000002, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80154c24a45, address which referenced memory

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.

SYSTEM_SKU: To Be Filled By O.E.M.

SYSTEM_VERSION: To Be Filled By O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: P1.40

BIOS_DATE: 01/14/2016

BASEBOARD_MANUFACTURER: ASRock

BASEBOARD_PRODUCT: 990FX Extreme6

BASEBOARD_VERSION:

DUMP_TYPE: 2

BUGCHECK_P1: 2

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80154c24a45

READ_ADDRESS: GetUlongFromAddress: unable to read from fffff8061d6d94c0
fffff8061d754390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
0000000000000002

CURRENT_IRQL: 2

FAULTING_IP:
tcpip!WfpAleMatchStatefulEndpoint+1f5
fffff801`54c24a45 458d4108 lea r8d,[r9+8]

CPU_COUNT: 8

CPU_MHZ: 1126

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_SESSION_HOST: DESKTOP-TICRLHT

ANALYSIS_SESSION_TIME: 02-25-2019 13:55:05.0990

ANALYSIS_VERSION: 10.0.18317.1001 amd64fre

TRAP_FRAME: ffffa481ccacf130 -- (.trap 0xffffa481ccacf130)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000011 rbx=0000000000000000 rcx=ffffa4823e717fa7
rdx=ffffa481ccacf610 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80154c24a45 rsp=ffffa481ccacf2c0 rbp=ffffa481ccacf3c0
r8=0000000000000003 r9=0000000000000000 r10=00000000dc84dfc3
r11=ffffe18d2d562000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
tcpip!WfpAleMatchStatefulEndpoint+0x1f5:
fffff801`54c24a45 458d4108 lea r8d,[r9+8]
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8061d3d6c69 to fffff8061d3c5440

STACK_TEXT:
ffffa481`ccacefe8 fffff806`1d3d6c69 : 00000000`0000000a 00000000`00000002 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffa4********f4350 00000000`0000007d : tcpip!WfpProcessInTransportStackIndication+0x74b
ffffa481`ccad0580 fffff801`54c4d68f : ffffa481`ccad07e0 ffffe18d`359f6ea0 ffffe18d`359f6ea0 00000000`00000000 : tcpip!InetInspectReceiveDatagram+0x2c0
ffffa4****9 : 00000000`00000000 00000000`00000000 ffffe1****
ffffa481`ccad1260 fffff806`1d331fe8 : ffffa481`ccad1550 00000000`00000002 ffffe18d`2d4bc040 ffffa481`ccad14d0 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x127
ffffa481`ccad13a0 fffff806`1d331f5d : fffff801`54c6bf10 ffffa481`ccad14d0 ffffe18d`2d427760 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x7****1 : 00000000`00000000 ffffa481`ccad1750 00000000`00000001 ffffe18d`2dfb74e0 : tcpip!FlReceiveNetBufferListChain+0x2be
ffffa481`ccad1650 fffff801`5479239d : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000002 : ndis!ndisMIndicateNetBufferListsToOpen+0x221
ffffa481`ccad1720 fffff801`547977c3 : c0011020`00300001 00400000`00000000 00000000`00000000 fffff806`00000002 : ndis!ndisMTopReceiveNetBufferLists+0x23d
ffffa481`ccad17b0 fffff801`54795087 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisCallReceiveHandler+0x43
ffffa4**** 00000000`00000001 : L1C63x64+0x96cc
ffffa481`ccad1988 ffff7e37`0000002d : 00000000`00000000 ffffa481`ccad1a68 00000000`00000001 00000000`00000000 : 0xffffe18d`00000000
ffffa481`ccad1990 00000000`00000000 : ffffa481`ccad1a68 00000000`00000001 00000000`00000000 00000000`00000002 : 0xffff7e37`0000002d


THREAD_SHA1_HASH_MOD_FUNC: 134ddf6fe60b1201220491f1d9e****6cc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: L1C63x64

IMAGE_NAME: L1C63x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 59c02d4b

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 96cc

FAILURE_BUCKET_ID: AV_L1C63x64!unknown_function

BUCKET_ID: AV_L1C63x64!unknown_function

PRIMARY_PROBLEM_CLASS: AV_L1C63x64!unknown_function

TARGET_TIME: 2019-02-25T12:46:28.000Z

OSBUILD: 17763

OSSERVICEPACK: 316

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 3e3c

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_l1c63x64!unknown_function

FAILURE_ID_HASH: {1c745e23-731f-42c8-af3a-346943adb42b}

Followup: MachineOwner
---------

:)

 

Blue Screen of Death (Crash) When Playing Games


Nothing for step 10.

Step 11 -

 

Blue Screen

Hi,





Blue screens could be caused by problems with your computer’s hardware or with its driver. Still, we
would like to know more about the issue. Please clarify the following:

• Did you get a STOP code?
• Did you install any hardware or driver recently?

For basic troubleshooting steps to resolve blue screen errors, we suggest checking out this
article and simply follow the steps.



Feel free to contact us if you need further help.

 

Startup Blue Screen

Hi Jon,

Startup blue screen error(s) can occur if a problem causes your PC to shut down or restart unexpectedly. It could be due to the following:

• Outdated device software drivers
• Corrupted Windows update system files
• Software/Security conflicts

We would like to know some information:

• Did you get any blue screen stop error codes?
• Have you tried booting in Safe mode?

We suggest that you check this
article about troubleshooting blue screen errors and follow the troubleshooting steps provided there.

We will wait for your response