BSOD with Stop 0x124_GenuineIntel_PROCESSOR_TLB

[christop]

I have a Clevo laptop from 2007. It crashed on 17 August with a Blue Screen giving an 0x124 error. Since then, I have been unable to start up Windows without it crashing again. I have been running the machine without problems in Safe Mode, sometimes for 24 hours at a stretch. I have tried using the Diagnostic startup in msconfig, but this also crashes.
The interior is free of dust, and both fans are operational. I tried running CPU Thermometer in normal mode, after letting the machine cool down. The machine ran long enough for me to see it reporting one core running at 53C, the other at 55C at the point the Blue Screen took over.
All of the dump files I have examined implicate the processor, most involving the Translation Lookaside Buffer.
I have been encouraged by reading The Complete Debugging Guide to Stop 0x124 on this forum to think that there may be a way to solve this problem, but I find the processes detailed there a little hard to follow.

Details requested on the Blue Screen of Death (BSOD) Posting Instructions:· The OS is Windows 7 (x64)
· The original installed OS was Windows Vista
· The current OS is the full retail version of Windows 7 Professional
· The system dates from 2007
· I upgraded to Windows 7 in 2014
· The CPU is an Intel Core 2 Duo T7500 2.20GHz
· The video Card is an NVIDIA Geforce 8700M GT
· The System Manufacturer is Clevo
· The model number is M570RU

I attach the SysnativeFileCollectionApp.zip file. I could not get perfmon to produce a report in Safe Mode.

 

[christop]

I have tried using the !errec extension on my dump files and am getting the message "No export errec found".

 

[blueelvis]

Hi Christop & Welcome to the forums ^_^,

I have tried using the !errec extension on my dump files and am getting the message "No export errec found".

Are you running the correct command? The correct command is !errrec instead of !errec. Also, are you passing the correct argument that is the second parameter of the dump file?

Like you said, there is a problem of Timeout in the Translation Lookaside Buffer and the most recent most dump says that there is a problem in the L0 cache of the CPU -

1: kd> !errrec fffffa80052814f8===============================================================================
Common Platform Error Record @ fffffa80052814f8
-------------------------------------------------------------------------------
Record Id     : 01d0e6f23f989a05
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 9/4/2015 9:15:37 (UTC)
Flags         : 0x00000002 PreviousError


===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8005281578
Section       @ fffffa8005281650
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal


Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000006fa
Processor ID  : 0x0000000000000000


===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80052815c0
Section       @ fffffa8005281710
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal


Local APIC Id : 0x0000000000000000
CPU Id        : fa 06 00 00 00 08 02 00 - bd e3 00 00 ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00


Proc. Info 0  @ fffffa8005281710


===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8005281608
Section       @ fffffa8005281790
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal


Error         : [B]BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)[/B]
  Status      : 0xf200080000000800

