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.
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.
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
- Short Drive Self Test
- Short generic
- Long generic
If the short generic fails, no need for the long generic.
NoteDo not run SeaTools on an SSD as the results will be invalid.
Disk Check - Windows 7 Help Forums
- 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
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.
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?
Not necessarily because of the bad sectors, but also because of the other results.It seems like it's time to buy a new hard drive, right?
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.
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!
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.
Quote