Getting my Butt Kicked by BSODs on the Daily

Mike-EEE · Oct 25, 2019

Yeah?

Sysnative Windows Update · Oct 25, 2019

Please still go through with it. Maybe there is a service interfering.... (MS or not MS).

Mike-EEE · Oct 25, 2019

Ah correct... there's the Services tab. If one of these were responsible for the issue, wouldn't they show up in the BSOD/memory dumps? I thought that was the whole reason for those reports, it shows which dlls/services were involved at the time of the crash.

Sysnative Windows Update · Oct 25, 2019

Yes, generally, but in this case, I want to double-check that 2+2=4. That is, that some internal MS service isn't causing a conflict with Hyper-V (this really shouldn't be the case, but you know...)

Mike-EEE · Oct 25, 2019

Tricky part about that is that obviously there are several Hyper-V services, and I am not entirely sure about the services that they depend on... it could possibly introduce further volatility if a dependency is missing, or a crash occurs due to another condition introduced by disabling a swath of dependencies.

My feeling is that if one of these were responsible we would know about it in the crash reports. My other feeling is that since we are basically to point of disabling services that were installed with a default, untouched installation of the latest released software product, that we really do not have a confident/plausible explanation for what ails my machine, except save that 1903 is a very bad monster.

Sysnative Windows Update · Oct 25, 2019

Yes, I see. Is there a chance you could back the current configuration up in order not to lose anything or cause any inadvertent damage? This is why I was more leaning towards hardware rather than software, but since you were more willing to explore software, I went the software route. Unfortunately, when it comes to BSOD troubleshooting, it oftentimes comes down to eliminating stuff one by one until we are left with the answer.

My reasoning being, once we have the users reinstall their OS and start fresh, we have essentially eliminated all possibilities of file corruption and/or driver conflict, which would leave hardware as the cause.

Another thing you can try is the following, although I suspect it will come up okay since this is a clean installation:

SFC Scan

Click on the Start button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator
When command prompt opens, copy and paste the following commands into it, press enter after each

sfc /scannow

Wait for this to finish before you continue

copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Mike-EEE · Oct 25, 2019

Yeah, very appreciative of your suggestions and way of thinking here, as well as you taking the time to explain it to me. Again if I could somehow install 1809 again it would answer a lot of questions. What I would really like is to have a Hyper-V resource or someone who works in the Hyper-V group to help out with this, but alas all my posts to Hyper-V-related resources have fallen flat.

In any case, I have attached the requested file.

Sysnative Windows Update · Oct 25, 2019

You could install 1809 if you have the iso saved somewhere, but that would require a clean installation.

Mike-EEE · Oct 25, 2019

Heh, if only.

BTW/FWIW:

https://twitter.com/x/status/1187777192815665157

Mike-EEE · Oct 25, 2019

Also something of note: I had a bunch of cumulative updates hit my host machine today, including an optional one which took forever. I've installed them all. Let's see how it do.

Sysnative Windows Update · Oct 25, 2019

Keep me posted.

Mike-EEE · Oct 25, 2019

Yeah, unfortunately, I hit another BSOD.

It doesn't take much. I left the machine for 15 minutes and returned to the Login Screen of Doom. Funny thing is that it can take 15 minutes or it can take 9 hours... as long as it's idle, it's susceptible.

However, the good news is that I did manage to score me an 1809 image from a secret angel hero so I will be installing that and hold down the fort until 1903 arrives.

I gotta say that it will truly suck if the BSODs continue back in 1809.

Anyways, I will keep this thread apprised.

Sysnative Windows Update · Oct 25, 2019

That's unfortunate. Please do attempt to reinstall 1809 (as long as it's a legitimate copy) and see if the BSODs stop.

Mike-EEE · Oct 31, 2019

Welp... 5 days in and zero BSODs. Pretty confident this is an issue now in 1903 and am praying that it is fixed in 1909.

MichaelB · Oct 31, 2019

heard of others too, but not from Intel Platform.....as my machines are running it might be a glitch on AMD again.....

Mike-EEE · Oct 31, 2019

FWIW I have created a Feedback Hub issue here:
https://aka.ms/AA6ekem

I would greatly appreciate any upvotes/comments you can provide to help escalate/promote awareness around this issue.

