Freeze (crash) after boot or at login screen (only mouse moves)

Hi guys!

So basically this started happening after first upgrading to Win10 some time ago. I then reinstalled Win10 (fresh) for a while and it all seemed ok for a short while. Now more and more often my computer freezes making me have to reboot 2 or 3 times after logging into Windows. Sometimes also freezes on login screen. Usually mouse moves but I cant click or touch anything.

· OS - Windows 10 x64 (fresh install - less then 1 year)

​Speccy information:
http://speccy.piriform.com/results/r...i8df3itK7bIxBa


All help is appreciated!

Hello and welcome to TenForums :)

The errors point to a hard disk problem.

Code:

DISK_HARDWARE_ERROR: There was error with disk hardware
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error.

BugCheck 154, {ffffaf09e8843000, ffff9280e4736ff0, 2, 0}

*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : hardware_disk

Please check your disks using a utility like HDTune. Hopefully this will identify any problems.

Diagnostics Test

 HDD TEST

Run HDTune to

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

It may take some time to perform it properly. Look for any signs of errors and post results.

So I found I had 1 HD giving out way to high temperatures. Will replace this one as soon as I have finished HDTunein another HD. Thios HD seems to have a few errors: Yellow on "Current Pending sector" and blue on "C/ Interface CRC Error Count. Has been scanning it for hours so far found 1 Error at 545956 MB (LBA 1118118336): Does this mean I need to replace this disk too. None of the erronoun disks are boot disks...

Good news that your boot disks are OK. Change one thing at a time so that you can verify improvements and be sure you have cured the BSOD problem. Make backups of everything (if you have not already done so) in case you get a complete failure.

Have a look at the following tutorial that shows how CHKDSK can be used to check and repair errors:
Drive Error Checking in Windows 10

Will do. Now would you characterize this as a BSOD crash? Not 100% I did put this in the right forum. But it definitively is a crash of some kind. Will post as I progress.

The error analysis I did was from several mini-dumps created from your BSOD events. It is quite possible that you have been getting a mixture of freezes and crashes and that not all of them have triggered a BSOD. But the log files showed you had a BSOD on 16th, 28th and 31st March.

Ok thanks alot, and FYI I must have gone blind here. Going through the drives again I find this error on my 180GB Intel SSD boot drive:

(05) Retired Block Count:2

This does not sound too good... Time to get rid of this HD too?

If I should get rid of it, could it still be used for a storage disk for non important data without causing crashes to comp?

Retired block counts indicate that these blocks have been marked so as not to be used, the disk will continue to work fine but if the count starts to rise it indicates that the disk is failing. Keep a check on it but it doesn't sound too bad at the moment.

Still there is a lot of errors in the Eventviewer. This one (and some like it) I have had for a long time:
"The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{6d7958e0-16aa-11e7-bfa1-002683379cfd}#0000000000100000."

There obviously is something wrong here. I just did replace one olde 320gb (remember those?:)) HD, with another old one 500. I have not had any crashes since coming here, but I still think there is stuff wrong. Like driver issues. I reran the DM log collector and added it to this post if there is any changes.

Don't be worried by those event viewer warning messages, I get them too. They seem to occur at bootup. Some people have reported that by changing the way the Windows Driver Foundation service starts from "Manual" to "Automatic" these errors will go away. I've not bothered since it does not seem to be a problem.