Solved Computer freezes/recovers or freezes/crashes ~once per day

[coffent]

For the past few weeks, about 1/2 hour after booting my computer up in the morning, whatever program I'm using at the moment will stop responding. If I continue to try to get it to respond, its screen will dim and I get the message "Not responding". The disk activity light goes on 100%. To a certain extent I can still get to other programs that are already running, but I can't open new ones. Usually, if I just sit and wait, after about 30-60 sec everything will be ok again; other times nothing will happen for several minutes after which I'll get a BSOD with the message "Windows was shut down..." and
Collecting data for crash dump ...
Initializing disk for crash dump ...

Because of this, I've been running Process Explorer. When the problem occurs I can switch to it if it's on the second screen of my dual-screen system. When I do so, almost everything seems normal:
CPU 1.5%
System Commit 3.46 GB
Physical Memory 3.0 GB
I/0 2 kB
Network 400 B
Disk 0 kB
The abnormal indication is that the disk shows 0 kB even though the disk activity indicator is on 100% of the time. The list of processes shows Avast (anti-virus program) and System to have overwhelmingly the largest I/O Read Bytes, but this doesn't seem abnormal.

I use the program WhoCrashed to check dump files. Some time ago I used it to cause a deliberate crash to check that dump files were being written. They are. However when I check crash dump files after the BSOD there is nothing new in them (WhoCrashed shows only the results of the test crash.)

Usually, but not always, after the first 30-60 sec freeze and/or crash, the computer seems to be ok for the rest of the day.

Any ideas as to what is causing this or how I can check further?

