Two Crashes, Repaired, Crash

Winver 22H2 (OS Build 22631.3085)

Yesterday morning, computer greeted me by saying it had crashed. I restarted it with no problems, so spent some time computing. When I came back, computer had crashed again, so I ran sfc /scannow and DISM repairs; both programs reported having found and fixed difficulties.

I computed off and on for the rest of the day, but was again greeted this morning by another crash notification. I promptly reran yesterday's problem seekers, neither of which having found any discrepancies. All has been well for some four hours.

What ought I to do to find anything that neither sfc nor DISM found this morn?

To get better help with your Windows BSOD issue, please read these instructions and follow the steps below.

Click to expand...

Find out why you got a Blue Screen of Death (BSOD) error and how to stop it.

FreeBooter said:

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

Find out why you got a Blue Screen of Death (BSOD) error and how to stop it.

Click to expand...

Thanks for your quick reply. I did not post in the BSOD forum as it has been so very long since I last encountered a crash that I did not even recall what BSOD means, and wondered where I ought to have posted my original message.

Blue Screen of Death (also known as a blue screen or BSoD) is an error screen displayed on a Windows computer system after a fatal system error, also known as a system crash: when the operating system reaches a condition where it can no longer operate safely. BSoDs can be caused by poorly written device drivers or malfunctioning hardware, such as faulty memory, power supply issues, overheating of components, or hardware running beyond its specification limits.

The instructions for downloading the V2 program are themselves wrong, as no zip file is downloaded, just what seems to be what one might see after extracting the files from that which I don't get. Following the instructions to double-click on the shortcut, which for me is inside what I get when I supposedly download the zip, tells me this:

"The term '.\resources\main.ps1' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:2
+ &'.\resources\main.ps1'
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (.\resources\main.ps1:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException"

I don't speak nor read that language, which unlike something such as Middle English ( c. 1150 to c. 1470) at least somewhat comprehensible to me.

The tutorial said that if the V2 program does not work, use the DM Log collector. I clicked on that, which ran and I am posting the resulting "temp" file. However, there is also on the desktop a zipit file which reported this:

Windows Script Host
X
Script:
1 Line:

Char:

Click to expand...

Error:
Code:
C:\Users\jlieb\Desktop\_ziplt.vbs
2
1
Subscript out of range
800A0009
Source: Microsoft VBScript runtime error
OK

Here is what is in "temp":

I had no problem downloading the V2 script zip archive from below link and executed without problems.

FreeBooter said:

I had no problem downloading the V2 script zip archive from below link and executed without problems.

https://www.elevenforum.com/attachments/v2-log-collector1-11-zip.34993/

Click to expand...

Not I, who just tried yet again and who got the expected gibberish. Maybe that is a low altitude version that does not work at 7,000 MSL....

Maybe your antivirus software causing the problem.

FreeBooter said:

Maybe your antivirus software causing the problem.

Click to expand...

Malwarebytes

I have no idea, sorry.

FreeBooter said:

I have no idea, sorry.

Click to expand...

I have no ideas, and that is not limited to this subject....

Last report for today, which is that turning Malwarebytes off had no effect on the failure of the V2 installer to work properly.

This morning brought another crash, alas. Sfc /scannow found nothing, DISM did, rather quickly, did not indicate that a log had been created (I am not sure if it does that, although I thought it did after previous uses.)

Should I download and install an ISO, saving everything, or is there something else I should do to try to fix whatever it is that is causing the crashes?

You can yourself take a look at the BSoD crash dump files to find out if anyone is points to device driver causing the problem, it's usually third-party device driver that will cause the problem as long as there is no faulty hardware component.

This guide will walk you through opening, analyzing and making sense of Windows crash dump files.

FreeBooter said:

You can yourself take a look at the BSoD crash dump files to find out if anyone is points to device driver causing the problem, it's usually third-party device driver that will cause the problem as long as there is no faulty hardware component.

This guide will walk you through opening, analyzing and making sense of Windows crash dump files.

Click to expand...

Thank you for taking the time to post the video. I have not had the time to reply, having many other things to interrupt my life such as stacking a delivery of well over a cord of firewood. I have watched it twice, and am uncertain how to run the program, as the speaker goes rather fast, and his accent is somewhat difficult to understand. Do you know of any other instructions for running the program?

Yesterday morning, I again found that the computer had crashed sometime during the night. Strangely, at least to me, neither sfc /scannow nor DISM found any problems. That being so, I did my usual morning run-through on the computer, then left for three or four hours. When I returned home, I found not a BSOD but a computer that had restarted.

I logged on, and while reading the accumulation of emails, I was suddenly confronted with a totally black screen. Having no idea, of course, what to do, I waited to see if that would change. After maybe fifteen seconds (I did not bother to start counting "One thousand one, on thousand two", etc., as I was sitting there suddenly I was back reading emails.

When I finished, I saw that I had at least one notification, which was that Dell Support Assist (SA) had found one file to download and install, so I opened SA. which stated that there were no new items to install. I checked the SA history file (or perhaps some other source in SA, I don't remember) which showed the timing and installing of some unnamed update. The timing showed that the installation of the unnamed whatever was right when I was reading email; I concluded that it was that which caused the momentary black screen.

The episode was not similar to any other I have ever seen with SA, but usually when there is a normal set of update files to download and install, when that process is ready to a restart, I will return to SA and see that at least one regular update had downloaded and installed; however, if I happen to look at SA before it was ready to restart, that particular file was sometimes still running. The update yesterday was out of the normal sequence of downloading/installing, and much quicker than any other updates I have seen.

In short, this episode was odd, but at least given all the other oddities of the world, I shall not fret too long about it.

Having realized that I could download a copy of the video and expand it to full size, which neither that nor the link to You Tube would work in the embedded copy in the forum, I did watch it full-size, which did not help. While I was doing that, I suddenly realized that you may have been the creator/narrator. If so, I sincerely hope that you did not take offense by my comment.

I have many strong points, among which tact is not listed..

I am not going to mark this as solved, as it is not; rather, I am abandoning it. When I started, I thought that it might be relatively easy to fix, although that was not based on any knowledge of this type of fault. It turned out to be complex, and no one was offering any more suggestions (that is not complaining, just a fact.)

Given that I have a Dell guarantee which gives me direct access to top-tier assistance, the matter is in Dell's system. I've already had some interesting assistance, and as the problem is not yet solved, that shall continue. Had I understood at first, which I did not nor could have, I would have started with Dell.

So be it, abandoned this shall be.