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.

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.

Code:

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

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.

Testing the RAM:

koolkat77 said:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   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):

Arc said:

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:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

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.

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:

Code:

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.

Please scan for possible infection and file corruption:

• Download TDSS-Killer and scan for rootkits.

Please update the BIOS:

Code:

!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

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:
• Attachment 305336
• A75 Motherboard Series Manufacturing - ASRock Inc.