BSODs after waking from sleep

Nova Prime · 24 May 2015

My self-built PC gives me BSODs immediately or soon after waking from sleep, but not regularly. It can happen twice in a week and then not happen for maybe two months, but it does keep happening. I use it every day and put it to sleep every night and occasionally during the day. I generally don't shut it down or reboot it unless I have a specific reason to.

Today after it happened again it took a lot longer to boot than normal, with the green/blue ring spinning in the middle of the screen for ages before it took me to the desktop. Then shortly after that, before I'd opened anything, it bluescreened again (not a usual occurence), then took an unusual amount of time to start up this time too, but is working.

I ran memtest when I first got it so I don't think bad RAM is the problem.

Help please!

Arc · 25 May 2015

Uninstall Virtual Clone Drive.

Update Realtek network driver from Realtek

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept then restart.

Report us for any further BSOD after doing these three.
____________________________________________________

Code:

BugCheck 1E, {ffffffffc0000005, fffff88007c3efa0, 0, 0}

Probably caused by : HTTP.sys ( HTTP!UlDisconnectEvent+d4 )

Followup: MachineOwner
---------

Code:

BugCheck 50, {fffff8a1152d0f60, 1, fffff880012cce27, 5}


Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonClose+1e7 )

Followup: MachineOwner
---------

Nova Prime · 01 Jun 2015

Okay, I updated that driver and uninstalled Virtual Clonedrive. I also removed several (but not all) startup items. I've still had bluescreens though. Here's my new file.

Arc · 02 Jun 2015

Why not all? They are not needed to be there, but they can cause problems by staying there.

Anyway, this BSOD is caused by Logitech driver.

Code:

BugCheck D1, {0, 2, 8, 0}

*** WARNING: Unable to verify timestamp for LHidFilt.Sys
*** ERROR: Module load completed but symbols could not be loaded for LHidFilt.Sys
Probably caused by : LHidFilt.Sys ( LHidFilt+e555 )

Followup: MachineOwner
---------

Search for any possible driver update for your mouse. Support and Downloads

Nova Prime · 02 Jun 2015

The software I've let start up is video driver software, Xbox controller software, Sticky Notes, MS Security Client, Logitech SetPoint, and Ditto (which just monitors my clipboard).

The driver (only for XP, which you linked) for my Logitech mouse is over a decade old, but I'm running the current version of SetPoint which correctly detects and works with my mouse. Should I uninstall it and reinstall it? Is that likely to change anything?

Arc · 02 Jun 2015

If you dont install SetPoint, does the mouse work, as a simple USB mouse? If it works (a USB device should), then dont use SetPoint.

In Startup, Sticky notes and MSE will be enough.

Nova Prime · 02 Jun 2015

It works, but it's a lot nicer to use with SetPoint. It feels better and I'm able to use all its buttons.

Arc · 02 Jun 2015

As you said, the mouse is over a decade old. It does not have the required drivers for the operating system. In this case, SetPoint is causing the BSODs.

Keeping everything in mind, take your decision.

If you are ready to neglect the BSODs, continue using SetPoint.