Anyone here a BSOD expert willing to take a gander at my logs?

[britechguy]

I definitely am not a BSOD expert and I have seen a recent uptick in BSODs on this machine, virtually always as part of doing a restart. In most cases I get all the standard messages from Windows that come if you have verbose shutdown enabled, but at the very end the "Restart circles" stop spinning, I usually have only one on the display, and the computer hangs for a short period of time, followed by the BSOD.

I did use NirSoft's BlueScreen View as well as BSODInspector (ancient) but I just am not good enough to dig through BSOD minidump files and make heads or tails of things.

The world's not coming to an end, but I'd love to figure out if there is something I could actually do to stop this or not.

I'm running Windows 11 Pro Version 22H2 on unsupported hardware where it's only the CPU that's the unsupported part. All the other requirements, including TPM, are met.

 

[Sky-Knight]

I'm running Windows 11 Pro Version 22H2 on unsupported hardware...

There, I found the problem for you.

Every single patch makes it worse, the platform is designed for an architecture you don't own and the only fix is a BIOS or driver update you will never get.

Get off 11, your machine isn't compatible.

The CPUs changed... I cannot explain specifically what's going on but Microsoft drew that line for many reasons, and the CPU is one of the larger ones.

 

[Fred Claus]

THere was just a Youtube video on running Windows 11 on an unsupported machine. I wonder if that is your problem. Do you know what the error said on the BSOD?

 

[britechguy]

Get off 11, your machine isn't compatible.

Not yet. Not by a long shot.

I went into this knowing that issues might crop up, but I'm far from the only one running Win11 on unsupported hardware and I'd prefer to keep the experiment going.

Anyone who does not care to assist in light of this absolutely should not do so. But saying, "dump Win11 on that machine," is a no-go at the moment as well.

 

[britechguy]

Do you know what the error said on the BSOD?

No, I don't, but that's what the logs/dump files are about. It's just that I do not have the requisite knowledge to know how to interpret them correctly.

It may be that bailing on Win11 on this machine is the ultimate solution. I can easily FABS my data off then restore from the Win10 image I took immediately prior to starting this experiment and FABS it back. I'm just not ready to go that route just yet.

Everything is going swimmingly, on the whole, except for this weird BSOD error that's limited to when I do a Restart (at least so far).

 

[Markverhyden]

I agree with @Sky-Knight to a certain extent. Even if it's only the CPU that's not supported you can't reliably determine what's the cause. If nothing BSOD's are notoriously unreliable in pinpointing problems. I'd try a new profile and see what happens rather than going on an extended snipe hunt.

 

[Markverhyden]

Does it happen every single time when you select reboot? Have you closed aqll open apps and windows before restarting? So what happens when you do a shutdown instead? Fire up Process Monitor see what it tells you.

 

[Fred Claus]

I'm really nerdy about things and I like to learn. When I find something new I store it in a digital notebook for future reference. Here is one I have about a Reboot loop in Windows 11.

Getting Windows 11 Boot Loop? Troubleshoot This Error Now - EaseUS

Are you getting a Windows 11 boot loop? Then, don't panic. Just check out this EaseUS troubleshoot guide to fix the error now and securely use your Windows 11 PC.

www.easeus.com

Might this help?

 

[Fred Claus]

Here's the video I was talking about

 

[Sky-Knight]

BSODs in Windows are stupidly rare these days.

They boil down to one of three things...

1.) Bad Driver (Most likely)
2.) Bad RAM
3.) Bad Power

There are other causes, but these three things are the reason for most intermittent and random BSOD events. The fact that the BSOD fails to identify a specific driver tells me it's a core system fault, which means the kernel can't even figure out what's up, and THAT happens when either your machine is infected beyond all recognition, or the software asked the hardware to do something it cannot do.

Your system isn't supported. The experiment is over. You lack the skill to dig deeper by your own admission, and you're asking the rest of us to volunteer our time for free to fix it for you. The list of things that are to be considered "rude" at best here are growing by the second.

The OS doesn't support that platform. Like it or not, that's full stop, do not pass go right there.

