Veit ikke om dette er riktig?
SPOILER ALERT! Vis spoiler
* *
* Bugcheck Analysis *
* *
************************************************************ *******************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff802b5e9886e, ffffc48197ca6fd0, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
5: 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: fffff802b5e9886e, Address of the instruction which caused the bugcheck
Arg3: ffffc48197ca6fd0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.14393.351 (rs1_release_inmarket.161014-1755)
DUMP_TYPE: 2
BUGCHECK_P1: c0000005
BUGCHECK_P2: fffff802b5e9886e
BUGCHECK_P3: ffffc48197ca6fd0
BUGCHECK_P4: 0
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruksjonen i 0x%p refererte minne ved adressen 0x%p. Minnet kunne ikke v re %s.
FAULTING_IP:
nt!KiDeliverApc+ae
fffff802`b5e9886e 498b4a30 mov rcx,qword ptr [r10+30h]
CONTEXT: ffffc48197ca6fd0 -- (.cxr 0xffffc48197ca6fd0)
rax=0000000000000002 rbx=ffff898f750d1800 rcx=0000000000000000
rdx=fbff898f750d1898 rsi=0000000000000000 rdi=ffff898f750d1898
rip=fffff802b5e9886e rsp=ffffc48197ca79e0 rbp=ffffc48197ca7a30
r8=0000000000000000 r9=00000000000000b4 r10=fbff898f750d1888
r11=ffffc48197ca7a70 r12=0000000000000000 r13=0000000000000000
r14=ffffc48197ca7b00 r15=ffff898f751d7700
iopl=0 nv up ei ng nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287
nt!KiDeliverApc+0xae:
fffff802`b5e9886e 498b4a30 mov rcx,qword ptr [r10+30h] ds:002b:fbff898f`750d18b8=????????????????
Resetting default scope
CPU_COUNT: 8
CPU_MHZ: dac
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3c
CPU_STEPPING: 3
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x3B
PROCESS_NAME: plugin-container.exe
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: DESKTOP-JGNVQ46
ANALYSIS_SESSION_TIME: 11-02-2016 23:24:50.0398
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER: from fffff802b5e98791 to fffff802b5e9886e
STACK_TEXT:
ffffc481`97ca79e0 fffff802`b5e98791 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000003 : nt!KiDeliverApc+0xae
ffffc481`97ca7a70 fffff802`b5eecb50 : ffff898f`750d1800 00000000`ffffffff 00000000`0008d302 00000000`00000000 : nt!KiCheckForKernelApcDelivery+0x21
ffffc481`97ca7aa0 fffffec8`5784be5d : 00000000`00000003 00000000`00000020 00000000`00041dff 000000e7`d77fb560 : nt!ExReleaseResourceAndLeaveCriticalRegion+0x50
ffffc481`97ca7ad0 fffff802`b5f5e093 : ffff898f`750d1800 00000000`00000000 00000000`00000000 00000000`00000001 : win32kfull!NtUserCallNoParam+0x3d
ffffc481`97ca7b00 00007ffe`43d71144 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000e7`d77fec38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`43d71144
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff802b5eadea1-fffff802b5eadea2 2 bytes - nt!MiResolvePrivateZeroFault+211
[ 80 f6:00 ee ]
fffff802b5eadeca-fffff802b5eadecc 3 bytes - nt!MiResolvePrivateZeroFault+23a (+0x29)
[ 40 fb f6:00 77 ee ]
fffff802b5eadee8-fffff802b5eadee9 2 bytes - nt!MiResolvePrivateZeroFault+258 (+0x1e)
[ 80 fa:00 80 ]
fffff802b5eb022a-fffff802b5eb022b 2 bytes - nt!MiGetFreeOrZeroPage+7a (+0x2342)
[ 80 fa:00 80 ]
9 errors : !nt (fffff802b5eadea1-fffff802b5eb022b)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
STACK_COMMAND: .cxr 0xffffc48197ca6fd0 ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE
PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE
TARGET_TIME: 2016-11-02T21:28:49.000Z
OSBUILD: 14393
OSSERVICEPACK: 351
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-10-15 05:38:38
BUILDDATESTAMP_STR: 161014-1755
BUILDLAB_STR: rs1_release_inmarket
BUILDOSVER_STR: 10.0.14393.351
ANALYSIS_SESSION_ELAPSED_TIME: 10e1
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:memory_corruption_large
FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}
Followup: memory_corruption
---------
Sitat av
Ygg
Vil anbefale deg å prøve å starte opp systemet med en gpu og en ram-brikke.
Krasjer systemet igjen da, bytt gpu og prøv igjen, krasjer det fortsatt så ville jeg prøvd hver ram-brikke hver for seg på begge gpuer.
nå vet ikke jeg hvilken bios du har på hovedkortet men om du har brukt en "automatisk" overklokkingsfunksjon så er det mulig det har overklokket ram-klokkehastigheten din også.
Så det kan være lurt på laste inn fabrikkinstillinger for biosen din.
Hørtes ekstremt klotete og kjedelig ut, kjøper ikke dyr gaming pc for å sitte med det marerittet her ass.
Biosen er nyeste jeg har funnet til mitt kort AM 1B
Har som sagt ingen overklokking på noe som helst nå, alt er på default, bortsett fra at boostfunksjonen til cpu er aktivert (3900 mhz).
Alt dette står over
Sist endret av Fleff; 3. november 2016 kl. 00:27.
Grunn: Spoiler på bugcheck