BSOD - BCC 124

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Desio se BSOD pre možda 10 minuta.

BCCode 124.
Problem signature:
  Problem Event Name:   BlueScreen
  OS Version:   6.1.7601.2.1.0.256.1
  Locale ID:   9242

Additional information about the problem:
  BCCode:   124
  BCP1:   0000000000000000
  BCP2:   FFFFFA8007FCC5D8
  BCP3:   0000000000000000
  BCP4:   0000000000000000
  OS Version:   6_1_7601
  Service Pack:   1_0
  Product:   256_1

Files that help describe the problem:
  C:\Windows\Minidump\111614-34928-01.dmp
  C:\Users\Srdjan\AppData\Local\Temp\WER-48968-0.sysdata.xml


BlueScreenView log :
==================================================
Dump File         : 111614-34928-01.dmp
Crash Time        : 16.11.2014 0:32:10
Bug Check String  :
Bug Check Code    : 0x00000124
Parameter 1       : 00000000`00000000
Parameter 2       : fffffa80`07fcc5d8
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4adb5c
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18526 (win7sp1_gdr.140706-1506)
Processor         : x64
Crash Address     : ntoskrnl.exe+4adb5c
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\111614-34928-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 262.144
Dump File Time    : 16.11.2014 0:32:27
==================================================



Mislio sam da je do novog RAMa kog sam instalirao 10. međutim, našao sam još jedan dump fajl, isti BCC ali se desio 7. ovog meseca. Ne znam kada se taj BSOD 7. desio jer se ne sećam bilo kog problema.

Evo tog starijeg loga :

==================================================
Dump File         : 110714-47408-01.dmp
Crash Time        : 7.11.2014 2:51:22
Bug Check String  :
Bug Check Code    : 0x00000124
Parameter 1       : 00000000`00000000
Parameter 2       : fffffa80`04c268f8
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4adb5c
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18526 (win7sp1_gdr.140706-1506)
Processor         : x64
Crash Address     : ntoskrnl.exe+4adb5c
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\110714-47408-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 262.144
Dump File Time    : 7.11.2014 2:51:42
==================================================



Vidim da je ovo široka oblast pa može svašta biti ali je izgleda vezano za hardver?

Kada se BSOD desio nisam imao ništa overklokovano niti mi je po defaultu bilo šta overklokovano sem kada igram igre, i opet to je samo grafička.

Radio je Chrome, OS se "smrzao" na sekundu i desio se restart.

Imate li predstavu šta bi moglo biti ?

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Daj nam izveštaj programa WhoCrashed, detaljniji je od BluescreenView:

Preuzmi instalaciju za WhoCrashed program sa sledeceg linka:
http://www.resplendence.com/download/whocrashedSetup.exe
Ovaj program ce analizom pokusati proveriti koji drajver je uzrocnik greske.
Napomena: ovaj program zahteva instalaciju.


Dvoklikom pokreni instalaciju i klikni Next. Stikliraj opciju I Accept the agreement pa zatim ponovo na Next.
Program instaliraj na onu lokaciju i pod onim imenom koju ti program ponudi.
Klikni na Next i u sledecem prozoru klikni Next
Stikliraj opciju Create a Desktop Icon i potom klikni na Next pa zatim na Install.




Kada instaliras WhoCrashed program,pokreni ga.

Napomena: Ukoliko ti program izbaci obavestenje koje bi trebalo da izgleda ovako:

Klikni na Download the requested file from Microsoft site now i pricekaj da se proces
preuzimanja dodatnih fajlova i njihova instalacija dovrsi.


Kada se program pokrene klikni na dugme Analyze.
Kada program zavrsi analizu izbacice ti prozor sa obavestenjem. Klikni Ok.

Desni klik na prostor stranice programa sa izvestajem i izaberi opciju Select All.
Desni klik na prostor stranice programa sa izvestajem i izaberi opciju Copy
Otvori novi notepad i izaberi opciju Paste da bi kopirao sadrzaj loga u notepad.

Sada mozes zatvoriti program.

Okaci notepad sa sadrzajem loga u sledecu poruku.

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Uloguj se preko Facebooka da bi skinuo fajl:

https://www.mycity.rs/must-login.png

Imaš il neki predlog za aplikaciju koja može da loguje temperature u pozadini ?

Mada, ne verujem da je temperatura. Baš kada se BSOD desio nisam ništa zahtevno radio a pre toga računar bio pod "punim pritiskom" satima i nije bilo problema...

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Izgleda da je u pitanju hardverski problem (overclock?), mada se u nekim slučajevima kao razlog pojavljuje i drajver ili bug u Windowsu koji prikazuje 0x124 Bugcheck kode kao hardvesrski problem a u stvari je nešto do softvera.

Probaćemo da izvučemo podatke o tome šta je uzrok BSOS-a preko Windows SDK, a ti, ako možeš, pošalji ta dva dmp fajla uz poruku (ako nisu preveliki).
Program za praćenje i logovanje temperatura? Probaj sa HWINFO.

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Uloguj se preko Facebooka da bi skinuo fajl:

https://www.mycity.rs/must-login.png

https://www.mycity.rs/must-login.png

Klok vrednosti su bile standardne kada se desio BSOD.

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Uloguj se preko Facebooka da bi skinuo fajl:

Napisano: 16 Nov 2014 9:56

WHEA_UNCORRECTABLE_ERROR

Citat:This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

Dopuna: 16 Nov 2014 10:41

Trebace nam event log za aplikaciju i sistem. Ovo su vremena.

Sat 15.11.2014 23:32:10

Fri 7.11.2014 1:51:22

