Blue screen of death - no downloads or changes to computer recently

Here's my opinion, it would be good if you get a new computer. As you hopefully know, Windows 7 is officially not supported anymore so updates to fix problems aren't going to be developed anymore. I'm aware that a move may be a challenging task when you're so used to Windows 7, but in my biased opinion in the long term it is worth it. It would not be smart to attempt to upgrade the operating system without getting a new computer as you would risk experiencing various problems, some consider doing this with old computers because they believe it's cheaper but in my opinion it's not worth the efforts.

Having said that, I noticed there are a few drivers involved in the crashes that I am unable to trace back to a particular installed program or hardware component which can happen for different reasons, but a concern I have is that these drivers cannot be updated or reinstalled anymore. I would normally suggest updating them and see how it goes, but if one of these drivers is contributing to or are causing the crashes, then there's nothing else I can suggest but a removal of whichever program or hardware component it belongs to and hoping that resolves the problem.

Code:

ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: 83d7dd00, Original thread which is the cause of the failure
Arg2: 865b2020, New thread
Arg3: 83d73fd0, Stack address of the original thread
Arg4: 00000000

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

*** WARNING: Unable to verify timestamp for SbFw.sys
*** WARNING: Unable to verify timestamp for pssdklbf.sys
Unable to load image \SystemRoot\system32\DRIVERS\SBFWIM.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SBFWIM.sys
Unable to load image \SystemRoot\system32\DRIVERS\e1y6232.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1y6232.sys

axe0 said:

Here's my opinion, it would be good if you get a new computer. As you hopefully know, Windows 7 is officially not supported anymore so updates to fix problems aren't going to be developed anymore. I'm aware that a move may be a challenging task when you're so used to Windows 7, but in my biased opinion in the long term it is worth it. It would not be smart to attempt to upgrade the operating system without getting a new computer as you would risk experiencing various problems, some consider doing this with old computers because they believe it's cheaper but in my opinion it's not worth the efforts.

Having said that, I noticed there are a few drivers involved in the crashes that I am unable to trace back to a particular installed program or hardware component which can happen for different reasons, but a concern I have is that these drivers cannot be updated or reinstalled anymore. I would normally suggest updating them and see how it goes, but if one of these drivers is contributing to or are causing the crashes, then there's nothing else I can suggest but a removal of whichever program or hardware component it belongs to and hoping that resolves the problem.

Code:

ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: 83d7dd00, Original thread which is the cause of the failure
Arg2: 865b2020, New thread
Arg3: 83d73fd0, Stack address of the original thread
Arg4: 00000000

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

*** WARNING: Unable to verify timestamp for SbFw.sys
*** WARNING: Unable to verify timestamp for pssdklbf.sys
Unable to load image \SystemRoot\system32\DRIVERS\SBFWIM.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SBFWIM.sys
Unable to load image \SystemRoot\system32\DRIVERS\e1y6232.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1y6232.sys

Hello axe0,

Thank You very much for viewing the Dump files etc. and trying to identify which program[s] the Drivers that have caused the BSOD problems on my Computer are associated with.

Obviously if You cannot identify the Programs I certainly would not be able to - I take it that the Code in your message is to show me what you found ?

While this thread has been on the Forum I have been trying to search to see if there were any other methods of investigating Computer / Hard Drive problems and I have recently ran both CheckDisk and SFC /scannow just to see if they produced any results relating to problems that might be relevant to my Computer - also I had read that they carried out repairs if problems were found.

The SFC - System File Checker did produce results that showed there were some Corrupted Files that could not automatically be repaired - I managed to find the CBS.log file where those results were listed and I managed to turn it into a Zip File which I have attached here.

Would You do me a favour and look through that please - I would really appreciate it:

The sections where the Corrupted files are identified are very easy to see on the pages:

The first un-repairable files are at about a third of the way down page 2 - the next few are about half way down page 6 - next few near bottom of page 7 and last few at bottom of page 11.

This is just in case any of the files are related to what you have already seen - if not I hope that these files are either not vital for running the Computer or are not important enough to cause serious problems ?

If I could afford to buy a new Computer I would definitely do so.

I think that I mentioned previously that I am retired on a basic pension so unless my Computer becomes totally useless I cannot afford to buy a new one.

If it does become unusable I would have to get into unwanted debt to buy one because I could not be without one for at least online Grocery shopping / getting my Food and household essentials delivered as I am Housebound with a severe Back problem and problems with both knees.

Thanks again for your help axe0 I really appreciate it.

Chris

The usual options you find online, SFC, chkdsk, and some other options are usually bad options in that they have literally no effect at all for the problems you specifically have.

I do not intend to say that those options are crap by themselves, they are incredibly effective and powerful tools when they are used for the right problems. This BSOD problem is not a problem where they can be effective, otherwise I would have suggested them.

Those online 'tutorials' are generic and the options are assembled based on what others have reported, but from what I have seen they are complete time wasters and ineffective as they suggest so many useless things. In the end they might suggest something that is a little closer to the actual cause, but for some reason they still mess it up there.

BSOD crashes are almost always caused by third party software, not by Windows itself. SFC checks system files that are protected, as in not even an administrator can fiddle with them. Even if system files scanned by SFC were to be corrupted that are somehow connected to wifi for example (one of the drivers is a network adapter driver), it does not give any indication whatsoever as to what program or hardware component is causing BSOD crashes.