BSOD that is out of my knowledge range - 0x101

B

Benlightenment

Member
Joined
Sep 2, 2013
Posts
9
Hey all,

I've had to come here because I've tried all I can think of to get to the root of this problem I've been having, and now I need some help.
For the past month or two, I've been getting random blue screens (usually the 0x101. Sometimes another that I can't remember because it isn't fresh...) and I have no idea what is causing it.

It only seems to be when I play certain games, which happen to be MMOs. Both Guild Wars 2 and DC Universe Online have caused this problem, even though the computer is more than capable of handling them. Stranger still is that I can play new games like Payday 2 and ARMA 3 on full settings for hours on end and never have a single problem. I do usually run MMOs in Windowed mode, and with Firefox in the background (shouldn't make too much of a difference, but who knows!)

Back when it first happened, I ran Memtest and it had no problems, and for a while, things seemed to be okay. But now they seem to be happening with a bit of regularity again and it's getting annoying.

· OS - Windows 7
· x64
· Windows 7 was the OEM OS.
· 2 years old (roughly, bought in December)
· OS has never been reinstalled.

· Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz (8 CPUs), ~3.1GHz
· AMD Radeon 6950 2048mb
· ASUSTeK Computer INC. P6X58D-E Rev 1.xx

· Overclockers UK
· Ultima Hydrophobia" Intel Core i7 950 3.06GHz @ 4.00GHz DDR3 H2O System

Any and all help would be much appreciated! I've attached a rar of lots of stuff, including the things from the BSOD posting instructions (although the jcgriff2 app kept getting stuck on "Waiting for System Information to finish" even though it already had... I've attached all the files in any case).
 
Hi,

There are no DMP files located in your jcgriff output folder. Can you please manually navigate to %systemroot%\Minidump and zip up and attach any dumps here manually?

Regards,

Patrick
 
Patrick said:
Hi,

There are no DMP files located in your jcgriff output folder. Can you please manually navigate to %systemroot%\Minidump and zip up and attach any dumps here manually?

Regards,

Patrick
Click to expand...

Done that now. Just managed to force a crash after only 30 minutes or so playing. Not a blue screen though, just a hard lock up that needed a restart (though the "Windows has recovered from an unexpected shutdown" did call it a Blue Screen, so who knows!)
 

Attachments

Right, thanks.

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    @ fffffa800677ba08
Section       @ fffffa800677bb90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

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

You have an internal CPU timer failure on Processor 0 (first and primary CPU core) and Cache Bank 5. It's hard to make any calls for sure in regards to what the problem is when we only have one dump for now as we cannot check for consistency.

There is only so much you can do with a bugcheck like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

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 or overclocking - How To Clear CMOS (Reset BIOS)

3. Ensure your BIOS is up to date.

4. The only software conflict that can usually cause *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite. If you have something like this software-wise, remove it ASAP.

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

Regards,

Patrick
 
Thanks for the quick replies! So far, I've done 3 of the 5.

1. Temps seem normal (from what I can tell). CPU peaked at 63C under load in a game, and averaged about 50-58. GPU was about 40, and Motherboard/HDD were averaging around 33.
2. I've cleared this (I think) by choosing the Load Default Settings option. The CPU was advertised as OC'd, so I'm not sure if this reset it or not (and whether that's a cause of the problem)
4. I did have Asus AI Suite installed, which I didn't know of. I've uninstalled it now.

3 I've been checking on, but I'm unsure how to figure out exactly which version my BIOS is at. The board is this one, and from what I can tell, is at version 0502 from what I've seen in Speccy and others. Yet when I try to install the latest version, it tells me that my computer doesn't meet the requirements for this update. So I'm a bit stumped as to what to do next.

And obviously 5... well, I'm hoping it doesn't come to that!
 
Hi,

1. Those temps are fine.

2. Good work. Yes, when CPU's are 'advertised as stable' at a certain clock, it's generally just advertising garbage. You cannot guarantee stability, no matter what anyone says. What they do is purchase processors and find out what their 'stress programs' pass depending on the clock and voltage values they have set. By clearing the CMOS or loading optimized defaults, you're undoing this and bringing everything back to stock (non-overclocked) settings.

3. Don't worry about the BIOS right now, actually. We'll go into it further if we need to.

4. Good work.

5. Me neither :grin1:

Keep me updated.

Regards,

Patrick
 
Touch wood, no blue screen yet... things have seemed fine since those few little adjustments.

