Windows 10: Black screen every Thursday, PC quit sleeping this past week.

OK, let me try that. As things are now, if I force it into sleep, it finally shuts down and then comes right back awake again. This has been happening the whole time since the July OS upgrade. Nothing seems to explain it.

Here, I just ran these after forcing sleep and it came back awake right away, even though I'd disabled wake timers:

 

Well that is progress. Search [Driver] Legacy Kernel Caller yields lots of hits. Haven't had a chance to review second screen pront but I do remember it.

Ken

 

Ok, now this is getting interesting! Never heard of this Event Viewer before! Exciting! *Smile


















OK, now I'm recalling this. The root hub was identified awhile back, but I pulled any USB extension hubs out, and the only thing left was the onboard chipset itself, which threw me into having to deal with chipset stuff that may be end of life and not have a fix for, now that the OS has gone to Windows 10. ( or at least over my head, and I'd have to risk everything on this PC to try to update chip sets or whatever - I think we talked about that before ).

 

Could I ask, when you put your device to sleep is it possible to remove all unnecessary USB devices. Wireless dongle, keyboard, printer, label printer etc. Then send to sleep with mouse and unplug mouse.

Not getting any hits on that USB Root Hub. I will look at the other Legacy Kernel Caller. Likely they are some how related.

Way back you were going to install the latest chipset that Intel had discovered, did you. (Create restore point.) Did you buy a new wireless dongle?

Thanks for screen shots. Lets try no USB devices. May be even use a different mouse from another system for experiment

One last caution. As we don't know what caused you video to correct more messing around may just bring it back. Your call as to pursuing.

 

I suppose I could. Would be a big mess. The first question becomes, if it was all doing fine and sleeping under Win 7, why not with Windows 10?

Chipset? Hardware chipset? No.

I need to learn how to do that.

Not yet. I have one picked out. They arent expensive. Just haven't had time. I still haven't even had time to set up my solstice present leg stretcher for my martial arts leg stretching.

Whew. Ok, but will take a few days for me to get time to deal with all that.

Yeah, wish I knew on that one...

 

Well you are not going to want to hear this. Windows 10 doesn't like at least one of your old drivers.

Okay I think we are chasing ghosts. You install the chipset drivers and tell us when its done.

To create a restore point, Windows + R, type sysdm.cpl, click on system protection tab, ensure restore points are enabled, click on create near bottom. Give it a name. Do this before chipset.

Okay, since thread started in December 2016 a couple more weeks is cool.

Ken

 

Ok, I just got motivated here, and ordered one of these on Amazon, which is very highly rated over some 800 reviews:

OURLINK 600Mbps mini 802.11ac Dual Band 2.4G/5G Wireless Network Adapter USB Wi-Fi Dongle Adapter with 2dBi Antenna Support Windows XP,Win Vista,Win 7,Win 8.1, Win 10,Mac OS X 10.6-10.12

 

OK, I just had a BSOD after trying to play an MP4 video. It gave the stupid smiley BSOD and said to refer to "Thread stuck in device driver".

Here's a whole screen shot of a cluster....er...mess, around what happened. If you could suggest what to probe in depth into? MBAM is Malware Bytes, by the way.

 

Can you screen print the Event 1001 say 20 lines above, with the words bug check.

Both tabs. Thanks. You should now have a new dump.

 

Not sure what you mean "both tabs".

 

You gave us the General tab, beside it is the details tab. Just like you did in posting 61 of this thread.

 

Ah, got it. I didn't even know what I was doing. LOL

 

Sorry. Most of info is hidden. Please double click on bug check. Most of info is cut off.

It might be easier if you used one of the tools I mentioned like nirsoft's bluescreen view.


Ken

 

Here's the XML view, which I think is all there is?

 

Jeez, here we go again. It looks like it fritzes for awhile, before finally crashing. This Event Viewer is apparently a valuable too, if I knew what I was seeing and how to fix this mess.