Šta je novo?
Od:
Filteri

Cudne greske u Windowsu

Nisam gledao u event viewer-u ali u HWInfo nema.
 
Nema u event viewer-u nista za WHEA. U Administrative events ima brdo..
1664201237215.png
 
Ok. Nije do graficke sto je najvaznije jer da jeste bio bi problem potencijalni sa garancijom, jer je tesko i specificno reprodukovati. Kad smo zamenili RAM nije puklo nekoliko partija Overwatch-a, nema ni greske u Chrome-u za sada. Do sutra ce kod mene biti njegov RAM pa cemo videti da li je to resilo..

Izgleda da je do memorije. Imao sam i neki mali stutter u Overwatch-u koji je zamenom memorije nestao, izgleda da je dosao kraj ovom budzet G.SKill Aegis kit-u..
 
Pa testiraj memoriju.
 
Ma puca sada i sa novom memorijom. Na blizzard forumu mi rekli da neki pozadinski proces pravi problem (na osnovu logova). Discord nije, puca i bez njega. Jedino sto radi u pozadini sve vreme i sto je radilo na oba sistema je Logitech G Hub za G502. Sada testiram bez njega kako se ponasa..
 
Ne i nemam namere, stres testovi su prolazili. Puca i bez Logitech G Hub-a. Nista, bataljujem Overwatch, ionako izlazi dvojka za nedelju dana, pa ako bude radila nek radi.

Bukvalno crashuje Overwatch redovno i po neki chrome tab, ne moram da koristim taj softver i to je to :D
 
A da probaš da instaliras kompletno samo Windows 11, drajvere za ploču i grafičku, chrome i overwatch?
 
Nista posebno i nemam, legalan Windows je instaliran pre nekoliko dana. Imam samo discord, LG Hub, qBitTorrent (seeduje sa HDD-a). Nikakve modifikacije windowsa, nista klokovano..
 
A jesi li probao da reimenuješ owerwatch u owervatchtest? Kažu da to pomaše imaš uputstvo na prošloj strani.
 
Imam razne ekstenzije za Chrome, ali je chrome prestao da puca :D

Izasao Overwatch 2, sada ne mogu ni da otvorim igricu, u loadingu mi se restartuje ceo PC 😂
 
Pogeldaj da li imas koji .dmp u LiveKernelReports folderu ili u minidump (Windows dir)
 
Saga se nastavlja:

Pokrenuo sam system file checker (sfc /scannow) i pronasao je greske koje je popravio. Naknadno pokretanje nije nalazilo probleme.
chkdsk komanda nije nasla probleme.
Hard Disk Sentinel prikazuje dobar health za HDD i SSD (znam da nije merodavan za SSD).

Edit:

DISM komanda takodje nije pronasla nista.
 
Poslednja izmena:
danilo989 je napisao(la):
Pogeldaj da li imas koji .dmp u LiveKernelReports folderu ili u minidump (Windows dir)
Kliknite za proširenje...
Sada se javljaju crash dumpovi u LiveKernelReports. Evo sta sam dobio:


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