Dopuna: 16 Nov 2014 10:44

Evo izvestaja, koji se dobijaju kad se dump provuce kroz debugger.


https://www.mycity.rs/must-login.png

https://www.mycity.rs/must-login.png

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Application :
15.11.2014 23:31:39 Tip : Information

Log Name:      Application
Source:        gupdate
Date:          15.11.2014 23:31:39
Event ID:      0
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Srki94
Description:
The description for Event ID 0 from source gupdate cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Service stopped

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="gupdate" />
    <EventID Qualifiers="0">0</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-11-15T22:31:39.000000000Z" />
    <EventRecordID>28659</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Srki94</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Service stopped</Data>
  </EventData>
</Event>

Application loga za 7. nema.

System :
Opet nema tačnog unosa za 15.11, evo najranijeg pre njega :

Log Name:      System
Source:        Service Control Manager
Date:          15.11.2014 23:31:39
Event ID:      7036
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Srki94
Description:
The Google Update Service (gupdate) service entered the stopped state.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="16384">7036</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2014-11-15T22:31:39.003014300Z" />
    <EventRecordID>108801</EventRecordID>
    <Correlation />
    <Execution ProcessID="992" ThreadID="5468" />
    <Channel>System</Channel>
    <Computer>Srki94</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">Google Update Service (gupdate)</Data>
    <Data Name="param2">stopped</Data>
    <Binary>67007500700064006100740065002F0031000000</Binary>
  </EventData>
</Event>

Nema ni unosa za 7.11, evo najranijeg pre njega :

Log Name:      System
Source:        Service Control Manager
Date:          7.11.2014 1:49:25
Event ID:      7036
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Srki94
Description:
The Application Experience service entered the running state.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="16384">7036</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2014-11-07T00:49:25.451141900Z" />
    <EventRecordID>104067</EventRecordID>
    <Correlation />
    <Execution ProcessID="988" ThreadID="6716" />
    <Channel>System</Channel>
    <Computer>Srki94</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">Application Experience</Data>
    <Data Name="param2">running</Data>
    <Binary>410065004C006F006F006B00750070005300760063002F0034000000</Binary>
  </EventData>
</Event>

Dakle nema nikakvih error unosa u event vieweru za te datume, niti blizu njih... Kako u Application tako i u System tabu.

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Analiza WinDebug programa:

Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Sloba\Desktop\96967_540457979_111614-34928-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at start of path element
Error: Empty Path.
Symbol search path is:     SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`03258000 PsLoadedModuleList = 0xfffff800`0349b890
Debug session time: Sun Nov 16 00:32:10.704 2014 (UTC + 1:00)
System Uptime: 0 days 0:00:10.843
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

...................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007fcc5d8, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner
---------

2: 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
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007fcc5d8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre

STACK_TEXT: 
fffff880`031d95b0 fffff800`03518cb9 : fffffa80`07fcc5b0 fffffa80`06d02660 00000000`0000000d 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031d9ad0 fffff800`033f9ea7 : fffffa80`07fcc5b0 fffff800`034732d8 fffffa80`06d02660 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031d9b00 fffff800`03361275 : fffff800`034d4d00 00000000`00000001 fffffa80`07c7c820 fffffa80`06d02660 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031d9b40 fffff800`032d7261 : fffff880`00c30e00 fffff800`03361250 fffffa80`06d02600 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031d9b70 fffff800`0356973a : 00000000`00000000 fffffa80`06d02660 00000000`00000080 fffffa80`06cf1740 : nt!ExpWorkerThread+0x111
fffff880`031d9c00 fffff800`032be8e6 : fffff880`02fd7180 fffffa80`06d02660 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031d9c40 00000000`00000000 : fffff880`031da000 fffff880`031d4000 fffff880`031d91a0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION: 

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_authenticamd_processor_cache_prv

FAILURE_ID_HASH:  {1ad1b150-35c8-1f65-d8fb-43448eb460cb}

Followup: MachineOwner
---------


WARNING: Whitespace at start of path element
Error: Empty Path.

Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Sloba\Desktop\96967_934736010_110714-47408-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at start of path element
Error: Empty Path.
Symbol search path is:     SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`03202000 PsLoadedModuleList = 0xfffff800`03445890
Debug session time: Fri Nov  7 02:51:22.605 2014 (UTC + 1:00)
System Uptime: 0 days 0:00:13.792
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

...................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004c268f8, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner
---------

3: 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
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004c268f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre

STACK_TEXT: 
fffff880`031f55b0 fffff800`034c2cb9 : fffffa80`04c268d0 fffffa80`03cc9660 00000000`0000000e 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031f5ad0 fffff800`033a3ea7 : fffffa80`04c268d0 fffff800`0341d2d8 fffffa80`03cc9660 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031f5b00 fffff800`0330b275 : fffff800`0347ed00 00000000`00000001 fffffa80`04f0c760 fffffa80`03cc9660 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031f5b40 fffff800`03281261 : fffff880`0108be00 fffff800`0330b250 fffffa80`03cc9600 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031f5b70 fffff800`0351373a : 00000000`00000000 fffffa80`03cc9660 00000000`00000080 fffffa80`03cb9890 : nt!ExpWorkerThread+0x111
fffff880`031f5c00 fffff800`032688e6 : fffff880`02fd7180 fffffa80`03cc9660 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031f5c40 00000000`00000000 : fffff880`031f6000 fffff880`031f0000 fffff880`041a1180 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION: 

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_authenticamd_processor_bus_prv

FAILURE_ID_HASH:  {78c2f422-5335-4ef3-5cef-a28518da5023}

Followup: MachineOwner
---------