BSOD when playing CSGO. How to fix?

[Kireur]

Well i was playing CSGO today when my laptop just froze and then it let me to this blue screen. The error was 'IRQL Not less not equal' Was looking for a solution but i did not get what it meant.

This is from the dump file
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {28, 2, 0, fffff803d3da3759}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff803d3da3759, address which referenced memory

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


DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000028

CURRENT_IRQL: 2

FAULTING_IP:
nt! ?? ::FNODOBFM::`string'+2cbc9
fffff803`d3da3759 488b4628 mov rax,qword ptr [rsi+28h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: AV

PROCESS_NAME: csgo.exe

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

TRAP_FRAME: ffff8c8064357100 -- (.trap 0xffff8c8064357100)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff858000000028 rbx=0000000000000000 rcx=0000000000000000
rdx=ffff858000000028 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803d3da3759 rsp=ffff8c8064357290 rbp=0000000000000000
r8=ffffa1866f284460 r9=0000000000000001 r10=0000000fffffffff
r11=ffff858000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt! ?? ::FNODOBFM::`string'+0x2cbc9:
fffff803`d3da3759 488b4628 mov rax,qword ptr [rsi+28h] ds:00000000`00000028=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff803d3d72829 to fffff803d3d676f0

STACK_TEXT:
ffff8c80`64356fb8 fffff803`d3d72829 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff8c80`64356fc0 fffff803`d3d70e07 : 00000000`00cd917d fffff803`d3f40090 00000000`f7fe5c67 fffff803`d3cee61b : nt!KiBugCheckDispatch+0x69
ffff8c80`64357100 fffff803`d3da3759 : ffffbadd`130c208c fffff803`d3c58d9f 00000000`00000001 ffffbadd`130c20ac : nt!KiPageFault+0x247
ffff8c80`64357290 fffff803`d3c89c9a : 00000000`00000000 ffffd800`000a77a8 ffff8c80`64357680 00000000`14ef5000 : nt! ?? ::FNODOBFM::`string'+0x2cbc9
ffff8c80`64357390 fffff803`d40ffd04 : 00000000`00000003 00000000`00000001 00000000`00001000 00000000`00001000 : nt!MmProbeAndLockPages+0x25a
ffff8c80`643574a0 fffff803`d40ff92f : 00000000`0038e900 00000000`00000010 ffffa186`6f273250 00000000`00000001 : nt!MmCopyVirtualMemory+0x364
ffff8c80`64357950 fffff803`d40ff7cb : ffffa186`789c7080 00000000`0038e958 ffff8c80`64357a28 00000000`00b7dca8 : nt!MiReadWriteVirtualMemory+0x15f
ffff8c80`643579d0 fffff803`d3d72393 : 00000000`714e45d0 00000000`00000410 00000000`00000000 00000000`00b7d7b8 : nt!NtReadVirtualMemory+0x1b
ffff8c80`64357a10 00007ff9`22c168b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0038e938 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`22c168b4


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff803d3da3044 - nt! ?? ::FNODOBFM::`string'+2c4b4
[ fa:85 ]
fffff803d3da344a-fffff803d3da344c 3 bytes - nt! ?? ::FNODOBFM::`string'+2c8ba (+0x406)
[ 40 fb f6:00 6c d8 ]
fffff803d3da3478 - nt! ?? ::FNODOBFM::`string'+2c8e8 (+0x2e)
[ fa:85 ]
fffff803d3da34a2-fffff803d3da34a4 3 bytes - nt! ?? ::FNODOBFM::`string'+2c912 (+0x2a)
[ 40 fb f6:00 6c d8 ]
fffff803d3da34d0 - nt! ?? ::FNODOBFM::`string'+2c940 (+0x2e)
[ fa:85 ]
fffff803d3da3833 - nt! ?? ::FNODOBFM::`string'+2cca3 (+0x363)
[ fa:85 ]
fffff803d3da3847 - nt! ?? ::FNODOBFM::`string'+2ccb7 (+0x14)
[ fa:85 ]
fffff803d3da3920 - nt! ?? ::FNODOBFM::`string'+2cd90 (+0xd9)
[ fa:85 ]
fffff803d3da392a - nt! ?? ::FNODOBFM::`string'+2cd9a (+0x0a)
[ fa:85 ]
fffff803d3da3e8d-fffff803d3da3e8f 3 bytes - nt! ?? ::FNODOBFM::`string'+2d2fd (+0x563)
[ 40 fb f6:00 6c d8 ]
fffff803d3da3eeb - nt! ?? ::FNODOBFM::`string'+2d35b (+0x5e)
[ fa:85 ]
fffff803d3da3f96-fffff803d3da3f97 2 bytes - nt! ?? ::FNODOBFM::`string'+2d406 (+0xab)
[ 80 f6:00 d8 ]
19 errors : !nt (fffff803d3da3044-fffff803d3da3f97)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE

BUCKET_ID: MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:memory_corruption_large

FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption

Also not sure if this means anything but I downloaded a blue screen checker and most of it were due to this one program
ntoskrnl.exe what does this mean?

 

[Colif]

ntoskrnl = new technology operating system kernel: brains of windows 10, it does lots of things including dealing with driver requests and managing memory. It often gets blamed for driver errors.

IRQ errors are normally driver errors.

you can try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, run the blue screen checker and see what driver it reveals

Note: sometimes this may put you in a boot loop so download the Windows 10 media creation tool and use it to make a win 10 installer on USB, and use it as a boot disc if need be.

 

[Kireur]

ntoskrnl = new technology operating system kernel: brains of windows 10, it does lots of things including dealing with driver requests and managing memory. It often gets blamed for driver errors.

IRQ errors are normally driver errors.

you can try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, run the blue screen checker and see what driver it reveals

Note: sometimes this may put you in a boot loop so download the Windows 10 media creation tool and use it to make a win 10 installer on USB, and use it as a boot disc if need be.

Do i actually need to do this? Because just by running CSGO, i can actually get the BSOD. So do i have to specifically do this or is it as long as i get a BSOD.
Because when i use Bluescreenchecker on the minidump files that I got from the BSOD, it just says its the ntoskrnl.exe that causes it.

 

[Colif]

yes, but ntoskrnl isn't the cause, and blue screen view isn't showing enough, so running driver verifer tests the drivers out and should find actual cause, not windows,

other option is follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

but I can't read dumps so I figure I help with something that just doesn't live you sitting around waiting for an answer