This will continue, and it will continue to get worse in time. The core security tech baked into Windows and the primary reason we've all been able to enjoy so much less malware on Win10 than previous versions of Windows is being pushed in new directions to ensure things stay that way... The farther this war goes, the more unstable your rig will be.

The new tech demanded by the system requirements is not optional, regardless of what the keyboard warriors on the Internet claim.

Finally, in my experience all issues related to BSOD on reboot or shutdown are BIOS/EFI related. And the latter is heavily CPU dependent.

 

[Diggs]

They boil down to one of three things...

1.) Bad Driver (Most likely)
2.) Bad RAM
3.) Bad Power

For me it is #2.
At least 75% of the BSODs I've had are memory related. Although I haven't seen it recently, memory used to fail at a surprising rate. If you have both sticks in start by taking one out.

 

[Sky-Knight]

For me it is #2.
At least 75% of the BSODs I've had are memory related. Although I haven't seen it recently, memory used to fail at a surprising rate. If you have both sticks in start by taking one out.

yeah... or for whatever reason they wake up one day and decide they're fine single channel, but want to be flaky when dual channel. RAM can be a real PITA when it decides to be, and the worst part? All this impacts SSDs too!

So is this machine faulting because Microsoft patched something to actually break it on this specific platform? Or is there a near impossible to troubleshoot problem with one of the components due to age?

If a client shows up with such a rig we have no choice but to replace it because we can never be sure it's "fixed".

 

[britechguy]

Does it happen every single time when you select reboot? Have you closed aqll open apps and windows before restarting? So what happens when you do a shutdown instead?

I really have no intention of snipe hunting over the long term.