1: kd> !errrec fffffa80`056e2038
===============================================================================
Common Platform Error Record @ fffffa80056e2038
-------------------------------------------------------------------------------
Record Id     : 01d0e643ab80a327
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 9/3/2015 12:26:39 (UTC)
Flags         : 0x00000000


===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80056e20b8
Section       @ fffffa80056e2190
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal


Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : TLB error
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000006fa
Processor ID  : 0x0000000000000001


===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80056e2100
Section       @ fffffa80056e2250
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal


Local APIC Id : 0x0000000000000001
CPU Id        : fa 06 00 00 00 08 02 01 - bd e3 00 00 ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00


Proc. Info 0  @ fffffa80056e2250


===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80056e2148
Section       @ fffffa80056e22d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal


Error         : [B][U]DTLBL0_ERR (Proc 1 Bank 2)[/U][/B]
  Status      : 0xb200000000010014

The L0 Cache is consistent in the errors.

Furthermore, there is a very high chance that there is a problem with the CPU since most of the 0x124 are related to hardware.

Since you don't have much installed on the system, I would suggest you to take the laptop to the Customer Care and get it checked.



-Pranav

 

[christop]

Hi Christop & Welcome to the forums ^_^,

I have tried using the !errec extension on my dump files and am getting the message "No export errec found".

Are you running the correct command? The correct command is !errrec instead of !errec. Also, are you passing the correct argument that is the second parameter of the dump file?

Like you said, there is a problem of Timeout in the Translation Lookaside Buffer and the most recent most dump says that there is a problem in the L0 cache of the CPU -
The L0 Cache is consistent in the errors.

Furthermore, there is a very high chance that there is a problem with the CPU since most of the 0x124 are related to hardware.

Since you don't have much installed on the system, I would suggest you to take the laptop to the Customer Care and get it checked.



-Pranav

Thanks for the spelling correction! The !errrec extension is now working for me.

I have been working my way through The Complete Debugging Guide to Stop 0x124 carefully, trying to follow it.

I have used WinDbg for a number of years, but have never got much beyond clicking the !analyse -v. This has been a real learning experience for me.

I see that the SysnativeFileCollectionApp only gathered recent dump files. I have attached a copy of the original dump file from 17 August, which also seems to point to the L0 cache of the CPU.

I have ordered a replacement processor through Amazon, and I hope this will resolve the problem.

 

[christop]

I also tried using the !tzinfo extension to try and find if the processor was overheating, having first found the CPU identifier using !prcb, but I could not make much sense of the results, particularly the

Current Temperature:                 00000000 (0.0K)

result. I am assuming that the figure shows degrees Kelvin?

kd> !prcb
 PRCB for Processor 1 at fffff780ffff0000:
 Current IRQL -- 15
 Threads--  Current fffffa8006004060 Next 0000000000000000 Idle fffff880009f4f40
 Processor Index 1 Number (0, 1) GroupSetMember 2
 Interrupt Count -- 0ddc2be5
 PRCB for Processor 1 at fffff780ffff0000:
 Current IRQL -- 15
 Threads--  Current fffffa8006004060 Next 0000000000000000 Idle fffff880009f4f40
 Processor Index 1 Number (0, 1) GroupSetMember 2
 Interrupt Count -- 0ddc2be5
 Times -- Dpc    0000cd7f Interrupt 00007e46 
          Kernel 004cb146 User      001afea9 
 Times -- Dpc    0000cd7f Interrupt 00007e46 
          Kernel 004cb146 User      001afea9 
 1: kd> !tzinfo fffff780ffff0000
 1: kd> !tzinfo fffff780ffff0000
 ThermalInfo @ 0xfffff780ffff0000
   Stamp:         00001f80  Constant1:  00000001  Constant2:   06004060
   Period:        00000000  ActiveCnt:  00000000  AffinityEx:  0xfffff780ffff0010
   Current Temperature:                 00000000 (0.0K)
   Passive TripPoint Temperature:       80050031 (214781137.7K)
   Critical TripPoint Temperature:      00000000 (0.0K)
   Hibernate TripPoint Temperature:     00000000 (0.0K)
 ThermalInfo @ 0xfffff780ffff0000
   Stamp:         00001f80  Constant1:  00000001  Constant2:   06004060
   Period:        00000000  ActiveCnt:  00000000  AffinityEx:  0xfffff780ffff0010
   Current Temperature:                 00000000 (0.0K)
   Passive TripPoint Temperature:       80050031 (214781137.7K)
   Critical TripPoint Temperature:      00000000 (0.0K)
   Hibernate TripPoint Temperature:     00000000 (0.0K)

 

[blueelvis]

Hi Christop ^_^,


You are welcome :)

Regarding the !tzinfo command, the minidumps do not store the information regarding the Thermal Zones of the system. If I am correct (Not sure), you would be able to see the data structures regarding the Thermal Zone in Kernel Dumps and Complete Memory Dumps.

The temperature reported is in Kelvin :)

Also, if this was a problem due to overheating, we wouldn't see the constant pattern of L0 cache causing the problem. There would have been other effects which you would have experienced (Like sudden power off).


Also, when you say that you have ordered a replacement processor do you intend to replace the processor yourself? Asking because if you intend to do the replacement yourself, I would suggest you to be extremely careful since it won't be an easy task.


Let me know how it goes ^_^

-Pranav

 

[christop]

Also, when you say that you have ordered a replacement processor do you intend to replace the processor yourself? Asking because if you intend to do the replacement yourself, I would suggest you to be extremely careful since it won't be an easy task.


Let me know how it goes ^_^

-Pranav

Thanks for your concern. I am familiar with the inside of this machine. I also have the service manual for this model, which shows the steps quite clearly. I am aware of the importance of protecting against ESD; also that the CPU needs to be entered the right way round!

Amazon say the new processor should be with me in one or two weeks (it is coming from Japan). I will let you know how things go.

 

[blueelvis]

Thanks for your concern. I am familiar with the inside of this machine. I also have the service manual for this model, which shows the steps quite clearly. I am aware of the importance of protecting against ESD; also that the CPU needs to be entered the right way round!

Amazon say the new processor should be with me in one or two weeks (it is coming from Japan). I will let you know how things go.

Alright. Let me know how it goes :)


-Pranav

 

[Jared]

Regarding the !tzinfo command, the minidumps do not store the information regarding the Thermal Zones of the system. If I am correct (Not sure), you would be able to see the data structures regarding the Thermal Zone in Kernel Dumps and Complete Memory Dumps.

Correct.

Passive TripPoint Temperature:       80050031 (214781137.7K)

Made me laugh, over 14 times hotter than the core of our Sun.
Bit high. :r1:

 

[christop]

Sorry for the delay in reporting back to you. The processor did not arrive from Japan, and I had to find another source. I am pleased to report that with the replacement processor in place, everything now seems to be working. Many thanks for your assistance and expertise.
I have one more query if you are able to answer it. Whilst waiting for the processor to arrive, I read up about the Translation Lookaside Buffer. Can you suggest why the computer was able to run without crashing in Safe Mode, without a fully functioning processor?

 

[Jared]

Sorry for the delay in reporting back to you. The processor did not arrive from Japan, and I had to find another source. I am pleased to report that with the replacement processor in place, everything now seems to be working. Many thanks for your assistance and expertise.
I have one more query if you are able to answer it. Whilst waiting for the processor to arrive, I read up about the Translation Lookaside Buffer. Can you suggest why the computer was able to run without crashing in Safe Mode, without a fully functioning processor?

Difficult to say exactly why, but from the look of it, there was hardly any load on the processor in Safe Mode.