Windows 10: Suddenly started getting BSOD every 15 minutes or so

XML down below, it seems to be happening at random, i cant access the dump because it fails everytime i get the BSOD- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">- <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" /> <EventID>41</EventID> <Version>8</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2023

:)

 

Suddenly, BSOD every 15-20 minutes


As the title suggests, my PC has been running fine, up until last night, playing Fallout 4, suddenly BSOD. Today, I turn it back on, and it crashes booting, then crashes over and over every 15-20 minutes, giving me many different types of errors, including page file, security, etc. The crashes don't seem to be related to anything I'm doing, just random.

Log file attached as per instructions. If any additional details are needed, please let me know.

Thanks in advance for any help, this is maddening.

 

Network drivers take a long time (15+ minutes) to install

I'm running Windows 10 Pro 20H1 and I have a problem.

Any network driver that is listed under Network adaptors in Device Manager takes a very long time to get installed. This includes the Cisco AnyConnect Secure Mobility driver, TAP-Windows Adaptor V9, and ... most importantly ... various Hyper-V network drivers,
i.e. Virtual Switch, Virtual Extension, Virtual Adaptor, etc.

Examples:

1. If I grab a copy of tap-windows-9.21.2.exe and run it, the installation takes 15+ minutes, and all this time is spent waiting for Windows to configure the driver class. During this time, tap-windows-9.21.2.exe appears stuck.
   
2. If ask Device Manager's Add Hardware Wizard to install an arbitrary Network Adaptor, even Microsoft Loopback Adaptor, again, the installation takes 15+ minutes, during which the Add Hardware Wizard appears stuck.
3. If Hyper-V Manager attempts to configure a virtual adaptor, switch, extension, etc., again, the installation of the virtual device's driver takes 15+ minutes.

During this 15+ minutes, the driver appears in Device Manager with a yellow icon. The Properties window reads:

Windows is still setting up the class configuration for this device. (Code 56)

Perhaps the most obvious workaround is to suck it up and with the 15+ minutes. Sadly, no. While I might have had the patience to wait 15+ minutes, some apps, like Hyper-V Manager don't. They bail with an error message.

Steps that I have followed to troubleshoot this issue:

• Running various Windows and Microsoft Support troubleshooters
• Resetting the network configuration, both via Setting and via netcfg -d
• Uninstalling all apps that install a network adaptor and starting over from zero
• Updating Windows

 

N97 15 minute call limit?!?

The thing is that before I went to version 20, I have had conversations longer than 15 minutes without a problem. 20 is when this started happening. I just upgraded to 21, but not yet have the opportunity to have 15+ minute discussion. Maybe version
21's listed enhancement of "Improved call reliability" addresses this bug? Grrrr!