Witam, Potrzebuje pomocy w zrozumieniu czego dotyczą błedy bluescreen które często wywalają mi w komputerze, w załączniku przesyłam dokładne informacje trzech Bsodów które zjechałem z pliku minidump w windows. Z góry dziękuję za pomoc :)) Parametry sprzętowe PC Płyta głowna: Gigabyte G1 Sniper A88X Procesor: AMD APU A10 7700K RAM: AMD Radeon R9 Gamer Serries 2x4096MB DDR3 2133MHz Grafika: Gigabyte RX480 8GB Zasilacz: SilentiumPC L2 600W Dysk1: LiteOn SSD 120GB Dysk2: Samsung 1TB Napęd: LG BD-Rewriter Chłodzenie komputera CPU:2x120mm wentylator, obudowa: 3x120mm + 1x140mm wentylator, wszystkie wentylatory zasilane z płyty głownej. PCI-Ex x1 karta Wifi TPLink Problem opisywałem w innym poście kiedy to od miesiąca resetował się komputer wówczas problemem był wadliwy zasilacz Corsair CS750M 750W który wymieniłem na ten podany w specyfikacji wyżej. Przestał się resetować ale lecą BSODY. W programie OCCT POWER SUPPLY wykresy podobne do tych przed wymianą zasilacza. EDIT https://obrazki.elektroda.pl/5066599100_1515826322_thumb.jpghttps://obrazki.elektroda.pl/3007660800_1515826326_thumb.jpghttps://obrazki.elektroda.pl/5388021300_1515826328_thumb.jpghttps://obrazki.elektroda.pl/1257738200_1515826332_thumb.jpghttps://obrazki.elektroda.pl/1789879600_1515826335_thumb.jpghttps://obrazki.elektroda.pl/9637767900_1515826341_thumb.jpghttps://obrazki.elektroda.pl/9251635300_1515826344_thumb.jpghttps://obrazki.elektroda.pl/9480533000_1515826347_thumb.jpghttps://obrazki.elektroda.pl/4702340900_1515826351_thumb.jpghttps://obrazki.elektroda.pl/9743486700_1515826354_thumb.jpghttps://obrazki.elektroda.pl/1440034200_1515826358_thumb.jpghttps://obrazki.elektroda.pl/7149970600_1515826362_thumb.jpghttps://obrazki.elektroda.pl/8296502200_1515826365_thumb.jpghttps://obrazki.elektroda.pl/7694082600_1515826369_thumb.jpghttps://obrazki.elektroda.pl/6925710300_1515826373_thumb.jpghttps://obrazki.elektroda.pl/3076270600_1515826376_thumb.jpghttps://obrazki.elektroda.pl/6300435800_1515826380_thumb.jpghttps://obrazki.elektroda.pl/3835108200_1515826383_thumb.jpghttps://obrazki.elektroda.pl/5005773700_1515826387_thumb.jpg Dodano po 44 : Powyżej wykresy z błędem Power Supply na nowej zasiłce nowym zasilaczu. Dodano po 2 : Formatowałem wszystkie dyski, zamieniałem sloty pamięci RAM, odpalałem komputer na pojedynczej kości, wstawiałem inny dysk to przetestowania, Memtest nic nie wykrył, Dr WEB z poziomu biosu też nic nie wykrył. Dodano po 1 : Co najlepsze BSOD nigdy nie wyskoczył podczas grania a podczas zwykłej pracy przy odpalaniu przeglądarki, programu antywirusowego lub innych programach :// Scaliłem. RADU23
Microsoft (R) Windows Debugger Version 10.0.15063.468 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\011218-6625-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 16299 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff801`f3e11000 PsLoadedModuleList = 0xfffff801`f4177fd0
Debug session time: Fri Jan 12 13:34:19.422 2018 (UTC + 1:00)
System Uptime: 0 days 0:09:31.229
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff801f3eaca59, fffffe810b9331e8, fffffe810b932a30}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!RtlSubtreePredecessor+9 )
Followup: MachineOwner
---------
2: kd & gt; !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: fffff801f3eaca59, The address that the exception occurred at
Arg3: fffffe810b9331e8, Exception Record Address
Arg4: fffffe810b932a30, Context Record Address
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.16299.192 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.
SYSTEM_PRODUCT_NAME: To be filled by O.E.M.
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: To be filled by O.E.M.
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: F11
BIOS_DATE: 12/24/2015
BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.
BASEBOARD_PRODUCT: G1.Sniper A88X-CF
BASEBOARD_VERSION: x.x
DUMP_TYPE: 2
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff801f3eaca59
BUGCHECK_P3: fffffe810b9331e8
BUGCHECK_P4: fffffe810b932a30
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - & lt; Unable to get error code text & gt;
FAULTING_IP:
nt!RtlSubtreePredecessor+9
fffff801`f3eaca59 488b4810 mov rcx,qword ptr [rax+10h]
EXCEPTION_RECORD: fffffe810b9331e8 -- (.exr 0xfffffe810b9331e8)
ExceptionAddress: fffff801f3eaca59 (nt!RtlSubtreePredecessor+0x0000000000000009)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000180
Attempt to read from address 0000000000000180
CONTEXT: fffffe810b932a30 -- (.cxr 0xfffffe810b932a30)
rax=0000000000000170 rbx=ffffa20f1029b7e8 rcx=ffffa20f1029b7e8
rdx=ffffd40e6ecd64f0 rsi=0000000000000000 rdi=ffffd40e6ecd64f0
rip=fffff801f3eaca59 rsp=fffffe810b933428 rbp=0000000000000000
r8=ffffffffffffffff r9=ffffb8001bad4180 r10=0000000000000fff
r11=0000000000000160 r12=ffffa20f1029b7e8 r13=ffffa20f1029b7e8
r14=ffffd40e6ecd64f0 r15=ffffa20f1029b7e8
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!RtlSubtreePredecessor+0x9:
fffff801`f3eaca59 488b4810 mov rcx,qword ptr [rax+10h] ds:002b:00000000`00000180=????????????????
Resetting default scope
CPU_COUNT: 4
CPU_MHZ: d42
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 30
CPU_STEPPING: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - & lt; Unable to get error code text & gt;
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000180
FOLLOWUP_IP:
nt!RtlSubtreePredecessor+9
fffff801`f3eaca59 488b4810 mov rcx,qword ptr [rax+10h]
BUGCHECK_STR: AV
READ_ADDRESS: fffff801f420d380: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
0000000000000180
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
ANALYSIS_SESSION_HOST: DESKTOP-IUC3ULB
ANALYSIS_SESSION_TIME: 01-13-2018 04:49:07.0365
ANALYSIS_VERSION: 10.0.15063.468 x86fre
LAST_CONTROL_TRANSFER: from fffff801f3f18831 to fffff801f3eaca59
STACK_TEXT:
fffffe81`0b933428 fffff801`f3f18831 : fffff805`e3027060 00000000`ffff7fff ffffd40e`6bd49e50 fffff805`e3027060 : nt!RtlSubtreePredecessor+0x9
fffffe81`0b933430 fffff805`e30052b1 : ffffa20f`1029b7e8 fffff801`f3e40b79 ffffd40e`6be4b700 ffffd40e`6ecd64b8 : nt!RtlDeleteNoSplay+0xb1
fffffe81`0b933460 fffff805`e303ac9e : ffffd40e`6bd49e6c fffffe81`00000000 00000000`00000000 00000000`00000000 : FLTMGR!TreeUnlinkMulti+0xb1
fffffe81`0b9334b0 fffff805`e3007d06 : 00000000`00000000 ffffd40e`6ecd8210 ffffd40e`00004000 ffffd40e`6f19e010 : FLTMGR!FltpRemoveAllNamesCachedForFileObject+0x12e
fffffe81`0b933530 fffff805`e30073f8 : fffffe81`0b933720 00000000`00000000 ffffd40e`6f632802 00000000`00000400 : FLTMGR!FltpPerformPreCallbacks+0x796
fffffe81`0b933650 fffff805`e3006ffb : ffffd40e`6f632840 fffffe81`0b933720 ffffd40e`6f632840 fffffe81`0b933730 : FLTMGR!FltpPassThroughInternal+0x88
fffffe81`0b933680 fffff805`e3006d9e : ffffffff`fffe7960 ffffd40e`6bd40920 00000000`00000080 00000000`00000000 : FLTMGR!FltpPassThrough+0x1ab
fffffe81`0b933700 fffff801`f3e2b2d9 : ffffd40e`6ecd8210 fffff801`f3e2b1cd ffffa20f`09c99ff8 fffff801`f40c0347 : FLTMGR!FltpDispatch+0x9e
fffffe81`0b933760 fffff801`f428bc32 : ffffd40e`6ecd8210 ffffd40e`6ecd7090 ffffd40e`6bd40920 ffffd40e`6a879030 : nt!IofCallDriver+0x59
fffffe81`0b9337a0 fffff801`f42e2c2e : ffffa20f`102a5890 ffffd40e`6ecd7090 00000000`00000000 ffffd40e`6a988c60 : nt!IopDeleteFile+0x122
fffffe81`0b933820 fffff801`f3e41261 : 00000000`00000000 00000000`00000000 ffffd40e`6ecd7090 ffffd40e`6ecd8210 : nt!ObpRemoveObjectRoutine+0x7e
fffffe81`0b933880 fffff801`f42c8fd4 : 00000000`00000000 ffffd40e`6ecd7010 ffffd40e`00000265 ffffd40e`74536d4d : nt!ObfDereferenceObject+0xa1
fffffe81`0b9338c0 fffff801`f3f5420f : ffffd40e`00000001 00000000`00000000 ffffd40e`6ecd7018 ffffa20f`09c7dcb0 : nt!MiSegmentDelete+0x17c
fffffe81`0b933920 fffff801`f3f54119 : 00000000`00000000 fffff801`00000001 00000000`00000002 fffff801`f4197f00 : nt!MiProcessDereferenceList+0xa3
fffffe81`0b9339e0 fffff801`f3f28807 : ffffd40e`6be4b700 ffffd40e`6be4b700 00000000`00000080 fffff801`f3f53ff0 : nt!MiDereferenceSegmentThread+0x129
fffffe81`0b933c10 fffff801`f3f8de96 : ffffb800`1bad4180 ffffd40e`6be4b700 fffff801`f3f287c0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
fffffe81`0b933c60 00000000`00000000 : fffffe81`0b934000 fffffe81`0b92e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
THREAD_SHA1_HASH_MOD_FUNC: 13af88641dc6dab4adf129895a7bd33ee6abc121
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ca7715c688664479409d16394b1662a0b1d3461e
THREAD_SHA1_HASH_MOD: 125d71d0e736f07ae4df0933ed49fcd65c695052
FAULT_INSTR_CODE: 10488b48
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!RtlSubtreePredecessor+9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5a4a1659
IMAGE_VERSION: 10.0.16299.192
STACK_COMMAND: .cxr 0xfffffe810b932a30 ; kb
BUCKET_ID_FUNC_OFFSET: 9
FAILURE_BUCKET_ID: AV_nt!RtlSubtreePredecessor
BUCKET_ID: AV_nt!RtlSubtreePredecessor
PRIMARY_PROBLEM_CLASS: AV_nt!RtlSubtreePredecessor
TARGET_TIME: 2018-01-12T12:34:19.000Z
OSBUILD: 16299
OSSERVICEPACK: 192
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2018-01-01 12:07:05
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.16299.192
ANALYSIS_SESSION_ELAPSED_TIME: 1d2c
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_nt!rtlsubtreepredecessor
FAILURE_ID_HASH: {9c83f313-8194-6a8e-da2b-014e09f29178}
Followup: MachineOwner
---------