Sysnative Windows Update · Oct 31, 2019

Are you still crashing?

Mike-EEE · Oct 31, 2019

softwaremaniac said:
Are you still crashing?

Ah, sounds like you missed my previous post:
Getting my Butt Kicked by BSODs on the Daily

It's been working great since reinstalling 1809. Zero BSODs since, and I have used it exhaustively, four guest machines utilizing over 32GB of RAM:

So, happy now... but who knows what 1909 will bring. If/when I make the jump I will update this thread with progress.

BTW, I am hoping that 1909 will eventually be available to me, and I won't have to install 1903 first.

Sysnative Windows Update · Nov 2, 2019

Great!

And yes, you can jump straight to 1909 when it releases.

jcgriff2 · Nov 3, 2019

Hi. . .

Mike-EEE said:
Ah, as in keyboard and such? Did I provide the requested information/.zip file correctly? I was under the impression it provided all the goods... please let me know if there is something I messed up in the process. Newb here. :)

You provided the info correctly, but there is no report that tells us what devices are connected to the system, which is why softwaremaniac asked.

Mike-EEE said:
The [Sysnative] app is awesome, btw... nice work with that. Assuming you just didn't rootkit my machine and have turned it into a mining rig for your new crypto sale.

No.. it is batch and VBS code wrapped up in a digitally signed EXE file that I wrote [most of it] back in 2008 and it primarily runs Windows executables like msinfo32, dxdiag, systeminfo, Windows Management Instrumentation (WMI), etc... It does not get installed or install anything; no registry entries are made; just the Sysnative folder in Documents is created, which you can delete at any time.

Mike-EEE said:
the problem being relayed by the BSOD is a SYNTHETIC_WATCHDOG_TIMEOUT which is related to Hyper-V/Hypervisor.

That is what the one dump seems to tell us with bugcheck 0x1ca, which I have never encountered before.

Bug Check 0x1CA SYNTHETIC_WATCHDOG_TIMEOUT - Windows drivers

It is important to keep in mind that this bugcheck DOES NOT mean with 100% certainty that the hypervisor is at fault.

The Sysnative app executed on 24 October 2019.

Code:

Original Install Date:     10/21/2019, 9:58:40 AM
System Boot Time:          10/24/2019, 4:35:32 PM

So, at the time that the Sysnative app was run, Windows 10 installation was just 3 days old.

Sorry if I missed it in one of your posts, but have you reinstalled the latest version of Windows 10 trying to fix these BSODs?

It's just that if you installed the latest version of Windows 10, then left for 10 days, I would expect the "Original Install Date" to be at least 10 days prior to the start date of this thread (24 October 2019).

How many times have you reinstalled the latest version of Windows 10, assuming that you have?

Since the bugcheck mentions a hung processor, I'd like you to run Prime95 CPU test - CPU STRESS testing: Mersenne.org Prime95 and Intel Processor Diagnostic Tool (IPDT)

Also run the AMD System Monitor - https://www.amd.com/en/support/kb/faq/gpu-100

I agree with softwaremaniac - we're more than likely looking for unknown hardware failure here.

How often does the system BSOD? There was only a single dump (1) in the Sysnative zip file that I downloaded.

I do not know much about Hyper-V. Can you turn it off and test your system?

I'd like for you to run Driver Verifier with Hyper-V on and your 4 VMs running - Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista

Then turn Hyper-V off and run Driver Verifier.

Driver Verifier must run in the background for at least 24 hours. You can use the system while it is running.

It's job is to check 3rd party kernel-mode and graphics drivers and if a violation is found, to force a BSOD on your system. If this happens, please get the dump (\windows\minidump); copy it to Documents; zip it up and attach to your post.

While suspect, I know, it is possible that unknown hardware failure occurred on or around the same time that the newest version of Windows 10 was installed. Stranger things have happened.

Regards. . .

jcgriff2

EDIT: I just read that you reverted to prior W10 version, so please ignore the testing requested in my post.

Getting my Butt Kicked by BSODs on the Daily

Member

Inactive

Member

Inactive

Member

Inactive

Member

Attachments

Inactive

Member

Member

Inactive

Member

Inactive

Member

Sysnative Staff, BSOD Kernel Dump Senior Analyst

Member

Inactive

Member

Inactive

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)