Skocz do zawartości
Modryyy

Po Aktualizacji sterowników restartuje sie

Przez Modryyy, w Sterowniki, BIOS, UEFI

Rekomendowane odpowiedzi

Modryyy Newbie

Modryyy

Opublikowano
Opublikowano (edytowane)

Komputer

MSI RX5700 Gaming X

Ryzen 5 3600

Msi B450 A Pro max

PSU: Vero M2  od SillentiumPC

RAM: IRDM PRO 2x 8 gb 3600

 

Po aktualizacji sterowników do karty graficznej komputer się resetuje z takimi błędami: IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION

W ogóle po złożeniu kompa lubiał się restartować więc były wymieniane ramy od viperów po te co są teraz, ale potem doszły do ładu z jednymi sterownikami i przestał sie restartować. A po ostatniej aktualizacji to wszystko wróciło, nie jest podkrecany itd. Potem wróciłem do tych sterow i nie pomogło.
MiniDumpy wkładam do spoilerów:

Spoiler 



Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Administrator\Downloads\040421-10453-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff805`2d000000 PsLoadedModuleList = 0xfffff805`2dc2a490
Debug session time: Sun Apr  4 12:48:41.589 2021 (UTC + 2:00)
System Uptime: 0 days 0:00:38.252
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
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
2: 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: fffff30000000000, 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: fffff8052d29e6b6, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-31NBVB7

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 7

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

    Key  : Analysis.System
    Value: CreateObject


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  a

BUGCHECK_P1: fffff30000000000

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8052d29e6b6

