BSOD from NTOSKRNL.EXE, 0x00000101, even after reinstalling OS

[Namo]

Hopefully someone here can help me out, this has been driving me mad.

I'd been getting a lot of BSODs related to various drivers from all sorts of sources, such as AMD drivers and network drivers, and I read that this may be due to "leftover drivers" and registry entries left behind after updating drivers. I didn't much feel like tracking down and cleaning out all this so I just opted to reinstall Windows which has helped in the past.

I thought it did help this time but I got a BSOD again a short time ago related to NTOSKRNL.exe with a 0x00000101 bug check code, which I'd seen before I reinstalled Windows. (I'm getting this info from Bluescreen View, the BSOD itself said "A clock interrupt was not received on a secondary processor within the allocated time interval")

Please help, I'm at the end of my rope here. What info do you need from me to help me get this sorted?

EDIT: Added the required Seven Forums Diagnostic .zip file. My bad, should have read before posting.

 

[YoYo155]

Hey Namo, welcome to SF .

0x101, unfortunately this bug check code doesn't contain enough
information in the minidump file be analyzed fully.

Please upload the Kernel dump file using Dropbox or Skydrive, the file is located in the Windows directory
and is usually a few hundred Megabytes in size.

C:\Windows\MEMORY.dmp

The single hint I can get from the minidump is with relation to the GPU (Graphics card).

What is the make, model and age of your PSU (Power Supply)?
Fill out this form and post back the result:

• Power Supply Calculator

:ar: Test for thermals and stability:

• Download HWinfo and post a Screenshot of the sensors window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.
  • Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).
     Note

  It is not mandatory to run both tests simultaneously, although possible as long as the temperatures are under constant monitoring.

:ar: Testing the RAM:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

When done with the testing procedure take a picture and upload it here.

:ar: This will help you to determine where the issue is origination from (if any):

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[Namo]

My MEMORY.DMP is 1.31 GB. https://dl.dropboxusercontent.com/u/19151812/MEMORY.DMP

My PSU is this: SeaSonic M12II 520 Bronze 520W. I bought it new in September 2012. (My PC was built in September 2012.) The Power Supply Calculator gave me 362W but there were a few things on the form I didn't know what to put for.

I've attached the requested screenshots of HWiNFO. I should note that my PC hard froze (just stopped responding; no BSOD) after attempting to close Prime95; Furmark and HWiNFO were already closed.

I ran a pass on Memtest86+ when all of this trouble first began and didn't get any errors, but it was only one pass. I'll run a few passes and post again with a photo when I can.

Edit: Added photo of Memtest86+ screen. I ran it for as long as I could. At the rate it was going, 7 passes would have taken far too long. Hopefully this won't cause any problems, but the next time I'm sure I'll be away from the house for a few days I'll leave Memtest running.

Also, about two weeks ago I ran Furmark for about 30 minutes and nothing happened. Not sure if that's helpful or not.

 

[YoYo155]

Hi Namo, sorry for my short absence.

Thanks for the Kernel dump, I'm not seeing anything decisive so I'll offer a couple changes.
A quick question though, does the bugcheck (BSOD) happens
only when you are playing La-Mulana?

:ar: Install a previous release of the AMD PGU driver:
You're using version 13.9:

Driver Version    13.251.0.0

Uninstall Catalyst Control Center.
Then follow through with a pass of Driver Sweeper.

Download version 13.1
​

   Note

Install the display driver only! | Do not install the Catalyst Control Center software.

:ar: Please scan for possible infection and file corruption:

• Download TDSS-Killer and scan for rootkits.

:ar: Please update the BIOS:

!sysinfo machineid
Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=1146]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
[COLOR=Red][B]BiosVersion = P1.20
BiosReleaseDate = 06/15/2011[/B][/COLOR]
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
SystemFamily = To Be Filled By O.E.M.
SystemVersion = To Be Filled By O.E.M.
SystemSKU = To Be Filled By O.E.M.
BaseBoardManufacturer = ASRock
BaseBoardProduct = A75M-HVS
BaseBoardVersion =

   Warning

Flashing the BIOS is a risky procedure. If you are uncomfortable
performing it yourself have a technician perform it for you.
Regardless, flashing is at your own risk.

• Update to 1.70:
• View attachment 305336
• A75 Motherboard Series Manufacturing - ASRock Inc.

 

[Namo]

Actually yes, I only get BSODs during La-Mulana as of late. I also got a hard freeze while running GZDoom--not a blue screen, but the same kind of lock-up I get in La-Mulana right before a BSOD.

By the way, I was away from the house for a few days and ran Memtest the whole time. 23 passes, no errors. I can still post a photo if you want.

I'll try all that stuff and report back. Thank you for your help so far!

 

[Namo]

TDSS Killer found nothing, and I downgraded my GPU drivers as instructed. Ten minutes of La-Mulana gave me a crash, only it wasn't a BSOD, it was more like the display glitched out. I'd gotten this kind of crash before downgrading my GPU drivers and before reinstalling Windows.

I haven't tried flashing the BIOS since it's risky. If you can't think of anything else that could be causing these crashes I'll try it.

 

[Scotty Mac]

Quick question, is your CPU overclocked? From my experience that 0x101 code for me was not enough cache ratio/uncore voltage. Even sometimes it would be not enough core voltage. That Usually shows up as 0x124. but it can be 0x101. If it's not oc'ed, then disregard this

 

[Namo]

It was overclocked previously but isn't anymore, though; I disabled the overclocking once I started getting these crashes. The thing is, it'd apparently been overclocked since day one and I didn't know it; the friends of mine who built my PC probably enabled that for me before sending it to me. The moment I saw it was overclocked, my reaction was basically "Oh shit it was overclocked this whole time?!" and disabled it immediately, since I hear OC'ing is dangerous.

