BSOD when closing valorant


  1. Zoaz324
    Posts : 1
    Windows 10
       New #1

    BSOD when closing valorant


    So this happened 4 times already to me, I tried everything to updating bios, deleting and uninstalling Valorant, checking my laptop for faulty hardware nothing is wrong with my laptop, and updating everything, and checking for errors in cmd. I emailed this to riot and they just gave me the same reply and i gave them logs too

    my pc is a asus vivobook with ryzen 3 3250u apu

    heres my dump file:
    012022-10765-01
      My Computer
    Quote Quote

  3. tomdsr
    Posts : 890
    10 Pro/11 Pro Dual Boot
       New #2

    Zoaz324 said:
    So this happened 4 times already to me, I tried everything to updating bios, deleting and uninstalling Valorant, checking my laptop for faulty hardware nothing is wrong with my laptop, and updating everything, and checking for errors in cmd. I emailed this to riot and they just gave me the same reply and i gave them logs too

    my pc is a asus vivobook with ryzen 3 3250u apu

    heres my dump file:
    012022-10765-01
    You'll need to contact valorant support as this is an issue soley with that executable.

    3: 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: ffffd40b39618a23, 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: fffff805670891a4, address which referenced memory

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

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

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 2733

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 13241

    Key : Analysis.Init.CPU.mSec
    Value: 733

    Key : Analysis.Init.Elapsed.mSec
    Value: 13879

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 76

    Key : WER.OS.Branch
    Value: vb_release

    Key : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key : WER.OS.Version
    Value: 10.0.19041.1


    BUGCHECK_CODE: a

    BUGCHECK_P1: ffffd40b39618a23

    BUGCHECK_P2: 2

    BUGCHECK_P3: 0

    BUGCHECK_P4: fffff805670891a4

    READ_ADDRESS: fffff80567afb390: Unable to get MiVisibleState
    Unable to get NonPagedPoolStart
    Unable to get NonPagedPoolEnd
    Unable to get PagedPoolStart
    Unable to get PagedPoolEnd
    unable to get nt!MmSpecialPagesInUse
    ffffd40b39618a23

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXNTFS: 1 (!blackboxntfs)


    BLACKBOXPNP: 1 (!blackboxpnp)


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: VALORANT-Win64-Shipping.exe

    TRAP_FRAME: ffffd08a44db1500 -- (.trap 0xffffd08a44db1500)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffff80566e00000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff805670891a4 rsp=ffffd08a44db1690 rbp=ffffd08a44db17c0
    r8=0000000000000001 r9=0000000000000001 r10=ffffe50554f438a8
    r11=0000000000000076 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na po nc
    nt!ExFreeHeapPool+0x124:
    fffff805`670891a4 f646f304 test byte ptr [rsi-0Dh],4 ds:ffffffff`fffffff3=??
    Resetting default scope

    STACK_TEXT:
    ffffd08a`44db13b8 fffff805`67209269 : 00000000`0000000a ffffd40b`39618a23 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffd08a`44db13c0 fffff805`67205569 : ffffd08a`44db15c0 ffffd40b`3a3a7da8 00000000`00000000 ffffe505`54f43300 : nt!KiBugCheckDispatch+0x69
    ffffd08a`44db1500 fffff805`670891a4 : 00000000`00040283 00000000`00000001 00000000`00000000 fffff805`72bf0000 : nt!KiPageFault+0x469
    ffffd08a`44db1690 fffff805`677b1149 : ffffd08a`44db17c0 00000000`00000700 00000000`00000004 01000000`00100000 : nt!ExFreeHeapPool+0x124
    ffffd08a`44db1770 fffff805`733c2a34 : 00000000`000007e4 ffffe505`54f43300 fffff805`72bf0000 00000000`00000008 : nt!ExFreePool+0x9
    ffffd08a`44db17a0 00000000`000007e4 : ffffe505`54f43300 fffff805`72bf0000 00000000`00000008 fffff805`72bf0000 : vgk+0x7d2a34
    ffffd08a`44db17a8 ffffe505`54f43300 : fffff805`72bf0000 00000000`00000008 fffff805`72bf0000 00000000`00000001 : 0x7e4
    ffffd08a`44db17b0 fffff805`72bf0000 : 00000000`00000008 fffff805`72bf0000 00000000`00000001 00000000`00000000 : 0xffffe505`54f43300
    ffffd08a`44db17b8 00000000`00000008 : fffff805`72bf0000 00000000`00000001 00000000`00000000 00000000`000007e4 : vgk
    ffffd08a`44db17c0 fffff805`72bf0000 : 00000000`00000001 00000000`00000000 00000000`000007e4 ffffd08a`44db1840 : 0x8
    ffffd08a`44db17c8 00000000`00000001 : 00000000`00000000 00000000`000007e4 ffffd08a`44db1840 fffff805`7337b6f0 : vgk
    ffffd08a`44db17d0 00000000`00000000 : 00000000`000007e4 ffffd08a`44db1840 fffff805`7337b6f0 fffff805`670d7a50 : 0x1


    SYMBOL_NAME: nt!ExFreePool+9

    IMAGE_NAME: Pool_Corruption

    IMAGE_VERSION: 10.0.19041.1466

    MODULE_NAME: Pool_Corruption

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 9

    FAILURE_BUCKET_ID: AV_nt!ExFreePool

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {2ae0a97e-dcd7-47ef-dbfb-430f2cbf58a1}

    Followup: Pool_corruption
    ---------

    3: kd> !thread
    THREAD ffffe50557889300 Cid 07e4.1ce8 Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 3
    Not impersonating
    GetUlongFromAddress: unable to read from fffff80567a1150c
    Owning Process ffffe50554f43300 Image: VALORANT-Win64-Shipping.exe
    Attached Process N/A Image: N/A
    fffff78000000000: Unable to get shared data
    Wait Start TickCount 33402695
    Context Switch Count 4159092 IdealProcessor: 3
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    UserTime 00:00:00.000
    KernelTime 00:00:00.000
    Win32 Start Address 0x00007ff7f0e8d000
    Stack Init ffffd08a44db1c90 Current ffffd08a44daf060
    Base ffffd08a44db2000 Limit ffffd08a44dac000 Call 0000000000000000
    Priority 10 BasePriority 9 PriorityDecrement 0 IoPriority 2 PagePriority 5
    Child-SP RetAddr : Args to Child : Call Site
    ffffd08a`44db13b8 fffff805`67209269 : 00000000`0000000a ffffd40b`39618a23 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffd08a`44db13c0 fffff805`67205569 : ffffd08a`44db15c0 ffffd40b`3a3a7da8 00000000`00000000 ffffe505`54f43300 : nt!KiBugCheckDispatch+0x69
    ffffd08a`44db1500 fffff805`670891a4 : 00000000`00040283 00000000`00000001 00000000`00000000 fffff805`72bf0000 : nt!KiPageFault+0x469 (TrapFrame @ ffffd08a`44db1500)
    ffffd08a`44db1690 fffff805`677b1149 : ffffd08a`44db17c0 00000000`00000700 00000000`00000004 01000000`00100000 : nt!ExFreeHeapPool+0x124
    ffffd08a`44db1770 fffff805`733c2a34 : 00000000`000007e4 ffffe505`54f43300 fffff805`72bf0000 00000000`00000008 : nt!ExFreePool+0x9
    ffffd08a`44db17a0 00000000`000007e4 : ffffe505`54f43300 fffff805`72bf0000 00000000`00000008 fffff805`72bf0000 : vgk+0x7d2a34
    ffffd08a`44db17a8 ffffe505`54f43300 : fffff805`72bf0000 00000000`00000008 fffff805`72bf0000 00000000`00000001 : 0x7e4
    ffffd08a`44db17b0 fffff805`72bf0000 : 00000000`00000008 fffff805`72bf0000 00000000`00000001 00000000`00000000 : 0xffffe505`54f43300
    ffffd08a`44db17b8 00000000`00000008 : fffff805`72bf0000 00000000`00000001 00000000`00000000 00000000`000007e4 : vgk
    ffffd08a`44db17c0 fffff805`72bf0000 : 00000000`00000001 00000000`00000000 00000000`000007e4 ffffd08a`44db1840 : 0x8
    ffffd08a`44db17c8 00000000`00000001 : 00000000`00000000 00000000`000007e4 ffffd08a`44db1840 fffff805`7337b6f0 : vgk
    ffffd08a`44db17d0 00000000`00000000 : 00000000`000007e4 ffffd08a`44db1840 fffff805`7337b6f0 fffff805`670d7a50 : 0x1
      My Computers
    Quote Quote

  4. zbook
    Posts : 41,462
    windows 10 professional version 1607 build 14393.969 64 bit
       New #3

    See posting instructions:

    BSOD - Posting Instructions
      My Computer
    Quote Quote

  6. axe0
    Posts : 14,903
    Windows 10 Pro
       New #4

    tomdsr said:
    You'll need to contact valorant support as this is an issue soley with that executable.
    Just for information in case others see it as the cause, it's not the process that caused the exception, the process is shown because in that process the exception was raised. Because in a process a lot of stuff can happen (e.g. networking, I/O operations, ....), the process itself should not be considered as the cause.

    If you check the call stack, it shows that a driver, vgk, makes a call to free pool.
    Code:
    3: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffd08a`44db13b8 fffff805`67209269 nt!KeBugCheckEx
01 ffffd08a`44db13c0 fffff805`67205569 nt!KiBugCheckDispatch+0x69
02 ffffd08a`44db1500 fffff805`670891a4 nt!KiPageFault+0x469
03 ffffd08a`44db1690 fffff805`677b1149 nt!ExFreeHeapPool+0x124
04 ffffd08a`44db1770 fffff805`733c2a34 nt!ExFreePool+0x9
05 ffffd08a`44db17a0 00000000`000007e4 vgk+0x7d2a34
06 ffffd08a`44db17a8 ffffe505`54f43300 0x7e4
07 ffffd08a`44db17b0 fffff805`72bf0000 0xffffe505`54f43300
08 ffffd08a`44db17b8 00000000`00000008 vgk
09 ffffd08a`44db17c0 fffff805`72bf0000 0x8
0a ffffd08a`44db17c8 00000000`00000001 vgk
0b ffffd08a`44db17d0 00000000`00000000 0x1
    Looking specifically at the instruction where the problem occurred, unless my memory is off and the relevant register's value is not saved during a crash, this looks to be subtracting (rsi address - 0Dh) with an address not pointing to anything which isn't possible. Because of the IRQL in parameter 2 of the bugcheck in combination with this operation the crash occurs.
    Code:
    3: kd> .trap 0xffffd08a44db1500
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff80566e00000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff805670891a4 rsp=ffffd08a44db1690 rbp=ffffd08a44db17c0
 r8=0000000000000001  r9=0000000000000001 r10=ffffe50554f438a8
