New Windows 10 Install leads to repeat BSOD [ntoskrnl.exe error]

Question

Hi everyone,

I have been having some issues with an old computer that I would like some help with. The computer has a fresh install of Windows 10 Home (64-bit) and repeatedly crashes to a BSOD within an hour.

Some background on the computer:

This is an old Lenovo IdeaCentre k330 (~11 years old) that has been an old faithful computer which I've only ever had to upgrade the GPU for. This computer has literally handled anything and everything I've thrown at it without a single crash or problem. I've upgraded to a new PC and gave this one to my girlfriend because it still works very well.

Here's where the problems begin. I took my old SSD out of this new computer and installed a new SSD for my GF, and then did a fresh install of Windows 10 Home. It worked as expected for a while but then gave me a BSOD citing an ntoskrnl.exe error.

I've parsed through several different forums, all of which have different solutions and none that work for me. I've checked the RAM, rewired all the internals, did another fresh install of Windows 10, tried changing power settings, updated Windows, etc. Nothing seems to work and I've come to a wall.

Here is a link to the .dmp files: https://drive.google.com/drive/folders/1VEeB3QpzZOy3uHRyHmN4-2j-S9vp9Mjr?usp=sharing

Some more info about the PC:

The machine is an old Lenovo IdeaCentre K330
CPU: Intel i7-2600
Motherboard: Custom Lenovo board, bios rev: 1.0
RAM: 12 GB
PSU: Corsair cx500M
GPU: Nvidia GTX 970
SSD: Samsung Evo 860 1TB

For whatever reason, the CPU usage percent is ALWAYS at 100%, even if there's nothing by task manager running. It also says the power usage is very high. The issue can't be malware as it is a brand new SSD, with a fresh install of windows. (See attached pic for more info).

Something else to note is that the machine still crashes on Safe Mode! This made me think it could be a hardware error or a problem tied to Windows 10 itself.

As I've said before, this computer has been with me for years and has never once crashed. I even played Resident Evil 2 Remake and Resident Evil 7 at max settings the week before I moved PCs.

We really want to get this computer back running and it's really important to me. Any and all help is appreciated!!

Task Manager CPU Usage

Answer 1

A final update for everyone:

Downgrading to Windows 8.1 has fixed all the problems with the computer. It has not crashed once and the CPU/Power Levels are normal.

I don't know if this is an issue Windows 10 could/should fix, but if anyone else has this problem, try downgrading.

Answer 2

One thing I need to say, don’t change hardware personally on a brand-name computer, even though you are an experienced computer user…
We cannot generate old Lenovo laptop is compatible with your new bought SSD and the latest Windows 10 system, its hardware configurations may only support some specific types of hard disk and Lenovo OEM system, our customization leads to BSOD.
On Windows side, reinstall system is the final method, since you have tried it, we have other system related methods for your device. What I can think of is similar to you: 1,hardware issue. 2,Windows 10 issue.
I suggest to reinstall previous Windows version such as Windows 8.1 or Windows 7 on your girl friend’s computer. Or just return the old SSD to the laptop and install the new SSD on your new computer, copy files is better than BSOD.

PS： dump file analysis doesn't supply any useful information
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000094, The exception code that was not handled
Arg2: fffff80547711266, The address that the exception occurred at
Arg3: ffffd20e92aee5e0, Parameter 0 of the exception
Arg4: 000000000000005a, Parameter 1 of the exception

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2671

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on MININT-372EJ2O

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 32355

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 76

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000094

BUGCHECK_P2: fffff80547711266

BUGCHECK_P3: ffffd20e92aee5e0

BUGCHECK_P4: 5a

EXCEPTION_PARAMETER1:  ffffd20e92aee5e0

EXCEPTION_PARAMETER2:  000000000000005a

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  WerFault.exe

BAD_STACK_POINTER:  fffff8054b27f158

