1070 Ti sistemde BIOS güncellemesi sonrası mavi ekran hatası

Merhabalar. Bios güncellemesi yaptım. Valorant girince böyle bir hata verdi:


************* Preparing the environment for Debugger Extensions Gallery repositories **************

ExtensionRepository : Implicit

UseExperimentalFeatureForNugetShare : true

AllowNugetExeUpdate : true

NonInteractiveNuget : true

AllowNugetMSCredentialProviderInstall : true

AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToChakraJsProvider : false



-- Configuring repositories

----> Repository : LocalInstalled, Enabled: true

----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

Genişletmek için tıkla...

Genişletmek için tıkla...

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds

Genişletmek için tıkla...

Genişletmek için tıkla...

----> Repository : UserExtensions, Enabled: true, Packages count: 0

----> Repository : LocalInstalled, Enabled: true, Packages count: 42



Microsoft (R) Windows Debugger Version 10.0.27668.1000 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Windows\Minidump\081124-16859-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 19041 MP (6 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0xfffff804`68200000 PsLoadedModuleList = 0xfffff804`68e2a820

Debug session time: Sun Aug 11 00:03:08.858 2024 (UTC + 3:00)

System Uptime: 0 days 0:07:24.568

Loading Kernel Symbols

...............................................................

................................................................

...................................................

Loading User Symbols

PEB is paged out (Peb.Ldr = 0000009e`a8ad7018). Type ".hh dbgerr001" for details

Loading unloaded module list

......

For analysis of this file, run !analyze -v

nt!KiOpIsPrefix+0x34:

fffff804`6855d560 3811 cmp byte ptr [rcx],dl ds:002b:00000000`0000007f=??

1: kd> !analyze -v

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

• *
• Bugcheck Analysis *
• *

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



UNEXPECTED_KERNEL_MODE_TRAP (7f)

This means a trap occurred in kernel mode, and it's a trap of a kind

that the kernel isn't allowed to have/catch (bound trap) or that

is always instant death (double fault). The first number in the

BugCheck params is the number of the trap (8 = double fault, etc)

Consult an Intel x86 family manual to learn more about what these

traps are. Here is a portion of those codes:

If kv shows a taskGate

use .tss on the part before the colon, then kv.

Else if kv shows a trapframe

use .trap on that value

Else

.trap on the appropriate frame will show where the trap was taken

(on x86, this will be the ebp that goes with the procedure KiTrap)

Endif

kb will then show the corrected stack.

Arguments:

Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT

Arg2: ffffd601d1fdce70

Arg3: 000000004c2d7440

Arg4: fffff8046855d560



Debugging Details:

------------------





KEY_VALUES_STRING: 1



Key : Analysis.CPU.mSec

Value: 2686



Key : Analysis.Elapsed.mSec

Value: 8523



Key : Analysis.IO.Other.Mb

Value: 15



Key : Analysis.IO.Read.Mb

Value: 1



Key : Analysis.IO.Write.Mb

Value: 21



Key : Analysis.Init.CPU.mSec

Value: 671



Key : Analysis.Init.Elapsed.mSec

Value: 636005



Key : Analysis.Memory.CommitPeak.Mb

Value: 84



Key : Bugcheck.Code.LegacyAPI

Value: 0x1000007f



Key : Bugcheck.Code.TargetModel

Value: 0x1000007f



Key : Dump.Attributes.AsUlong

Value: 8



Key : Dump.Attributes.KernelGeneratedTriageDump

Value: 1



Key : Failure.Bucket

Value: 0x7f_8_STACKPTR_ERROR_nt!KiOpIsPrefix



Key : Failure.Hash

Value: {86e96a3d-759a-3843-e965-febfa54be9e1}





BUGCHECK_CODE: 7f



BUGCHECK_P1: 8



BUGCHECK_P2: ffffd601d1fdce70



BUGCHECK_P3: 4c2d7440



BUGCHECK_P4: fffff8046855d560



FILE_IN_CAB: 081124-16859-01.dmp



DUMP_FILE_ATTRIBUTES: 0x8

Kernel Generated Triage Dump



FAULTING_THREAD: ffff8f0af7785080



BAD_STACK_POINTER: 000000004c2d7440



BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXNTFS: 1 (!blackboxntfs)





BLACKBOXWINLOGON: 1



CUSTOMER_CRASH_COUNT: 1



PROCESS_NAME: VALORANT-Win64



STACK_TEXT:

00000000`4c2d7440 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiOpIsPrefix+0x34





SYMBOL_NAME: nt!KiOpIsPrefix+34



MODULE_NAME: nt



IMAGE_NAME: ntkrnlmp.exe



IMAGE_VERSION: 10.0.19041.4648



STACK_COMMAND: .process /r /p 0xffff8f0af4144080; .thread 0xffff8f0af7785080 ; kb



BUCKET_ID_FUNC_OFFSET: 34



FAILURE_BUCKET_ID: 0x7f_8_STACKPTR_ERROR_nt!KiOpIsPrefix



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {86e96a3d-759a-3843-e965-febfa54be9e1}



Followup: MachineOwner

---------