r11=0000000000000076 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!ExFreeHeapPool+0x124:
fffff805`670891a4 f646f304        test    byte ptr [rsi-0Dh],4 ds:ffffffff`fffffff3=??
    The vgk driver looks to be from the anticheat software used by Valorant. Definitely contact Valorant support about this.
      My Computers
    Quote Quote

 

  Related Discussions
Hey guys, so as the title says, 12 minutes after opening the game Valorant, I get the BSOD saying Whea_Uncorrectable_Error. I've tried a bunch of trouble shooting and have been back and forth with their support team over the last two weeks. Nothing...
My computer will randomly blue screen while I'm playing League of Legends/Overwatch or directly after I close the game. I've gone through and updated all my drivers so I'm unsure of the actual problem currently. I've attached what I think may be...
BSOD After Closing 3ds Max
in BSOD Crashes and Debugging

Hi all, I'm getting a BSOD every time I close 3ds Max. Memory dump says nvlddmkm.sys. I did a complete uninstall and install of 372.54 graphics driver. Disabled Nvidia streaming service which I have read can cause problems. Neither helped. I'll...
BSOD when closing computer lid
in BSOD Crashes and Debugging

Hi, every time i close my computer lid, which is supposed to suspend the computer, it instead reboots causing bsod as i can see My computer is an asus n551jx running windows 10. I send the dump file attached thanks for helping 81023
BSOD after closing CS:GO or Dota 2
in BSOD Crashes and Debugging

I tried everything and anything known to man, but I still get these freezes after I close CS:GO for example. It doesn't happen every time, but once a day, it freezes and i have to hard reset the computer. I've reset my windows without keeping the...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 20:51.
Find Us




Windows 10 Forums