Stop the request for a password after hibernation or sleep

That is what it has always been.  After the last update it started to ask for a password.  I have changed some of the timeouts will see how it goes.

One suggestion was to use GPEDIT - not found

Another was to check options not available - not available

In another window was an option to uncheck.  t is immediately above Hard Disk - no option abve hard disk.

Hi JeanPaulK, I am Rob, a volunteer and a 10 time and dual award MVP specializing in Windows troubleshooting and Bluescreen analysis. 
 
If using Fast Startup please turn it off until this issue is resolved. And you may need to leave it off.

Start - type in --> Control Panel  ....... find at top and click on it.

Control Panel - Power Options - Choose what the power buttons do - click "Change settings that are currently unavailable" - then uncheck Fast Startup - click Save Changes - Close - Restart the computer.

3 different Bug_Check usually points to a hardware issue. None of the 3 minidumps had specific cause so that also points to hardware.

This is the first and most revealing:

BugCheck 124, {0, ffff9c87967ed8f8, 0, 0}
Probably caused by : GenuineIntel

Processor report: (Note the FATAL)
===============================================
Common Platform Error Record @ ffff9c87967ed8f8
-------------------------------------------------------------------------------
Record Id     : 01d380736fb634a5
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 12/29/2017 7:05:45 (UTC)
Flags         : 0x00000002 PreviousError

===============================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffff9c87967ed978
Section       @ ffff9c87967eda50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000206c2
Processor ID  : 0x0000000000000000

===============================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffff9c87967ed9c0
Section       @ ffff9c87967edb10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : c2 06 02 00 00 08 20 00 - ff e3 9e 02 ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ ffff9c87967edb10

===============================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffff9c87967eda08
Section       @ ffff9c87967edb90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 0 Bank 5)
Status      : 0xfe00000000800400
Address     : 0x0000380020b913b8
Misc.       : 0x0000000000007fff

----

Could be heat related - try using a small fan to blow into the air intakes to see if that helps. Does it just act like it loses power or does it shutdown in a normal manner? Heat related does not always mean too much heat as it is very possible that something is too sensitive to even normal levels of heat.

Remove ALL power and reseat all cards, memory, and cables (both ends when possible) - actually remove and replace - do not just snug. Remove the dust bunnies and clean the vents. Check that the fans work (before and after opening the case). If a laptop about all you can do is reseat the memory and clean the  vents (still can try adding a small fan as a test).

This sounds like hardware so if the above does not help then you probably need the help of a real computer shop (one that does its own in-shop service) or the System Maker's Support.

1. Check the processor seating, heat sink, and the compound between the processor and the heat sink which are common causes.

=====

2. Check with ASRock Support, their online docs and drivers, and ask in their forums about known issues. Update the BIOS, chipset drivers, and the major onboard and separate device drivers.

BiosVersion = P1.60
BiosReleaseDate = 10/31/2011
BaseBoardManufacturer = ASRock
BaseBoardProduct = X58 Extreme6
BaseBoardVersion =                       
CPUID:        "Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz"
MaxSpeed:     2930
CurrentSpeed: 2946

ASRock - Support
http://www.asrock.com/support/index.asp

ASRock - Forums
http://www.asrock.com/support/forum.asp

ASRock - Downloads
http://www.asrock.com/support/download.asp

2. Run the memory tests (see methods below).

3. As needed use ALL the methods in the troubleshooters below.

4. After ALL the above if needed run Driver Verifier to see if it can indicate a CAUSE (see Driver Verifier methods below).

-----------------------------------------------------------

Troubleshoot blue screen errors <-- read this link
http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors

BCCode: 124   0x00000124

This is usually heat related, defective hardware, memory or even processor though it is  "possible" that it is driver related (rare). Remove ALL power and reseat all cards, memory, and cables (on both ends) - actually remove and replace - do not just snug. Make sure the system has adequate ventilation - add a small fan blowing into intakes. Carefully inspect the motherboard and other cards for damage. Pay attention to the fatal hardware error implication. You may need a real computer shop (one that does its own in-shop service) or the System maker's Support.

Check the processor seating, heat sink, and the compound between the processor and the heat sink which are common causes.

There have been a few instances where Norton/Symantec and other antivirus/security programs have caused this error.

-----

BCCode: 124   0x00000124

The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. 

This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 

BCCode: 124    0x00000124 <-- read this link
http://www.faultwire.com/solutions-fatal_error/The-system-encountered-an-uncorrectable-hardware-error-0x00000124-*1289.html?order=votes

=====

This utility makes it easy to see which versions are loaded : 

Run DriverView - set VIEW to Hide Microsoft drivers - update those without Dump in their names (and update BIOS and chipset drivers).

DriverView - Free - utility displays the list of all device drivers currently loaded on your system. For each driver in the list, additional useful information is displayed: load address of the driver, description, version, product name, company that created the driver, and more.
http://www.nirsoft.net/utils/driverview.html
  
For Drivers check System Maker as fallbacks and Device Maker's which are the most current. Right Click the Start Button - Device Manager - Display Adapter - write down the make and complete model of your video adapter - double click - Driver's tab - write down the version info. Now click UPdate Driver (this may not do anything as MS is far behind certifying drivers) - then Right Click - Uninstall - REBOOT this will refresh the driver stack.

Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard if 3rd party with their own software and drivers and any other major device drivers you have.

Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and then Device Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their latest versions. (Look for BIOS, Chipset, and software updates at System Maker's site while there.)

Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN - REBOOT after each installation.

Always check in Device Manager - Drivers tab to be sure the version you are installing actually shows up. This is because some drivers rollback before the latest is installed (sound drivers particularly do this) so install a driver - reboot - check to be sure it is installed and repeat as needed.

Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER - check manually by model.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm 
   
=====

Memory tests do not catch all errors such as mismatched memory (possible even for sticks that appear to be identical) and when faster memory is placed in the system behind slower memory. So it is best to also swap sticks in and out to check for those even if all memory tests fail to show a problem.

To test RAM check here - let it run 4+ hours or so.  <-- best method
www.memtest.org

MemTestX86 - Test RAM With
http://www.tenforums.com/tutorials/14201-memtest86-test-ram.html

For the Windows Memory Diagnostic Tool.

Type in Cortana's search box ->  Windows Memory Diagnostics at top of the list - click it. in Windows 8/8.1/10 the name is "Windows Memory 
Diagnostic".

====

After doing ALL the updates you can, and if the issue continues, then run 
DriverVerifier. 

Driver Verifier can help find some BSOD issues : 

Using Driver Verifier to identify issues with Windows drivers for advanced users
http://support.microsoft.com/kb/244617

How To Troubleshoot Driver Problems in Windows Vista or 7. (8/8.1 and 10 are essentially the same).
http://www.winvistaclub.com/t79.html

Using Driver Verifier
https://msdn.microsoft.com/en-us/library/windows/hardware/ff545448%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396 

WINKEY + X - RUN - type in -> verifier /reset      hit enter to disable

If Driver Verifier creates a minidump upload it and post the link here so we can analyze it.

Please let us know the results and if you need further assistance.