Loading Dump File [C:\Windows\LiveKernelReports\WHEA\WHEA-20221005-0019.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 19044 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`6c600000 PsLoadedModuleList = 0xfffff800`6d22a270
Debug session time: Wed Oct 5 00:19:28.056 2022 (UTC + 2:00)
System Uptime: 0 days 0:00:04.687
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
  • *
  • Bugcheck Analysis *
  • *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffdf8ebb06f840, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000bea00000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000108, Low order 32-bits of the MCi_STATUS value.

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

*************************************************************************
* *
* *
* Either you specified an unqualified symbol, or your debugger *
* doesn't have full symbol information. Unqualified symbol *
* resolution is turned off by default. Please either specify a *
* fully qualified symbol module!symbolname, or enable resolution *
* of unqualified symbols by typing ".symopt- 100". Note that *
* enabling unqualified symbol resolution with network symbol *
* server shares in the symbol path may cause the debugger to *
* appear to hang for long periods of time when an incorrect *
* symbol name is typed or the network symbol server is down. *
* *
* For some commands to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* *
* Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *
* *
*************************************************************************
*************************************************************************
* *
* *
* Either you specified an unqualified symbol, or your debugger *
* doesn't have full symbol information. Unqualified symbol *
* resolution is turned off by default. Please either specify a *
* fully qualified symbol module!symbolname, or enable resolution *
* of unqualified symbols by typing ".symopt- 100". Note that *
* enabling unqualified symbol resolution with network symbol *
* server shares in the symbol path may cause the debugger to *
* appear to hang for long periods of time when an incorrect *
* symbol name is typed or the network symbol server is down. *
* *
* For some commands to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* *
* Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *
* *
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3781

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 14246

Key : Analysis.Init.CPU.mSec
Value: 2764

Key : Analysis.Init.Elapsed.mSec
Value: 81567

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


FILE_IN_CAB: WHEA-20221005-0019.dmp

DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffdf8ebb06f840

BUGCHECK_P3: bea00000

BUGCHECK_P4: 108

PROCESS_NAME: smss.exe

STACK_TEXT:
ffffb206`d9d77190 fffff800`6cf5bb0f : ffffdf8e`bb06f820 00000000`00000000 ffffdf8e`bb06f840 00000000`00000022 : nt!LkmdTelCreateReport+0x13e
ffffb206`d9d776d0 fffff800`6cf5ba06 : ffffdf8e`bb06f820 fffff800`00000000 000000f5`00000000 000000f5`6ab8f5d0 : nt!WheapReportLiveDump+0x7b
ffffb206`d9d77710 fffff800`6cdc5a81 : 00000000`00000001 ffffb206`d9d77b80 000000f5`6ab8f5d0 00000000`00000210 : nt!WheapReportDeferredLiveDumps+0x7a
ffffb206`d9d77740 fffff800`6cc4dad7 : 00000000`00000000 ffffdf8e`ba0ce030 00000000`00000103 00000000`00000000 : nt!WheaCrashDumpInitializationComplete+0x59
ffffb206`d9d77770 fffff800`6ca0aab8 : ffffdf8e`bad60000 ffffdf8e`bad62060 ffffb206`d9d77b80 ffffdf8e`00000000 : nt!NtSetSystemInformation+0x1f7
ffffb206`d9d77b00 00007ffb`8dab06b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000f5`6ab8f578 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`8dab06b4


MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: LKD_0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f59f17e7-f24e-04f5-3f16-e9425b2acba5}

Followup: MachineOwner
 
Bugcheck code 124 moze biti vezano za CPU, ali na zalost ne zna se tacno sta je uzrok, Core, Memory Controller, PCIe itd.
Pogledaj sad u Event Viewer opet onaj filter za WHEA greske, moguce da ce ti se pojaviti sad unos. Ako bude, okaci detalje tog event-a.
 
@danilo989
Ima sada i tamo, bravo.
--------------------------------------------------------------
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 5

The details view of this entry contains further information.
----------------------------------------------------------------
XML: 
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" />
  <EventID>18</EventID>
  <Version>0</Version>
  <Level>2</Level>
  <Task>0</Task>
  <Opcode>0</Opcode>
  <Keywords>0x8000000000000000</Keywords>
  <TimeCreated SystemTime="2022-10-04T22:19:31.2484261Z" />
  <EventRecordID>4818</EventRecordID>
  <Correlation ActivityID="{09c52693-83e8-4829-92ec-28fec9afab46}" />
  <Execution ProcessID="3468" ThreadID="4028" />
  <Channel>System</Channel>
  <Computer>DESKTOP-TNCTO8M</Computer>
  <Security UserID="S-1-5-19" />
  </System>
- <EventData>
  <Data Name="ErrorSource">3</Data>
  <Data Name="ApicId">5</Data>
  <Data Name="MCABank">5</Data>
  <Data Name="MciStat">0xbea0000000000108</Data>
  <Data Name="MciAddr">0x101f8048346b955</Data>
  <Data Name="MciMisc">0xd01a0ffe00000000</Data>
  <Data Name="ErrorType">9</Data>
  <Data Name="TransactionType">2</Data>
  <Data Name="Participation">256</Data>
  <Data Name="RequestType">0</Data>
  <Data Name="MemorIO">256</Data>
  <Data Name="MemHierarchyLvl">0</Data>
  <Data Name="Timeout">256</Data>
  <Data Name="OperationType">256</Data>
  <Data Name="Channel">256</Data>
  <Data Name="Length">936</Data>
  <Data Name="RawData">435045521002FFFFFFFF03000100000002000000A80300001A131600040A16140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BBC37D925B3FD8D80102000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002010000000000100F87000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000500000000000000100F870000080C050B32F87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F0002060000000055B9468304F8010100000000000000000000000000000000000000000000000002000000020000006E1AFF5C3FD8D801050000000000000000000000000000000000000005000000080100000000A0BE55B9468304F8010100000000FE0F1AD0000000000500000000000000B00005000000004D0000000079000000230000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
  </EventData>
  </Event>
 
