Jump to content
_Paulo_

Losowe freezy i restarty Windows 10

Recommended Posts

Hej. Mam problem z komputerem od jakiegos czasu ktory objawia sie glownie w grach i zdecydowanie rzadziej w samym systemie. Nieraz wszystko idzie dobrze przez dluzszy czas a nieraz zlapie zwis na ekranie i reset po krotkiej chwili. Zrobilem zrzut z dmp i moze mnie ktos naprowadzi co jest nie tak bo przeciez nawet sie grac nie chce bo nie wiadomo ile podziala  :kwasny: Dodam ze problem wystepuje z oc i bez. Napiecia mierzone miernikiem pod obciazeniem i bez i wszystko w normie.

Konfig:

-i7 930 @ 4ghz

-Gigabyte X58a Ud3r

-6gb Adata Gaming ddr3 @1600

-Gigabyte GTX1060 6GB

-OCZ Modxstream 600w

 

Zrzut DMP:


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

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 1000007E, {ffffffffc0000005, fffff80ba99e4185, ffff8f80b26ff188, ffff8f80b26fe9d0}

 

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

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : memory_corruption

 

Followup: memory_corruption

---------

 

2: kd> !analyze -v

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

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

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

 

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

This is a very common bugcheck.  Usually the exception address pinpoints

the driver/function that caused the problem.  Always note this address

as well as the link date of the driver/image that contains this address.

Some common problems are exception code 0x80000003.  This means a hard

coded breakpoint or assertion was hit, but this system was booted

/NODEBUG.  This is not supposed to happen as developers should never have

hardcoded breakpoints in retail code, but ...

If this happens, make sure a debugger gets connected, and the

system is booted /DEBUG.  This will let us see why this breakpoint is

happening.

Arguments:

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: fffff80ba99e4185, The address that the exception occurred at

Arg3: ffff8f80b26ff188, Exception Record Address

Arg4: ffff8f80b26fe9d0, Context Record Address

 

Debugging Details:

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

 

 

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja w 0x%p odwo

 

FAULTING_IP: 

nvlddmkm+3a4185

fffff80b`a99e4185 3934a8          cmp     dword ptr [rax+rbp*4],esi

 

EXCEPTION_RECORD:  ffff8f80b26ff188 -- (.exr 0xffff8f80b26ff188)

ExceptionAddress: fffff80ba99e4185 (nvlddmkm+0x00000000003a4185)

   ExceptionCode: c0000005 (Access violation)

  ExceptionFlags: 00000000

NumberParameters: 2

   Parameter[0]: 0000000000000000

   Parameter[1]: 0000000000000000

Attempt to read from address 0000000000000000

 

CONTEXT:  ffff8f80b26fe9d0 -- (.cxr 0xffff8f80b26fe9d0;r)

rax=0000000000000000 rbx=0000000000000017 rcx=ffffa68a429b2a10

rdx=0000000000000017 rsi=0000000000000000 rdi=ffffa68a47133170

rip=fffff80ba99e4185 rsp=ffff8f80b26ff3c0 rbp=0000000000000000

 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000

r11=ffff8f80b26ff3f0 r12=ffffa68a40755000 r13=ffffa68a40cc0000

r14=ffffa68a498949b0 r15=ffffa68a42cc26f0

iopl=0         nv up ei pl zr na po nc

cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246

nvlddmkm+0x3a4185:

fffff80b`a99e4185 3934a8          cmp     dword ptr [rax+rbp*4],esi ds:002b:00000000`00000000=00000000

Last set context:

rax=0000000000000000 rbx=0000000000000017 rcx=ffffa68a429b2a10

rdx=0000000000000017 rsi=0000000000000000 rdi=ffffa68a47133170

rip=fffff80ba99e4185 rsp=ffff8f80b26ff3c0 rbp=0000000000000000

 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000

r11=ffff8f80b26ff3f0 r12=ffffa68a40755000 r13=ffffa68a40cc0000

r14=ffffa68a498949b0 r15=ffffa68a42cc26f0

iopl=0         nv up ei pl zr na po nc

cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246

nvlddmkm+0x3a4185:

fffff80b`a99e4185 3934a8          cmp     dword ptr [rax+rbp*4],esi ds:002b:00000000`00000000=00000000

Resetting default scope

 

CUSTOMER_CRASH_COUNT:  1

 

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

 

PROCESS_NAME:  System

 

CURRENT_IRQL:  0

 

ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja w 0x%p odwo

 

EXCEPTION_PARAMETER1:  0000000000000000

 

EXCEPTION_PARAMETER2:  0000000000000000

 

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPagedPoolEnd

unable to get nt!MmNonPagedPoolStart

unable to get nt!MmSizeOfNonPagedPoolInBytes

 0000000000000000 

 

FOLLOWUP_IP: 

nvlddmkm+3a4185

fffff80b`a99e4185 3934a8          cmp     dword ptr [rax+rbp*4],esi

 

BUGCHECK_STR:  AV

 

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre

 

EXCEPTION_STR:  0x0

 

LAST_CONTROL_TRANSFER:  from 0000000000000001 to fffff80ba99e4185

 

STACK_TEXT:  

ffff8f80`b26ff3c0 00000000`00000001 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffa68a`00000000 : nvlddmkm+0x3a4185

ffff8f80`b26ff3c8 00000000`00000000 : 00000000`00000000 00000000`00000000 ffffa68a`00000000 ffff5ff9`fe487e0d : 0x1

 

 

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt

    fffff80314e8fd27-fffff80314e8fd28  2 bytes - nt!MiResolvePageTablePage+3b7

[ ff f6:7f f9 ]

    fffff80314e8fd48-fffff80314e8fd4c  5 bytes - nt!MiResolvePageTablePage+3d8 (+0x21)

[ df be 7d fb f6:2f 5f be 7c f9 ]

    fffff80315082383-fffff80315082385  3 bytes - nt!ExFreePoolWithTag+363

[ 40 fb f6:80 7c f9 ]

10 errors : !nt (fffff80314e8fd27-fffff80315082385)

 

MODULE_NAME: memory_corruption

 

IMAGE_NAME:  memory_corruption

 

FOLLOWUP_NAME:  memory_corruption

 

DEBUG_FLR_IMAGE_TIMESTAMP:  0

 

MEMORY_CORRUPTOR:  LARGE

 

STACK_COMMAND:  .cxr 0xffff8f80b26fe9d0 ; kb

 

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

 

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

 

ANALYSIS_SOURCE:  KM

 

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

 

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

 

Followup: memory_corruption

---------


Edited by _Paulo_

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


Aktualności

Artykuły



×
×
  • Create New...