Jump to content

Windows 10 - event viewer and task manager - not responding

Hi. I have an Windows 10 Pro. Task manager and event viewer not responding. I am clicking and nothing happening. Is this related to hardware or software?  My disk is Samsung Evo 250 GB , and 2x8gb Kingston Hyperx 1600mhz.

 

 

Smart on disk is fine, GOOD statues in Samsung MAgician and no errors in HD TUNE. Memtest86 not showing errors.

Link to post
Share on other sites

It should be working. You have something playing games on you. A piss poor coded software that screwed up Windows, a tweak tool you are using or used in the past, horrible driver setup that screwed up Windows by replacing files...

 

If you have a spare HDD/SSD that you don't use and ready to be formatted, try plugging it as your main drive, install Windows 10, and do nothing. Don't install anything else. Not even Chrome/Firefox. NOTHING. And see if your task manager works now. If it does, it should eliminate hardware problem. Then let Windows Update do its things, restart the computer, and see if everything continues to work. If so, then that eliminates Windows 10 not liking your system.

 

The reason why I suggest a different HDD/SSD, is because I don't want you to loose your stuff. And if everything works wonders with your old HDD/SSD, and you when you have time, you replicate the same thing with your real drive (of course backup your stuff before), and now you have again problems of some kind (the same or something else is broken), then it could be your SSD is faulty, and no software can detect the fault.

 

Oh, something else to try, change the SATA cable of your drive. I doubt it, but it doesn't hurt trying. You should have extras from your motherboard.

Link to post
Share on other sites

Yes i am after format with GPT this time , not MBR.

 

And all is working fine and opening without problems.

 

So i guess MBR was broken? Is this related to hardware if mbr get broken? I read that somewhere:

OS on a GPT formatted disk, booted with UEFI, is BETTER THEN MBR & BIOS !
Why ?

  •  
  • Better (auto) chances to recover info from bad/damaged sector/block !
    (Partition table is redundantly stored, checked using CRC)
Link to post
Share on other sites

The MBR could have been poorly made thee first time, that is a possibility. It could also be that your UEFI which used to be set as BIOS emulation (for legacy OS, like Windows 7 and older, and legacy hardware that doesn't support UEFI) was iffy, and things screwed up when Windows detected that you had BIOS (because UEFI was emulating it), and made the MBR, and things screwed up.

 

So there is that. But yes, your SSD could be faulty and now error correction of GPT is hiding the issue. But I don't know if you tried a re-install before still with MBR, to know if the problem is the same. Usually, chances that the same data is at the exact same location (if we ignore the boot stuff), is rare. If you have not tried that or the problem is at different place, then it could be the SATA cable is faulty is miss connected, and the additional data of GPT for the error correction part helps solve that problem.

Link to post
Share on other sites

like I said, it could be that simply MBR was not well done the first time, due to some kind of issue, that caused a problem in some areas. So the drive is fine and all, but MBR had an issue. It is rare, but possible.

Link to post
Share on other sites

Last time if i can ask dear friend. You said: "But yes, your SSD could be faulty and now error correction of GPT is hiding the issue. But I don't know if you tried a re-install before still with MBR, to know if the problem is the same. Usually, chances that the same data is at the exact same location (if we ignore the boot stuff), is rare. If you have not tried that or the problem is at different place, then it could be the SATA cable is faulty is miss connected, and the additional data of GPT for the error correction part helps solve that problem."

 

But even if actually on GPT is fine and no problems still can i have faulty ssd? But like i said , SMART reports are 100% GOOD from CrystalDiskInfo and Samsung Magician. In Hd Tune no errors. 

Link to post
Share on other sites

GoodBytes last question. I will be very greatful for answer. 

You said:" The MBR could have been poorly made thee first time, that is a possibility. It could also be that your UEFI which used to be set as BIOS emulation (for legacy OS, like Windows 7 and older, and legacy hardware that doesn't support UEFI) was iffy, and things screwed up when Windows detected that you had BIOS (because UEFI was emulating it), and made the MBR, and things screwed up. "

 

So it was caused by software/bios or hardware?

Link to post
Share on other sites

So propably it was caused by software?

 

I mean about this like you said:" The MBR could have been poorly made thee first time, that is a possibility. It could also be that your UEFI which used to be set as BIOS emulation (for legacy OS, like Windows 7 and older, and legacy hardware that doesn't support UEFI) was iffy, and things screwed up when Windows detected that you had BIOS (because UEFI was emulating it), and made the MBR, and things screwed up. " "

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×