Question Pc Crash Minidump Share

[volkanaavci]

Hello.

************* Preparing the environment for debugger extensions gallery repositories **************
Extensionrepository : Implicit.
Useexperimentalfeaturefornugetshare : True.
Allownugetexeupdate : True.
Nonınteractivenuget : True.
Allownugetmscredentialproviderınstall : True.
Allowparallelınitializationoflocalrepositories : True.
Enableredirecttov8jsprovider : False.
-- Configuring repositories.
----> Repository : Localınstalled, enabled: True.
----> Repository : Userextensions, enabled: True.

>>>>>>>>> Preparing the environment for debugger extensions gallery repositories completed, duration 0.000 seconds.

************* Waiting for debugger extensions gallery to ınitialize **************

>>>>>>>>> Waiting for debugger extensions gallery to ınitialize completed, duration 0.015 seconds.

----> Repository : Userextensions, enabled: True, packages count: 0
----> Repository : Localınstalled, enabled: True, packages count: 41.

Microsoft (r) Windows debugger version 10.0.27553.1004 AMD64.
Copyright (C) Microsoft Corporation. All rights reserved.

Loading dump file [C:\Users\volka\Desktop\031824-10031-01.dmp]
Mini kernel dump file: Only registers and stack trace are available.

Symbol Search path is: Srv*
Executable Search path is:
Windows 10 kernel version 22621 MP (12 procs) Free X64.
Product: Winnt, Suite: Terminalserver singleuserts.
Kernel base = 0xfffff802`23000000 psloadedmodulelist = 0xfffff802`23c13530
Debug session time: Mon mar 18 05:52:00.700 2024 (utc + 3:00)
System uptime: 1 days 5:00:10.295
Loading kernel symbols.
..