READ_ADDRESS: fffff8052dcfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8052dc0f330: Unable to get Flags value from nt!KdVersionBlock
fffff8052dc0f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 fffff30000000000 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  ffff8e8bc0b3ed30 -- (.trap 0xffff8e8bc0b3ed30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff379bcde6000 rbx=0000000000000000 rcx=000000000000001f
rdx=fffff30000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8052d29e6b6 rsp=ffff8e8bc0b3eec0 rbp=fffff379bcde67f8
 r8=fffff30000000000  r9=000000000000000f r10=ffffa6853e64b090
r11=ffff817ee4000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiClearPteAccessed+0x776:
fffff805`2d29e6b6 498b10          mov     rdx,qword ptr [r8] ds:fffff300`00000000=????????????????
Resetting default scope

STACK_TEXT:  
ffff8e8b`c0b3ebe8 fffff805`2d407b69 : 00000000`0000000a fffff300`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff8e8b`c0b3ebf0 fffff805`2d403e69 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff8e8b`c0b3ed30 fffff805`2d29e6b6 : 00000000`00000000 fffffddb`afa03fbe 00000000`00000000 fffff805`2d2eb40f : nt!KiPageFault+0x469
ffff8e8b`c0b3eec0 fffff805`2d29dcb5 : ffffa685`4d949700 ffffa685`3e64b090 00000000`00000000 ffff9180`570a5f38 : nt!MiClearPteAccessed+0x776
ffff8e8b`c0b3ef40 fffff805`2d29da9f : ffff8e8b`c0b3f560 fffff301`289c0a90 ffffca80`04b1ef30 00000000`00000000 : nt!MiAgePteWorker+0x1e5
ffff8e8b`c0b3efa0 fffff805`2d20b9e6 : ffff8e8b`c0b3f560 fffff301`289c0a90 00000000`00000000 80000001`90a51867 : nt!MiAgePte+0x51f
ffff8e8b`c0b3f040 fffff805`2d20bafb : fffff379`00000000 ffffa685`4d949700 00000000`00000000 ffff8e8b`c0b3f5b0 : nt!MiWalkPageTablesRecursively+0x776
ffff8e8b`c0b3f0e0 fffff805`2d20bafb : fffff379`bcc04a20 ffffa685`4d949700 00000000`00000001 ffff8e8b`c0b3f5c0 : nt!MiWalkPageTablesRecursively+0x88b
ffff8e8b`c0b3f180 fffff805`2d20bafb : fffff379`bcc04000 ffffa685`4d949700 00000000`00000002 ffff8e8b`c0b3f5d0 : nt!MiWalkPageTablesRecursively+0x88b
ffff8e8b`c0b3f220 fffff805`2d25de6b : 00000000`00000002 ffffa685`4d949700 ffff8e8b`00000003 ffff8e8b`c0b3f5e0 : nt!MiWalkPageTablesRecursively+0x88b
ffff8e8b`c0b3f2c0 fffff805`2d25d901 : ffff8e8b`c0b3f560 00000000`00000000 00000000`00000002 00000000`00000000 : nt!MiWalkPageTables+0x36b
ffff8e8b`c0b3f3c0 fffff805`2d25d009 : 00000000`00000000 00000000`00000000 ffff9180`591a51c0 00000000`00000000 : nt!MiAgeWorkingSet+0x3d1
ffff8e8b`c0b3f8d0 fffff805`2d25c817 : 00000000`00000000 ffff8e8b`c0b3fa80 ffff8e8b`c0b3fa40 00000000`00000000 : nt!MiTrimOrAgeWorkingSet+0x3c9
ffff8e8b`c0b3f9c0 fffff805`2d240560 : fffff805`2dc50d40 ffff8e8b`c0b3fa80 00000000`00000026 ffff9180`00000200 : nt!MiProcessWorkingSets+0x227
ffff8e8b`c0b3fa60 fffff805`2d3b4f57 : 00000000`00000003 00000000`00000003 00000000`ffffffff ffff9180`571d6180 : nt!MiWorkingSetManager+0x110
ffff8e8b`c0b3fb20 fffff805`2d317e85 : ffffa685`3e6a7040 00000000`00000080 fffff805`2d3b4e00 00053337`00000008 : nt!KeBalanceSetManager+0x157
ffff8e8b`c0b3fc10 fffff805`2d3fd2a8 : ffff9180`57500180 ffffa685`3e6a7040 fffff805`2d317e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8e8b`c0b3fc60 00000000`00000000 : ffff8e8b`c0b40000 ffff8e8b`c0b3a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!MiClearPteAccessed+776

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.867

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  776

FAILURE_BUCKET_ID:  AV_nt!MiClearPteAccessed

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d44d98a4-381b-7e6c-a0d0-94a2c94e95b5}

Followup:     MachineOwner
---------

 

Spoiler 



Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Administrator\Downloads\032921-11468-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff805`11000000 PsLoadedModuleList = 0xfffff805`11c2a490
Debug session time: Mon Mar 29 18:24:32.570 2021 (UTC + 2:00)
System Uptime: 0 days 0:46:30.215
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
Loading unloaded module list
............
For analysis of this file, run !analyze -v
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
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: ffff8980c4094e70
Arg3: 0000000000000000
Arg4: fffff8051dc0838d

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-31NBVB7

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 5

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

    Key  : Analysis.System
    Value: CreateObject


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffff8980c4094e70

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8051dc0838d

BAD_STACK_POINTER:  0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  opera.exe

STACK_TEXT:  
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgkSubmitCommandInternal+0x1bd


SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  INVALID_KERNEL_CONTEXT_0x7f_8

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7dec4a1f-e7bf-6cb5-680a-3c5c14a52b06}

Followup:     MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
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: ffff8980c4094e70
Arg3: 0000000000000000
Arg4: fffff8051dc0838d

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-31NBVB7

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 2

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

    Key  : Analysis.System
    Value: CreateObject


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffff8980c4094e70

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8051dc0838d

BAD_STACK_POINTER:  0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  opera.exe

STACK_TEXT:  
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgkSubmitCommandInternal+0x1bd


SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  INVALID_KERNEL_CONTEXT_0x7f_8

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7dec4a1f-e7bf-6cb5-680a-3c5c14a52b06}

Followup:     MachineOwner
---------

 

 

Edytowane przez Modryyy

Udostępnij tę odpowiedź

Odnośnik do odpowiedzi
Udostępnij na innych stronach

Dołącz do dyskusji

Możesz dodać zawartość już teraz a zarejestrować się później. Jeśli posiadasz już konto, zaloguj się aby dodać zawartość za jego pomocą.

Gość
Dodaj odpowiedź do tematu...

×   Wklejono zawartość z formatowaniem.   Przywróć formatowanie

  Dozwolonych jest tylko 75 emoji.

×   Odnośnik został automatycznie osadzony.   Przywróć wyświetlanie jako odnośnik

×   Przywrócono poprzednią zawartość.   Wyczyść edytor

×   Nie możesz bezpośrednio wkleić grafiki. Dodaj lub załącz grafiki z adresu URL.

Ładowanie
×
Tematy
×
×
  • Dodaj nową pozycję...