Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Bot causes crash (IRQL_NOT_LESS_OR_EQUAL)
kamil234
#1 Posted : Monday, April 23, 2018 3:18:35 PM(UTC)

Rank: Advanced Member

Groups: Registered
Posts: 116

Thanks: 6 times
Was thanked: 34 time(s) in 20 post(s)
Hi Joy,

Any insight to this? Memory dump is below. Computer never crashes otherwise when im gaming (even demanding games + streaming, etc):
For refence, Im using the following:
Hardware: i5-3570K, 16GB ram, GTX1080 GPU.
OS: Windows 10 Pro with all updates installed.
==========================================

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: 00000000ffffff8a, 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: fffff803d5c7154a, address which referenced memory

Debugging Details:



DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.125 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1402

BIOS_DATE: 03/21/2014

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: P8Z77-V LK

BASEBOARD_VERSION: Rev X.0x

DUMP_TYPE: 2

BUGCHECK_P1: ffffff8a

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff803d5c7154a

WRITE_ADDRESS: fffff803d6005380: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
00000000ffffff8a

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiSelectReadyThread+7a
fffff803`d5c7154a 20418b and byte ptr [rcx-75h],al

CPU_COUNT: 4

CPU_MHZ: d48

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 1B'00000000 (cache) 1B'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: HearthRanger.exe

ANALYSIS_SESSION_HOST: GAMING-PC

ANALYSIS_SESSION_TIME: 04-23-2018 14:17:28.0085

ANALYSIS_VERSION: 10.0.15063.400 amd64fre

TRAP_FRAME: ffff85046eff3660 -- (.trap 0xffff85046eff3660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000ffffffff
rdx=00000000fffffffe rsi=0000000000000000 rdi=0000000000000000
rip=fffff803d5c7154a rsp=ffff85046eff37f0 rbp=0000000000000000
r8=0000000000000000 r9=000000000000000f r10=0000000000000000
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
nt!KiSelectReadyThread+0x7a:
fffff803`d5c7154a 20418b and byte ptr [rcx-75h],al ds:00000000`ffffff8a=??
Resetting default scope

MISALIGNED_IP:
nt!KiSelectReadyThread+7a
fffff803`d5c7154a 20418b and byte ptr [rcx-75h],al

LAST_CONTROL_TRANSFER: from fffff803d5d7c9e9 to fffff803d5d710e0

STACK_TEXT:
ffff8504`6eff3518 fffff803`d5d7c9e9 : 00000000`0000000a 00000000`ffffff8a 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffff8504`6eff3520 fffff803`d5d7ad7d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff8504`6eff3660 fffff803`d5c7154a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23d
ffff8504`6eff37f0 fffff803`d5c70c45 : ffffb380`fffffffe 00000000`ffffffff 00000000`00000000 00000000`0000000f : nt!KiSelectReadyThread+0x7a
ffff8504`6eff3880 fffff803`d5c7048a : ffffd688`00000000 00000000`00000000 00000000`00000000 00000000`06ab5000 : nt!KiSearchForNewThread+0x65
ffff8504`6eff38e0 fffff803`d5c6feae : ffffd688`42315080 ffffd688`42315180 00000000`010be84e fffff803`00000000 : nt!KiSwapThread+0xea
ffff8504`6eff39a0 fffff803`d5cae115 : ffffd688`000000df ffffd688`00000000 ffff8504`6eff3b01 00000000`00000001 : nt!KiCommitThreadWait+0x10e
ffff8504`6eff3a40 fffff803`d61078af : ffffd688`42315080 00000000`0116b000 00000000`1a7bfd00 00000000`1a7becb0 : nt!KeDelayExecutionThread+0x3e5
ffff8504`6eff3ad0 fffff803`d5d7c553 : 00000000`30f88c20 00000000`00000007 ffffffff`ffffd8f0 00000000`00000001 : nt!NtDelayExecution+0x5f
ffff8504`6eff3b00 00000000`594a1e5c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`1a7beca8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x594a1e5c


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 427527b2bcf135ea60bc718c0d816591068db2ea

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 732a8a5cf4fc3716432b918de8d911eafc3a3dfb

THREAD_SHA1_HASH_MOD: bc100a5647b828107ac4e18055e00abcbe1ec406

FOLLOWUP_IP:
nt!KiSelectReadyThread+7a
fffff803`d5c7154a 20418b and byte ptr [rcx-75h],al

FAULT_INSTR_CODE: 468b4120

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KiSelectReadyThread+7a

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.16299.125

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

PRIMARY_PROBLEM_CLASS: IP_MISALIGNED

TARGET_TIME: 2018-04-23T16:40:42.000Z

OSBUILD: 16299

OSSERVICEPACK: 125

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-12-07 16:55:32

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.16299.125

ANALYSIS_SESSION_ELAPSED_TIME: 505

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:ip_misaligned

FAILURE_ID_HASH: {201b0e5d-db2a-63d2-77be-8ce8ff234750}

Followup: MachineOwner
---------
rsndk
#2 Posted : Monday, April 23, 2018 5:53:20 PM(UTC)
Rank: Newbie

Groups: Registered
Posts: 1

same here. PLEASE FIX THIS!!!!!!!!!!!!!!!!
JoyAdmin
#3 Posted : Monday, April 23, 2018 11:26:53 PM(UTC)
Rank: Administration

Groups: Administrators
Posts: 4,847

Thanks: 805 times
Was thanked: 4539 time(s) in 1637 post(s)
Usually it's caused by you installed improper hardware drivers, especially drivers related with your display card.

Game and bot don't have any kernel driver, it can not cause BSOD at application level.

Also you can check this thread:

https://www.techsupportf...-a-new-comp-568449.html

1 user thanked JoyAdmin for this useful post.
kamil234 on 4/23/2018(UTC)
kamil234
#4 Posted : Monday, April 23, 2018 11:39:24 PM(UTC)

Rank: Advanced Member

Groups: Registered
Posts: 116

Thanks: 6 times
Was thanked: 34 time(s) in 20 post(s)
JoyAdmin;56029 wrote:
Usually it's caused by you installed improper hardware drivers, especially drivers related with your display card.

Game and bot don't have any kernel driver, it can not cause BSOD at application level.

Also you can check this thread:

https://www.techsupportf...-a-new-comp-568449.html




Thanks for the reply, but my BIOS, motherboard firmware, drivers, and windows updates are all up to date and proper. It just so happens, that the computer never BSOD, only randomly when running the bot.

If you don't think that's a bot issue, it's fine. It only happens random, so i can live with it.




Elekid
#5 Posted : Thursday, May 10, 2018 3:50:00 PM(UTC)
Elekid


Rank: Advanced Member

Groups: Registered
Posts: 101
Location: Nijmegen, The Netherlands

Thanks: 29 times
Was thanked: 65 time(s) in 58 post(s)
JoyAdmin, my computer also crashes ONLY when I'm using the bot. Never ever during not botting. So I think there actually is a problem. How can I help you find the problem?

I'm having this problem for a few months now. You can PM me if you need any specific information.

I don't get a BSOD but my computer just freezes after a couple of hours. Only way to continu is through a hard reset.
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.163 seconds.