It is now happening every single time do a Restart. When it comes to a Shutdown (and I don't have Fast Startup enabled) one of two things happens:

1. Everything looks ok but after the screen goes black (when it normally would) it's taking quite a while afterward before the machine actually powers down.
2. I get a BSOD during shutdown like I do with a Restart.

Neither of these were always the case. Startup is slower, too. I've already used CrystalDiskInfo along with Crucual Storage Executive to look at the SSD and both report good health.

I occasionally have AMD's Radeon Software come up at reboot after a BSOD saying that a BSOD was detected, and there is an indication in BlueScreen View that this is the occasional cause, but here's a screenshot from that program:

You'll notice that there are several in succession between 6:30 and 7:10 PM today, and the first three of those were during restarts done while applying 2023-04 Cumulative Update Preview for Windows 11 Version 22H2 for x64-based Systems (KB5025305). The last one was a test Shutdown that triggered a BSOD, and that was after one that did not, but was slow.

This is all a curiosity quest. If things ever get ugly during day to day use of the computer, I'll immediately roll back to Windows 10 via the system image I took. But I'm in the humor do play with this quite a bit more before I'd take that step.

Again, this has been an experiment from the outset, and I was fully aware it could fail for any of a number of reasons. Right now though it's still "not failed" as far as I'm concerned, and my curiosity is piqued in terms of at least trying to figure out what's happening.

 

[Sky-Knight]

Bug Check 0x133 DPC_WATCHDOG_VIOLATION - Windows drivers

The DPC_WATCHDOG_VIOLATION bug check has a value of 0x00000133.

learn.microsoft.com

DPC_WATCHDOG_VIOLATION

This error happens when the OS detects hardware not responding to commands within a reasonable amount of time.

Namely, Windows told your mainboard to reboot or shutdown, and it just straight didn't. Which is typically caused by a BIOS/EFI interface issue.

This is further evidence your CPU incompatibility with Windows is directly the cause of this fault. The only hope you have of resolution is a BIOS update, which I assume you're already running the most recent available and therefore you're SOL on a fix.

For the 3rd time, your experiment is at an end.

 

[Fred Claus]

I really have no intention of snipe hunting over the long term.

It is now happening every single time do a Restart. When it comes to a Shutdown (and I don't have Fast Startup enabled) one of two things happens:

1. Everything looks ok but after the screen goes black (when it normally would) it's taking quite a while afterward before the machine actually powers down.
2. I get a BSOD during shutdown like I do with a Restart.

Neither of these were always the case. Startup is slower, too. I've already used CrystalDiskInfo along with Crucual Storage Executive to look at the SSD and both report good health.

I occasionally have AMD's Radeon Software come up at reboot after a BSOD saying that a BSOD was detected, and there is an indication in BlueScreen View that this is the occasional cause, but here's a screenshot from that program:
View attachment 14558
You'll notice that there are several in succession between 6:30 and 7:10 PM today, and the first three of those were during restarts done while applying 2023-04 Cumulative Update Preview for Windows 11 Version 22H2 for x64-based Systems (KB5025305). The last one was a test Shutdown that triggered a BSOD, and that was after one that did not, but was slow.

This is all a curiosity quest. If things ever get ugly during day to day use of the computer, I'll immediately roll back to Windows 10 via the system image I took. But I'm in the humor do play with this quite a bit more before I'd take that step.

Again, this has been an experiment from the outset, and I was fully aware it could fail for any of a number of reasons. Right now though it's still "not failed" as far as I'm concerned, and my curiosity is piqued in terms of at least trying to figure out what's happening.

Have you tried doing a startup repair or maybe uninstalling an update? I know on a lot of HP machines if you let it boot to the logo screen and then hold the power button to turn it off, if you do that three times in a row it triggers the repair function.

 

[nlinecomputers]

@britechguy what is the hardware on this? Mobo or System Make and model. Aftermarket Video card make and model? Windows 11 build number.

 

[britechguy]

@nlinecomputers

HP 15-ba011cy laptop

Here's the beginning of a Speccy report from the last portable version of Speccy:
Operating System
Windows 11 Pro 64-bit
CPU
AMD A12-9600P
Bristol Ridge 28nm Technology
RAM
11.0GB
Motherboard
HP 81F9 (Socket FP4)
%1 Chipset
Graphics
Generic PnP Monitor (1366x768@60Hz)
1024MB ATI AMD Radeon R7 Graphics (HP) 50 °C
Storage
931GB Crucial CT1000BX500SSD1 (SATA (SSD)) 25 °C
Optical Drives
hp DVDRW GUD1N
Audio
Realtek High Definition Audio
Operating System
Windows 11 Pro 64-bit
Computer type: Virtual
Installation Date: 1/5/2023 11:14:55 PM
Serial Number: Redacted
Windows Security Center
User Account Control (UAC) Enabled
Notify level 2 - Default
Firewall Enabled

From Intel Support Assistant:

HP Notebook​

BIOS
Version
F.37
Date
6/22/2020
MOTHERBOARD
Manufacturer
HP
Model
81F9
Version
67.43
OPERATING SYSTEM
Edition
Microsoft Windows 11 Pro (64-bit)
Version (Build)
22H2 (10.0.22621)

Devices and Drivers​

PROCESSOR

AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G​

GRAPHICS

Freedom Scientific Accessibility Display Driver​

AMD Radeon R7 Graphics​

AUDIO

AMD High Definition Audio Device​

Realtek High Definition Audio​

NETWORKING AND I/O

Realtek PCIe FE Family Controller​

Intel® Dual Band Wireless-AC 3165​

Intel® Wireless Bluetooth®​

MEMORY

11 GB (actually 12GB installed)​

STORAGE

CT1000BX500SSD1​

-------------------------
There had been times in the past when Freedom Scientific's Accessibility Display Driver was known to cause problems, but I haven't heard of that recently. One thing I will do is to uninstall their accessibility software (as I need to update anyway) to see if that makes a difference.

 

[Philippe]

CrystalDiskInfo

1) I've found it not precise enough. Try this: https://gsmartcontrol.shaduri.dev/

2) Does it crash in safe mode?

 

[nlinecomputers]

Also any clues in the Event logs. Often you'll see stuff crashing before the actual BSOD happens.

 

[Markverhyden]

From the dump above everything starting with 4/15 was ntoskernel. I'd roll back updates to 4/14 then test.