STOP x101 - Clock Interrupt

H

hsmith1514

Member
Joined
Dec 16, 2013
Posts
14
Over the last month, I've been getting the STOP 0x101 BSOD. It seems to only happen if my CPU is running at above 90%, but it is sporadic. Sometimes stable, sometimes not. In an effort to resolve, I formatted and reinstalled my OS, along with updating all drivers and windows updates. I ran Verifier before the reformat, and it did not BSOD during the 2 days I had it running, which was right before I formatted. Along with the standard requested files, I also linked to the full MEMORY.DMP file in case it is needed. Any guidance would be much appreciated.

http://sdrv.ms/1c7WpIp <- MEMORY.DMP


· OS - Windows 7 Professional with SP1
· x64
· Has been this OS for about 18 months
· The OS is a full version that I've purchased from MS
· All the parts (HDDs, RAM, CPU, motherboard, video card) are about 18 months old
· Was just formatted and reinstalled clean yesterday (crashed again this morning)

· CPU - i7-980
· Video Card - Nvidia GeForce GT 610
· MotherBoard - Gigabyte EX58-UD3R v1.6
· Power Supply - ATX 850 watt

· Home-built PC
 

Attachments

Hi,

Thanks for the MEMORY.DMP, those help quite a bit when analyzing *101's. Unfortunately, it's corrupt and therefore I cannot seem to run any commands to get information, etc. Can you please enable Driver Verifier and leave it set to Kernel dump so we can get another MEMORY.DMP (this time hopefully not corrupt)?

Unable to read KLDR_DATA_TABLE_ENTRY at 33482824`4c8b48ff - NTSTATUS 0xC0000141
Click to expand...

^^ For reference, we usually see this in *124's and *101's when the CPU is at fault. We'll see.

Regards,

Patrick
 
Sure, thanks for the assistance. Only part I'm not totally sure about, what is meant by "leave it set to Kernel dump"?
 
Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure it's set to Kernel Memory Dump.

Regards,

Patrick
 
thanks, looks like it was set that way already. I will post back again when it crashes and gives me another dump file
 
Ok, it just now crashed again. For what it's worth, when the BSOD appears and it starts dumping physical memory to disk, it froze at 60. When these BSODs have been occurring, that is the norm (although the actual number it stops at varies), and the physical memory dump never actually gets to a completed state. I always end up having to hard-power off the machine. Also, this time a mini dump was not created. I linked to the new memory dump.

http://sdrv.ms/1czbptG <-- MEMORY.DMP
 
Another crash, and this one generated a Minidump, so I zipped and attached it. I went ahead and uploaded the newest MEMORY.DMP from this crash. The "dumping physical memory to disk" on the blue screen got to 70 this time before freezing up.

http://sdrv.ms/1bYR6t2 <-- newest MEMORY.DMP
 

Attachments

Good evening.

Both of the kernel dumps are corrupt are usual.

We're still seeing -
Unable to read KLDR_DATA_TABLE_ENTRY at 70ca5944`37d86c44 - NTSTATUS 0xC0000141
Click to expand...

and

possible paged-out or corrupt data.
Click to expand...

and

Page c10e3a435 too large to be in the dump file.
Page c6c4a7103 too large to be in the dump file.
Page a6e305ca8 too large to be in the dump file.
Page 9503c0f61 too large to be in the dump file.
Page 9457a6fca too large to be in the dump file.
Page 4c0e4ed88 too large to be in the dump file.
Click to expand...

With all of this said, I am almost 90% sure your CPU is biting the dust. There are few other possibilities which I will go through:

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - Speccy - System Information - Free Download

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - How To Clear CMOS (Reset BIOS)

3. Ensure your BIOS is up to date.

4. If all of the above fail, the only left to do is replace your processor as it is faulty.

5. There may be an incorrect setting in regards to your page file:

Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.
Click to expand...

6. If you'd like, to be sure your RAM isn't at fault, you can go ahead and run a Memtest for NO LESS than ~8 passes (several hours):

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

Regards,

Patrick
 
I ran Memtest86 overnight, and zero errors were reported. I went ahead and ordered a replacement CPU. Thanks for the assistance and pointing me in the right direction.
 
@Patrick

I understand that _KLDR_DATA_TABLE_ENTRY is some kind of data structure, which is sparely documented on the web. However, I think I may have found the answer on MSDN.

The _KLDR_DATA_TABLE_ENTRY may possibly be used with the PEB_LDR_DATA data structure which used to show information about the loaded modules for a process. The LDR_DATA_TABLE_ENTRY is then used to represent entries in a doubly linked list. I'm assuming the K may be a prefix for a Kernel version?

KernelMode.info ? View topic - Crash on x64 when dereferencing LIST_ENTRY

The NTStatus error code 0xC0000141 is documented as STATUS_INVALID_ADDRESS:

The address handle that was given to the transport was invalid.
Click to expand...

PEB_LDR_DATA structure (Windows)
May « 2012 « Just Let It Flow
 
hsmith1514 said:
I ran Memtest86 overnight, and zero errors were reported. I went ahead and ordered a replacement CPU. Thanks for the assistance and pointing me in the right direction.
Click to expand...

You jumped the gun quite a bit there! Did you make sure your BIOS was up to date, temperatures were okay, CMOS was cleared just in case of any improper BIOS settings, double check and fix the pagefile, etc?

Regards,

Patrick
 
I had already done all of that (except for the changing the page file) prior to my initial posting. BIOS upgraded and downgraded, just to test other versions, always using optimized defaults. Idle temps at 28-30, load temp peak at 60, well within the range for that chip. Since my pagefile hasn't changed in 18 months, I just assumed (maybe incorrectly) that it wouldn't be to blame, especially after formatting. The CPU was under warranty, so no cost for the exchange other than shipping. Once I get the new one installed Thursday or Friday, I'll post back my results, good or bad.
 
Well, I got the replacement CPU installed, and it crashed again yesterday afternoon, and froze like normal during the "dumping physical memory to disk" stage of the BSOD, so I assume corrupt dump file. Just as a test, I changed the pagefile settings to allow for Windows to manage the pagefile, rebooted, commenced more stress testing, and waited. Sure enough, late last night it crashed again, but this time it apparently BSOD'd with a x124 error instead of x101. The PC was actually shut down, and not frozen on the BSOD screen, so I think it may have actually generated a successful memory dump. I attached the newest minidump file, and uploaded/linked the new MEMORY.DMP. Hopefully some useful information can be gleaned from it.

http://sdrv.ms/1bYAH3F <-- MEMORY.DMP
 

Attachments

Right, good, we did get a proper dump!

The attached DMP file is of the WHEA_UNCORRECTABLE_ERROR (124) bugcheck.

A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).

If we run an !errrec on the 2nd parameter of the bugcheck (address of the WER structure) we get the following:

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

[COLOR=#ff0000][I][B]Error         : Internal timer (Proc 1 Bank 5)[/B][/I][/COLOR]
  Status      : 0xbe00000000800400
  Address     : 0x000000000042d28b
  Misc.       : 0x0000000000000000

We have an internal CPU timer failure, specifically on Processor 1 and Cache Bank 5. This type of error is extremely strange to see as you just REPLACED the CPU entirely. If you have the system at full defaults, latest BIOS, latest chipset drivers, etc.... I'd like to test your RAM to see if there's possibly an issue there. With that said, run Memtest for NO LESS than ~8 passes (several hours):

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

Regards,

Patrick
 
I ran Memtest86+ using 10 passes, and it listed 0 errors. Since you said the previous BSOD was indicative of a hardware problem, I went ahead and threw in an old video card, just in case that was my culprit.
 
Back
Top