Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

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

03 Feb 2014   #1

Windows 7 Ultimate x64
BSOD from NTOSKRNL.EXE, 0x00000101, even after reinstalling OS

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.

My System SpecsSystem Spec
04 Feb 2014   #2

Windows 10

Hey Namo, welcome to SF :) .

, 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.
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:

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   Note
    It is not mandatory to run both tests simultaneously, although possible as long as the temperatures are under constant monitoring.
Testing the RAM:

Quote   Quote: Originally Posted by koolkat77 View Post
Test and Diagnose RAM Issues with Memtest86+:
Tip   Tip
  • Pay close attention to part 3 of the tutorial "If you have errors"
  • 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.

This will help you to determine where the issue is origination from (if any):
Quote   Quote: Originally Posted by Arc View Post
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:
It is a RAM, a bad RAM.

But if you have got a result like that:
It is a motherboard issue. The particular slot is bad.
My System SpecsSystem Spec
04 Feb 2014   #3

Windows 7 Ultimate x64

My MEMORY.DMP is 1.31 GB.

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.
My System SpecsSystem Spec

07 Feb 2014   #4

Windows 10

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?

Install a previous release of the AMD PGU driver:
You're using version 13.9:
Driver Version
Uninstall Catalyst Control Center.
Then follow through with a pass of Driver Sweeper.
Download version 13.1
Note   Note
Install the display driver only! | Do not install the Catalyst Control Center software.

Please scan for possible infection and file corruption:

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.
BiosVersion = P1.20
BiosReleaseDate = 06/15/2011
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   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.

My System SpecsSystem Spec
11 Feb 2014   #5

Windows 7 Ultimate x64

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!
My System SpecsSystem Spec
12 Feb 2014   #6

Windows 7 Ultimate x64

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.
My System SpecsSystem Spec
12 Feb 2014   #7
Scotty Mac

Windows 7 64 bit SP1 OEM

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 :)
My System SpecsSystem Spec
12 Feb 2014   #8

Windows 7 Ultimate x64

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?
My System SpecsSystem Spec
12 Feb 2014   #9
Scotty Mac

Windows 7 64 bit SP1 OEM

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.
My System SpecsSystem Spec
12 Feb 2014   #10

Windows 7 Ultimate x64

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.
My System SpecsSystem Spec

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

Thread Tools

Similar help and support threads
Thread Forum
BSoD, STOP 0x00000101 - ntoskrnl.exe + nvlddmkm.sys
First of all, apologies if I miss something. This BSoD caused me to lose some unsaved data, and I am not happy. It happened multiple times in the past, but as I reset my PC to a system image, those minidumps aren't there. I would like to know if this could be caused by defective components, as...
BSOD Help and Support
Random BSOD multiple errors ntoskrnl.exe+75bc0 bug check 0x00000101
I am working on a laptop that has been getting random BSOD usually while nothing special is running. I have run memory checks, several antivirus scans to remove a lot of malware and trojans. Finally at my wits end with this. I would very much appreciate it if someone could point me in the right...
BSOD Help and Support
BSOD playing minecraft, error 0x00000101, ntoskrnl.exe
Hello everybody Since a couple of days I get a BSOD when I play Minecraft. The BSOD appears after a few minutes of playtime. It even appears when I am in the menus. Things i have tried: - Updating my video card drivers - updating my Java I am not really that handy with computers. If...
BSOD Help and Support
BSOD 0x00000101 (normally under load)
Hi. Had this rig for 6 months or less now, and have had nothing but problems. With some messing around with bios settings, I can sometimes get the system stable, but when some settings change it will go back to bsod'ing everywhere, and I can't even consider OC'ing. As I have mentioned in the...
BSOD Help and Support
BSOD happens randomly ' 0x00000101 '
I have bought a new computer last August - so it is 6 months old. Since I have got it, I randomly get the BSOD Stop 0x00000101 "A clock interrupt was not received on a secondary processor within the allocated time interval". I have updated all of my drivers, and now the computer is just...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 13:22.
Twitter Facebook Google+