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-6593-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 = 0xfffff800`2d88d000 PsLoadedModuleList = 0xfffff800`2dbf3fd0
Debug session time: Fri Jan 12 13:24:13.211 2018 (UTC + 1:00)
System Uptime: 0 days 0:40:52.017
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F7, {78223fcf640, 47c96ad5dae2, ffffb836952a251d, 0}
Probably caused by : ntkrnlmp.exe ( nt!_report_gsfailure+25 )
Followup: MachineOwner
---------
1: kd & gt; !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer. This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned. This is the classic " buffer overrun "
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and bugcheck call is the one that overran its local
variable(s).
Arguments:
Arg1: 0000078223fcf640, Actual security check cookie from the stack
Arg2: 000047c96ad5dae2, Expected security check cookie
Arg3: ffffb836952a251d, Complement of the expected security check cookie
Arg4: 0000000000000000, zero
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: 78223fcf640
BUGCHECK_P2: 47c96ad5dae2
BUGCHECK_P3: ffffb836952a251d
BUGCHECK_P4: 0
SECURITY_COOKIE: Expected 000047c96ad5dae2 found 0000078223fcf640
CPU_COUNT: 4
CPU_MHZ: d42
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 30
CPU_STEPPING: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0xF7
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: DESKTOP-IUC3ULB
ANALYSIS_SESSION_TIME: 01-13-2018 04:41:07.0630
ANALYSIS_VERSION: 10.0.15063.468 x86fre
LAST_CONTROL_TRANSFER: from fffff8002da6a9e5 to fffff8002da026e0
STACK_TEXT:
fffffe02`20f33398 fffff800`2da6a9e5 : 00000000`000000f7 00000782`23fcf640 000047c9`6ad5dae2 ffffb836`952a251d : nt!KeBugCheckEx
fffffe02`20f333a0 fffff800`2d88ea04 : ffffa686`5ab17000 fffffe02`20f33b80 00000000`000018c0 fffff800`2db3c43d : nt!_report_gsfailure+0x25
fffffe02`20f333e0 fffff800`2d88e8ce : 00000000`00000100 ffffa686`5ab188c0 ffffa686`5ab17008 fffffe02`20f33598 : nt!MiIdentifyPfn+0xe4
fffffe02`20f334a0 fffff800`2dcc473e : 00000000`00000000 ffffa686`5ab18188 ffffa686`5ab17000 fffffe02`42506650 : nt!MiIdentifyPfnWrapper+0x3e
fffffe02`20f334d0 fffff800`2dd17c0f : ffffa686`5a270700 00000000`00000001 fffffe02`20f336b4 ffffa686`5ab17000 : nt!PfpPfnPrioRequest+0xbe
fffffe02`20f33550 fffff800`2dd164d5 : 00000000`00000000 00000000`00000050 00000000`00000020 fffff800`2dc13f00 : nt!PfQuerySuperfetchInformation+0x2bf
fffffe02`20f33680 fffff800`2dd1459b : 0000055e`e6070001 00000000`00000000 0000023e`13c11012 00000000`00000002 : nt!ExpQuerySystemInformation+0x1e25
fffffe02`20f33ac0 fffff800`2da15203 : ffffa686`5a270700 00000000`00000000 ffffa686`5a270700 00000000`00000000 : nt!NtQuerySystemInformation+0x2b
fffffe02`20f33b00 00007ffd`80f90534 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000ef`bf379e18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`80f90534
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 0621696229749f19418dfeecf88f4c3d2bd5058e
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: b387530e3867e6860cc3d3373e4632efd9d1b348
THREAD_SHA1_HASH_MOD: 9f457f347057f10e1df248e166a3e95e6570ecfe
FOLLOWUP_IP:
nt!_report_gsfailure+25
fffff800`2da6a9e5 cc int 3
FAULT_INSTR_CODE: cccccccc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!_report_gsfailure+25
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5a4a1659
IMAGE_VERSION: 10.0.16299.192
BUCKET_ID_FUNC_OFFSET: 25
FAILURE_BUCKET_ID: 0xF7_MISSING_GSFRAME_nt!_report_gsfailure
BUCKET_ID: 0xF7_MISSING_GSFRAME_nt!_report_gsfailure
PRIMARY_PROBLEM_CLASS: 0xF7_MISSING_GSFRAME_nt!_report_gsfailure
TARGET_TIME: 2018-01-12T12:24:13.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: 23f3
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xf7_missing_gsframe_nt!_report_gsfailure
FAILURE_ID_HASH: {82d2c1b5-b0cb-60a5-9a5d-78c8c4284f84}
Followup: MachineOwner
---------