BSOD in normal mode - safe mode no problem

[usanzac]

I am here at my wit's end. I believe I am satisfying the requirements to post my issue here.

The background: I have been in IT since the 1970s. In terms of Windows generally, I'm probably pushing a 4 on a scale of 1-5 where 1 is noob and 5 is guru. sevenforums has been a go-to place for me for a long time in terms of finding information. I applaud the great work of everyone that makes contributions here.

My primary laptop is a Qosmio 500-series with a teeny weeny 64GB SSD and a 512GB HDD. It runs Win7 Ultimate "tweaked" so that as little as possible is on the SSD. Program Files, Data and Users are all junctioned off to the HDD. This set up has worked great for five years.

A recent shutdown involving a random "recommended" update screwed things up royally. This particular update routinely failed, previously, because it was looking for files on the system drive that were actually on a different drive. It also turns out that Microsoft had chosen to push Win10 down on to my wee SSD and effectively reduced available storage from just enough to precious little.

My trouble began around this time when Windows could not load a valid user profile for any user and always started with a temporary profile.

I did fix the problem with the recommended update after all this pain began but it did not help. I also moved the Win10 stuff to the bigger drive (with a junction) and that did not help.

I have done all sorts of things to get to the point where I can boot and use normal (not temporary) profiles but within a minute or so of booting in normal mode, I am getting BSODs. At first, it was x51 (1, ..., 17F7000, 374) (REGISTRY_ERROR) but now it is x50 (page fault).

Bear in mind, actually getting BSODs and kernel dumps is a huge step forward. Prior to that, I was getting nothing; the computer would simply turn off as if someone pulled the plug from the wall.

Something related to the x51 error suggested the nVidia drivers so I uninstalled them. That got me to the x50 error and, my wit's end.

I apologize for the long recount, but I'd really like to cut to the chase to find solutions to stabilize this system. I have backups of everything that matters. All restore points have been exhausted, including those before "this" problem began, curiously. Exhaustive local and USB/CD anti-malware programs have been run. SFC reports no problems. CHKDSK /R on all drives show no issues. Memory tests all OK. HDD diagnostics all golden.

There are some "Events" that merit attention, bearing in mind many of them come from running in Safe Mode. The whole "Out Of the Box Experience" (OOBE) thing pertaining to Mickey Soft's Anti-Malware software and services is not new so I am assuming not relevant right now.

The attached file includes the latest dump.

Thanks in advance for any help with this.

 

[axe0]

Before I say what I intend to say, I'd like to mention 2 things first.

1. Before the bluescreen is logged, an event has been logged that indicates that your system is very hot, around 100C (212F according to Google)

Event[76730]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2016-01-15T01:51:04.658
  Event ID: 89
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: kununurra
  Description: 
ACPI thermal zone ACPI\ThermalZone\THRM has been enumerated.             
_PSV = 372K             
_TC1 = 2             
_TC2 = 3             
_TSP = 4000ms             
_AC0 = 0K             
_AC1 = 0K             
_AC2 = 0K             
_AC3 = 0K             
_AC4 = 0K             
_AC5 = 0K             
_AC6 = 0K             
_AC7 = 0K             
_AC8 = 0K             
_AC9 = 0K             
[COLOR="Red"]_CRT = 377K[/COLOR]             
_HOT = 0K             
_PSL - see event data.

2. Both the 0x50 and 0x51 have something common, hard drive failure and file system corruption.
To scan for NTFS corruption you need to scan your hard drives.
I would normally also suggest to run a system file check.


What I'm intended to say is that you are running an ASUS Product ID (PID) on a Toshiba board.
This makes your installation counterfeit.
Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.

OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          simon
Registered Organization:   
Product ID:                [COLOR="red"]00426-OEM-8992662-00173[/COLOR]
Original Install Date:     5/28/2011, 1:10:56 PM
System Boot Time:          1/15/2016, 1:59:16 AM
System Manufacturer:       TOSHIBA

I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.

 

[usanzac]

Thank you for the prompt response. I have had this laptop for about five years and it has always had heat issues. I have it on top of a three fan laptop cooler and often with an additional fan behind it. Nothing much seems to help. Different tools give me different readings but I have been able to keep CPU temps below 90°C for the most part. I am not alone with this issue; many have these problems with this range of Qosmios.

Far more importantly, however, is the Windows license problem. I bought this PC used from a private seller. The fact it had been "upgraded" to Ultimate sealed the deal. I see now that I was duped. However, I have gotten some good mileage out of it as my primary Windows machine. I envision its future as a second machine...probably running Ubuntu.

As far as my current issue is concerned, I'll give CCleaner, SFC and CHKDSK yet another crack. Not much else I can do and now that I know what I am dealing with, I will no longer waste the valuable time of all the many great folks out there who could help.

 

[axe0]

Ccleaner wouldn't help much, especially in the current state of the system I wouldn't use the registry part as it may cause more trouble.