BSOD Event ID 1001 Bug Check 0x00000124 caused by ntoskrnl.exe driver

skopischke · Jan 15, 2012

Hello,

When I first started to encounter BSOD issues I was originally getting event id 18, Machine check exception, Translation Lookaside Buffer errors which I assumed was an issue with my CPU. I contacted Intel and they stated to me that Windows 7 was not correctly dumping the right information which is why it states the event id 18 error. They stated that it may be an issue with the motherboard or memory.

I have ran Memtest 86+ for 15+ passes and 0 errors were discovered. I have also done this with 1-4 memory sticks installed on the motherboard. I was able to run Prime95 overnight multiple times with 2 memory sticks installed and the only time it BSOD'd was with 1 module and this only happened once. The next day I ran Prime95 on the one module and it didn't BSOD.

The BSOD's are intermitten and happen more often when I am playing games. I have encountered the same BSOD when checking email, downloading files from the internet, and even when the CPU is idling at 0% with absolutely nothing running at all. The Blue ScreenView indicates the exact same parameters and that they are being reported from the ntoskrnl.exe driver.

In the past the most common driver that reported the BSOD's was the hal.dll driver. I have swapped my graphics card, network card, memory modules and I am still getting BSOD's. These parts I have tested on another computer and they work correctly. I have reinstalled the OS 3 times over the last year.

I am currently in contact with ASUS to see if the issue resides on the motherboard which is the only thing I haven't been able to swap including the processor. I have ran Memtest 86 and 86+, Prime95, Sisandra Lite, Linx, IPDTx64, as well as many other diagnostics/benchmarking tools with passing results. There are no specific times that this occurs and it can happen at any moment.

Any help in understanding what my issue is would be appreciated. When the system works fine I am very happy and it performs flawlessly. I hope that maybe I am having a driver or hardware issue and it is a simple fix.I have posted additional information you requested below including the attached .zip file named 'skopischke_BSOD.zip'

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Windows 7 Professional x64
- an OEM or full retail version? OEM = came pre-installed on system
- What is the age of system (hardware)? Purchased in February of 2011
- What is the age of OS installation (have you re-installed the OS?) Reinstalled OS 3 times, last reinstall was December 19, 2011.

JMH · Jan 15, 2012

0x124 is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress

Some generic advice.

If you are overclocking STOP.
Return to the default settings at least for now.

If you are running a RAID update its driver.

You can read more on this error and what to try here...

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

cluberti · Jan 15, 2012

In this case, it's a translation lookaside buffer error:

Code:

2: kd> !errrec fffffa80088e1028
...
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80088e1138
Section       @ fffffa80088e12c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
Error         : [COLOR=red][B]DTLBL0_ERR[/B][/COLOR] (Proc 2 Bank 4)
  Status      : 0xb200000000000014
 
2: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 2808
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 30 Stepping 5
ProcessorNameString = REG_SZ Intel(R) Core(TM) i5 CPU         760  @ 2.80GHz
Update Signature = REG_BINARY 0,0,0,0,4,0,0,0
Update Status = REG_DWORD 6
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD 400000000
 
2: kd> !sysinfo smbios
[SMBIOS Data Tables v2.6]
[DMI Version - 38]
[2.0 Calling Convention - No]
[Table Size - 2394 bytes]
[BIOS Information (Type 0) - Length 24 - Handle 0000h]
  Vendor                        American Megatrends Inc.
  BIOS Version                  1602   
  BIOS Starting Address Segment f000
  BIOS Release Date             12/16/2010
  BIOS ROM Size                 200000
  BIOS Characteristics
       04: - ISA Supported
       07: - PCI Supported
       09: - Plug and Play Supported
       10: - APM Supported
       11: - Upgradeable FLASH BIOS
       12: - BIOS Shadowing Supported
       14: - ESCD Supported
       15: - CD-Boot Supported
       16: - Selectable Boot Supported
       17: - BIOS ROM Socketed
       19: - EDD Supported
       23: - 1.2MB Floppy Supported
       24: - 720KB Floppy Supported
       25: - 2.88MB Floppy Supported
       26: - Print Screen Device Supported
       27: - Keyboard Services Supported
       28: - Serial Services Supported
       29: - Printer Services Supported
       30: - CGA/Mono Services Supported
       32: - BIOS Vendor Reserved
  BIOS Characteristic Extensions
       00: - ACPI Supported
       01: - USB Legacy Supported
       04: - LS120-Boot Supported
       05: - ATAPI ZIP-Boot Supported
       08: - BIOS Boot Specification Supported
       10: - Specification Reserved
  BIOS Major Revision           8
  BIOS Minor Revision           15
  EC Firmware Major Revision    255
  EC Firmware Minor Revision    255
[System Information (Type 1) - Length 27 - Handle 0001h]
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
  Version                       System Version
  Serial Number                                     
  UUID                          00000000-0000-0000-0000-000000000000
  Wakeup Type                   Power Switch
  SKUNumber                     To Be Filled By O.E.M.
  Family                        To Be Filled By O.E.M.
[BaseBoard Information (Type 2) - Length 15 - Handle 0002h]
  Manufacturer                  ASUSTeK Computer INC.
  Product                       P7P55D-E LX
  Version                       Rev 1.xx
  Serial Number                                
  Asset Tag

Given that a TLB miss in hardware or software is not fatal (if the virtual address is not stored in the TLB, it's simply computed and found manually from other source data), and we're crashing on a TLB failure, that would mean the hardware (in this case, the CPU) determined there was corruption or some other sort of hardware error in the data itself, and told Windows that it had experienced an unrecoverable hardware error. Note that this could be a CPU error, but this can also be a memory (RAM) error or a motherboard/BIOS error (just look up TLB errors with nvidia chipsets over the last few years). If you have the latest BIOS for that motherboard (which you do, according to the dump and the corresponding version listed on Asus' site for that model), you need to do a thorough RAM test before considering the CPU or motherboard bad. You did mention you had one issue with the RAM once (which didn't manifest on a subsequent test of that module), which would indicate that the RAM itself potentially is fine but the CPU or motherboard is bad. Given your symptoms, I'm inclined to believe it's the CPU, but I have seen bad motherboards cause this.

Unfortunately, this is *not* an easy one to nail down if you don't have sets of known-good working RAM and another known-good working CPU to swap in and test the motherboard with. If all of this is fairly new, I would consider an RMA of the whole lot if none of the vendors (CPU, mobo, RAM) give you a definitive answer one way or the other about their hardware being "good" or "bad", but that's just me.

BSOD Event ID 1001 Bug Check 0x00000124 caused by ntoskrnl.exe driver

skopischke

New member

Attachments

My Computer

JMH

Banned

My Computer

cluberti

Cat herder

My Computer