Strangely consistent BSoD issues relating to ntoskrnl.exe

Loopyluke · 04 Feb 2015

Since around the 11/12th of jan this year, I have been getting oddly consistent bluescreens that appear to be related to ntoskrnl.exe, according to bluescreenview.
The first time I start my PC for the day, about 5-10 minutes later it bluescreens. It restarts itself, and runs fine for the next 10 hours or so, probably longer but I usually turn it off by then. Now the odd thing is if I restart manually a third time, it will bluescreen again after 5-10 mins, with the 4th restart stable again.
I've been putting up with this annoyance the past month, having searched for solutions and not finding much.

What I have done to try and solve this:

System restore to a restore point over a week before the issue started - no luck
Install windows updates that I've been putting off - nothing
Run memtest for 8+ passes - no issues found
Reseated RAM chips, swapped from the two in use slots to the two unused - nothing

I haven't tried the driver verifier yet, but I'm fairly confident that should turn up nothing, due to not updating/installing any drivers for a few months at least, including iDevices.
If someone could analyze the dump files I've provided, and suggest some things to try I'd be very grateful. Not really feeling like wiping my computer again til W10 comes out at least!

Golden · 06 Feb 2015

Code:

Host Name:                 LUKE-PC
OS Name:                   Microsoft Windows 7 Ultimate 
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Luke
Registered Organization:   
Product ID:                00426-OEM-8992662-00006

Counterfeit installations such as yours contains heavily modified code that causes the installation to behave it unexpected ways. Analysing BSOD's and determining their causes on these sorts of installations is very unreliable.

My recommendation is to start with a clean slate, and install a genuine version of Windows. This will minimise the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable. Once you are running a genuine Windows installation, and are still experiencing BSOD's, we will be happy to help you solve them :)