Press CTRL-C (cdb, kd, ntsd) or CTRL-break (WinDbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
..............................................................
Loading user symbols.
Peb is paged out (peb.ldr = 00000000'010A1018). Type ".hh dbgerr001" for details.
Loading unloaded module list.
...............
For analysis of this file, run !analyze -v
NT!kebugcheckex:
Fffff802'234177F0 48894C2408 mov qword ptr [rsp+8],rcx SS:0018:ffffa686'74ef6030 = 000000000000003B.
2: Kd> !analyze -v
*******************************************************************************

• *
• Bugcheck analysis *
• *

*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a System service routine.
Arguments:
Arg1: 00000000C0000005, exception code that caused the bugcheck.
Arg2: FffFF8022322C74C, address of the instruction which caused the bugcheck.
Arg3: FffFA68674Ef6980, address of the context record for the exception that caused the bugcheck.
Arg4: 0000000000000000, Zero.

Debugging details:
------------------

Key_values_strıng: 1

Key : Analysis.CPU.msec
Value: 1125.

Key : Analysis.elapsed.msec
Value: 11056.

Key : Analysis.I😵ther.MB
Value: 28.

Key : Analysis.IO.read.MB
Value: 0

Key : Analysis.IO.write.MB
Value: 34.

Key : Analysis.ınit.CPU.msec
Value: 281.

Key : Analysis.ınit.elapsed.msec
Value: 490312.

Key : Analysis.Memory.commitpeak.MB
Value: 100.

Key : Bugcheck.code.legacyapı
Value: 0x3b.

Key : Bugcheck.code.targetmodel
Value: 0x3b.

Key : Dump.attributes.asulong
Value: 1008.

Key : Dump.attributes.diagdatawrittentoheader
Value: 1

Key : Dump.attributes.errorcode
Value: 0

Key : Dump.attributes.kernelgeneratedtriagedump
Value: 1

Key : Dump.attributes.lastline
Value: Dump completed successfully.

Key : Dump.attributes.progresspercentage
Value: 0

Key : Failure.bucket
Value: Av_dxgkrnl!operator_new

Key : Failure.hash
Value: {C60F340F-4F53-1790-5405-773A900F1A75}

Bugcheck_code: 3B.

Bugcheck_p1: C0000005.

Bugcheck_p2: FffFF8022322C74C.

Bugcheck_p3: FFFFA68674EF6980.

Bugcheck_p4: 0

Fıle_ın_cab: 031824-10031-01.dmp

Dump_fıle_attrıbutes: 0x1008.
Kernel generated triage dump.

Context: FFFFA68674EF6980 -- (.cxr 0xffffa68674ef6980)
Rax = fff7E28BCB79e888 rbx = 0000000000000008 rcx = 0000000000000000.
Rdx = fffFE28BD1B55888 rsi = 0000000000000000 rdi = 0000000000000000.
Rip = fffFF8022322C74C rsp = fffFA68674Ef73a0 rbp = 0000000000000000.
R8 = fffFE28BD1B55888 R9 = fffFE28BD1B55898 R10 = fffFE28BBE6002D0.
R11 = fffFE28BC79D1888 R12 = fffFE28BC79D1888 R13 = fffFE28BC225a000.
R14 = fffFE28BC2324038 R15 = fffFE28BC8A80FE8.
İopl = 0 nv up ei pl zrna po nc.
CS = 0010 SS = 0018 DS = 002b es = 002b FS = 0053 GS = 002b efl = 00050246.
NT!rtlrbremovenode+0x50C:
Fffff802'2322C74C F6401001 test byte ptr [rax+10h],1 DS:002b:fff7e28b'CB79E898=??
Resetting default scope.

Blackboxbsd: 1 (!blackboxbsd)

Blackboxntfs: 1 (!blackboxntfs)

Blackboxpnp: 1 (!blackboxpnp)

Blackboxwınlogon: 1

Customer_crash_count: 1

Process_name: explorer.exe

Stack_text:
Ffffa686'74ef73a0 fffff802'2322ADD1 : 00000000'00000000 ffffa686'74ef75A1 00000000'0000004D 00000000'00000000 : NT!rtlrbremovenode+0x50C
Ffffa686'74ef73D0 fffff802'2322ABE7 : Ffffa686'74ef7bc8 00000000'00000000 00000000'00000000 fffff802'23C143e0 : NT!rtlphpvschunksplit+0x41
Ffffa686'74ef7470 fffff802'2325735E : 00000000'0000004D 00000000'000004C0 ffffce81'0000004E 00000010'23210519 : NT!rtlphpvscontextallocateınternal+0x227
Ffffa686'74ef74e0 fffff802'23256C1F : 00000000'00000000 ffffe28b'cbc7D9a0 00000000'4B677844 00000000'000000FF : NT!exallocateheappool+0x70e
Ffffa686'74ef7600 fffff802'23aad68D : 00000000'00000102 00000000'00000001 00000000'00000001 00000001'00000000 : NT!expallocatepoolwithtagfromnode+0x5F
Ffffa686'74ef7650 fffff802'3C8174F2 : Ffffa686'74ef7C5C 00000000'00000000 00000000'00000000 00000000'00020000 : NT!exallocatepool2+0xdd
Ffffa686'74ef7700 fffff802'3C99D329 : 80000002'2042C867 00000000'00000000 ffffa686'74ef77D0 ffffe28b'cca0A820 : Dxgkrnl!operator New+0x32
Ffffa686'74ef7730 fffff802'3C99C5A0 : Ffff868D'09a2fd00 ffffa686'74ef7EA0 00000000'00000000 ffffffff'ffffffff : Dxgkrnl!dxgdevıce::createallocation+0xb49
Ffffa686'74ef7b50 fffff802'3C9dd4bb : 00007FFB'05A30000 00000000'00000010 ffff868D'10e84080 00000000'00000001 : Dxgkrnl!dxgkcreateallocationınternal+0x5e0
Ffffa686'74ef7df0 fffff802'2342C9E8 : Ffff868D'10e84080 00000000'00000000 00000000'0C33E440 ffff868D'00000000 : Dxgkrnl!dxgkcreateallocation+0xb
Ffffa686'74ef7e20 00007FFB'02F34C34 : 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000 : NT!kisystemservicecopyend+0x28
00000000'04265C58 00000000'00000000 : 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000 : 0x00007ffb`02f34c34

Stack_command: .process /r /p 0x3f800000; .cxr 0xffffa68674ef6980 ; KB.

Symbol_name: Dxgkrnl!operator New+32

Module_name: Dxgkrnl.

Image_name: dxgkrnl.sys

Image_versıon: 10.0.22621.3296

Bucket_ıd_func_offset: 32.

Faılure_bucket_ıd: Av_dxgkrnl!operator_new

Osplatform_type: X64.

Osname: Windows 10.

Faılure_ıd_hash: {C60F340F-4F53-1790-5405-773A900F1A75}

Followup: Machineowner.
---------

https://drive.google.com/file/d/1pv1BBWgEu-mXFgRR_MPlbcu34fIynPjy/view

 

[Lutfij]

explorer.exe
+
dxgkrnl.sys
Where did you source the installer for your OS?

 

[ubuysa]

I can see that you're running the vgk.sys driver, for the Riot Vanguard anti-cheat feature. Whilst this driver is not explicitly referenced in the dump, the BSOD occurred during a graphics operation so I suspect you were gaming at the time. In addition, the bugcheck happened in a function of the Windows runtime library which makes it even more possible that vgk.sys was the root cause.

The vgk.sys driver is a very common cause of BSODs, as are all of the anti-cheat tools TBH.

The version of vgk.sys that you have installed is recent...

2: kd> lmDvmvgk
Browse full module list
start             end                 module name
fffff802`39280000 fffff802`3a733000   vgk        (deferred)           
    Image path: vgk.sys
    Image name: vgk.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Feb 22 17:10:07 2024 (65D763CF)
    CheckSum:         014DD0EE
    ImageSize:        014B3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

But this is still the most likely cause.

You don;t give us any details about what you were doing at the time, but if you can reboot (to unload vgk.sys), then try stressing the system without running any games that require Riot Vanguard and see whether it still BSODs.

 

[Satan-IR]

I agree with above about the VKG driver. In general these kinds of software and their drivers are sometimes the source of a lot of trouble not worth their usefulness (whatever that may be).

Also please confirm, is your board Gigabyte B450M S2H (rev. 1.x)?

If yes, the BIOS installed at time the dump file was created appears to be F64.

There is a newer version (F65) dated 27 Feb. 2024 on motherboard website. It includes an update to AGESA. Perhaps updating the BIOS would fix any other issues now or prevent problems in future.

 

[volkanaavci]

explorer.exe
+
dxgkrnl.sys
Where did you source the installer for your OS?

from windows own site.

 

[volkanaavci]

Yes the motherboard is not up to date. thank you i will update

I agree with above about the VKG driver. In general these kinds of software and their drivers are sometimes the source of a lot of trouble not worth their usefulness (whatever that may be).

Also please confirm, is your board Gigabyte B450M S2H (rev. 1.x)?

If yes, the BIOS installed at time the dump file was created appears to be F64.

There is a newer version (F65) dated 27 Feb. 2024 on motherboard website. It includes an update to AGESA. Perhaps updating the BIOS would fix any other issues now or prevent problems in future.

thank you.

 

[volkanaavci]

Vanguard is causing the problem. What exactly should I do?

I can see that you're running the vgk.sys driver, for the Riot Vanguard anti-cheat feature. Whilst this driver is not explicitly referenced in the dump, the BSOD occurred during a graphics operation so I suspect you were gaming at the time. In addition, the bugcheck happened in a function of the Windows runtime library which makes it even more possible that vgk.sys was the root cause.

The vgk.sys driver is a very common cause of BSODs, as are all of the anti-cheat tools TBH.

The version of vgk.sys that you have installed is recent...

2: kd> lmDvmvgk
Browse full module list
start             end                 module name
fffff802`39280000 fffff802`3a733000   vgk        (deferred)          
    Image path: vgk.sys
    Image name: vgk.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Feb 22 17:10:07 2024 (65D763CF)
    CheckSum:         014DD0EE
    ImageSize:        014B3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

But this is still the most likely cause.

You don;t give us any details about what you were doing at the time, but if you can reboot (to unload vgk.sys), then try stressing the system without running any games that require Riot Vanguard and see whether it still BSODs.

 

[ubuysa]

Contact Valorant support and take this up with them.