Ovo je 99% do samog jezgra u procesoru. Treba samo proveriti tacno koje jezgro je u pitanju, na prvi pogled je jezgro #3. Da budemo 100% sigurni koje jezgro je u pitanju, skini CPUz, pa padajuci meni pored Tools, Save report as HTML
Okaci fajl ovde
 
@danilo989
Ima jos 3 ovakva errora, svi su nastali veceras. Sva 3 su prouzrokovala restart sistema. Pobriaso sam raw data jer mi nije davao forum da zalepim toliko dug post.
XML: 
Log Name:      System
Source:        Microsoft-Windows-WHEA-Logger
Date:          10/4/2022 10:51:27 PM
Event ID:      18
Task Category: None
Level:         Error
Keywords:
User:          LOCAL SERVICE
Computer:      DESKTOP-TNCTO8M
Description:
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 8

The details view of this entry contains further information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" />
    <EventID>18</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2022-10-04T20:51:27.4536770Z" />
    <EventRecordID>4668</EventRecordID>
    <Correlation ActivityID="{79df6821-591c-4fb5-9e8a-e68d7e433ba9}" />
    <Execution ProcessID="3564" ThreadID="3236" />
    <Channel>System</Channel>
    <Computer>DESKTOP-TNCTO8M</Computer>
    <Security UserID="S-1-5-19" />
  </System>
  <EventData>
    <Data Name="ErrorSource">3</Data>
    <Data Name="ApicId">8</Data>
    <Data Name="MCABank">5</Data>
    <Data Name="MciStat">0xbea0000000000108</Data>
    <Data Name="MciAddr">0x7ff7608025f0</Data>
    <Data Name="MciMisc">0xd01a0ffe00000000</Data>
    <Data Name="ErrorType">9</Data>
    <Data Name="TransactionType">2</Data>
    <Data Name="Participation">256</Data>
    <Data Name="RequestType">0</Data>
    <Data Name="MemorIO">256</Data>
    <Data Name="MemHierarchyLvl">0</Data>
    <Data Name="Timeout">256</Data>
    <Data Name="OperationType">256</Data>
    <Data Name="Channel">256</Data>
    <Data Name="Length">936</Data>
    <Data Name="RawData"></Data>
  </EventData>
</Event>

XML: 
Log Name:      System
Source:        Microsoft-Windows-WHEA-Logger
Date:          10/4/2022 10:19:36 PM
Event ID:      18
Task Category: None
Level:         Error
Keywords:
User:          LOCAL SERVICE
Computer:      DESKTOP-TNCTO8M
Description:
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 13

The details view of this entry contains further information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" />
    <EventID>18</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2022-10-04T20:19:36.5533787Z" />
    <EventRecordID>4603</EventRecordID>
    <Correlation ActivityID="{ab145b2e-1fc5-4c4f-a2bd-6d9845159af4}" />
    <Execution ProcessID="3516" ThreadID="4080" />
    <Channel>System</Channel>
    <Computer>DESKTOP-TNCTO8M</Computer>
    <Security UserID="S-1-5-19" />
  </System>
  <EventData>
    <Data Name="ErrorSource">3</Data>
    <Data Name="ApicId">13</Data>
    <Data Name="MCABank">5</Data>
    <Data Name="MciStat">0xbea0000000000108</Data>
    <Data Name="MciAddr">0x1007ffb11b71c1d</Data>
    <Data Name="MciMisc">0xd01a0ffe00000000</Data>
    <Data Name="ErrorType">9</Data>
    <Data Name="TransactionType">2</Data>
    <Data Name="Participation">256</Data>
    <Data Name="RequestType">0</Data>
    <Data Name="MemorIO">256</Data>
    <Data Name="MemHierarchyLvl">0</Data>
    <Data Name="Timeout">256</Data>
    <Data Name="OperationType">256</Data>
    <Data Name="Channel">256</Data>
    <Data Name="Length">936</Data>
    <Data Name="RawData"></Data>
  </EventData>