STACK_TEXT:  
fffff805`4b27f158 fffff805`47900c3e     : 00000000`0000001e ffffffff`c0000094 fffff805`47711266 ffffd20e`92aee5e0 : nt!KeBugCheckEx
fffff805`4b27f160 fffff805`477e68e2     : fffff805`47900c1c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff805`4b27f1a0 fffff805`47632fb7     : fffff805`4b27f710 00000000`00000000 fffff805`4b271fb0 fffff805`477e4a65 : nt!RtlpExecuteHandlerForException+0x12
fffff805`4b27f1d0 fffff805`4767b226     : fffff805`4b2717b8 fffff805`4b27fe20 fffff805`4b2717b8 00000000`00000064 : nt!RtlDispatchException+0x297
fffff805`4b27f8f0 fffff805`477de8b2     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff805`4b27ffb0 fffff805`477de880     : fffff805`477efa65 ffffd20e`9ba82780 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff805`4b271678 fffff805`477efa65     : ffffd20e`9ba82780 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff805`4b271680 fffff805`477e870a     : ffffd20e`9a4c5ca4 ffffd20e`9a4c582c fffff805`4b271980 fffff805`4c320028 : nt!KiExceptionDispatch+0x125
fffff805`4b271860 fffff805`47711266     : ffffad00`cd8ab2e8 fffff805`4b271aa9 fffff805`4801ed28 00000000`00000000 : nt!KiDivideErrorFault+0x30a
fffff805`4b2719f0 fffff805`4771108e     : 00000010`069a6700 00000000`00000003 fffff805`480fb4e0 ffffd20e`92fb9010 : nt!PpmPerfSelectProcessorState+0x1a6
fffff805`4b271b10 fffff805`476a4810     : fffff805`43525240 fffff805`4b271e80 fffff805`4b271cb0 fffff805`4b271e80 : nt!PpmPerfSelectProcessorStates+0x5e
fffff805`4b271b40 fffff805`4763a69e     : fffff805`43525240 ffffd20e`90be8000 fffff805`4b271ec0 fffff805`00000002 : nt!PpmCheckRun+0x40
fffff805`4b271bb0 fffff805`47639984     : 00000000`00000000 00000000`00000000 00000000`00000008 00000000`0000019c : nt!KiExecuteAllDpcs+0x30e
fffff805`4b271d20 fffff805`477e4a65     : 00000000`00000000 fffff805`43522180 00000000`00000000 000001c4`949a30c0 : nt!KiRetireDpcList+0x1f4
fffff805`4b271fb0 fffff805`477e4850     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff107`359e0ad0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


SYMBOL_NAME:  nt!PpmPerfSelectProcessorState+1a6

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.264

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1a6

FAILURE_BUCKET_ID:  0x1E_c0000094_STACKPTR_ERROR_nt!PpmPerfSelectProcessorState

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a349e6fc-c773-5f1f-3d98-37443aaf47b7}

Followup:     MachineOwner
---------

Answer 3

Thanks! I'll give changing the SSD with my old one and/or installing Windows 8 a shot. I'll report back when I have some time to try those things.

Answer 4

I have random BSOD after 2004 update. Crash coming 1 - 10 min after boot. I re-installed 2004 from usb media. No success, situation the same. In my laptop installed i5 2450M cpu (ES) - engineering sample edition. in task manger cpu always 100%.

@walrusPanda00 look your cpu edition in cpu-z specification, I think you have too ES.

Here my dumps http://newestvision.com/public/dumps/

All help is appreciated! Thanks.

Answer 5

Hi everyone,

Sorry for the late update. I don't get to come visit my girlfriend as often because of the pandemic.

Today, I swapped the SSD with the exact SSD I had for the past 5 years. However, when we installed Windows 10 on it, it led to all the problems described above. All the internals are now the exact same as what was originally installed, and I did tests with the components before.

Could this be a windows 10 issue? I installed Windows 10 on this computer in February of this year. Until I built my new computer, this older computer ran fine but would randomly freeze after the upgrade.

I'm gonna try installing Windows 8 on it tonight and see if anything is fixed. If any of you have any other ideas, please let me know. It'd be really disappointing to throw away this computer because it has been such a good device and I know it still has a lot of power left in it.

Any advice appreciated.