Could it possibly still be a power supply issue, despite not being overclocked anymore?

 

[Scotty Mac]

Well first off over clocking can be dangerous if you do not know what you're doing. Over clocking may shorten the life of the hardware that is overclocked. But then again, time also deteriates components too. You said you got that PSU in September 2012 right? Seasonic makes pretty good PSUs. First things I would try is what Yo Yo said to do before looking to the hardware. Update that BIOS. Flashing (updating) the BIOS is risky, but that's only if you lose power to your PC. So make sure you're not in a storm or anything. Look around in your BIOS for an option to set everything back to their default settings. For safety and backup, download the newer BIOS onto a USB drive. My advice tho, is to really look at your BIOS, get to know what does what. See, with my motherboard I put the BIOS on a thumb drive and used the installed flash that's on my board. I'm not sure if yours has that option or not. This is why I said look really good at your BIOS. Or even go to the website and look there.
On a side note, overclocking is not a bad thing. Unless you have it on a constant 24/7 oc. Which I personally don't because I don't do any folding. My OC kicks in when it needs to.

 

[Namo]

I was overclocked from basically day 1 of owning my new PC until about a month ago when I noticed it had been turned on (most likely, anyway--I don't recall ever overclocking myself so I can only assume it was done by the friends who put my PC together, unless some update to AMD's terrible Catalyst Control Center overclocked it for me). I do--er, did--run a good number of 3D games on this PC on high settings, though. But I feel like if I messed something up by being overclocked it'd have happened a long time ago. Could be totally wrong, of course. This is the first PC I've had where I've overclocked, even if it was without my knowledge, haha.

Either way, I'll try updating the BIOS once this storm passes. Thanks for the info, Scotty Mac.

 

[Scotty Mac]

I've heard good and bad things about that Catalyst. Just install the basic drivers for that video card. I'm pretty sure you didn't OC the CPU on accident .
Did you go into your current BIOS and set it all back to default? If so, that's a good step.
After you have done that part. Look for your "clear CMOS" button. Refer to the motherboards manual to find this button. DO NOT press that button unless your computer is powered OFF.
Once you have successfully understood the flashing (updating) process for that board, then attempt it. As I said earlier.. know your BIOS and know it well. It really pays off

 

[Namo]

I seemed to have done something wrong with updating the BIOS. I didn't damage anything, it's just when I ran the installer, nothing happened and my computer froze.

Is updating the BIOS absolutely necessary, do you think? I'd rather not risk break something because, even though I'm getting BSODs and occasional freezes, I'd rather have a computer that works but freezes occasionally than one that doesn't work at all, at least until I can afford new parts if necessary.

So would it be possible to continue troubleshooting and assume the BIOS aren't causing any issues, or do you think these outdated BIOS are absolutely a problem?

 

[Namo]

Just now my PC crashed but instead of going to a BSOD, the display just garbled up and I had to power off my PC. I was just using a web browser and a few other inconsequential programs, such as this thing and Tweetdeck.

This has happened twice in 24 hours, actually, and this is the fifth or so time it's happened in the past few weeks. I got a photo of it the first time it happened and I've attached it to this post. I didn't post about it the first time because I figured it was just a fluke.

Probably safe to say this is related to my other problems?

 

[Namo]

Alright, something astoundingly weird is happening.

I was using the free trial of Malwarebytes Anti-Malware and it expired yesterday, so every so often a little text bubble would appear telling me my trial was over and to click the bubble to see what to do about it. Clicking it brings up the screenshot of the window attached.

Clicking on the third option, "End Trial", makes my PC crash in the same way as my last post--screen garbled, have to shut it off manually. And it's extremely consistent. I've clicked it three times and each time the same crash. It doesn't matter what programs were running, either. The first time I had a browser with a livestream open, the second time some Windows startup programs were opening up, the third time I'd given my PC enough time to get all the startup programs running and everything.

So like I said, extremely weird, but hopefully whatever MBAM is doing to consistently crash my PC can help us more easily diagnose the root cause of my crashes, maybe? I've made a restore point just in case clicking on "End Trial" actually works one of these times.

Edit: After making this post I clicked on "End Trial" a fourth time just to make sure this wasn't three consecutive flukes, and no, it's not. It did it again.

 

[Namo]

I don't mean to keep posting in a row like this but the crashes are getting more frequent. Now in the past 24 hours my PC has frozen twice, similarly to the way it did in post 13, only instead of the screen getting scrambled, everything just halted entirely.

I wasn't really running any programs I hadn't been able to use before without any issues, just a web browser.

 

[YoYo155]

Hi Namo, please excuse my recent absence.

In light of recent events I recommend physically removing the GPU from the machine
and using the APU's integrated graphics and see if the issues continue in the same fashion.

Also if you had any new BSOD's please upload them using the http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html.

 

[Namo]

I haven't actually had any more BSODs, it's all scrambled screen crashes and just complete halts. I'll try removing the GPU.

 

[Namo]

I came down with the flu and was unable to post until now.

I cleaned the dust out of my PC and unplugged the graphics card, but when I turned on the PC, I didnt receive a display signal. Is there something I have to do to switch to my APU's integrated graphics?

 

[Namo]

I think it's safe to rule out the graphics card being a problem. Last night I was able to run Steam, a VOIP client, and a game for four hours. Today, I was using Steam and a low-end game, but I had Firefox downloading something in the background. Firefox had one of its famous memory leaks and pow. Freeze.