I've been keeping an eye on my temos though, out of paranoia, and I've seen them climb rather high. CPU and GPU were both hitting around 70C while running certain games, which made me a bit nervous. I did fire up the AMD Overdrive to increase the GPU fan speed a bit to try and keep it a bit lower, but that seems to have caused a new problem...

Since turning on today, I've noticed the PSU makes a little buzzing/electrical kind of noise sometimes, depending on what's going on. Googling it, it seems like a kind of common problem that I shouldn't worry about (it's a Corsair TX750W) but now I'm concerned it's something I've done!
 
Hi,

PSU buzzing and or coil whine is relatively normal at certain loads, no worries.

Regards,

Patrick
 
Almost a week with no problems where I thought everything was fine... then it happened.

I just had a hard lock while playing Payday 2. No bluescreen, no actual crash, so I couldn't tell what actually caused it. But once again the Windows Error dialog said BlueScreen. I was so hoping it was all fixed :/
 

Attachments

Hi,

Same bugcheck. . .

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

[COLOR=#ff0000][I][U][B]Error         : Internal timer (Proc 0 Bank 5)[/B][/U][/I][/COLOR]
  Status      : 0xfe00000000800400
  Address     : 0x000038800406d56a
  Misc.       : 0x0000000000007fff

Same error. Looks like a faulty CPU. Are you still under warranty?

Regards,

Patrick
 
Sadly not anymore :( The PC is coming up on 3 years old, and I'm pretty sure they wouldn't do anything about it now. I can try though...

Failing that, I guess it's time I start thinking about a replacement! Now to get some money saved...
 
Out of warranty, as expected :(

How long should a CPU like this last with faults? It'll probably talke me a little while to be able to get the money together, and as long as this isn't a completely serious problem that will escalate and escalate until it's just unusable, then I can probably manage. As it is, it seems pretty random and sparse when they do occur.
 
There's no definitive amount of time that can be determined as to how long your CPU will last with this issue. If you can manage how it is now, the best thing you can do is try and make the CPU as "comfortable" as possible: temperature reduction and underclocking. The higher the speed and temps, the more likely it'll trigger the bug in the hardware and make things unstable. It may get progressively worse as time goes on, but there's no way to tell unless actually seeing the system getting more and more unstable. Best just save as much as you can as early as you can to afford a replacement.

Also, try looking into that BIOS update further if at all possible. You said Speccy mentioned your bios is version 0502 when the one I see on the site is 0803. There may be timer bugs that have been fixed in the BIOS, so see what you can do about getting it updated.
 
Figured I'd revive this one rather than make a new thread!

My original issues have all gone! I did everything said in here, updated the BIOS, updated my graphics drivers and did a few other cleanups/changes and no blue screens.

Until today!

I had the following dump earlier from a bluescreen with the Registry Error call. Not knowing how to look through these dumps myself... I'd love it if someone else could and point me to the registry entry that's causing the issue!
 

Attachments

Hi,

The attached DMP file is of the REGISTRY_ERROR (51) bug check.

This indicates that a severe registry error has occurred.

This is almost exclusively caused when the registry is simply seriously corrupted and the only reasonable hope is to clean install the OS. It sometimes also however indicates that there was an I/O error while trying to read files from the registry (may be caused by a device driver). It's not very often I see this being caused by hardware.

Let's do the following:

1. ASACPI.sys - Wed Jul 15 23:31:29 2009

^^ Asus ATK0110 ACPI Utility. Also a part of many Asus utilities, Yours is dated from 2009 therefore it should be the stable version (pre 2009 is unstable). Check Asus' website just to be sure there are no updates - P6X58D-E - Motherboards - ASUS

2. Remove and replace AVG with Microsoft Security Essentials for temporary troubleshooting purposes:

AVG removal tool - AVG | Download tools and utilities

MSE - Microsoft Security Essentials - Microsoft Windows

If the above don't help, it'll be in your best interest to do a CLEAN install of Windows as this implies the registry is likely far too corrupt (we unfortunately cannot simply ABC123 fix the registry).

Regards,

Patrick
 
That's the thing though: this is a one off!

I've never had this BSOD before, and the one I had last night was the only one. Haven't had another yet.
Leading up to it, certain things kept crashing (mostly Firefox and Steam) and my initial thought was it was just Flash Player being irritating, as it likes doing that a lot. Then the BSOD popped a little later.

I can't really think of what might have caused it. I installed Blender recently, but other than that, the computer hasn't changed at all since my previous problems, and I haven't had a single issue until last night.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top