</Event>

XML: 
Log Name:      System
Source:        Microsoft-Windows-WHEA-Logger
Date:          10/4/2022 10:16:58 PM
Event ID:      18
Task Category: None
Level:         Error
Keywords:
User:          LOCAL SERVICE
Computer:      DESKTOP-TNCTO8M
Description:
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 12

The details view of this entry contains further information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" />
    <EventID>18</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2022-10-04T20:16:58.8380473Z" />
    <EventRecordID>4530</EventRecordID>
    <Correlation ActivityID="{01dfbfa4-00e6-4a5c-b4a5-7cd6ad036fbf}" />
    <Execution ProcessID="3684" ThreadID="4100" />
    <Channel>System</Channel>
    <Computer>DESKTOP-TNCTO8M</Computer>
    <Security UserID="S-1-5-19" />
  </System>
  <EventData>
    <Data Name="ErrorSource">3</Data>
    <Data Name="ApicId">12</Data>
    <Data Name="MCABank">5</Data>
    <Data Name="MciStat">0xbea0000000000108</Data>
    <Data Name="MciAddr">0x7ff6c9fb2626</Data>
    <Data Name="MciMisc">0xd01a0ffe00000000</Data>
    <Data Name="ErrorType">9</Data>
    <Data Name="TransactionType">2</Data>
    <Data Name="Participation">256</Data>
    <Data Name="RequestType">0</Data>
    <Data Name="MemorIO">256</Data>
    <Data Name="MemHierarchyLvl">0</Data>
    <Data Name="Timeout">256</Data>
    <Data Name="OperationType">256</Data>
    <Data Name="Channel">256</Data>
    <Data Name="Length">936</Data>
    <Data Name="RawData"></Data>
  </EventData>
</Event>

Link ka HTML fajlu (predugacak html da zalepim na forum, ne dozvoljava).

Zakacio sam CPU-Z report i kao txt fajl.
 

Prilozi

  • DESKTOP-TNCTO8M.txt
    177.4 KB · Pregleda: 2
"Processor APIC ID: 8" ti daje indikaciju koji APIC identifikacioni broj je Windows dodelio nekom jezgru. U screenshotu sam ti oznacio jezgra koja su problematicna, desna kolona je APIC. Core 2, 3, 5 su do sad izbacivali greske.
Jesi radio update BIOSa nedavno tj od kad su poceli problemi? Moguce da je nesto poremetilo krivu napon/frekvencija...
Screenshot 2022-10-05 011348.png
 
Nisam skoro radio, ali drzim uvek poslednji BIOS na ploci. Moguce je da je BIOS problem, nisam jos probao sa starijom verzijom biosa.

Nasao sam po netu da ovo hoce da puca zbog nedovoljno napona. Vec sam bio probao sa fabrickim bios podesavanjima i sa downclock-ovanjem i iskljucivanjem power saving/boost opcija. Sada sam podesio procesor na 3.7GHz i 1.35V, pogasio apsolutno sve power saving opcije kao i boost opcije, pa cemo videti.

Edit:

@danilo989
Hvala puno na pomoci.
 
Poslednja izmena:
Nista, srecno. :D

Samo da napomenem ako se nekom javljaju slicni problemi, Event ID 18/Error Type: Cache Hierarchy Error je uglavnom vezano za jezgro, dok je Event ID 19/Error Type: Bus/Interconnect Error vezano za Infinity Fabric
 
@danilo989
Da li mislis da one greke koje sam dobijao vezane za ACCESS_VIOLATION ili ILLEGAL_INSTRUCTION takodje mogu biti zbog iste stvari?
 
Ne znam, svasta moze da se desava ako jezgra nisu stabilna, ne bi me cudilo da su povezani.
 
To je kad hocu na default da koristim. Godinama rock stable OC na FX-u, pa na Ryzenu, a sada se pravim pametam i koristim stock... Ne biva :D
 
Moguce da je svirnuo procesor. Desavao se ovaj crash i na 1.35v 3.5GHz. Na 1.4V 3.5GHz se nije desio za sada..
 
Na kom si sad BIOSu/AGESAi?
 
Morate se prijaviti ili registrovati da odgovorite ovde.
Nazad
Vrh Dno