PLEASE NOTE: I downloaded and ran the DM Log Collector. When I did so, I got a brief notice saying something to the effect of "Action not completed. Access is denied." However it did create a zip file on the desktop. But when I try to upload it I get the message "You don't have permission to open this file." (I'm running as Administrator.) What's wrong?

 

[axe0]

You're the only user of the system I assume?

 

[coffent]

Yes, that's right.

 

[axe0]

Please follow below instructions to manually collect some data of a few files.
If there are any problems please let me know, I've written the instructions for another user at Bsod 0xD1 - Windows 10 Forums but I'm not 100% sure if everything works the same for Windows 7.

Please search for "msinfo32" (without quotes) and open the msinfo32 app,

• save it as msinfo32.nfo,
• in explorer go to the directory where it is saved,
• right click the msinfo32.nfo file,
• choose 'send to' or 'copy to',
• choose 'compressed (zipped) folder'

Please run following commands in an admin command prompt, it creates a file called 'systeminfo.txt', it is created with the DM Log Collector and shows some information about your system too but we'll have to do it manually now.

systeminfo > "%USERPROFILE%\Desktop\systeminfo.tmp"findstr /v "Owner." "%USERPROFILE%\Desktop\systeminfo.tmp" > "%USERPROFILE%\Desktop\systeminfo.txt"
del "%USERPROFILE%\Desktop\systeminfo.tmp"

Please search "dxdiag" (without quotes), you'll see a pop-up within a few moments.
In this popup you see the DirectX Diagnostic Tool, click on 'Save All Information' and save it as 'dxdiag.txt'

Please go in Windows Explorer to following location for the gathering of the minidumps: %systemroot%\minidump
Select all dumps from the last week, right click 1 of them and choose > send to > compressed (zipped) folder naming it as minidumps.

Now that we have a few files, please upload them all, you may put them all together in 1 zip file if you'd like
You can put them in a zip file by moving them in the same place, select the files > right click 1 of them and choose > send to > compressed (zipped) folder.

To sum up there are a few files gathered
1. msinfo file
2. systeminfo.txt file
3. dxdiag file
4. minidumps

 

[coffent]

I've attached the msinfo32.nfo file.
When I ran the DM Log Collector code you supplied I got the error message "ERROR: Invalid argument/option - 'findstr'.", so instead I just ran 'systeminfo > "%USERPROFILE%\Desktop\systeminfo.tmp" ' and have attached the file created.
I ran the DirectX diagnostic in both the 32-bit and (FWIW) the 64-bit versions and have attached both files.
There is only one minidump file, created when I deliberately crashed the system using WhoCrashed on March 24. FWIW, I've attached that as well.

Thanks for the help!

 

[coffent]

FYI, actually the first error message I got was "ERROR: Invalid argument/option - '/v'."

 

[axe0]

Thank you for the data, unfortunately the uploaded file 'systeminfo.tmp' is a temporary file what is useless for me as I have no idea what to do with temp files.
Please run following code below in an admin command prompt to generate the right file, that should work for Windows 7.

systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"

 

[coffent]

Actually, the tmp file *is* a text file, just with a different extension. Nevertheless I ran the code you supplied and have attached the txt file generated.
Thanks again!

 

[axe0]

I've just re-read your OP, do you remember what the bugcheck(s) is/are?

Could you run this command too in command prompt and upload the eventlog.txt created on the desktop please.

wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"

 

[coffent]

I tried to upload eventlog.txt, but its 18-MB size exceeds the 1-MB limit. I also tried zipping it, but strangely got an "Access is denied" message even though I can open it, move it to another folder, etc. The file lists events back to 12/19/15, so I could send you just the last 1-MB of it.

OP = original post? Not sure what you mean regarding the bugcheck(s).

BTW, since the problem occurs on most days, if there's a monitor that I can run that would help just let me know. As I mentioned, most times the system recovers after 30-45 sec, but I *think* I can force the system to crash by trying to switch to other windows during this time.

 

[axe0]

In the case of a size limit problem, upload it to a 3rd party uploader and post a shared link in your next reply.

Yes & bugcheck = the stopcode on the BSOD screen, like 0x7A, 0x124, 0x3B, 0x133, 0x101, etc., or as you would see it on the screen: 0x0000007A, 0x00000124, 0x0000003B, 0x00000133, 0x00000101, etc.

 

[coffent]

Here's a link to eventlog.txt: https://app.box.com/s/fpy8e781wuf59qj1en6cjm4u399wgodq

Unfortunately I don't remember the bug codes, if they were displayed at all. In one case that I recorded, after pressing ctrl/alt/del to try to bring up Task Manager, I got the message "The logon process was unable to display security and logon options when c/a/d was pressed. If the operating system does not respond, press ESC or restart the cptr by using the power switch." When I pressed ESC I got a BSOD. Other times (as I mentioned) both screens will go completely black except for the cursor, which I can move but can't do anything with.

 

[axe0]

The only BSOD that has been logged is the manual forced BSOD.
Try below tests.

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

1. Short Drive Self Test
2. Short generic
3. Long generic

If the short generic fails, no need for the long generic.

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk
Disk Check - Windows 7 Help Forums

Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

 

[coffent]

I haven't finished all the tests but here's an update:
On the boot (C drive, SeaTools stalled at 28% through. (It didn't indicate "failed", but it just wouldn't go any further, even with two tries and several hours.)
HD Tune found two sequential errors at locations that are 27% of the way through the 1.5 GB drive, so I expect SeaTools and HD Tune are finding the same problem.
I ran chkdsk some time ago after the problem first started occurring, but it didn't find anything wrong then. I can run it again.
Similarly, I ran Memtest86 at about the same time, and it found nothing wrong (though I think I ran it for only two passes, not eight).
It seems like it's time to buy a new hard drive, right?

 

[axe0]

It seems like it's time to buy a new hard drive, right?

Not necessarily because of the bad sectors, but also because of the other results.

 

[coffent]

I just now ran the HD Tune program twice more over the 400-410 GB area where the error was found before, and now everything seems fine.

 

[coffent]

I didn't see your last post, but it does seem like a new HD is in order. I hope that is the source of the problem. I'll let you know when I put in the new drive if the issue goes away. In the meantime, thanks very much for your help!

 

[axe0]

You're welcome

Keep me posted on the situation.

 

[coffent]

Shortly after your last note my computer crashed completely - after getting through the BIOS load it posted a line of gibberish, and that was that. Fortunately I'd backed everything up. I purchased a new hard drive, installed my backups on it, and I now seem to be back in business. I haven't had the problem I wrote about with the new drive, so it definitely looks like the old drive was the culprit. Thanks again for the help.

 

[axe0]

I'm glad that your problem is solved

You're most welcome.