Windows 10: Memory

I don't know if this is the right place for this, but I don't think it should be in the BSOD group.

All of my HPs are giving me memory errors when I shut down Build 10130. The error is: 0x00007FF94A95CC60 for this desktop and 0x00007FFDBDB6CC60 for my 15.6" laptop. Last night, when I shut down the desktop, I was given a different number with the 0x0000 and CC60 being unchanged while the 7FF04A95 had changed.

I don't seem to be having any problems, but it's rather jarring when I get that error and it won't go away until I click OK.

:)

 

Connecting to wifi

My laptop did an automatic update today and now I can't connect to my wifi. I just got this laptop a few days ago, and am still learning it, so I have no idea where to look or how to fix it.

 

Microsoft Securty Essentials on windows 10

manually yank out? sigh!

 

In order to avoid this annoying bug, use the context menu of the Start Button (the same way you would do it on Windows 8.1) when you need to shut down, log out or restart your computers.

Tell us if, by doing this, the problem disappears.

Cheers!

 

That's how I shut down. Click on Start>Power>Shutdown

 

I think everyone has the same issue because I do have it too. I just ignore it. It doesn't affect the performance anyway.

 

No, but you have to click with the right button of your mouse. You'll then see a contextual menu and one of the groups at the bottom of the list will give you the different options available in your system: sleep, log out, shut down, restart, etc.

This is how I and some more people are avoiding this. You may still see some messages stating that a certain process is preventing the system to shutdown. Just wait a couple of seconds and they should be cleared eventually.

Cheers!

 

Same here, Robot, so I'm marking it solved. There's another more active thread on the same thing, so we don't need this one. *Smile

 

I thought you are talking about your own memory here. *Biggrin

 

OK, I'll try that one. Same number of clicks. *Smile And just as easy. Or, maybe I'll just try the power button. At any rate, there's another thread on this issue, so I'm marking this one solved. This is a Microsoft issue.

 

Yes this is a bug, I can tell you that it affects at least builds 10130, 10134 and 10135.