品質効果を再生するたびに、 IRQL_NOT_LESS_OR_EQUAL BLUE画面に表示されます.
このゲームのみが青い画面現象に表示され、すべてメインインターフェイスではなくゲーム、ブルースクリーンに入り、他のゲームにこの現象があるのは
2077
、地下鉄休暇、大3Aゲームなど...
最初はメモリ問題です.メモリを変更した後、この現象は解決します...
1つの起動dump
解析はorigin
のファイル問題です.このブルースクリーンコードは数回、解決しました...
Microsoft(R)WindowsDebugRerversion10.0.21349.1004amd64
`
Copyright(C)Microsoft Corporation.AllRightServed.
MinikerneldumpFile:registersandstacktraceavaiabaiableable
ResponseTime(MS)場所
DEFERREDSRV*
SymbolSearchPathis:srv*
executableAcearchPathis:
windows 10KernelVersion19041MP(16PROCS)FreeX64
製品:Winnt、Suite:TerminalServersingleUserts
MACHINENAME:
kernelbase= 0xffffff8003F200000PSLoadedModuleList= 0xfffff800
`3fe2a490
DebugSessionTime:Thujun2422:53:43.2192021(UTc+ 8:00)
SystemUptime:1日13:07:59.917
LoadingKernelSymbols
.
PRESSCTRL-C(CDB、KD、NTSD)ORCTRL-BREAK(WINDBG)TOABORTSYMBOLLADSTHATTAKETOOUTOONTOOUTOUTOONG.
実行!symnoisybefore.ReloadTotRackDownProblemSloadingSymbols.
..........................................................
...........................................................
...........................................................
............
LoadingUsersySymbols
LoadingUnloadedModuleList
.........................
前分析:
!Analyze-V
NT!Kebugcheckex:
`
FFFFF8003F5F5DB048894C2408MOVQWORDPTR [RSP + 8]
RCXSS:FFFDDD06
`3eeeff0= 000000000000000A
!
5:KD>Analyze-V
**
*BugCheckAnalysis*
**
IRQL_NOT_LESS_OR_EQUAL(a)
anattemptwasmadeToAccessapable(orcompletelyInvalid)addressatan
InterrupTrequestLevel(IRQL)ThatisTooHigh.thisusususususususususususususususususususususususususususususususususususususususususususususususususususususususususususususususususususus
GEASEBYDRIVERSUSINGIMPROPERADDRESSES.
ifakenettebuggerisavailableGetStackBacktrace.
引数:
arg1:0000000FFFFFFFF、MemoryReferenced
arg2:0000000000000002、iRQL
arg3:0000000000000001、ビットフィールド:bit0:value0= readoperty、1= writeOperation
bit3:value0= notAnexecuteOperation、1= executeOperation(OnolonChipSwhichSupportThisleVelofStatus)
ARG4:FFFFF8003F412D8B、AddressWhiChreferenceEncestMory
DebuggingDetails:
key_values_string:1
!
key:analyysis.cpu.msec
値:2046
キー:AnalyInsis.DebugAnalysis管理
value:create
key:analyysis.lapsed.msec
値:3695
key:analyysis.init.cpu.msec
値:280
key:AnalyInsion.init.elapsed.msec
値:7604
key:AnalyInsist.Memory.commitpeak.mb
値:76
dump_file_attributes:0x8
kernelgeneratedtriagedump
bugheck_code:a
bugheck_p1:ffffffffff
bugcheck_p2:2
bugcheck_p3:1
BUGCHECK_P4:FFFFF8003F412D8B
write_address:fffff8003fefb390:UnableTogetMivisibleState
UnableTogetNonpagedPoolStart
UNABLETOGETNONPAGEDPOOLEND
UnableTogetPagetPoolStart
UnableTogetPagedPoolend
UNABLETOGETNTMMSPecialPagesInuse
の
0000000ffffffffffffBlackBoxBSD:1(
!ブラックボックスBS)
!
blackboxntfs:1(blackboxntfs)
!
blackboxpnp:1(blackboxpnp)
ブラックボックスウィンロゴン:1
customer_crash_count:1
process_name:masseffectandr
trap_frame:fffdd063eef130-(.trap0xffffdddddd063eeaf130)
注:ThetrameDoesnotContainallRegisters
SomEregistervalesMayBezeroedorinkorRecordorecorred.
rax= 0000000000000000000RBx= 0000000000000000000RCX= 0000000FFFFFFFFF
RDX= 000000000000000000000000000000000
RIP= FFFFFF8003F412D8BRSP= FFFDDD063EEF2C0RBP= FFFDDD063EEF3C0
R8= 00000000000000000R9= 0000000FFFFFFFFFR10= FFFFFFF000000000
r11= fffdddd063eef290r12= 0000000000000000000000000000000000
R14= 00000000000000000000
iopl= 0 nvupeiplzrnaponc
NT!MigetPageChain + 0xBAB:
!
FFFFF800
3F412D8B0F8262010000JBNTMigetPagageChain + 0xD13(FFFFF800
`3F412EF3)[BR= 0]
`
ResettingDefaultScope
stack_text:
FFFDDD06
3EEEEFE8FFFF8003F607D69:00000000
0000000A0000000FFFFFFF00000000
0000000200000000
!
00000001:NTKebugchex
`
fffddd06
3eeff0ffff8003F604069:FFFFFFF
fffffff000000`
00000000FFFF9F80
`13FA6F8FFFFFF800
!
3f4ea255:NTKibugCheckDispatch + 0x69
`
fffddd063eeaf130fffff800
`3F412D8B:8a000007
`
70C1B863FFFCD01
!
00770c1b:NTKipageFault + 0x469
FFFDDD06
3EEEF2C0FFFFFF800
3F40FCD8:FFFDDD06
3eef600000000`
00000000FFFCD01
!
A47DD180:NTMigetPagageChain + 0xBAB
FFFDDD06
3EEEF500FFFFF800
3F40F228:FFFDD06
3EEEF690FFFFDD06`
0000000000000000
00000000:NT
!MireSolvePrivateZeroFault + 0x6e8
`
fffddd063eeeaf630FFFFF800
`00000000
`00000000200000000
`
0000000000000000
00000002:NT
!MireesolvedMandzeroFault + 0x208
`
FFFDDD06
3EEEF720FFFF800
3F40C6E9:FFFA50E
05D07540FFFA50E
c0000016000000000000000000000000:NT
!MidispatchFault + 0x22D
`
fffddd063eeeaf860ffff800
`00000000
0000000000
0000000100000000
`
A951FB68FFFDD06
`3EEFA80:NT
!MMAccessFault + 0x189
FFFDDD06
3EEEFA0000007FFF
CC58A62D:00000000
0000000000000000000000000000
`
000000000000002 0000000000000000
!
00000000:NTKipageFault + 0x35E
00000000
00000000:0000000000000000000000
00000000000000
0000000000000000
`0000000000000000
00000000:0x00007FFF0000000000000000
00000000000000CC58A62D
!
symbol_name:ntMigetPageChain + BAB
!
module_name:nt
image_version:10.0.19041.906
stack_command:.thread;
.cxr;
KB
image_name:ntkrnlmp.exe
BUCKET_ID_FUNC_OFFSET:BAB
failure_bucket_id:av_ntMigetPageChain
osplatform_type:x64
osname:windows 10
failure_id_hash:{0e6728ab-CF4F-0CE6-A21D-B2680731698A}
フォローアップ:MachineOwner
返信リスト(回答:1)
こんにちは!
Windows 10
Blue Screen、
情報を統合するために、あなたが遭遇した問題を解決するのを助けます
繰り返しの繰り返しの投稿をお勧めしません.フォローアップと返信のための積極的な投稿に集中することをお勧めします.
あなたが遭遇した問題を解決するのを助けることを楽しみにして...
注:この投稿は閉じられ、もう一度返信しないでください...